Develop Bugs

Using Windows Vista

I just post this thread in order to help others which are having the same problem as I am and to avoid looking arround on all the posts for this answer.
I'm so happy that I've not yet test this procedure wanted to share with you ASAP.
Thanks pvdhelm
pvdhelm said:
Follow these instructions and your vista problem is over.
I used this guide and it works for my artemis p3300 phone!
Please try downloading the latest WMDC first before attempting anything in this section of the guides. you will find the latest version HERE .
To follow this guide please make sure you have a copy of WinRAR installed, I will refer to the Windows Mobile Device Centre as the WMDC for ease of reading. If you do not have the WMDC installed please go here to install it first.
One problem with windows VISTA is that it uses the new "Windows Mobile Device Centre" and not activesync which we are used to, thus our standard RUU programs will not upgrade our Hermes devices as in windows XP. This guide will show you how to configure VISTA to work just the same as XP with our RUU programs.
For this guide firstly you need to download the new drivers:
Drivers for Windows Vista x32
Drivers for Windows Vista x64
Please note the x64 drivers are unsigned so to use them successfully you must disable driver signing.
Extract the contents to a folder on your desktop, call this folder "AS_DRIVERS". It contains the drivers from activesync which we will use instead of the native VISTA WMDC drivers when the device is in bootloader.
Now you must enter the bootloader on your device, to do this press and hold both the side ok button and the power button then put your stylus into the hole on the bottom of the device, your device will reset and show the red blue green bootloader screen. LEAVE THE DEVICE IN BOOTLOADER MODE and connect it using the USB cable to your VISTA PC.
Now navigate into the WMDC (Start>All Programs>Windows Mobile Device Center) and click on the "connection settings" menu icon
In the connection settings menu untick "allow USB connections" then press OK.
Now exit the WMDC and return to the desktop, go into the start menu and type "Services", this will take you into the local services dialogue and show a list of all services either running or registered with your pc.
Scroll down the list and make sure these services are present:
Windows Mobile-based connectivity
Windows Mobile 2003-based connectivity
If these services are not started then double click each one and set them to Automatic start by clicking the "startup-type" drop-down menu and selecting automatic then click the start button in the same window, apply the setting by pressing OK. Now return back to the desktop again.
Go into the start menu and type "Device Manager" then run, this will take you into the device manager. Click the "+" symbol next to "Mobile Devices" and double click on "HTC USB Sync".
This will bring up the properties of the currently connected device (the hermes in bootloader).
Go to the "Driver" tab and click "Update Driver".
Click "Browse My Computer for Driver Software".
Select "Let me pick from a list...."
Click the "Have Disk" button.
Click "Browse" and navigate to the AS_DRIVERS folder we created earlier.
Vista x32 users select the file "wceusbsh.inf"
Vista x64 users select the file "wceusbshx64.inf"
Then click Open.
click next and the driver will be installed (wait a moment).
Press close and escape back to the desktop now.
Now we must stop the WMDC process, start the task manager by pressing Ctrl+Shift+Escape.
click the WMDC line and click "End Process". In the confirmation window, again press End Process.
Now re-enter the WMDC and re-enable USB connections (click connection settings and tick the box "enable USB connections").
Your RUU programs for HardSPL/Radios/WM6 ROMs should now run as desired once you are synced with WMDC. Since we have updated the driver which vista uses when the device is in bootloader mode.
NOTE:: This technique is still in testing so if you have any issues please post in the official thread. Until we find another way to get RUU working with vista you may need to revert back to XP for upgrading your Artemis.
Click to expand...
Click to collapse
Just test it without any problem. I confirm the feasability of this procedure.
It rocks!
Always restart after before trying. It has worked with me.

Ha, Well I have tested and all works well, after this I've flashed USPL and B&B 3.7 ROM with no difficulty.

Now if I could only figure out why Mobile device Center will not install properly on my Vista Ultimate that I just 'upgraded' to today. It connected once, ran the sync but did not back up the contacts on my phone to outlook, and now on subsequent tries, the program wont open because of 'unknown problems'.
Maybe it's a sign to roll back to XP.

uninstall wmdc and then re-install. I had this error at first but fixed now.

