tab

Read more about the article Diamond Problems: flash doesn’t work, stops at 0% Or 5% (invalid model ID)
Hacks / ROM Updates

Diamond Problems: flash doesn’t work, stops at 0% Or 5% (invalid model ID)

htc touch diamond flash update problems invalid idUpdate doesn’t work at all / stops at 1%

Short answer: Your device is needs HardSPL. See links at bottom to get it, read on to understand the difference between Standard/Developer Edition!
Long answer:If your Diamond refuses to be updated completely, you’re probably missing HardSPL. The SPL is the device’s bootloader. It controls what can be flashed and what not. In order to flash anything not signed by HTC or your cell operator, you will need a “custom” version, called HardSPL.
There is two versions of HardSPL, the links are at the bottom, but please continue reading the next section before downloading.

Update stops at 0%

Short answer: You’re running the normal HardSPL and you’re trying to flash an unsigned (not signed by olinex) ROM. You need the developer version which fixes the 0% issue. Link is at the bottom of this post. Read on to understand the difference between Standard/Developer Edition!
Long answer: First you need to understand that there are two definitions of “signed”. HTC and the mobile operators sign ROMs so that the RUU flash utility allows them to be flashed. Usually this is what the word “signed” in the filename means.
Then there is another definition of signed: The developers of HardSPL introduced their own signing process. They want to ensure that people flashing cooked ROMs can rely on a certain quality standard. The normal version of HardSPL will only allow ROMs signed by OliNex to be flashed. If the ROM you are about to flash is signed, it will say so in the thread you got it from. If it isn’t signed, you will need the developer version of HardSPL. That one will allow any ROM to be flashed. Get it at the bottom of this posting.
A note on this: The signing process by olinex makes sure that the ROM you’re about to flash won’t brick your device. It doesn’t mean all other ROMs are necessarily evil.

Update stops at 5%/Invalid Model ID is displayed

Short answer: The model ID hardcoded in the ROM image doesn’t match the ID of your device. Read on for a fix.
Long answer: Don’t Panic. Your Device isn’t broken
Each Diamond Model has it’s own ID. My German MDA Compact IV is a DIAM200. Other models are DIAM150/DIAM300/DIAM100….
Now ROMs might be configured to be flashable to a specific Model ID only, even though technically they would work fine on any Model ID.
In that case the ROM needs to be “reconfigured” – this process works for full ROMs as well as Radios.

  • If you are running a foreign Version of Windows or have Regional Settings other than English US configured, please set them to English U.S. temporarily. Otherwise NBHUtil will not function correctly.
  • First you’ll need OliPro’s NBH Util (0.92 works for the Diamond).
  • Fire it up, switch to “Extract NBH”
  • Select the nbh of the ROM/Radio to be flashed and hit Go
  • Extract the components you need. Radio/Splash/OS. If there’s an SPL in there, you can safely discard/ignore it. You have HardSPL for that.
  • Make note of the Target CID, Version, Language and Chunk Size. FYI the Model ID is the problematic setting here. If it says DIAM10000 and you have a DIAM300 you’re screwed.
  • Switch to the Build NBH tab and select the Diamond as target
  • Note how the Model ID is preset to DIAM*****. The wildcard allows any device
  • Change target CID, Version, Lang & Chunk size to the values you wrote down.
  • Select each saved component under the NBH items
  • Hit Build NBH and save the file as RUU_signed.nbh to a folder of your choice and flash it with the DiamondCustomRUU.exe or ROMUpdateUtility.exe
  • Donate to OliPro because he just made your device useful

(more…)

3 Comments
August 10, 2008
Read more about the article How to use low-res (176*220) titles on QVGA display
Hacks

How to use low-res (176*220) titles on QVGA display

If you have a QVGA Smartphone like the HTC Vox / s710, you know well enough that most existing games and other graphics-based Smartphone apps (Windows Mobile 6 Standard) out there only use a postage-stamp sized screen area. An example of this is PDAMill’s Flux Challenge, which, being designed for the traditional low-res (176*220) Smartphone resolution, only uses part of the available QVGA screen estate: (more…)

0 Comments
July 27, 2008
Hacks

Pocket PC overclock – XScale and OMAP processors

How to overclock your Pocket PC with XScale or OMAP processor. Why would you want to do this? speed of course, up to 50% faster in some cases, but you can also get better battery life if you underclock your Pocket PC when you don’t need all the speed and overclock when you do.

There are many different tools that really dive in to the specific results on Pocket PC models, this how-to is to just get you up and running quickly, literally (to find your processor type go to Settings > Device Information and then Hardware tab).

Use this piece of software at your own risk!!! I am not responsible for any damage caused by this software!!! (more…)

5 Comments
July 16, 2008
Mods

HTC Universal memory upgrade – 128MB

With the help of Mamaich and some others (please add all i have forgotten), the Universal can now have 128 MB of Ram instead of 64 MB. This procedure involves hardware modification! Do it at your own risk! These are the steps that are needed to accomplish the ultimative goal of having 128 MB Ram:

This is an update to the previous information that was here but a little out of date. This procedure is how to upgrade your Universal from 64Mb to 128Mb by removing the two 32Mb M-RAM chips and replacing them with two 64Mb M-RAM chips. This is a complex procedure and requires some specialist equipment to do the job. You will need the following equipment to do the job properly.

  • Hot air re-work station with vacuum pick-up
  • Soldering iron
  • Solder wick
  • BGA re-work station
  • X-Ray equipment
  • Magnified inspection equipment
  • Flux

First thing is to get hold of two of the 64Mb M-RAM chips.
What you need are Infineon HYB25L512160AC -7.5 (2 pcs – 512MBit each)
Chips harvested from the BlueAngel are confirmed to work.
These chips are 54-ball BGA’s (Ball Grid Array) devices, which means that they have little solder balls (0.4 mm) on the bottom and cannot be soldered using a conventional soldering iron. It is also worth mentioning that these chips are moisture sensitive and must be stored in dry conditions preferable in dry-pack sealed packaging. If they get damp there is a chance that they will “Pop-corn” during the soldering process. i.e. the moisture will turn to steam and split open the chips.

(more…)

4 Comments
July 13, 2008
Hacks / Tweaks and Tricks

HTC Touch Diamond performance tweaks and hacks

This is a summary of the proven tweaks taken from the Diamond Tweaks thread. Let’s keep the comments in the Diamond Tweaks thread and keep this one as a list of the actual tweaks only to be an easily accessible summary. Thanks to all who discovered the Tweaks (not mentioning by name because there’s too many to mention and all I did is aggregate).

Warning: Be sure you know what you’re doing and read around the Diamond forums to see where others have run into trouble and with which tweaks on which ROMs. Many people have had to Hard Reset their devices while others have had no problems so read up!
(more…)

1 Comment
July 2, 2008