Error protocol error fail to init control

Error protocol error fail to init control

i’m trying to unlock mi account on redmi note 9

Operation : Identify [ v2.25 ]
Mode : FLASH

1. Make sure device is powered off. Power off, if need. Wait 20 seconds after
2. Insert USB cable in phone
Waiting for device connection .

PTFN : MediaTek USB Port (COM60)
MODE : BOOTROM
PORT : 60
Waiting BOOT ack .
BROM : Skip ACK verify
BROM : Init BROM
BROM init passed!
CHIP : MT6768 , SBID : 0x8A00 , HWVR : 0xCA00 , SWVR : 0x0000
CODE : Talbot
TYPE : MODERN [RAPHAEL]
BROM : MEID : 579646BF3DD07E234D8A5A572B3E3C4E
BROM : SecLevel : 0x000000E7
BROM : SecMode : SBC+SLA+SDA+EXT
BROM : BROM|BL : 0x05|0xFE
BROM : BOOTROM
MODE : 0_base : BASE_v2112 | Manual : Enabled
BROM : SOCID : 58E399825B79778A0A4933FBB26BA027B81B5C88B8FE41557A BA161E1905F028
BROM : SLA : Local Auth

Error : Protocol Error : Fail to init Control!
>>> Check USB driver, restart software

how to fix it ?
thx

Posts: 1,112
Member: 1788877
Status: Offline >> Check previous message for more info!

Operation : Identify [ v2.25 ]
Mode : FLASH

1. Make sure device is powered off. Power off, if need. Wait 20 seconds after
2. Insert USB cable in phone
Waiting for device connection .

PTFN : MediaTek USB Port (COM60)
MODE : BOOTROM
PORT : 60
Waiting BOOT ack .
BROM : Skip ACK verify
BROM : Init BROM
BROM init passed!
CHIP : MT6768 , SBID : 0x8A00 , HWVR : 0xCA00 , SWVR : 0x0000
CODE : Talbot
TYPE : MODERN [RAPHAEL]
BROM : MEID : 579646BF3DD07E234D8A5A572B3E3C4E
BROM : SecLevel : 0x000000E7
BROM : SecMode : SBC+SLA+SDA+EXT
BROM : BROM|BL : 0x05|0xFE
BROM : BOOTROM
MODE : Xiaomi : Helio [G70][G80] | Manual : Disabled
BROM : SOCID : 58E399825B79778A0A4933FBB26BA027B81B5C88B8FE41557A BA161E1905F028
BROM : SLA : Local Auth
BROM : SLA : Auth Started!
BROM : SLA : Look for EMI
BROM : SLA : EMI not found
BROM : SLA : Auth Passed!
BROM : SLA : 0x0000001F
AGENT : Look for suitable BootChain in DA .
AGENT : MTK_AllInOne_DA.bin
AGENT : Found MT6768
AGENT : MTK_DOWNLOAD_AGENT
BROM : Sending 1st DA .
BROM : DA sent
BROM :Transfer control to DA .
DA : AGENT started!

DA : SETUP HW PARAMS FAILED! PROTO_VER is OLD?

Error : Fail to init protocol!
>>> Check and select CORRECT SETTINGS for your device!

Posts: 1,112
Member: 1788877
Status: Offline >> Remove battery, cable. Check cable/connection/driver! Check SW hint! Repeat operation!

Posts: 1,112
Member: 1788877
Status: Offline v2.25

Load IDBase v616218 Ok!

UserName and/or Password not set! Can’t continue!

Update failed! Check settings and/or internet connection!

Operation : Identify [ v2.25 ]
Mode : FLASH

1. Make sure device is powered off. Power off, if need. Wait 20 seconds after
2. Insert USB cable in phone
Waiting for device connection .

