DISCUSSION: BB5BOX Update BB5 v0.0.3.5 - added 2 unlock methods

[The_Gorr]

Thanks for infos

br

<= The_Gorr =>

Originally Posted by BB5box.org

Method 2 was used from software version 0.0.2.6 to 0.0.3.0
Method 1 was used on all other software versions.
Some users reported they have success and work more good Method 2 (we read forum and based this on reported software versions).
Some other users reported the all other versions (Method 1) worked well or more good.
So, we included both 2 methods now. Try one, if not unlock can try the other one.
It also depends on phone models, so on some phones could work better Method 1 and on some other phones could work better Method 2.
What exactly is the difference is hard to explain here, mainly is about tunning timing values and at exactly what time (regarding to clock front signal) data is sampled, also if data is sampled on rising or falling edge of the clock.

Something like this graphic (we can change timings inside CPLD also clock edge, risimg or falling):
http://en.wikipedia.org/wiki/Image:F...ld_Toutput.svg

All this timings in real world (when you perform unlock) could differ from one flash chip to another. Also this timings is influenced of capacitance loading values over CLK and DATA lines (= length of TP wires, position of TP wires, GND connection point).

[shadigsm]

nice update wow

www.gsm4pal.com

[samuelscu]

Originally Posted by BB5box.org

Method 2 was used from software version 0.0.2.6 to 0.0.3.0
Method 1 was used on all other software versions.
Some users reported they have success and work more good Method 2 (we read forum and based this on reported software versions).
Some other users reported the all other versions (Method 1) worked well or more good.
So, we included both 2 methods now. Try one, if not unlock can try the other one.
It also depends on phone models, so on some phones could work better Method 1 and on some other phones could work better Method 2.
What exactly is the difference is hard to explain here, mainly is about tunning timing values and at exactly what time (regarding to clock front signal) data is sampled, also if data is sampled on rising or falling edge of the clock.

Something like this graphic (we can change timings inside CPLD also clock edge, risimg or falling):
http://en.wikipedia.org/wiki/Image:F...ld_Toutput.svg

All this timings in real world (when you perform unlock) could differ from one flash chip to another. Also this timings is influenced of capacitance loading values over CLK and DATA lines (= length of TP wires, position of TP wires, GND connection point).

Thanks for the explaination. Very good.
Please add this in the update thread next time if you would like to.
That would be very convient for users.
Thanks BB5Box Team suppoters.

[r.a]

hi

thanks for update

[BB5box.org]

Originally Posted by samuelscu

Thanks for the explaination. Very good.
Please add this in the update thread next time if you would like to.
That would be very convient for users.
Thanks BB5Box Team suppoters.

It was added now in update thread, also with yellow markings for what is most important to know for end user.

[Nurettin Duman]

Very nice update Thanks BB5 team!!!........................

[honyjee]

nice update Thanks BB5 team

[senkron24]

Originally Posted by BB5box.org

Method 2 was used from software version 0.0.2.6 to 0.0.3.0
Method 1 was used on all other software versions.
Some users reported they have success and work more good Method 2 (we read forum and based this on reported software versions).
Some other users reported the all other versions (Method 1) worked well or more good.
So, we included both 2 methods now. Try one, if not unlock can try the other one.
It also depends on phone models, so on some phones could work better Method 1 and on some other phones could work better Method 2.
What exactly is the difference is hard to explain here, mainly is about tunning timing values and at exactly what time (regarding to clock front signal) data is sampled, also if data is sampled on rising or falling edge of the clock.

Something like this graphic (we can change timings inside CPLD also clock edge, risimg or falling):
http://en.wikipedia.org/wiki/Image:F...ld_Toutput.svg

All this timings in real world (when you perform unlock) could differ from one flash chip to another. Also this timings is influenced of capacitance loading values over CLK and DATA lines (= length of TP wires, position of TP wires, GND connection point).

this is genail idea no need downgrade etc i wil test big thx

best ragarts senkron24

[FU_Too]

