5.00

Ok merci,
Donc si j'ai bien compris en installant le CFW 6.60 ME-1.8 (http://www.pspgen.com/divers/telecharger-199764.html), le firmware s'installe su la sd sans toucher a mon 5.00 m33 qui lui reste le firmeware propre a la mémoire interne de la psp.
J'ai bon ?

repair/restore with :

redsn0w 0.9.15b3

Extras
Even more
Restore
IPSW
iPhone4,1_6.1.3_10B329_Restore


en cas de tout souci avec l'iphone 4s ou tout modele iphone, je fais cette manip qui fonctionne a 100%,
pour tout les autres modeles suivre le lien internet, choisissez votre .ipsw en faisant cette meme manip,
aucune erreur 3194, 1015 ou autre, helas cela ne concerne que la restauration et non l'unlockage (qui ne peut se faire que par l'operateur "sfr, orange, etc),
mais au moins l'iphone retrouve ses fonctions et une bonne base, pour tout les testeurs de jailbreak.





Jailbreak (for) :
http://ih8sn0w.com/index.php/download/f ... wbreeze/pc

news for jailbreak -> ios7
http://www.evasionjailbreak.com/apple-a ... velopment/

infos en plus :
copier Redsnow + IPSW dans un dossier sur le bureau
redsn0w 0.9.15b3 : executer en tant qu'administrateur (windows8)
iTunes ouvert pendant ce processus

pour unlock : cydia -> ultrasnow (la recherche marche aussi) redemarrer, et c'est tout

pour un bon jailbreak via snowbreeze :

http://ih8sn0w.com/index.php/download/f ... wbreeze/pc



une fois IPSW snowbreeze créé, dans iTunes : shift + clic souris (PC) sur "restaurer" et selectionner votre IPSW snowbreeze
attendez la fin du processus, et voilà votre iphone est jailbreaké et pour unlock : cydia -> ultrasnow (la recherche marche aussi) redemarrer
(uniquement pour puce non-A5) et ce avec ou sans sauvegarde tinyumbrella-6.14.00

