MTK-bypass / bypass_utility

MIT License
460 stars 114 forks source link

MT6768 not responding correctly #21

Closed mca-network closed 3 years ago

mca-network commented 3 years ago

EDIT: Solved, I let the phone die on a shelf for two weeks, happened to be on a fresher install of windows 10 and hadn't installed any drivers yet. so with only the material I know had worked at hand, and a little more knowledge into the bootrom itself, I was able to recover the phone with a couple NVRAM errors, but I fixed those after I figured out how to.

_**This device amongst other things has an erased boot partition. The device loops and doesn't have the ability to enter fastboot, it seems only the first part? of the MTK BROM driver is being loaded now if I'm interpreting that correctly. I constantly get this response back once the device is seen, as well as a couple others I will also add as I come across them again.

Essentially I'm under the impression that the phone isn't responding back correctly the info it's looking for because it seems to be something different every time. Not sure how to get it to pick back up again.**_

[2021-03-27 07:33:46.580863] Waiting for device
[2021-03-27 07:34:06.551479] Found port = COM5

Traceback (most recent call last):
  File "main.py", line 212, in <module>
    main()
  File "main.py", line 43, in main
    config, serial_link_authorization, download_agent_authorization, hw_code  = get_device_info(device, arguments)
  File "main.py", line 174, in get_device_info
    log("Device hw code: {}".format(hex(hw_code)))
NameError: name 'log' is not defined
Press any key to continue . . .