Shand359 said:
uninstall wmdc and then re-install. I had this error at first but fixed now.
Click to expand...
Click to collapse
I had a feeling, I did that procedure once already with redundant results....but then again, half of my peripherals such as DVD-ROM, or wireless card didn't work, but then miraculously started working just as I was about to teach my laptop how to fly.
I will keep trying, thank you.

itschase said:
I had a feeling, I did that procedure once already with redundant results....but then again, half of my peripherals such as DVD-ROM, or wireless card didn't work, but then miraculously started working just as I was about to teach my laptop how to fly.
I will keep trying, thank you.
Click to expand...
Click to collapse
I'm not sure if that is the problem, but did you tried after restart vista?
When I made the procedure it was not working and then tried to restart and it was perfect.

Bluetooth sync works fine, but USB won't load driver. WM5 OEM, so no bootloader on my 8525. Will this solve my USB problem?

Hmm .. tried to follow the process above and Vista told me I already had the most recent version of the driver .. strange huh ?

For French :
http://www.forummobiles.com/index.php?showtopic=136003&hl=nuls

scratch that .. i missed a bit

Shand359 said:
uninstall wmdc and then re-install. I had this error at first but fixed now.
Click to expand...
Click to collapse
Agreed. Some 'versions' of windows Vista have WMDC built in, it is no good, uninstall WMDC and download the version from MS web site. Once installed run Windows Update.

owencutajar said:
Hmm .. tried to follow the process above and Vista told me I already had the most recent version of the driver .. strange huh ?
Click to expand...
Click to collapse
I had this issue too, uninstall vista drivers first, then install those from XP.

I followed these directions to update my Himalaya/Alpine-like i-mate PDA2 with disappointing results -- at first. WMDC claimed there was an error and I could not get it to respond. I flounced away and pouted for a little bit, and when I came back decided the only thing I could think of to change now before re-installing WMDC altogether was to roll back the driver for the mobile devices (in device manager) and WA-LA! Pouting works! I am now able to sync and Klaus (the i-mate) plays nice with Bob (PC)... ah, household bliss!
Thanks!

i still cannot get my laptop to see the artemis when it is bootloader mode - i have the XP driver on!!!!

I would love to try it, but does anybody have a german manual, or a translation program that translates Windows English into Windows German?

htc s620 stuck at startup

Hi,
My S620 is stuck at the startup screen showing just the htc logo and won't go any further. Anyone know how I can fix this?

Try to remove the battery, the SIM card and the memory card. Just insert the battery and try again. This worked for me.

It does not work:-( Anyone know how to put directly into bootloader mode?

Or anyone has any other tip?

bump anyone have an idea why mine stopps at the htc screen at start up?

Hard reset?
Did you tried hard-reset? You need at least one previous sync sesion, or you will loose everything stored on the device.

I tried that. Not working;-(

It does not react at keyboard pressure at all;-(

surfer said:
Hi,
My S620 is stuck at the startup screen showing just the htc logo and won't go any further. Anyone know how I can fix this?
Click to expand...
Click to collapse
which rom did you use and have you unlocked it with Imeicheck ?

jhwo99 said:
which rom did you use and have you unlocked it with Imeicheck ?
Click to expand...
Click to collapse
The WM6 rom and it was unlocked through imeicheck. Any ideas?

surfer said:
The WM6 rom and it was unlocked through imeicheck. Any ideas?
Click to expand...
Click to collapse
I had a similar problem and Imeicheck helped me out.
"Plan B" worked for me.
I hope this will help you.
A) flashing ANY new ROM as CROSS-MODEL-ID update
B) Fix the "Data crashes"
In case you have problems please indicate the step letter/number which is not clear / not working for you.
Just do EVERYTHING EXCAT STEP BY STEP and everything will work.
---------
A)
Please do it EXACT step by step like described now and it will work (it is ESSENTIAL that you do it EXACT STEP BY STEP)
0) turn off antivirus/firewall/everything else running in background
1) start phone in windows, connect active sync (green circle in system tray of your pc)
2) start the unlocker (phone screen will turn white, active sync will disconnect, THIS IS NORMAL)
3) when asked for KEY-FILE or COMM ERROR#1 comes up WAIT 2 MINUTES (DON'T TOUCH ANYTHING)
4) DO NOT TOUCH PHONE AT ALL for ALL the next steps!!!
5) remove USB cable
6) close the unlocker on PC
7) reconnect USB cable
8) unpack the "RUU_Excalibur_TMO_US_1.20.531.1_4.1.13.34_02.79.90_Test.exe"
(right click on the .exe and select "Winzip->Unzip to folder..."
9) in the extracted folder you will find a file called like "RUU_signed.nbh" (.NBH), open it with HEX EDITOR (e.g. HexWorkshop) and locate the string like "EXCA20000" near the beginning of the file. Change it to "EXCA****" (all without the quotes, overwrite the DIGITS with STARS)
10) in the extracted folder you will find a file called like "RUU_Update.exe", open it with HEX EDITOR and SEARCH the string "BsaD5SeoA" and OVERWRITE it with "IMEICHECK" (all without the quotes)
11) start the just edited RUU_Update.exe now and make the ROM update (screen of phone will stay white ALL THE TIME, THIS IS NORMAL)
12) wait till update is complete and phone will start with the new ROM
13) To fix the "Data Crashes" problem just make a COMPLETE run of the unlocker (see B) ) and you are done.
---------
B) To fix the "Data crashes" you only have to make a COMPLETE run of the unlocker.
Please do it EXACT step by step like described now and it will work (it is ESSENTIAL that you do it EXACT STEP BY STEP)
0) turn off antivirus/firewall/everything else running in background
1) start phone in windows, connect active sync (green circle in system tray of your pc)
2) start the unlocker (phone screen will turn white, active sync will disconnect, THIS IS NORMAL)
3) when you get COMM ERROR #1 WAIT 2 MINUTES (DON'T TOUCH ANYTHING)
4) DO NOT TOUCH PHONE AT ALL for ALL the next steps!!!
5) remove USB cable
6) close the unlocker on PC
7) reconnect USB cable
8) start unlocker again and now it will complete the unlock
9) at next start the "Data Crashes" will be away.

