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

[4D3]

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 (http://forum.xda-developers.com/showthread.php?t=540290&page=59) 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!!)

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



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 (http://forum.xda-developers.com/member.php?u=614742) - for pointing me to the light!
l2tp (http://forum.xda-developers.com/member.php?u=407815) - for the images
lunasea (http://forum.xda-developers.com/member.php?u=1745042) - for providing me with working drivers

and of course to anyone else I forgot.


I hope this helps people!!

MG

[4D3]

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 (http://www.ngohq.com/home.php?page=dseo)
Remove Watermark V0.8 (http://deepxw.blogspot.com/2008/12/remove-watermark-v03-build-20081210.html)

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:

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... :P


BTW... u made a beautiful how-to man. Great job! :D


-----------------------------------------------------------------------

Big thanks to maybeme (http://forum.xda-developers.com/member.php?u=1580443) 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 (http://forum.xda-developers.com/attachment.php?attachmentid=210100&d=1248862015) 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!!):

http://maybeme.be/mtty/thumb/01.png (http://maybeme.be/mtty/01.png)

5: Right Click and Select "Properties" then go to Driver tab, then Select "Update Driver"

http://maybeme.be/mtty/thumb/02.png (http://maybeme.be/mtty/02.png)

6: Choose to "Browse Computer For Driver" (the second option):

http://maybeme.be/mtty/thumb/03.png (http://maybeme.be/mtty/03.png)

7: Select "Let Me Pick From A List...." (the second option):

http://maybeme.be/mtty/thumb/04.png (http://maybeme.be/mtty/04.png)

8: Click "Have Disk":

http://maybeme.be/mtty/thumb/05.png (http://maybeme.be/mtty/05.png)

9: Select the folder with downloaded driver From Step 1 and select "wceusbsh.inf" (this is the same file for x86 & x64):

http://maybeme.be/mtty/thumb/06.png (http://maybeme.be/mtty/06.png)

10: You will get back to previous screen, then click Install

10a: WINDOWS 7 ONLY - The Below Warning will appear, Select "Install anyway":

http://maybeme.be/mtty/thumb/07.png (http://maybeme.be/mtty/07.png)

11: The drivers will be successfully installed:

http://maybeme.be/mtty/thumb/08.png (http://maybeme.be/mtty/08.png)

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:

http://maybeme.be/mtty/thumb/09.png (http://maybeme.be/mtty/09.png)

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

[4D3]

Follow this procedure for FLASHING YOUR ROM FROM INTERNAL STORAGE AFTER MTTY

Before you start grab: mtty1.42.zip (http://forum.xda-developers.com/attachment.php?attachmentid=208457&stc=1&d=1248437219)

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.

[4D3]

Before you start:

a: FULLY COMPLETE POST 1
b: grab: mtty1.42.zip (http://forum.xda-developers.com/attachment.php?attachmentid=208457&stc=1&d=1248437219)

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.

[pauldgroot]

Very good to have a MTTY thread that rounds everything up!

Good job and thanks for all the effort!

[dieselboy]

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!

[4D3]

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!

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

[4D3]

Very good to have a MTTY thread that rounds everything up!

Good job and thanks for all the effort!


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

[Reb0rn]

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... :P


BTW... u made a beautiful how-to man. Great job! :D

[4D3]

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... :P


BTW... u made a beautiful how-to man. Great job! :D


added this to the first post!!

thanks alot!

MG

[benko286]

well done :)


sticky!

[4D3]

well done :)


sticky!


Agreed!!!


MG

[epiphone]

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.

[4D3]

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?

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.



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.


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!!)

[epiphone]

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!

[Reb0rn]

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 :D

[sb0611]

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!

MG, is it "task 29 55aa" or "task 28 55aa"?

[4D3]

MG, is it "task 29 55aa" or "task 28 55aa"?


sorry my error "task 28 55aa"

ill edit previous post

MG

[skilty]

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

[4D3]

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


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

[skilty]

thanks for the reply,

got it running without the drivers (well it showed the usb option anyway), i've followed the rest of your instructions from there.. hopefully it'll solve some of the weird flashes i've done recently..

thanks for the guide :D

[@antonio@]

hi
I have 29 tasks running these results:

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 928 FAIL !!!
Write 0xFF start page=0x5040, total page=0x1AFC0
Format BINFS end

with the command "task 28 55aa"
I could solve my problem?
I confirmed that not format the memoryNand?


grazie

[4D3]

hi
I have 29 tasks running these results:

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 928 FAIL !!!
Write 0xFF start page=0x5040, total page=0x1AFC0
Format BINFS end

with the command "task 28 55aa"
I could solve my problem?
I confirmed that not format the memoryNand?


grazie


Hi,

you are using the wrong commands!!!

I dont know what task 29 does!!!


6c: type "task 28 55aa" to get your device formatted:

---------------------
MTTY OUTPUT:
---------------------
Cmd>task 28 55aa
Format start
Fill RSVD information for block 288 to 321
Storage start sector=0xB600, total sector=0xF240
Storage start block=761, total block=969
Total Bad Block in CE: 0

Erase physical block from 1051 to 2048

formatstorage Bad block found: 1625
Format end

Cmd>

[Reb0rn]

ROFL maybe it was good we didnt make it that easy for ppl to get this to work ... can one actually brick ones phone with the MTTY?

[makeveral]

good job MysticGenius! this was really needed :)

[robinbb]

good job MysticGenius! this was really needed :)

Seconded. At last I have MTTY running OK! Ta

[@antonio@]

Hi,

you are using the wrong commands!!!

I dont know what task 29 does!!!


thanks I have resolved:

Cmd>task 28 55aa
Format start
Fill RSVD information for block 288 to 321
Storage start sector=0x9600, total sector=0x11040
Storage start block=633, total block=1089
Total Bad Block in CE: 0

Erase physical block from 923 to 2048

formatstorage Bad block found: 1216
Format end

:) ;)

[4D3]

good job MysticGenius! this was really needed :)


Seconded. At last I have MTTY running OK! Ta


Im really glad this is helping people, i just with it could be stickied!!!

(It should be stickied!!)

MG

[4D3]

thanks I have resolved:

Cmd>task 28 55aa
Format start
Fill RSVD information for block 288 to 321
Storage start sector=0x9600, total sector=0x11040
Storage start block=633, total block=1089
Total Bad Block in CE: 0

Erase physical block from 923 to 2048

formatstorage Bad block found: 1216
Format end

:) ;)

No Problem!!

MG

[epiphone]

Gee, @antonio@ you got the exact same issue as I see thread below.... but I haven't tried task 28 55aa yet (although task 28 didn't work). Can you describe how you got yourself into that fix in the first place? I am still wondering what hit me.

http://forum.xda-developers.com/showthread.php?t=539958

I booked my phone in to the HTC fellows but they just called back saying my mobo is fried and are asking for a phenomenal sum to get it repaired... am now hoping that they don't know about MG's mtty method and it can work! :)

[4D3]

Gee, @antonio@ you got the exact same issue as I see thread below.... but I haven't tried task 28 55aa yet (although task 28 didn't work). Can you describe how you got yourself into that fix in the first place? I am still wondering what hit me.

http://forum.xda-developers.com/showthread.php?t=539958

I booked my phone in to the HTC fellows but they just called back saying my mobo is fried and are asking for a phenomenal sum to get it repaired... am now hoping that they don't know about MG's mtty method and it can work! :)


I thinkk you should try the exact procedure i prescribed.

including "set 14 0" "task 28 55aa", "task 0" and double hard reset!

Just follow the instructions exactly and i think you will be fine.

You cannot "fry" the mobo on these phones, to do so you would have to microwave the device! or put a crack in the mobo through dropping it.

I dropped mine in the toilet the other day, i turned it off, took the case of it, let it dry for a few hours, reassembled it and it worked!! - these phone pretty tough!!

I do not believe what they are saying and i think they are trying to get some more money from you!!

Does your device turn on? yes.... so no fried mobo!!!

when do you get you device back?

MG

[epiphone]

Haha.... damn dude... hope you disinfected your phone! :)

I can't wait to try your method and prove that xda community is one up against htc folks! Not sure when they will return the set, think should be this couple of days. They did however manage to already make some money from me anyhow... there is a minimum charge just for booking it in.

I will make sure I report back to your thread my results, good/bad. I can indeed turn on my phone, get into bootloader, and see "Serial" change to "USB" when I try to flash via PC.

[4D3]

Haha.... damn dude... hope you disinfected your phone! :)

lol yeah!!!


I can't wait to try your method and prove that xda community is one up against htc folks! Not sure when they will return the set, think should be this couple of days. They did however manage to already make some money from me anyhow... there is a minimum charge just for booking it in.

Do you not have insurance from your provider? why did you take it directly to htc?

also how old is you device? (how long since you paid for it!!)

also what did htc want to charge you? (if this fais i may be able to help you out in a different way ;):D)


I will make sure I report back to your thread my results, good/bad. I can indeed turn on my phone, get into bootloader, and see "Serial" change to "USB" when I try to flash via PC.


Im pretty sure if you can get to that you will not have an issue, just DONT flash the NRGZ rom again until you get a rom onto your device and working.

I would try BSB or a stock rom before the ENERGY rom.

MG

[epiphone]

They are quoting me something like 350 USD to get the mobo changed, which is exactly what I kinda paid for the phone in June 2008 when I first bought it first hand. It has been more than a year so I do not have anymore warranty left.

[MrAdelphi02]

Thank you for this thread, but I can't seem to make this work!!!

I have Windows 7 Ultimate, but even rebooting the computer in 'Ignore digitally signed drivers' still wont let me update the x64bit driver...

My download isn't wce_x64.inf as in the very well presented pictures, but instead it shows up as wceusbsh.inf

Is the download correct???

[4D3]

Thank you for this thread, but I can't seem to make this work!!!

I have Windows 7 Ultimate, but even rebooting the computer in 'Ignore digitally signed drivers' still wont let me update the x64bit driver...

My download isn't wce_x64.inf as in the very well presented pictures, but instead it shows up as wceusbsh.inf

Is the download correct???

yeah the download is correct, the images were supplied by someone else (credited in the first post)

wceusbsh.inf is correct, i think i stated that in the instructions.

mmm seems odd, i have this installed on 7 Ultimate also and it worked, you can either try again or.... i am actually doing a fresh install of windows 7 tonight, so if you can wait i will see whats going on.

i can assure you that this method is SPECIFICALLY for windows 7 and Vista with many successes.

I would suggest, connecting your device is bootloader mode, go to your system/device manager and uninstall the device completely.

disconnect, reboot your system, then start from post 1 step 1.

Best of luck, (i will try also tonight, im pretty sure Reb0rn (http://forum.xda-developers.com/member.php?u=614742) in the thread has this working on Win7 x64!!)

[Reb0rn]

yup... works for me... but i got my drivers from another source then the ones u have here thou... maybe its that...

Maybe i should send u them as i can assure you they work in Win 7 Ultimate final with my "start without verified digital signature bla bla bla" shit on x64:P

[4D3]

yup... works for me... but i got my drivers from another source then the ones u have here thou... maybe its that...

Maybe i should send u them as i can assure you they work in Win 7 Ultimate final with my "start without verified digital signature bla bla bla" shit on x64:P

Yeah that would be great!! ill note you my email

MG

[Reb0rn]

Sweet ;) Those drivers work 100% tested as long as you follow the guide.

[epiphone]

Report : Still cannot fix my problem. I think the problem is in the "Total Bad Block in CE: 1".... others are seeing it at =0.

Cmd>set 14 0
HTCST ÚÈÒHTCE
Cmd>task 28 55aa
Format start
Fill RSVD information for block 288 to 321
Storage start sector=0x10EC0, total sector=0xA100
Storage start block=1116, total block=644
Total Bad Block in CE: 1

Erase physical block from 1407 to 2048

Format end

Cmd>task 0 <- I can't get the device to reboot with this command...

Anyone know other ideas? Seems this fellow has a similar issue, he mentioned something about changing his nand chip... how do I do that? I tried some of the commands he did when tried on my set:

Cmd>info 8

--- 2K bytes sector version ---

DEVICE NAME=samsung_k9k2g08
DEVICE ID=0xAA
DEVICE MAKER ID=0xEC
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x800
BLOCK PAGE=0x40

Checking block information

BLOCK 0 (0x0) is reversed block
BLOCK 1 (0x1) is reversed block
BLOCK 2 (0x2) is reversed block
BLOCK 3 (0x3) is reversed block
BLOCK 8 (0x8) is reversed block
BLOCK 10 (0xA) is reversed block
BLOCK 11 (0xB) is reversed block
BLOCK 12 (0xC) is reversed block
BLOCK 13 (0xD) is reversed block
BLOCK 14 (0xE) is reversed block
BLOCK 28 (0x1C) is reversed block
BLOCK 29 (0x1D) is reversed block
BLOCK 30 (0x1E) is reversed block
BLOCK 31 (0x1F) is reversed block
BLOCK 226 (0xE2) is bad block <=========== this should be the root of my issue?? My RUU flash always shows ERROR 226
Partition[0], type=0x20, start=0x2, total=0x63E
Partition[1], type=0x23, start=0x640, total=0x8C0
Partition[2], type=0x25, start=0xF00, total=0xF040
Partition[3], type=0x4, start=0xFF40, total=0xB080

CE Total Length(with sector info) = 0x801FA00
CE CheckSum Length(without sector info) = 0x7FA0000

http://forum.xda-developers.com/showthread.php?t=493595

[schbounz]

Thanks for this tutorial !

Note that on my PC the driver was named "HTC Device/HTC USB Sync", not "Mobile devices/Microsoft USB Sync". It can be confusing, so if my remark can be helpful to someone else...

[Brav0]

I have a question about this line:

formatstorage Bad block found: 1625

I get a different number there, is that bad? Or will it be different for some phones?

My phone seems to run without any problems. Anyways thanks for this awesome guide!

[s2007]

I did post 2 point 4 and do not see Microsoft USB Sync but only HTC USB Sync as wrote schbounz. It is OK? Can I continue?

PS> Thanks for instruction

[schbounz]

It is OK? Can I continue?
I did, it worked :)

