Related
Please, if someone has MDA PRO with original ROM can use this indications to completely backup it (and upload it to
ftp://ftp.xda-developers.com/Uploads/Universal/
please!!!)
What you need:
MDA Pro ;-)
USB cable
PC
1 sd card or mmc card (at least 128MB)
MTTY.EXE (you can find it in internet but the version can use usb connection and not only COM connection)
NTRW.EXE (you can find it in internet.this file must to be copied on your pc on C:\ not in other folders)
If you have ActiveSync installed on your PC on ActiveSync connection settings uncheck USB connection
Before connecting your MDA you should bring it into the boot loader mode. This can be done by simultaneously pressing power + camera buttons and at the same time the soft reset button with the stylus.
The password to enter bootloader is UNIVERSAL
insert a BLANK sd-card
Link the usb cable
Run MTTY.EXE and select USB connection
After that a terminal window will popup in that window.
Type (if you want to backup operating system):
d2s 70100000 04000000
or type (if you want to backup extended rom):
d2s 74100000 00a00000
and press enter. Your MDA will start copying the ROM to the sd card. The screen of your MDA will be dark (no light), but you will see it counting up to 100%. When it reaches 100% it will say it is calculating the checksum. Give it some time till its done and it will say checksum ok.
Please note that there are others command to type due to what you want to obtain.They are:
d2s 60000000 00800000 8M radio rom
d2s 70000000 00100000 1M SPL
d2s 70100000 04000000 64.00 M OS TrueFFS
d2s 74100000 00a00000 10.00 M extrom DSK2ART00 fatfsd
d2s 74b00000 02c40000 44.25 M root filesystem TRUEFFS
After finishing the transfer of the German ROM from your MDA to the SD card, put your SD card into an SD card reader connected to your pc. Your pc might pop up a warning message that says your SD Card is not formatted would you like to format? Click No and open a Command prompt (DOS) window.
Change directory to your root directory (cd c:\) and run the command ntrw read German.nb1 x: where x is the drive letter of your sd card. That command will create the ROM Backup file of your German ROM into your C drive root directory by the name of German.nb1. Make sure you keep German.nb1 in a safe place and use a copy of that file for the rest of the procedure. Note that after finishing the copy from your SD card to German.nb1 file ntrw might give you an error, just don’t pay attention to it.
Luca
(excuse me for my bad english!)
Error message
I have an MDA PRO on Netherlands origional ROM. I am not able to use MTTY.exe to back up my ROM. I follow your procedure with the following exceptions:
1. "Before connecting your MDA you should bring it into the boot loader mode. This can be done by simultaneously pressing power + camera buttons and at the same time the soft reset button with the stylus."
NOTE: Bootloader mode is the dark screen that says "Serial" (unplugged) or "USB" (plugged). I can only access this by using POWER + LIGHT + SOFT RESET.
2. "Run MTTY.EXE and select USB connection. After that a terminal window will popup in that window."
NOTE: Is it necessary after this step to run the command "password UNIVERSAL"?
3. "Type d2s 70100000 04000000"
NOTE: I, as with others, recieve the following error:
USB>d2s
Not allow operation!
USB>d2s 70100000 04000000
Not allow operation!
This final error is where I am stuck. Thanks in advance to anyone who can advise!
I have exactly the same issue as nedbsd.........
Using original Dutch T-Mobile rom:
version: 1.12.42
date: 08/23/05
radio: 1.00.02
protocol: 42.33.P8
ext. rom: 1.12.125 WWE
Hmm... this isn't working for me either. It looks like the MDA Pro is taking the password but not staying in the right mode.
The transcript from MTTY looks like this:
USB>password UNIVERSAL
HTCSPass.< YHTCEUSB>d2s 70100000 04000000
Not allow operation!
USB>
Which is a bit of a mess. It does seem that this is the right password, however, as if I type in a different password I get an error message:
USB>password BADPASS
HTCSInvalid password.R¿ËPHTCEUSB>
This is from a standard English MDA PRO. Any ideas?
MDA Pro Rom backup
So, no fresh ideas :?:
same problems as above:
first stage - password UNIVERSAL
HTCSPass.< YHTCEUSB>
looks like OK
then 2ds
Invalid command : 2ds
or by Topogigi advice
h full
Invalid command : h
MDA Pro Rom backup
really Invalid command-
password UNIVERSAL
HTCSPass.< YHTCEUSB>d2s 70100000 04000000
Not allow operation!
USB>
etc.
This sounds very strange to me. From the beginning of the pocketpc era the bootloader was provided with a comprehensive help feature that you could recall with the command "h full"....
Topogigi said:
This sounds very strange to me. From the beginning of the pocketpc era the bootloader was provided with a comprehensive help feature that you could recall with the command "h full"....
Click to expand...
Click to collapse
Well, you are not the only one that finds it strange, there is about a dozen threads allready about people trying to figure out how to make a rom-image from the universal. No succes so far!
The commands published here on the wiki page just don't work.....
Yup, I've already read all the threads forum-wide concerning the efforts people made to get a rom dump, but noone suggested to try with "h". So, I was curious to see what would happen, that's all! :wink:
BTW, you can notice yourself that there is something very strange in the result you reported in the other thread:
password UNIVERSAL
HTCSPass.< YHTCEUSB>h full
Invalid command : h
For a help screen, use command ? or h
USB>
Click to expand...
Click to collapse
:shock:
That drives me to think that our problems are password related. Perhaps "UNIVERSAL" is a valid password, but with all the commands disabled... :?:
Any success ?
password UNIVERSAL
HTCSPass.< YHTCEUSB>d2s 70100000 04000000
Not allow operation!
USB>
ROM-Verion: 1.13.156 GER
ROM-Date: 09/28/05
Radio-Version: 1.04.10
ExtROM-Version: 1.13.163
Provider: Vodafone
Any update or solution on the backup?
unfortunately not yet ...
@ciapal
what is your bootloader version please???
THANX
buzz
Mine is 0.60 :roll:
.60 here too
hmm, i have 1.00 and i always get "Not allow operation!"
buzz
ah..Anyone has find out how to get the rom....i want to know
ah..Anyone has find out how to get the rom....i want to know
Hi All,
Please, help me with my PDA.
I got used htc universal (vodafone VPA IV). He is semi dead. Device has following problems:
1. display is black-and-white (or grey colored)
2. touchscreen doesn't work
3. device was not dissasembled (there are no stickers removed) and has no damage marks
4. while loading, it shows "NO GSM" D 1.13.56 GER
5. Of course, GSM functions aren't working.
6. I can bypass 'please tap screen...' during first mobile win loading (after hard reset) but then I cann't see task bar.
7. Keyboard of device works but, for example, win-key (with windows logo) does not open main menu for me.
8. On the desktop, I can go into time-settings page, user info, messaging, tasks, appointments, wireless settings menu, baterry meny, screen alignment, calendar, contacts.
9. Bluetooth works, wireless - I'am not sure.
10. I can sync PDA with PC, and with activesync browse and change files on PDA.
I think, from this classification, I have Type 1a.
When I tried to flash my device with Universal_Vodafone_11362_WWE_ROM, UNI_QTEK_13077_176_10900_WWE_Ship and HTC_Uni_SIM_Unlock_v1, I got always radio ROM upgrade error: 114 (upgraiding stops at 0%). While using MTTY116, I am getting "level = FF" after task 32, "not allowed" after d2s commands.
I tried already
USB> password 0000000000000000
USB> set 1e 1
USB> erase a0040000 c80000
USB> erase a0cc0000 c80000
USB> erase a1940000 640000
USB> set 1e 0
Click to expand...
Click to collapse
Also I tried to flash HTC_Uni_SIM_Unlock_v1 to get superCID (but radio ROM error 114).
Here is my log from usb-monitor (in the process of upgrading and receiving "error 114" message).
What can I do with my device? Will be upgrading using SD card helpfull in this situation or I have no chances?
Thanks for any help.
Join the club.......
http://forum.xda-developers.com/showthread.php?t=289260
Exactly the same problem
I just bricked my a696 in the process of doing the official asus update and have been trying to unbrick it using the information in this forum (particularly here and here) without any luck. I was wondering if anyone could help me with this problem. this is what I have figured out and done from my reading:
1. I have downloaded the image file for my unit - A696_dump_wm6_2_eng.rar
2. I have also downloaded USBLoader.exe
when I connect my pda, I can get it into the mode where it accepts usb input (POWER + ENTER + RESET). However when I try to run usbloader I get a bunch of errors that seem to suggest that my computer can't open a connection to the usb port.
------------------------------------
C:\usbloader nk.nb0
#####################################################################
# USB image transfer tool for Intel PXA27X USB Development Board #
# Version: 1220'04 Author: O.C #
#####################################################################
try to open \\.\wceusbsh001
try to open \\.\wceusbsh002
try to open \\.\wceusbsh003
try to open \\.\wceusbsh004
try to open \\.\wceusbsh005
USB pipe opening error
------------------------------------
I am using vista business, and am running the command prompt in administrator mode. I have also tried doing the same procedure on a windows xp machine and it has given me the same error. When I connect my pda, windows does detect the connection and loads a usb device driver. Active Sync does not start. I feel like I am missing something very basic that I just don't know about. any help would be greatly appreciated, thanks in advance!
Same problem
OK ..I am now up to the same spot. The next step I am going to try is to try to do it from the SD card using this method. I will let you know how I get on.
Anyone else offer any suggestions?
JohnYW
Fixed
I managed to get my ASUS 696 back again, thanks to the info posted on this forum.
Using the NB0 file plus USBloader.exe finally got it to go. It seems the loader only looks at the first 5 USB ports and if you are plugged into anything higher it doesnt find it. I am using a laptop with a docking station and 2 monitors so had numerous USB ports. When I plugged it into one of the two ports on the laptop itself - Voila - it worked and I now have a working ASUS 696 - no longer a brick!
1. Download the A696_dump_wm6_2_eng.rar file plus USBLoader.exe files.
2. Unzip the rar file
3. Run command prompt and navigate to where these files are.
4. Connect USB cable to bricked unit
5. Hold power and Enter and hit reset and hold till unit goes into USBloader mode
6. From the command prompt run the USB tool with the unzip file and sit back and watch. About 2 minutes and it will reboot. Hopefully all well.
To find those files just google them - good luck
Not fixed for me
I only have 3 USB-ports on my Laptop and USBLoader works with none of them.
The PDA installs himselve as:
-Windows CE USB-device
-- ASUS USB Sync
Outside of the USB-Controller tree.
I get the exact same error as influxx described. Is there any other way to get USBLoader check all the USBs or getting the connection going?
My system is WIN-XP SP2.
Half fixed
Well, i managed to establish the usb connection by using a 10-years-old Laptop with only two USB1.1 ports.
Now i get to that point:
C:\PDA>USBLoader.exe nk.nb0
#####################################################################
# USB image transfer tool for Intel PXA27X USB Development Board #
# Version: 1220'04 Author: O.C #
#####################################################################
try to open \\.\wceusbsh001
The file nk.nb0 was opened
Image total Size 61808640 bytes
NB0 image downloading.....
File nk.nb0 total 61808640 byte read
Size of ACK_PACKET = 20 address of buffer=7c91ee18
<PIPE00> R : request 20 bytes -- 20 bytes read
What we read AckType < 55aa > dwRet < 99 >
Size of ACK_PACKET = 20 address of buffer=55aa
The PDA shows 100% ... but thats all...
No restart, nothing (I waited 15min). If i unplug or reset the PDA i get an infinite number of lines like this:
........
<PIPE00> R : request 20 bytes -- 0 bytes read
What we read AckType < 0 > dwRet < 0 >
Size of ACK_PACKET = 20 address of buffer=0
<PIPE00> R : request 20 bytes -- 0 bytes read
What we read AckType < 0 > dwRet < 0 >
Size of ACK_PACKET = 20 address of buffer=0.........
And my PDA acts like before. Is my Rom dead?
EDIT: No it wasn't. The mainboard kept analyzing the Battery as too low and so everything (flashing included) was locked.
Asus 696 bricked
Can anyone please post an .DIO and or other fix to get my Asus A696 back to work? (pref. WM6 engl)
It hangs on the ASUS bootscreen, after an unsuccesfull ROM upgrade...
I can't use usbloader.exe and nk.nb0 file since I have not a USB cable, and I am forced to use a method of recovery that use only the SD card.
CyBear said:
EDIT: No it wasn't. The mainboard kept analyzing the Battery as too low and so everything (flashing included) was locked.
Click to expand...
Click to collapse
So what did you do to fix it? I am having the exact same problem. (bricked 636N after failed update to WM6)
--EDIT--
Ok my problem was that I dumped a WM6 from another 636N and the bricked one was WM5. After restoring a dutch WM5 image (which worked) I updated to an english ROM that worked.
The one thing tipping me off to find a WM5 dump was that at around 84% when restoring, the counter jumped back to 1%, continued to 14% then jumped to 100%.
Thx for all the wonderful advice on this forum. Now I have not only a working 636N but also the knowledge to restore one if it breaks in the future (I have around 20)
CyBear said:
Well, i managed to establish the usb connection by using a 10-years-old Laptop with only two USB1.1 ports.
Now i get to that point:
C:\PDA>USBLoader.exe nk.nb0
#####################################################################
# USB image transfer tool for Intel PXA27X USB Development Board #
# Version: 1220'04 Author: O.C #
#####################################################################
try to open \\.\wceusbsh001
The file nk.nb0 was opened
Image total Size 61808640 bytes
NB0 image downloading.....
File nk.nb0 total 61808640 byte read
Size of ACK_PACKET = 20 address of buffer=7c91ee18
<PIPE00> R : request 20 bytes -- 20 bytes read
What we read AckType < 55aa > dwRet < 99 >
Size of ACK_PACKET = 20 address of buffer=55aa
The PDA shows 100% ... but thats all...
No restart, nothing (I waited 15min). If i unplug or reset the PDA i get an infinite number of lines like this:
........
<PIPE00> R : request 20 bytes -- 0 bytes read
What we read AckType < 0 > dwRet < 0 >
Size of ACK_PACKET = 20 address of buffer=0
<PIPE00> R : request 20 bytes -- 0 bytes read
What we read AckType < 0 > dwRet < 0 >
Size of ACK_PACKET = 20 address of buffer=0.........
And my PDA acts like before. Is my Rom dead?
EDIT: No it wasn't. The mainboard kept analyzing the Battery as too low and so everything (flashing included) was locked.
Click to expand...
Click to collapse
I have the exact problem, it loads to 100% then gives me these errors. How the hell do i fix this. PLEASE somebody give me some support on this, the battery has been charging for hours so i cant imagine it thinking i dont have enough battery power.
JohnYW said:
1. Download the A696_dump_wm6_2_eng.rar file plus USBLoader.exe files.
2. Unzip the rar file
3. Run command prompt and navigate to where these files are.
4. Connect USB cable to bricked unit
5. Hold power and Enter and hit reset and hold till unit goes into USBloader mode
6. From the command prompt run the USB tool with the unzip file and sit back and watch. About 2 minutes and it will reboot. Hopefully all well.
To find those files just google them - good luck
Click to expand...
Click to collapse
I have asked this in another thread as well with no response. What/where is this ENTER key??????? I know where the POWER button is and I know where the RESET button is but nothing on the unit or in the manual says ENTER.
same problemmm... which is the enter key ???? reset and power i understand... help me pls
The enter key is the one in the center of the circular directional pad. Press that button and the power button while hitting the reset. Hold these buttons until the USBloader screen comes up. Hope this helps, good luck!
Day2 with a bricked Diamond....
=================================
Background
==========
Happened while trying to flash EnergyROM released 7/22
WinXP, not on any USB Hub, and on Unsigned-Hard-SPL-Diamond-Olinex.
The vol down + back + reset method doesn't go to completion (I have had no issues with BsB roms so far using this method), on the Diamond it shows :
--------------------------
00018003
DIAMING.nbh - FAIL
OS - FAIL
Update Terminate
UPDATE FAIL
--------------------------
If I try to soft reset the screen shows the classic bootloader screen, and the RUUNBH at the top-right:-
-----------------------
Diam100 64M
SPL-1.40.OliNex
MicroP-Diam (LED) v.11
-----------------------
PSOC-Diam STAGE_PVT v0x30
Upgrade ROM code error
Please try again
--------------------------------------------
I am able to re-flash this HardSPL (and in doing so removes the ROM Upgrade Error and enter into Bootloader mode (vol down + reset) successfully.
I am also able to re-flash my Radio (Diamond_Radio_1.00.25.05.nbh).
Any rom however that I then try to flash using CustomRUU/ROMUpdateUtility does not work, it always gets stuck at around 20% with the below error:
---------------------------------------------------------
ERROR 226 : FLASH WRITE
Flash write error happened. Pls check your PDA phone.
---------------------------------------------------------
I read that I am supposed to be trying signed ROMs that work with my HardSPL, and went to this thread to get one, but same thing it is also stuck at 20%.
http://forum.xda-developers.com/showthread.php?t=400411
Have also tried the below MTTY method describe in some of the Kaiser (Yes, pretty desperate, getting stupid) threads:
======================================================================================
1. Download mtty.exe from here: http://taeguk.co.uk/xda
2. Disable activesync (connection settings -> uncheck "allow usb connections")
3. Kill the following two processesto stop active sync; rapimgr.exe and wcescomm.exe (Ctrl+Shift+Esc, select from the list of processes).
4. Connect your Kaiser to PC using USB cable.
5. Open mtty, select USB port and click OK.
6. Hit ENTER twice, you should see the "Cmd>" prompt.
7. Type the command "boot", you should see something like this:
Cmd> boot
InitDisplay: Display_Chip=1
No card inserted
OSSIReadBack ++
Read SI data from flash success
tail signature match
Checksum match
UserStorageSIPreload ++
======================================================================================
...except that I don't get the above lines after executing the boot command, instead I see:
--------------------------------------------------
Cmd>boot
InitDisplay: Display_Chip=1
dwDirectNum: 0, dwMatrixNum: 0, dwMicroPNum: 0
Fill RSVD information for block 288 to 321
Storage start sector=0xFF40, total sector=0xB080
Storage start block=1054, total block=706
Total Bad Block in CE: 1
Erase physical block from 1345 to 2032
si backup: Erase physical block from 2032 to 2048
Fixed new dwPSImageSize = 0x5640000
--------------------------------------------------
...and my Diamond boots to the "Touch Diamond" screen with the black backdrop. Can someone help?
try to connect the phone with mtty and type task 29.
this should format your phone.
then connect it with activesync and flash a stockrom onto it.
it that works, try flashing a design rom.
Dude, thanks for your reply... I got the following, this means it failed right?
------------------------------------
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 226 FAIL !!!
Write 0xFF start page=0x5040, total page=0x1AFC0
Format BINFS end
Cmd>
epiphone said:
Dude, thanks for your reply... I got the following, this means it failed right?
------------------------------------
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 226 FAIL !!!
Write 0xFF start page=0x5040, total page=0x1AFC0
Format BINFS end
Cmd>
Click to expand...
Click to collapse
try flashing a stock rom. you can download it from the htc website and see what happens.
Dude....Tried this stock rom (actually I tried before trying what you suggested), it still didn't work; the flashing process still stuck at the same place 26%.
RUU_Diamond_hTC_Asia_HK_WWE_1.34.831.1_52.24.25.08_0.93.25_Ship
found this in another thread :
type (dont copy&paste):
task 28
and press enter
If the result is the following then you are out of luck:
flFormatPhysicalDrive:status=23
DOC_format failed!
Got this:
Cmd>task 28
Format start
Fill RSVD information for block 288 to 321
Storage start sector=0xFF40, total sector=0xB080
Storage start block=1054, total block=706
Total Bad Block in CE: 1
Erase physical block from 1345 to 2032
si backup: Erase physical block from 2032 to 2048
Format end
Cmd>
Trying stock rom again.....
on my old phone i had to type
format BINFS
to format the flash. you could try that.
if the rom flash still does not work.
you seem to have a bad block on your internal memory. i am not sure how to get around that.
a stock rom fills the entire rom space with new information. that might introduce problems as well.
maybe you should also try a design rom (not the energy one, because that is a large rom)
try the bsb or deepshining. they have less information and might not use the memory at block 26.
if that does not help, you will have to find people with more knowledge than me.
Still can't flash the stockrom still stuck at 26% after trying task 28...
I can't get the format BINFS command through:
Cmd>format BINFS
Command error !!!
Thanks for your time anyway dude... appreciate it.
try searching , i also found this
http://forum.xda-developers.com/showthread.php?t=296722
*deleted repeated post
*deleted repeated post
Dude.. no offence but that I thought is for Hermes, not HTC Diamond? Also that thread seems pretty old...?
Bump... anyone can give other suggestions?
disconnecting any USB device
epiphone said:
Still can't flash the stockrom still stuck at 26% after trying task 28...
I can't get the format BINFS command through:
Cmd>format BINFS
Command error !!!
Thanks for your time anyway dude... appreciate it.
Click to expand...
Click to collapse
try disconnecting any USB device the PC, including Pendrive (leave only the diamond connected), then flash the stock rom
epiphone said:
Dude.. no offence but that I thought is for Hermes, not HTC Diamond? Also that thread seems pretty old...?
Click to expand...
Click to collapse
i am sorry that there is not a solution on a silver platter.
so after reading my link things you could try:
the hardspl is made by the same person. maybe he included the task 2a in your spl as well?
apparently fixing a bad block can be done with a hardspl. maybe you can send the guy creating the hardspl a personal message with your problem.
get your magic wand, wave and say "reparo"
throw your phone out the window or send it for repairs.
Dude, thanks for your answer, nothing helped me still...
I have tried to PM the SPL makers, but quite sure they wouldn't have time to respond Eventually i have had to book my Diamond in for repairs, not sure what is the cost/repair.
My problem now is what should I do in future, since I figure I will flash again... don't see what I done wrong that can suddenly cause this to happen in the first place... I have been flashing for about a year now.
epiphone said:
Dude, thanks for your answer, nothing helped me still...
I have tried to PM the SPL makers, but quite sure they wouldn't have time to respond Eventually i have had to book my Diamond in for repairs, not sure what is the cost/repair.
My problem now is what should I do in future, since I figure I will flash again... don't see what I done wrong that can suddenly cause this to happen in the first place... I have been flashing for about a year now.
Click to expand...
Click to collapse
there is never any garantee for flashing.
things you can try are the same as the things you tried to restore your phone.
so format or flash a stock rom, before a custumized rom.
do not try every rom, but just the ones that seem professional.
i know this is old topic but i want to contribute.
just today had sort of same issue, except my device flashed full until the end where RUU replied error and the device got stuck spl with RUUNBH. i did task 29 and the flashed a stock htc rom and that fixed issue. just like that.
Hello Everyone!
I'm having the same issue as OP, but I tried task 29, task 28 55aa, task 28, and neither worked for me. The flash of a single OS stucks at 76% with flash write error (226), I've searched the forum for hours, but none of the same flash error code issues was mine. I can reflash radio, but not the os, my hardspl is olinex 1.93, when I reflash the radio it start and stucks at the Touch Diamond screen with the radio and stuff number on the right side. If I then try to flash a rom (even stock rom from HTC site!) It freezes around 65% with the same error. If I command in mtty task 16 0, then again it freezes on the Touch Diamond screen. Please anyone can help?
UP: Got it resolved!! My internal flash is damaged, coz if I flash a 60Mb rom, it succeedes, if I flash a rom with over 80mb in size, it fails.
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