surfer said:
The WM6 rom and it was unlocked through imeicheck. Any ideas?
Click to expand...
Click to collapse
Is your problem solved ?

jhwo99 said:
Is your problem solved ?
Click to expand...
Click to collapse
I can acess the bootloader now. So all i've to do is to find an official WM5 rom to try and flash back again. Any ideas?

surfer said:
I can acess the bootloader now. So all i've to do is to find an official WM5 rom to try and flash back again. Any ideas?
Click to expand...
Click to collapse
You van find the WM5 rom in this forum, but i suggest to install the Russian HTC rom. This works great (for me).
I work with all the options in the telephone, the whole day. Without any problems !

s 621 stuck on wm6
hello
Need Help pls! my new htc dash has stucked on the wm6 logo, active sync does not recognize the phone . it happened after ive installed on phone language extender
could any1 help pls...?
thnks

Ok this is what you do, hold down the camera button located to the right of the space bar for like 10 seconds, then while still holding it own plug the USB in and you should see the menu come up with three colors. This is where you load your original ROM and if its T Mobile you can get the rom from the website.

s 621 stuck on wm6
thank you very much for ur reply. i got the 3 color on screen. pls advise meaning of "flash..." pls note im not a t mobile member
thank u so much for helping

Oh ok I can get that rom for you, well flash means to install. Let me ask you one quick thing is your phone tmobile branded. Like does it have the tmobile logo on it or not.

s 621 stuck on wm6
nop
the phone aint branded
i actually got wm6 and when i try to install it the black window says there s no device connected..

Um... Well use this file to reflash it okay. Make sure that the tri-colored screen is on when you try to install the rom (reflash means install ok)
http://rapidshare.com/files/7886560...S_1.33.422.1_4.1.13.51_03.07.90_Ship.exe.html

reanimate universal, no splash, no connection to pc with cable

