afghanjohnny
03-12-2006, 00:36
I flashed a K600 with R2J005 yesterday and after stupidly pressing "repair/unlock" in sonicsbox before uploading customize.xml the phone now subbornly wont take certloaders. I canīt even "Read CID" anymore.
Recover in DVT 13.8 reports sucess on CID19 but nothing changes.
Recover in TMS just says that my battery is depleted which it isnīt.
Recover in Sonicsbox is an sucess for CID36 Red, but nothing changes.
Recover in SETool cracked reports the following:
----------------
GUI v0.91373/UNI
standalone version engaged.
Card serial:xxxxxxxxx
Loaded 49 flash descriptors
RECOVERY MODE STARTED
Open COM port OK
PHONE IS INVISIBLE (00000000)
Recovery:041213 1451 MATCXC1325413_CERTLOADER R3S
Fetching phone data from OTP
OTP status:0 locked:1 CID:36 PAF:0 IMEI:NUMBERSOMITTED CERT:RED
bad file, will not flash it.
Recovery failed. Phone dead.
Elapsed:11 secs.
-----------------
Which file is bad by the way, why will it not flash it?
Any ideas? I read that the K608i had a resistor that sometimes had to be shortcircuted, is it the same for K600?
Could a miniUSB cable be the trick?
Recover in DVT 13.8 reports sucess on CID19 but nothing changes.
Recover in TMS just says that my battery is depleted which it isnīt.
Recover in Sonicsbox is an sucess for CID36 Red, but nothing changes.
Recover in SETool cracked reports the following:
----------------
GUI v0.91373/UNI
standalone version engaged.
Card serial:xxxxxxxxx
Loaded 49 flash descriptors
RECOVERY MODE STARTED
Open COM port OK
PHONE IS INVISIBLE (00000000)
Recovery:041213 1451 MATCXC1325413_CERTLOADER R3S
Fetching phone data from OTP
OTP status:0 locked:1 CID:36 PAF:0 IMEI:NUMBERSOMITTED CERT:RED
bad file, will not flash it.
Recovery failed. Phone dead.
Elapsed:11 secs.
-----------------
Which file is bad by the way, why will it not flash it?
Any ideas? I read that the K608i had a resistor that sometimes had to be shortcircuted, is it the same for K600?
Could a miniUSB cable be the trick?