Bienvenue sur PSPGen! Vu que tu possèdes une PSP 1000 en 5.00 M33, le meilleur reste pour toi de mettre à jour en CFW 6.60 ME-1.8 (inutile d"installer la mise à jour officielle).

Oui précise, tu tombes sur ce message :

- Quand tu veux lancer PSPGen Version Builder ?
- Après utilisation de PSPGen Version Builder ?
- Ou bien toujours lors du lancement de l'installeur du LCFW 6.60 ME-1.8 ?

Dans PSPGen Version Builder, tu as bien écrit 5.50, et non une version supérieur à 6.60 ni la version 0.00 ?

voila j'ai essayer burnermax, et j'ai aussi la derniere mise a jour de l'iXtreme burner
mais ça marche toujours pas, je ne sais pas ce qui cloche

log :
I 00:36:58 ImgBurn Version 2.5.7.0 started!
I 00:36:58 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7601 : Service Pack 1)
I 00:36:58 Total Physical Memory: 3 145 272 KB - Available: 1 864 964 KB
I 00:36:58 Initialising SPTI...
I 00:36:58 Searching for SCSI / ATAPI devices...
I 00:36:58 -> Drive 1 - Info: DTSOFT BDROM 1.05 (H:) (Virtual)
I 00:36:58 -> Drive 2 - Info: DTSOFT BDROM 1.05 (I:) (Virtual)
I 00:36:58 -> Drive 3 - Info: ATAPI iHAS524 B AL2A (F:) (ATA)
I 00:36:58 Found 1 DVD±RW/RAM and 2 BD-ROMs!
I 00:46:46 Operation Started!
I 00:46:46 Source File: N:\X360\metalgear_revengeance\Metal.Gear.Rising.Revengeance.XBOX360-MARVEL\mvl-mgrr.dvd
I 00:46:46 Source File Sectors: 4 267 015 (MODE1/2048)
I 00:46:46 Source File Size: 8 738 846 720 bytes
I 00:46:46 Source File Volume Identifier: DVD_ROM
I 00:46:46 Source File Volume Set Identifier: 9ad30000MS UDFBridge
I 00:46:46 Source File Application Identifier: CDIMAGE 2.45 (12/06/2000 TM)
I 00:46:46 Source File Implementation Identifier: Microsoft CDIMAGE UDF
I 00:46:46 Source File File System(s): ISO9660; UDF (1.50)
I 00:46:46 Destination Device: [2:0:0] ATAPI iHAS524 B AL2A (F:) (ATA)
I 00:46:46 Destination Media Type: DVD+R DL (Disc ID: MKM-003-00)
I 00:46:46 Destination Media Supported Write Speeds: 2,4x; 4x; 6x; 8x
I 00:46:46 Destination Media Sectors: 4 267 040
I 00:46:46 Write Mode: DVD
I 00:46:46 Write Type: DAO
I 00:46:46 Write Speed: 4x
I 00:46:46 DVD+R DL Reserve Track: No
I 00:46:46 Link Size: Auto
I 00:46:46 Lock Volume: Yes
I 00:46:46 Test Mode: No
I 00:46:46 OPC: No
I 00:46:46 BURN-Proof: Enabled
I 00:46:46 Write Speed Successfully Set! - Effective: 5 540 KB/s (4x)
I 00:46:46 Book Type Setting: DVD-ROM
I 00:46:46 Advanced Settings - Force HT: Yes, Online HT: No, OverSpeed: No, SmartBurn: Yes
I 00:46:46 Optimal L0 Data Zone Capacity: 2 133 520
I 00:46:46 Optimal L0 Data Zone Method: Copied From Original Disc
I 00:46:46 Set L0 Data Zone Capacity Succeeded!
I 00:46:48 Filling Buffer... (40 MB)
I 00:46:49 Writing LeadIn...
I 00:47:20 Writing Session 1 of 1... (1 Track, LBA: 0 - 4267014)
I 00:47:20 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 4267014)
I 00:47:20 Writing Layer 0... (LBA: 0 - 2133519)
W 00:47:24 Failed to Write Sectors 11296 - 11327 - Reason: Logical Unit Communication Time-Out
W 00:47:24 Retrying (1 of 20)...
W 00:47:27 Retry Failed - Reason: Invalid Address For Write
W 00:47:27 Retrying (2 of 20)...
W 00:47:27 Retry Failed - Reason: Invalid Address For Write
W 00:47:27 Retrying (3 of 20)...
W 00:47:27 Retry Failed - Reason: Invalid Address For Write
W 00:47:27 Retrying (4 of 20)...
W 00:47:27 Retry Failed - Reason: Invalid Address For Write
W 00:47:27 Retrying (5 of 20)...
W 00:47:27 Retry Failed - Reason: Invalid Address For Write
W 00:47:27 Retrying (6 of 20)...
W 00:47:27 Retry Failed - Reason: Invalid Address For Write
W 00:47:27 Retrying (7 of 20)...
W 00:47:27 Retry Failed - Reason: Invalid Address For Write
W 00:47:27 Retrying (8 of 20)...
W 00:47:27 Retry Failed - Reason: Invalid Address For Write
W 00:47:27 Retrying (9 of 20)...
W 00:47:27 Retry Failed - Reason: Invalid Address For Write
W 00:47:27 Retrying (10 of 20)...
W 00:47:27 Retry Failed - Reason: Invalid Address For Write
W 00:47:27 Retrying (11 of 20)...
W 00:47:27 Retry Failed - Reason: Invalid Address For Write
W 00:47:27 Retrying (12 of 20)...
W 00:47:27 Retry Failed - Reason: Invalid Address For Write
W 00:47:27 Retrying (13 of 20)...
W 00:47:27 Retry Failed - Reason: Invalid Address For Write
W 00:47:27 Retrying (14 of 20)...
W 00:47:27 Retry Failed - Reason: Invalid Address For Write
W 00:47:27 Retrying (15 of 20)...
W 00:47:27 Retry Failed - Reason: Invalid Address For Write
W 00:47:27 Retrying (16 of 20)...
W 00:47:27 Retry Failed - Reason: Invalid Address For Write
W 00:47:27 Retrying (17 of 20)...
W 00:47:27 Retry Failed - Reason: Invalid Address For Write
W 00:47:27 Retrying (18 of 20)...
W 00:47:28 Retry Failed - Reason: Invalid Address For Write
W 00:47:28 Retrying (19 of 20)...
W 00:47:28 Retry Failed - Reason: Invalid Address For Write
W 00:47:28 Retrying (20 of 20)...
W 00:47:28 Retry Failed - Reason: Invalid Address For Write
W 00:47:46 Retrying (21)...
W 00:47:46 Retry Failed - Reason: Invalid Address For Write
E 00:47:47 Failed to Write Sectors 11296 - 11327 - Reason: Logical Unit Communication Time-Out
E 00:47:47 Next Writable Address: 11312
I 00:47:47 Synchronising Cache...
W 00:47:56 User opted to skip the 'Close Track/Session/Disc' functions.
E 00:47:56 Failed to Write Image!
I 00:47:56 Exporting Graph Data...
I 00:47:57 Graph Data File: C:\Users\CONNARD\AppData\Roaming\ImgBurn\Graph Data Files\ATAPI_iHAS524_B_AL2A_LUNDI-6-MAI-2013_00-46_MKM-003-00_4x.ibg
I 00:47:57 Export Successfully Completed!
E 00:47:57 Operation Failed! - Duration: 00:01:10
I 00:47:57 Average Write Rate: 868 KB/s (0.6x) - Maximum Write Rate: 3 105 KB/s (2.2x)