PTFN : MediaTek USB Port (COM60)
MODE : BOOTROM
PORT : 60
Waiting BOOT ack .
BROM : Skip ACK verify
BROM : Init BROM
BROM init passed!
CHIP : MT6768 , SBID : 0x8A00 , HWVR : 0xCA00 , SWVR : 0x0000
CODE : Talbot
TYPE : MODERN [RAPHAEL]
BROM : MEID : 579646BF3DD07E234D8A5A572B3E3C4E
BROM : SecLevel : 0x000000E7
BROM : SecMode : SBC+SLA+SDA+EXT
BROM : BROM|BL : 0x05|0xFE
BROM : BOOTROM
MODE : 0_base : BASE_v2112 | Manual : Enabled
BROM : SOCID : 58E399825B79778A0A4933FBB26BA027B81B5C88B8FE41557A BA161E1905F028
BROM : SLA : Local Auth
BROM : SLA : Auth Started!
BROM : SLA : Look for EMI
BROM : SLA : EMI not found
BROM : SLA : Auth Passed!
BROM : SLA : 0x0000001F
AGENT : Look for suitable BootChain in DA .
AGENT : MTK_AllInOne_DA.bin
AGENT : Found MT6768
AGENT : MTK_DOWNLOAD_AGENT
BROM : Sending 1st DA .
BROM : DA sent
BROM :Transfer control to DA .
DA : AGENT started!

DA : SYNC with DA FAILED!

Error : Fail to init protocol!
>>> Remove battery, cable. Check cable/connection/driver! Check SW hint! Repeat operation!

Источник

Error protocol error fail to init control

Card found : 73FD734E , v0137
Infinity-Box Chinese Miracle MediaTek Service Module [ MTK ] v2.05

Load IDBase v123080 Ok!

Operation : Identify [ v2.05 ]

1. Make sure device is powered off. Power off, if need. Wait 20 seconds after
2. Insert USB cable in phone
Waiting for device connection .

PTFN : MediaTek PreLoader USB VCOM Port (COM3)
MODE : PRELOADER PORT
PORT : 3
Error : Failed to open port!

Error : Fail to init protocol!
Remove battery, cable. Check cable/connection/driver! Check SW hint! Repeat operation!

Operation : Identify [ v2.05 ]

1. Make sure device is powered off. Power off, if need. Wait 20 seconds after
2. Insert USB cable in phone
Waiting for device connection .

PTFN : MediaTek PreLoader USB VCOM Port (COM3)
MODE : PRELOADER PORT
PORT : 3
Waiting BOOT ack .
PRELOADER : ACK confirmed!
BROM : Init BROM
BROM init passed!
CHIP : MT6580 , SBID : 0x8A00 , HWVR : 0xCA00 , SWVR : 0x0000
TYPE : LEGACY MTK
BROM : SecLevel : 0x00000001
BROM : SecMode : SBC
BROM : PRELOADER PORT
MODE : 0_base : BASE_v1712 | Manual : Disabled
AGENT : Look for suitable BootChain in DA .
AGENT : DA_PL.bin
AGENT : Found MT6580
AGENT : MTK_DOWNLOAD_AGENT
BROM : Sending 1st DA .

BROM : 0x00002001 : DA SEND ERROR!
ERROR : SECURE BOOT : MISMATCH BOOT SIGNATURE!
INFO : PRELOADER Level : Connect device in BROM mode!

Error : Fail to init protocol!
Remove battery, cable. Check cable/connection/driver! Check SW hint! Repeat operation!

Operation : Identify [ v2.05 ]

1. Make sure device is powered off. Power off, if need. Wait 20 seconds after
2. Insert USB cable in phone
Waiting for device connection .

PTFN : MediaTek PreLoader USB VCOM Port (COM3)
MODE : PRELOADER PORT
PORT : 3
Waiting BOOT ack .
PRELOADER : ACK confirmed!
BROM : Init BROM
BROM init passed!
CHIP : MT6580 , SBID : 0x8A00 , HWVR : 0xCA00 , SWVR : 0x0000
TYPE : LEGACY MTK
BROM : SecLevel : 0x00000001
BROM : SecMode : SBC
BROM : PRELOADER PORT
MODE : 0_base : BASE_v1712 | Manual : Disabled
AGENT : Look for suitable BootChain in DA .
AGENT : DA_SWSEC.bin
AGENT : Found MT6580
AGENT : MTK_DOWNLOAD_AGENT
BROM : Sending 1st DA .

BROM : 0x00002001 : DA SEND ERROR!
ERROR : SECURE BOOT : MISMATCH BOOT SIGNATURE!
INFO : PRELOADER Level : Connect device in BROM mode!

Error : Fail to init protocol!
Remove battery, cable. Check cable/connection/driver! Check SW hint! Repeat operation!

Operation : Identify [ v2.05 ]

1. Make sure device is powered off. Power off, if need. Wait 20 seconds after
2. Insert USB cable in phone
Waiting for device connection .

