Unconfigured Ad Widget

Collapse

Announcement

Collapse
No announcement yet.

Bricked Huawei P20 Lite

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

  • Bricked Huawei P20 Lite

    Hello,

    My P20 Lite bricked for no reason (while usual charging). Bootloop on Huawei Logo. I tried to flash
    Anne-L21 9.1.0.132(C10E3R1P6T8)_Firmware_9.0.0_r3_EMUI9.1.0 _05015ABF
    but flashing always failed on going to upgrade mode cause of the bootlop on Huawei logo (even if I try to do it by myself).

    Then I tried to enable software testpoint, however the same problem apper — can't go in upgrade mode.

    After that, Anne-L21 9.1.0.368(C431E6R1P7T8) Firmware EMUI9.1.0 05015UJQ also failed on upgrade mode

    And now I dunno what to do:
    Code:
    DC Phoenix 0.0.0.158
    user:
    
    Looking for a device in upgrade mode
    No devices detected in upgrade mode
    Device found: 9WV4C18603007989
    
    
    Standard update
    Not Reboot NOT checked
    Update Verlist to server on file load NOT checked
    Enable testpoint NOT checked
    Disable testpoint NOT checked
    Try Rescue Recovery checked
    Bypass version check NOT checked
    Old slow algo checked
    
    Detecting recovery partition
    File size: 5,425,328,760 bytes
    Current version(CURVER): ANE_GLOBAL_CUST 9.1.0(C999)
    ERECOVERY_KERNEL partition found
    ERECOVERY_RAMDISK partition found
    ERECOVERY_VENDOR partition found
    
    07-May-21 00:32:43 Starting to try Rescue Recovery...
    
    
    Looking for a device in fastboot mode
    Device found: 9WV4C18603007989
    
    
    Getting IMEI...
    Getting build number...
    Getting model ...
    Getting battery state...
    Getting backdoor info...
    Getting lock state info...
    Getting lock boot info...
    
    Build number: :ANE-LX1 9.1.0.315(C10E6R1P6)
    Model: ANE-LX1
    Vendor/Country: hw/ru
    Battery state: 3686mv
    OEM lock state info:
    FB LockState: LOCKED
    USER LockState: LOCKED
    OEM get bootinfo:
    locked
    
    Getting base version...
    Base Version: ANE-LGRP2-OVS 9.1.0.315
    Getting cust version...
    Cust Version: ANE-LX1-CUST 9.1.0.6(C10)
    Getting preload version...
    Preload Version: ANE-LX1-PRELOAD 9.1.0.6(C10R1)
    
    Process identifier:31313055
    
    
    Erasing ver .. .
    File size: 5,425,328,760 bytes
    Current version(CURVER): ANE_GLOBAL_CUST 9.1.0(C999)
    Writing rescue_recovery_kernel partition
    RESCUE_RECOVERY_KERNEL partition update ...OK
    Writing rescue_recovery_ramdisk partition
    RESCUE_RECOVERY_RAMDISK partition update ...OK
    Writing rescue_recovery_vendor partition
    RESCUE_RECOVERY_VENDOR partition update ...OK
    Update recovery parttion OK
    Looking for device in upgrade mode...
    
    USB Device REMOVAL
    Type: @oem39.inf,%hwfastboot%;Android Sooner Single ADB Interface
    VidPid: VID_18D1&PID_D00D
    Instance id: 5&3478949&0&4
    Process was cancelled by user
    Enter recovery mode FAIL
    
    Cannot enter in Recovery mode
    Looking for some advice and guidance,
    Best regards
    Last edited by kot.kma; 2021-05-06, 09:52 PM. Reason: wrong log

  • #2
    We do not have specific solutions for specific problems, we just provide tools for flashing, sadly from your explanation it may as well be hardware fault, phone's don't get bricked just by charging them, maybe unless it was modified in the past. At this point can only try to put it in testpoint mode and attempt to flash board software file, maybe will help in your case. board software files have "board software" or "board firmware" words in file name. Can try to look up on DC-phoenix support area.
    >>Free Octohide VPN for Android, find it on Google Play Here<<

    Comment


    • #3
      I tried to put in software testpoint, but there is the same error — can't go in upgrade mode. Now I'll try to do hardware TP.
      UPD: Ok, I'm done with dissasembly. Is it ok to short TP while phone is ON and stack on Huawei Logo? Or phone must be turned off while that process?
      Last edited by kot.kma; 2021-05-08, 10:24 AM. Reason: UPD

      Comment


      • #4
        How should I decide? Google can't help.

        Heeelp! Timer...
        You do not have permission to view this gallery.
        This gallery has 1 photos.
        Last edited by kot.kma; 2021-05-08, 01:12 PM.

        Comment


        • #5
          The result of flashing board via hardware TP:

          Code:
          DC Phoenix 0.0.0.158
          user:kot.kma
          
          Device detected:
          COM12: HUAWEI USB COM 1.0 (COM12)
          BOOTLOADER selected to update:Kirin659_T0_A8.0_V2
          08-May-21 19:21:48 Starting to write device...
          
          Process identifier:31334121
          
          Validating file...
          
          Writing bootloader...
          Step 1...
          Step 2...
          
          Waiting for device REMOVAL/INSERTION...
          
          Waiting for fastboot device...
          
          USB Device REMOVAL
          Type: @oem64.inf,%qcomdevice00%;HUAWEI USB COM 1.0
          VidPid: VID_12D1&PID_3609
          Instance id: 5&3478949&0&1
          
          USB Device INSERTION
          Type: @oem39.inf,%hwfastboot%;Android Sooner Single ADB Interface
          VidPid: VID_18D1&PID_D00D
          Instance id: 5&3478949&0&1
          Device found: 9WV4C18603007989
          
          
          Looking for a device in fastboot mode
          Device found: 9WV4C18603007989
          
          
          Getting IMEI...
          Getting build number...
          Getting model ...
          Getting battery state...
          Getting backdoor info...
          Getting lock state info...
          Getting lock boot info...
          
          SN:9WV4C18603007989
          IMEI:863675040855475
          IMEI1:863675040881489
          MEID:00000000000000
          Build number: :ANE-LX1 9.1.0.315(C10E6R1P6)
          Model: ANE-LX1
          Vendor/Country: hw/ru
          Battery state: 0
          OEM lock state info:
          FB LockState: UNLOCKED
          USER LockState: LOCKED
          OEM get bootinfo:
          unlocked
          
          Software written
          08-May-21 19:22:33 Writing device finished OK
          08-May-21 19:22:33 Starting to write device in FASTBOOT mode...
          File to update: C:\Users\kot.kma\Desktop\Phones\P20 Lite\brick\ANE-Full-Repair-NV-included-Board-A039-8.0.0.dgtks
          
          Looking for a device in fastboot mode
          Device found: 9WV4C18603007989
          
          
          Getting IMEI...
          Getting build number...
          Getting model ...
          Getting battery state...
          Getting backdoor info...
          Getting lock state info...
          Getting lock boot info...
          
          SN:9WV4C18603007989
          IMEI:863675040855475
          IMEI1:863675040881489
          MEID:00000000000000
          Build number: :ANE-LX1 9.1.0.315(C10E6R1P6)
          Model: ANE-LX1
          Vendor/Country: hw/ru
          Battery state: 0
          OEM lock state info:
          FB LockState: UNLOCKED
          USER LockState: LOCKED
          OEM get bootinfo:
          unlocked
          
          
          Process identifier:31334136
          
          
          
          Waiting for OEM erase_storage_all command ...FAIL
          Waiting for answer...
          Fatal error: Cannot access to device
          
          Waiting for OEM erase_emmc_all command ...OK
          Fatal error: Cannot access to device
          
          Waiting for device REMOVAL/INSERTION...
          REMOVAL/INSERTION wait result: iUsbProc.DisConnect:False; iUsbProc.Connect:False; Elapsed time:60332; Waitfor:60000
          
          No devices detected in testpoint mode
          
          Cannot access to device
          08-May-21 19:24:32 Writing device finished - INCOMPLETE

          Comment


          • #6
            So... Is there anything that I could try?
            Last edited by kot.kma; 2021-05-08, 04:56 PM.

            Comment


            • #7
              Battery must be connected/charged during this.
              >>Free Octohide VPN for Android, find it on Google Play Here<<

              Comment


              • #8
                Yes, it was.

                Comment


                • #9
                  Then either it is faulty or completely discharged as it shows 0 capacity.
                  >>Free Octohide VPN for Android, find it on Google Play Here<<

                  Comment


                  • #10
                    I'm sure that it's charged, cause phone easily can stay almost whole day at bootloop logo w/o charging.

                    Comment


                    • #11
                      What may cause that fault?

                      Comment


                      • #12
                        Hardware failure, main board most likely.
                        >>Free Octohide VPN for Android, find it on Google Play Here<<

                        Comment


                        • #13
                          hi, back here. this time with the P20 Lite - pretty dead. does not go to recovery mode (blue and red squares on the green background), in fastboot from these data:
                          fastboot info
                          firmware version : failed (device sent unknown status)
                          device name : failed (remote FAIL)
                          oeminfo: getvar.vendor.country FAILED (remote: cannot ...)
                          serial N: OK
                          bootloader state : locked
                          battery voltage : 3305mv

                          do you think I have the possibility to resurrect him with dc-phoenix?
                          thank you

                          Comment


                          • #14
                            Sorry, can not confirm that repair will work. This depends from phone damage level and other conditions.
                            If it has android more than 8, then you should try these instructions: https://www.dc-unlocker.com/huawei-b...d-repair-by-tp
                            If lower, then https://www.dc-unlocker.com/dc-phoen...epair-tutorial

                            Comment


                            • #15
                              Thanks for the reply. the point is, I don't know anything about the installed firmware. I'll give it a try next week. regards

                              Comment

                              Working...
                              X