Hey guys
I know there's a post nearly the same like this one allready, but i'd like to have a "how to reanimate" and not have the ppl to read 300 posts. The idiot i am i upgraded MDA with USB Hub and disconnected by accident while upgrading....
So here the steps to do
1. get out SD card and SIM
2.try to fix it with another flash, if doesn't work, step 3 (if computer reconizes your universal with active sync DON'T CONTINUE THIS TUTORIAL)
3.try mtty.exe (open active sync, uncheck usb conn, close active sync, terminate wcsmm.exe in task mngr)
4.now put universal in cradle, open mtty.exe
5.where Port1 is, change to usb, connect
6. (don't copy/paste) press "return", enter "set 14 0", press "return"
7.enter "task 28", press "return"
8.enter "task 28 55aa", press "return"
9.close program, disconnect from cradle
10.backlight+power+reset connect to the cradle
11. use ORIGINAL software to update RADIO only, it should work now, or try RUU_TMO_Radio_11200_GER_20060616.exe (http://rapidshare.com/files/97208659/RUU_TMO_Radio_11200_GER_20060616.exe.html)
http://festplatte.aon.at/a/filemanager.get/1710719/RUU_TMO_Radio_11200_GER_20060616.exe
12. upgrade With full version, radio, bootloader and winCE
13. hold both "-" "-"-keys and "reset"
14.WAIt, the screen looks black, maybe it takes 5 minutes, but it worked again =)))))
I did it, after 3 days of trying, thats why i'm so happy =)))
hope it will work same as it worked

Extended ROM Update Error 113

~~~~~~~~~~~~~~~~~~~~
**** PROBLEM SOLVED ****
~~~~~~~~~~~~~~~~~~~~
Hi everybody,
I'm using german T-mobile MDApro with 64MB. I had one of your WM6 running. Good work btw! I only had some issues with WLAN an SDHC so I wanted to update.
And now I am in big trouble. I flashed one of your new WM6.1 as I usually did for the last 12 times when everything worked just fine. Bit this time I had error 113 during Extended ROM Udate. I tried and tried and always hat errors during the update process. And then I found out that I connected the device via USB-Hub!!! I know that it is not recommended. So I removed the hub connected the device to PC, but the error will remain the same for all updates and different ROMs.
There is no way to get the unit running again. Always the same: The fist part of update (CE) works fine, but the second part (extendes ROM) don't start. After a few seconds I get "error 113", sometimes I saw "error 114".
When I do a reset to factory defaults the screen remains completely blank (black)
After reset the device shows serial, connecting it to USB it shows USB. I have to do once or twice the [light + on/off + reset] to get it in this mode. Activesync 4.5 is running but doesn't connect or recognize the device.
Any suggestions?
Thank you so much!

some more details...
Bootloader v1.01 start after [power+light+reset]
- serial without USB cable
- usb when cabel is inserted (direct to PC)
MTTY starts and shows USB>
- anything I enter nothing happens on screen. I tried task 28 55aa, screen only shows "usb... v1.01"
Trying to flash original ROM:
- ROM Build starts from 0-100%
- when it tries to store Extended ROM nothing happens until Error 113
- the screen is blank this time (no "usb")
- when I unplug usb-cable screen returns to "serial"
- when I replug usb-cable screen shows "usb" again
BTW: the charge-LED is always off when connected to usb
maybe this helps some of you experts to have an idea?
Did I totally screw up my MDA??

Solution to the Problem
Hi everybody,
I found the solution here in the Forum. So please forgive my double posting
w3rti wrote in his post http://forum.xda-developers.com/showthread.php?t=374564:
So here the steps to do
1. get out SD card and SIM
2.try to fix it with another flash, if doesn't work, step 3 (if computer reconizes your universal with active sync DON'T CONTINUE THIS TUTORIAL)
3.try mtty.exe (open active sync, uncheck usb conn, close active sync, terminate wcsmm.exe in task mngr)
4.now put universal in cradle, open mtty.exe
5.where Port1 is, change to usb, connect
6. (don't copy/paste) press "return", enter "set 14 0", press "return"
7.enter "task 28", press "return"
8.enter "task 28 55aa", press "return"
9.close program, disconnect from cradle
10.backlight+power+reset connect to the cradle
11. use ORIGINAL software to update RADIO only, it should work now, or try RUU_TMO_Radio_11200_GER_20060616.exe (http://rapidshare.com/files/97208659...60616.exe.html)
http://festplatte.aon.at/a/filemanag...R_20060616.exe
12. upgrade With full version, radio, bootloader and winCE
13. hold both "-" "-"-keys and "reset"
14.WAIt, the screen looks black, maybe it takes 5 minutes, but it worked again =)))))
Click to expand...
Click to collapse
I tried the same strings with mtty, but the key was to type it and NOT to copy/paste it. And this time it worked!
And at the end of step 11 there is no feedback on the screen of the pda (blank screen, nothing). So I waited for 10 minutes and gave him a [power-light-reset]
After that my favorite ROM-version did flash all throw the whole process.
Thank you guys

