I've made this little guide so that more users will be able to use HyperTerminal in detecting phone HW problems. Too many users are blaiming SETool for their dead phones.
Case:
Let's say you're only getting a white screen when turning your phone on, or that you're getting the infamous "Can't get packet properties."-error.
Solution:
Either pick a random reason (and that won't do much good for your phone )or do the following to see if the phone itself can provide you with a hint:
1: Open HyperTerminal (Start->Programs->Accessories->Communications).
2: Configure a name for the connection. I've called mine "Debug".
3: Select the proper COM port.
4: Configure baudrate and press "OK".
5: In the "Transfer"-menu, click "Capture Text", then choose a path and name for the log. You will see that the "Capture" indicator has been activated.
6: Attach a powered-off phone (the phone might start charging, this is OK). Give it a minute or two to run selftests, then post the captured text as an attachment if you want an opinion from us.
Code:
FSFLASH: NAND Flash device @ [0x50000000-0x5FFFFFFF] 262144 Kb
FSFLASH: Vendor (0x20): ST
FSFLASH: Device: NAND02GR3B (0x00AA)
............
FSFLASH: Bad block found @ 0x50000000
FSFLASH: Bad block found @ 0x50020000
FSFLASH: Bad block found @ 0x50040000
.................
FSFLASH: Bad block @ 0x500C0000 replaced by 0x501C0000
FSFLASH: Bad block @ 0x500E0000 replaced by 0x501E0000
FSFLASH: Too many bad blocks
If you see this during flashing, it's safe to assume that SETool is not to blaim. (The above error is not related to a case of WSOD, it's only for demonstrational purposes).
Attached Thumbnails
Bookmarks