Originally Posted by BB5box.org

Method 2 was used from software version 0.0.2.6 to 0.0.3.0
Method 1 was used on all other software versions.
Some users reported they have success and work more good Method 2 (we read forum and based this on reported software versions).
Some other users reported the all other versions (Method 1) worked well or more good.
So, we included both 2 methods now. Try one, if not unlock can try the other one.
It also depends on phone models, so on some phones could work better Method 1 and on some other phones could work better Method 2.
What exactly is the difference is hard to explain here, mainly is about tunning timing values and at exactly what time (regarding to clock front signal) data is sampled, also if data is sampled on rising or falling edge of the clock.

Something like this graphic (we can change timings inside CPLD also clock edge, risimg or falling):
http://en.wikipedia.org/wiki/Image:F...ld_Toutput.svg

All this timings in real world (when you perform unlock) could differ from one flash chip to another. Also this timings is influenced of capacitance loading values over CLK and DATA lines (= length of TP wires, position of TP wires, GND connection point).

Ah! at last you start explaining reasons to us, that is most refreshing and gives us understanding of some of our problems we sometimes have. Could you also explain some of the causes of these errors "ERROR: 11160001 ERROR: 30020091" and what causes can be attributed to response byte 55 and response byte 08 so to give us better understanding of what we are doing wrong when its no fault of box or your software

[GUDO-GSM]

can u add next update 6131 version 6.60 unlock..

br

[icebergblack200]

Good update BB5box Team

[dragosgsm]

That's the best update ever!!!!!!!!!!!!!!!
Thank's BB5Box Team....no more update/downgrade firmware...that's a goog thing!!!!!!!!!!!!!!!

[fretburner]

FU_too was right.please give us some guides or errors.we are blindfolded regarding errors.we do not know what we did wrong why we got errors like response byte 08,etc.i almost throw my box with that error.

[johansel]

Keyboard wrong codes counter: 0 wrong tries from max. 3 tries
Cable wrong codes counter: 0 wrong tries from max. 10 tries
Phone unlocked succesfull

[BB5box.org]

Originally Posted by FU_Too

Ah! at last you start explaining reasons to us, that is most refreshing and gives us understanding of some of our problems we sometimes have. Could you also explain some of the causes of these errors "ERROR: 11160001 ERROR: 30020091" and what causes can be attributed to response byte 55 and response byte 08 so to give us better understanding of what we are doing wrong when its no fault of box or your software

Response byte 08 - was explained more times, is usual FBUS response to wron SP code. It could come from wrong testpoint touch (e.g. resistive contacts, to much used cables - dirty, oxidated, longer cables, electrical noisy environment in your area, ...)

Response byte 55 - this is not an real response from FBUS, is like an error code, and that means no any response come from phone at SP unlock code FBUS command. Usualy comes when touch wrong testpoint, or when capacitance load over CLK and/or DATA lines are to high, and phone (who is powered and running, CPU is reading continously from flash chip) can no more operate in right conditions (is like you just "remove" flash chip when phone is running), so regular software flow execution inside phone CPU is stopped and usualy CPU watchdog comes and give a reset to whole phone.

ERROR: 11160001 ERROR: 30020091 - this errors comes when software can no more communicate with phone when reading SP locks command over FBUS. Usualy commes after response byte 55. You will get exactly same errors if disconnect FBUS cable or if disconnect power supply from phone when software read SP locks ...

So, both this 3 errors could have complicated causes, and a real answer of exactly where is the problem can be find only if have an high speed digital osciloscope with memory, who record CLK and DATA signals, and watching at this signals will show the real cause.

But again all this errors was discussed more times in more threads, and solution is: shorter cables, right GND connection point, shorter USB cable, clean testpoint location (e.g. on some 6300, 5200, 5300 testpoints could be covered with some isolating material, including dirty and oxidated areas), corract and firmly touch of testpoints, fixing VBAT, BSI and GND connections on phone board (using some adeshive tape).

Hope now all is more clear ...