Yehuuuuuuuuuu Oleyyyyyyyyy Jasjarım çalışıyor
I love you
i love you
i love you
i love you
thanks
thanks
thanks
thanks
thanks
thanks
thanks
thanks
thanks
thanks
thanks
thanks
thanks
................................................................................................................................................................................................................

[REF] The DEFINITIVE MTTY Thread!! - Diamond Edition

This is a friendly warning to people who are new to the site/new to the thread.
There has been a LOT of unnecessary posts recently from people who cannot be bothered searching starting HERE ON PAGE 59 POST 581 onwards.
I will simply not reply or reply with "Search". Why should I help when people cannot be bothered ATTEMPTING to help themselves?
Also anyone thinking of asking either of the following questions:
1: "After task 29, I get this output in MTTY: Total Bad Block in CE: x"
2: "After task 29, I get this output in MTTY:
ERASE block xxx FAIL !!!
ERASE block xxx FAIL !!!"
(where x is a random number)
This has been asked 100+ times in this thread so this is the final time I will answer:
IT MEANS NOTHING..NADA..ZIP! I have not experienced ANY problem with this output...Please stop asking!
There is a LOT of information in this thread. All you need is the first 4 posts or the search button OR if it is a GENUINE problem post it and I will help!
​
------------------------------------------------------------
Hi,
Over the last couple of weeks, as all of us flashing junkies are continuously flashing devices there has been an increase in "Strange Problems" which to all intents and purposes are just “clog ups” and “bad flashes”
As we all know MTTY is the key here, but I can say from personal experience that this small piece of software is a MASSIVE pain in the ass to get working, i must have tried 15-20 different “recommended” procedures to get it work and all failed.
But I managed to find a failsafe method of getting MTTY working on Vista AND Windows 7, also x86 AND x64!! (I have all 4 windows installations and the methods detailed below worked on all)
NOTE: WORKS WITHOUT DRIVER INSTALL ON XP
If for some reason you cannot got this to work on XP do the following: (Thanks kgerry!!)
kgerry said:
Hi,
if you run XP and you have Problems to connect to USB try following:
1. Launch ActiveSync on PC
2. Go to connection settings
3. Uncheck the Allow USB Connection
4. bring the device to bootloader.
5. Now, run mtty ...
... try again to switch from COM1 to USB and follow the instructions of perfect post 3
Hope it helps ... Kgerry
Click to expand...
Click to collapse
Here is how this thread works:
Post 1: Description
Post 2: Driver Installation
Post 3: MTTY Instructions For FLASHING FROM INTERNAL STORAGE
Post 4: MTTY Instructions For FLASHING FROM YOU SYSTEM
THANKS to:
Reb0rn - for pointing me to the light!
l2tp - for the images
lunasea - for providing me with working drivers
and of course to anyone else I forgot.
I hope this helps people!!
MG