Bonjour,

j'ai souvent cette meme erreur qui se repete a l'infini lors de la gravure :
"logical unit communcation time out"

mais qu'est ce que ca veut dire ?

je suis sous Windows 7 x64 Edition
j'ai un lecteur ATAPI iHAS524 B AL2A (F:) (ATA)
avec le dernier firmware AL2A
j'ai imgburn Version 2.5.7.0

je grave en 2.4x et 4x avec des verbatim MKM-003-00
j'ai mis les options
Force HT: Yes, Online HT: No, OverSpeed: No, SmartBurn: Yes
layerbreak sur calclulate optimal

et patcher chaque iso avec la derniere version abgx
j'ai regler tous ce qui faut je crois


ca fait peut etre le 20eme dvd que je rate.
je commence a croire que j'ai la poisse....



Avez vous une quelcquonque solution à ce curieux probleme

merci d'avance,

cordialement,
Ninjaa



voila un screenshot de l'erreur


voici le log :
I 23:07:39 ImgBurn Version 2.5.7.0 started!
I 23:07:39 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7601 : Service Pack 1)
I 23:07:39 Total Physical Memory: 3 145 272 KB - Available: 1 478 836 KB
I 23:07:40 Initialising SPTI...
I 23:07:40 Searching for SCSI / ATAPI devices...
I 23:07:40 -> Drive 1 - Info: DTSOFT BDROM 1.05 (H:) (Virtual)
I 23:07:40 -> Drive 2 - Info: DTSOFT BDROM 1.05 (I:) (Virtual)
I 23:07:40 -> Drive 3 - Info: ATAPI iHAS524 B AL2A (F:) (ATA)
I 23:07:40 Found 1 DVD±RW/RAM and 2 BD-ROMs!
I 23:10:36 Operation Started!
I 23:10:36 Source File: N:\X360\metalgear
I 23:10:36 Source File Sectors: 4 267 015 (MODE1/2048)
I 23:10:36 Source File Size: 8 738 846 720 bytes
I 23:10:36 Source File Volume Identifier: DVD_ROM
I 23:10:36 Source File Volume Set Identifier: 9ad30000MS UDFBridge
I 23:10:36 Source File Application Identifier: CDIMAGE 2.45 (12/06/2000 TM)
I 23:10:36 Source File Implementation Identifier: Microsoft CDIMAGE UDF
I 23:10:36 Source File File System(s): ISO9660; UDF (1.50)
I 23:10:36 Destination Device: [2:0:0] ATAPI iHAS524 B AL2A (F:) (ATA)
I 23:10:36 Destination Media Type: DVD+R DL (Disc ID: MKM-003-00)
I 23:10:36 Destination Media Supported Write Speeds: 2,4x; 4x; 6x; 8x
I 23:10:36 Destination Media Sectors: 4 267 040
I 23:10:37 Write Mode: DVD
I 23:10:37 Write Type: DAO
I 23:10:37 Write Speed: 4x
I 23:10:37 DVD+R DL Reserve Track: No
I 23:10:37 Link Size: Auto
I 23:10:37 Lock Volume: Yes
I 23:10:37 Test Mode: No
I 23:10:37 OPC: No
I 23:10:37 BURN-Proof: Enabled
I 23:10:37 Write Speed Successfully Set! - Effective: 5 540 KB/s (4x)
I 23:10:37 Book Type Setting: DVD-ROM
I 23:10:37 Advanced Settings - Force HT: Yes, Online HT: No, OverSpeed: No, SmartBurn: Yes
I 23:10:37 Optimal L0 Data Zone Capacity: 2 133 520
I 23:10:37 Optimal L0 Data Zone Method: Copied From Original Disc
I 23:11:07 Set L0 Data Zone Capacity Succeeded!
I 23:11:09 Filling Buffer... (40 MB)
I 23:11:09 Writing LeadIn...
I 23:11:11 Writing Session 1 of 1... (1 Track, LBA: 0 - 4267014)
I 23:11:11 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 4267014)
I 23:11:12 Writing Layer 0... (LBA: 0 - 2133519)
W 23:17:19 Failed to Write Sectors 984160 - 984191 - Reason: Logical Unit Communication Time-Out
W 23:17:19 Retrying (1 of 20)...
W 23:17:23 Retry Failed - Reason: Invalid Address For Write
W 23:17:23 Retrying (2 of 20)...
W 23:17:23 Retry Failed - Reason: Invalid Address For Write
W 23:17:23 Retrying (3 of 20)...
W 23:17:23 Retry Failed - Reason: Invalid Address For Write
W 23:17:23 Retrying (4 of 20)...
W 23:17:23 Retry Failed - Reason: Invalid Address For Write
W 23:17:23 Retrying (5 of 20)...
W 23:17:23 Retry Failed - Reason: Invalid Address For Write
W 23:17:23 Retrying (6 of 20)...
W 23:17:23 Retry Failed - Reason: Invalid Address For Write
W 23:17:23 Retrying (7 of 20)...
W 23:17:23 Retry Failed - Reason: Invalid Address For Write
W 23:17:23 Retrying (8 of 20)...
W 23:17:23 Retry Failed - Reason: Invalid Address For Write
W 23:17:23 Retrying (9 of 20)...
W 23:17:23 Retry Failed - Reason: Invalid Address For Write
W 23:17:23 Retrying (10 of 20)...
W 23:17:23 Retry Failed - Reason: Invalid Address For Write
W 23:17:23 Retrying (11 of 20)...
W 23:17:23 Retry Failed - Reason: Invalid Address For Write
W 23:17:23 Retrying (12 of 20)...
W 23:17:23 Retry Failed - Reason: Invalid Address For Write
W 23:17:23 Retrying (13 of 20)...
W 23:17:24 Retry Failed - Reason: Invalid Address For Write
W 23:17:24 Retrying (14 of 20)...
W 23:17:24 Retry Failed - Reason: Invalid Address For Write
W 23:17:24 Retrying (15 of 20)...
W 23:17:24 Retry Failed - Reason: Invalid Address For Write
W 23:17:24 Retrying (16 of 20)...
W 23:17:24 Retry Failed - Reason: Invalid Address For Write
W 23:17:24 Retrying (17 of 20)...
W 23:17:24 Retry Failed - Reason: Invalid Address For Write
W 23:17:24 Retrying (18 of 20)...
W 23:17:24 Retry Failed - Reason: Invalid Address For Write
W 23:17:24 Retrying (19 of 20)...
W 23:17:24 Retry Failed - Reason: Invalid Address For Write
W 23:17:24 Retrying (20 of 20)...
W 23:17:24 Retry Failed - Reason: Invalid Address For Write
W 23:18:23 Retrying (21)...
W 23:18:23 Retry Failed - Reason: Invalid Address For Write
W 23:18:24 Retrying (22)...
W 23:18:24 Retry Failed - Reason: Invalid Address For Write
E 23:18:25 Failed to Write Sectors 984160 - 984191 - Reason: Logical Unit Communication Time-Out
E 23:18:25 Next Writable Address: 984176
I 23:18:25 Synchronising Cache...
W 23:18:33 User opted to skip the 'Close Track/Session/Disc' functions.
E 23:18:33 Failed to Write Image!
I 23:18:33 Exporting Graph Data...
I 23:18:33 Graph Data File: C:\Users\CONNARD\AppData\Roaming\ImgBurn\Graph Data Files\ATAPI_iHAS524_B_AL2A_MERCREDI-1-MAI-2013_23-10_MKM-003-00_4x.ibg
I 23:18:33 Export Successfully Completed!
E 23:18:33 Operation Failed! - Duration: 00:07:56
I 23:18:33 Average Write Rate: 4 545 KB/s (3.3x) - Maximum Write Rate: 5 631 KB/s (4.1x)