PTFN : MediaTek PreLoader USB VCOM Port (COM3)
MODE : PRELOADER PORT
PORT : 3
Waiting BOOT ack .
PRELOADER : ACK confirmed!
BROM : Init BROM
BROM init passed!
CHIP : MT6580 , SBID : 0x8A00 , HWVR : 0xCA00 , SWVR : 0x0000
TYPE : LEGACY MTK
BROM : SecLevel : 0x00000001
BROM : SecMode : SBC
BROM : PRELOADER PORT
MODE : 0_base : BASE_v1712 | Manual : Disabled
AGENT : Look for suitable BootChain in DA .
AGENT : MTK_AllInOne_DA.bin
AGENT : Found MT6580
AGENT : MTK_DOWNLOAD_AGENT
BROM : Sending 1st DA .

BROM : 0x00002001 : DA SEND ERROR!
ERROR : SECURE BOOT : MISMATCH BOOT SIGNATURE!
INFO : PRELOADER Level : Connect device in BROM mode!

Error : Fail to init protocol!
Remove battery, cable. Check cable/connection/driver! Check SW hint! Repeat operation!

Operation : Identify [ v2.05 ]

1. Make sure device is powered off. Power off, if need. Wait 20 seconds after
2. Insert USB cable in phone
Waiting for device connection .

PTFN : MediaTek PreLoader USB VCOM Port (COM3)
MODE : PRELOADER PORT
PORT : 3
Waiting BOOT ack .
PRELOADER : ACK confirmed!
BROM : Init BROM
BROM init passed!
CHIP : MT6580 , SBID : 0x8A00 , HWVR : 0xCA00 , SWVR : 0x0000
TYPE : LEGACY MTK
BROM : SecLevel : 0x00000001
BROM : SecMode : SBC
BROM : PRELOADER PORT
MODE : 0_base : BASE_v1712 | Manual : Disabled
AGENT : Look for suitable BootChain in DA .
AGENT : MTK_AllInOne_DA.bin
AGENT : Found MT6580
AGENT : MTK_DOWNLOAD_AGENT
BROM : Sending 1st DA .

BROM : 0x00002001 : DA SEND ERROR!
ERROR : SECURE BOOT : MISMATCH BOOT SIGNATURE!
INFO : PRELOADER Level : Connect device in BROM mode!

Error : Fail to init protocol!
Remove battery, cable. Check cable/connection/driver! Check SW hint! Repeat operation!

Источник

Error protocol error fail to init control

Information about [MTK sec 2022] models.

Write here phone model name and #CM2MT2 software log text in case of failed boot .

If you can boot phone with test-point attach here test-point image or link to test-point.
You can UPLOAD this way test-point images or new DA to server.

Before post here be sure you tried all possible base | model | DA | Local SLA options.

Try to change these config values:

1. Install CM2MT2 v2.37 or higher and click to «Identify». You will see list of suggested loaders. Try it.
2. Remember about boot keys, f.e. Volume + and Volume — buttons
3. Use TEST-POINT
4. In some cases it may be HW fault, f.e. faulty device DRAM. Make HW report and try also boot over FireFly mode.

If nothing helps it may be some kind of new unsupported device — people call it blocked bootrom
In this case the only way — wait for the solution.

Posts: 28,936
Member: 148515
Status: Offline Status: Offline >> Remove battery, cable. Check cable/connection/driver! Check SW hint! Repeat operation!

Posts: 29
Member: 644926
Status: Offline Status: Offline >> Remove battery, cable. Check cable/connection/driver! Check SW hint! Repeat operation!

Operation : Identify [ v1.20 ]

1. Make sure device is powered off. Power off, if need. Wait 10 seconds after
2. Insert USB cable in phone
Waiting for device connection .

PTFN : Nokia USB Serial Port (COM49)
MODE : NOKIA USB SERIAL
PORT : 49
BROM : Init BROM
BROM init passed!
CHIP : MT6261 , SBID : 0xCB01 , HWVR : 0x8000 , SWVR : 0x0001
BROM : SECCFG : 0x00000005
BROM : NOKIA USB SERIAL
BROM : 0x05 BL : 0x00
BROM : MEID : 9D2706EB9212F4E0D80CAB98B9BC64EF
BROM : Run BootLoader .
BOOT : Run BL ver. 01
BOOT : 0x05 BL : 0x01
BOOT : WD : 0005
BOOT : RTC : Setup .
BOOT : RTC : 000E
BOOT : PRJ : GEMINIVAL.10.01.11.p1
BOOT : SWR : 10.01.11
BOOT : BDDS : 30
BOOT : PSRM : Init
BOOT : PSRM : 0003

