Help --- trying to Unlock Bootloader and install Lineage OS

2»

Comments

  • jjremaxjjremax detroit, miPosts: 43 ✭✭✭✭

    @benkores, I did use another browser and was able to download your exe. file, and thank you. When I tried to follow your options 1, kind of confused about the message "Please unplug your device before continuing". I thought the phone has to be connected with my computer through USB cord. Otherwise, how to connect them. So, I kept the USB connection, but it came up Failed to Install Qualcomm Driver. (I also did disconnect the phone and the computer, but it came up the same message, Failed) The log is too big to show here. So, I copied the sentence that shows ! below for your review. Not sure where I did wrong, or there are something setting I did do right. I do checked the USB debugging and OEM unlocking. The last part shows Signature thing. Please help. Thanks.

    ===================================================================

  • jjremaxjjremax detroit, miPosts: 43 ✭✭✭✭

    ! dvi: Device restart was skipped (DONOTCALLCONFIGMG).

    ! inf: Found legacy AddReg operation using non-relative key (HKLM\Software\Wow6432Node\AMD\Install\South Bridge\SMBus).
    ! inf: Driver package 'smbusamd.inf' is NOT configurable.

    ! dvi: Add Service: NULL Controlling service.

    ! inf: Empty Section! [KSProxy.Files]
    ! inf: Empty Section! [KSDriver.Files]
    ! inf: Empty Section! [KSProxy.DelFiles]

    ! sto: Skipping missing driver package file 'HP1006SU.ENT'.
    ! sto: Skipping missing driver package file 'HP1006SD.SDD'.
    ! sto: Skipping missing driver package file 'HP1006SD.chm'.
    ! sto: Skipping missing driver package file 'P1006IPS.dll'.
    ! sto: Skipping missing driver package file 'HP1006SMs.DLL'.
    ! sto: Skipping missing driver package file 'P1006OS.HTM'.
    ! sto: Skipping missing driver package file 'HP1006SU.ENT'.
    ! sto: Skipping missing driver package file 'HP1006SD.SDD'.
    ! sto: Skipping missing driver package file 'HP1006SD.chm'.
    ! sto: Skipping missing driver package file 'P1006IPS.dll'.
    ! sto: Skipping missing driver package file 'HP1006SMs.DLL'.
    ! sto: Skipping missing driver package file 'P1006OS.HTM'.

    ! inf: Found legacy CopyFiles operation with non-system target path (C:\Program Files\HP\HP LaserJet P1000_P1500 Series) for 'P1006OS.HTM'.
    ! inf: Driver package 'hpljp1005.inf' is NOT configurable.

    ! inf: Found legacy AddReg operation using non-relative key (HKLM\SOFTWARE\WinChipHead\IC\CH341SER).
    ! inf: Driver package 'ch341ser.inf' is NOT configurable.

    ! idb: Unable to find driver INF match for 'tape.inf' under 'SCSI\SequentialWangDAT_Model_1300______'.
    ! idb: Unable to find driver INF match for 'tape.inf' under 'SCSI\SequentialTECMAR__TRAVAN_NS20_____'.
    ! idb: Unable to find driver INF match for 'tape.inf' under 'SCSI\SequentialEXABYTE_EXB-85058HE-0000'.
    ! idb: Driver INF match for 'tape.inf' already exists under 'SCSI\SequentialWangDAT_Model_1300______'.
    ! idb: Driver INF match for 'tape.inf' already exists under 'SCSI\SequentialTECMAR__TRAVAN_NS20_____'.
    ! idb: Driver INF match for 'tape.inf' already exists under 'SCSI\SequentialEXABYTE_EXB-85058HE-0000'.

    !!! sto: Failed to find driver update 'C:\WINDOWS\WinSxS\amd64_tape.inf_31bf3856ad364e35_6.3.9600.16384_none_d73937a451752493\tape.inf' in Driver Store. Error = 0x00000490

    !!! sto: Failed to find driver update 'C:\WINDOWS\WinSxS\amd64_usb.inf_31bf3856ad364e35_6.3.9600.17238_none_bbf0bf16e23d5004\usb.inf' in Driver Store. Error = 0x00000490

    !!! sto: Failed to find driver update 'C:\WINDOWS\WinSxS\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.18191_none_ae72bd57d78fb0aa\usbport.inf' in Driver Store. Error = 0x00000490

    ! sig: Verifying file against specific (valid) catalog failed! (0xe0000244)
    ! sig: Error 0xe0000244: The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version.

    ! sig: Verifying file against specific (valid) catalog failed! (0xe0000244)
    ! sig: Error 0xe0000244: The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version.

    !!! sig: An unexpected error occurred while validating driver package. Catalog = qcser.cat, Error = 0xE0000244
    !!! sig: Driver package is considered unsigned, and Code Integrity is enforced.
    !!! sig: Driver package failed signature validation. Error = 0xE0000244

    !!! sig: Driver package failed signature verification. Error = 0xE0000244
    !!! sto: Failed to import driver package into Driver Store. Error = 0xE0000244

    !!! inf: Failed to import driver package into driver store
    !!! inf: Error 0xe0000244: The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version.
    inf: {SetupCopyOEMInf exit (0xe0000244)} 22:29:31.027
    <<< Section end 2017/11/16 22:29:31.041
    <<< [Exit status: FAILURE(0xe0000244)]

    ! sig: Verifying file against specific (valid) catalog failed! (0xe0000244)
    ! sig: Error 0xe0000244: The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version.

    ! sig: Verifying file against specific (valid) catalog failed! (0xe0000244)
    ! sig: Error 0xe0000244: The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version.

    !!! sig: An unexpected error occurred while validating driver package. Catalog = qcser.cat, Error = 0xE0000244
    !!! sig: Driver package is considered unsigned, and Code Integrity is enforced.
    !!! sig: Driver package failed signature validation. Error = 0xE0000244

    !!! sig: Driver package failed signature verification. Error = 0xE0000244
    !!! sto: Failed to import driver package into Driver Store. Error = 0xE0000244

    !!! inf: Failed to import driver package into driver store
    !!! inf: Error 0xe0000244: The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version.
    inf: {SetupCopyOEMInf exit (0xe0000244)} 22:30:53.952
    <<< Section end 2017/11/16 22:30:53.962
    <<< [Exit status: FAILURE(0xe0000244)]

    ! sig: Verifying file against specific (valid) catalog failed! (0xe0000244)
    ! sig: Error 0xe0000244: The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version.

    ! sig: Verifying file against specific (valid) catalog failed! (0xe0000244)
    ! sig: Error 0xe0000244: The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version.

    !!! sig: An unexpected error occurred while validating driver package. Catalog = qcser.cat, Error = 0xE0000244
    !!! sig: Driver package is considered unsigned, and Code Integrity is enforced.
    !!! sig: Driver package failed signature validation. Error = 0xE0000244

    !!! sig: Driver package failed signature verification. Error = 0xE0000244
    !!! sto: Failed to import driver package into Driver Store. Error = 0xE0000244

    !!! inf: Failed to import driver package into driver store
    !!! inf: Error 0xe0000244: The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version.
    inf: {SetupCopyOEMInf exit (0xe0000244)} 22:32:05.381
    <<< Section end 2017/11/16 22:32:05.390
    <<< [Exit status: FAILURE(0xe0000244)]

    ! sig: Verifying file against specific (valid) catalog failed! (0xe0000244)
    ! sig: Error 0xe0000244: The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version.

    ! sig: Verifying file against specific (valid) catalog failed! (0xe0000244)
    ! sig: Error 0xe0000244: The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version.

    !!! sig: An unexpected error occurred while validating driver package. Catalog = qcser.cat, Error = 0xE0000244
    !!! sig: Driver package is considered unsigned, and Code Integrity is enforced.
    !!! sig: Driver package failed signature validation. Error = 0xE0000244

    !!! sig: Driver package failed signature verification. Error = 0xE0000244
    !!! sto: Failed to import driver package into Driver Store. Error = 0xE0000244

    !!! inf: Failed to import driver package into driver store
    !!! inf: Error 0xe0000244: The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version.
    inf: {SetupCopyOEMInf exit (0xe0000244)} 22:47:53.836
    <<< Section end 2017/11/16 22:47:53.846
    <<< [Exit status: FAILURE(0xe0000244)]

    ! sig: Verifying file against specific (valid) catalog failed! (0xe0000244)
    ! sig: Error 0xe0000244: The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version.

    ! sig: Verifying file against specific (valid) catalog failed! (0xe0000244)
    ! sig: Error 0xe0000244: The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version.

    !!! sig: An unexpected error occurred while validating driver package. Catalog = qcser.cat, Error = 0xE0000244
    !!! sig: Driver package is considered unsigned, and Code Integrity is enforced.
    !!! sig: Driver package failed signature validation. Error = 0xE0000244

    !!! sig: Driver package failed signature verification. Error = 0xE0000244
    !!! sto: Failed to import driver package into Driver Store. Error = 0xE0000244

    !!! inf: Failed to import driver package into driver store
    !!! inf: Error 0xe0000244: The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version.
    inf: {SetupCopyOEMInf exit (0xe0000244)} 22:52:36.114
    <<< Section end 2017/11/16 22:52:36.128
    <<< [Exit status: FAILURE(0xe0000244)]

    ! sig: Verifying file against specific (valid) catalog failed! (0xe0000244)
    ! sig: Error 0xe0000244: The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version.

    !!! sig: An unexpected error occurred while validating driver package. Catalog = qcser.cat, Error = 0xE0000244
    !!! sig: Driver package is considered unsigned, and Code Integrity is enforced.
    !!! sig: Driver package failed signature validation. Error = 0xE0000244

    !!! sig: Driver package failed signature verification. Error = 0xE0000244
    !!! sto: Failed to import driver package into Driver Store. Error = 0xE0000244

    !!! inf: Failed to import driver package into driver store
    !!! inf: Error 0xe0000244: The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version.
    inf: {SetupCopyOEMInf exit (0xe0000244)} 23:01:11.997
    <<< Section end 2017/11/16 23:01:12.011
    <<< [Exit status: FAILURE(0xe0000244)]

  • jjremaxjjremax detroit, miPosts: 43 ✭✭✭✭

    ! sig: Verifying file against specific (valid) catalog failed! (0xe0000244)
    ! sig: Error 0xe0000244: The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version.

    ! sig: Verifying file against specific (valid) catalog failed! (0xe0000244)
    ! sig: Error 0xe0000244: The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version.
    sig: {_VERIFY_FILE_SIGNATURE exit(0xe0000244)} 10:36:04.281
    !!! sig: An unexpected error occurred while validating driver package. Catalog = qcser.cat, Error = 0xE0000244
    !!! sig: Driver package is considered unsigned, and Code Integrity is enforced.
    !!! sig: Driver package failed signature validation. Error = 0xE0000244

    !!! sig: Driver package failed signature verification. Error = 0xE0000244
    !!! sto: Failed to import driver package into Driver Store. Error = 0xE0000244

    !!! inf: Failed to import driver package into driver store
    !!! inf: Error 0xe0000244: The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version.
    inf: {SetupCopyOEMInf exit (0xe0000244)} 10:36:04.618
    <<< Section end 2017/11/17 10:36:04.627
    <<< [Exit status: FAILURE(0xe0000244)]

    ! sig: Verifying file against specific (valid) catalog failed! (0xe0000244)
    ! sig: Error 0xe0000244: The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version.

    ! sig: Verifying file against specific (valid) catalog failed! (0xe0000244)
    ! sig: Error 0xe0000244: The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version.

    !!! sig: An unexpected error occurred while validating driver package. Catalog = qcser.cat, Error = 0xE0000244
    !!! sig: Driver package is considered unsigned, and Code Integrity is enforced.
    !!! sig: Driver package failed signature validation. Error = 0xE0000244

    !!! sig: Driver package failed signature verification. Error = 0xE0000244
    !!! sto: Failed to import driver package into Driver Store. Error = 0xE0000244

    !!! inf: Failed to import driver package into driver store
    !!! inf: Error 0xe0000244: The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version.
    inf: {SetupCopyOEMInf exit (0xe0000244)} 17:17:55.150
    <<< Section end 2017/11/17 17:17:55.159
    <<< [Exit status: FAILURE(0xe0000244)]

    ! dvi: Device restart was skipped (DONOTCALLCONFIGMG).

    ! dvi: Device restart was skipped (DONOTCALLCONFIGMG).

    ! inf: Found legacy AddReg operation defining co-installers (CoInstallers32).
    ! inf: Driver package 'android_winusb.inf' is NOT configurable.

    ! sig: Verifying file against specific (valid) catalog failed! (0x800b0109)
    ! sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.

    ! idb: Driver INF match for 'oem4.inf' already exists under 'USB\VID_22B8&PID_2D7B&MI_03'.
    ! idb: Driver INF match for 'oem4.inf' already exists under 'USB\VID_22B8&PID_41DB&MI_01'.

    ! inf: Driver package is already in driver store

    ! sig: VerifyTrustFailed for C:\WINDOWS\system32\SETAAC.tmp.
    ! sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.

    ! flq: MoveFile: 'C:\WINDOWS\System32\SETB851.tmp' to 'C:\WINDOWS\System32\WinUSBCoInstaller2.dll' FAILED!
    ! flq: Error 5: Access is denied.

    ! flq: MoveFile: 'C:\WINDOWS\System32\SETB891.tmp' to 'C:\WINDOWS\System32\WdfCoInstaller01009.dll' FAILED!
    ! flq: Error 5: Access is denied.

    !!! dvi: Device not started: Device has problem: 0x0a: CM_PROB_FAILED_START.

    ! ndv: Queueing up error report since device has a PnP problem...

    ! sig: Verifying file against specific (valid) catalog failed! (0x800b0109)
    ! sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.

    ! sig: Driver package signer is unknown, but user trusts signer.

    ! sig: Error 0xe0000244: The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version.

    ! sig: Verifying file against specific (valid) catalog failed! (0xe0000244)
    ! sig: Error 0xe0000244: The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version.
    sig: {_VERIFY_FILE_SIGNATURE exit(0xe0000244)} 09:33:01.242
    !!! sig: An unexpected error occurred while validating driver package. Catalog = qcser.cat, Error = 0xE0000244
    !!! sig: Driver package is considered unsigned, and Code Integrity is enforced.
    !!! sig: Driver package failed signature validation. Error = 0xE0000244
    sto: {DRIVERSTORE IMPORT VALIDATE: exit(0xe0000244)} 09:33:01.278
    !!! sig: Driver package failed signature verification. Error = 0xE0000244
    !!! sto: Failed to import driver package into Driver Store. Error = 0xE0000244

    !!! inf: Failed to import driver package into driver store
    !!! inf: Error 0xe0000244: The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version.
    <<< Section end 2017/12/07 09:33:01.486
    <<< [Exit status: FAILURE(0xe0000244)]

    ! sig: VerifyTrustFailed for C:\WINDOWS\system32\SETF80B.tmp.
    ! sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.

    ! inf: Driver package is already in driver store

    ! sig: Verifying file against specific (valid) catalog failed! (0xe0000244)
    ! sig: Error 0xe0000244: The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version.

    ! sig: Verifying file against specific (valid) catalog failed! (0xe0000244)
    ! sig: Error 0xe0000244: The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version.
    sig: {_VERIFY_FILE_SIGNATURE exit(0xe0000244)} 09:41:57.477
    !!! sig: An unexpected error occurred while validating driver package. Catalog = qcser.cat, Error = 0xE0000244
    !!! sig: Driver package is considered unsigned, and Code Integrity is enforced.
    !!! sig: Driver package failed signature validation. Error = 0xE0000244

    !!! sig: Driver package failed signature verification. Error = 0xE0000244
    !!! sto: Failed to import driver package into Driver Store. Error = 0xE0000244

    !!! inf: Failed to import driver package into driver store
    !!! inf: Error 0xe0000244: The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version.
    <<< Section end 2017/12/07 09:41:57.758
    <<< [Exit status: FAILURE(0xe0000244)]

  • jjremaxjjremax detroit, miPosts: 43 ✭✭✭✭

    @benkores, the error message on the window shows.

    Error OK Error >nul 2>&1.

    Failed to install Qualcomm Driver! Check C:\Windows\Inf\setupapi.dev.log for details.

    Above is kind of details. Not sure if this will help you know what error would be or not.

  • jjremaxjjremax detroit, miPosts: 43 ✭✭✭✭

    @benkores, I downloaded a driver online and there is no yellow icon in my Device Manager now. Also, it shows ZTE 2017U in the Portable Devices of Device Manager. But it still shows that Failed to install Qualcomm Driver when I re-do your Axon/Toolkit. Please tell me where I did was wrong please. Thanks.

  • jjremaxjjremax detroit, miPosts: 43 ✭✭✭✭

    The Qualcomm issue is gone now. But could not test. Always tell me ADB device is not connected. Need to more thinking here

  • jjremaxjjremax detroit, miPosts: 43 ✭✭✭✭

    @benkores, After re-did the drivers download, The ADB and Qualcomm issues are gone. However, I tried many times now and it always come up saying "Fastboot device is not connected". From your pop-up instruction, saying if the device rebooted normally, then the device has no access to Fastboot. Use the Miflash instructions for the boot loader unlock option to restore the device fastboot mode. So, I downloaded Miflash (which is kind of Xiaomiflash) from online. The problem is whenever I try to select the phone from C in that Miflash:, the selection always grays out, which means I can not choose the phone and do such Miflash thing. Could you please help me here? Many thanks in advance.

  • benkoresbenkores Staten Island, NYPosts: 471 ✭✭✭✭✭✭✭

    @jjremax said:
    @benkores, After re-did the drivers download, The ADB and Qualcomm issues are gone. However, I tried many times now and it always come up saying "Fastboot device is not connected". From your pop-up instruction, saying if the device rebooted normally, then the device has no access to Fastboot. Use the Miflash instructions for the boot loader unlock option to restore the device fastboot mode. So, I downloaded Miflash (which is kind of Xiaomiflash) from online. The problem is whenever I try to select the phone from C in that Miflash:, the selection always grays out, which means I can not choose the phone and do such Miflash thing. Could you please help me here? Many thanks in advance.

    @jjremax said:
    @benkores, After re-did the drivers download, The ADB and Qualcomm issues are gone. However, I tried many times now and it always come up saying "Fastboot device is not connected". From your pop-up instruction, saying if the device rebooted normally, then the device has no access to Fastboot. Use the Miflash instructions for the boot loader unlock option to restore the device fastboot mode. So, I downloaded Miflash (which is kind of Xiaomiflash) from online. The problem is whenever I try to select the phone from C in that Miflash:, the selection always grays out, which means I can not choose the phone and do such Miflash thing. Could you please help me here? Many thanks in advance.

    You didn't have to download and install MiFlash. The toolkit comes with it and automatically installs it. All you have to do is run the bootloader unlock option. Try uninstalling the MiFlash you have installed and just run the option.

  • jjremaxjjremax detroit, miPosts: 43 ✭✭✭✭

    OK. I will uninstalling that. But how and where can I run the bootloader unlock option? Sorry, kind of stupid here. After I did the rebooted, it came up normal system reboot.

  • jjremaxjjremax detroit, miPosts: 43 ✭✭✭✭

    @benkores. I found the bootloader unlock option from your tool screen and did that. It came up Miflash and also it shut down the phone automatically, which let the Miflash could not detect the phone. Should I power the phone on to continue here or what should I do? Thanks again.

  • jjremaxjjremax detroit, miPosts: 43 ✭✭✭✭

    @benkores. I am able to Miflash now. However, the phone always goes to bootloader mode, and it is still locked after I followed your option 7, try to unlock the phone. What I am trying to say is it will goes to bootloader as well even I re-do the option 1, install the drivers. What should I do from here? Thanks.

  • jjremaxjjremax detroit, miPosts: 43 ✭✭✭✭

    @benkores. This morning, I re-did your Axon7Toolkit starting from option 1, it always come up Fastboot device in not connected in the bootloader. (There is Android Composite Bootloader Interface in the Device Manager). The device state is still locked. The device rebooted not normally, which means the device has access to fastboot now according to your pop up instruction. Could you please tell me what I should do from here? Thanks.

  • jjremaxjjremax detroit, miPosts: 43 ✭✭✭✭

    There is a yellow icon on that Android Composite Bootloader. But after update the driver, it shows the driver is up to date and the yellow icon still remains there.

Sign In or Register to comment.