Pour pouvoir le desimlocker il faut le baseband qui va avec. Pour cela il faut que tu mette le baseband de l'iPad puis ensuite downgrader le base bande en 5.13.04. Pour cela test en 6.1.3 car je ne sais pas si sa fonctionne sinon faudra revenir au 4.1. Donc premièrement tu lance redsnow tu fais extra puis select ipsw. Tu sélectionne l'ipsw 6.0 ensuite tu clique sur jailbreak. Tu décoche cydia et coche install baseband ipad. Une fois fait vérifié que ton baseband est en 6.15.00. Si c'est le cas tu peux faire le downgrade du baseband en suivant ce tuto: http://www.iphonegen.fr/downgrade-iphone-avec-baseband-ipad-06-15-00-article-9412-1.html. Insiste si sa marche pas du premier coup. Ensuite si tu es bien en 5.13.04 tu met ultrasnow et sa sera bon.

comme Firefox la dit downgrade ton baseband en 5.13.04. Tu as le tuto ici: http://www.iphonegen.fr/downgrade-iphone-avec-baseband-ipad-06-15-00-article-9412-1.html

Merci mamoul et... autant pour moi. Le Gears judgment est bien Basic Stealth mais il y a quand même des lignes en jaune et....
J'aime pô les lignes en jaune.
Bref.. voici le log d'abgx (j'ai remis les couleurs telles qu'elles sont affichées exceptions faites du jaune que j'ai mis en orange pour faciliter la lecture) :

