Unconfigured Ad Widget

Collapse

Announcement

Collapse
No announcement yet.

P20 Lite - cannot enter to upgrade mode after Update OEMINFO

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

  • P20 Lite - cannot enter to upgrade mode after Update OEMINFO

    Please help.

    Here is log 1
    Code:
    BOOTLOADER selected to update:Kirin659_T0_A8.0_V1
    Unlock FRP checked
    Change model to:ANE-L21
    Change vendor to:hw
    Change country to:eu
    DC Phoenix 0.0.0.129
    user:galoml
    
    Device detected:
    COM45: HUAWEI USB COM 1.0 (COM45)
    BOOTLOADER File to update: Kirin659_T0_A8.0_V1
    OEM File to update: ANE-L21
    20. 5. 2020 21:11:12 Starting to write device...
    
    Process identifier:24591971
    
    
    Writing bootloader...
    Step 1...
    Step 2...
    
    Waiting for device REMOVAL/INSERTION...
    
    Waiting for fastboot device...
    
    USB Device REMOVAL
    Type: @oem121.inf,%qcomdevice00%;HUAWEI USB COM 1.0
    VidPid: VID_12D1&PID_3609
    Instance id: 5&33f10317&0&1
    
    
    USB Device INSERTION
    Type: @oem53.inf,%hwfastboot%;Android Sooner Single ADB Interface
    VidPid: VID_18D1&PID_D00D
    Instance id: 89U4C18811014818
    
    Device found: 89U4C18811014818
    
    
    Looking for a device in fastboot mode
    Device found: 89U4C18811014818
    
    
    Getting IMEI...
    Getting build number...
    Getting model ...
    Getting battery state...
    Getting backdoor info...
    Getting lock state info...
    Getting lock boot info...
    
    SN:89U4C18811014818
    IMEI:861754046852406
    
    IMEI1:861754046882411
    
    MEID:00000000000000
    Build number: :ANE-LX1 8.0.0.168(C432)
    Model: ANE-LX1
    Vendor/Country: hw/eu
    Battery state: 2853mv
    OEM lock state info:
    FB LockState: UNLOCKED
    USER LockState: LOCKED
    OEM get bootinfo:
    unlocked
    
    
    Unlocking FRP...
    Writing FRP partition
    FRP partition update :FAIL partition error
    Writing FRP partition
    FRP partition update ...OK
    Writing OEMINFO partition
    OEMINFO partition update ...OK
    Software written
    20. 5. 2020 21:11:46 Writing device finished OK

    Log 2
    Code:
    USB Device REMOVAL
    Type: @oem53.inf,%hwfastboot%;Android Sooner Single ADB Interface
    VidPid: VID_18D1&PID_D00D
    Instance id: 89U4C18811014818
    
    
    USB Device INSERTION
    Type: @oem53.inf,%hwfastboot%;Android Sooner Single ADB Interface
    VidPid: VID_18D1&PID_D00D
    Instance id: 89U4C18811014818
    
    DC Phoenix 0.0.0.129
    user:galoml
    
    
    File size: 4 339 262 744 bytes
    Current version(CURVER): ANE-BD 1.0.0.999
    Package Type: OFFLINE_UPDATE
    
    Revision: 0
    Checking partition: VERLIST
    DC Phoenix 0.0.0.129
    user:galoml
    
    
    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: 89U4C18811014818
    
    Detecting recovery partition
    File size: 4 339 262 744 bytes
    Current version(CURVER): ANE-BD 1.0.0.999
    ERECOVERY_KERNEL partition found
    ERECOVERY_RAMDISK partition found
    ERECOVERY_VENDOR partition found
    
    20. 5. 2020 21:16:10 Starting to try Rescue Recovery...
    
    
    Looking for a device in fastboot mode
    Device found: 89U4C18811014818
    
    
    Getting IMEI...
    Getting build number...
    Getting model ...
    Getting battery state...
    Getting backdoor info...
    Getting lock state info...
    Getting lock boot info...
    
    SN:89U4C18811014818
    IMEI:861754046852406
    
    IMEI1:861754046882411
    
    MEID:00000000000000
    Build number: :ANE-LX1 8.0.0.168(C432)
    Model: ANE-LX1
    Vendor/Country: hw/eu
    Battery state: 2856mv
    OEM lock state info:
    FB LockState: UNLOCKED
    USER LockState: LOCKED
    OEM get bootinfo:
    unlocked
    
    
    Process identifier:24592097
    
    
    Erasing ver .. .
    File size: 4 339 262 744 bytes
    Current version(CURVER): ANE-BD 1.0.0.999
    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
    
    USB Device REMOVAL
    Type: @oem53.inf,%hwfastboot%;Android Sooner Single ADB Interface
    VidPid: VID_18D1&PID_D00D
    Instance id: 89U4C18811014818
    
    Looking for device in upgrade mode...
    Process was cancelled by user
    Enter recovery mode FAIL
    
    Cannot enter in Recovery mode

  • #2
    Then must put it in that mode manually.
    >>Free Octohide VPN for Android, find it on Google Play Here<<

    Comment


    • #3
      I tried this, but it is not possible to run this mode manually (volume + and -, then USB)

      "Battery state: 2853mv" - is that enought?

      Comment


      • #4
        Originally posted by galoml View Post
        I tried this, but it is not possible to run this mode manually (volume + and -, then USB)

        "Battery state: 2853mv" - is that enought?
        No
        charge battery .
        needed 3.7 or more

        Comment


        • #5
          Thanks for help, battery charched and it works OK.
          Now I should use full stock firmware ANE-LX1, but I can find it in support area.

          Comment


          • #6
            Originally posted by galoml View Post
            Thanks for help, battery charched and it works OK.
            Now I should use full stock firmware ANE-LX1, but I can find it in support area.
            Now the phone is at what stage? Did you manage to flash boot?
            support has such firmware, ANE-Downgrade-Board-A039-8.0.0.dgtks
            need to flash through testpoint

            Comment


            • #7
              Yes, I used this firmware and flashed it to phone with testpoint,
              phone is in working condition now,
              but it has weird info about type, firmware version, region etc.,
              so I need flash it with correct firmware.

              Sorry, I am out of my PC now,
              I can not post log.

              Comment


              • #8
                Originally posted by galoml View Post
                Yes, I used this firmware and flashed it to phone with testpoint,
                phone is in working condition now,
                but it has weird info about type, firmware version, region etc.,
                so I need flash it with correct firmware.

                Sorry, I am out of my PC now,
                I can not post log.
                Fix Imei vendor and model via hcu client
                direct unlock
                download https://androidhost.ru/a24
                and flash via rescue mode

                Comment


                • #9
                  Thak you, but it not works, phone has still weird info, it shows only "ANE" model, bad customization "0JKG" ...

                  First firmware version in phone was ANE-LX1 9.1.0.306(C432E6R1P7), I needed to turn off FRP.

                  So I did downgrade with Anne-L21_8.0.0.108(C432)_Firmware_Android_8.0.0_EMUI_8. 0.0 with VERSION BYPASS checked, and with this starts problems.
                  I tried flash a few firmwares.
                  After that I use BOOTLOADER file and update OEMINFO with testpoint, drain battery, get charged battery,
                  again use BOOTLOADER file and update OEMINFO with testpoint and flashed ANE downgrade board firmware from support.

                  Then I fixed MODEL, VENDOR and COUNTRY with latest HCU, phone did factory reset and gets to bootloop.
                  I flashed yours firmware from Android host.

                  But phone has still weird info in About menu.

                  This is info from HCU:
                  Code:
                  Read phone info
                  
                  2020-05-30 12:32:11.015 Autodetect COM port and phone type start!
                  2020-05-30 12:32:11.779 Found COM port: COM46
                  2020-05-30 12:32:11.779 Found phone type: Huawei Android phone (HiSilicon CPU)
                  2020-05-30 12:32:11.795 Open COM port COM46 (Android Adapter PCUI (COM46))...
                  2020-05-30 12:32:11.936 Start read phone info!
                  2020-05-30 12:32:17.131 Connecting to server...
                  2020-05-30 12:32:17.459 Connected!
                  2020-05-30 12:32:18.769 CP State: ready
                  2020-05-30 12:32:18.769 Read phone basic info...
                  2020-05-30 12:32:19.409 Read phone secure info...
                  2020-05-30 12:32:24.089 Read phone info done!
                  
                  Firmware ver.: System 8.0.0.046(0JKG)
                  Dataver: ANE-LX1 8.0.0.153(C432)_DATA_ANE-L01_hw_eu
                  FASTBOOT:Chipset-dallas8.0.0.001(03TI)_FASTBOOT
                  BOOT:System 8.0.0.046(0JKG)_BOOT
                  RECOVERY:(unknow)
                  SYSTEM:System 8.0.0.046(0JKG)
                  MAINVER:System 8.0.0.046(0JKG)
                  DATAVER:ANE-LX1 8.0.0.153(C432)_DATA_ANE-L01_hw_eu
                  APTIME:Thu Sep 27 13:20:05 CST 2018
                  
                  Current security patch not supported!
                  Please help, what shoul I proceed next?





                  Last edited by galoml; 2020-05-30, 12:22 PM.

                  Comment


                  • #10
                    Originally posted by galoml View Post
                    Thak you, but it not works, phone has still weird info, it shows only "ANE" model, bad customization "0JKG" ...

                    First firmware version in phone was ANE-LX1 9.1.0.306(C432E6R1P7), I needed to turn off FRP.

                    So I did downgrade with Anne-L21_8.0.0.108(C432)_Firmware_Android_8.0.0_EMUI_8. 0.0 with VERSION BYPASS checked, and with this starts problems.
                    I tried flash a few firmwares.
                    After that I use BOOTLOADER file and update OEMINFO with testpoint, drain battery, get charged battery,
                    again use BOOTLOADER file and update OEMINFO with testpoint and flashed ANE downgrade board firmware from support.

                    Then I fixed MODEL, VENDOR and COUNTRY with latest HCU, phone did factory reset and gets to bootloop.
                    I flashed yours firmware from Android host.

                    But phone has still weird info in About menu.

                    This is info from HCU:
                    Code:
                    Read phone info
                    
                    2020-05-30 12:32:11.015 Autodetect COM port and phone type start!
                    2020-05-30 12:32:11.779 Found COM port: COM46
                    2020-05-30 12:32:11.779 Found phone type: Huawei Android phone (HiSilicon CPU)
                    2020-05-30 12:32:11.795 Open COM port COM46 (Android Adapter PCUI (COM46))...
                    2020-05-30 12:32:11.936 Start read phone info!
                    2020-05-30 12:32:17.131 Connecting to server...
                    2020-05-30 12:32:17.459 Connected!
                    2020-05-30 12:32:18.769 CP State: ready
                    2020-05-30 12:32:18.769 Read phone basic info...
                    2020-05-30 12:32:19.409 Read phone secure info...
                    2020-05-30 12:32:24.089 Read phone info done!
                    
                    Firmware ver.: System 8.0.0.046(0JKG)
                    Dataver: ANE-LX1 8.0.0.153(C432)_DATA_ANE-L01_hw_eu
                    FASTBOOT:Chipset-dallas8.0.0.001(03TI)_FASTBOOT
                    BOOT:System 8.0.0.046(0JKG)_BOOT
                    RECOVERY:(unknow)
                    SYSTEM:System 8.0.0.046(0JKG)
                    MAINVER:System 8.0.0.046(0JKG)
                    DATAVER:ANE-LX1 8.0.0.153(C432)_DATA_ANE-L01_hw_eu
                    APTIME:Thu Sep 27 13:20:05 CST 2018
                    
                    Current security patch not supported!
                    Please help, what shoul I proceed next?




                    Yes now vendror change )
                    its C432 / other region
                    now needed

                    Comment


                    • #11
                      Solved,thank You very much.

                      Comment

                      Working...
                      X