|
Welcome to the GSM-Forum forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. Only registered members may post questions, contact other members or search our database of over 8 million posts. Registration is fast, simple and absolutely free so please - Click to REGISTER! If you have any problems with the registration process or your account login, please contact contact us . |
|
Register | FAQ | Donate | Forum Rules | Root any Device | ★iPhone Unlock★ | ★ Direct Codes ★ | Direct Unlock Source |
| LinkBack | Thread Tools | Display Modes |
02-10-2013, 17:22 | #1 (permalink) |
Freak Poster Join Date: Jun 2012
Posts: 109
Member: 1772418 Status: Offline Thanks Meter: 7 | T999 No response from the RIFF Box. I recived this phone a few days ago. The problem was caused by installing a custom launcher for the phone. While resurrecting and trying to use the DCC tab i get this: ------------------------------------------------------- Open serial port...OK Connecting to the RIFF Box...OK Firmware Version: 1.34, JTAG Manager Version: 1.48 Selected Resurrector: [Samsung T999 V1.0.4716.5824] Connecting to the dead body...OK Detected dead body ID: 0x407910E1 - CORRECT! Set I/O Voltage reads as 1.82V, TCK Frequency is RTCK Adaptive Clocking RTCK Sampling is: [Sample at 9 MHz] Resurrection sequence started. Establish communication with the phone...OK Initializing internal hardware configuration...OK Uploading resurrector data into memory...OK Starting communication with resurrector...FAILED ERROR: No response from the RIFF Box. ------------------------------------------------------- I´ve used all of the speeds but i get this same message every time. The conections have been done about 4 times using different cables. Tried with and without: Ground conection, battery, USB plugged, external power from the power supply. The device i belive it is not damaged, i can still: Read ICE registry, apply NRST, Reset it, halt it and alanize its JTAG chain all with good results. Any ideas? Supporters, is the DLL final or you´ve noticed similar behavior and working on it? -------------------------------------------------------- Resetting target...OK STATUS: Target is halted. R0 = 0x00005DC0 R6 = 0x00000001 R12 = 0x00000000 R1 = 0x00000000 R7 = 0x00000000 R13 = 0x0002DF08 R2 = 0x00000001 R8 = 0x00001388 R14 = 0x0000E368 R3 = 0x0002DF28 R9 = 0x000203E0 R15 = 0x00018194 R4 = 0x00001388 R10 = 0x00000000 CPSR = 0x800000D3 R5 = 0x00062000 R11 = 0x00000000 ----------------------------------------------------------- Halting target...OK STATUS: Target is halted. R0 = 0x000005E9 R6 = 0x00000000 R12 = 0x58FBA05A R1 = 0xFFFFFFF9 R7 = 0x12400000 R13 = 0x2A003C10 R2 = 0x00000001 R8 = 0x00902820 R14 = 0x2A002520 R3 = 0x00000000 R9 = 0xFF00FF80 R15 = 0x2A001BE0 R4 = 0x2A003C3C R10 = 0x00036BC7 CPSR = 0x200000D3 R5 = 0x2A00320C R11 = 0x40FF0080 |
Bookmarks |
| |
|