[HaiLe512]

I did your very detailed procedure and it works. I am using XP so I could skip some steps. I am now running w/o soft reset for a few days. Thanks.

Question: What happened to the bad block? I hope this program masks it coz if you run the MTTY program again, the same bad blocks appear. I had multiple bad blocks (six to be exact!).

Thanks,
:D
A happy ROM-Flasher!

[4D3]

I did post 2 point 4 and do not see Microsoft USB Sync but only HTC USB Sync as wrote schbounz. It is OK? Can I continue?

PS> Thanks for instruction


Yeah, as long as you install the drivers to your device, it doesnt matter what the device shows up as in the device manager!!

MG

[Kulik]

sorry to bother you guys with this, but how do I install active sync on Vista? installation always stops and says its for winXP only and for sync I ve always used Windows Mobile Device Center, but it seems drivers are totally different.

[4D3]

sorry to bother you guys with this, but how do I install active sync on Vista? installation always stops and says its for winXP only and for sync I ve always used Windows Mobile Device Center, but it seems drivers are totally different.

well you cannot use active sync on Vista. the vista version is Windows Mobile Device Center. but this is only the software on your PC.

your device when you connect it via USB gives 3 options, the first is ACTIVE SYNC, second is USB etc etc. you need to select Active Sync.

(I didnt add it to the tutorial because i thought it was obvious!!!! :eek:)


MG

[Kulik]

your device when you connect it via USB gives 3 options, the first is ACTIVE SYNC, second is USB etc etc. you need to select Active Sync.

(I didnt add it to the tutorial because i thought it was obvious!!!! :eek:)


MG

AAA:D thats what that means:P ok, my bad, it is obvious, i just got a little confused...

EDIT: Anyways, now Ive done it right n i must say WOW, what a guide, step by step, brilliant work! Helped a lot.

[4D3]

AAA:D thats what that means:P ok, my bad, it is obvious, i just got a little confused...


No Problems!!

MG

[teorouge]

Ehi guys, have any ideas about that?

Cmd>task 28 55aa
Format start
Fill RSVD information for block 288 to 321
Storage start sector=0x9500, total sector=0x11180
Storage start block=629, total block=1094
Total Bad Block in CE: 0

Erase physical block from 919 to 2048

formatstorage Bad block found: 1736
Format end

I dont' think it gets to format, at least not the 4GB... am I right? Is stock rom installing the only way out? That overwrites the radio, too! Or may I format the Internal Storage simply via Windows, somehow I don't know about? :D

[Reb0rn]

Hey dude... i think you should mention in the How To that Hard-SPL IS REQUIRED to use this software...

Some nuts have been using this with original SPL and bricked their phone badly...

So again: THIS SHOULD BE USED WITH HARD-SPL ONLY, NOT STOCK SPL's!!!

[4D3]

Hey dude... i think you should mention in the How To that Hard-SPL IS REQUIRED to use this software...

Some nuts have been using this with original SPL and bricked their phone badly...

So again: THIS SHOULD BE USED WITH HARD-SPL ONLY, NOT STOCK SPL's!!!


Are you serious? people are that stupid?

Ill add to the first post!!

[Reb0rn]

Are you serious? people are that stupid?

Ill add to the first post!!

Yup... up to 5 diamond's bricked in the spanish forums what ive heard :P

So put it in big red letters :P

[makeveral]

Yup... up to 5 diamond's bricked in the spanish forums what ive heard :P

So put it in big red letters :P

ye thats true! well in fact 2-3 ppl not 5 :D

i wrote the tutorial and i wrote in bold
IMPORTANT NOTE: YOU NEED A HARDSPL

but looks like some ppl dont read xD

btw MG i upgraded to windows7 , used the drievrs you posted and worked perfectly so thanks ;)

[4D3]

ye thats true! well in fact 2-3 ppl not 5 :D

i wrote the tutorial and i wrote in bold
IMPORTANT NOTE: YOU NEED A HARDSPL

but looks like some ppl dont read xD

btw MG i upgraded to windows7 , used the drievrs you posted and worked perfectly so thanks ;)

No problem, im glad you found this useful!! still loving your ROM!!

working on moving over from Sashimi install to XDA_UC!! just abit apprehensive!!

MG

[AaaApl]

Follow this procedure for FLASHING YOUR ROM FROM INTERNAL STORAGE AFTER MTTY

8: ...press "Vol Up" and IMMEDIATELY press and hold "Vol Down and Back" (Back = Small Arrow above "End Call" Button) to Initiate ROM Flash

What for is "Vol Down and Back" in this case? I think this part is not needed.

[4D3]

What for is "Vol Down and Back" in this case?

well considering this is your first post here, ill go easy.

but how exactly do you think you will initiate the rom flash from your internal storage without these key presses.

these steps are a VERY well documented and THE only way to initiate a flash from the device internal storage.

you are totally incorrect and this is irrelevant to the thread.


I think this part is not needed.

LOL, ok, well i invite you to skip that step and see what happens, but dont be surprised if you end up with a device with no ROM.

ROFL!!!

The reason you need this is CLEARLY written below:



8: Hard-reset (Pen Reset, then Press and Hold Vol Down and Circle) on completion "Press Vol Up To Boot" Is displayed, press "Vol Up" and IMMEDIATELY press and hold "Vol Down and Back" (Back = Small Arrow above "End Call" Button) to Initiate ROM Flash

[Reb0rn]

uhm i dont know man. Everytime ive flashed like 3 or 4 times i have to use MTTY again... can this be the sign of my mobile nearing death?

[4D3]

uhm i dont know man. Everytime ive flashed like 3 or 4 times i have to use MTTY again... can this be the sign of my mobile nearing death?


nah, just bloated roms!!

if you had phone death your nand chip would be going and MTTY would tell you with bad blocks in the CE output from MTTY.

MG

[Thiago Fialho]

This work with any cooked? or i need stock rom for do that?

[4D3]

This work with any cooked? or i need stock rom for do that?

i dont understand what your asking? you cant cook this into a rom.

MG

[Thiago Fialho]

The diamimg.nbh need to be original or can be a cooked rom?

[Thiago Fialho]

I am asking that because i don't have stock rom, so if i flash one cooked rom mtty will work?

[4D3]

I am asking that because i don't have stock rom, so if i flash one cooked rom mtty will work?

ahh sorry, use any rom you want, that is why you would do it this way!!

MG

[teorouge]

nah, just bloated roms!!

if you had phone death your nand chip would be going and MTTY would tell you with bad blocks in the CE output from MTTY.

MG

So do you think "formatstorage Bad block found: 1736" is the first hint to "Bye bye Diamond"? Or how should I get it? That only one block, number 1736, is failing? So what? I mean, i have a warranty for some months and I'd use that, if the MTTY error isn't nice...

[Reb0rn]

nah, just bloated roms!!

if you had phone death your nand chip would be going and MTTY would tell you with bad blocks in the CE output from MTTY.

MG

that is bad thou... i have a bad block :(

hmmm... maybe time to think about a touch HD :P

[Anakha56]

Can I ask a stupid question?

What does MTTY do? I have run it but I am just curious to know what the difference is between a MTTY format and install vs a new ROM (cooked) format and install? Please dont flame me for my stupid question as said I am just curious to know why it is needed and how it solves our problems.

Many many thanks for guide worked like a charm! :D

[4D3]

So do you think "formatstorage Bad block found: 1736" is the first hint to "Bye bye Diamond"? Or how should I get it? That only one block, number 1736, is failing? So what? I mean, i have a warranty for some months and I'd use that, if the MTTY error isn't nice...

Id only worry if you have CE bad blocks, even then, if you can MTTY and flash i wouldnt be to bothered about them either!!

as long as you can flash!!

[4D3]

that is bad thou... i have a bad block :(

hmmm... maybe time to think about a touch HD :P

mm, maybe not, i would be wrong on the CE block front, but as long as your device MTTY's and accepts a new rom flash i wouldnt be bothered.

I read in the wiki somewhere that it seems to be random with the bad blocks, and in my personal experience i have MTTY and got a bad block, and other times i have done it and had none!!!

MG

[4D3]

Can I ask a stupid question?

What does MTTY do? I have run it but I am just curious to know what the difference is between a MTTY format and install vs a new ROM (cooked) format and install? Please dont flame me for my stupid question as said I am just curious to know why it is needed and how it solves our problems.

Many many thanks for guide worked like a charm! :D

Formats the NAND chip that hod the rom.

It is needed because for EG if you flash a rom that it 120mb in size, then flash to a 100mb rom, there is 20mb of the old rom left on the NAND which can cause you phone to act very funny, symptoms like, disappearing programs, hard-resetting, icons moving around strangely etc etc.

basically what this method does it format the NAND, then you Hard-Reset to completely erase EVERYTHING then you flash your new rom to a clean/empty NAND.

Hope that helps

MG

[Anakha56]

Thanks for the explanantion, greatly appreciated :).

[flitzjoy]

I got some strange errors here. If some one can help me.

Ok, i´m using Win7 x64 with correct active sync driver and running with driver signature enforcement disabled.

I do everything fine but in step 11 my HTC device got some strange error like "error code 10".

If I go to driver date it show 2003 anyway.

but after the last step My USB Unknow device isnt installed correctly so I cant use MTTY.

[alienao]

Hi MG, first of all thanks for the tutorial, it is really worth!! The thing is that i usually flash from the PC (it's only that i'm used to do it...), and from some time ago i though i was doing the mtty "pre-flash" process correctly, but it is quite different to yours and i'm now confused :confused:...

I started to "mtty" the phone since the first time it begun to hard-reset automatically after a rom flash. I searched and found this post: http://forum.xda-developers.com/showpost.php?p=3433851&postcount=22. I tried and it worked!!! So, the process i usually follow is:
1) Phone in bootloader
2) In Mtty, execute command "task 29"
3) Without hard- or soft-resetting, start the RUU with the desired ROM and flash

I haven't experienced hard-resets anymore... Now the question is: am i doing wrong? What's your opinion, continue doing that way or doing as your tutorial says?

Thanks in advance!!

[4D3]

Hi MG, first of all thanks for the tutorial, it is really worth!! The thing is that i usually flash from the PC (it's only that i'm used to do it...), and from some time ago i though i was doing the mtty "pre-flash" process correctly, but it is quite different to yours and i'm now confused :confused:...

I started to "mtty" the phone since the first time it begun to hard-reset automatically after a rom flash. I searched and found this post: http://forum.xda-developers.com/showpost.php?p=3433851&postcount=22. I tried and it worked!!! So, the process i usually follow is:
1) Phone in bootloader
2) In Mtty, execute command "task 29"
3) Without hard- or soft-resetting, start the RUU with the desired ROM and flash

I haven't experienced hard-resets anymore... Now the question is: am i doing wrong? What's your opinion, continue doing that way or doing as your tutorial says?

Thanks in advance!!

Ok,

to start, i have a list of the available MTTY commands task 29 isnt on it, i dont know what this does, where it came from, nor do i care to try it to find out!!!

I have searched alot of MTTY bootloader commands and I have never seen task 29!!!

set 14 0 tells the device to expect an OS boot after flashing
task 28 Formats the NAND (Where the rom is held)
task 28 55 aa Formats the NAND & REFORMATS the partition

After formatting, as with a normal hard disk, artefacts can be recovered from it which is why you perform a HARD-RESET after MTTY.

In my opinion i would use my method as it uses real commands that are documented and it also removes the artefacts.

Also i would start flashing from your device and not from your PC, firstly it takes about 2 minutes instead of 10 minutes and secondly, the less time you spend in "Flash Mode" the less that can go wrong, i.e. power loss etc etc.

Hope that helps

MG


P.S. the extra steps i have used take about an extra 2-3 seconds to execute but give a whole world of extra safety during flashing!!

I mean imagine using MTTY without set 14 0, and your device never boots again!!!

[pinttas]

Does MTTY solve the lag of GPS?

[AgentSmith]

Formats the NAND chip that hod the rom.

It is needed because for EG if you flash a rom that it 120mb in size, then flash to a 100mb rom, there is 20mb of the old rom left on the NAND which can cause you phone to act very funny, symptoms like, disappearing programs, hard-resetting, icons moving around strangely etc etc.

basically what this method does it format the NAND, then you Hard-Reset to completely erase EVERYTHING then you flash your new rom to a clean/empty NAND.

Hope that helps

MG
MG, thank you so much for giving me the tools and information to fix my Diamond! :) After having flashed so many roms the phone started to act weird yesterday after flashing one of the latest roms, showing all kinds of symptoms like you describe here. Now it is working again as it should. MTTY should be the default step before every flash as there's really no alternative for a complete format of the NAND.

This thread should be another sticky!!

[alienao]

Ok,

to start, i have a list of the available MTTY commands task 29 isnt on it, i dont know what this does, where it came from, nor do i care to try it to find out!!!

I have searched alot of MTTY bootloader commands and I have never seen task 29!!!

set 14 0 tells the device to expect an OS boot after flashing
task 28 Formats the NAND (Where the rom is held)
task 28 55 aa Formats the NAND & REFORMATS the partition

After formatting, as with a normal hard disk, artefacts can be recovered from it which is why you perform a HARD-RESET after MTTY.

In my opinion i would use my method as it uses real commands that are documented and it also removes the artefacts.

Also i would start flashing from your device and not from your PC, firstly it takes about 2 minutes instead of 10 minutes and secondly, the less time you spend in "Flash Mode" the less that can go wrong, i.e. power loss etc etc.

Hope that helps

MG


P.S. the extra steps i have used take about an extra 2-3 seconds to execute but give a whole world of extra safety during flashing!!

I mean imagine using MTTY without set 14 0, and your device never boots again!!!

Thanks for the explanation MG!! I think i'll follow your advice and do it as you mention in the tutorial... for the next flash ;)

Rgds!

[4D3]

Does MTTY solve the lag of GPS?

Not to my knowledge, if it does it might be because your rom is abit bloated

MG

[4D3]

MG, thank you so much for giving me the tools and information to fix my Diamond! :) After having flashed so many roms the phone started to act weird yesterday after flashing one of the latest roms, showing all kinds of symptoms like you describe here. Now it is working again as it should. MTTY should be the default step before every flash as there's really no alternative for a complete format of the NAND.

This thread should be another sticky!!


No Problem,im happy to help.

I also agree with the sticky idea, this is the only thread like it and it is so help/useful yet no sticky!!

MG

[AgentSmith]

I am wondering now if mtty can be used for other devices too like the TD2 and the Sony Xperia. I guess it can but I want to be sure. ;)

[4D3]

I am wondering now if mtty can be used for other devices too like the TD2 and the Sony Xperia. I guess it can but I want to be sure. ;)

I would say yes to the TD2, and not sure for the Xperia!! (I dont have either so cant say for definite!!)

I think MTTY is ok for HTC devices as it has been used on kaiser, hermes etc etc

MG

[alienao]

+1 to make this post sticky ;)

[y2kreamy]

Hi MG,

Many thx !! great work indeed.

I am new to xda dev,MTTY n all, ur guide is fantastic though to follow.

I have been flashin rom like mad as i have discovered XDA-Dev a month ago only, otherwise was thinking to sell my diam.

did mtty to know whethr bad blocks left in d device.

got following output.

Cmd>set 14 0
HTCST ÚÈÒHTCE
Cmd>task 28 55aa
Format start
Fill RSVD information for block 288 to 321
Storage start sector=0xD340, total sector=0xD580
Storage start block=878, total block=854
Total Bad Block in CE: 0

Erase physical block from 1168 to 2048

Format end

Cmd>task 0

Cmd>

now i hav a ques, aftr firing set 14 0 cmd
result is HTCST ÚÈÒHTCE
but what u hav mentioned is HTCST ÚÈÒHTCEUSB

why this diff, also block num are different

Excuse me, i am asking this ques, cud b a stupid ques, but request u to reply.

also is it ok to run mtty, bfr every new rom flash?

thank you!

[4D3]

got following output.

Cmd>set 14 0
HTCST ÚÈÒHTCE
Cmd>task 28 55aa
Format start
Fill RSVD information for block 288 to 321
Storage start sector=0xD340, total sector=0xD580
Storage start block=878, total block=854
Total Bad Block in CE: 0

Erase physical block from 1168 to 2048

Format end

Cmd>task 0

Cmd>


the bad blocks seem to be random!! I get bad blocks when i use MTTY, others in the thread have also reported different bad blocks too, but from what i understand these make no difference.

there has been some mention about this but i cant remember where i saw it, the only thing i would look for is bad CE blocks as these can give an indication that the NAND chip is about to break, but even then there has been a post previously stating 1 bad CE block, but the device still flashed!!

Unfortunately i cannot find more info about this!


now i hav a ques, aftr firing set 14 0 cmd
result is HTCST ÚÈÒHTCE
but what u hav mentioned is HTCST ÚÈÒHTCEUSB

Doesnt matter as long as you "set 14 0" this forces an OS boot after format.


why this diff, also block num are different

I have no idea lol, sometimes when i run MTTY instead of CMD> i get USB>

block numbers could be dependant on your device!! dont worry bout it!



also is it ok to run mtty, bfr every new rom flash?

thank you!

yeah EVERYTIME! (also you should flash from Internal Storage not via USB from your PC)

Hope that helps

MG

[y2kreamy]

the bad blocks seem to be random!! I get bad blocks when i use MTTY, others in the thread have also reported different bad blocks too, but from what i understand these make no difference.

there has been some mention about this but i cant remember where i saw it, the only thing i would look for is bad CE blocks as these can give an indication that the NAND chip is about to break, but even then there has been a post previously stating 1 bad CE block, but the device still flashed!!

Unfortunately i cannot find more info about this!



Doesnt matter as long as you "set 14 0" this forces an OS boot after format.



I have no idea lol, sometimes when i run MTTY instead of CMD> i get USB>

block numbers could be dependant on your device!! dont worry bout it!




yeah EVERYTIME! (also you should flash from Internal Storage not via USB from your PC)

Hope that helps

MG


Thank you for your help & promptness.

Always do the internal flashing as u suggest.

You guys are great!!! Keep up the good work:):):)

[guylich]

thanks I'am sure it would be really helpfull

[Riel]

Does MTTY solve the lag of GPS?


Well not if it is of any importance to the tread, but I can say that I am 100% sure that this does NOT solve the lag of GPS. That is a completedly other issue.

[truszek]

@MysticGenius, first of all - thank You. I got question - if i wanna flash from internal storage, can i skip Post 4: MTTY Instructions For FLASHING FROM YOU SYSTEM, and do only Post3?

Thanks again.

[4D3]

@MysticGenius, first of all - thank You. I got question - if i wanna flash from internal storage, can i skip Post 4: MTTY Instructions For FLASHING FROM YOU SYSTEM, and do only Post3?

Thanks again.


Yeah, " MTTY Instructions For FLASHING FROM YOU SYSTEM" is the instructions if you want to flash from your system.

If you want to flash from your device follow post 2 and 3

MG

[FrAsErTaG]

Many Many Thanks!!!

[4D3]

Many Many Thanks!!!

no problem,vote for sticky!!

Im Putting a pole uo now!!

MG

[4D3]

All who subscribe to this thread please make a vote!!!

Sticky! Sticky! Sticky!

[katakgoreng]

my g sensor seems to stop working..in teeter, the ball only roll left and right but cannot roll up and down, is it have to do with the driver or the hardware? can mtty be used to format the rom to solve the problem or i can just flash new rom using conventional method (ruu)?

[emton]

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)


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 (http://forum.xda-developers.com/member.php?u=614742) - for pointing me to the light!
l2tp (http://forum.xda-developers.com/member.php?u=407815) - for the images
lunasea (http://forum.xda-developers.com/member.php?u=1745042) - for providing me with working drivers

and of course to anyone else I forgot.


I hope this helps people!!

MG

Um.. could you describe more about MTTY, I would think if you want this to be the definitive MTTY thread, then someone donno about MTTY should be able to understand MTTY from your thread. Just a suggestion.
thanks:p

[4D3]

Um.. could you describe more about MTTY, I would think if you want this to be the definitive MTTY thread, then someone donno about MTTY should be able to understand MTTY from your thread. Just a suggestion.
thanks:p


Im not being funny but what exactly do you think the first 4 posts do?

if you want to "learn" about MTTY use google!

this thread is devoted to a buggy device using MTTY, not to teach you the finer points of MTTY.

MG

[4D3]

my g sensor seems to stop working..in teeter, the ball only roll left and right but cannot roll up and down, is it have to do with the driver or the hardware? can mtty be used to format the rom to solve the problem or i can just flash new rom using conventional method (ruu)?


No, MTTY is for completely removing the rom from the NAND so it is free for a new rom, it will not fix a broken rom, you need to contact the rom cheif for that!!


Sorry

MG

[sandervanzijl]

immediately pressing vol down and up did not work for me.

you could change this to the easier:
press volume down and back, then press the red reset button on the back of the phone.
keep pressing vol down and back until rom screen starts.
you will see a message about loading the rom image etc.

[4D3]

immediately pressing vol down and up did not work for me.

at no point in my instructions do i mention ANYWHERE to press vol down and up!!



Can i suggest you read them properly.

you are cheeky telling me that i need to read my own instructions, i know what they say because i wrote them.

can i suggest that you actually get a grasp of my instructions before you criticise them.

also i will be making no edit at all based on your suggestion because these instructions work.


you could change this to the easier:
press volume down and back, then press the red reset button on the back of the phone.
keep pressing vol down and back until rom screen starts.
you will see a message about loading the rom image etc.

why would i do this when it is completely wrong? what you suggest it a rom flash then no hard reset, which is kinda stupid.

after every rom flash you are supposed hard reset, this is common knowledge.

to invoke a Hard-Reset you press vol down + circle, when its complete you get a message saying "Vol Up to Boot"

to flash from internal storage you press vol down + back.

these instructions are not up for debate, they work, i use them on a daily basis.

MG

[y2kreamy]

immediately pressing vol down and up did not work for me.

you could change this to the easier:
press volume down and back, then press the red reset button on the back of the phone.
keep pressing vol down and back until rom screen starts.
you will see a message about loading the rom image etc.

It is as simple as entering bootloader in other cases or flashing rom from internal device.

We have a great thread, which must b a sticky!!!! Kindly appreciate!!!

Hi MG,

I have a question. sry if noob, when we press vol dwn + circle and then Vol up to restore and then when that finishes vol up to boot and immediately vol down + back key to flash rom.

y double hard reset, can't that be done directly flashing rom with single hard reset.

in first hard reset, we are reloading the existing rom and in second step, we flash reqd rom/new rom.

now when we reload existing rom, dont they again occupy nand? and there is no mtty run run in between?

hope im clear?

thx

[4D3]

It is as simple as entering bootloader in other cases or flashing rom from internal device.

We have a great thread, which must b a sticky!!!! Kindly appreciate!!!


Thanks muchly!!


Hi MG,

I have a question. sry if noob, when we press vol dwn + circle and then Vol up to restore and then when that finishes vol up to boot and immediately vol down + back key to flash rom.

y double hard reset, can't that be done directly flashing rom with single hard reset.

in first hard reset, we are reloading the existing rom and in second step, we flash reqd rom/new rom.

now when we reload existing rom, dont they again occupy nand? and there is no mtty run run in between?

hope im clear?

thx


I think you are a little confused, ill try and clear it up, this is whats actually happening throughout the process:

1: Enter bootloader
2: MTTY
3: Hard-Reset
4: Flash ROM
5: Hard Reset

the effect of this process is:

1: Bootloader gives access to the NAND
2: MTTY formats the NAND (removes the existing rom)
3: Hard-Reset clears the device and partition
4: Flash sends ROM to NAND
5: Hard Reset cleans out the files left over from the flash.

does that make it clearer?

If not i can try again!! :o

MG

[empds]

Thanks muchly!!




I think you are a little confused, ill try and clear it up, this is whats actually happening throughout the process:

1: Enter bootloader
2: MTTY
3: Hard-Reset
4: Flash ROM
5: Hard Reset

the effect of this process is:

1: Bootloader gives access to the NAND
2: MTTY formats the NAND (removes the existing rom)
3: Hard-Reset clears the device and partition
4: Flash sends ROM to NAND
5: Hard Reset cleans out the files left over from the flash.

does that make it clearer?

If not i can try again!! :o

MG

"does that make it clearer?"
"If not i can try again!! :o"
"which is kinda stupid"

I must say I read the last few posts and like your nickname you must be a really genious and you must think all the rest are stupid and ignorant.

Do a favor to the community and stop being a really jerk and the most arrogant guy at XDA developers, otherwise you will be only talking to yourself.

[y2kreamy]

does that make it clearer?

MG[/QUOTE]

Nicely detailed...Thank you...:):):)

[4D3]

"does that make it clearer?"
"If not i can try again!! :o"
"which is kinda stupid"



Firstly, i was trying to make it clearer, and the sentiment in my statement was that if i didnt hit the mark id try explaining it again!!

whats wrong with that? also if you look at the response i got to the message i would say that i satisfied the questions asked of me:

does that make it clearer?

MG

Nicely detailed...Thank you...:):):)

three smiley faces!!!


I must say I read the last few posts and like your nickname you must be a really genious and you must think all the rest are stupid and ignorant.

genious? GENIUS!!

If you are going to attempt to insult me use correct spellings for a start!

as for the last few posts, when someone hasnt read the instructions correctly, made incorrect assumptions and then suggests that i make incorrect alterations to the instructions that have been proven to work time and time again.

this is a stupid thing to do. especially if someone who is new to this reads the incorrect instructions thinking that they are an improvement on the original and screws their phone, the blame will be passed to this thread and me.



Do a favor to the community and stop being a really jerk and the most arrogant guy at XDA developers, otherwise you will be only talking to yourself.


You have no idea about me, you have no idea about anything really!! you have been on this forum for 20 days, made absolutely no contribution to anything, you have only posted 16 times ALL of which have been to gain information for yourself and not to help ANYONE out.

I have to say my favourite is this one:

People have to donate to get these apps???

This is a shame and should not be posted at XDA Developers. People should only donate as gratitude and contribuition for the developer work.

XDA means share, share, and share not pay, pay and pay, there are other sites and forums that you can post these apps if your only concern is profit.

In my opinion these kind of threads are the reason for users to leave and search for other communities and therefore should be closed.

Redirections and informations about Private Forums should be banned too.

Admittedly i gave schaps a bit of a hard time with the whole touchXperience thing but we reconciled and i have to say his apps are worth the money.

I really love this bit:


XDA means share, share, and share not pay, pay and pay, there are other sites and forums that you can post these apps if your only concern is profit.

where did you get this garbage from?



In my opinion these kind of threads are the reason for users to leave and search for other communities and therefore should be closed.

when YOU contribute SOMETHING maybe then you can have a voice!!!

but you who expect everything to be given out for free are moaning. if you want the apps donate, if you dont want to donate dont moan!!

MG

[sandervanzijl]

can i suggest that you actually get a grasp of my instructions before you criticise them.

also i will be making no edit at all based on your suggestion because these instructions work.



you are completely right. I made a mistake. let me quote you from your manual.


8: Hard-reset (Pen Reset, then Press and Hold Vol Down and Circle) on completion "Press Vol Up To Boot" Is displayed, press "Vol Up" and IMMEDIATELY press and hold "Vol Down and Back" (Back = Small Arrow above "End Call" Button) to Initiate ROM Flash


this will not work. first you give instructions for a hard reset, then a rom flash. when you have formatted your phone with mtty, a hard reset is useless, because there is nothing to reset. so after mtty you first need to fill the rom area with a new rom, then do a hard reset.

what you want to do is:
8a flash rom from internal storage
8b do a hard reset.
(just as you said in your comments to my post)

to do this you need to press:
8a vol down + back + pen reset (hold vol down + back until you enter bootloader)
wait until the device has flashed the rom. ( if needed follow instructions on screen.)
8b then hard reset again by pressing vol down + circle + pen reset (hold vol down + circle until you are in bootloader)
then press vol up (as instructed on the screen) to do the hard reset.
press vol up again to reboot.

I think this is a very good thread, but you also need to see comments as positive feedback on how to improve a good thing. not as an attack on what you are doing.

[4D3]

you are completely right. I made a mistake. let me quote you from your manual.



this will not work. first you give instructions for a hard reset, then a rom flash. when you have formatted your phone with mtty, a hard reset is useless, because there is nothing to reset. so after mtty you first need to fill the rom area with a new rom, then do a hard reset.

what you want to do is:
8a flash rom from internal storage
8b do a hard reset.
(just as you said in your comments to my post)

to do this you need to press:
8a vol down + back + pen reset (hold vol down + back until you enter bootloader)
wait until the device has flashed the rom. ( if needed follow instructions on screen.)
8b then hard reset again by pressing vol down + circle + pen reset (hold vol down + circle until you are in bootloader)
then press vol up (as instructed on the screen) to do the hard reset.
press vol up again to reboot.

I think this is a very good thread, but you also need to see comments as positive feedback on how to improve a good thing. not as an attack on what you are doing.


No offence taken, i just wanted you to re-read and make sure you understood, 95% of problems with MTTY is people not understanding what they are doing.

also the hard-reset after the MTTY does have an effect, it may not affect your particular diamond, but on mine it is the difference between it working and not, the step is harmless to your device, but it just makes it easier to have one set of instructions that will work on all devices.

also when the NAND is formatted there are some artefacts left in memory, the hard-reset after MTTY removes these.

the hard-reset as you know is to restore the default settings of the rom, so if your flashing the NAND the files to do so are held in memory, the hard-reset removes these.

(or the reading i did pointed me to that conclusion, if you know different im more than happy to learn!!)

MG

[sandervanzijl]

No offence taken, i just wanted you to re-read and make sure you understood, 95% of problems with MTTY is people not understanding what they are doing.

also the hard-reset after the MTTY does have an effect, it may not affect your particular diamond, but on mine it is the difference between it working and not, the step is harmless to your device, but it just makes it easier to have one set of instructions that will work on all devices.

also when the NAND is formatted there are some artefacts left in memory, the hard-reset after MTTY removes these.

the hard-reset as you know is to restore the default settings of the rom, so if your flashing the NAND the files to do so are held in memory, the hard-reset removes these.

(or the reading i did pointed me to that conclusion, if you know different im more than happy to learn!!)

MG

I can agree. And viewed that way your instructions seem to make sense, but are not complete.

after a rom flash you need another hard reset.

that is why I interpreted your instructions as wrong.

the complete procedure after mtty should be:

8a hard reset
8b flash rom from internal storage
8c do a hard reset.

to do this you need to press:
8a hard reset by pressing vol down + circle + pen reset (hold vol down + circle until you are in bootloader)
then press vol up (as instructed on the screen) to do the hard reset.
press vol up again to reboot.
8b vol down + back + pen reset (hold vol down + back until you enter bootloader)
wait until the device has flashed the rom. ( if needed follow instructions on screen.)
8c then hard reset again by pressing vol down + circle + pen reset (hold vol down + circle until you are in bootloader)
then press vol up (as instructed on the screen) to do the hard reset.
press vol up again to reboot.


would you agree?

By the way, i never needed to do a hard reset after mtty and my diamond works perfect. I do use mtty to make sure i do not get any problems after flashing. for example unexpected hard resets.
another step to prevent this is to first flash a stock rom, then flash the cooked rom, then do a hard reset. and maybe using mtty in between.

[upm15]

"95% of problems with MTTY is people not understanding what they are doing"
I think i'm one of them. Sorry asking a noob question, doing MTTY will it format my Internal storage? If yes, that means I need to backup all my internal storage data?

[y2kreamy]

Firstly, i was trying to make it clearer, and the sentiment in my statement was that if i didnt hit the mark id try explaining it again!!

whats wrong with that? also if you look at the response i got to the message i would say that i satisfied the questions asked of me:



three smiley faces!!!

MG

Some ppl don't read forum rules...one can argue when they have a point. Just criticising does not make sense, it needs a valid point.

Dont wry MG, your thread has helped many, included in links of many rom devs, ya some got confused like me, never mind.

[4D3]

"95% of problems with MTTY is people not understanding what they are doing"
I think i'm one of them. Sorry asking a noob question, doing MTTY will it format my Internal storage? If yes, that means I need to backup all my internal storage data?


no MTTY only affects the device, not the internal storage! your internal storage will be left in tact

Hope that helps

MG

[alienao]

Ok,

to start, i have a list of the available MTTY commands task 29 isnt on it, i dont know what this does, where it came from, nor do i care to try it to find out!!!

I have searched alot of MTTY bootloader commands and I have never seen task 29!!!

...



Hi MG, i just wanted to mention that i've found the meaning of the "task 29" command, thanks to another guy who has posted the link to the wiki (i don't remember where, i think i've found it in a google search). It is in http://wiki.xda-developers.com/index.php?pagename=Diamond_Bootloader. That task actually formats the BinFS, which from my understanding is part of the NAND as well, but not the whole NAND... I've searched for more info about
that binfs and although is documented, is too low-level to me. Something about "Binary ROM image File System", which i guess is where the rom itself is held in the NAND...

only wanted to let you know, don't know if it helps...

[upm15]

no MTTY only affects the device, not the internal storage! your internal storage will be left in tact

Hope that helps

MG

Thanks. Just another question:
"7: Exit MTTY, Hard-Reset (POWER + Circle Button + Pen Reset) then being the device back to bootloader and connect to USB, finally run ROM Flasher and flash via USB"

Hard-reset should be Circle Button+Vol Down+Pen reset? I tried Power+Circle button+Pen reset it is just a normal reset. Sorry I quite new in this.

[Brav0]

Thanks. Just another question:
"7: Exit MTTY, Hard-Reset (POWER + Circle Button + Pen Reset) then being the device back to bootloader and connect to USB, finally run ROM Flasher and flash via USB"

Hard-reset should be Circle Button+Vol Down+Pen reset? I tried Power+Circle button+Pen reset it is just a normal reset. Sorry I quite new in this.

Vol Down + Circle Button + Pen Reset = Hard Reset

:)

[4D3]

Thanks. Just another question:
"7: Exit MTTY, Hard-Reset (POWER + Circle Button + Pen Reset) then being the device back to bootloader and connect to USB, finally run ROM Flasher and flash via USB"

Hard-reset should be Circle Button+Vol Down+Pen reset? I tried Power+Circle button+Pen reset it is just a normal reset. Sorry I quite new in this.

Vol Down + Circle Button + Pen Reset = Hard Reset

:)

No, after MTTY, pen reset, then press and hold vol down and Circle.

ill swap it round in the instructions for clarity.

EDIT: changed the instructions to: (Pen Reset, then Press and Hold Vol Down and Circle)

thanks for the heads up

MG

[4D3]

Hi MG, i just wanted to mention that i've found the meaning of the "task 29" command, thanks to another guy who has posted the link to the wiki (i don't remember where, i think i've found it in a google search). It is in http://wiki.xda-developers.com/index.php?pagename=Diamond_Bootloader. That task actually formats the BinFS, which from my understanding is part of the NAND as well, but not the whole NAND... I've searched for more info about
that binfs and although is documented, is too low-level to me. Something about "Binary ROM image File System", which i guess is where the rom itself is held in the NAND...

only wanted to let you know, don't know if it helps...


Thanks for the info, really useful!

task 29 seems to format the CE block, which is the place on the NAND where the ROM is held, but it is between 2 specific points on the NAND.

what we want to do is COMPLETELY format the NAND.

Really nice info, thanks alot :):)

MG

[4D3]

Hi,

just to let you all know that i have revised the last 3 steps of these instructions in light of some new information.

you will notice that "task 0" has changed to "task 8" and the last 2 steps have been revamped for efficiency.

PLEASE PLEASE read and use these NEW additions.

Thanks for your time

MG

[hudytheone]

just want to say many thanks for a great thread simply followed MG's instructions mi diamond works perfectly again thanks again

[4D3]

just want to say many thanks for a great thread simply followed MG's instructions mi diamond works perfectly again thanks again


Glad to help!!

Vote Sticky!!

MG

[BB88]

The x86 drivers are dated 10/6/2004, not 2003 nor 2007. What is wrong?
Anyway, USB was not showing in MTTY after I installed the driver. So I go back to the device and set it to Active Sync instead of USB when I plug in my cable, and disable USB connection in Active Sync on PC. USB is then showing up in MTTY.

[4D3]

The x86 drivers are dated 10/6/2004, not 2003 nor 2007. What is wrong?
Anyway, USB was not showing in MTTY after I installed the driver. So I go back to the device and set it to Active Sync instead of USB when I plug in my cable, and disable USB connection in Active Sync on PC. USB is then showing up in MTTY.


doesnt matter bout driver year, as long as its not 2007.

ive swapped drivers about and not changed pics.

MG

[4fun00]

Should try this, what a great job man! Ty!

[deathgod1989]

is there a way to do this with a mac?

[4D3]

is there a way to do this with a mac?


dont think so, its kinda counter productive to have a WM device and a MAC, surely if you had a mac you would be using an i-Pants-Phone?
(Sorry I HATE Apple!!)

i guess you could but you would need a MAC version of MTTY, mac HTC USB AS Drivers.

Other than that, the other things that will probably be different is the driver install method.

The commands issued to MTTY will not change so you can use the instructions from post 2 and 3.

(I have a question, why? WM & mac? :confused::rolleyes:;))

MG

[okoto]

MG, Thank you for putting this together, it's very helpful and informative.
I follows all the steps and was successful 9 (I think). Here is what I did:
Cmd>set 14 0
HTCST ÚÈÒHTCE
Cmd>task 28 55aa
Format start
Fill RSVD information for block 288 to 321
Storage start sector=0xD340, total sector=0xD580
Storage start block=878, total block=854
Total Bad Block in CE: 0

Erase physical block from 1168 to 2048

Format end

Cmd>task 8

If MTTY formats the divice, why then after I did hard reset ( after MTTY and before flashing the new rom) the old rom was still there and started installing. My understanding is that it was suppose to be gone - that was the whole point of MTTY.:confused:

[4D3]

MG, Thank you for putting this together, it's very helpful and informative.
I follows all the steps and was successful 9 (I think). Here is what I did:
Cmd>set 14 0
HTCST ÚÈÒHTCE
Cmd>task 28 55aa
Format start
Fill RSVD information for block 288 to 321
Storage start sector=0xD340, total sector=0xD580
Storage start block=878, total block=854
Total Bad Block in CE: 0

Erase physical block from 1168 to 2048

Format end

Cmd>task 8

If MTTY formats the divice, why then after I did hard reset ( after MTTY and before flashing the new rom) the old rom was still there and started installing. My understanding is that it was suppose to be gone - that was the whole point of MTTY.:confused:


This has already been covered in the thread.

This is whats actually happening throughout the process:

1: Enter bootloader
2: MTTY
3: Hard-Reset
4: Flash ROM
5: Hard Reset

the effect of this process is:

1: Bootloader gives access to the NAND
2: MTTY formats the NAND (removes the existing rom)
3: Hard-Reset clears the device and partition
4: Flash sends ROM to NAND
5: Hard Reset cleans out the files left over from the flash.

does that make it clearer?

MG

[flitzjoy]

is there a way to do this with a mac?

There´s a project named HTCFlasher (http://forum.xda-developers.com/showthread.php?t=399762) that aims to create a rom flashing utility to run on Linux. It its opensource (so can be portable to Mac or any other system) and it do more than just flashing a rom like extract a rom from the device or enter in bootloader serial prompt and execute commands (mtty).

I never tested and the project seems to be a little stopped, anyway is something worth looking.

[shendere]

Sorry, but I have Windows XP and I have not USB title.

What to do ????:mad::mad::mad:

[4D3]

Sorry, but I have Windows XP and I have not USB title.

What to do ????:mad::mad::mad:

Dont know, this thread if for Vista and Win 7.

Win XP has no issue with MTTY so i dont know y ur posting :mad: here, I guess your issue is because YOU are not using MTTY correctly.

As far as im aware on XP you just put the phone into bootloader and run MTTY


MG

[y2kreamy]

As far as im aware on XP you just put the phone into bootloader and run MTTY

MG

Yes!! confirmed by me as i have XP (SP2 32) no probs in running MTTY

[4D3]

Yes!! confirmed by me as i have XP (SP2 32) no probs in running MTTY


Thanks muchly!!

MG:D

[Zinken]

Sorry, but I have Windows XP and I have not USB title.

What to do ????:mad::mad::mad:

Uncheck the box "allow USB-connections" in active sync.

At least that solved it for me.

[Zinken]

First of all, thank you for this guide. If it solves my freezing issues and eliminates the need for flashing a stock rom between upgrades I will be very pleased.

One thing though: when executing the formatting with command "task 28 55aa" I het a different output,

Cmd>task 28 55aa
Format start
Fill RSVD information for block 288 to 321
Storage start sector=0xBB00, total sector=0xED40
Storage start block=781, total block=949
Total Bad Block in CE: 3

Erase physical block from 1074 to 2048

formatstorage Bad block found: 1329
formatstorage Bad block found: 1389
formatstorage Bad block found: 1525
Format end

Do you know what these bad blocks mean?

Thanks in advance!

[4D3]

First of all, thank you for this guide. If it solves my freezing issues and eliminates the need for flashing a stock rom between upgrades I will be very pleased.

One thing though: when executing the formatting with command "task 28 55aa" I het a different output,

Cmd>task 28 55aa
Format start
Fill RSVD information for block 288 to 321
Storage start sector=0xBB00, total sector=0xED40
Storage start block=781, total block=949
Total Bad Block in CE: 3

Erase physical block from 1074 to 2048

formatstorage Bad block found: 1329
formatstorage Bad block found: 1389
formatstorage Bad block found: 1525
Format end

Do you know what these bad blocks mean?

Thanks in advance!

Currently I dont know what the Bad Blocks mean, can you flash you device?

If you can i wouldnt worry as sometimes i get bad blocks and sometimes i dont!!

I have been looking for ages for info on this but i guess it is privy to a select few!!

MG

[Zinken]

Currently I dont know what the Bad Blocks mean, can you flash you device?

If you can i wouldnt worry as sometimes i get bad blocks and sometimes i dont!!

I have been looking for ages for info on this but i guess it is privy to a select few!!

MG

Yeah, no problem to flash and no issues noticed after flashing. In other words nothing to worry about I guess.

Thanks anyway.

[cashlee]

hello

i am using vista 64
i have a problem with "Driver Installation "
at step 9 when i have click on 'have disk', i have select the "wceusbsh"
when i clicked on OK , it said
" this folder doesnt contain a compatible software driver for your
device. If the folder contains a driver, make sure it;s designed to work with
windows for x64 based system"

i also tried it on safe mode, but it doesn;t work

[4D3]

hello

i am using vista 64
i have a problem with "Driver Installation "
at step 9 when i have click on 'have disk', i have select the "wceusbsh"
when i clicked on OK , it said
" this folder doesnt contain a compatible software driver for your
device. If the folder contains a driver, make sure it;s designed to work with
windows for x64 based system"

i also tried it on safe mode, but it doesn;t work

Hi,

I think you need this:

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... :P


BTW... u made a beautiful how-to man. Great job! :D


(It is posted at the bottom of the driver installation section, maybe ill move it to the top!!)

MG

[kwambewright]

which drivers do i use for a win 7 32 bit system?

[4D3]

which drivers do i use for a win 7 32 bit system?

the ones for a 32 bit system? (What kind of question is that?:confused:)

Do you really need talked through that? and no your question is not valid its stupid!

x64 means 64 bit
x86 means 32 bit

MG

[edefux]

hey guy´s i have problems with step 7 flashing from internal storage.


"7: Immediately DISCONNECT your device and Hard-reset (Pen Reset, then Press and Hold Vol Down and Circle) on completion "Press Vol Up To Boot" Is displayed, press "Vol Up" and IMMEDIATELY press and hold "Vol Down and Back" (Back = Small Arrow above "End Call" Button) to Initiate ROM Flash"

this is the way you describe it. i ran mtty and all the commands worked ... last task immediately disconnected the device. i pushed the red button with the pen then held the volume key down and pressed the circle button at the same time. this brings me into a menu where i have 3 options ... i took the first one "restore to factory settings" the i pressed vol up to boot but i can not iniciate the rom flash !!!

i immediately held vol down and back ... the device restores only the factory settings, but still my aztor rom is on there (???) no flash

what did i do wrong ... can i now savely flash throug active sync, am i through with the mtty process now?

[neoceltic]

hey guy´s i have problems with step 7 flashing from internal storage.


"7: Immediately DISCONNECT your device and Hard-reset (Pen Reset, then Press and Hold Vol Down and Circle) on completion "Press Vol Up To Boot" Is displayed, press "Vol Up" and IMMEDIATELY press and hold "Vol Down and Back" (Back = Small Arrow above "End Call" Button) to Initiate ROM Flash"

this is the way you describe it. i ran mtty and all the commands worked ... last task immediately disconnected the device. i pushed the red button with the pen then held the volume key down and pressed the circle button at the same time. this brings me into a menu where i have 3 options ... i took the first one "restore to factory settings" the i pressed vol up to boot but i can not iniciate the rom flash !!!

i immediately held vol down and back ... the device restores only the factory settings, but still my aztor rom is on there (???) no flash

what did i do wrong ... can i now savely flash throug active sync, am i through with the mtty process now?

Have you previously copy the new diamimg.nbh (the ROM that you want to flash) in your internal storage? :confused:
If not, the vol down and back button do nothing because there is no image file ROM to flash! ;)

[edefux]

thanks for your fast reply ... but i did copy the diaming.nbh to the root of the internal storage ... even renamed it in DIAMING.nbh to match the instructions ...

?(

[neoceltic]

thanks for your fast reply ... but i did copy the diaming.nbh to the root of the internal storage ... even renamed it in DIAMING.nbh to match the instructions ...

?(

Yes, but you'll have to rename as DIAMIMG.nbh (not DIAMING.nbh). it is for DIAMond IMaGe. :p

[edefux]

omG .... thanks mate ... how did i get through university with this sort of reading disorder (?) ;)


XP users like me ... no need for the driver installation

thx for this great guide

[Shizophren]

Hi,

I think you need this:

Originally Posted by Reb0rn View Post
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... :P


BTW... u made a beautiful how-to man. Great job!




MG

Hi, i have the same Problem at Step 9. I cannot choose the wceusbsh.inf File.

I started my Vista 64 bit in this "ignore digitally signed drivers" mode, but i still get the messege, that the driver is not supportet on 64Bit OS.

My Device is connected and the bootloader says USB. What can i do???

OK, the W7 X64 Driver seems to working, but after installing i get the messege that my device cannot be started...whats that?

[Jujulian]

Since I did this the first Sign of Live is the Diamond Logo and afterwards I get the Diamond Logo again with the rom infos etc in the right corner...

Berforhand that act was faster and I had the rom infos direct...

A clue what I can do to fix this?

[4D3]

Since I did this the first Sign of Live is the Diamond Logo and afterwards I get the Diamond Logo again with the rom infos etc in the right corner...

Berforhand that act was faster and I had the rom infos direct...

A clue what I can do to fix this?


I dont really understand what you are asking, but i dont believe you did have it faster, i have never once turned my device on and had the rom info immediately, it ALWAYS appears after a few seconds.

I think you have just noticed the small get between the logo showing and the text appearing!

Nothing can fix it, it is how the phone boots!! pretty much the same as your PC, you turn it on, see a black screen, then the white text appears!

I hope i answered your question?

:) MG

[4D3]

Hi, i have the same Problem at Step 9. I cannot choose the wceusbsh.inf File.

I started my Vista 64 bit in this "ignore digitally signed drivers" mode, but i still get the messege, that the driver is not supportet on 64Bit OS.

My Device is connected and the bootloader says USB. What can i do???

OK, the W7 X64 Driver seems to working, but after installing i get the messege that my device cannot be started...whats that?

which drivers are you using? did you use these:

x64 Active Sync Drivers.zip (http://forum.xda-developers.com/attachment.php?attachmentid=208452&d=1248436681)

or the ones saying "Win 7 Tested"

Either set of drivers SHOULD work on vista, but i cannot guarantee this, however i can tell you that all drivers do work and they have been tested and verified by numerous people on the thread.

the only thing i can suggest is that you may have missed something? or try the other x64 drivers and get back to me with the results.

If the worst comes to the worst ill install x64 vista on a virtual box and run through the install myself.

MG

[kwambewright]

the ones for a 32 bit system? (What kind of question is that?:confused:)

Do you really need talked through that? and no your question is not valid its stupid!

x64 means 64 bit
x86 means 32 bit

MG

Sorry for my ignorance! I saw the x64 equaling 64 bit and figured it would be the same for 32 bit. My computer knowledge is not that great. Its fine now, I did it on my XP partition and it worked fine. I was hesitant to try on XP because the last time I tried it did not work on either but that was because the instructions were no where near as clear as these and they had me using cmd>task 29. I apologize for looking like an idiot and inconveniencing you with such a heartfelt reply.;)

[4D3]

Sorry for my ignorance! I saw the x64 equaling 64 bit and figured it would be the same for 32 bit. My computer knowledge is not that great. Its fine now, I did it on my XP partition and it worked fine. I was hesitant to try on XP because the last time I tried it did not work on either but that was because the instructions were no where near as clear as these and they had me using cmd>task 29. I apologize for looking like an idiot and inconveniencing you with such a heartfelt reply.;)


Its ok, I was just a bit stumped by the question!!

task 28 is a command of a different bootloader to format, i think it is from the Himalaya device!

as long as your sorted now!!

MG :)

[Krzysiec]

I`m running WIN 7 and ... After trying to update driver with working and tested WIN 7 driver System is warning me about not digitaly signed driver and after all (reset PC and enter to bootloader) Serial doesn`t change to USB ... Any idea ?

[gorbett]

how long does it typically take for a ROM to load? my diamond has been sitting at "Loading..." for about 20 minutes after following the internal storage steps.

thanks!

[Krzysiec]

Ok my previous post is out of date ;) Stupid me i didn`t noticed there was write to run WIN 7 with f8 and turn off signed drivers checking ;) After that everything went right :) THANKS a lot for GREAT HOW TO ! ;) Cheers !

[Reb0rn]

still cant belive they havent stickyd this thread... its not something you just let pass by...

[4D3]

how long does it typically take for a ROM to load? my diamond has been sitting at "Loading..." for about 20 minutes after following the internal storage steps.

thanks!

Takes about 5-6 mins!

MG

[mderksen]

I have got some problems.

I installed the correct USB (2003) drivers.
Rebooted my device and copied DIAMIMG.nbh to the internal storage root.
Started MTTY and used the MTTY codes, no problems so far.
Disconnect the USB cable after last MTTY code and did Hard-reset.

But it doens't show "Press VolUp to boot". It displays

1. Press VolUp to restore manufacturer default
2. Press VolDown to restore manufacturer default and format moviNAND.
3. Press other keys to cancel

What happend? :(

[4D3]

I have got some problems.

I installed the correct USB (2003) drivers.
Rebooted my device and copied DIAMIMG.nbh to the internal storage root.
Started MTTY and used the MTTY codes, no problems so far.
Disconnect the USB cable after last MTTY code and did Hard-reset.

But it doens't show "Press VolUp to boot". It displays

1. Press VolUp to restore manufacturer default
2. Press VolDown to restore manufacturer default and format moviNAND.
3. Press other keys to cancel

What happend? :(


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.

follow this instructions, you havent done the hard reset, you only get vol up to boot after hard reset, all you have done is initiated the hard reset, not actually started it!!

MG

[mderksen]

follow this instructions, you havent done the hard reset, you only get vol up to boot after hard reset, all you have done is initiated the hard reset, not actually started it!!

MG

This is my MTTY output:

Cmd>set 14 0
HTCST ÚÈÒHTCE
Cmd>task 28 55aa
Format start
Fill RSVD information for block 288 to 321
Storage start sector=0xBD00, total sector=0xEB40
Storage start block=789, total block=941
Total Bad Block in CE: 0

Erase physical block from 1079 to 2048

Format end

Cmd>task 8

After this i get to point 7. I removed the USB cable from my device and did hard reset (Pen Reset, then Press and Hold Vol Down and Circle). But I still get this menu:

1. Press VolUp to restore manufacturer default
2. Press VolDown to restore manufacturer default and format moviNAND.
3. Press other keys to cancel

*edit*
I'm using the BsB6.5Q ROM btw (http://forum.xda-developers.com/showthread.php?t=506533)

Thanks

[4D3]

This is my MTTY output:



After this i get to point 7. I removed the USB cable from my device and did hard reset (Pen Reset, then Press and Hold Vol Down and Circle). But I still get this menu:

1. Press VolUp to restore manufacturer default
2. Press VolDown to restore manufacturer default and format moviNAND.
3. Press other keys to cancel

so press volume up to hard-reset, then press volume up to boot.

this thread is about MTTY, and hard-resetting is common knowledge so im not covering things like hard-resetting.

i dont see the problem, i assume you know how to hard-reset?

MG

[mderksen]

so press volume up to hard-reset, then press volume up to boot.

this thread is about MTTY, and hard-resetting is common knowledge so im not covering things like hard-resetting.

i dont see the problem, i assume you know how to hard-reset?

MG

Thank you very much!

I thought the hard reset was already been done by pressing the reset button + vol down + circle. It worked now. Sorry for not understanding. But I thought you had another menu when pressing reset + vol down + circle.

[MattJ1989]

Just wanted to say thank you so much! Made my Diamond work perfectly again!

[Riel]

I want a new rom. I want to format the device first to make it best.

I do a format (it's clean then)

I do a hard reset (the old rom is installed back)

I flash new rom (over the old rom)

What's the advantage ?

Another question is this:

ON first format I got:

Erase physical block from 1168 to 2048



Then I flashed new ROM, and did MTTY again (for my feeling eliminate the above problem) and with the format after the new rom flash I get:

Erase physical block from 793 to 2048

Looks like a good 400 blocks more?


And last:

7: Immediately DISCONNECT your device and Hard-reset (Pen Reset, then Press and Hold Vol Down and Circle) on completion "Press Vol Up To Boot" Is displayed, press "Vol Up" and IMMEDIATELY press and hold "Vol Down and Back" (Back = Small Arrow above "End Call" Button) to Initiate ROM Flash

Why can't I do:

7: Immediately DISCONNECT your device and Hard-reset (Pen Reset, then Press and Hold Vol Down and Back) (Back = Small Arrow above "End Call" Button) to Initiate ROM Flash

[4D3]

Just wanted to say thank you so much! Made my Diamond work perfectly again!

No Problem, im glad to help :):)

MG

[4D3]

I want a new rom. I want to format the device first to make it best.

I do a format (it's clean then)

I do a hard reset (the old rom is installed back)

I flash new rom (over the old rom)

what are you talking about?

how can the old rom be installed when you have just formatted with MTTY?


What's the advantage ?

Why are you doing this without knowing what your doing? also if your using this thread you should know why your performing these actions!!

THe reason for this is VERY well documented on this site, and can be easily found if you read the first post of most ROMs, here is an example from the BSB thread:



IF YOU HAVE FREEZES/HARD RESETS/STRANGE PROBLEMS USE MTTY YES MTTY MTTY MTTY MTTY MTTY MTTY MTTY MTTY AND IF STILL PROBLEMS UPGRADE TO HARDSPL 1.93 (tutorial here (http://forum.xda-developers.com/showthread.php?t=540290), thanks to MG)




Another question is this:

ON first format I got:

Erase physical block from 1168 to 2048

Then I flashed new ROM, and did MTTY again (for my feeling eliminate the above problem) and with the format after the new rom flash I get:

Erase physical block from 793 to 2048

Looks like a good 400 blocks more?


Firstly, why MTTY, flash a rom then MTTY again? why are you doing this? it does not say anywhere to do this.

It is quite obvious why this has happened, the first ROM was Smaller then the second one you flashed.

why would you do this?



And last:

7: Immediately DISCONNECT your device and Hard-reset (Pen Reset, then Press and Hold Vol Down and Circle) on completion "Press Vol Up To Boot" Is displayed, press "Vol Up" and IMMEDIATELY press and hold "Vol Down and Back" (Back = Small Arrow above "End Call" Button) to Initiate ROM Flash

Why can't I do:

7: Immediately DISCONNECT your device and Hard-reset (Pen Reset, then Press and Hold Vol Down and Back) (Back = Small Arrow above "End Call" Button) to Initiate ROM Flash

I dont know, just press the buttons, they are in the same place on every Diamond.

Im really sorry to say this but you havent asked one question here, and all of your errors and questions have been addressed in the thread and the instructions.

I can only suggest you read the instructions and follow what they ACTUALLY say, not what you have done.

MG

[gozeff]

quote:
6b: type "set 14 0" without the quotes to tell bootloader to boot the OS after reset:

---------------------
MTTY OUTPUT:
---------------------
CMD>set 14 0
HTCST UEHTCEUSB>
---------------------


my device behaves differently. it says:
----------------
Cmd>set 14 0
HTCST ÚÈÒHTCE
Cmd>
----------------
should i go on with the process? i just wanna be sure it won't damage the device. thanx in advance.

[Riel]

what are you talking about?

how can the old rom be installed when you have just formatted with MTTY?



Why are you doing this without knowing what your doing? also if your using this thread you should know why your performing these actions!!

THe reason for this is VERY well documented on this site, and can be easily found if you read the first post of most ROMs, here is an example from the BSB thread:






Firstly, why MTTY, flash a rom then MTTY again? why are you doing this? it does not say anywhere to do this.

It is quite obvious why this has happened, the first ROM was Smaller then the second one you flashed.

why would you do this?




I dont know, just press the buttons, they are in the same place on every Diamond.

Im really sorry to say this but you havent asked one question here, and all of your errors and questions have been addressed in the thread and the instructions.

I can only suggest you read the instructions and follow what they ACTUALLY say, not what you have done.

MG


It's not that I didn't know what i was doing, in fact, used MTTY a lot. This morning I was thinking what info the hard-reset was trying to write, but it doesn't :)

I was wondering why to hard reset first, and then engage the flash procedure from NAND, and not immediatedly start the flash procedure?

So all my questions were stupid, and the different sizes are obvious to me now :)

Sorry bothering :p

[Riel]

But still:

This is whats actually happening throughout the process:
-------------------------------------------------------
1: Enter bootloader
2: MTTY
3: Hard-Reset
4: Flash ROM
5: Hard Reset

the effect of this process is:

1: Bootloader gives access to the NAND
2: MTTY formats the NAND (removes the existing rom)
3: Hard-Reset clears the device and partition
4: Flash sends ROM to NAND
5: Hard Reset cleans out the files left over from the flash.

does that make it clearer?

MG
-------------------------------------------------------

But what I meant to point out:

1: OK
2: OBVIOUS
3: IT REINSTALLS THE LAST ROM? (Back to factory settings, progress bar)
4: FLASHES NEW ROM FROM DIAMIMG.nbh
5: IT INSTALLS FLASHED ROM

Or do I see that wrong?

[4D3]

quote:
6b: type "set 14 0" without the quotes to tell bootloader to boot the OS after reset:

---------------------
MTTY OUTPUT:
---------------------
CMD>set 14 0
HTCST UEHTCEUSB>
---------------------


my device behaves differently. it says:
----------------
Cmd>set 14 0
HTCST ÚÈÒHTCE
Cmd>
----------------
should i go on with the process? i just wanna be sure it won't damage the device. thanx in advance.


Hi,

if you read the thread, the outputs displayed by mtty sometimes vary dont worry bout it.

MG

[4D3]

It's not that I didn't know what i was doing, in fact, used MTTY a lot. This morning I was thinking what info the hard-reset was trying to write, but it doesn't :)

I was wondering why to hard reset first, and then engage the flash procedure from NAND, and not immediatedly start the flash procedure?

So all my questions were stupid, and the different sizes are obvious to me now :)

Sorry bothering :p

No problems!!



3: IT REINSTALLS THE LAST ROM? (Back to factory settings, progress bar)



No, this resets factory settings of a ROM is present on the NAND, if there is no ROM present, all settings are ZERO, resulting in the device clearing any files left by MTTY.

then you flash to a completely empty NAND with your new ROM, and this is what stops the bloated ROM effect, which is caused by fragments of previous roms being left on the NAND and interfering with the new rom!

MG :)

[Riel]

I am sorry if I don't get this :) But:

when formatting the NAND, the 'previous' rom is not gone, it is still sitting somewhere (since I can recover it by hard reset?).

No, this resets factory settings of a ROM is present on the NAND, if there is no ROM present, all settings are ZERO, resulting in the device clearing any files left by MTTY.

Than resetting should not make my phone boot at all before flashing a new rom?

It still does here ...

so:
when I task 28 55aa?
reboot with task 8

perform a hard reset (writing zero)

it will boot the previous rom! (preparing device for first use blabla)


Are there different places where rom-info is stored?
When I flash a nbh file, is it going somewhere else first?

[moeper]

Hi mystic,

how do I know, if the ROM flash happend? I do all you descrip, but at the point "press vol down + back arrow" everything is going very fast and I can´t believe, that the flash worked, how do I know if flash worked or I only start my old flash with some hard reset problems...???
THX

[4D3]

Hi mystic,

how do I know, if the ROM flash happend? I do all you descrip, but at the point "press vol down + back arrow" everything is going very fast and I can´t believe, that the flash worked, how do I know if flash worked or I only start my old flash with some hard reset problems...???
THX

the flash from internal storage should only take 2-3 minutes!!!

it takes 10-12 from USB!

if you followed the instructions ytou will have sucessfully flashed your phone!

Congrats

MG ;):)

[moeper]

is there a visual recognition? Cause I think after pressing Vol Up the phone directly reboots and start the old flash and nothing real happens withal pressing minus + right...mhhh....cause I have the problem with my flash that it says two theys one after another, "phone could not boot correctly, press send du reset or some other key to continue [...]" and after pressing some key it has done half a hard reset and 75% of data were lost...very strange...hope this is done by now, or I did it not correctly and don´t have a real mtty flashed mobilphone...

[eruvaer]

Hi MysticGenius,

first thanks a lot for this thread, helped me to fix some strange problems with my diamond :).

As a suggestion, could you add to your first post that this also works out of box with windows xp? Because I first tried several times with windows 7 and didn't get the drivers to work, till I read somewhere else that it should work with xp w/o installing drivers. Tried it and had no problems. Voted for sticky :).

Greets Eruvaer

[4D3]

Hi MysticGenius,

first thanks a lot for this thread, helped me to fix some strange problems with my diamond :).

As a suggestion, could you add to your first post that this also works out of box with windows xp? Because I first tried several times with windows 7 and didn't get the drivers to work, till I read somewhere else that it should work with xp w/o installing drivers. Tried it and had no problems. Voted for sticky :).

Greets Eruvaer


Sure thing!!

MG

[ascorpion]

I've got some problems with my MDA.
In mtty output i get 'Total Bad Block in CE: 1'. Tried many times. It happens all the time. Then i tried 'task 29' (thx to cmonex for tip but still no results)

Maybe i paste whole mtty output and somene could help me and other people who gets those message.


Cmd>set 14 0
HTCST ÚČŇHTCE
Cmd>task 28 55aa
Format start
Fill RSVD information for block 288 to 321
Storage start sector=0x7700, total sector=0x13000
Storage start block=509, total block=1216
Total Bad Block in CE: 1

Erase physical block from 800 to 2048

Format end

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 339 FAIL !!!
Write 0xFF start page=0x5040, total page=0x1AFC0
Format BINFS end

Cmd>task 8

Hope someone can help, Regards.

PS,
I use Hard SPL 1.93, phone is SIM UNLOCKED. I use cooked ROMs like Nataly and Cloudy 1.3.
Tried upgrading to STOCK rom but after a week i got random hard reset with Error which is show in the picture.
http://img3.imageshack.us/img3/8812/snc00049a.th.jpg (http://img3.imageshack.us/i/snc00049a.jpg/)

[4D3]

I've got some problems with my MDA.
In mtty output i get 'Total Bad Block in CE: 1'. Tried many times. It happens all the time.

Help with what? just flash a different rom!

the error you show in the pic is caused from a Manila 3D error, flash to a different rom!!

No-one can do anything about bad CE block, also if you read the thread this has been covered a few times


Then i tried 'task 29' (thx to cmonex for tip but still no results)

Dont know why you would do this, this formats the BinFS not the NAND!!


Maybe i paste whole mtty output and somene could help me and other people who gets those message.
Hope someone can help, Regards.


I still dont know what exactly you want help with?

MG

[ascorpion]

Just wanted to know how to format and clean phone with mtty when i get bad CE block...
but if you say no-one can do anything with this.
Thanks for answer

[4D3]

Just wanted to know how to format and clean phone with mtty when i get bad CE block...
but if you say no-one can do anything with this.
Thanks for answer

As i said if you read the thread, there has been 2-3 people mentioning that they have some bad blocks, even some CE block errors.

but as long as you can flash your device!!

MG

[pietvu]

In the tutorial it said type but i used copy paste. That’s why it did not work. I hope my comment saves other people some time.

Thank you for the description.

[4D3]

In the tutorial it said type but i used copy paste. That’s why it did not work. I hope my comment saves other people some time.

Thank you for the description.



It says all the way through the instructions "type" did you read them?

6b: type "set 14 0"

6c: type "task 28 55aa"

6d: type "task 8"


MG

[puredreamz]

I am running Windows XP but I cant find "USB" as a selction when running mtty1.42. Is there something I'm doing wrong? Should I install a driver? If so which one does my XP require? Thanks

[4D3]

I am running Windows XP but I cant find "USB" as a selction when running mtty1.42. Is there something I'm doing wrong? Should I install a driver? If so which one does my XP require? Thanks



NOTE: WORKS WITHOUT DRIVER INSTALL ON XP

Read the posts, i will help but evidently you have not read the instructions.

MG

[puredreamz]

Read the posts, i will help but evidently you have not read the instructions.

MG

I have read the instructions many times MysticGenius but I still dont know what I am doing wrong. I did notice that it said on XP you dont need to install the drivers. Does that mean skip post 2 entirely? Either way I tried putting my device in bootloader and restarting and my computer does find an unknown device but when I run mtty I still dont get that USB selection that post number 3 and 4 talk about. Please tell me if I have missed something.

[4D3]

I have read the instructions many times MysticGenius but I still dont know what I am doing wrong. I did notice that it said on XP you dont need to install the drivers. Does that mean skip post 2 entirely? Either way I tried putting my device in bootloader and restarting and my computer does find an unknown device but when I run mtty I still dont get that USB selection that post number 3 and 4 talk about. Please tell me if I have missed something.


well the only thing i can think of is:

when your using XP you need to load active sync and de-select "Allow USB Connections" then reboot and try mtty.

other than that you will have to PM me as this thread is for Vista and Win7!

MG

[gsmdb]

well the only thing i can think of is:

when your using XP you need to load active sync and de-select "Allow USB Connections" then reboot and try mtty.

other than that you will have to PM me as this thread is for Vista and Win7!

MG

The other way is more simple, don't change anything from default. Just load active sync. Choose File-Connection Settings, run Connect, click Next. Active sync detects all connections. Leave the window (don't CLOSE it), run mtty and usb is recognized

[moeper]

7: Immediately DISCONNECT your device and Hard-reset (Pen Reset, then Press and Hold Vol Down and Circle) on completion "Press Vol Up To Boot" Is displayed, press "Vol Up" and IMMEDIATELY press 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.

I tried point 7. after all points on two phones, a friend tried it too, but we are not able to initiate ROM Flash, the old rom is still flashed, nothing happends....my problems with the phone are gone away since mtty and hard reset, but the part with flashing a rom from internal storage, that doen´t work, someone has the same problems?

[4D3]

I tried point 7. after all points on two phones, a friend tried it too, but we are not able to initiate ROM Flash, the old rom is still flashed, nothing happends....my problems with the phone are gone away since mtty and hard reset, but the part with flashing a rom from internal storage, that doen´t work, someone has the same problems?

ROFL!!! I do this daily and it DOES work! I can tell you have not bothered reading the thread as you would know that this is a completely tried and tested method!

PEOPLE: we have a P.I.C.N.I.C Error!!

(Problem In Chair Not In Computer)

Have you actually copied the new rom you wish to flash to your internal storage?

MG

[herpez]

Hi. I can succesfull install the driver and have USB on the software, however, when i tipe


6b: type "set 14 0" without the quotes to tell bootloader to boot the OS after reset:

And the other commands, it doesnt outup nothing, just:

CMD>

...

What can i do?

Thanks

[4D3]

Hi. I can succesfull install the driver and have USB on the software, however, when i tipe


6b: type "set 14 0" without the quotes to tell bootloader to boot the OS after reset:

And the other commands, it doesnt outup nothing, just:

CMD>

...

What can i do?

Thanks


hi,

are you typing the commands not pasting them in?

maybe try restarting MTTY?

I have never experienced this and it has never been mentioned in the thread!!

MG

[herpez]

hi,

are you typing the commands not pasting them in?

maybe try restarting MTTY?

I have never experienced this and it has never been mentioned in the thread!!

MG


My bad!
Sorry :(

Too noob error. I was Copy and paste, now i made it

Really THANKS!

[donald-c]

A lot of things on this for my device were not perfect but so far it seems to have worked, flashing new ROM now :)

Hopefully it'll fix the many issues I've been getting :(

[Riel]

Can this be stikied ? Searched my ass off to find it back :)

[blueeagle]

very usefull thing! thank you very much!

[4D3]

Can this be stikied ? Searched my ass off to find it back :)


AGREED!!!


Glad you found it useful!!

MG

[Riel]

AGREED!!!


Glad you found it useful!!

MG

I do it every time when I flash a rom. And searching for this topic is a pain in the ass. Try it :)

I can't remember the commands, so well it should be stickied. Why isn't it? There are far more unused topics stickied.

[tombrighteyes]

i had some trouble at first..
im running on my sisters xp at the moment and well it doesn't need the drivers so i thought that was a good thing. and well it is
but it would be great if you put on the post to remember to disable the usb on activesinc i was wondering for a while why it wasn't showing me the USB option.

allmost gave up.

but i did it finally and flashed my rom and everything. i'll see if it worked with the hard reset and feezing at reboot problems ive had. (what can i say, i like to flash alot)

if anything still keeps happening ill post an update or something.
i noticed the problems i had which made me go to this on the BsB 6.5 WWE ROM
just if anybody is interested in knowing :)
maybe its its too much info.. but its better then not getting enough :P
thanks again :)

[zindo]

i use vista on my pc...i have this problem when i install the driver...

231731

version of the driver

231732


problem is with the error10

where is the matter??? :mad:

[jarino]

hi.

I've 32-bits version of Windows 7.

I can't find drivers to W7 and I didn't find the RIGHT answer what I must excactly do when I've W7 for good working of MTTY.

ps. I've tried with x64 with F8.. didn't work correctly...

[Hellas4]

Hello there!
Trying days now to update the active sync driver and the the messege i receive is " The device cannot star (code 10) "

Any Help??

[4D3]

hi.

I've 32-bits version of Windows 7.

I can't find drivers to W7 and I didn't find the RIGHT answer what I must excactly do when I've W7 for good working of MTTY.

ps. I've tried with x64 with F8.. didn't work correctly...


ok, firstly open eyes!!

driver are in the second post: x86 Active Sync Drivers.zip (http://forum.xda-developers.com/attachment.php?attachmentid=208451&d=1248436681)

second, why are you using x64 drivers on 32 bit win 7?

and to get mtty working follow posts 2 & 3

MG

[4D3]

i use vista on my pc...i have this problem when i install the driver...

231731

version of the driver

231732


problem is with the error10

where is the matter??? :mad:


i cant read Italian! i cant read the error message, if you can translate i will help!

(this method does work, it has been tryed and tested MANY MANY times and errors only occur when posts 2 & 3 are not followed EXACTLY)

MG

[4D3]

Hello there!
Trying days now to update the active sync driver and the the messege i receive is " The device cannot star (code 10) "

Any Help??


you need to provide more info into the error!!

how is the error occuring? what steps are you taking to get the error.

are you following posts 2 & 3 exactly? (if you miss/change/overlook ANY step this WILL fail!)

MG

[Joh@n]

Yesterday I followed all the steps in the first posts of this thread and I must say it was all clear to me. The reason I searched for this topic is that my Touch Diamond has a little problem. When it starts up, it will show the Windows Mobile screen, start the today screen...and after 2 seconds reboot itself again and again. I heard from another user the MTTY process could fix these kind of issues, so, happy me :)

After flashing the new ROM all went well yesterday evening, until this morning. The thing I had noticed yesterday during the MTTY process is the following. One of the steps returned this value:

Total Bad Block in CE: 1

I think this is the issue my TD is fucked up again now. Is there anything in MTTY to fix this issue? Or should I flash the original ROM and send it to HTC?

EDIT: Ah well, I see in this thread that it should not be an issue, because I can flash my ROM. But it still keeps rebooting and after a hard reset it is very, very slow..

[zindo]

i cant read Italian! i cant read the error message, if you can translate i will help!

(this method does work, it has been tryed and tested MANY MANY times and errors only occur when posts 2 & 3 are not followed EXACTLY)

MG

i resolve it!!!i follow exactly the post 2 & 3!!now works perfectly!!you're so great

:)

[Hellas4]

Tryed it STEP BY STEP 10 times following all the procedures exaclty and all the times i get this message.. anyone pls help,
i am using Windows 7 RC x86 English

[chowdarygm]

Tryed it STEP BY STEP 10 times following all the procedures exaclty and all the times i get this message.. anyone pls help,
i am using Windows 7 RC x86 English

me too facing the same problem...........plz help

[rikkiepikkie]

Hi I got stuck on step 6a. If I press "enter" I don't get a prompt and can't type anything.

I'm using windowsXP....Hope someone can help me. Thanks in advance!!

[awaisanwaar]

hi! I wann ask few questions about this mtty as I am a newbee :P
what kind of drivers are prohibit to have in the windows xp ? I mean , drivers of usb shouldn't be installed or other drivers like of graphics ??

last thing I wanted to ask is that it is compulsory to formet internal storage via mtty or its just a option that mmty can also do ? and what are these bad sectors like that

Total Bad Block in CE: 1

is this a normal result of process or something is done wrong with e process ? if something is done wrong then how it could be resolved safely ????

waiting for your answers...
regards!

[Novski]

me too facing the same problem...........plz help


Same problem here! help needed!:confused:

[shafirin]

Thanks for your valuable time spent for finding the way to fix bad blocks. Great.

[Blahzay]

Thanks alot man worked great for me on Win 7 x64. Great guide.

[deepthroat]

thanks Mystic, this is definitely definitive ! :D

[Kappalainen]

I had the same problem as some of you, that when I installed the dowloaded driver (and by the way, I have W7 32-bit) it said, that device could not start. I tried to open mtty anyway and noticed that it had no USB-option to choose (surprise, surprise...). Then I actually accidentally opened the original Active sync control center and enabled the "Allow USB connections", just for fun. After this I was compleately stunned, that the USB-option came available in mtty. I have absolutely no logic to why this happened. The date on the driver says somethingsomething.2004 and not 2003 as it says it should be.
Regardless I managed to use the mtty successfully. If someone really knows why something like this happened, please enlighten us :)

[Hellas4]

I had the same problem as some of you, that when I installed the dowloaded driver (and by the way, I have W7 32-bit) it said, that device could not start. I tried to open mtty anyway and noticed that it had no USB-option to choose (surprise, surprise...). Then I actually accidentally opened the original Active sync control center and enabled the "Allow USB connections", just for fun. After this I was compleately stunned, that the USB-option came available in mtty. I have absolutely no logic to why this happened. The date on the driver says somethingsomething.2004 and not 2003 as it says it should be.
Regardless I managed to use the mtty successfully. If someone really knows why something like this happened, please enlighten us :)

Ohhh!!! So... i'm trying to find where this option is "Allow USB connections" and i can't find it! can you enlight me first!! ??

[Kappalainen]

Ohhh!!! So... i'm trying to find where this option is "Allow USB connections" and i can't find it! can you enlight me first!! ??

I actually just did a windows search with the words Active sync. It found the .exe to change settings for it. Do you have the Active sync software installed? Don't even know if its relevant to have it, but that's where i found the option to allow or disallow USB-connections. Can't tell you the exact name because I have a finnish version :)

[usama ali]

thanks MysticGenius

i used to read that the members' diomand always hard rest itself . i never had this problem but recently i had this terrible problem , then i uesed your MTTY and it worked :). now my diamond is back to life again(thanks to you)

sorry for my poor English

[donald-c]

Tryed it STEP BY STEP 10 times following all the procedures exaclty and all the times i get this message.. anyone pls help,
i am using Windows 7 RC x86 English

I get the same problem, I installed MTTY before and it just seems to be, gone... Now my phones f***ed up again, (installed a stock ROM and flashed ONE ROM and it constantly needs the ROM flashed to boot...)
Done everything according to the guide :/

Edit: As soon as I finished typing that and pressed save it worked lol, disconnected my phone and reconnected it and it worked?

[max3o6]

I lucking fove you guys...

:):D:):D:):D:):D:cool:

[vajra25]

is it the same way to use with xperia?
thanks

[michi3l]

IT doesnt say 2003.... But 2004, is that a problem or can i continue?

[Darren8448]

Im running vista 32 so I dont need to install any drivers.

Ive enetered bootloader, changed to usb. Run mtty.exe clicked ok but in the new windows I cant type a single letter??? I can copy and paste but obviously then cannot <enter>???


Any advice??

[diabolik]

I followed the 2 1st post but when I reconnect the diamond to the PC remains in serial it does not get in usb
please help
i'm on win 7 with driver for win 7

[michi3l]

IT doesnt say 2003.... But 2004, is that a problem or can i continue?

Anyone?? :confused:

[Nirak]

Anyone?? :confused:

You can continue, the 'trick' is that you'll be able to choose USB in MTTY application.
Thanks to this thread i rescued another Diamond yesterday and saw the same driver year.
Running windows 7RC x86 (32bit)

[Nirak]

Im running vista 32 so I dont need to install any drivers.

Ive enetered bootloader, changed to usb. Run mtty.exe clicked ok but in the new windows I cant type a single letter??? I can copy and paste but obviously then cannot <enter>???


Any advice??

forgive if this is a stupid q, but did you hit the 'enter' first (to get the 'cmd>' in MTTY)?

[Darren8448]

forgive if this is a stupid q, but did you hit the 'enter' first (to get the 'cmd>' in MTTY)?

thats the issue I cant press enter?!? or type anything at all?!?

[michi3l]

7: Immediately DISCONNECT your device and Hard-reset (Pen Reset, then Press and Hold Vol Down and Circle) on completion "Press Vol Up To Boot" Is displayed.

When is disconnect after " task 8" and do hard reset i can only reset data, and it doesnt say reboot or something? Whats the problem? :(

[rikkiepikkie]

thats the issue I cant press enter?!? or type anything at all?!?

Same problem here: winXP

[sieu_sury]

My diamond is error with code format!!!
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!

somebody help me?:confused:

[4D3]

IT doesnt say 2003.... But 2004, is that a problem or can i continue?

No thats not a problem, i updated the drivers but i didnt update the image"!!

no issue!

sorry for late reply, I only just got back from hols.

MG

[4D3]

Im running vista 32 so I dont need to install any drivers.

Ive enetered bootloader, changed to usb. Run mtty.exe clicked ok but in the new windows I cant type a single letter??? I can copy and paste but obviously then cannot <enter>???


Any advice??


Hi sorry for late reply, but the only OS that needs NO drivers is winXP!!

if your using vista u need drivers! read the posts!!

;)

Same problem here: winXP



NOTE: WORKS WITHOUT DRIVER INSTALL ON XP



this thread is for Vista and Win 7, XP has no known issues (it has been like this for years!!) also XP does not need drivers installed! the only thing with XP is you need to load ActiveSync and select "Disallow USB Connections"

Other than that i can offer no help as i do not have XP installed and i have not got the time/space on my Lappy to get it on! there is already 4 OS's

MG

[4D3]

I followed the 2 1st post but when I reconnect the diamond to the PC remains in serial it does not get in usb
please help
i'm on win 7 with driver for win 7


what version of 7 are you using?

I have an Official (i.e. not an internet leaded release, it is the version that will be available on the 22rd) release of Windows 7 x64 & x86

My system is quad booting with Win7 x64 & x86 and also Vista x64 & x86 and it have this working on all 4 OS!

if you dont get the USB option you HAVE done something wrong while following post 2!

MG

[4D3]

My diamond is error with code format!!!
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!

somebody help me?:confused:


how did you get the error, i need to know the steps if im to help you out!!

MG ;)

[4D3]

7: Immediately DISCONNECT your device and Hard-reset (Pen Reset, then Press and Hold Vol Down and Circle) on completion "Press Vol Up To Boot" Is displayed.

When is disconnect after " task 8" and do hard reset i can only reset data, and it doesnt say reboot or something? Whats the problem? :(


Im sorry but i do not understand.

task 8 reboots the device immediately then you need to hardreset, then perform the flash from internal storage, then hard reset again then allow the device to boot!

Hope that helps

MG

[sieu_sury]

how did you get the error, i need to know the steps if im to help you out!!

MG ;)

my diamond only show boots first splap. i have updated ROM SHIP 2.03 for diamond and ROM cooks but it still too. Now it only into Bootloader and conneted with USB! i bad:(
Is it died DOC?

please Help me!!!

steps! i enter "task 28 55aa"

Cmd>task 28 55aa
Format start
Fill RSVD information for block 288 to 321
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
Format end

Cmd>

[dchegini]

My PC OS is Win XP but there is no USB in the MTTY menu, since on Win XP no driver is required, what shall I do to perform MTTY?
(Hard SPL unsigned Olinex 1.93 )

[4D3]

My PC OS is Win XP but there is no USB in the MTTY menu, since on Win XP no driver is required, what shall I do to perform MTTY?
(Hard SPL unsigned Olinex 1.93 )

As i said previously:

the only thing with XP is you need to load ActiveSync and select "Disallow USB Connections" then reboot.

Other than that i can offer no help as i do not have XP installed and i have not got the time/space on my Lappy to get it on! there is already 4 OS's



I have never heard of anyone using XP having issues with MTTY so no-one has really looked into it

[sieu_sury]

please Help me!!!

steps! i enter "task 28 55aa"

Cmd>task 28 55aa
Format start
Fill RSVD information for block 288 to 321
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
Format end

Cmd>

==> died CHIP DOC!???

[ozzybulldog]

Hi, thanks for your topic and your mtty explanation, but I also get the same error:

Cmd>task 28 55aa
Format start
Fill RSVD information for block 288 to 321
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
Format end

Oz

[BeneX1]

Hello,

i can't see the USB port under MTTY 1.42 and XP SP3.

Device Manager shows a Windows CE USB Device -> PocketPC USB Snyc, when i connected Diamond in Bootloader Mode (Hard SPL 1.34).

I installed none of the drivers, as it is not neccessary for XP (btw. ActiveSync ist installed and working).

XP System and MTTY output see attached screenshot.

EDIT:
I just needed to kill wcescomm.exe from ActvieSync. Now it's working!

[cippalippa00]

Tryed it STEP BY STEP 10 times following all the procedures exaclty and all the times i get this message.. anyone pls help,
i am using Windows 7 RC x86 English
I have the same problem...no solution? :(

[quendil]

Hi everyone. i have an idea/question. what if after the task 8 command we skip the hard reset and we proceed straight to the rom update process? that can happen if after the task 8 command we hold down volume down and back button.after all the hard reset doesnt seem to serve any specific task.
so, what do you think?

[4D3]

Hi everyone. i have an idea/question. what if after the task 8 command we skip the hard reset and we proceed straight to the rom update process? that can happen if after the task 8 command we hold down volume down and back button.after all the hard reset doesnt seem to serve any specific task.
so, what do you think?

No!!

If i thought that would work in every instance i would have written that into the instructions.

Many (uninformed) people like you have asked this repeatedly throughout the thread, so i can assume that you also have not read the thread.

This works so im not changing it.

[quendil]

Fair enough and true i havent read all threads.
But i like experimenting and since it worked for me once i tthought about posting about ot.
Thanx anyway for your quick answer.
Cheers!

[Demon_man]

excellent guide had no choice to do this thank you very much worked like a charm :)

+1 to you

[J0nas]

I'm sorry, but what a difference between "normal" flashing via internal storage and this process?

Sorry my english...

[lordgarret]

i've tried the procedure on post 3, but i have a problem:
i've winXP, so i shouldn't install any driver, but i can't chose the USB option in the first screen of the mtty1.42.exe...!
what does it mean? what should i do?
thx

[kgerry]

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

[lordgarret]

thx i'll try...
now i've just flashed without this system and i haven't problem...

[willsonb_987]

BUMP!. Please can admins make this sticky?