Kalmar
Junior Member | Редактировать | Профиль | Сообщение | Цитировать | Сообщить модератору
Ошибки, возникающие при прошивке и методы лечения,
найдено здесь http://www.miccom.cc/phpBB/viewtopic.php?p=664178
Error 0101
==========
Description:
DIV cannot connect to your phone.
Probable Solution:
- Clean your contacts
- Cable may be faulty
- Wrong settings for LPT port
- Battery not loaded
- Lots of other things ...
The 0101 seems to be like a "device not ready" error.
Common after a failed flash, then it cannot connect after that.
Unhooking the cable from the phone, reseating the battery, and reconnecting the cable seems to solve it.
Error 0102
==========
There is an easy trick to flash such phones giving this error with div. (Battery Dance)
Just do the following steps:
1. Open back case of phone so the battery can be accessible
2. Connect div cable to phone
3. Start div, select flash files, press flash
4. Now to the trick:
- on the phone without the battery cover, you need to press with your fingers on the battery to make contact.
- when div progressbar shows 2% there is small delay before div shows error 0101 or 0102 and during that delay it is essential to release pressure on battery enough to loose its contact with the phone, and right after that reapply pressure on the battery again. Voila ! Progress bar shows 5%. This step must be repeated untill div shows "load data to phone" . Then do not release battery untill flash has ended. All will be good - phone alive!
Well, these steps might have to be repeated fifteen or twenty times untill it works, you have to have a lot of patience, but finally it will work.
Error 0106
==========
RSA Protected flash (R6c005 etc)
This error is caused because SE have changed their flashes, they are RSA protected, and div cannot bypass the boot authority.
Solution:
This can be removed with DIV5. Follow the DIV5 tutorial for removing RSA
Error 3002
==========
Description:
unknown
Probable solution:
unknown
Error 320B
==========
Description:
unclear
Probable solution:
- Try a reflash
Error 350E
==========
Description:
- Might be a problem with processor speed
Probable solution:
(1) DISABLE the HT support and set the Paralla port to EPP
(2) Install a brand new Windows 98 in another HDD (don't forget to install all drivers for all devices, otherwise, you MUST unplug all another devices.
(3) FULLY charge your cellphone battery
(4) Follow the steps provided by Muppet, or the updated one by ToddJG.
(5) ****** more important ****** set the "Flashing operation speed (baud rate):" to "115 KBps". Don't know why, but set to higher speed seems to lead to failure
(6) Start to flash
For most people decreasing the rate of flashing (baud) on the Div software seems to solve this problem.
Error 3523
==========
Description:
unclear
Probable solution:
- Try a reflash
Error 3541
==========
Solved it by doing:
1. Disconnect phone
2. Remove battery
3. Insert battery
4. Connect phone
5. Select Normal as flash speed
6. Do selected jobs
Error 3608
==========
Description:
ERROR 3608 means ARM flash chip failed to erase (bulk erase command issued, but flash not blank). It does it at 1% as on ARM chip, it does not use the progressive erase-write cycles, uses erasing the whole chip (this is the first percent), then starts to write only if the chip is empty (e.g. contents in the given range is of 0xFFs).
This can be caused by badly soldered or damaged flash chip, dirty phone connectors, bad connections, but also because of your PC being too fast (hate stable and accurate delay values, eh?), thus it would advance to flash blank check/write before the chip can actually finish the operation.
- Might be a faulty or fried ARM chip inside the phone
- Might be a faulty cable
- Might be a faulty dongle
Probable solution:
Try correcting the above mentioned issues that could cause this.
Error 3612
==========
Description:
- Might be closely related to error 3608
Probable solution:
see above
Error 3614
==========
Description:
- Might be closely related to error 3608
Probable solution:
see above
OR
In one case was found to be wired pins inside the phone connector part of the cable to be touching non wired pins.
Error 3621
==========
Description:
Occurs when trying to fix bluetooth problem with T68x
Probable solution:
unknown
Error 4014
==========
Description:
unclear
Probable solution:
Flash Chip needs replacement/reballing due to poor/no contact (T68).
Try downloading DIV USB/LPT 1.8 or newer for Txx6 phones. Run userport.exe, follow the instructions when you click "Start", and when you have userport.exe working, then run the divusb application and choose "Rebuild SP Area" for the T616.
That should fix your problems. If it still reports that error, then there's either something wrong with your phone, something wrong with your cable, or something wrong with your LPT setup on your computer.
Error 4016/4017/4019
====================
Description:
Damaged GDFS area.
Once this happened, you can only flash avr & arm. All other functions will give you error 4016/4017.
Solution to solve this problem:
1) Flash FULL GDFS in avr format (sbn).
OR
2) Mr. the_laser have a "T610 GDFS Writer" to flash FULL GDFS.
Probable solution:
Go to http://laser.cellular-support.com and download setool.exe, as well as a GDFS file for your phone.
Extract the GDFS file, and put it in the same location as setool.exe.
Get userport and run it (it should be included with DIV USB if you don't have it).
Plug in your terminator dongle, drop to a command prompt, go to the folder where you put the files, and type:
setool -?
That will tell you how to use it.
SETool is the same thing as GDFS_Writer.
Error 5202
==========
Description:
- Might be unstable USB Power
Probable solution:
- Try a different USB port
Has been seen a few times. Before trying the rebuild SP Area again, pull the battery out for 10 seconds then put it back in. Try the flash again. Also make sure you don't have lots of other USB devices plugged in/in use (such as a USB mouse) as it is noticed that this can seriously piss Div off while trying some operations.
Error 5302
==========
Description:
- Might be closely related to error 5202
Probable solution:
see above
Error 5701
==========
Description:
- Might be from playing around with the battery menu
Probable solution:
Flash using the "Batterymonitor_GDFS.zip" in unpacked condition. Available in the downloads section.
Error 6101
==========
Description:
Before flashing, doing a "Read All Codes" causes this error.
Probable solution:
Old firmware (i.e. R1A) seems to cause this.
Do "Rebuild SP using OTP IMEI" before flashing.
Error 6106
==========
Description:
- Might be closely related to error 6101
Probable solution:
Before making the operation you must execute Rebuild SP area using OTP IMEI.
Error 6202
==========
Description:
unknown
Probable solution:
unknown
|
(( говорит нет такого ресурса 
