Related
I just post this thread in order to help others which are having the same problem as I am and to avoid looking arround on all the posts for this answer.
I'm so happy that I've not yet test this procedure wanted to share with you ASAP.
Thanks pvdhelm
pvdhelm said:
Follow these instructions and your vista problem is over.
I used this guide and it works for my artemis p3300 phone!
Please try downloading the latest WMDC first before attempting anything in this section of the guides. you will find the latest version HERE .
To follow this guide please make sure you have a copy of WinRAR installed, I will refer to the Windows Mobile Device Centre as the WMDC for ease of reading. If you do not have the WMDC installed please go here to install it first.
One problem with windows VISTA is that it uses the new "Windows Mobile Device Centre" and not activesync which we are used to, thus our standard RUU programs will not upgrade our Hermes devices as in windows XP. This guide will show you how to configure VISTA to work just the same as XP with our RUU programs.
For this guide firstly you need to download the new drivers:
Drivers for Windows Vista x32
Drivers for Windows Vista x64
Please note the x64 drivers are unsigned so to use them successfully you must disable driver signing.
Extract the contents to a folder on your desktop, call this folder "AS_DRIVERS". It contains the drivers from activesync which we will use instead of the native VISTA WMDC drivers when the device is in bootloader.
Now you must enter the bootloader on your device, to do this press and hold both the side ok button and the power button then put your stylus into the hole on the bottom of the device, your device will reset and show the red blue green bootloader screen. LEAVE THE DEVICE IN BOOTLOADER MODE and connect it using the USB cable to your VISTA PC.
Now navigate into the WMDC (Start>All Programs>Windows Mobile Device Center) and click on the "connection settings" menu icon
In the connection settings menu untick "allow USB connections" then press OK.
Now exit the WMDC and return to the desktop, go into the start menu and type "Services", this will take you into the local services dialogue and show a list of all services either running or registered with your pc.
Scroll down the list and make sure these services are present:
Windows Mobile-based connectivity
Windows Mobile 2003-based connectivity
If these services are not started then double click each one and set them to Automatic start by clicking the "startup-type" drop-down menu and selecting automatic then click the start button in the same window, apply the setting by pressing OK. Now return back to the desktop again.
Go into the start menu and type "Device Manager" then run, this will take you into the device manager. Click the "+" symbol next to "Mobile Devices" and double click on "HTC USB Sync".
This will bring up the properties of the currently connected device (the hermes in bootloader).
Go to the "Driver" tab and click "Update Driver".
Click "Browse My Computer for Driver Software".
Select "Let me pick from a list...."
Click the "Have Disk" button.
Click "Browse" and navigate to the AS_DRIVERS folder we created earlier.
Vista x32 users select the file "wceusbsh.inf"
Vista x64 users select the file "wceusbshx64.inf"
Then click Open.
click next and the driver will be installed (wait a moment).
Press close and escape back to the desktop now.
Now we must stop the WMDC process, start the task manager by pressing Ctrl+Shift+Escape.
click the WMDC line and click "End Process". In the confirmation window, again press End Process.
Now re-enter the WMDC and re-enable USB connections (click connection settings and tick the box "enable USB connections").
Your RUU programs for HardSPL/Radios/WM6 ROMs should now run as desired once you are synced with WMDC. Since we have updated the driver which vista uses when the device is in bootloader mode.
NOTE:: This technique is still in testing so if you have any issues please post in the official thread. Until we find another way to get RUU working with vista you may need to revert back to XP for upgrading your Artemis.
Click to expand...
Click to collapse
Just test it without any problem. I confirm the feasability of this procedure.
It rocks!
Always restart after before trying. It has worked with me.
Ha, Well I have tested and all works well, after this I've flashed USPL and B&B 3.7 ROM with no difficulty.
Now if I could only figure out why Mobile device Center will not install properly on my Vista Ultimate that I just 'upgraded' to today. It connected once, ran the sync but did not back up the contacts on my phone to outlook, and now on subsequent tries, the program wont open because of 'unknown problems'.
Maybe it's a sign to roll back to XP.
uninstall wmdc and then re-install. I had this error at first but fixed now.
Shand359 said:
uninstall wmdc and then re-install. I had this error at first but fixed now.
Click to expand...
Click to collapse
I had a feeling, I did that procedure once already with redundant results....but then again, half of my peripherals such as DVD-ROM, or wireless card didn't work, but then miraculously started working just as I was about to teach my laptop how to fly.
I will keep trying, thank you.
itschase said:
I had a feeling, I did that procedure once already with redundant results....but then again, half of my peripherals such as DVD-ROM, or wireless card didn't work, but then miraculously started working just as I was about to teach my laptop how to fly.
I will keep trying, thank you.
Click to expand...
Click to collapse
I'm not sure if that is the problem, but did you tried after restart vista?
When I made the procedure it was not working and then tried to restart and it was perfect.
Bluetooth sync works fine, but USB won't load driver. WM5 OEM, so no bootloader on my 8525. Will this solve my USB problem?
Hmm .. tried to follow the process above and Vista told me I already had the most recent version of the driver .. strange huh ?
For French :
http://www.forummobiles.com/index.php?showtopic=136003&hl=nuls
scratch that .. i missed a bit
Shand359 said:
uninstall wmdc and then re-install. I had this error at first but fixed now.
Click to expand...
Click to collapse
Agreed. Some 'versions' of windows Vista have WMDC built in, it is no good, uninstall WMDC and download the version from MS web site. Once installed run Windows Update.
owencutajar said:
Hmm .. tried to follow the process above and Vista told me I already had the most recent version of the driver .. strange huh ?
Click to expand...
Click to collapse
I had this issue too, uninstall vista drivers first, then install those from XP.
I followed these directions to update my Himalaya/Alpine-like i-mate PDA2 with disappointing results -- at first. WMDC claimed there was an error and I could not get it to respond. I flounced away and pouted for a little bit, and when I came back decided the only thing I could think of to change now before re-installing WMDC altogether was to roll back the driver for the mobile devices (in device manager) and WA-LA! Pouting works! I am now able to sync and Klaus (the i-mate) plays nice with Bob (PC)... ah, household bliss!
Thanks!
i still cannot get my laptop to see the artemis when it is bootloader mode - i have the XP driver on!!!!
I would love to try it, but does anybody have a german manual, or a translation program that translates Windows English into Windows German?
Hello, I tried updating my trinity on vista 64bit using a guide from trinityguides.info and the 64bit drivers I found there.
I just can get an further updating because my HTC usb sync driver says something about an error code 39
Is there any way to avoid this?
I've already tried updating wm6 trough a memory card "by renaming RUU_signed.nbh to TRINIMG.nbh
like described on Wiki Trinity SDCardFlashing" but i didn't worked
Btw. I've only got vista 64bit and OSX(using a macbook) so I hope i don't also have to install an windows 32bit version
Thanx in advance for any help or tips!
sorry you're having trouble.. if you have a problem it's better to post within the guide thread, than start a new one. Can you tell me what the error says exactly when it comes up?
have you disabled driver signing?
*update* i've been scouring the net for an answer, but only a handful of ppl have experienced this problem, and so far can't find any posts with the solution. There definitely are some ppl having trouble with the x64 driver. Post if you find anything, and i'll do the same
sspl
I had the same problem trying to install it with a sd-card.....
just download SSPL-TRIN.exe from this post http://forum.xda-developers.com/showthread.php?t=293632&highlight=sspl and put it in the root directory of your sd-card with the TRINIMG.nbh file....
i am hoping you stil have a wm5 or wm6 installed...when you insert your card go to the root directory of your card then dubble tap on the SSPL-TRIN.exe it wil pop up in installer mode and then press power to install......
Het heeft voor mij gewerkt......
Thanx for the info but i can't disabled driver signing on my Vista ultimate, seems like the guys from Microsoft disabled this funtion with their latest updates
Does somebody have any solution for this?
@TheBlackDragon:
Seems like this method doesn't work with wm6,I've got MuN 2.01.TE installed on my device.
The phone still works but I would like to put the official wm6 rom on it!
Btw. I've now got the follow SPL:
TRIN100
IPL-0.50
TRIN100
SPL-9.99.CP
let me look in to this.. can you please list the steps you tried to take to disable driver signing, so at least we know where you're stuck?
*edit*
ok, this is what i've got so far.. can you try these methods and let me know what works and what doesn't (i don't have x64). I guess we're looking for a permanent disabling of driver signing, cause some of these steps seem to only disable until reboot.
OPTION 1 - Bcedit
1. Create a shortcut on the desktop to cmd.exe
(this recipe explains how to create a shortcut if you don't know how)
Right click on an empty space on the desktop to open the context menu
Select New
Select Shortcut with a left-click
In the location box type cmd.exe
Select Next
Name your shortcut and push Finish
2. Right-click on the shortcut and select Run as administrator
3. When the command window opens, type or paste the following and press ENTER:
Bcdedit.exe /set nointegritychecks ON
4. Reboot and then try installing the driver
some people listed some variations on this method, they are as follows:
if the "bcdedit /set nointegritychecks ON" does not work, try "bcdedit -set nointegritychecks ON"
or try bcdedit -set loadoptions \”DISABLE_INTEGRITY_CHECKS”
(this seems to be a more permanent fix i guess)
OPTION 2 - F8
An F8 boot option introduced with Windows Vista—“Disable Driver Signature Enforcement”—is available to disable the kernel-signing enforcement only for the current boot session. This setting does not persist across boot sessions.
OPTION 3 - gpedit
open the command line again (i guess it wouldn't hurt to open with administrative priviledges as listed in option 1)
Navigate to User Configuration -> Administrative Templates -> System -> Driver Installation
enable the "Code signing for drivers" and then choose "Ignore".
Hello,
I have 3 month's ago flashed my htc 3300 with wm6 english (pdavliet).
I have used uspl and the wm6 rom.
Today i flashed my phone again but with wm6 dutch.
And now i can't start my phone.
When i push the startbutton the phone start in de startmenu with bleu screen wich is from 02 and the phone still hanging on that screen.
I think i broke my phone i must have do something wrong.
Is there anyone who can help to get my phone fixed without sending it to the manufacturier.
Please help me i turned my phone into a brick.
I am waiting for a response (i hope i get some)
I am from holland and my phone is from mda pro 3
Thank you all
try to hard reset, if not follow the instructions here http://forum.xda-developers.com/showthread.php?t=308242
HELP me please,
I've got the same problem... it was working perfectly but at same point it freezes!! I’ve tried a soft reset but didn’t work, then tried a hardware reset but it says “Format failed”. Really don’t know what to do!
Do I have to re-flash my artemis, can I do that even if it freezes at the splash screen?
P.S.: i have the B&B 4.2
Thx very much
follow the abovr link to reflash bricked devices
Is that meaning it is brikked?
But it worked for couple of months!
no it doesn't mean it's bricked but you can't hard reset.
Maybe you can try to use uspl on it and see if it succeds, if then try to reflash....
Thank you very much
Just a last question if you don't matter can I run the UPLS even if my PDA freezes when the Spalsh screen appears?
Thank you!
I think so as the phone stops to be flashed.
You can check if the activ sync icone is green.
On another forum a guy had a similar problem, he tried to hard reset about 20 times and it finaly passed
what if i would take off the battery for few hours?
Do you think it will erase everything like an hardware reset?
Act syn dosn't get green.... and 20 hardware reset are too much
Thank you!
removing the battery won't change anything, imagin if it goes down for a few days and you don't charge it.
It's a flash memory.
The only thing lesft may be to get into the bootloader and reflash
OK.... i connected my pda to my computer and i bootloaded! But my computer dosen't reconize it and so i cannot run the UPLS
Any idea?
Thank guys
No USPL, 1st reflash your p3000 with your ORIGINAL HTC orT-Mobile Rom and correct language. WM6 is just released officially so i should not be a problem to find your ROM. In the past this was the biggest problem (no way to get the original rom).
When this is done, then USPL and change to another rom (other language and extra cherrys!).
GL
edit: To do so, put the artemis in bootloader mode, connect to usb and start RUUGetInfo.exe. Wait and see what happens . Should work fine.
THANK!!!
i'll try!
yessssssssssssssssssss
Thank you all!!!
I solved my problem. I turned my brick into a phone hahahaahh
I am very happy
How to get in the bootloader menu?
Start your phone
hold speedialbutton and softreset but still holding the speeddial button and then the bootmenu will appair (dont forget the usb cable it must plugged in before you go in to the bootmenu)
How do i get the 'wceusbsh.inf' file?
On your cd from the phone.
Before starting: Your device needs to be connected to the PC, and in BOOTLOADER mode.
Step 1 of 16: Extract this zip file to a memorable location on your machine (e.g. the desktop). 'wceusbsh.inf' This is the Activesync 4.5 RTM USB driver.
[attachment=21151:VistaRUU.zip]
Step 2 of 16: Run 'Windows Mobile Device Center', and click 'Connection Settings'.
Step 3 of 16: Uncheck the 'Allow USB Connections' box, and select 'OK'.
Step 4 of 16: Run 'Services' by clicking the Start Orb and typing 'Services', and ensure the 'Windows Mobile-based connectivity' and Windows Mobile 2003-based connectivity' services are started. If they are not, click the service name and press the 'play' button on the top bar.
Step 5 of 16: Load 'Device Manager' by clicking the Start Orb and typing 'Device Manager'. Expand the 'Mobile devices' section and click the 'HTC USB Sync' (or similarly named) item.
Step 6 of 16: Click the 'Action' menu and select 'Update Driver Software'.
Step 7 of 16: Click 'Browse my computer for driver software'.
Step 8 of 16: Click 'Let me pick from a list of device drivers on my computer'.
Step 9 of 16: Click 'Have Disk'.
Step 10 of 16: Click 'Browse', and browse to the location where you extracted the ZIP' wceusbsh.inf' file in Step 1.
Step 11 of 16: Double click 'wceusbsh.inf'.
Step 12 of 16: Select 'HTC USB Sync' from the list, and click 'Next'.
Step 13 of 16: Wait while your driver is installed.
Step 14 of 16: Run 'Task Manager' by clicking the Start Orb and typing 'taskmgr'. Then find the 'WMDC.EXE' item, and click 'End Process'.
Step 15 of 16: Install your update! Everything should now run fine! You just need to bear in mind the final step when you want to start syncing normally again...
Step 16 of 16: In 'Windows Mobile Device Center', re-enable the 'allow USB connections' checkbox you disabled in Step 2.
This is a friendly warning to people who are new to the site/new to the thread.
There has been a LOT of unnecessary posts recently from people who cannot be bothered searching starting HERE ON PAGE 59 POST 581 onwards.
I will simply not reply or reply with "Search". Why should I help when people cannot be bothered ATTEMPTING to help themselves?
Also anyone thinking of asking either of the following questions:
1: "After task 29, I get this output in MTTY: Total Bad Block in CE: x"
2: "After task 29, I get this output in MTTY:
ERASE block xxx FAIL !!!
ERASE block xxx FAIL !!!"
(where x is a random number)
This has been asked 100+ times in this thread so this is the final time I will answer:
IT MEANS NOTHING..NADA..ZIP! I have not experienced ANY problem with this output...Please stop asking!
There is a LOT of information in this thread. All you need is the first 4 posts or the search button OR if it is a GENUINE problem post it and I will help!
------------------------------------------------------------
Hi,
Over the last couple of weeks, as all of us flashing junkies are continuously flashing devices there has been an increase in "Strange Problems" which to all intents and purposes are just “clog ups” and “bad flashes”
As we all know MTTY is the key here, but I can say from personal experience that this small piece of software is a MASSIVE pain in the ass to get working, i must have tried 15-20 different “recommended” procedures to get it work and all failed.
But I managed to find a failsafe method of getting MTTY working on Vista AND Windows 7, also x86 AND x64!! (I have all 4 windows installations and the methods detailed below worked on all)
NOTE: WORKS WITHOUT DRIVER INSTALL ON XP
If for some reason you cannot got this to work on XP do the following: (Thanks kgerry!!)
kgerry said:
Hi,
if you run XP and you have Problems to connect to USB try following:
1. Launch ActiveSync on PC
2. Go to connection settings
3. Uncheck the Allow USB Connection
4. bring the device to bootloader.
5. Now, run mtty ...
... try again to switch from COM1 to USB and follow the instructions of perfect post 3
Hope it helps ... Kgerry
Click to expand...
Click to collapse
Here is how this thread works:
Post 1: Description
Post 2: Driver Installation
Post 3: MTTY Instructions For FLASHING FROM INTERNAL STORAGE
Post 4: MTTY Instructions For FLASHING FROM YOU SYSTEM
THANKS to:
Reb0rn - for pointing me to the light!
l2tp - for the images
lunasea - for providing me with working drivers
and of course to anyone else I forgot.
I hope this helps people!!
MG
Driver Installation
Pre-Cursor To Driver Installation – FOR EVERYONE (x64/x86 Vista/Win 7)
This will remove the need for users, x64 in particular, to use “Unsigned Drivers.” Also since in Vista SP2 (x64 & x86) they removed the “F8” options Completely!
Files Needed:
Driver Signature Enforcement Overrider
Remove Watermark V0.8
1: Run the Driver Signature Enforcement Overrider and select “ENABLE TEST MODE” and Press Next
2: There will be a warning to REBOOT, Press “OK”
3: Go Back to Driver Signature Enforcement Overrider Select “Exit” then Click “Next”
4: Run the “Remove Watermark V0.8” for you OS type (x64 or x84)
5: In the Command Window type “Y” and wait for the process to complete
6: Once complete REBOOT your system and begin the driver install
NOTE: If you DO NOT complete the above, some users will need to press "F8" During Bootup - (ANOTHER NOTE FOR x64 USERS, EVERY TIME YOU NEED TO USE MTTY YOU MUST REBOOT YOUR COMPUTER, HIT F8 AND SELECT: "START WINDOWS WITHOUT DIGITALLY SIGNED DRIVER CHECK")
For Info See Post Below:
Reb0rn said:
I must just say that u might have to watch the x64bit drivers if they are digitally signed... Cuz neither Vista 64 nor Windows 7 64 will let u load or start those drivers if they are not digitally signed.
IF that the case and if u have installed the driver but it says that it has stopped it due to the driver not been Digitally signed u have to start windows vista/7 in "ignore digitally signed drivers" mode.
When u start the computer, keep hitting F8 and it will prompt you if u want to start in safe mode bla bla and in the bottom of that list there is an option that goes something like this:
Start Windows without Digitally signed Driver Check... or sumthing like that...
This is only if u have problems with the x64 driver... like i did...
BTW... u made a beautiful how-to man. Great job!
Click to expand...
Click to collapse
-----------------------------------------------------------------------
Big thanks to maybeme for providing a host for the images!!
1: Download the relevant drivers for your system attached to this post: these work for both Vista and Win7, all you have to choose is x86 or x64
EDIT: It has been found that with different versions of Windows 7 x64 need different Active Sync Drivers... If you are using Windows x64 please try x64 AS Drivers Win 7 Tested & Working.zip FIRST!!!
2: Connect Device to PC via Active Sync, Once Connected Uncheck USB Connections,DISCONNECT DEVICE then Reboot Computer
3: Bring device into bootloader (Reset + Hold Vol Down), This will show the Red, Blue, Green screen showing "Serial" - Once Computer booted, connect device in bootloader mode to USB, the word "Serial" will change to "USB"
4: Go to "Control Panel -> System -> Device Manager" and select Microsoft Usb Sync in Mobile Devices section (NOTE: This MAY say HTC USB Sync but as long as you select your device!!):
5: Right Click and Select "Properties" then go to Driver tab, then Select "Update Driver"
6: Choose to "Browse Computer For Driver" (the second option):
7: Select "Let Me Pick From A List...." (the second option):
8: Click "Have Disk":
9: Select the folder with downloaded driver From Step 1 and select "wceusbsh.inf" (this is the same file for x86 & x64):
10: You will get back to previous screen, then click Install
10a: WINDOWS 7 ONLY - The Below Warning will appear, Select "Install anyway":
11: The drivers will be successfully installed:
12: When you get back to "Driver Properties" check driver version. If the "Driver Date" has changed from 2nd step (2003 instead of 2007), the installation has been a success:
13: Lastly leave the device connected and in "Bootloader" and reboot you system. Upon Rebooting an "Unknown Device" is installed, this is your HTC device.
Now the Active Sync Drivers are Installed
MTTY - Flashing From INTERNAL STORAGE
Follow this procedure for FLASHING YOUR ROM FROM INTERNAL STORAGE AFTER MTTY
Before you start grab: mtty1.42.zip
AND ENSURE YOU HAVE HARD-SPL ON YOU DEVICE!!
Procedure:
1: Download a ROM of your Choice, RENAME the *.nbh for your ROM to: DIAMIMG.nbh
2: Copy DIAMIMG.nbh to the "Internal Storage" of your Device.
3: Bring device into bootloader (Reset + Hold Vol Down), this will show the Red, Blue, Green screen showing "Serial" - Connect device in bootloader mode to USB, the word "Serial" will change to "USB"
4: Run mtty1.42.exe, You will se a box showing "COM1" from this list select "USB" - If USB isn't in the list, something has gone wrong in the "Driver Installation" Section of POST 1
5: Leave default parameters, (8 bits / Flow Control NONE / Stop bits 1 / Parity None / Local Echo No) and Click OK
6: Run following commands:
6a: Press enter first to get prompt (Will Show as EITHER USB> or CMD> - Personally Mine Showed CMD>)
---------------------
MTTY OUTPUT:
---------------------
CMD>
---------------------
6b: type "set 14 0" without the quotes to tell bootloader to boot the OS after reset:
---------------------
MTTY OUTPUT:
---------------------
CMD>set 14 0
HTCST ÚÈHTCEUSB>
---------------------
6c: type "task 29" to get your device formatted:
---------------------
MTTY OUTPUT:
---------------------
Cmd>task 29
Format BINFS start
Fill RSVD information for block 288 to 321
CE start sector=0x14, total sector of CE and TFAT=0x14
CE start start block=321, total block=1727
ERASE block 1337 FAIL !!!
Write 0xFF start page=0x5040, total page=0x1AFC0
Format BINFS end
Cmd>
---------------------
6d: type "task 8" to ask your device reboot:
---------------------
MTTY OUTPUT:
---------------------
Cmd>task 8
Cmd>
---------------------
7: Immediately DISCONNECT your device and hold "Vol Down and Back" (Back = Small Arrow above "End Call" Button) to Initiate ROM Flash
8: After ROM flash Hard-reset (Pen Reset, then Press and Hold Vol Down and Circle) again, on completion "Press Vol Up To Boot" Is displayed, press "Vol Up" and allow the ROM to boot.
MTTY - Flashing From USB
Before you start:
a: FULLY COMPLETE POST 1
b: grab: mtty1.42.zip
AND ENSURE YOU HAVE HARD-SPL ON YOU DEVICE!!
Procedure:
1: Bring device into bootloader (Reset + Hold Vol Down), this will show the Red, Blue, Green screen showing "Serial" - Connect device in bootloader mode to USB, the word "Serial" will change to "USB"
2: Run mtty1.42.exe, You will se a box showing "COM1" from this list select "USB" - If USB isn't in the list, something has gone wrong in the "Driver Installation" Section of POST 1
3: Leave default parameters, (8 bits / Flow Control NONE / Stop bits 1 / Parity None / Local Echo No) and Click OK
4: Run following commands:
5a: Press enter first to get prompt (Will Show as EITHER USB> or CMD> - Personally Mine Showed CMD>)
---------------------
MTTY OUTPUT:
---------------------
CMD>
---------------------
5b: type "set 14 0" without the quotes to tell bootloader to boot the OS after reset:
---------------------
MTTY OUTPUT:
---------------------
CMD>set 14 0
HTCST ÚÈHTCEUSB>
---------------------
5c: type "task 29" to get your device formatted:
---------------------
MTTY OUTPUT:
---------------------
Cmd>task 29
Format BINFS start
Fill RSVD information for block 288 to 321
CE start sector=0x14, total sector of CE and TFAT=0x14
CE start start block=321, total block=1727
ERASE block 1337 FAIL !!!
Write 0xFF start page=0x5040, total page=0x1AFC0
Format BINFS end
Cmd>
---------------------
5d: type "task 8" to ask your device reboot:
---------------------
MTTY OUTPUT:
---------------------
Cmd>task 8
Cmd>
---------------------
6: Immediately DISCONNECT your device then Press and Hold Vol Down to bring the device back to bootloader and connect to USB.
7: Run ROM Flasher and flash via USB. After rom flash is completed Hard-reset (Pen Reset, then Press and Hold Vol Down and Circle) then allow the ROM to boot.
Very good to have a MTTY thread that rounds everything up!
Good job and thanks for all the effort!
i must say this is the reason i got my old rom working and stuck with it without wanting to upgrade. this happened to me, and for about 4 days or more the phone kept crashing and needing a hard reset. even changing roms or reloading the same rom didnt fix.
i tried the MTTY thing and it was difficult to get going.
i personally really appreciate writing all this up, because now i will probably go and try another rom, with this thread in the back of my mind if things start acting up.
so thanks!
dieselboy said:
i must say this is the reason i got my old rom working and stuck with it without wanting to upgrade. this happened to me, and for about 4 days or more the phone kept crashing and needing a hard reset. even changing roms or reloading the same rom didnt fix.
i tried the MTTY thing and it was difficult to get going.
i personally really appreciate writing all this up, because now i will probably go and try another rom, with this thread in the back of my mind if things start acting up.
so thanks!
Click to expand...
Click to collapse
To be honest, i have NEVER experienced the issues that require MTTY! I have always just flashed from internal storage and never had an issue.
I wrote this because i just wanted to get MTTY working incase i ever do experience it!!
MG
pauldgroot said:
Very good to have a MTTY thread that rounds everything up!
Good job and thanks for all the effort!
Click to expand...
Click to collapse
No problem, I personally got sick of trying loads of instructions to have them fail!
Most of my failures were due to drivers and improper installation!
Glad you find this useful!!
MG
I must just say that u might have to watch the x64bit drivers if they are digitally signed... Cuz neither Vista 64 nor Windows 7 64 will let u load or start those drivers if they are not digitally signed.
IF that the case and if u have installed the driver but it says that it has stopped it due to the driver not been Digitally signed u have to start windows vista/7 in "ignore digitally signed drivers" mode.
When u start the computer, keep hitting F8 and it will prompt you if u want to start in safe mode bla bla and in the bottom of that list there is an option that goes something like this:
Start Windows without Digitally signed Driver Check... or sumthing like that...
This is only if u have problems with the x64 driver... like i did...
BTW... u made a beautiful how-to man. Great job!
Reb0rn said:
Start Windows without Digitally signed Driver Check... or sumthing like that...
This is only if u have problems with the x64 driver... like i did...
BTW... u made a beautiful how-to man. Great job!
Click to expand...
Click to collapse
added this to the first post!!
thanks alot!
MG
well done
sticky!
benko286 said:
well done
sticky!
Click to expand...
Click to collapse
Agreed!!!
MG
MG, great thread thanks....
I am wondering whether you have any idea what happened to my Diamond, and what could I have done to save it (it is now with HTC).
http://forum.xda-developers.com/showthread.php?t=539958
I didn't do the "Driver Installation" part you described in your procedure, although I could still see the "USB" option in the dropdown, can that be where I went wrong?
Would also like to check how come recently there seems more flash problems reported? I myself have been flashing for some one year or so now... and never had a problem till now... I would like to get back to flashing again once my Diamond returns (hopefully), but now I am not sure I would since I am not sure what I did wrong to cause the problem to start in the first place.
epiphone said:
MG, great thread thanks....
I am wondering whether you have any idea what happened to my Diamond, and what could I have done to save it (it is now with HTC).
http://forum.xda-developers.com/showthread.php?t=539958
I didn't do the "Driver Installation" part you described in your procedure, although I could still see the "USB" option in the dropdown, can that be where I went wrong?
Click to expand...
Click to collapse
Possibly, i really would suggest running throught the entire thread if you have a brick.
reinstall the drivers, using the ones i have posted, also use the MTTY i have posted.
also USE the exact commands i have posted (i.e. not "task 28", use "task 28 55aa")
then after the MTTY format, HARD-RESET your device then to clear anything else off, then in your case, flash from the PC not internal storage.
epiphone said:
Would also like to check how come recently there seems more flash problems reported? I myself have been flashing for some one year or so now... and never had a problem till now... I would like to get back to flashing again once my Diamond returns (hopefully), but now I am not sure I would since I am not sure what I did wrong to cause the problem to start in the first place.
Click to expand...
Click to collapse
Personally i have never experienced (touch wood) these flashing problems, i have consistently flashed from internal storage and NEVER via USB.
personally this is where i think the problem resides, with leftover data from USB flashing logging up the devices.
as there are more "Bloated roms" (i.e. ones with loads of nice but useless software) this is also causing the problems.
having said that i use possibly the most bloated rom about, the NRGZ EnergyROM series!! i swap between this and the BSB, im more drawn to the BSB at the moment as there is more storage and ram free.
but as i said this is only my opinion and not verifiable facts! (i could be totally wrong!!)
MG, thanks for your replies... unfortunately I am not able to try the "task 28 55aa" now that I have booked my phone in This thread however, will no doubt be useful for more others in time to come!
Hmmm... the strange thing is that after ive had these problems i have to use MTTY as soon as i must flash another ROM then the one i already have in...
But as i said... no problems as long as it works
epiphone said:
MG, thanks for your replies... unfortunately I am not able to try the "task 29 55aa" now that I have booked my phone in This thread however, will no doubt be useful for more others in time to come!
Click to expand...
Click to collapse
MG, is it "task 29 55aa" or "task 28 55aa"?
sb0611 said:
MG, is it "task 29 55aa" or "task 28 55aa"?
Click to expand...
Click to collapse
sorry my error "task 28 55aa"
ill edit previous post
MG
sorry for the noob question, i'm on XP would I still need to run through the driver setup in the first post?
skilty said:
sorry for the noob question, i'm on XP would I still need to run through the driver setup in the first post?
Click to expand...
Click to collapse
I dont have XP, but i guess not, i have never heard of people having a problem with MTTY on XP.
Just disable USB connections in active sync, reboot your system and start MTTY.
If there s no USB option you may have to find the XP Active Sync Drivers and follow my method, but using the XP drivers.
MG
I have Windows 7 RC1 64 bit version , I have installed Device manager 6.1 , I can sync with Diamond I have succesfully done Hard SPL, but in ROM upgrading Doesnot proceed and stop at 0 % and finishing wit error
Shomoha said:
I have Windows 7 RC1 64 bit version , I have installed Device manager 6.1 , I can sync with Diamond I have succesfully done Hard SPL, but in ROM upgrading Doesnot proceed and stop at 0 % and finishing wit error
Click to expand...
Click to collapse
i have win7 rtm 64-bit, and rom upgrades work. (also worked in the beta and rc1.)
by device manager, you mean windows mobile device center, yes?
it has an single upgrade via windows update, maybe that will solve the problem.
apart from these, you can also install the rom file (after extacting it) by copying it to internal storage with the name diamimg.nbh.
yes I mean windows mobile device center, I will try your Suggestion, but I really want to Know what is my problem , Hard SPL is done with no problem but rom upgrade could not be done
Internal storage method is faster, easier and safer.. why not thinking of that?
hy from what i now after flashing on w7 you have too install other driver for the phone when it is in bootloader then the ones that update installs. if the driver date is something with 2007 you have to take the driver from the mtty threat and install them in the Force driver signiture diseable (something like that) mode of the w7. when it boots hit f8 and from that list you will see what i meant. afterwords i recommend the internal storage flashing method(more simple and faster, in case of electicity stop less problems). hope this helps
p.s. after some interesting erorrs i found that a usb mouse when i was in signiture desabled mode of the w7 gave me troble. all went well after removing the mouse.... (microsoft mouse)...h..h.hh.
mauk said:
p.s. after some interesting erorrs i found that a usb mouse when i was in signiture desabled mode of the w7 gave me troble. all went well after removing the mouse.... (microsoft mouse)...h..h.hh.
Click to expand...
Click to collapse
thank you Mauk
I have upgradeed with internal storage methode, thanks again