SWVer : GEMINIVAL.10.01.11.p1
FLASH : 00C2 : 0025 : 0036 : 0000
PRDC : 059Z0X8
IMEI[1] : 353102xxxxxxxxxx
IMEI[2] : 353102xxxxxxxxxx
NCK : 20 digits
PROV : 24407000

Saved as : 353102xxxxxxxxx.mtsec
Saved to : C:InfinityBoxBEST2Backup

Done!
Elapsed: 00:01:31

Operation : Reset Settings [ v1.20 ]

1. Make sure device is powered off. Power off, if need. Wait 10 seconds after
2. Insert USB cable in phone
Waiting for device connection .

PTFN : Nokia USB Serial Port (COM49)
MODE : NOKIA USB SERIAL
PORT : 49
BROM : Init BROM
BROM init passed!
CHIP : MT6261 , SBID : 0xCB01 , HWVR : 0x8000 , SWVR : 0x0001
BROM : SECCFG : 0x00000005
BROM : NOKIA USB SERIAL
BROM : 0x05 BL : 0x00
BROM : MEID : 9D2706EB9212F4E0D80CAB98B9BC64EF
BROM : Run BootLoader .
BOOT : Run BL ver. 01
BOOT : 0x05 BL : 0x01
BOOT : WD : 0005
BOOT : RTC : Setup .
BOOT : RTC : 000E
BOOT : PRJ : GEMINIVAL.10.01.11.p1
BOOT : SWR : 10.01.11
AGENT : Look for suitable BootChain in DA .
AGENT : Device AutoID failed!

Источник

Просмотр полной версии : Xiaomi 2016101 Redmi Note 4x нормально не коннектица с QLM

The reason I’ve done this is because partition names are not consistent between devices, in fact they’re totally arbitrary even when using different PIT files on the same device. There’s really nothing stopping ROM developers (or Samsung) from creating new PIT files and naming partitions however they please.

This might be a bit long-winded, but I’ll try explain why this is a problem…

Heimdall needs to know partition names in order to determine which files should be flashed to which partition on the device. In fact Heimdall actually needs uses the partition IDs. But the partition ID can be grabbed by looking up a partition name in a PIT file. The partition ID is what is sent to the phone when flashing.

When I first started developing Heimdall it only supported one device, the GT-I9000. As such I hard-coded the partition names to match arguments. Here’s the official mapping as supported by Heimdall 1.4 RC1:

argumentPartitionNamesMap["pit"].push_back("PIT");
argumentPartitionNamesMap["factoryfs"].push_back("FACTORYFS");
argumentPartitionNamesMap["cache"].push_back("CACHE");
argumentPartitionNamesMap["dbdata"].push_back("DBDATAFS");

argumentPartitionNamesMap["primary-boot"].push_back("IBL+PBL");
argumentPartitionNamesMap["primary-boot"].push_back("BOOT");

argumentPartitionNamesMap["secondary-boot"].push_back("SBL");
argumentPartitionNamesMap["secondary-boot"].push_back("SBL1");

argumentPartitionNamesMap["secondary-boot-backup"].push_back("SBL2");
argumentPartitionNamesMap["param"].push_back("PARAM");
argumentPartitionNamesMap["kernel"].push_back("KERNEL");
argumentPartitionNamesMap["recovery"].push_back("RECOVERY");
argumentPartitionNamesMap["efs"].push_back("EFS");
argumentPartitionNamesMap["modem"].push_back("MODEM");
argumentPartitionNamesMap["radio"].push_back("RADIO");
argumentPartitionNamesMap["normal-boot"].push_back("NORMALBOOT");
argumentPartitionNamesMap["system"].push_back("SYSTEM");
argumentPartitionNamesMap["user-data"].push_back("USERDATA");
argumentPartitionNamesMap["fota"].push_back("FOTA");
argumentPartitionNamesMap["hidden"].push_back("HIDDEN");
argumentPartitionNamesMap["movinand"].push_back("MOVINAND");
argumentPartitionNamesMap["data"].push_back("DATAFS");
argumentPartitionNamesMap["ums"].push_back("UMS.EN");
argumentPartitionNamesMap["emmc"].push_back("GANG");

