Aller au contenu

  2. → Affichage d'un profil : Messages: champi07

champi07

Inscrit(e) (le) 18 déc. 2011
Déconnecté Dernière activité juin 04 2012 19:37
-----

Messages que j'ai postés

Dans le sujet : RE-flasher pcb matrix freedom

04 juin 2012 - 10:31

J'ai bien la clé de mon lecteur.
Est-ce possible que ce soit un problème de clé ?
Si je n'ai pas la bonne clé je ne sais pas écrire ?
J'avais pensé à un problème de PC.
Pour ce qui est du matériel utilisé : USB PRO + ALIMENTATION MOLEX (A quoi sert le bouton POWER / SWITCH sur cette dernière ?)

Merci pour votre aide

Si vous avez une idée de test je suis preneur

Dans le sujet : RE-flasher pcb matrix freedom

01 juin 2012 - 09:21

Une idée du pourquoi je ne sais pas écrire ?

Dans le sujet : RE-flasher pcb matrix freedom

01 juin 2012 - 09:11

Bonjour je vais détailler ma manipulation,

Le PCB utilisé est un pcb Matrix freedom déja flashé sans aucun problème sous JF avec la version LT 2.0+

Jungle Flasher detecte le matériel : voir image 1
...
Je lance Intro / Device ID
...
Pas de problème : voir image 2
...
Je lance un "Read"
...
Pas de problème : voir image 3
...
Maintenant je lance un Write --> ça se gâte Problème sur SPI : image 4
...
Je lance la commande 0x80 --> ça se passe bien : image 5
...
Je relance un Write --> et la je bloque sur writing bank 0 : image 6

Je ne comprend pas un dirai un winbond briqué....

Merci pour votre aide


Dans le sujet : RE-flasher pcb matrix freedom

01 juin 2012 - 09:10

Voici le reste des images + log

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
JungleFlasher 0.1.92 Beta (304)
Session Started Fri Jun 01 09:24:39 2012
This is a 32 bit process running on 4 x 32 bit CPUs
X360USB PRO detected, Version 0.18
portio32.sys Driver Installed
portio32.sys Driver Started, thanks Schtrom !
Found 6 I/O Ports.
Found 3 Com Ports.
Found 3 windows drives C: <img src='http://www.logic-sunrise.com/forums/public/style_emoticons/default/ohno.gif' class='bbc_emoticon' alt='D:' /> E:
Found 1 CD/DVD drives E:
Sending Vendor Intro to port 0x0000
Status 0x51
Sending Vendor Intro to port 0x0000
Status 0x51
Re-sending Vendor Intro:
.
Serial flash found with Status 0x72
Sending Device ID request to port 0x0000
Spi Status: 0x8C
Manufacturer ID: 0xEF
Device ID: 0x11
Flash Name:  Winbond/NEX(W25P20/NX25P20)
Flash Size:  262144 bytes
Getting Status from port 0x0000
Serial flash found with Status 0x72
Reading Drive Key.
............
Stage 1 failed
Authorisation Failed!
Getting Status from port 0x0000
Serial flash found with Status 0x72
Reading Bank 0: ................
Reading Bank 1: ................
Reading Bank 2: ................
Reading Bank 3: ................
Dumped in 9937mS
Loading firmware from buffer
Drive key @ n/a A141C12E950E93389B35C9FA0BAAEC8F
Firmware Osig: [PLDS	DG-16D4S		0225]
Firmware is:  LT-Plus 2.0					
Key database updated
Auto-Loading firmware file C:\JungleFlasher v0.1.92 Beta (304)\firmware\LTPlus-0225-v3.0.bin
MD5 hash:  1a38d3a2a6519339599fa1866642c513
Genuine LT plus v3.0
Drive key @ n/a FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
Firmware Osig: [PLDS	DG-16D4S		0225]
Firmware is:  LT-Plus 3.0					
Spoofing Target
DVD Key copied to target
Key Sector copied from Source to Target
Target is LT - ID strings not copied to Target