Driver Installation
Pre-Cursor To Driver Installation – FOR EVERYONE (x64/x86 Vista/Win 7)
This will remove the need for users, x64 in particular, to use “Unsigned Drivers.” Also since in Vista SP2 (x64 & x86) they removed the “F8” options Completely!
Files Needed:
Driver Signature Enforcement Overrider
Remove Watermark V0.8
1: Run the Driver Signature Enforcement Overrider and select “ENABLE TEST MODE” and Press Next
2: There will be a warning to REBOOT, Press “OK”
3: Go Back to Driver Signature Enforcement Overrider Select “Exit” then Click “Next”
4: Run the “Remove Watermark V0.8” for you OS type (x64 or x84)
5: In the Command Window type “Y” and wait for the process to complete
6: Once complete REBOOT your system and begin the driver install
NOTE: If you DO NOT complete the above, some users will need to press "F8" During Bootup - (ANOTHER NOTE FOR x64 USERS, EVERY TIME YOU NEED TO USE MTTY YOU MUST REBOOT YOUR COMPUTER, HIT F8 AND SELECT: "START WINDOWS WITHOUT DIGITALLY SIGNED DRIVER CHECK")
For Info See Post Below:
Reb0rn said:
I must just say that u might have to watch the x64bit drivers if they are digitally signed... Cuz neither Vista 64 nor Windows 7 64 will let u load or start those drivers if they are not digitally signed.
IF that the case and if u have installed the driver but it says that it has stopped it due to the driver not been Digitally signed u have to start windows vista/7 in "ignore digitally signed drivers" mode.
When u start the computer, keep hitting F8 and it will prompt you if u want to start in safe mode bla bla and in the bottom of that list there is an option that goes something like this:
Start Windows without Digitally signed Driver Check... or sumthing like that...
This is only if u have problems with the x64 driver... like i did...
BTW... u made a beautiful how-to man. Great job!
Click to expand...
Click to collapse
-----------------------------------------------------------------------
Big thanks to maybeme for providing a host for the images!!
1: Download the relevant drivers for your system attached to this post: these work for both Vista and Win7, all you have to choose is x86 or x64
EDIT: It has been found that with different versions of Windows 7 x64 need different Active Sync Drivers... If you are using Windows x64 please try x64 AS Drivers Win 7 Tested & Working.zip FIRST!!!
2: Connect Device to PC via Active Sync, Once Connected Uncheck USB Connections,DISCONNECT DEVICE then Reboot Computer
3: Bring device into bootloader (Reset + Hold Vol Down), This will show the Red, Blue, Green screen showing "Serial" - Once Computer booted, connect device in bootloader mode to USB, the word "Serial" will change to "USB"
4: Go to "Control Panel -> System -> Device Manager" and select Microsoft Usb Sync in Mobile Devices section (NOTE: This MAY say HTC USB Sync but as long as you select your device!!):
5: Right Click and Select "Properties" then go to Driver tab, then Select "Update Driver"
6: Choose to "Browse Computer For Driver" (the second option):
7: Select "Let Me Pick From A List...." (the second option):
8: Click "Have Disk":
9: Select the folder with downloaded driver From Step 1 and select "wceusbsh.inf" (this is the same file for x86 & x64):
10: You will get back to previous screen, then click Install
10a: WINDOWS 7 ONLY - The Below Warning will appear, Select "Install anyway":
11: The drivers will be successfully installed:
12: When you get back to "Driver Properties" check driver version. If the "Driver Date" has changed from 2nd step (2003 instead of 2007), the installation has been a success:
13: Lastly leave the device connected and in "Bootloader" and reboot you system. Upon Rebooting an "Unknown Device" is installed, this is your HTC device.
Now the Active Sync Drivers are Installed

MTTY - Flashing From INTERNAL STORAGE
Follow this procedure for FLASHING YOUR ROM FROM INTERNAL STORAGE AFTER MTTY
Before you start grab: mtty1.42.zip
AND ENSURE YOU HAVE HARD-SPL ON YOU DEVICE!!
Procedure:
1: Download a ROM of your Choice, RENAME the *.nbh for your ROM to: DIAMIMG.nbh
2: Copy DIAMIMG.nbh to the "Internal Storage" of your Device.
3: Bring device into bootloader (Reset + Hold Vol Down), this will show the Red, Blue, Green screen showing "Serial" - Connect device in bootloader mode to USB, the word "Serial" will change to "USB"
4: Run mtty1.42.exe, You will se a box showing "COM1" from this list select "USB" - If USB isn't in the list, something has gone wrong in the "Driver Installation" Section of POST 1
5: Leave default parameters, (8 bits / Flow Control NONE / Stop bits 1 / Parity None / Local Echo No) and Click OK
6: Run following commands:
6a: Press enter first to get prompt (Will Show as EITHER USB> or CMD> - Personally Mine Showed CMD>)
---------------------
MTTY OUTPUT:
---------------------
CMD>
---------------------
6b: type "set 14 0" without the quotes to tell bootloader to boot the OS after reset:
---------------------
MTTY OUTPUT:
---------------------
CMD>set 14 0
HTCST ÚÈHTCEUSB>
---------------------
6c: type "task 29" to get your device formatted:
---------------------
MTTY OUTPUT:
---------------------
Cmd>task 29
Format BINFS start
Fill RSVD information for block 288 to 321
CE start sector=0x14, total sector of CE and TFAT=0x14
CE start start block=321, total block=1727
ERASE block 1337 FAIL !!!
Write 0xFF start page=0x5040, total page=0x1AFC0
Format BINFS end
Cmd>
---------------------
6d: type "task 8" to ask your device reboot:
---------------------
MTTY OUTPUT:
---------------------
Cmd>task 8
Cmd>
---------------------
7: Immediately DISCONNECT your device and hold "Vol Down and Back" (Back = Small Arrow above "End Call" Button) to Initiate ROM Flash
8: After ROM flash Hard-reset (Pen Reset, then Press and Hold Vol Down and Circle) again, on completion "Press Vol Up To Boot" Is displayed, press "Vol Up" and allow the ROM to boot.

