January 24th 2011 pre-release

[swingtan]

Just letting you know that some are using the tap-tap talk plug in......

Sent from my HTC Desire

[GMPX]

No Problem.

Sent from my PC which has a Gigabyte H55-USB3 MB with an i5 quad core, GT430 video card.

[ScarabEpic22]

Wonder if this is my issue BBF'ing my P10 as Ive applied all the latest updates and formatted everything at least 2x now. Ill check again in a few weeks when Im home again, but is there any way to fix the magic identifer? Seems even when I took my original .tun that I pulled back in 2005 and just opened it in V7 (probably around build 139-143, cant remember exactly) and resaved as a .ctd to BBF it gave me the $0502 error. Did the same thing with my T42 file I converted from a .tun, but if I BBR the file first then I could BBF that one back in.

Sent from my HP dv6t Quad Edition Core i7-2630QM, ATi Radeon HD 6570M 1GB, Bluray rom, 640gb 7200rpm hdd. (and crap this one has to go back to HP, dang Intel's Cougar Point chipset having the SATA quality degrading over a few years. Ive had it for maybe 3 weeks now :( )

[swingtan]

I'm trying a new test. I've read the tune out with build 149/142 and made a couple of adjustments. Then saved the tune as a .ctd to the SD card ready for BBF test. Doing this results in a successful BBF. So I think the magic numbers were missed very early on and the save process does not generate the magic number again.

Simon.

Sent from my HTC Desire (again)....

[ScarabEpic22]

Hmmm ok Ill try flashing the stock tune then reading it back out and modifying that.

Wonder if my magic number was missing from the beginning and is the reason I couldnt BBF.

[swingtan]

I reckon that's it in a nut shell. Some time in the past the magic number was either not used, or dropped out of the code for some reason. Back when BBF didn't exist, this wasn't a problem as the old laptop flash process didn't need it. Then when BBF came in, the magic numbers became importent, but as it occurred just after BBR, it's likely that most people tried reading tunes first, which created the magic number. The used BBF on those read tunes so all was OK. It's not until you went back and used and old laptop read tune that the problem became apparent. I'm also going to guess the problem only occurs with early OS's in each controller, later OS's that came out after the magic number became important probably have it configured automatically.

Whatever the cause, the work around is fairly easy.

• Flash the tune in with the laptop
• BBR the tune back out
• Continue tuning with the newly read tune

Of course if you're stuck with BBF only, then it may be a bit harder. However I guess we could work on a set of known good OS's with magic numbers, then youjust need to create a script from the tune you have to apply to the new base tune.

Simon

[gmh308]

No Problem.

Sent from my PC which has a Gigabyte H55-USB3 MB with an i5 quad core, GT430 video card.

But without a tap tap talk plug in.....

[aaronr]

Did this issue get fixed yet. I have same issue with BB trying to flash tunes. I will try the work around on post #76. Thanks

[Blacky]

Yes it should be fixed in the currently available version here:
http://www.efilive.com/index.php?opt...=48&Itemid=133

Regards
Paul

[aaronr]

O.K. I made sure all my stuff is updated but still getting same errors. I tried to to read my tune with the bb and got a message that says options.txt is empty. When I try to flash tune with bb error $0502 scrip file not found.
Thanks