Loading MTK_Flash source file
Sending Spi UnLock request to Port 0x0000
Spi Status: 0x00
Sending Lite-On-Erase request to port 0x0000
..............
Drive returned Status 0x72
Manufacturer ID: 0x0
Device ID: 0x0
Flash Name:  Unknown type
Flash Size:  n/a
Unknown flash type Write aborted !
Unknown flash type Write aborted !
Sending Vendor Intro to port 0x0000
Serial flash found with Status 0x72
Sending Device ID request to port 0x0000
Spi Status: 0x00
Manufacturer ID: 0x0
Device ID: 0x0
Flash Name:  Unknown type
Flash Size:  n/a
Unknown flash type Write aborted !
Sending Vendor Intro to port 0x0000
Serial flash found with Status 0x72
Sending Device ID request to port 0x0000
Spi Status: 0x8C
Manufacturer ID: 0xEF
Device ID: 0x11
Flash Name:  Winbond/NEX(W25P20/NX25P20)
Flash Size:  262144 bytes
Getting Status from port 0x0000
SPi flash found with Status 0x72
Spi is locked, Aborting!
Sending Spi UnLock request to Port 0x0000
Spi Status: 0x00
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: .XECUTER X360USB PRO removed.
XECUTER X360USB PRO attached.
Drive is Slim Lite-On..
Key found in KeyDB at record (2 - N/A)
Key is: A141C12E950E93389B35C9FA0BAAEC8F
Key has been tested and verified, thanks C4eva !
Sending Vendor Intro to port 0x0000
Status 0x51
Sending Vendor Intro to port 0x0000
Serial flash found with Status 0x72
Sending Device ID request to port 0x0000
Spi Status: 0x8C
Manufacturer ID: 0xEF
Device ID: 0x11
Flash Name:  Winbond/NEX(W25P20/NX25P20)
Flash Size:  262144 bytes
Sending Spi UnLock request to Port 0x0000
Spi Status: 0x00
Lite-On-Erase NOT sent
Getting Status from port 0x0000
SPi flash found with Status 0x72
Spi is locked, Aborting!
Sending Vendor Intro to port 0x0000
Serial flash found with Status 0x72
Sending Device ID request to port 0x0000
Spi Status: 0x00
Manufacturer ID: 0x0
Device ID: 0x0
Flash Name:  Unknown type
Flash Size:  n/a
Sending Vendor Intro to port 0x0000
Serial flash found with Status 0x72
Sending Device ID request to port 0x0000
Spi Status: 0x00
Manufacturer ID: 0x0
Device ID: 0x0
Flash Name:  Unknown type
Flash Size:  n/a
Sending Vendor Intro to port 0x0000
Serial flash found with Status 0x72
Sending Device ID request to port 0x0000
Spi Status: 0x8C
Manufacturer ID: 0xEF
Device ID: 0x11
Flash Name:  Winbond/NEX(W25P20/NX25P20)
Flash Size:  262144 bytes
Getting Status from port 0x0000
SPi flash found with Status 0x72
Spi is locked, Aborting!
XECUTER X360USB PRO removed.
Sending Vendor Intro to port 0x7090
Status 0xD0
XECUTER X360USB PRO attached.
Drive is Slim Lite-On..
Key found in KeyDB at record (2 - N/A)
Key is: A141C12E950E93389B35C9FA0BAAEC8F
Key has been tested and verified, thanks C4eva !
Sending Vendor Intro to port 0x0000
Status 0x51
Re-sending Vendor Intro:
.
Serial flash found with Status 0x72
Sending Device ID request to port 0x0000
Spi Status: 0x8C
Manufacturer ID: 0xEF
Device ID: 0x11
Flash Name:  Winbond/NEX(W25P20/NX25P20)
Flash Size:  262144 bytes
Getting Status from port 0x0000
Serial flash found with Status 0x72
Reading Bank 0: ................
Reading Bank 1: ................
Reading Bank 2: ................
Reading Bank 3: ................
Dumped in 10141mS
Loading firmware from buffer
Drive key @ n/a A141C12E950E93389B35C9FA0BAAEC8F
Firmware Osig: [PLDS	DG-16D4S		0225]
Firmware is:  LT-Plus 2.0					
Key database updated
Auto-Loading firmware file C:\JungleFlasher v0.1.92 Beta (304)\firmware\LTPlus-0225-v3.0.bin
MD5 hash:  1a38d3a2a6519339599fa1866642c513
Genuine LT plus v3.0
Drive key @ n/a FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
Firmware Osig: [PLDS	DG-16D4S		0225]
Firmware is:  LT-Plus 3.0					
Spoofing Target
DVD Key copied to target
Key Sector copied from Source to Target
Target is LT - ID strings not copied to Target

Loading MTK_Flash source file
Getting Status from port 0x0000
SPi flash found with Status 0x72
Spi is locked, Aborting!
Loading firmware file C:\Matrix\fw\beber\LTPlus-0225-v3.0u.bin
MD5 hash:  db5c70eaaabb53501c2c4f53dce9abfd
Genuine LT plus v3.0 (9504 upgrade)
Drive key @ n/a FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
Firmware Osig: [PLDS	DG-16D4S		0225]
Firmware is:  LT-Plus 3.0					
Spoofing Target
DVD Key copied to target
Key Sector copied from Source to Target
Target is LT - ID strings not copied to Target

Sending Spi UnLock request to Port 0x0000
Spi Status: 0x00
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: .
Getting Status from port 0x0000
Invalid Status 0x0
Getting Status from port 0x0000
Invalid Status 0x0

Dans le sujet : RE-flasher pcb matrix freedom

01 juin 2012 - 09:09

Bonjour je vais détailler ma manipulation,

Le PCB utilisé est un pcb Matrix freedom déja flashé sans aucun problème sous JF avec la version LT 2.0+

Jungle Flasher detecte le matériel : voir image 1
...
Je lance Intro / Device ID
...
Pas de problème : voir image 2
...
Je lance un "Read"
...
Pas de problème : voir image 3
...
Maintenant je lance un Write --> ça se gâte Problème sur SPI : image 4
...
Je lance la commande 0x80 --> ça se passe bien : image 5
...
Je relance un Write --> et la je bloque sur writing bank 0 : image 6

Je ne comprend pas un dirai un winbond briqué....

Merci pour votre aide

  1. LS forums
  2. → Affichage d'un profil : Messages: champi07
  3. Privacy Policy