MTTY - Flashing From USB
Before you start:
a: FULLY COMPLETE POST 1
b: grab: mtty1.42.zip
AND ENSURE YOU HAVE HARD-SPL ON YOU DEVICE!!
Procedure:
1: Bring device into bootloader (Reset + Hold Vol Down), this will show the Red, Blue, Green screen showing "Serial" - Connect device in bootloader mode to USB, the word "Serial" will change to "USB"
2: Run mtty1.42.exe, You will se a box showing "COM1" from this list select "USB" - If USB isn't in the list, something has gone wrong in the "Driver Installation" Section of POST 1
3: Leave default parameters, (8 bits / Flow Control NONE / Stop bits 1 / Parity None / Local Echo No) and Click OK
4: Run following commands:
5a: Press enter first to get prompt (Will Show as EITHER USB> or CMD> - Personally Mine Showed CMD>)
---------------------
MTTY OUTPUT:
---------------------
CMD>
---------------------
5b: type "set 14 0" without the quotes to tell bootloader to boot the OS after reset:
---------------------
MTTY OUTPUT:
---------------------
CMD>set 14 0
HTCST ÚÈHTCEUSB>
---------------------
5c: type "task 29" to get your device formatted:
---------------------
MTTY OUTPUT:
---------------------
Cmd>task 29
Format BINFS start
Fill RSVD information for block 288 to 321
CE start sector=0x14, total sector of CE and TFAT=0x14
CE start start block=321, total block=1727
ERASE block 1337 FAIL !!!
Write 0xFF start page=0x5040, total page=0x1AFC0
Format BINFS end
Cmd>
---------------------
5d: type "task 8" to ask your device reboot:
---------------------
MTTY OUTPUT:
---------------------
Cmd>task 8
Cmd>
---------------------
6: Immediately DISCONNECT your device then Press and Hold Vol Down to bring the device back to bootloader and connect to USB.
7: Run ROM Flasher and flash via USB. After rom flash is completed Hard-reset (Pen Reset, then Press and Hold Vol Down and Circle) then allow the ROM to boot.

Very good to have a MTTY thread that rounds everything up!
Good job and thanks for all the effort!

i must say this is the reason i got my old rom working and stuck with it without wanting to upgrade. this happened to me, and for about 4 days or more the phone kept crashing and needing a hard reset. even changing roms or reloading the same rom didnt fix.
i tried the MTTY thing and it was difficult to get going.
i personally really appreciate writing all this up, because now i will probably go and try another rom, with this thread in the back of my mind if things start acting up.
so thanks!

dieselboy said:
i must say this is the reason i got my old rom working and stuck with it without wanting to upgrade. this happened to me, and for about 4 days or more the phone kept crashing and needing a hard reset. even changing roms or reloading the same rom didnt fix.
i tried the MTTY thing and it was difficult to get going.
i personally really appreciate writing all this up, because now i will probably go and try another rom, with this thread in the back of my mind if things start acting up.
so thanks!
Click to expand...
Click to collapse
To be honest, i have NEVER experienced the issues that require MTTY! I have always just flashed from internal storage and never had an issue.
I wrote this because i just wanted to get MTTY working incase i ever do experience it!!
MG

pauldgroot said:
Very good to have a MTTY thread that rounds everything up!
Good job and thanks for all the effort!
Click to expand...
Click to collapse
No problem, I personally got sick of trying loads of instructions to have them fail!
Most of my failures were due to drivers and improper installation!
Glad you find this useful!!
MG

