Unconfigured Ad Widget

Collapse

Announcement

Collapse
No announcement yet.

Honor 9 (STF-L09) - Found and connected to USB via Testpoints... wat do now?

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

  • Honor 9 (STF-L09) - Found and connected to USB via Testpoints... wat do now?

    Hi,

    Since DC-Phoenix killed my smartphone some month ago I finaly found a solution and connected it via Testpoints to Computer. It is shown up as "USB SER" in Device Manager with a yellow "!"...
    Now I don't know what I must do next. Anyone can help me please?

    EDIT.: FOUND the right drivers ... now it shows HUAWEI USB COM 1.0 (COM3) in Device Manager
    Not recognized by DC-Phoenix -
    "Looking for a device in upgrade mode
    No devices detected in upgrade mode

    Looking for a device in
    fastboot mode
    No devices detected in
    fastboot mode

    No device detected to update"

    Last edited by C3lv1c3; 2018-09-24, 03:56 PM.

  • #2
    Have you selected board software for flashing? All other files won't suit for this mode. See 3rd method from dc-phoenix guide.
    >>Free Octohide VPN for Android, find it on Google Play Here<<

    Comment


    • #3
      Originally posted by Valdemaras View Post
      Have you selected board software for flashing? All other files won't suit for this mode. See 3rd method from dc-phoenix guide.
      Hi, I selected "Stanford-L09_C432B130_Firmware_Belgium_Germany_France_Nethe rlands_Portugal_Switzerland_Spain_Italy_Austria_Po land_Denmark_Finland_Czech_Republic_Hungary.APP" file.

      I think I need a file specially for testpoint flashing. THX for help!
      Can you make such a file?

      Comment


      • #4
        FIXED:
        Phone revived.
        I used Stanford-AL10_STFAL00S001028_Board Software_general_Android 7.0_EMUI5.1_05022CLB

        Comment


        • #5
          Ok sorry for multi post:

          Phone got revived from dead.
          It is stuck now in DCPhoenix:
          "Writing rescue_recovery partition with file recovery" in DC-Phoenix (Loads and Loads and Loads already finished 4 times nothing happens anymore)
          -Huawei eRecovery is opened on the smartphone.

          what do now?

          Comment


          • #6
            Flash another full stock rom. Make sure phone boots up after flashing board software alone.
            >>Free Octohide VPN for Android, find it on Google Play Here<<

            Comment


            • #7
              worked.
              Do you know how to get back Huawei Boot up Animation back? when I turn on smartphone only some strange red and green colors show up instead.

              Also any way to get OTA back? IMEI/Model Nr. are totaly wrong in Software. Huawei Updater doesn't open.

              Comment


              • #8
                After flashing board software you must flash full stock rom in hopes for your animations to return. You also may need to repair sn/imei and rest of the info on hcu as guide advices if you read it at least once.
                >>Free Octohide VPN for Android, find it on Google Play Here<<

                Comment


                • #9
                  I can't revive the phone with new DC Phoenixes (105 and above).

                  DC Phoenix 0.0.0.115
                  user:radiotrance_l1y

                  Looking for a device in force upgrade mode
                  Device detected:
                  COM7: HUAWEI USB COM 1.0 (COM7)
                  08.08.2019 19:10:01 Starting to write device in FASTBOOT mode...
                  File to update: Stanford-AL10_STFAL00S001028_Board Software_general_Android 7.0_EMUI5.1_05022CLB.dgtks
                  Device detected:
                  COM7: HUAWEI USB COM 1.0 (COM7)

                  Process identifier:17522667


                  Writing bootloader...
                  Writing Stanford-AL10_STFAL00S001028_Board Software_general_Android 7.0_EMUI5.1_05022CLB_3.dtwork...

                  USB Device REMOVAL
                  Type: @oem122.inf,%qcomdevice00%;HUAWEI USB COM 1.0
                  VidPid: VID_12D1&PID_3609
                  Instance id: 6&35278267&2&2


                  USB Device INSERTION
                  Type: @oem122.inf,%qcomdevice00%;HUAWEI USB COM 1.0
                  VidPid: VID_12D1&PID_3609
                  Instance id: 6&35278267&2&2


                  Error writing Bootloader
                  08.08.2019 19:10:12 Writing device finished - INCOMPLETE

                  Phone is in bootloop. eMMC chip was retracted form the board and tested.
                  What could be done?

                  Comment


                  • #10
                    You should use loader + oeminfo solution, after phone's in fastboot use firmware that is in mobile for highest chance to revive it.
                    >>Free Octohide VPN for Android, find it on Google Play Here<<

                    Comment


                    • #11
                      Could you please be more specific? How to use this solution and which loader to select?

                      Comment


                      • #12
                        Originally posted by Radiotrance View Post
                        Could you please be more specific? How to use this solution and which loader to select?
                        Connect phone via testpoint
                        Select correct bootloader on DC-phoenix
                        Write your wished data in OEMINFO secion, it must match firmware file data that you want to update your device with
                        More info here http://forum.gsmhosting.com/vbb/f100...other-2533473/
                        >>Free Octohide VPN for Android, find it on Google Play Here<<

                        Comment

                        Working...
                        X