****************GEARS Judgment (log ABGX)************************
Files in ISO: 2329, Folders in ISO: 6
Total bytes used: 7573448751 (87.43%)
Game appears to have random padding

Checking default.xex
Original PE Filename: GearGame-Xbox360-Shipping.pe
Original PE Timestamp: 2013/01/26 05:09:52
Min Kernel Required: v2.0.15574.0
Game Name: Gears of War: Judgment
No Avatar Awards
Achievements: 50 Achievements totaling 1000 Gamerscore
XEX CRC = CA6F4228
XEX Media ID: 9FBDAE7F981389A6F6D2EA3A-540C7CD0

Region Code: 0xFFFFFFFF
Region Free!

Checking topology data
Querying the online database to find the appropriate verified data to use...
Querying the online database
100% [================================>] 35 2.3 KB/s ETA 00:00
Topology information was downloaded successfully

Looking for TOP_XGD3-DID-F87A804E_v1.sha1 in the online verified database
Server file TOP_XGD3-DID-F87A804E_v1.sha1 no newer than local file - not re
trieving
Topology data is currently verified

Checking SS
Timestamp of Authoring: 2013/01/30 00:00:00
Timestamp of Mastering: 2013/02/11 17:46:44
SS Version: 2 (trusted)
SS CRC = A8D95716 (RawSS = 0B104FB5)
SS Media ID: 9FBDAE7F981389A6F6D2EA3A-540C7CD0 (matches game)
SS looks valid

