huntdilan,
There is a small favor you could do me, if you don't mind. (It will add to community knowledge.) Remember how I was curious about whether or not QPST alters the /misc partition when you are doing the Cricket mods?
Finding out isn't too hard - I'll provide instructions below. Since you've already used fastboot once, we'll use fastboot again with a capability of the S-OFF bootloader. (Don't worry, it is harmless)
0) Before you begin, make sure there are no PB00IMG.zip files in the toplevel folder of your SD card.
1) Power the phone off
2) Power the phone on by holding Send+End simultanously.
You should see a screen which looks like the HBOOT screen, but instead it will say "FASTBOOT"
3) Plug the phone in to the computer.
You should see the phone screen change from "FASTBOOT" to "FASTBOOT USB"
4) Try the "fastboot devices" command to see if your device is recognized.
5) run the following fastboot command:
C:\sdk\platform-tools>fastboot oem saveprt2sd misc -n miscpart.img -a
You should see output which looks like this:
Code:
... INFOSaveImageToSD partition file name:misc
INFOSaveImageToSD output file name:miscpart.img
INFOCmd5 CMD_TIMEOUT
INFOsdcc_poll_status(): i=12
INFOCmd5 polling status timed out
INFOSD: CMD5 fail, rc=2 ..
INFOSD 2.0
INFOHC card
INFO Searching free data sectors....
INFO [SAVE2SD] 131072 bytes saved.
INFO [SAVE2SD] 262144 bytes saved.
INFO [SAVE2SD] 393216 bytes saved.
INFO [SAVE2SD] 524288 bytes saved.
INFO [SAVE2SD] 655360 bytes saved.
INFO [SAVE2SD] Done.
OKAY [ 4.894s]
finished. total time: 4.895s
(6)
After that, you can restart your phone, either by pulling the battery, or by using the bootloader menus to navigate to HBOOT (Vol Down) -> Recovery (Vol Up) -> Reboot system now
The dumped image file will be at /sdcard/miscpart.img
Now, the dumped (misc partition) image file is binary, and in an undocumented format (possibly the HTC kernel sources might have some clues). Normally, a Unix-like tool called "hexdump" can be used to examine the file.
In mine (a Verizon phone), the Verizon CID ("VZW__001") appears 5 times within the partition - at the very beginning (byte 0), and then every 128 kB offset thereafter:
Code:
$ hexdump -C miscpart.img | grep VZW
00000000 56 5a 57 5f 5f 30 30 31 00 00 00 00 00 00 00 00 |VZW__001........|
00020000 56 5a 57 5f 5f 30 30 31 00 00 00 00 00 00 00 00 |VZW__001........|
00040000 56 5a 57 5f 5f 30 30 31 00 00 00 00 00 00 00 00 |VZW__001........|
00060000 56 5a 57 5f 5f 30 30 31 00 00 00 00 00 00 00 00 |VZW__001........|
00080000 56 5a 57 5f 5f 30 30 31 00 00 00 00 00 00 00 00 |VZW__001........|
I don't know if you are familiar with Unix/Linux tools like "hexdump" or "strings". If you want, we could arrange for you to drop the file someplace - it contains zero private information, so far as I am aware. Either that or you could just look at the first couple of bytes in the file using an editor that tolerates binary files.
Here's what mine looks like - it is almost all null (0) bytes, with string data in it - see the following pastebin:
HTC Droid Eris (Verizon) /misc hexdump - Pastebin.com
It appears that information is replicated every 128 kB (which makes sense because the Eris' flash memory has "eraseblock" size which is 128 kB - if one eraseblock is marked bad, the others are still available.
Anyway, congrats on the phone rescue. I hope you will consider doing the above (harmless) experiment.
eu1
).
isnt there a tool i can flash in recovery that will show me back blocks? seem to remember seeing something on xda(prolly from eu1 
)
