Announcement

Collapse
No announcement yet.

Bricked huawei p20 lite

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

  • Bricked huawei p20 lite

    Hello, i have the ANE-LX1 version of the p20 lite and everytime i try to open it i get "your device has failed verification and may not work properly" message. I can't access recovery but i can enter fastboot.
    The phone has bootloader locked and frp unlocked and i have android 9.0.
    The problem is that i wasn't able to flash anything using DC-Phoneix.
    For example this is what i get when trying to flash firmware:

    DC Phoenix 0.0.0.132
    user:mihaifilat


    Standard update
    Not Reboot NOT cheked
    Update Verlist to server on file load NOT checked
    Try Rescue Recovery checked
    Bypass version check NOT checked
    Old slow algo checked

    Looking for a device in upgrade mode
    No devices detected in upgrade mode
    Device found: 89UDU18531006165

    Extracting recovery partition

    Extracting partition: ERECOVERY_KERNEL
    ERECOVERY_KERNEL partition extracted

    Extracting partition: ERECOVERY_RAMDISK
    ERECOVERY_RAMDISK partition extracted

    Extracting partition: ERECOVERY_VENDOR
    ERECOVERY_VENDOR partition extracted

    1/9/2021 2:09:50 PM Starting to try Rescue Recovery...


    Looking for a device in fastboot mode
    Device found: 89UDU18531006165


    Getting IMEI...
    Getting build number...
    Getting model ...
    Getting model by product ...
    Getting model by roduct ...
    Getting battery state...
    Getting backdoor info...
    Getting lock state info...
    Getting lock boot info...

    Model: hi6250
    Battery state: 0
    OEM lock state info:
    FB LockState: UNLOCKED
    USER LockState: LOCKED
    OEM get bootinfo:
    unlocked


    Process identifier:29503245


    Erasing ver .. .
    Getting lock state info...

    Erasing ver .. .
    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
    Uptade recovery parttion OK
    Enter recovery mode FAIL

    Cannot enter in Recovery mode

    I have also tried flashing board software with testpoint method.
    Looking for a device in force upgrade mode
    Device detected:
    COM4: HUAWEI USB COM 1.0 (COM4)
    1/9/2021 2:19:38 PM Starting to write device in FASTBOOT mode...
    File to update: C:\Users\Mihai\Desktop\ANE-Full-Repair-NV-included-Board-A039-8.0.0.dgtks
    Device detected:
    COM4: HUAWEI USB COM 1.0 (COM4)

    Process identifier:29503379


    Writing bootloader...
    Step 1...
    Step 2...

    Waiting for device REMOVAL/INSERTION...

    USB Device REMOVAL
    Type: @oem88.inf,%qcomdevice00%;HUAWEI USB COM 1.0
    VidPid: VID_12D1&PID_3609
    Instance id: 5&1e7d8db7&0&13


    USB Device INSERTION
    Type: @oem71.inf,%compositeadbinterface%;Android Composite ADB Interface
    VidPid: VID_18D1&PID_D00D
    Instance id: 89UDU18531006165


    Waiting for fastboot device...
    Device found: 89UDU18531006165


    Looking for a device in fastboot mode
    Device found: 89UDU18531006165


    Getting IMEI...
    Getting build number...
    Getting model ...
    Getting battery state...
    Getting backdoor info...
    Getting lock state info...
    Getting lock boot info...

    SN:89UDU18531006165
    IMEI:867906037640067
    IMEI1:000000000000000
    MEID:00000000000000
    Build number: :ANE-LX1 9.1.0.370(C432E7R1P7)
    Model: ANE-LX1
    Vendor/Country: hw/eu
    Battery state: 0
    OEM lock state info:
    FB LockState: UNLOCKED
    USER LockState: LOCKED
    OEM get bootinfo:
    unlocked



    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

    Cannot access to device
    1/9/2021 2:20:47 PM Writing device finished - INCOMPLETE


  • #2
    Did you flash custom recovery to your device previously?

    Comment


    • #3
      No, i didn't. honestly, i am quite confused as why the phone got bricked, i didn't try to alter the software in any way even the bootloader was locked. The one thing that i remember doing the night before was disabling internet and data access of some huawei apps (HMS core and something else), but i doubt that could damage the phone this badly

      Anyway, at this point in time i think any discussion would be useless since my temporary license has already finished.
      Most probably i would buy another phone or replace the motherboard as these can be found for cheap.

      Comment


      • #4
        We can always extend licenses in good effort, we want you to have your phone repaired For now lets try to find out if it can enter upgrade over usb mode. Turn off phone, hold both vol buttons and connect it to usb.

        Comment


        • #5
          Originally posted by Valdemaras View Post
          We can always extend licenses in good effort, we want you to have your phone repaired For now lets try to find out if it can enter upgrade over usb mode. Turn off phone, hold both vol buttons and connect it to usb.
          i have tried it now and i got a green screen with a red and blue square in the middle.
          This is a recreated image, o the phone the image briefly flashed and then closed.

          Oh, and another thing, i can't boot the phone without it plugged in, it says it has no battery which is wired since if when i connected my phone to dc phoneix (in fastboot mode) it said 3000 mv or something like that which is normal.
          Attached Files
          Last edited by mihaifilat; 4 days ago.

          Comment


          • #6
            Originally posted by mihaifilat View Post
            i have tried it now and i got a green screen with a red and blue square in the middle.
            This is a recreated image, o the phone the image briefly flashed and then closed.

            Oh, and another thing, i can't boot the phone without it plugged in, it says it has no battery which is wired since if when i connected my phone to dc phoneix (in fastboot mode) it said 3000 mv or something like that which is normal.
            So phone has or it doesn't battery attached to it when you do it?

            Comment


            • #7
              Originally posted by Valdemaras View Post

              So phone has or it doesn't battery attached to it when you do it?
              The phone has the battery connected and it is charged, but for some reason the phone doesn't detect it as being charged, so I can only open the phone when it is plugged in. After the phone has opened (the error message is on the screen) It stays on even without being plugged in ( and not only for few minutes, I have tested and it lasts about 10 hours with the screen on)

              Comment


              • #8
                Okay, this seems to be a dead end using this method, i've extended your license, please try to use just loader, make sure bootloader is unlocked after it enters fastboot when using loader. Then you should attempt flash full stock rom in it.

                Comment


                • #9
                  Originally posted by Valdemaras View Post
                  Okay, this seems to be a dead end using this method, i've extended your license, please try to use just loader, make sure bootloader is unlocked after it enters fastboot when using loader. Then you should attempt flash full stock rom in it.
                  thanks for extending the license, i successfully flashed the kirin659_T0_V1 and V2 but the bootloader still appears to be locked.

                  Oh, and about the battery, i misread and 3350mv is not normal since the battery specs say it should be 3820mv

                  Comment


                  • #10
                    Ok will need to forward this to dev as this is most unusual:
                    Please do this:
                    1. Restart DC-Phoenix.
                    2. Press CTRL+L
                    3. Select firmware ANE-Full-Repair-NV-included-Board-A039-8.0.0.dgtks and flash from testpoint mode
                    4. After unsuccessful flashing close DC-phoenix
                    5. Open directory where DC-phoenix software is placed in
                    6. Look for .dgtkl file there, send it to me, please

                    If dev confirms there is no way and board dead, then will check for refund.

                    Comment


                    • #11
                      Originally posted by Valdemaras View Post
                      Ok will need to forward this to dev as this is most unusual:
                      Please do this:
                      1. Restart DC-Phoenix.
                      2. Press CTRL+L
                      3. Select firmware ANE-Full-Repair-NV-included-Board-A039-8.0.0.dgtks and flash from testpoint mode
                      4. After unsuccessful flashing close DC-phoenix
                      5. Open directory where DC-phoenix software is placed in
                      6. Look for .dgtkl file there, send it to me, please

                      If dev confirms there is no way and board dead, then will check for refund.
                      ok, here is the link to the file https://drive.google.com/file/d/1lyo...ew?usp=sharing

                      Comment


                      • #12
                        Just noticed that you are doing all this on old version of DC-phoenix, please try again on new one, meanwhile we will investigate the log file though it may be not what we neededsince it's from old version.

                        Comment


                        • #13
                          Originally posted by Valdemaras View Post
                          Just noticed that you are doing all this on old version of DC-phoenix, please try again on new one, meanwhile we will investigate the log file though it may be not what we neededsince it's from old version.
                          oh, sorry i have now updated but flashing still fails. this is the log file form the latest(153) version https://drive.google.com/file/d/1nRa...ew?usp=sharing

                          Comment


                          • #14
                            Okay, problem at the moment seems that your phone has no rescue recovery in it and board firmware doesn't contain such partition. So you need to flash normal UPDATE.APP firmware from fastboot with standard method selected on dc-phoenix and slow algo option checked. Let us know with results, may as well copy/paste here info from dc-phoenix for better view.

                            Comment


                            • #15
                              Where could i find the UPDATE.APP file. When i search from dc-phoneix i found Anne-L21_8.0.0.108(C432)_Firmware_Android_8.0.0_EMUI_8. 0.0.APP. But my phone is ANE-LX1. Will this work?

                              Comment

                              Working...
                              X