Related
It might be very simple to all you educated guys, but I am sure there are a few more like me that are a bit baffled by some of the threads on here.
What would be REALLY nice would be a 'simple' step-by-step guide to installing wm6 on our devices, and what we need to download to achieve it, eg "you need this for MDACIII, and this for O2 Orbit"
Obviously anyone trying it runs the risk of buggering up their phone, but that's their own fault.
Any volunteers?
stunno said:
It might be very simple to all you educated guys, but I am sure there are a few more like me that are a bit baffled by some of the threads on here.
What would be REALLY nice would be a 'simple' step-by-step guide to installing wm6 on our devices, and what we need to download to achieve it, eg "you need this for MDACIII, and this for O2 Orbit"
Obviously anyone trying it runs the risk of buggering up their phone, but that's their own fault.
Any volunteers?
Click to expand...
Click to collapse
having asked the same question myself here goes.
Download USPL and follow the instructions. they are very clear.
Download
extract
connect phone with minimum 50% battery
soft reset and once started up fully run the app by clicking on Rom Update utility
follow the process through once finished your device will restart.
once restarted you then can flash the rom of your choice
I used Black and Blue again ran the update utility and bingo.
dont forget that all data on your device will be lost so make sure you have back up of contacts etc in outlook on pc.
Finaly make sure you have Activesync 4.5
enjoy
AS STATED ALTHOUGH THIS WORKS YOU ALL DO IT AT YOUR OWN RISK
Id just like to know really is that how many people have done it without unlocking the device for o2 orbit uk. i have one and am not really willing to try it unless i know there are people out there that have tried it and it worked.
as there is no rom install file from o2 for this, there is no way bacj and bricked phone is the only way forward. id like not to brick my phone as i need it daily.
so, has anyone with a locked o2 device upgraded to WM6 successfully and which rom did you use if it worked.?
joey jojo said:
Id just like to know really is that how many people have done it without unlocking the device for o2 orbit uk. i have one and am not really willing to try it unless i know there are people out there that have tried it and it worked.
as there is no rom install file from o2 for this, there is no way bacj and bricked phone is the only way forward. id like not to brick my phone as i need it daily.
so, has anyone with a locked o2 device upgraded to WM6 successfully and which rom did you use if it worked.?
Click to expand...
Click to collapse
i have o2 uk orbit and all is well
pof said:
I created update package for this ROM in NBH format, so no risk of bricking when flashing it, just unzip & run RomUpgradeUtility.exe
Download here:
ARTE_WWE_WM6.zip
NOTE: Before flashing you need to have Artemis USPL on your device.
Click to expand...
Click to collapse
Taken from Bepe's thread about the modified o2 German update. Basically you need to use the Artemis USPL program and then use the first link to install which I did successfully on a CID locked phone.
Thanks guys, but, unfortunately, the uspl thing does not work on my pc
Along with a few others I get the 'black screen' on my mdac3 then activesync disconnects and the rom loader throws up an error
Luckily my mdac3 survives through a soft reset
I think the idiots guide is not quite there yet
hi..
i have O2 uk orbit.. which is still locked, i fully charged the battery, completed a hard reset of the phone used the pof Artemis Update SPL (USPL) v.01 upgrade (wow what a brain box he is!) just in case it failed, so i could you use any NBH file to get you orbit to work again if i failed. Then used Bepe's WM6 os.nb file renamed it to windows.nb downloaded ATRE.zip unzipped the ARTE.zip file placed the windows.nb into the same directory, don't forget to edit UpgradeRom.bat file 0x3900000 to 0x3500000 with in the ATRE directory and copied and installed EnableRapi.cab to the phone. Reset it the phone and then started the UpgradeRom.bat! 12 mins later upgrade complete. Hard restart the phone.. Chewing nails by now... all went well did a soft reset of the phone before the O2 ExtROM autorun starts..
sorted, and did half way though a night shift at 3 am.. not bad at all!
crushuk said:
hi..
i have O2 uk orbit.. which is still locked, i fully charged the battery, completed a hard reset of the phone used the pof Artemis Update SPL (USPL) v.01 upgrade (wow what a brain box he is!) just in case it failed, so i could you use any NBH file to get you orbit to work again if i failed. Then used Bepe's WM6 os.nb file renamed it to windows.nb downloaded ATRE.zip unzipped the ARTE.zip file placed the windows.nb into the same directory, don't forget to edit UpgradeRom.bat file 0x3900000 to 0x3500000 with in the ATRE directory and copied and installed EnableRapi.cab to the phone. Reset it the phone and then started the UpgradeRom.bat! 12 mins later upgrade complete. Hard restart the phone.. Chewing nails by now... all went well did a soft reset of the phone before the O2 ExtROM autorun starts..
sorted, and did half way though a night shift at 3 am.. not bad at all!
Click to expand...
Click to collapse
Confused... is it really necessary to take all these steps? I thought that the only thing required is to run Pof's tool USPL, and after that run Romupdateutility.exe from the package in .nbh format (the link is just a few messages above yours). Please correct me when I'm wrong.
step by step guide
stunno said:
Any volunteers?
Click to expand...
Click to collapse
OK, I volunteered... This is a detailed list of steps how I installed a new ROM on my MDA Compact III (CID locked, at least I think so). It worked without any errors or problems. I used PDAVIET Black&Blue v2.0. It was my first flash on my Artemis, so I more than understand your need for step-by-step guide
1. download the file Artemis_USPL.zip
2. unpack into the folder c:\USPL
3. download the file ARTEMIS_Black_Blue_v2.zip
4. unpack into the folder c:\ROM
5. soft reset your phone and have it charged over 50% (I have it fully charged)
6. wait until the system starts on your Artemis
7. turn on flight mode (probably not necessary, but I wanted to minimize any risks)
8. connect your Artemis to PC with a USB cable
9. wait until ActiveSync icon in your tray (lower right corner of your windows desktop) turns from gray to green. If you connect your Artemis for the first time to PC, you do not need to set up synchronization, just click "cancel" on the first screen of "Synchronization Setup Wizard"
10. while ActiveSync icon is green, run c:\USPL\start_uspl.exe
11. a DOS screen will pop up with the text "Initializing: 0.." in the bottom indicating probably seconds from the start (it stopped around 70 in my case after about 1.5 min)
12. DOS screen disappears and PDA Phone ROM update utility pops up
13. at the same time, your Artemis turns blank (orange/green LED turns off as well)
14. tick the check box next to " I understand..." and then click Next
15. tick the check box next to " I completed..." and then click Next
16. a box saying "Verifying information on your PDA..." pops up
17. on the next screen click Update button
18. next screen says "Upgrade to ... image version 9.99" - click Next
19. Next screen says "You are now ready to update..." - click Next, a window with a blue progress bar appears with a text "Updating ROM image..", it quickly runs to 100%
20. next screen says "Congratulations! ..." - click Finish
21. your phone turns on and boots into your old system, however it should be CID unlocked now
22. your Active Sync should reestablish and icon turns green again
23. do not touch anything (phone or USB cable) and run C:\ROM\ROMUpdateUtility.exe (make sure activesync icon is green)
24. PDA Phone ROM Update utility window appears, tick the check box next to " I understand..." and then click Next
25. tick the check box next to " I completed..." and then click Next
26. a box saying "Verifying information on your PDA..." pops up
27. on next screen click Update button (says "Current information...")
28. next screen says "Upgrade to ... image version BnB2.0" - click Next
29. Next screen says "You are now ready to update..." - click Next
30. a window with a blue progress bar appears with a text "Updating ROM image..", your Artemis will have light gray screen with blue progress bar showing the progress of flashing - do not touch anything and wait (it took 2-3 minutes on my 3 years old PC)
31. next screen says "Congratulations! ..." - click Finish
32. your Artemis turns on and starts booting, you can disconnect it from PC now
33. the boot screen remains the same (T-Mobile in my case), so do not panic!! it is normal
34. wait until calibrate the screen appears, calibrate, choose time zone and you are ready to use your new OS
35. let me know if this manual was clear enough, whether it helped you and please suggest potential changes for improvement
Take care,
Dzim
i've just succesfully flashed my dutch CID-LOCKED MDA Compact 3 with this method, so i'd say it's reasonably fool-proof
A couple of questions before i take the plunge - if my t-mobile cmda iii is already CID unlocked, can i just go straight to the update rom part.
Also, is there any way of dumping my standard t-mobile rom first off? I'm having trouble trying to use itsutils due to the app lock.
Cheers Dzim!
Your instructions worked perfectly.
One very happy complete idiot here!
Furbious said:
A couple of questions before i take the plunge - if my t-mobile cmda iii is already CID unlocked, can i just go straight to the update rom part.
Also, is there any way of dumping my standard t-mobile rom first off? I'm having trouble trying to use itsutils due to the app lock.
Click to expand...
Click to collapse
There is a TMobile rom on here somewhere already, I just cant find it at the moment
My Compact 3 it’s death now. After pres voice commander button MDA start only to the boot loader. Can’t run complete system.
Pleas tell me. How can I write the new rom with WM5 or WM6 ?
OOPS! Working well apart from the "cant save word documents" bug!!
Just an update - to use the v1 or v2 black and blue, even though it is unlocked, you still need to use the supercid util.
Otherwise you get the rom update getting to 3% before crashing out to say the rom is corrupted.
I've now converted 2 other tmobile compact mda IIIs successfully, wm6 is much quicker
Yes, with my Compact was exactly as You say. Now is death. What I can do now to repair it.
big thanks to Dzim, used the idiots guide and now on wm6 =D
cheers!
PS: first post
Hi! Nemesis, try to connect your HTC to your pc in bootloader mode.
Lauch start_uspl.exe in USPL folder. Follow instruction on post N°9 by DZIM.
After USPL your HTC should reboot (maybe in bootloader mode only).
Launch the ROMUpdateUtility.exe in Black&Blue ROM v2 and follow instruction.
Thanks gguyaz
Pleas tell me.
Could I doing this upgrade with Windows Vista on my PC?
Firstly I would like to say thanks to this site and the trinityguides.info site for the great work people have being doing and making available to everybody, it is great being able to use my trinity with wm6, keep the good work going!
Now the issue I seem to be hitting the same "error [260] connection" every time I attempt to update anything on my Trinity. I have followed the advice on the trinityguides site regarding being stuck in bootloader mode to no avail, and I can't seem to find anything in the posts on the xda site which will rectify the issue.
Previously I have been able to update to AX3L v2.8.01 version without any problems, but I decided to update to sammy's ultra light, it initially kicks into des' crashproof sspl, but then it can't connect to the pc. even when I manually enter olipro's hard-spl it does the same. I have tried to re-install hard-spl, but can't. Disconnecting the usb option in the activesync settings doesn't do anything either. Does anybody have any suggestions for me please?
I am not even too sure if my trinity should have both Des' crashproof and hard-spl on it at the same time? Could someone advise me on whether this is alright please?
the tech details:
Trinity
AX3L_OS_v2.0.8.2
radio - 1.46.30 (even though it doesn't say this in the device info, or boot screen after soft reset)
Home PC - XP (just in case)
Did you also try flashing it again, the ROM I mean. I have this error also but as soon as I execute the ROM flash again it finds the device and starts flashing:
http://forum.xda-developers.com/showpost.php?p=1449597&postcount=2
I am assuming you mean flash with the new ROM, sammy's in my case?
yes, as described in the link I posted before. As soon as the error occurs, do not touch the phone, leave it, just start the ROM flash procedure again. (execute ROMUpdateUtility.exe)
No, I am in the same situation. The first attempt puts the device in 'ipl-sspl by des' bootloader mode then after about 10 seconds or so the error[260] is displayed on the pc. If I exit the ruu app and attempt again, nothing new happens on the trinity (i.e. it is still in Des bootloader) and the message is displayed again.
the thing is that when it first goes into des bootloader mode, the white strip doesn't have any text in it. If I pull the usb cable out then put it back in, 'serial' is then displayed in the white bar, but I am still in the same situation as before.
What operating system en activesync are you using?
On the PC I am using XP and Activesync 4.5
Check your connection settings to accept USB connections. Also, try using Hard-SPL 1.30 before flashing the ROM again.
deejacker said:
the thing is that when it first goes into des bootloader mode, the white strip doesn't have any text in it. If I pull the usb cable out then put it back in, 'serial' is then displayed in the white bar, but I am still in the same situation as before.
Click to expand...
Click to collapse
In your PC, try another USB connection.
BLOODY HELL!!! It is the simplest things which we often forget to try. Thanks Jotam for pointing out an obvious point, it must have needed a re-plug of the usb cable into another port for the pc to pick up the device again. I will remember that for future updates so I don't make a dumb ass of myself again. Thanks guys/gals.
Vista
Using Vista? if so which version?
Hi I asked this question yesterday, I am a noob :-[ but the only difference is I'm using Vista Ultimate.
Just for others who have the problem.
When you replug into another USB port (Luckly I've got two on my laptop..)
I used the Vista drivers from TrintyGuides and bingo !
now I try and flash a WM6.....English or Italian...maybe French.
Thanks for the help I keep you posted.
Richard
It works
Now to discover the joys of WM6 after only having WM5 for two weeks....
/i am getting the same only rom update 3.14.4.1 now sees the phone..
has the device name changed???
evene exploit no longer sees the phone
sorry, can you be a little more clear.. what ROM are you flashing, and what exactly is happening?
by the way... i thought error 246 was the connection error... am i mixed up? which is 260?
This seems to be on any rom bar the Dopod roms
and it says 260 connection error
Error 260 connection error - the phone is not going in to bootloader mode - and the RUU cannot seem to initiate communication with the phone.
I'm getting this a lot recently trying to flash.
However, Hold the power and camera buttons while resetting with the stylus (keep them buttons held down).
When you get to the bootloader - plug the phone in - wait till you see the USB at the bottom of the bootloader screen - then run the RUU again - it WILL work - every time.
I used to get this error message alot. sometimes the programs you install don't allow you to update even if you force the phone into bootloader mode so you have to hardreset the device and then upgrade.....hope this helps
htc diamond stuck
T-Rob said:
yes, as described in the link I posted before. As soon as the error occurs, do not touch the phone, leave it, just start the ROM flash procedure again. (execute ROMUpdateUtility.exe)
Click to expand...
Click to collapse
hi ,
my htc diamond stack, no respond on the screen i try to do hard reset with tree buttons but its not working, nothing happaned, screen stay home screen with the time and not responding touching the screen at all
please emergensy help
I have a TyTN with official Russian WM6 onto it, which includes 1.16 radio version. I want a newer one, because this seems unstable, so i decided to update just radio (i don't want any cooked ROM or whatever for now).
Each new version of radio I found here failed earlier or later on a Vista x64 computer with error 260. What I have tried is 1.54.07.00 and 1.54.00.10 and 1.50.
To my surprise, packaging is different, but the effect is the same: after "Verifying the image on your device" (i can hear USB disconnecting and connecting back as the device enters bootloader) they time out with 260.
Right now I'm trying to revert what have I done to Vista as it won't allow me to turn off driver signing, as advised.
Ah, this doesn't work either (same error 260).
What am I doing wrong? My bootloader is, as said on that screen:
Code:
HERM200
IPL-1.01
HERM200
SPL-1.40.Olipro
Yes, I have installed some...er...thing before, maybe it was called "HardSPL", but it didn't come handy and wasn't any use to me as I decided against cooking a ROM.
Update: What I like the most is, despite all my attempts the device still works! Other than the radio troubles, that is.
I've updated from an SD card.
Try this my friend... http://www.mrvanx.org
Thank you, I did.
Please note the x64 drivers are unsigned so to use them successfully you must disable driver signing.
Click to expand...
Click to collapse
This is what I'm unable to do, but I suppose is beyond this forum.
Hi
I have had the same problem with my x64 vista pc and the 260 error msg. It took me hours but what seemed to finally fix it for me was to:
1. completely remove WMDC from the pc, reboot the pc,
2. reinstall WMDC plus upgrade,
3. uncheck the allow USB connections option on your 8525, exit out of the window, then do a soft reset
4. now make a USB connection w the PC
Let us know how it works
Sorry, you'll have to wait till my next upgrade Everything is working so far - so until I need something that can't be achieved using SD flashing I'll stick to this technique. Thanks for the advice anyway.
All,
I'm upgrading what I believe to be a pre-release verizon Vogue. When I boot the device a series of numbers pop up
M 03
B 01
P ACAAAAM-4070
R 1.60.30
D 1.15
When I hold the power+camera+reset, I get the following at the top:
VOGU100
SPL-0.36.0000
CPLD-3
Can anyone tell me what these mean, and if that confirms the device is already unlocked? These same numbers showed up when i unlocked a phone years ago (the last time I tried to do this).
Now, when I run RUU (MFG 2.31 unlocker), I the 'verifying information' part does not seem to be gathering much info. The Image Version has NOTHING listed (see screenshot). If I try to begin the update, it shows the update version as 'Unlocker 2.31' (see screenshot).
Is this expected?
When I start the update process, it kicks off and suddenly errors with a "ERROR [262]: UPDATE ERROR" Message reads: "The ROM Update Utility has encountered communications errors during the update process." Screenshot provided of the Vista mobility center.
Update: I've also experienced an application failure "Windows Mobile-2003-based device connectivity has stopped working" in Vista. See latest attachment.
Any insight would be greatly appreciated.
-zarfu
Update: MicroSD card was in the phone at the time
Update2: Added Vista application failure screenshot
Update3: I should also disclose, i'm running Windows Vista SP1 64-bit
zarfu said:
All,
I'm upgrading what I believe to be a pre-release verizon Vogue. When I boot the device a series of numbers pop up
M 03
B 01
P ACAAAAM-4070
R 1.60.30
D 1.15
When I hold the power+camera+reset, I get the following at the top:
VOGU100
SPL-0.36.0000
CPLD-3
Can anyone tell me what these mean, and if that confirms the device is already unlocked? These same numbers showed up when i unlocked a phone years ago (the last time I tried to do this).
Now, when I run RUU (MFG 2.31 unlocker), I the 'verifying information' part does not seem to be gathering much info. The Image Version has NOTHING listed (see screenshot). If I try to begin the update, it shows the update version as 'Unlocker 2.31' (see screenshot).
Is this expected?
When I start the update process, it kicks off and suddenly errors with a "ERROR [262]: UPDATE ERROR" Message reads: "The ROM Update Utility has encountered communications errors during the update process." Screenshot provided of the Vista mobility center.
Update: I've also experienced an application failure "Windows Mobile-2003-based device connectivity has stopped working" in Vista. See latest attachment.
Any insight would be greatly appreciated.
-zarfu
Update: MicroSD card was in the phone at the time
Update2: Added Vista application failure screenshot
Update3: I should also disclose, i'm running Windows Vista SP1 64-bit
Click to expand...
Click to collapse
OK
1.make sure the Phone is connected through Activesync
2.it is supposed to show unlocker_2.3.1 when trying to update YOU MUST UPDATE IN ORDER TO PUT CUSTOM ROM AND CAREFULLY DO WHAT THE COMPUTER TELLS YOU
Thanks - can you clarify 'make sure the phone is connected through activesync'
Vista SP1 has the Mobile Device Center which manages the connection. That connection is failing due to the application failure I sent in the udpated thread. it may be easier for me to walk through the steps and you identify any changes that are necessary:
1. Boot the phone, establishing and verifying the connect between the phone and Mobile Device Center
2. Unplug USB cable
3. Power+Camera+Reset to Rainbow/'Serial'
4. Plug USB cable in
(At this point, Mobile Device Manager does not show a connection of course, but the device is recognized through in device manager as 'microsoft usb sync')
5. Run RUU (2.31 unlocker)
---> At the point where RUU says 'verifying information', the Microsoft crash agent kicks in with the failure shown in Capture4.jpg
The docs and readme's do not have troubleshooting steps for this fault.
Again, any help would be greatly appreciated.
-zarfu
Update: I have tried all these sets on a Vista 32-bit home edition laptop, and the same failures occur. This biggest missing piece I see is the references to 'ActiveSync.' There is no build of ActiveSync for Vista or beyond - that product was sunset for Mobile Device Center i suspect. As anyone successful run this on Vista and beyond, or do i need to roll-back to XP to use ActiveSync?
Not sure if you have tried this or not as it's unclear in your first post, have tried simply establishing a connection and running the unlocker skipping going into bootloader entirely? it should automatically put you into bootloader if my memory serves me.
Worked. Thank you!
3.9 ROM is up and running. What's with the crappy old digital keyboard. I thought Microsoft had changed the keyboard to be finger friendly...
zarfu said:
Worked. Thank you!
3.9 ROM is up and running. What's with the crappy old digital keyboard. I thought Microsoft had changed the keyboard to be finger friendly...
Click to expand...
Click to collapse
Great stuff!! What's the 3.9 ROM?, thought you were installing NFSFAN's rom as you said 6.5 v16.
Yes, ignore that comment. I was trying out two different builds, and confused the two. Thanks again for the help.
Hi all,
I wanted to put a new ROM on my Touch Diamond p3700, and managed to bust it.
I followed the MTTY guide from here
http://forum.xda-developers.com/showthread.php?t=416211
I got through the steps OK, but at some point, after restarting the device I noticed that it stop booting.
It would display only TOUCH diamond, and that's it. No other red numbers with RGD.
I tried a hard reset. Nothing. I also did a hard reset with a moviNAN format, and nothing. (though I think this might have made matters worse)
I tried a RUU, and it stays at 0% for a couple of minutes and then gives an error on the PC.
I tried an original ROM, but it says Not allowed for this Vendor ID (goes up to 1%).
I tried Hard SPL 1.24 a couple of times but this also stays at 0% for a couple of minutes and then gives an error.
I am totally out of ideas, but I'm only an extreme beginner, so I do hope there will be a solution.
Any help would be greatly appreciated.
Thanks.
try with HSPL 1.93
hspl 1.93
Hi.
Thanks for the reply
I assume you're talking about this
http://forum.xda-developers.com/showpost.php?p=9246383&postcount=2
I downloaded the archive, extracted it.
As I said, the phone doesn't boot, so I can't connect it to activesync,
but I did go to bootloader (red green blue screen), inserted the cable and showed USB.
Reading your steps I saw that I might have missed the hspl step inside the MTTY tut. So basically I did the mtty part without the hspl.
I connected the phone to the PC, it sais USB, I ran ROMUpdateUtility.exe, the grey screen appeared with 0%, stayed like that for 5 minutes and program gives an error that it can't communicate.
hexer4u said:
Hi.
Thanks for the reply
I assume you're talking about this
http://forum.xda-developers.com/showpost.php?p=9246383&postcount=2
I downloaded the archive, extracted it.
As I said, the phone doesn't boot, so I can't connect it to activesync,
but I did go to bootloader (red green blue screen), inserted the cable and showed USB.
Reading your steps I saw that I might have missed the hspl step inside the MTTY tut. So basically I did the mtty part without the hspl.
I connected the phone to the PC, it sais USB, I ran ROMUpdateUtility.exe, the grey screen appeared with 0%, stayed like that for 5 minutes and program gives an error that it can't communicate.
Click to expand...
Click to collapse
there is no HSPL step to perform in mtty mode. go to bootloader and report back the SPL version you have.
there is no reason you shudnt be unable to format. maybe you might need a jumpSPL if ur previous spl is hard spl-ed
In bootloader is says:
DIAM 100 64M
SPL-1.93.0000
MicroP-Diam (LED) v11
PSOC-Diam STAGE_PVT v0x32
hexer4u said:
In bootloader is says:
DIAM 100 64M
SPL-1.93.0000
MicroP-Diam (LED) v11
PSOC-Diam STAGE_PVT v0x32
Click to expand...
Click to collapse
you are still having the stock SPL...
lets get you HSPL...give me a few minutes while i come with attachements and instructions
download+unzip to C:\ (recommended)
- connect ur device in bootloader mode
- dont do mtty at this stage
-run the DiamondCustomRUU.exe
report back
ruu err
I get this
Code:
ERROR[262]: UPDATE ERROR
The ROM Update Utility has encountered communication erros during the update porocess.
The program will guide you step-by-step to recover fomr the errors so you can continue witht the update
hexer4u said:
I get this
Code:
ERROR[262]: UPDATE ERROR
The ROM Update Utility has encountered communication erros during the update porocess.
The program will guide you step-by-step to recover fomr the errors so you can continue witht the update
Click to expand...
Click to collapse
did u try flashing this HSPL?
whats ur current location so i can recommend a flash of stock rom.
I'm in Romania. My phone was locked on Vodafone.
What do you mean "flashing this HSPL"? This error I get when running DiamonCustomRUU.exe in the archive you posted. It starts the progress bar on both PC and phone, stays at 0% and after 5 minutes, it gives that error.
okay. download this. and run the diamond-sspl.bat
if it runs successfully and ur screen turns black...then run DiamondCustomRUU.exe again to flash SPL 1.93
if the batch file does not run let me know...
btw i wil be here till we can sort this out
I connected the device in bootloader. Shows USB.
I ran diamond-sspl.bat
and says:
Warning: no device connected.
Waiting for device to connect...
A window pops up, and says if I want to retry. Hitting yes just pops again.
So basically it says that it can't copy whatever it needs on the device because it's not connected. But the device is connected in bootloader and says USB.
okies....lemme make a cross check of the HSPL on my device and report back
in the meantime, do you have your STOCK ROM? the original rom that came with your device.
if you dont, but still know the rom version to download, check here....
http://shipped-roms.com/index.php?category=windows mobile&model=Diamond
in the event we cant proceed any further, atleast we can recover ur device to start up again with batch file...
Try this version of HSPL which allow a temporary SSPL on ur device in order to allow a transition of SPL..
as usual report back. this is the last step...after this if there is no progress we may have to resort to stock rom and then start at step 1.
btw HSPL 1.93 confirmed working on my device.
The same issue. Error 262.
Isn't the problem somewhere in the communication between the PC and device?
When I run ROMUpdateUtility.exe the device does go to the grey screen with progressbar at 0%, but that's about it.
I don't have my original ROM, and I don't know the version,
but I think this should be it
RUU_Diamond_HTC_WWE_EastEurope_2.03.479.2_Radio_Signed_Diamond_52.51.25.26_1.09.25.23_Ship.exe
You can try restarting your PC and then try to confirm any USB conenction problems.
But if on the device it appears USB in the bottom half of the bootloader screen it means the connection is okay.
Now this is a flash (see attachement) i only use as a last resort. If this doesnt flash, consider downloading the rom file you jus mentioned and flash it...
Download the attachment and run the .exe file. Follow the steps...if it works...try flashing any HSPL u have downloaded.
also try this link from htc.
http://www.htc.com/ro/SupportDownload.aspx?p_id=133&cat=2&dl_id=483
input ur device serial (which is under ur battery) and see if u can download. this is more direct approach to download the correct rom file for ur device.
YES!
Fixed it.
I switched USB ports, left the default driver (2007, not 2004 as was said in MTTY), used the ROM I said above and it worked.
Thanks a lot for your assistance.
good!
and if ur up for another try. then start with the attachement HSPLwSSPL
dont do any mtty. jus try to see if u can flash HSPLwSSPL...
but if ur done for the day, i wish u a rest well earned.... hehe...
anyways feel free to drop a PM in my inbox shud u decide...