Develop Bugs

Problems with imate sp3

Well i bought this mobile yesterday, now i tried to instal wm 5.0 on it.
One of the problems is, as you have to unzip a file supercid and use it, how do u actually make it work correctly, it always fails with the alpha tool...
Maybe it's because i have SPL 2.4.33.11, could it be because of that, that those things fail? (If it does, how do i downgrade it, so i can install wm 5.0 on it?)
And something about unlocking ur applications, how the hell do you do that, none of the ways i've tried didn't work... any help would be welcome...
thanks...

Yep you need a 1.XX SPL bootloader. Do a google search you'll find the answer - you're not the first to have this.
Richard

Flashing ROM and Vista (x64), no problem!

I flashed 2 ROM's made by DOPOD and HTC with Vista x64. They both worked without any problem and without replacing any driver (I just use WMDC 6.1 x64).
I tried to flash AX3L_OS_v2.0.8.1 and I got connection 260 problems.
I solved it by copying the RUU_signed.nbh from AX3L into the directory of the RUU_Trinity_DOPODASIA_WWE_3.00.707.17_6275_1.46.00.11_108_Ship (DOPOD WM6 SEA), after that .. flashing isn't a problem.
The ROMUpdateUtility of AX3L has version 3.1.3.2 and of the DOPOD SEA ROM 3.14.4.1. for example, does this make the difference? I don't know, but maybe this helps to improve the installation of the custom ROM's.

Stingray66 said:
I flashed 2 ROM's made by DOPOD and HTC with Vista x64. They both worked without any problem and without replacing any driver (I just use WMDC 6.1 x64).
I tried to flash AX3L_OS_v2.0.8.1 and I got connection 260 problems.
I solved it by copying the RUU_signed.nbh from AX3L into the ditrectory of the RUU_Trinity_DOPODASIA_WWE_3.00.707.17_6275_1.46.00.11_108_Ship (DOPOD WM6 SEA), after that .. flashing isn't a problem.
The ROMUpdateUtility of AX3L has version 3.1.3.2 and of the DOPOD SEA ROM 3.14.4.1. for example, does this make the difference? I don't know, but maybe this helps to improve the installation of the custom ROM's.
Click to expand...
Click to collapse
Thanks for the info Stingray66. I recently re-installed 32bit XP on my machine (now triple boot) so that I could perform ROM updates at home as well as work.
I need XP for other things at the mo, too, so not a problem, maybe this will save me from having to reboot into XP to flash. Thx.

Stingray66 said:
I flashed 2 ROM's made by DOPOD and HTC with Vista x64. They both worked without any problem and without replacing any driver (I just use WMDC 6.1 x64).
I tried to flash AX3L_OS_v2.0.8.1 and I got connection 260 problems.
I solved it by copying the RUU_signed.nbh from AX3L into the ditrectory of the RUU_Trinity_DOPODASIA_WWE_3.00.707.17_6275_1.46.00.11_108_Ship (DOPOD WM6 SEA), after that .. flashing isn't a problem.
The ROMUpdateUtility of AX3L has version 3.1.3.2 and of the DOPOD SEA ROM 3.14.4.1. for example, does this make the difference? I don't know, but maybe this helps to improve the installation of the custom ROM's.
Click to expand...
Click to collapse
very interesting... so now we're just waiting on someone to get this updated RUU to push SSPL before flashing so people don't need CID unlock I guess?

nealed said:
Thanks for the info Stingray66. I recently re-installed 32bit XP on my machine (now triple boot) so that I could perform ROM updates at home as well as work.
Click to expand...
Click to collapse
I flashed at work (XP) too and modified the driver in the Vista (x86) at home with the VistaRUU.zip (contains a ActiveSync 4.5 driver). I don't really like that because when you switch USB-port etc. then you have to replace it again.
I had Vista (x64) installed just before my holidays and flashed the device with the unofficial (beta?) HTC WM6 ROM without a problem. I didn't pay much attention to it 3.5 weeks ago, because the holidays came closer and closer.
BTW That ROM worked fine incl. WLM and TomTom. We did 2400 km on the internal GPS. It's a bit slower with short turns then the SIRFIII, but works ok. The internal GPS does f*ck up the GPRS connection when the GRPS is switching spots for example inside Paris or when you cross borders. (I understand now why HTC disabled the GPS feature in the P3600).
Today I flashed the SEA version also without a problem. I was wondering what AX3L has done the last 4 weeks so I flashed the 2.8.1 but I had the 260 connection problem.
When the device is in the bootloader and when I look under the device manager of Vista, the version of the HTC USB Sync driver is 6.1.6965.0. Unpacking AX3L_OS_v2.0.8.1.zip and running the update utility give a error 260. D810_SEA_WM6_Upgrade_20070709.zip works fine.
Replacing the RUU_signed.nbh is a solution, double checked it.

