2 mxbox no read no check not nothing after upgrade firmware (ANSWERED - WARRANTY)

[christiam]

hi

I have two green boxes, after upgrading to firmware 0.50 mx 3.5 rev 1.6 does not read any phone with dtc4, does nothing bb5 Mr. gbluez coemnto he had to change the pnp BCP69 which one of the boxes change it but the result is the same, then I read that TIP32 is compatible and proceeded to change but no mistake, in my case I remove this component NBOX BCP69 and place it on the green and mx either, but it turns out, install and TIP32 in NBOX this if it works, Mr. Manole I dare say it is problem of your hardware or your software and try everything and Documentation can not yet work with any of the mxbox rj45 and one has no more than 2 months of buying it, which happens left the log and pictures

sr that I have to buy additional warranty mxbox and not true I sell in my country its box to other workshops and asked not time to update the firmware to version 0.50 and continue to work normally with your box with the old firm, the box is cheap which is expensive is the shipping and taxes paid pro send the money to another country to buy distributors you publish

[christiam]

hi

I have two green boxes, after upgrading to firmware 0.50 mx 3.5 rev 1.6 does not read any phone with dtc4, does nothing bb5 Mr. gbluez coemnto he had to change the pnp BCP69 which one of the boxes change it but the result is the same, then I read that TIP32 is compatible and proceeded to change but no mistake, in my case I remove this component NBOX BCP69 and place it on the green and mx either, but it turns out, install and TIP32 in NBOX this if it works, Mr. Manole I dare say it is problem of your hardware or your software and try everything and Documentation can not yet work with any of the mxbox rj45 and one has no more than 2 months of buying it, which happens left the log and pictures

sr that I have to buy additional warranty mxbox and not true I sell in my country its box to other workshops and asked not time to update the firmware to version 0.50 and continue to work normally with your box with the old firm, without of*****ng the box is cheap which is expensive is the shipping and taxes paid pro send the money to another country to buy distributors you publish

this log mxgreen check bus dtc4

MXKEY Serial: [MxKey Team HTI Flasher Interface (WinUSB) 4] - C08541DC
Using device: HTI BOX, FW ver: 00.50
Connection status: OHCI:HUB:USB 2.00 (Full-speed)
Driver: WinUSB, ver: 3.5.0.0 , NTMP ver: 6.1.7601.17514
Module ver: 1.0.0.18624(06-08-2011), Library ver: 1.0.0.12274(06-08-2011)
Boot error: 00 00 FF FE
- Repeat the procedure. Sometimes it is a matter of temporary communication problem or similar.
- Check that all used cable are solid without any visible damage and have good contact. If possible, try with other cables.
- On rare occasions phone might be damaged or dead. So, if possible, try with another phone.

This log is with the BCP69 pcp97 and TIP32 pnp but none of the 3 runs, but the same if I ran my old NBOX


[IMG]

[christiam]

Originally Posted by christiam

hi

I have two green boxes, after upgrading to firmware 0.50 mx 3.5 rev 1.6 does not read any phone with dtc4, does nothing bb5 Mr. gbluez coemnto he had to change the pnp BCP69 which one of the boxes change it but the result is the same, then I read that TIP32 is compatible and proceeded to change but no mistake, in my case I remove this component NBOX BCP69 and place it on the green and mx either, but it turns out, install and TIP32 in NBOX this if it works, Mr. Manole I dare say it is problem of your hardware or your software and try everything and Documentation can not yet work with any of the mxbox rj45 and one has no more than 2 months of buying it, which happens left the log and pictures

sr that I have to buy additional warranty mxbox and not true I sell in my country its box to other workshops and asked not time to update the firmware to version 0.50 and continue to work normally with your box with the old firm, without of*****ng the box is cheap which is expensive is the shipping and taxes paid pro send the money to another country to buy distributors you publish

this log mxgreen check bus dtc4

MXKEY Serial: [MxKey Team HTI Flasher Interface (WinUSB) 4] - C08541DC
Using device: HTI BOX, FW ver: 00.50
Connection status: OHCI:HUB:USB 2.00 (Full-speed)
Driver: WinUSB, ver: 3.5.0.0 , NTMP ver: 6.1.7601.17514
Module ver: 1.0.0.18624(06-08-2011), Library ver: 1.0.0.12274(06-08-2011)
Boot error: 00 00 FF FE
- Repeat the procedure. Sometimes it is a matter of temporary communication problem or similar.
- Check that all used cable are solid without any visible damage and have good contact. If possible, try with other cables.
- On rare occasions phone might be damaged or dead. So, if possible, try with another phone.

This log is with the BCP69 pcp97 and TIP32 pnp but none of the 3 runs, but the same if I ran my old NBOX


[IMG]

error in atach is bcp69 no pcb ok


As you can see the exchange of BCP69 mxbox NBOX to the first image and throw that error paquet dtc4 error and does not read the bootloader, but again we TIP32 new BCP69 or purchased in an electronic phone if I read whit jaf crack whit nbox

[MANOLE]

Please ask your reseller for warranty. We give 6 months warranty to all resellers.

This warranty starts from the date you first time update your HTI, not from the date he sold it to you.

What is your HTI serial number ? I can tell you when your HTI warranty starts.

Postal charges are really cheap if send with Air Mail registered. I know it from experience.

BR,
Manole

[kiricu]

@christiam

why you don't try to add input and output caps very close to the voltage regulator IC pins? If you check on DS of any VR Linear IC you can see that it is recommended to put as close as possible to the pins to guaratee the specs wrote on DS, the benefits are better stability and better load transition. You can put #2 100uF Electrolytic aluminium caps for input and output pins.

Best Regards
kiricu

[girlmikaela]

salamat amo ok n rin box namin

[shadigsm]

MXKEY [MxKey Team HTI Flasher Interface (WinUSB) 6], SN: C0802DAA
Using device: HTI, FW ver: 00.50, SN: 00005A1B
Connection status: EHCI:HUB:HUB:USB 2.00 (Full-speed)
Driver: WinUSB, ver: 3.5.1.0
Module ver: 1.0.0.19815(08-01-2012), Library ver: 1.0.0.13716(10-01-2012)
APE Data :
SYSTEM ASIC ID: 008815D3 [Nomadik ver: 2.x]
ASIC MODE ID: 00
PUBLIC ID: 09A1E38CA0E3652915DCF15387AFCBE30863D9AD
ROOT KEY HASH: 0BBC4203E2D3B82504C75CB65E906A35
ROM ID: 137A9A3B33259D2C
CMT Data :
SYSTEM ASIC ID: 000000010000022600010006400C192101031103 [RAPIDO3G ver: 1.13]
EM0 ID: 00000295
EM1 ID: 00000B22
PUBLIC ID: 0B9000026872005261C2A706DAFD30F1F2659F9A
ASIC MODE ID: 00
ROOT KEY HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE
ROM ID: 4B9B75103E691FF8
SecondaryBoot: RAPIDOv11_2nd.fg [BB5] version: 1.37.1 revision: 0.0 size: 0x3B80
Supported Ids: 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105
eBB5ProtocolType: OLD ؟؟