Mxbox problem- help me! (ANSWERED) I have a problem with mxbox after update on 00.50 on bb5 i recieve this error ERROR: Packet Error(0xAA), code 0xC0000002 ERROR: Packet Error(0xAA), code 0xC0000002 Error details: Bad contact, TX line remains low ! VCC_PH BSI TX RX RX2 CLK 1 0 0 1 1 0 ERROR: bootstrap failed! ...on dct4 works perfectly.I upgraded and downgraded the box a few times, i clicked synchronize files, and i change a few mini usb cables! i checked hardware and it's okay! i receive this error without any phone connected! does anybody have a solution please help me!:confused: |
Quote:
|
that's true! but it should be a fix! |
Try changing the usb cable is good ........ |
mx box usb cabel se problam bhi ati hai [change and trai] |
just do synchronization once................ |
please post again buscheck logs with serial, do not edit. BR |
Quote:
Same problem for me Here is my log with serial, buyed mxkey, buyed hti buyed usbanalyzer, now first answer from support without thread deleted, thankyou gbluez BR MXKEY [MxKey Team HTI Flasher Interface (WinUSB) 2], SN: C080C525 Using device: HTI, FW ver: 00.50, SN: 00005911 Connection status: OHCI:HUB:USB 2.00 (Full-speed) Driver: WinUSB, ver: 3.5.0.0 Module ver: 1.0.0.19663(13-12-2011), Library ver: 1.0.0.13682(17-12-2011) APE Data : SYSTEM ASIC ID: 17100708 [OMAP1710 ver: 2.0] ASIC MODE ID: 00 PUBLIC ID: 08CCA4FB8C3E903E768A7219517178C8DB114756 ROOT KEY HASH: 49A97E826B93BA20B7ED0B082475C00500000000 ROM ID: 1DFD66132C872FD4 CMT Data : SYSTEM ASIC ID: 000000010000022600010006010C192101003000 [RAP3G ver: PA 3.0] EM0 ID: 00000295 EM1 ID: 00000B22 PUBLIC ID: 18D0000B67F80154178DBDE813D174223EBB1C51 ASIC MODE ID: 00 ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1 ROM ID: 273F6D55DFAAF68F SecondaryBoot: RAP3Gv3_2nd.fg [BB5] version: 9.11.1 revision: 0.0 size: 0x3C00 Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002 eBB5ProtocolType: OLD |
installed rev 1.5, update box but same problem Driver: WinUSB, ver: 3.5.0.0 Module ver: 1.0.0.19228(10-11-2011), Library ver: 1.0.0.13150(10-11-2011) APE Data : SYSTEM ASIC ID: 17100708 [OMAP1710 ver: 2.0] ASIC MODE ID: 00 PUBLIC ID: 08CCA4FB8C3E903E768A7219517178C8DB114756 ROOT KEY HASH: 49A97E826B93BA20B7ED0B082475C00500000000 ROM ID: 1DFD66132C872FD4 CMT Data : SYSTEM ASIC ID: 000000010000022600010006010C192101003000 [RAP3G ver: PA 3.0] EM0 ID: 00000295 EM1 ID: 00000B22 PUBLIC ID: 18D0000B67F80154178DBDE813D174223EBB1C51 ASIC MODE ID: 00 ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1 ROM ID: 273F6D55DFAAF68F SecondaryBoot: RAP3Gv3_2nd.fg [BB5] version: 9.11.1 revision: 0.0 size: 0x3C00 Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002 eBB5ProtocolType: OLD |
Quote:
Quote:
To solved ur problem, please use USB Interface Check : HERE Regard, |
Quote:
@LEENO: are you sure your phone is OK? please check with single engine based phone. BR |
@gbluez all phones are ok, readed and flashed with other tools but, after update 0.50 hti can't read info, still with ufc and phone in testmode. Only boot work. Me and other users asked for same problem but threads deleted BR |
Quote:
|
We can not simulate this problems and all boxes what we have is working good. Promised one of this HTI from an user with same problem. Under investigation. All you have to do not is to wait till we get this box and do the investigations. BR, Manole |
All times are GMT +1. The time now is 18:13. |
vBulletin Optimisation provided by
vB Optimise (Pro) -
vBulletin Mods & Addons Copyright © 2024 DragonByte Technologies Ltd.
- GSM Hosting Ltd. - 1999-2023 -