I must just say that u might have to watch the x64bit drivers if they are digitally signed... Cuz neither Vista 64 nor Windows 7 64 will let u load or start those drivers if they are not digitally signed.
IF that the case and if u have installed the driver but it says that it has stopped it due to the driver not been Digitally signed u have to start windows vista/7 in "ignore digitally signed drivers" mode.
When u start the computer, keep hitting F8 and it will prompt you if u want to start in safe mode bla bla and in the bottom of that list there is an option that goes something like this:
Start Windows without Digitally signed Driver Check... or sumthing like that...
This is only if u have problems with the x64 driver... like i did...
BTW... u made a beautiful how-to man. Great job!

Reb0rn said:
Start Windows without Digitally signed Driver Check... or sumthing like that...
This is only if u have problems with the x64 driver... like i did...
BTW... u made a beautiful how-to man. Great job!
Click to expand...
Click to collapse
added this to the first post!!
thanks alot!
MG

well done
sticky!

benko286 said:
well done
sticky!
Click to expand...
Click to collapse
Agreed!!!
MG

MG, great thread thanks....
I am wondering whether you have any idea what happened to my Diamond, and what could I have done to save it (it is now with HTC).
http://forum.xda-developers.com/showthread.php?t=539958
I didn't do the "Driver Installation" part you described in your procedure, although I could still see the "USB" option in the dropdown, can that be where I went wrong?
Would also like to check how come recently there seems more flash problems reported? I myself have been flashing for some one year or so now... and never had a problem till now... I would like to get back to flashing again once my Diamond returns (hopefully), but now I am not sure I would since I am not sure what I did wrong to cause the problem to start in the first place.

epiphone said:
MG, great thread thanks....
I am wondering whether you have any idea what happened to my Diamond, and what could I have done to save it (it is now with HTC).
http://forum.xda-developers.com/showthread.php?t=539958
I didn't do the "Driver Installation" part you described in your procedure, although I could still see the "USB" option in the dropdown, can that be where I went wrong?
Click to expand...
Click to collapse
Possibly, i really would suggest running throught the entire thread if you have a brick.
reinstall the drivers, using the ones i have posted, also use the MTTY i have posted.
also USE the exact commands i have posted (i.e. not "task 28", use "task 28 55aa")
then after the MTTY format, HARD-RESET your device then to clear anything else off, then in your case, flash from the PC not internal storage.
epiphone said:
Would also like to check how come recently there seems more flash problems reported? I myself have been flashing for some one year or so now... and never had a problem till now... I would like to get back to flashing again once my Diamond returns (hopefully), but now I am not sure I would since I am not sure what I did wrong to cause the problem to start in the first place.
Click to expand...
Click to collapse
Personally i have never experienced (touch wood) these flashing problems, i have consistently flashed from internal storage and NEVER via USB.
personally this is where i think the problem resides, with leftover data from USB flashing logging up the devices.
as there are more "Bloated roms" (i.e. ones with loads of nice but useless software) this is also causing the problems.
having said that i use possibly the most bloated rom about, the NRGZ EnergyROM series!! i swap between this and the BSB, im more drawn to the BSB at the moment as there is more storage and ram free.
but as i said this is only my opinion and not verifiable facts! (i could be totally wrong!!)

MG, thanks for your replies... unfortunately I am not able to try the "task 28 55aa" now that I have booked my phone in This thread however, will no doubt be useful for more others in time to come!

Hmmm... the strange thing is that after ive had these problems i have to use MTTY as soon as i must flash another ROM then the one i already have in...
But as i said... no problems as long as it works

epiphone said:
MG, thanks for your replies... unfortunately I am not able to try the "task 29 55aa" now that I have booked my phone in This thread however, will no doubt be useful for more others in time to come!
Click to expand...
Click to collapse
MG, is it "task 29 55aa" or "task 28 55aa"?

sb0611 said:
MG, is it "task 29 55aa" or "task 28 55aa"?
Click to expand...
Click to collapse
sorry my error "task 28 55aa"
ill edit previous post
MG

sorry for the noob question, i'm on XP would I still need to run through the driver setup in the first post?

skilty said:
sorry for the noob question, i'm on XP would I still need to run through the driver setup in the first post?
Click to expand...
Click to collapse
I dont have XP, but i guess not, i have never heard of people having a problem with MTTY on XP.
Just disable USB connections in active sync, reboot your system and start MTTY.
If there s no USB option you may have to find the XP Active Sync Drivers and follow my method, but using the XP drivers.
MG