racerx_ said:
very interesting... so now we're just waiting on someone to get this updated RUU to push SSPL before flashing so people don't need CID unlock I guess?
Click to expand...
Click to collapse
I dunno
I do know that my bootloader has been changed to IPL-1.00 and SPL-9.99.CP, but I can still flash any ROM.

Stingray66 said:
I solved it by copying the RUU_signed.nbh from AX3L into the directory of the RUU_Trinity_DOPODASIA_WWE_3.00.707.17_6275_1.46.00.11_108_Ship (DOPOD WM6 SEA), after that .. flashing isn't a problem.
Click to expand...
Click to collapse
Can anyone confirm this for the Vista (x86) 32Bit?

Stingray66 said:
I dunno
I do know that my bootloader has been changed to IPL-1.00 and SPL-9.99.CP, but I can still flash any ROM.
Click to expand...
Click to collapse
yeah, the ipl must be from the official ROM, and SPL9.99 from AX3L's rom i guess. What i meant was, once someone puts sspl in this new RUU then anyone could flash with it regardless of SPL or CID unlock.. anyway, good find!

Help!! - Can't Upgrade anything on my Diamond

Hello to anyone who can help me...
i am posting this thread after searching this forum for answers to my problem, and i could not find the answers...
I have the Diamond (DIAM100) with Original SPL 1.37.000 and GER Stock Rom installed.
My Upgrade goal is HardSPL 1.38 Signed (Olinex) / DiamondProject V2 GER / radio .05
I try to upgrade SPL, Radio and Rom according to several guides in this forum, but nothing seems to work for me.
I tried using the RUU Program with HardSPL, tried Diamond CustomRUU, tried manual Bootloader access, everytime the Upgrade Software stays at 0% (on the phone also) and after about 5 minutes i get ERROR [262].
Luckily, i haven't bricked my diamond yet, it always came back to life again.
i can confirm, that the device enters bootloader mode, then changes to grey screen with progress bar. But that is all.
Maybe it is a Vista issue, maybe not.
But all i get is ERROR [262]: Update Error
Suggestions, anyone?
Thanks in advance for any serious help...
______________________________________
HTC TD DIAM100
MDA Compact I (Magician, unmodified)
MDA VarioII (Hermes, running Schaps 3.54GER, thanks Schaps great ROM)

I get EXACTLY the same... i've tried everything (except a hammer) to fix it.
I'm running
Rom: 1.37.707.1 wwe
Radio: 1.00.25.03
Proto: 52.26a.25.09h
I'm also using Vista 32
(all fresh out of the HTC box)

http://forum.xda-developers.com/showthread.php?p=2338991

Are you running Vista X64 coz i had the same error in it ..

try to flash it with xp!

udayrulz said:
Are you running Vista X64 coz i had the same error in it ..
Click to expand...
Click to collapse
... Running Vista Ultimate 32bit, but not sure if that will make a difference...
I will try to get hands on XP computer tonite....

You can always try running the RUU update utility in WinXP32 compat mode.

What Hard SPL ar eyou using???.... usually the problem...
you will need Developer edition if the ROM is not signed.

developer edition worked for me on Vista 32. Thanks guys!

OK
I ran a Hard-SPL (from the dev thread) Diamond-OliNex
This completed and did whatever it did and i had to do the basic setup on the phone again.
I have now got the radio ending .06 from this thread this thread and cant get it to work with the OilNex Hard SPL or the 1.34 listed in that thread.
I'm back to square one where Error 262 Update error is occuring.
I'm tring to flash the radio as the O/S i have appears to be running sweet but its having web issues that appear to be DNS/Connection related.
This needs an idiots guide like the other phones have .... 'coz i'm an idiot and I can't do it.

