Announcement

Collapse
No announcement yet.

RIFF JTAG – Easy repair HTC Butterfly S 901s 4G LTE supported

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • RIFF JTAG – Easy repair HTC Butterfly S 901s 4G LTE supported

    RIFF JTAG – Easy repair HTC Butterfly S 901s 4G LTE supported Repairing bricked HTC Butterfly S (PO6821000) is easy with the RIFF Box. Phone is auto powered on with USB Data Cable connected to the PC. Battery presence may be required. In case you have no USB cable near, make sure battery is charged […]

    More...
    ICQ: 299-912-089
    QQ: 1634811353

  • #2
    Dear Legija.
    Error with resurrector at restoring HTC Butterfly S (PO6821000)

    Open serial port...OK
    Connecting to the RIFF Box...OK
    Firmware Version: 1.37, JTAG Manager Version: 1.56
    Selected Resurrector: [HTC Butterfly S (PO6821000) V1.0.5095.52956]

    Connecting to the dead body...OK
    Detected dead body ID: 0x2071B0E1 - WRONG!!!
    ERROR: Current ID does not belong to the HTC Butterfly S (PO6821000) family.

    Pinout of resurrector was not true, was used pinout of Batterfly PL9911000. Resurrector from PL9911000 gave the same error. In what could be the cause of the error (not a valid resurrector?)

    Comment


    • #3
      Disable checking ID

      Comment


      • #4
        If you ignore the ID

        Open serial port...OK
        Connecting to the RIFF Box...OK
        Firmware Version: 1.37, JTAG Manager Version: 1.56
        Selected Resurrector: [HTC Butterfly S (PO6821000) V1.0.5095.52956]

        Connecting to the dead body...OK
        Detected dead body ID: 0x2071B0E1 - IGNORED!
        Set I/O Voltage reads as 1.81V, TCK Frequency is RTCK
        Adaptive Clocking RTCK Sampling is: [Sample at MAX]

        Resurrection sequence started.
        Establish communication with the phone...OK
        Initializing internal hardware configuration...OK
        Uploading resurrector data into memory...OK
        Starting communication with resurrector...OK

        Detected an Initialized FLASH1 Chip, ID: 0x0045/0x0100 (SEM16G, 0x0003AB400000 Bytes = 14.68 GB)
        Detected an Initialized FLASH2 Chip, ID: 0x0045/0x0100 (SEM16G, 0x000000400000 Bytes = 4.00 MB)

        Flashing the dead body...
        ERROR: DCC Loader has reported Error Code = 0x51 (0x000000). Trying to recover...OK
        ERROR: DCC Loader has reported Error Code = 0x51 (0x000000). Trying to recover...OK
        ERROR: DCC Loader has reported Error Code = 0x51 (0x000000). Trying to recover...OK
        ERROR: Stopped due to multiple communication errors. Terminating at 0x000000000000

        Comment


        • #5
          And now try to reduce the frequency, but it seems that the problem with memory
          Last edited by vekt; 08-19-2014, 03:46 PM.

          Comment

          Working...
          X