PDA

View Full Version : Cables Problem with the new update 5.0


toukour
09-12-2004, 06:24
Blazer Update 5.0 released

This is what I got with the new version

Cable B is detected by software as B. ?
Cable E is detected by software as B. ?
Cable C is detected by software as B. ?
Cable A detected ok!
Cable D detected ok!

Please help Us .

Best regards.

EndlessConnections
09-12-2004, 08:55
Since ,youre in USA you shouldnt be worried about other cables and as for the Update, Blazer Team works on updates 24/7 and will resolve this issue soon.


Blazer Update 5.0 released

This is what I got with the new version

Cable B is detected by software as B. ?
Cable E is detected by software as B. ?
Cable C is detected by software as B. ?
Cable A detected ok!
Cable D detected ok!

Please help Us .

Best regards.

dannyogolo
09-14-2004, 19:59
I think I have same problem

I tried to use cable C for 7100, but It detected it as Alcatel 320 Cable B
I tried E to, same thing.
Now I cant do anything with that phone.

Is this software or cable problem ???
I also tried with 4.9c and 4.9e, both give same error (though this was after first using 5.0)

Raskal
09-14-2004, 21:28
I think I have same problem

I tried to use cable C for 7100, but It detected it as Alcatel 320 Cable B
I tried E to, same thing.
Now I cant do anything with that phone.

Is this software or cable problem ???
I also tried with 4.9c and 4.9e, both give same error (though this was after first using 5.0)

We will double check it tomorow, and let post here results.

Phil
09-16-2004, 13:29
I had this problem too, eeprom content inside cables was wrong.
After reprogram them all is OK and works fine

Regards

Phil

toukour
09-16-2004, 16:55
We will double check it tomorow, and let post here results.
WE STILL WAITING FOR THE RESULTS .PLEASE

BEST REGARDS.

hoangminhtam
09-16-2004, 20:27
i have problm. with the cable C1200 that i made after Blazer's hex n schema c1200.
the box can not detect the cable
inside, i use eep. 24c256 instead of 24LC256 as guided in schema .
m' I wrong ??

dannyogolo
09-17-2004, 10:53
Yes, we are waiting for solution for bad cables

hakima
09-17-2004, 13:37
I have problem with cables "C" when working with G5300i!!!
Always must to press and hold power button untill all done!!!

WBR

doctormike
09-18-2004, 00:53
Dear Blazer Team,

I also have cable problems:

Cable A is not recognized at all and get message : Insert cable
Cable B is recognized as E.

I tried versions 49 & 50 of your software.

PS. I am new user and have no older versions to check.

Running WinXP - SP1 and have tried on another pc under WinMe; results are the same.

Regards
Mike

Raskal
09-18-2004, 01:30
I had this problem too, eeprom content inside cables was wrong.
After reprogram them all is OK and works fine

Regards

Phil


I see teleway start copy cables :) to make it cheap.

Let see how cheap can make the uni box...

toukour
09-18-2004, 14:15
I see teleway start copy cables :) to make it cheap.

Let see how cheap can make the uni box...
We are all waiting for that.But what we should do with our bad cables ? :confused:

Raskal
09-18-2004, 15:09
We are all waiting for that.But what we should do with our bad cables ? :confused:

Ask your reseller for replacement and they will do that, is the fastest way.

toukour
09-18-2004, 15:20
Ask your reseller for replacement and they will do that, is the fastest way.

Thank you a lot . :) :)

hoang
09-18-2004, 19:46
I have problem with cables "C" when working with G5300i!!!
Always must to press and hold power button untill all done!!!

WBR
Connect pn 15 to 18, that's all!

hakima
09-20-2004, 12:45
Yes,U are right bro!!!
Now all done!!!
I already open my cables( which include with my box ) and see hehe
Pin 13 short pin 15 to GND :mad:
Now 15 short to 18 ( PWO short to VBAT ) and pin 13 is GND!!!

WBR

taopheek
10-02-2004, 23:54
I think I have same problem

I tried to use cable C for 7100, but It detected it as Alcatel 320 Cable B
I tried E to, same thing.
Now I cant do anything with that phone.

Is this software or cable problem ???
I also tried with 4.9c and 4.9e, both give same error (though this was after first using 5.0)

hey im still waiting for the reply cos i ve d same prob with Danny :mad: