Nokia6300白屏重启死而复生记

陪伴我一年半的6300，今天早上开机突然崩溃，可以打开菜单，但是无法打开短信或者任何和手机存储有关的内容，开机一分钟左右就自动重启，反复如此。
说是突然，其实并不突然，前两天就有征兆，因为短信太满了，开机非常慢，昨天早上更是开了几次才开起来，正是因为如此，今天早上起来的第一件事情就是想把里边的短信导出来然后删掉，没想到，就在这最后的最后时刻，它坚持不住了！
本来还期望多开几次能够有一次能能打开，只要有一次能打开，我就能删掉一些东西，那么就能正常了，没想到，折腾一上午，重启无数次，问题依旧！在网上搜索，有和我一模一样的问题，但是解决方案只有送客服或者自己刷机！不管这两种方案，都意味着，我要丢失通信录和整个11月的短信！
一直折腾到中午，实在没有办法，郁闷得午饭也没吃完，于是带上手机直奔文三路昌地火炬大厦的客服中心。进去取了个号，坐着边等边想，虽然过保了，但是要是收我50，能把手机修好，我还是可以接受的。没想到轮到我了，一问客服MM，居然要100，我说，这个问题很明显，刷一下机，10分钟就好的啊，又不要什么配件，可是他说，对啊，刷机就是这个价格，当场晕倒，不在我可以接受的范围内，直接回来。
于是，下午我就开始研究如何刷机，在看了很多文章之后，锁定一篇和我完全一样情况的解决方案，还有一篇手机无法启动的强刷方案作为详细的补充。

诺基亚6300白屏死机刷机复活技巧分享
http://www.it.com.cn/f/mobile/088/22/645456.htm

凤凰2008强刷死机图文教程
http://www.nokiabbs.com/thread-558404-1-1.html

无奈，实验室限制网络，几个软件下到傍晚还没下好，一怒之下回到寝室，发誓不解决问题不吃饭。

总结起来，主要步骤如下（部分摘抄自上述两篇文章）：

一、准备刷机工具。共三个，A.凤凰刷机2008  B. 6300的固件包 C. 糯鸡鸭的PC套件

下载地址如下：

《凤凰刷机2008破解版》下载（需要下载 纳米机器人）：http://www.namipan.com/d/Phoenix2008Patched.exe/88d9bd4708d2c30a28a0ae35f8ff4e430ca634bdf1c51107
刷机固件《6300_RM-217_DP20_6.00__sw-06.60.exe》：http://www.namipan.com/d/30bd4da35faec0b5338fa56d32209868bc4f9d922dbfe601
刷机固件《6300_RM-217_DP20_6.10__sw-06.60.rar》：http://www.namipan.com/d/90a2ce3aece161eebd656db9f2636c5609e75c8521ac8c04

二、 安装刷机工具，这里注意必须在安装凤凰刷机2008之前把电脑里之前装的PC套件和数据线驱动都删除干净。 然后按照凤凰刷机→固件包（注意先装6.00再装6.10）→PC套件的安装顺序把工具安装好。
注：网上有帖子说凤凰2008不需要PC套件，有些说要，我是在最后装了PC套件才开刷的，这样操作下来没问题。但是几乎所有帖子说如果原来有PC套件，要先下个专门的cleaner清除掉，然后装凤凰。我下午在NOKIA官方网站上看到这个CLEANER，但是傍晚要用的时候又找不到了。反正本本系统有GHOST，用五分钟建了个全新的系统，防止意外。

三、和原文中说的一样，常规的方法肯定不行，因为机器一直重启，只能强刷。

以下摘抄原文：

　　诺基亚6300拿出SIM卡及存储卡，装上电池，插上数据线。连入电脑，插上直冲，以防刷机过程中断电。 （这里最好能放进一块没用的SIM卡，或者确保刷机的时候没有电话进来的SIM卡，我在后面按电源键的时候，由于没有SIM卡开机会询问，几次开机都无法检测到设备，最后放进去一块SIM开才OK。至于直冲，后来也是直接拔掉才能识别设备，不知道怎么回事，反正是冒了把险，但是要是一块满的电池肯定没问题的，因为刷机只需要10分钟，我现在刷好过去两个小时了，电池还是满的）
　　打开phoenix，file -manage connections-new-勾上NO CONNECTION（这里没有这个NO CONNECTION可以勾，参考另一篇，先选择USB，建立好连接，然后把NO CONNECTION的顺序换到第一个，我觉得这步还是很重要的）,-下一步-完成-apply-close
　　              ↓

　　file-open product-选RM217（注意，找不到6300的，RM217即小6了）-ok
　　              ↓