Checking DMI
Timestamp of Authoring: 2013/01/30 00:00:00 (matches SS)
DMI CRC = 10C29F23
DMI Media ID: 9FBDAE7F981389A6F6D2EA3A-540C7CD0 (matches game)
DMI looks valid

Checking PFI
PFI CRC = 26AF4C58
PFI matches known data (XGD3)

Video partition found
Checking L0 Video padding... L0 Video is zero padded
Checking L1 Video padding... L1 Video is zero padded
Checking XGD3 Stealth padding... XGD3 Stealth is zero padded
Video CRC = 7CA74873 (V0 = E19EDCAB, V1 = BF9ADA5F)

Basic Stealth check passed!

Starting Verification
Looking for A8D95716CA6F4228.ini in the online verified database
There is no verified rip of this Xex/SS combination in the online database
Failed to find a verified ini file for this Xex/SS combination
Verification failed

Starting AutoFix
Looking for Xex_CA6F4228.ini in the online verified database
There is no verified rip of Xex CRC CA6F4228 in the online database
Failed to find a verified ini file for this Xex
AutoFix Failed, Stealth is still unverified

Checking for AnyDVD style game data corruption while running CRC check...

Checking Game CRC... (press Q to cancel)
Percent Elapsed Estimated Time Average Current Errors Total
Done Time Time Left Speed Speed Recovered Retries
100% 0:42 0:42 0:00 195.8 MB/s 187.4 MB/s

AnyDVD style corruption was not detected
Game CRC = ABE373F0


Press any key to exit . . .
****************GEARS Judgment (FIN log ABGX)*********************


Alors que pour le Gears 3 que j'ai aussi rippé moi-même personnellement tout seul j'ai (pour la fin uniquement hein !):

****************GEARS 3 (Log ABGX)*******************************
Video partition found
Checking L0 Video padding... L0 Video is zero padded
Checking L1 Video padding... L1 Video is zero padded
Checking XGD3 Stealth padding... XGD3 Stealth is zero padded
Video CRC = 40D4DB0D (V0 = 4E61AF96, V1 = 74BC19E0)

Basic Stealth check passed!

Starting Verification
Looking for 9138A749DC1BD8B2.ini in the online verified database
Downloading 9138A749DC1BD8B2.ini
100% [================================>] 327 21.3 KB/s ETA 00:00
9138A749DC1BD8B2.ini was downloaded successfully

Using 9138A749DC1BD8B2.ini (327 bytes)
Video CRC matches
V0 CRC matches
V1 CRC matches
PFI CRC matches
DMI CRC matches
SS CRC matches
Xex CRC matches

Checking Game CRC... (press Q to cancel)
Percent Elapsed Estimated Time Average Current Errors Total
Done Time Time Left Speed Speed Recovered Retries
100% 2:08 2:08 0:00 64.5 MB/s 64.4 MB/s

AnyDVD style corruption was not detected
Game CRC = 5B6A94AB (matches)

All CRCs match
Verification was successful!

Press any key to exit . . .
****************GEARS 3 (FIN Log ABGX)***************************
Voili.

J'ai également une autre question :
Je m'apprête à ripper les 2 précédents opus de Gears (1 et 2 donc) et je m'interroge sur l'utilité de le faire dans la mesure où un ami me l'avait déjà fait à l'époque. Je peux donc refaire un ISO de mes backups via imgburn et les repasser sous abgx histoire de les patcher avec les "nouveaux"... euh.. patches ?

Merci