As you can see that list is already a bit ridiculous, and some parameters like —primary-boot can correspond with multiple partition names eg. «IBL+PBL» or «BOOT».

Potentially I could keep updating this list every time someone encounters a new partition name. But between the time someone encounters the new partition and the time it takes me to update Heimdall, users would be stuck, and totally unable to flash.

However, I already solved this problem with the introduction of partition ID based flashing (in Heimdall 1.3?) through numbered arguments. This allows Heimdall to flash partitions that aren’t in the list of known hard-coded partition names (shown above). Theoretically this allows Heimdall to flash any device that uses PIT files.

This is actually how the Heimdall Firmware Package format works, through use of partition IDs. Although I’m considering migrating it to use partition names instead.

The new partition name arguments are just an extension of this system, instead of using the partition ID, you specify the exact partition name and Heimdall looks it up in the PIT file for you.

In fact as of v1.3, Heimdall Frontend was already using partition names. If you load up your devices PIT file in Heimdall Frontend you see the complete list of partitions on the device using their actual partition names (much like print pit).

Basically what I’m saying is that the —kernel, —secondary-boot etc. way of flashing has reached its limits and is no longer useful. This is particularly true when you look at the Qualcomm phones in US. Unfortunately they don’t match the —primary-boot, —secondary-boot model at all. If I recall correctly, there are 6 different files that are required to perform roughly the same task as just boot.bin and Sbl.bin on Exynos devices. They also have two different modem partitions one called MODEM, and one called MDM. Rather than trying to define and maintain separate arguments for all these different partitions its much easier just to allow users to flash using partition names directly.

HOWEVER, I am considering adding the following command:

heimdall autoflash [--pit <filename>] --files <filename[, filename, ...]>

For example, your flash would have looked like:

heimdall autoflash --files system.img cache.img modem.bin boot.img bootloader.bin hidden.img recovery.img

What autoflash would do, is what I just did for you manually. Which is map filenames to particular partitions.

However, this autoflash method would give up one of the most significant advantages of Heimdall, which is that you can name your files however you please. For autoflash to work, you’d have to name your files precisely how they appear in the PIT file, but this is how Odin works anyway so it’s not too big of an issue. The other downside is of course that autoflash would be limited to flashing partitions that actually have a filename. If you look at the output of your print-pit command you’ll see some partitions don’t have filenames. Odin is not capable of flashing these partitions, but Heimdall is.

Re: подружить USB-UPS с NUT

Сообщение

156 » 02.03.2009 09:06

Привет народ! У меня система сусе 10.3 , бесперебойник иппон 700, настраивал как написано тут
http://vitaly.easycoding.org/2008/02/26/po…on-v-linux.html
так там всё заработало сразу при дефолтных настройках через ком порт. Теперь поставил сусю 11.1 , решил настроить через usb кабель, для начала не хотел мегатек стартовать, писал ошибку при старте. Решилось раскоментированием строки user=root в файле ups.conf , как я предполагаю, это назначает рутовские права для этой проги, что не есть хорошо, ну на данном этаме это не важно. [myups]
driver = megatec_usb
port = auto
по команде lsusb видно , на какой шине и адресу сидит бесперебойник
Теперь пишет при старте
# rcupsd start
Starting NUT UPS drivers done
Starting NUT UPS server done
Starting NUT UPS monitor done
как видно, вроде бы все работает, драйвер стартанул, сервер поднялся, монитор поднялся, но при просмотре по команде
# upsc myups@localhost
пишет , Error: Driver not connected , очевидно , что не может подключиться к драйверу . На сайте мегатека в факе достаточно туманно написано, про неправильные настройки и конфигурации. Так же не может подключиться к драйверу и прога монитонинга knutclient . Хотелось бы получить общие предположения, почему при очевидном старте драйвера к нему не может подключиться ничего. Пробовал компилисть натклиета, 4 последние версии, ни одна не собралась под сусей 11.1. Короче, вечером удалил нат, и заново установил из сайта webpin , началась полная хрень, и именно не запускаются драйвер, монитор и сервер, но почему то пишет , что они выключились, и по прежнему драйвер не грузится. Это при тех же самых конфигах. Одназночно прихожу к выводу , что виновата програмка nut , так как на одном и том же железе при одних м тех же настройках совершенно разные результаты. При такой глючности проги настраивать её бесполезное занятие, так как даже при правильных конфигах не работает.