Saturday, October 29, 2011
nokia 1680 solution
1680 Camera solution
1680 short solution
1680 repair solution
1680 charger solution
1680 local mode 1
1680 local mode 2
nexian Solution
1265 lcd blank
nexian hang keypad
nexian dead
ruim connector break
ruim connector break(jumper)
Sunday, October 2, 2011
HWK error update log
Error messages:
1. HWK SD REPAIR ERROR: xxxxx
HWK upgrade error. This error occures when HWK was affected by third-party tools before upgrade or your HWK is a clone. Please don't contact anyone, it's your own stupid fault.
2. Your account is suspended. Please contact your reseller!
Your account is blocked by administrator. Please contact your reseller
You need to provide your reseller at least the following information:
- The date and invoice number of your HWK purchase
- Full log given to you by upgrade client
3. No more upgrade logs.
HWK module with this serial number was already upgraded. If you already upgraded your HWK, you need not to upgrade it again until directed. If you haven't tried to upgrade it yet, get this error on upgrade and cannot run latest software versions, please contact your reseller
You need to provide your reseller at least the following information:
- The date and invoice number of your HWK purchase
- Full log given to you by upgrade client
4. Server is going to shutdown. Please try update in 20 minutes.
Server is being stopped by administrator. Please try upgrade process again in 20 mins.
5. Account for this HWK module does not exist on server. Please contact your reseller!
Account for HWK number with this serial does not exist on server. Please contact your reseller.
You need to provide your reseller at least the following information:
- The date and invoice number of your HWK purchase
- Full log given to you by upgrade client
6. Authorization failed! Are you using the latest HWK Upgrade client software version?
Server authorization error. Please ensure you are using the latest UFS suite and upgrade client software versions
7. Your account was closed by the server administrator. Please contact your reseller!
Your account on server was closed by administrator. Please contact your reseller
You need to provide your reseller at least the following information:
- The date and invoice number of your HWK purchase
- Full log given to you by upgrade client
8. Error: Your update client version is expired! Please download new client from the support area and start the upgrade again.
Download new upgrade client from support area and try upgrading your HWK module with it.
9. Error upgrading applets: HWK UPDATE ERROR: xxxxxx
Hardware problem occured during upgrade process. Please contact your reseller.
You need to provide your reseller at least the following information:
- The date and invoice number of your HWK purchase
- Full log given to you by upgrade client
10. Error connecting to ufs: hwk login error: xxxx
Error establishing data transmission channel with HWK module. Please ensure your module is present and is correctly installed. If you are unable to solve the problem by yourself - please contact your reseller
You need to provide your reseller at least the following information:
- The date and invoice number of your HWK purchase
- Full log given to you by upgrade client
11. Authentication stage error: Server reported error:Not translated!
Please select English language om the software's welcome page and retry upgrade process. Now error message will be shown correctly
12. Connection to server failed: Socket Error # 10060
Connection to server failed: Socket Error # 10061
Connection refused.
Please disable or uninstall all installed antivirus and firewall software and retry upgrade operation. If the error persists, please ensure, that your internet provider is not using firewall also
13. Authentication stage error: Socket Error # 10053
Software caused connection abort.
General TCP/IP failture occured. Please disconnect from internet (having your modem switched off for example), wait for 5-7 minutes and connect to internet again and retry upgrade process.
14. Authentication stage error: Socket Error # 10054
Connection reset by peer.
TCP/IP connection to server from your PC is unstable. Please try to connect to internet via different internet provider. If you have no such possibility, please try to perform upgrade process several times until you get positive result.
15. Connection Closed Gracefully.
Connection to server was suddenly terminated. Please retry upgrade process a bit later or try to connect to the internet via another internet provider and retry the upgrade.
16. Authentication stage error: Error: Server returned unrecognized reply.
You are using an old version of the update client, please install the latest HWK Suite and use the update client from that version.
17. License 5 not active.
Please contact your UFSx reseller and request a set of license keys for your UFSx device.
By: GSM Forum
1. HWK SD REPAIR ERROR: xxxxx
HWK upgrade error. This error occures when HWK was affected by third-party tools before upgrade or your HWK is a clone. Please don't contact anyone, it's your own stupid fault.
2. Your account is suspended. Please contact your reseller!
Your account is blocked by administrator. Please contact your reseller
You need to provide your reseller at least the following information:
- The date and invoice number of your HWK purchase
- Full log given to you by upgrade client
3. No more upgrade logs.
HWK module with this serial number was already upgraded. If you already upgraded your HWK, you need not to upgrade it again until directed. If you haven't tried to upgrade it yet, get this error on upgrade and cannot run latest software versions, please contact your reseller
You need to provide your reseller at least the following information:
- The date and invoice number of your HWK purchase
- Full log given to you by upgrade client
4. Server is going to shutdown. Please try update in 20 minutes.
Server is being stopped by administrator. Please try upgrade process again in 20 mins.
5. Account for this HWK module does not exist on server. Please contact your reseller!
Account for HWK number with this serial does not exist on server. Please contact your reseller.
You need to provide your reseller at least the following information:
- The date and invoice number of your HWK purchase
- Full log given to you by upgrade client
6. Authorization failed! Are you using the latest HWK Upgrade client software version?
Server authorization error. Please ensure you are using the latest UFS suite and upgrade client software versions
7. Your account was closed by the server administrator. Please contact your reseller!
Your account on server was closed by administrator. Please contact your reseller
You need to provide your reseller at least the following information:
- The date and invoice number of your HWK purchase
- Full log given to you by upgrade client
8. Error: Your update client version is expired! Please download new client from the support area and start the upgrade again.
Download new upgrade client from support area and try upgrading your HWK module with it.
9. Error upgrading applets: HWK UPDATE ERROR: xxxxxx
Hardware problem occured during upgrade process. Please contact your reseller.
You need to provide your reseller at least the following information:
- The date and invoice number of your HWK purchase
- Full log given to you by upgrade client
10. Error connecting to ufs: hwk login error: xxxx
Error establishing data transmission channel with HWK module. Please ensure your module is present and is correctly installed. If you are unable to solve the problem by yourself - please contact your reseller
You need to provide your reseller at least the following information:
- The date and invoice number of your HWK purchase
- Full log given to you by upgrade client
11. Authentication stage error: Server reported error:Not translated!
Please select English language om the software's welcome page and retry upgrade process. Now error message will be shown correctly
12. Connection to server failed: Socket Error # 10060
Connection to server failed: Socket Error # 10061
Connection refused.
Please disable or uninstall all installed antivirus and firewall software and retry upgrade operation. If the error persists, please ensure, that your internet provider is not using firewall also
13. Authentication stage error: Socket Error # 10053
Software caused connection abort.
General TCP/IP failture occured. Please disconnect from internet (having your modem switched off for example), wait for 5-7 minutes and connect to internet again and retry upgrade process.
14. Authentication stage error: Socket Error # 10054
Connection reset by peer.
TCP/IP connection to server from your PC is unstable. Please try to connect to internet via different internet provider. If you have no such possibility, please try to perform upgrade process several times until you get positive result.
15. Connection Closed Gracefully.
Connection to server was suddenly terminated. Please retry upgrade process a bit later or try to connect to the internet via another internet provider and retry the upgrade.
16. Authentication stage error: Error: Server returned unrecognized reply.
You are using an old version of the update client, please install the latest HWK Suite and use the update client from that version.
17. License 5 not active.
Please contact your UFSx reseller and request a set of license keys for your UFSx device.
By: GSM Forum
Saturday, October 1, 2011
Watch Dog Definition
Watchdog stored in UEM, first used for controlling the system power-on and power-down. Both are used to block IMEI security and storage, the Watchdog will control the IMEI in UEM ROM with the IMEI stored in the IC flash, if there is a difference between the IMEI in UEM IMEI and IMEI in Flash then the Watchdog will provide the Shutdown command in 13detik time. Example watchdog could occur if the UPP who recognize the IMEI of sync as below:UEM IMEI: 35153200064744IC Flash IMEI: 35153200147706
* FLASH memory for the IMEI in UEM UEM Inside there is a place used for storing data and Tuning Values IMEI. IMEI data storage properties in UEM is OTP (One Time Programming) where the IMEI data can be written only once and can not be removed or replaced, therefore UEM used or has ever entered the IMEI number can not be used to other phones, except where IC IMEI in Flash can be equated back to the UEM IMEI itself. The process of returning the IMEI mensikronkan called Calculate RPL. Of course there is the IMEI flash IC that can be written back.If IMEI in UEM UEM problematic or corrupt then it can not be used or can not be repaired anymore! UEM IMEI is corrupt can easily be identified if we do the info on the flasher box and stated: UEM IMEI: 351p32e% 064 724 <<IMEI in UEM is no longer display the numerical data! There is no any solution other than replacing it with anew. In the above case nokia phone will usually display the IMEI ????????? when we type the following code: * # 06 # <where the IMEI that is on UEM IMEI is different than it should, although there is only one number was different. This causes the phone can not accept sim cards (GSM) and will die automatically in a few seconds.WD BB5 reply in terms more familiar with Superdongle key. so if there BB5 SD yg watchdog corrupt so well, auto restart every few minutes. gampangannya wd be interpreted as a time bomb .. dct4/wd2 if only the range of 40 seconds dah barking his alias ****** explode om, hehe .. (I wrote this term) BB5 rather lengthy reply in the range 3-5 minutes, but in principle the same aja ..wd cause is a corrupt RPL.
for the case of the WD what hars done depends on where the source of the damage, if imei diuem yah yg dah walopun calculate RPL remains an injectable solution UEM wd wrote his will in the new locker injected both UEM and flash ic (and data1 data2)kecuai if the source of the flash ic aja corrupt, and injecting enough ask2rpl/calculate data1 (ic flash) dah wrong.
specific areas that store BB5 RPL not only in Rap, but also in nandflash. who can make beautiful BB5 RPL 123 456 ... the cause of data on nandflash tereset / kehapus. solution to this problem just re-write rpl well if there is data backupx, kalo beli deh yah ndak rplx. of the process via a read ask first (when readask who read the master data that are on Rap)
* FLASH memory for the IMEI in UEM UEM Inside there is a place used for storing data and Tuning Values IMEI. IMEI data storage properties in UEM is OTP (One Time Programming) where the IMEI data can be written only once and can not be removed or replaced, therefore UEM used or has ever entered the IMEI number can not be used to other phones, except where IC IMEI in Flash can be equated back to the UEM IMEI itself. The process of returning the IMEI mensikronkan called Calculate RPL. Of course there is the IMEI flash IC that can be written back.If IMEI in UEM UEM problematic or corrupt then it can not be used or can not be repaired anymore! UEM IMEI is corrupt can easily be identified if we do the info on the flasher box and stated: UEM IMEI: 351p32e% 064 724 <<IMEI in UEM is no longer display the numerical data! There is no any solution other than replacing it with anew. In the above case nokia phone will usually display the IMEI ????????? when we type the following code: * # 06 # <where the IMEI that is on UEM IMEI is different than it should, although there is only one number was different. This causes the phone can not accept sim cards (GSM) and will die automatically in a few seconds.WD BB5 reply in terms more familiar with Superdongle key. so if there BB5 SD yg watchdog corrupt so well, auto restart every few minutes. gampangannya wd be interpreted as a time bomb .. dct4/wd2 if only the range of 40 seconds dah barking his alias ****** explode om, hehe .. (I wrote this term) BB5 rather lengthy reply in the range 3-5 minutes, but in principle the same aja ..wd cause is a corrupt RPL.
for the case of the WD what hars done depends on where the source of the damage, if imei diuem yah yg dah walopun calculate RPL remains an injectable solution UEM wd wrote his will in the new locker injected both UEM and flash ic (and data1 data2)kecuai if the source of the flash ic aja corrupt, and injecting enough ask2rpl/calculate data1 (ic flash) dah wrong.
specific areas that store BB5 RPL not only in Rap, but also in nandflash. who can make beautiful BB5 RPL 123 456 ... the cause of data on nandflash tereset / kehapus. solution to this problem just re-write rpl well if there is data backupx, kalo beli deh yah ndak rplx. of the process via a read ask first (when readask who read the master data that are on Rap)
Subscribe to:
Posts (Atom)