　　flashing-firmware updata-点...标志- 选择版本，注意此处最好选与手机之前版本相同的，6300是0515747，简体中文国行版-OK。
（如果是其他版本，可以参考《BB5系列刷机最新CODE码对照表大全》
http://www.nokiabbs.com/thread-492413-1-1.html）
　　          ↓

　　勾上DEAD PHONE USB FLASHING （此处非常关键，是强刷的必要条件）
　　              ↓

　　点REFURBISH
　　          ↓

　　后按照提示需长按下手机上的开机按钮，电脑会发现6300并自动安装PC套件里的一些驱动。 （我在这里第一次按了没反应，提示设备没有加载，具体的英文忘了，然后跳出一个框问是否重试。幸好有另一篇文章，说到这个“凤凰2008开始写入程序（这个是写入主程序时的截图，如果进入不到这个步骤，从上一步开始重复操作操作，掌握好按下开机键的时间）”，实践证明，按开机键的时间非常关键，要一开始就马上按，我反复折腾了几次才顺利完成）

　　嘻唰唰……嘻唰唰……

　　10分钟后刷机完成。

　　开机，随着动听的糯鸡鸭开机声（平时也没觉得这么悦耳啊，哈哈），小六复活了，一切恢复正常。

哈哈，非常开心，前两天刚刚修复了T60的FAN ERROR问题，其实就是拆出来，刷刷灰加点油，但是要是送到客服，之前有人去过，又是100多的。今天又解决了手机的大问题，看来以后要注意下不要存太多东西了，也说明了自己动手丰衣足食这个道理。

升级成6.60系统后，初始时间直接是2008年1月1日，看来的确比较新，但是感觉发短信打字的响应速度没有以前快，看来越新的版本总是越臃肿，呵呵，不管怎么样，我的机器也成了08年的机器了，好好体验一把~






