6630 - CMT 1st Boot Error, RAP3 not ready

[ManWolf]

I've been trying out the BB5 support this evening using my 6630.

On two different PCs I get the following error after the second line beginning RAP3 R0ID. The same cable/UFS box combination can read the hardware and software info from the phone, it is reporting v3.45.113 for the APE and Euro-1 PPM.

Any ideas how to fix this? I'm keen to upgrade the firmware but not until I'm convinced that the phone is responding correctly.

The phone works quite happily as a phone, so I don't think it is faulty.

--

WolfMan

Hello,
Can You tell us which cable You use , and if possible, atach here screenshot with mentioned error.

Thanks.

[ARBI]

you must to use a special adapter for bb5.
regards

[ManWolf]

Originally Posted by legija

Hello,
Can You tell us which cable You use , and if possible, atach here screenshot with mentioned error.

Thanks.

Cable is a Griffin/UFS N6630 cable, it does not have the connections for external Vpp. I need to check the connections and compare them with the schematic posted yesterday, it may be a cable fault but I can't see how exactly. Before the error message the blue and green LEDs are lit quite solidly for some 15 seconds or more, so the box is trying to read or write something to the phone.

I will generate a screen shot later today and upload it.

--

WolfMan

[ManWolf]

Originally Posted by ManWolf

I will generate a screen shot later today and upload it.

Here are the screen shots, I'll check the cable and report later

--

WolfMan

[Odia The Ultimate]

Originally Posted by ManWolf

Here are the screen shots, I'll check the cable and report later

--

WolfMan

I've had this a few times on different PCs, can you try to lower the speed, if that does not help increase the FBUS_DELAY in the ini file, also try to run check again directly after the not ready error.

Odia.

[zoltranfull]

[Settings]
Dct3_Path=\Wintesla\
Beep=On
Tips=On
Full_Info=On
Engl=W2004 ; Do not edit this line
Fade=Off ; Fade in animation control
F_Delay=1 ; F-Bus Delay in ms

[Support]
Url1=www.twisterflasher.com
Url2=www.ufsxsupport.com/index.php
Url3=www.google.com
Url4=www.ufsx.com
ka=-26326
kb=14037
kc=16265
kd=-4514

Fbus Delay 1 My Computer Asus P4 2.8 GHZ 120 GB HARDDISK 256 mb ddram Speed Fbus delay ????

[ManWolf]

Originally Posted by Odia The Ultimate

I've had this a few times on different PCs, can you try to lower the speed, if that does not help increase the FBUS_DELAY in the ini file, also try to run check again directly after the not ready error.

Odia.

I've tried changing the FBUS speed setting and it has made no difference at all. I'll try the FBUS_DELAY setting, can you suggest a good number to try, the default appeats to be 1ms.

--

WolfMan

[Odia The Ultimate]

Originally Posted by ManWolf

can you suggest a good number to try, the default appeats to be 1ms.

Its impossible to say, you need to find the correct setting for the PC your using by trial and error, but 2 and 3 are good values, the range is 1 ... 9.

Odia.

[ManWolf]

Originally Posted by Odia The Ultimate

Its impossible to say, you need to find the correct setting for the PC your using by trial and error, but 2 and 3 are good values, the range is 1 ... 9.

OK, well I've tried all values from 1 through to 9 with both a 6630 and 6680, neither will boot correctly.

I've tried various combinations of power button pushing and plugging in cables at different times, none of this helped at all.

I have also just checked the cables I have for each phone against the schematics posted by Phil yesterday, they are correctly connected as far as I can see.

So, what's the next thing? I'm using a 1.13GHz PIII and my laptop is a 1.3GHz Celeron M 350.

--

WolfMan

[ManWolf]

Originally Posted by ManWolf

OK, well I've tried all values from 1 through to 9 with both a 6630 and 6680, neither will boot correctly.

I've tried various combinations of power button pushing and plugging in cables at different times, none of this helped at all.

I have also just checked the cables I have for each phone against the schematics posted by Phil yesterday, they are correctly connected as far as I can see.

I've obviously had a visit from the bit-rot fairy, so I decided to completely uninstall the UFS drivers and UFS Suite and then to reinstall UFS Suite 2.0 on my laptop again. For some reason this has now resulted in a working DCTxBB5 program. I'll do the same on the desktop machine too.

I don't know what this could be exactly, but some combination of factors screwed it up and now it seems to be fixed.

Apologies for having to hassle everyone about it here.

--

WolfMan