Status err 0xc0010001 flash tool как исправить

No, I didn’t reboot or unplug the device. I keep it connected to the same USB port.
I can’t run a bypass utility twice without a power cycle. BTW is it expected?
First time output is the same that I posted already, when I try to runt it again it just output:
Waiting for device
With power cycle the outputs are the same.
Please also take into account that bypass utility is not working correctly without these changes

diff --git a/src/device.py b/src/device.py
index cd75939..a1a49c9 100644
--- a/src/device.py
+++ b/src/device.py
@@ -123,13 +123,16 @@ class Device:
         self.echo(addr, 4)
         self.echo(size, 4)

-        self.check(self.dev.read(2), to_bytes(0, 2))  # arg check
+#        self.check(self.dev.read(2), to_bytes(0, 2))  # arg check
+        assert from_bytes(self.dev.read(2), 2) <= 0xff

         for _ in range(size):
             data = from_bytes(self.dev.read(4), 4)
             result.append(data)

-        self.check(self.dev.read(2), to_bytes(0, 2))  # status
+#        self.check(self.dev.read(2), to_bytes(0, 2))  # status
+
+        assert from_bytes(self.dev.read(2), 2) <= 0xff

         # support scalar
         if len(result) == 1:

otherwise it’s throwing an exception:

[2021-04-22 10:49:08.729440] Disabling protection                                                                                                    
Traceback (most recent call last):                                                                                                                     
File "C:bypass_utilitymain.py", line 213, in <module>                                                                           
main()                                                                                                                                             
File "C:bypass_utilitymain.py", line 58, in main                                                                               
 result = exploit(device, config.watchdog_address, config.payload_address, config.var_0, config.var_1, payload)
File "C:bypass_utilitysrcexploit.py", line 17, in exploit                                                                      
device.read32(addr - (cnt - i) * 4, cnt - i + 1)                                                                                                   
File "C:bypass_utilitysrcdevice.py", line 126, in read32                                                                       
self.check(self.dev.read(2), to_bytes(0, 2))  # arg check                                                                                          
File "C:bypass_utilitysrcdevice.py", line 88, in check                                                                         
raise RuntimeError("Unexpected output, expected {} got {}".format(gold, test))
RuntimeError: Unexpected output, expected 0x0000 got 0x0003

Check this comment from the original issue #25 (comment)

02.12.2018, 16:51

Fish



Регистрация:

17.08.2013

Сообщений:

34,095

Репутация:



13204

Принесли телефон Meizu M5 на перепрошивку. SP Flash Tool постоянно выбивал одну и ту же ошибку 0xC0010001. Телефон определялся корректно, но прошиваться не хотел.

Решилась проблема удалением всех драйверов МТК и установкой по новой драйвера. До этого (куча устройств была прошито) проблем с драйверами не было.

Архив с драйвером, который ставил прикрепил к посту.

Cкачать:

USB-to-Serial_1_0_1.zip




14.11.2021, 09:55

Алексей Полоскин



Регистрация:

23.02.2015

Сообщений:

1

Репутация:



0

Сообщение от Fish

Принесли телефон Meizu M5 на перепрошивку. SP Flash Tool постоянно выбивал одну и ту же ошибку 0xC0010001. Телефон определялся корректно, но прошиваться не хотел.

Решилась проблема удалением всех драйверов МТК и установкой по новой драйвера. До этого (куча устройств была прошито) проблем с драйверами не было.

Архив с драйвером, который ставил прикрепил к посту.

вложение не скачивается



29.04.2023, 12:18

Fish



Регистрация:

17.08.2013

Сообщений:

34,095

Репутация:



13204

Сообщение от Алексей Полоскин

вложение не скачивается

Для скачивания вложений зарегестрируйтесь и оформите подписку

1. The flashing machine has passed the red bar, and the purple bar is stuck. (Error code 4008)
If this happens, you can remove the battery, then reinstall it, and choose to shut down after entering REC. Then brush again.
2. After the driver is installed, an error message will pop up after a few flashes.
This situation is generally due to the power supply problem of the USB port. Use the USB port on the back of the PC, or unplug several devices with high power consumption.
3. Under normal operation/working conditions, it is different from the problem prompt in step 2. (Typical 3013 question, the highest occurrence rate)
This question is often asked by everyone. This question basically occurs because everyone upgraded to 4.1.2 and then wanted to go back to 4.0.4. Everyone uses 4.1. 2 When flashing, you can use SP_Flash_Tool to flash 4.0.4 again, or use the official SP_Flash_Tool of Turtle 4.1.2.
Summary of MTK mobile phone line flashing error messages and solutions
[1022 error]: The flashing software version does not match the mobile phone, or the USB interface is not working well
[Solution] First change the USB port to flash: no It is recommended to download the latest flashing software and try it!
[1040 Error]: S_UNSUPPORTED_OPERATION flashing boot file Scatter.txt does not match
[Solution]: Download the line flashing ROM suitable for your machine, it is obvious that this copycat opportunity is encountered! For example, the machine is a dual-core 6577, but the downloaded flashing ROM is a single-core 6575, so an error will be reported.
[2005 Error]: S_BROM_CMD_STARTCMD_FAIL
[Solution]: Actually, the flashing package file is not loaded. Yes, reopen the flashing software and continue to flash!
[3002 Error]: If the following picture is not checked, after flashing, it will prompt [>TOOL DL image Fail! =>uboot is blocking
by dl info]
[Solution]Remember to check the option in the following figure, and just re-line it once! In this way, the boot screen will not be stuck.
[3144 Error] S_DA_EMMC_FLASH_NOT_FOUND:
[Solution]: The boot file Scatter.txt does not match, please change to the correct line and package! Mainly common in EMMC partition model
and MTD partition machine boot TXT can not be mixed!
[4004 error]: driver problem
[solution]: first try to install the MTP driver, if it fails, uninstall the driver and then reinstall the driver to identify or reinstall the computer
[4032 error]: operation method problem
[Solution]: After the red progress bar is completed, please press the volume down button (the key to decrease the volume) immediately to trigger the subsequent
yellow progress bar for flashing. It is best to brush the machine with the battery installed. For details, please refer to the tutorial post on the top of the Lenovo S920 section.
There are more detailed operations!
【4050 Error】: S_FT_NEED_DOWNLOAD_ALL_FAIL; a common error in single recovery. Because there is a big gap between the target ROM file and the handheld
system, it is impossible to flash it alone.
[Solution]: Replace the recovery.img file into the original factory line brush package, click the screenshot below to select, and then line brush, so
the progress bar will go. If it still doesn’t work, refresh the line completely.
[5066 error] S_DL_PC_BL_INVALID_GFH_FILE_INFOR:
[Solution]: Import the flashing boot file txt error, check whether the imported txt file is used for flashing! Do it again!
[8038 Error]: SP FLASH TOOL ERROR, the specific reason is unknown
[Solution]: 1. If you encounter this prompt, then, you must only click on the “fireware-upgrade” or “solid”
Piece-upgrade” button to refresh! Complete the line brush once!
2. It may also be that the version of the flashing software is not suitable for mobile phones
[8100 error]: can not find usb port! This is a reminder that the flashing driver is not fully recognized/installed. Please reinstall the driver
or change the port to change the computer system to XP, etc.
[Solution]: Please reinstall the driver and shut down to identify it, it is recommended Change the computer, change the desktop, etc.
[8200 error]: The reason is that the mobile phone system and the flash package system are different from the chip platform.
[Solution]: Method 1: Find the ROM again, your ROM is wrong ! For example, the machine is 6575 and the flashing package is 6577, so it will
report such an error. Method 2: Update the latest version of the flashing software