Monty Burns said:
OK
I ran a Hard-SPL (from the dev thread) Diamond-OliNex
This completed and did whatever it did and i had to do the basic setup on the phone again.
I have now got the radio ending .06 from this thread this thread and cant get it to work with the OilNex Hard SPL or the 1.34 listed in that thread.
I'm back to square one where Error 262 Update error is occuring.
I'm tring to flash the radio as the O/S i have appears to be running sweet but its having web issues that appear to be DNS/Connection related.
This needs an idiots guide like the other phones have .... 'coz i'm an idiot and I can't do it.
Click to expand...
Click to collapse
Yeah, but for me the problem still is to get ANY HardSPL on the Diamond in the first place.
I was trying to put HardSPL 1.38_Signed to the phone...
Adwinp: thanks for the advice, but did not work either...
As far as i can tell, this may be a problem with the USB driver from the Windows mobility center software...
I will try on real XP and give you feedback tomorrow.
thanks guys.

Doctor_Who said:
...
I was trying to put HardSPL 1.38_Signed to the phone...
...
Click to expand...
Click to collapse
The developer edition i.e. unsigned worked for me.
I am currently going through the stages in the wiki VERY closely. Dont know if they will work :/

Doctor_Who said:
Hello to anyone who can help me...
i am posting this thread after searching this forum for answers to my problem, and i could not find the answers...
I have the Diamond (DIAM100) with Original SPL 1.37.000 and GER Stock Rom installed.
My Upgrade goal is HardSPL 1.38 Signed (Olinex) / DiamondProject V2 GER / radio .05
I try to upgrade SPL, Radio and Rom according to several guides in this forum, but nothing seems to work for me.
I tried using the RUU Program with HardSPL, tried Diamond CustomRUU, tried manual Bootloader access, everytime the Upgrade Software stays at 0% (on the phone also) and after about 5 minutes i get ERROR [262].
Luckily, i haven't bricked my diamond yet, it always came back to life again.
i can confirm, that the device enters bootloader mode, then changes to grey screen with progress bar. But that is all.
Maybe it is a Vista issue, maybe not.
But all i get is ERROR [262]: Update Error
Suggestions, anyone?
Thanks in advance for any serious help...
______________________________________
HTC TD DIAM100
MDA Compact I (Magician, unmodified)
MDA VarioII (Hermes, running Schaps 3.54GER, thanks Schaps great ROM)
Click to expand...
Click to collapse
I had the exact same problems. I tried every possible combination of Hard SPL and ROMs. Here is what worked for me in the end (no problems since):
1. install newest .Net 3.5 on windows PC (don't know if this has anything to do with my problems but after installing everything started working fine)
2. install Unsigned HardSPL (developer edition): http://forum.xda-developers.com/showthread.php?t=400950
3. install chosen ROM / Radio ROM with RUU (Rom Updater Utility): http://forum.xda-developers.com/showthread.php?t=396073
After flashing a ROM the device makes a hard reset so you should backup your data first! http://forum.xda-developers.com/showthread.php?t=299705
good luck!

Finally it worked, also thanks to all who replied in this thread.
So i like to share my experience in this:
1. first i downloaded all SPL and Radio i could find, then i looked for GER language Rom. Quickly decided for DPT V2.
2. First attempt to flash failed completely on a Vista PC (32 Bit Ultimate)
3. Back home, moved all the downloaded files to my XP SP2 PC..
4. Noticed: DiamondCustomRUU would not start in XP, got error message saying "... could not be initialized", so i tried the standard RUU instead, with the shortcut of manually putting the PDA into Bootloader mode...
5. Sucessfully flashed HardSPL 1.38 on the Diamond, and the device rebooted with Hard reset.
6. Next i tried to upgrade Radio to .05 Version... Failed, stuck a 0%
7. Changed SPL to 1.40 (Unsigned), now the Radio could be flashed. Seems that Radio Files are Unsigned?
8. Flashed DPT V2. Success.
But still wondered about the unsigned Radio file...
Again, thank you all
-------------

diamond won't upgrade to 1.93 hspl

I have a gsm diamond (from t-mobile uk) and have flashed it to 1.34 hspl to use the new 25.16 radio and dutty's v3.1 both are working fine however I can't *upgrade* (i know it's not an upgrade per se) to hspl 1.93. it's stuck on 1.34.
using customruu it goes through the normal motions and on screen shows it to 100% then restarts etc, but after i check by going into the bootloader it hasn't updated. I have looked about and search for some time now and don't see anyone expericencing quite the same thing.
any ideas??

paulmurphy777 said:
I have a gsm diamond (from t-mobile uk) and have flashed it to 1.34 hspl to use the new 25.16 radio and dutty's v3.1 both are working fine however I can't *upgrade* (i know it's not an upgrade per se) to hspl 1.93. it's stuck on 1.34.
using customruu it goes through the normal motions and on screen shows it to 100% then restarts etc, but after i check by going into the bootloader it hasn't updated. I have looked about and search for some time now and don't see anyone expericencing quite the same thing.
any ideas??
Click to expand...
Click to collapse
...unfortunately no ideas, just the same problem described here already: http://forum.xda-developers.com/showthread.php?p=2927161#post2927161

paulmurphy777 said:
I have a gsm diamond (from t-mobile uk) and have flashed it to 1.34 hspl to use the new 25.16 radio and dutty's v3.1 both are working fine however I can't *upgrade* (i know it's not an upgrade per se) to hspl 1.93. it's stuck on 1.34.
using customruu it goes through the normal motions and on screen shows it to 100% then restarts etc, but after i check by going into the bootloader it hasn't updated. I have looked about and search for some time now and don't see anyone expericencing quite the same thing.
any ideas??
Click to expand...
Click to collapse
I have the exact same issue... I tired updating it from 1.24 to 1.93 and it restarted like it updated it. But when I go into boot loader its still got the old hardspl.
Does anyone know why??
I have tried searching around for a solution but no luck

I'm no noob and i've flashed 100's of times across many fones and unbricked a few with some careful reading but this seems very odd and stupidly simple. No idea what i'm missing.... only thing i can think to try is to flash from internal storage, but i would think this unwise with the hardspl as I thought hardspl would control access to the internal storage like some sort of bios perhaps?!

Same here
Hey guys,
Does anyone knows what is the resolution for this? I having the same problem as well.

Hi guys!
HSPL blocks write attempts to the SPL-part of the nand! You need to run SSPL from windows mobile and then flash the HSPL-Version you want. This is pretty much the only way to override that write-protection!
cheers
chris

gladiac said:
Hi guys!
HSPL blocks write attempts to the SPL-part of the nand! You need to run SSPL from windows mobile and then flash the HSPL-Version you want. This is pretty much the only way to override that write-protection!
cheers
chris
Click to expand...
Click to collapse
i have almost same problem but the only difference that my Diamond don't have hardspl on it and whenever i try to flash any hardspl phone stops at 0% and stays there for a long time....I want to change my Diamonds language...So can anyone suggest me solution.....I have already posted here on forum but no answer yet!
http://forum.xda-developers.com/showthread.php?t=749664
Another little question that how i can flash hardspl via internal storage and where its root???Root is the device path which we seen as drive in computer when we use mass storage or any other?

gladiac said:
Hi guys!
HSPL blocks write attempts to the SPL-part of the nand! You need to run SSPL from windows mobile and then flash the HSPL-Version you want. This is pretty much the only way to override that write-protection!
cheers
chris
Click to expand...
Click to collapse
Thank you. used this and it worked

Hi everybody,
got yesterday another diamond, after mine died some time ago. It has 193 spl and I cannot upgrade to olinex spl. It runs through everything, but upon reboot it still has the original 193 spl. Any ideas? I really need to flash, mine speaks Dutch and I want it in English. Please help. Kind regards. Ben

Flashing can't start, and cant't find solution the after searching the forum

So as you can figure out from the thread title I have a problem flashing my htc diamond.
I have installed a HardSPL version 1.30 OliNex, I can confirm that becouse on the three color screen there is a text saying "1.30 OliNex".
I still have the original ROM that comes with the phone when I bought it, so this meant to be my first flashing.
I want to flash the phone with this rom http://forum.xda-developers.com/showthread.php?t=593678 it is a WM 6.5 based ROM.
Because in the ROM package there wasn't a ROMUpdateUtility.exe I used it from other ROM package.
Connected via ActiveSync and followed the wizard. The phone reset and there came a gray screen with a progress bar. Now both progress bars on the phone and on the PC screen remain 0% and after a wile RUU finished with 262 ERROR Connection error, see the attached picture.
After that I tried to flash it from Internal Storage. A followed the steps according the procedure, and after the three colored screen it came the gray screen with "Loading..." message. I waited for almost 30 minutes and nothing happened.
What seems to be the problem?
I assumed about firewall disabling the connection. But I turned off the firewall and again the same story.
Then somewhere I found that there is incompatibility with the RUU and HardSPL version, but tried to flash with the same RUU that I used when I was installing HardSPL.
Then I tough that the problem is about flashing unsigned ROM on a signed HSPL, but it is not that the ROM is signed.
I am afraid to use MTTY so I don't brick my phone, because this is my first time flashing a Diamond.
I'm confused What seems to be the problem?
Any help can be welcomed.
Could this be indication of a hardware problem? When waiting for the "Loading..." message disappear the back cover warms a little.
Thanks.

1. Did you use the RUU from my thread?
2. NEVER USE AN H-SPL RUU TO FLASH ANYTHING OTHER THAN H-SPL!
3. is this a CMDA phone. IE, what network are you on?

Well no I didn't use the RUU from your thread, I've used a RUU from other ROM package.
This is not a CDMA phone I'm on T-Mobile Macedonia network. And the phone looks like this
On other Macedonian forum they told me it is a hardware problem. Can this be true?
So what do you think about my problem?

Well no I didn't use the RUU from your thread, I've used a RUU from other ROM package.
This is not a CDMA phone I'm on T-Mobile Macedonia network. And the phone looks like this
On other Macedonian forum they told me it is a hardware problem. Can this be true?
So what do you think about my problem?
EDIT: I did tried the RUU you recommended in your thread but it's the same.
I think it is in the PDA.

Configure active sync, and uncheck "allow usb connection" and try again.
For updating from internal storage you must have to copy the rom to the root of internal storage with a special name, ""diamimg.nbh"

Hmmm..
What he said... and...
Should have used one of the earlier SPLs. you only need to use the latest one if you are having problems with the older versions. I have the same diamond and used an early SPL.
Upgrade the radio rom first and go with a rom that's version 6.1 not 6.5 as most 6.5 roms now pack the Sense application.. (IMO Non-Sense, Senseless (Not enought ram or responsiveness))
Old roms here
http://forum.xda-developers.com/showthread.php?t=470757
Give olinex some cash for his Diamond Unlocker as this is the surefire way to fix it.

johnyboy_ said:
Configure active sync, and uncheck "allow usb connection" and try again.
For updating from internal storage you must have to copy the rom to the root of internal storage with a special name, ""diamimg.nbh"
Click to expand...
Click to collapse
The connection between PC and PDA is made, because as I said there is a progress bar on the phone screen too.
djfuego said:
What he said... and...
Should have used one of the earlier SPLs. you only need to use the latest one if you are having problems with the older versions. I have the same diamond and used an early SPL.
Upgrade the radio rom first and go with a rom that's version 6.1 not 6.5 as most 6.5 roms now pack the Sense application.. (IMO Non-Sense, Senseless (Not enought ram or responsiveness))
Old roms here
http://forum.xda-developers.com/showthread.php?t=470757
Give olinex some cash for his Diamond Unlocker as this is the surefire way to fix it.
Click to expand...
Click to collapse
As I understand you, you are saying to install later version of Hard SPL right?
So to install a new version of Hard SPL I just need to do the same procedure as the first time, or I have to uninstall the previous one?
And please help me which version of Hard SPL is safest to install? I'm afraid of the developer versions or maybe they aren't so scary
Are you a 100% positive it is the HardSPL?

djandreski said:
And please help me which version of Hard SPL is safest to install? I'm afraid of the developer versions or maybe they aren't so scary
Are you a 100% positive it is the HardSPL?
Click to expand...
Click to collapse
Presuming from your post, you are using a signed Olinex SPL, i doubt that the rom has been signed be OliNex, the only difference with Dev is you can flash any Rom, flash the Dev one from my thread, nothing to be afraid of
Good Luck
Badwolve1

What are the steps of installing new SPL?
Do I just need to do the same procedure as the first time, or I have to uninstall the previous one(somehow)?
UPDATE: I did it, I successfully flashed my Diamond PDA! It seams that the problem was in the SPL I installed 1.40 OliNex Unsigned and it flashed like a charm. Thanks guys for the help. Now this thread can be closed, or do I have to close it myself.

Great!
Glad it all worked out