附：凤凰刷机的日志：
Flashing started
Creating product data items list
Product data items list created
Backup not required
Flashing phone
Initializing
Loading image files...
Waiting for USB device. Press phone's power button (if you start from dead terminal)
ROM Boot Drivers loaded. Creating RAW connection
Connecting to device...
Connection opened
Connection opened to BootCode successfully
First wait command failed. Preparing for bootrom waiting loop ...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Sending Wait Request...
Closing connection
Failed to send wait request!
Retrying bootrom connection
Waiting for USB device. Press phone's power button (if you start from dead terminal)
ROM Boot Drivers loaded. Creating RAW connection
Connecting to device...
Connection opened
Connection opened to BootCode successfully
First wait command succeeded.
First wait command failed. Preparing for bootrom waiting loop ...
Flashing Secondary boot code: 14464 Bytes
Sending USB data: 28%
Sending USB data: 57%
Sending USB data: 85%
Sending USB data: 100%
Secondary boot loaded
Skipping USB handshake...
Flashing Update Server Data: 245312 Bytes
Sending USB data: 2%
Sending USB data: 10%
Sending USB data: 20%
Sending USB data: 30%
Sending USB data: 40%
Sending USB data: 50%
Sending USB data: 60%
Sending USB data: 70%
Sending USB data: 80%
Sending USB data: 90%
Sending USB data: 100%
Flashing PASUB TOC Data: 58304 Bytes
Sending USB data: 7%
Sending USB data: 14%
Sending USB data: 21%
Sending USB data: 35%
Sending USB data: 42%
Sending USB data: 56%
Sending USB data: 63%
Sending USB data: 70%
Sending USB data: 84%
Sending USB data: 91%
Sending USB data: 100%
Update server loaded
Waiting for Update Server to boot...
Closing connection
Connecting to device...
Connection opened
Asic CMT: Verifying communication to device...
Asic CMT: UA Protocol 1.0 detected.
Initializing Update Server....
Asic CMT: Verifying communication to device...
Asic CMT: UA Protocol 1.0 detected.
Loading image files...
Loading image files...
Asic CMT: Selecting programming blocks...
Warning: PAPUBKEY already selected
Asic CMT: Start programming 24816 KB...
Asic CMT: Erasing rm217__06.60.mcusw
Asic CMT: Erasing area 1...
Asic CMT: Erasing area 2...
Asic CMT: Erasing area 3...
Asic CMT: Erasing area 4...
Asic CMT: Erasing area 5...
Asic CMT: Erasing area 6...
Asic CMT: Erasing area 7...
Asic CMT: Erasing area 8...
Asic CMT: Erasing area 9...
Asic CMT: Erasing rm217__06.60.ppm_r
Asic CMT: Erasing area 1...
Asic CMT: Erasing rm217__06.60.image_ctv_cn
Asic CMT: Erasing area 1...
Asic CMT: Programming rm217__06.60.mcusw
Asic CMT: Programming  0%
Asic CMT: Programming  2%
Asic CMT: Programming  4%
Asic CMT: Programming  6%
Asic CMT: Programming  8%
Asic CMT: Programming  10%
Asic CMT: Programming  12%
Asic CMT: Programming  14%
Asic CMT: Programming  16%
Asic CMT: Programming  18%
Asic CMT: Programming  20%
Asic CMT: Programming  22%
Asic CMT: Programming  24%
Asic CMT: Programming  26%
Asic CMT: Programming  28%
Asic CMT: Programming  30%
Asic CMT: Programming  32%
Asic CMT: Programming  34%
Asic CMT: Programming  36%
Asic CMT: Programming  38%
Asic CMT: Programming  40%
Asic CMT: Programming  42%
Asic CMT: Programming  44%
Asic CMT: Programming  46%
Asic CMT: Programming  48%
Asic CMT: Programming  50%
Asic CMT: Programming  52%
Asic CMT: Programming  54%
Asic CMT: Programming  56%
Asic CMT: Programming  58%
Asic CMT: Programming rm217__06.60.ppm_r
Asic CMT: Programming  60%
Asic CMT: Programming  62%
Asic CMT: Programming  64%
Asic CMT: Programming  66%
Asic CMT: Programming  68%
Asic CMT: Programming  70%
Asic CMT: Programming  72%
Asic CMT: Programming  74%
Asic CMT: Programming  76%
Asic CMT: Programming  78%
Asic CMT: Programming  80%
Asic CMT: Programming rm217__06.60.image_ctv_cn
Asic CMT: Programming  82%
Asic CMT: Programming  84%
Asic CMT: Programming  86%
Asic CMT: Programming  88%
Asic CMT: Programming  90%
Asic CMT: Programming  92%
Asic CMT: Programming  94%
Asic CMT: Programming  96%
Asic CMT: Programming  98%
Asic CMT: Verifying communication to device...
Waiting for communication response: 25
Waiting for communication response: 24
BB5 USB Flashing succeeded
Phone flashing completed. Waiting for phone to boot up
Bootup successful
Verifying communication to product (before flash finalizing)
Communication verified
Product code changed
Doing factorysets
Factorysets complete
Loading default data to phone
Loading default data to phone
Getting Data Package
Reading product state
Starting backup/restore sub-procedure: data item pre-delay
data item pre-delay
data item pre-delay
Sub-procedure completed: Succeeded., result code: 0
Starting to backup/restore data item: Certificates, version: 1.0
Data Item backup/restore completed: Succeeded., result code: 0
Starting backup/restore sub-procedure: data item post-delay
data item post-delay
data item post-delay
Sub-procedure completed: Succeeded., result code: 0
Starting backup/restore sub-procedure: data item pre-delay
data item pre-delay
data item pre-delay
Sub-procedure completed: Succeeded., result code: 0
Starting to backup/restore data item: EmergencyNumbers, version: 1.0
Data Item backup/restore completed: Succeeded., result code: 0
Starting backup/restore sub-procedure: data item post-delay
data item post-delay
data item post-delay
Sub-procedure completed: Succeeded., result code: 0
Starting backup/restore sub-procedure: data item pre-delay
data item pre-delay
data item pre-delay
Sub-procedure completed: Succeeded., result code: 0
Starting to backup/restore data item: ProductProfile, version: 1.0
Data Item backup/restore completed: Succeeded., result code: 0
Starting backup/restore sub-procedure: data item post-delay
data item post-delay
data item post-delay
Sub-procedure completed: Succeeded., result code: 0
Starting backup/restore sub-procedure: data item pre-delay
data item pre-delay
data item pre-delay
Sub-procedure completed: Succeeded., result code: 0
Starting to backup/restore data item: Contacts, version: S40_FILE2
Data Item backup/restore completed: Succeeded., result code: 0
Starting backup/restore sub-procedure: data item post-delay
data item post-delay
data item post-delay
Sub-procedure completed: Succeeded., result code: 0
Starting backup/restore sub-procedure: data item pre-delay
data item pre-delay
data item pre-delay
Sub-procedure completed: Succeeded., result code: 0
Starting to backup/restore data item: ISSVariantActivator, version: 1.0
Data Item backup/restore completed: Succeeded., result code: 0
Starting backup/restore sub-procedure: data item post-delay
data item post-delay
data item post-delay
Sub-procedure completed: Succeeded., result code: 0
Backup/restore result: 0 out of 5 items were not backed up
Default data loading complete
Stopping all operations, returning phone to default mode
All operations completed
Product flashing succeeded.

[本日志由 Alex 于 2008-12-01 08:54 PM 编辑]
文章来自: 本站原创
引用通告: 查看所有引用 | 我要引用此文章
Tags: