Printable View
Hi I'm using NKFlasher4.79 in Win XP with userport to flash my 5210.
After flashing I use DCT3Repairv3.2 to update faid/unlock.
My phone seems to get flashing done smoothly(backup aslo tested) but when switched on, displays nothing and even cannot connect through mbus cable! It happened after I was monkeying around with DCT3Repair, what might have been wrong? now I cant even connect through mbus!
btw I do have a Dejan1.08 dongle but I dunno how to use! need help
Well another 5210 cannot get range(need to calculate faid) so I did... many times now but ro range. checked the mbus cable by trying to read phone info and was successful. I guess this means the mbus cable is ok huh? Tried EepromToolsv4 by b-phreaks, can read phone info but says no phone connected when pressing set sp locks to default or repair eeprom and sometimes 'cant update Eeprom'!
Any solutions... guys!!!
Hmmm, Try NokTool 1.8 :)
I have used Noktool 1.8 Not helpful, it cannot initialise phone
Hi,
I flashed this type once myself with Rolis and found out my backup flash was void, only filled with FF's.
I found out for 5210 it's better to use kNok, that gave a reliable backup file.
So if it's no XP-ports problem, possibly this can help U?
NokDoc
Yeah I used knok to re-flash the 5210 and its flash was ok. then there comes calculating faid. the mbus can read the phone and after pressing update faid it does restart the phone. BUT no range! restarts phone!!
I have tried eeprom tools, it too CAN read phone info but when i press the padlock it says no phone connected. :-?
Hi,
If it's an original file U use, setting the faid command itself always supposed to work.
But if some bytes were changed in Ur file, recalcs are required.
And for 5210 recalcing the flash checksum is still impossible.
And a wrong flash checksum make a wrong set faid command.
A trick to work around that is to disable all calc functions inside Ur flash.
But that's only a clue when U modded a file.
NokDoc