Hi, hoping someone can help.
Getting the following. Can't get past it. Also what does the Diam100 stand for as I notice others have different.
A tri-colored screen that reads as follows:
Diam100 64M
SPL-1.37.0000
MicroP-Diam (LED) v.11
-----------------------
PSOC-Diam STAGE_PVT v0x30
Upgrade ROM code error
Please try again
Thanks for you help!
1: state the subject in the thread title, that's what it's for
2: search is your best friend; the issue you mention has been discussed in several threads
3: I'd recommend: get into bootloader mode (seems like you can); install hardSPL again, flash again with any ROM supported by hardspl.
4: insert [solved] in front of your thread title.
5: this is NOT a relevant subject for this forum (it's got nothing to do with rom development)
apologies, im new to this (only got the diamond today) and havent been able to use it yet and this forum was the closest thing i could find to getting it working.
Im unable to enter bootloader mode (volume down, reset?)
Also can't get my diamond to connect to pc and keep getting connection errors when trying to install Hard-SPL?
Thanks, your help is appreciated.
The tricolor screen IS bootloader mode.
Just run the HardSPL, then Rom upgrade utility from a rom, and that's it.
IF you got it in this state, you'd probably want to return it (you got warranty?)
Thanks for your help.
Is HardSPL going to install even though ActiveSync isn't recognising the device (ie not connected). When i run it it seems to work and then a grey screen with 0% shows. Then the install program comes back with a 'connection problem' message,i go through all the steps but just keeps happening. I read posts on this earlier today but it seems the install program is fixed and shouldnt do it any more????
...also ive done all the firewall changes to make sure it connects etc etc. Forgive me if im not doing something that has been posted already, but i couldnt find it.
Thanks.
I had the same problem make sure you install the HARD SPL but the unsigned version not the sign version.....it should work them.....
i think there's two issues people are describing here..
1) installing hard spl.. if you get the 0% error, then you need to follow the instructions in the thread and manually run SSPL from your phone and then start the RUU
2) if you keep getting errors while trying to install your rom AFTER installing hard-spl, then you probably are flashing an unsigned ROM on the signed hard-spl.. go to the sticky thread and download a signed version of the ROM you want..
Thanks guys. I dont see how i can do the manual install, as it requires me to copy a file onto the diamond and at this stage i cant even get activesync to connect to it. I dont beleive its a problem with activesync or the pc as ive tried many many things, but rather that the diamond isnt communicating properly.
Also i havent even got to installing the new ROM yet as i cant get past HARDSPL install.
Do you think installing the un-signed HARDSPL version will work? as in will it install when the signed version won't?
all your help is very much appreciated. I cant wait to actually turn my phone on for the first time!
you haven't turned it on yet
is that right?
you have not had it working yet?
or have you tried to update it even before using the phone???????
yeh unfortunatley thats right, yet to turn it on. hopefully will have it up and running shortly...
1) can you confirm exactly what happened to get you stuck in the bootloader screen? (it usually doesn't just happen by itself)
2) Have you tried to soft reset to get your device out of bootloader?
3) are you flashing in win xp or vista?
4) are you connected through a usb hub?
yes, tried soft rest but it just returns to bootloader screen.
using winXP SP3. Not using a USB hub. have tried different ports.
Have tried the signed and unsigned versions of HardSPL.
I keep getting to the 0% grey screen and then the communication error 262.
Maybe i should try and just flash the original ROM? Does anyone know where I can download it from and the HTC e-club doesnt have it? Or is this not the next step???
Thanks!
yeah try the original ROM..
but still i don't understand how you got to this point.. what were you trying to flash when it got stuck in bootloader?
I bought the phone like this.
Do you know where i can get the original ROM from? I tried e-club (both worldwide and SEA) no luck.
Appreciate your help on this.
?? that's quite strange... is there any reason why you're not just returning it for a new set?
try this thread for SEA ROM
I bought it whilst overseas last week in SEA. Im now back in australia and would like to try my best to fix it before going down the long and difficult warranty path.
Do you think its buggered? Or the fact that its in the bootloader screen and giving me this message quite common on failed ROM updates?
Do you think an orginal ROM install will fix it? if so where can i get it from?
Thank you.
well that's what i'm asking..
you got this screen when you pulled it out of the box, or tried to update the ROM and then hung on this screen. also, if you did try an update, was it a SEA update, or australian ROM
i wouldn't say its a common issue.. i also don't think your device is bricked, since its showing bootloader.. diamond is relatively new so i don't really know a lot about getting it out of this state.
trying to load original ROM is a good option.. one thing is for sure, before any further flashes (after you get out of this mess) you want hard-spl on your device.
If flashing original ROM doesn't work, i'd suggest PM'ing walshieau, olipro, or pof as they know a lot more about this type of stuff.. do post your results
Thanks for the link above. i'll give it a go. is it different from the one in the ROM list??
Related
I follow instruction in http://forum.xda-developers.com/showthread.php?t=313486 but after hardreset.
My p800w is stuck in T-Mobile logo and version number. It can't continue booting up to windows mobile.
Question: How to flash ROM without ActiveSync?
How to recovery my Artemis?
Welcome any advice,
Thanks in advance.
Yea me to, mine is now a brick after that upgrade? No active sync connection possible and all I get now is the blue O2 start screen after the hard reset with the red writing and numbers in the top left hand corner..
Phone is an UK XDA Orbit
IPL 1.25.0001
SPL 1.11.0000
GSM 02.67.90
OS 3.4.0.0
HELP!!!!!!!
yeah, I had the same problem and have created a thread for it already. unfortunately I got no useful replies, and it seems that I am stuck waiting for an official o2 ROM so that I can recover my Orbit.
It seems there is a way to un brick our phones I just need to get my phone bootted into bootlader mode which no one seems to say how to do??
Can anyone help how I can boot my Orbit , like what combo of keys I need to press to boot it into bootloader mode then XP will see it at a driver level apparently Active Sync still won;t but I will be able to run some German ROM update with the ROM file replaced with the other ones and it may come back to life..
Help how can I boot my phoen in bootloader mode???
motomob said:
It seems there is a way to un brick our phones I just need to get my phone bootted into bootlader mode which no one seems to say how to do??
Can anyone help how I can boot my Orbit , like what combo of keys I need to press to boot it into bootloader mode then XP will see it at a driver level apparently Active Sync still won;t but I will be able to run some German ROM update with the ROM file replaced with the other ones and it may come back to life..
Help how can I boot my phoen in bootloader mode???
Click to expand...
Click to collapse
I read in here that you hold the voice button and soft reset.
Decaf said:
I read in here that you hold the voice button and soft reset.
Click to expand...
Click to collapse
Correct and use mtty
Already see in the forum ....
Thanks guys and apologies for the spelling..I ran the Artemis_USPL before I tried upgrading to WM6 and again have been able to run it after with my new brick now with the phone in bootloader mode but still when I try and run the german ROM update a) it will only work with the german file which freezes @ 3%? This seems to be a known problem reading around and b )when I replace it with the smaller ROM file, 54MB the german one is 66MB, I originally tried to use it doesn't read the ROM file or the update utility doesn't want to read it. I reckon I might be able to get it back if I can get one of the ROM update utilities to read a good ROm file and send it to the phone.
I can;t find this MTTY program to sniff the USB port and return the code of if the USPL util wokred as I think that could be key to all of this.
Can anyone post a quick how to here for
1) install MTTY from somewhere
2) what command to run agaist the phoen to see if the USPL util worked and what values I should be looking for
3) another WM6 ROM version (that the update utils can read) download location I can download from to try and send to the phone using the German update util
Not asking for much am I but I desperately need my phone back WM5 or 6 in the next day or so so really can't send it off.
Thanks
Error message I recive at the 3% stage when using the German ROM and english update util.
use the file attach and read that :
http://forum.xda-developers.com/showthread.php?t=285112
Thanks but I'm not that cleud up on what commands I'm meant to be sending. It works in Bootloader mode I ge a response from the phone by send it a command. But even if I get a response telling me what the CID status is its not much help as I think ti shoudl have tekane BEBEs ROM by now as I've got the german ROMUpdateUtility sending that 54,272KB file to the phone but it stops after 3%. What are my options?
motomob said:
But even if I get a response telling me what the CID status is its not much help as I think
Click to expand...
Click to collapse
That's right. On older models MTTY was quite useful, but not on the Artemis. You cannot use it to read the CID status anyway. If you are not sure about the status, run the USPL tool, just to make sure.
I've already re run the USPL ROMUpdateUtility and it completes 100% okay in bootloader mode. But after I hard reset and then try and flash the WM6 BEBE ROM or any ROM German etc back onto it it either fails with the error code I posted up earlier or gets to 3% and fails.
What are my options at this stage? Does anyone have a link to another ROM I can try like the original WM5 O2 ROM or any other WM6 ROm that might work. I'm willing to give them all a try as it's just a useless phone right now and I haven;t sent it off as 1) I need it before the weekend and 2) As I can flash some ROMs with the USPL and others have done this no problem I really feel there must be a solution as I can still falsh the phone.
What can I say RTFM... I did it all right and I didn't have a brick, I missed out one small detail... loading on the ROM with the extended ROM. All now running and it does seem a little faster than WM5.
Thank you to all those that tried to help out. To the others that are still having probs.. Don't try and run the update in the middle of a busy day in the office whilst trying to manage 100 other things meaning you are probably missing out a line like me...
One question though how do I get back my O2 power and storage meters on the today screen back as I liked them and the WiFi seems to have a bug where when it is enabled and you click on the WiFi symbol up the top it only allows you to switch it on, when it is already on.. so you have to open up the COMM manager to switch it off.
So how did you fix it exactly? I have read this thread thoroughly and can't find out what you did!
ERROR[206] occurs while trying to update ROM to WM6
While tring to update ROM to WM6 on O2 XDA Orbit i encounter ERROR[206].
I wanted to attach the screen shot but dont know how to do that, but anyway what i am doing is i attached my pda to my pc via activesync using supplied usb cord. Everything goes well till i reach a screen where it says "You are now ready to update your ROM image...." and once i click next a progress bar apperas and my pda shuts and activesync exit's automatically and my pda tries to restart with RBG band and some text:RUU, IPL 1.25.0001, SPL 1.25.0000 and USB. And thats it after few seconds or a min i get the ERROR[206] and my pda hangs.
I dont know why Activesysn shutsdown ???
Just an additional in i want to tell that without installing activesync i am not able to connect/pair my pda with my pc. So do i need to install the drivers and then try or it doen't matter cause once i install Active sync i can connect the device.
Please help me with this....
Thanks
unable to load bootloader!!!!!!!!!!!!
HELP!!!!!!!!
I have HTC3300, tried to update rom, now its bricked. I tried to start bootloader by pressing the voicebutton and softreset but loads in t-mobile screen and hangs, im unable to start the bootloader.
Is this end of story or are there any other options to get the bootloader to start????
please help
Bootloader
I had a problem with my phone loaded touch flow 4 and cid unlocking, everything was fine then after a while it froze at boot up.
I look put the battery and did a hard reset, put it into bootloadeder mode, reflashed with a t-mobile rom does not need to be cid unlocked to do that.
Once origonal rom was working, cid unlock again, flashed back to touchflow 4.0 - sorted
Where did you got an tmobile rom from can you tell me. Mine is also freezing on booting almost once every day or so after I've upgraded to 4.0
Hello, I cant follow/or understand the guides found here or in
trinityguides to recover my device.
I have successfully flashed severa cocked roms before, however this last one failed and left me in tri-color screen displaying SPL-9.99-CP
What do i need to do, my active sync want connect and give me the green OK.
It say it cant detect my device when i connecs it?
Please help, im not good at this, how can i get the device to be recognized by
active sync?
Any help very much appreciated!
allanredo said:
Hello, I cant follow/or understand the guides found here or in
trinityguides to recover my device.
I have successfully flashed severa cocked roms before, however this last one failed and left me in tri-color screen displaying SPL-9.99-CP
What do i need to do, my active sync want connect and give me the green OK.
It say it cant detect my device when i connecs it?
Please help, im not good at this, how can i get the device to be recognized by
active sync?
Any help very much appreciated!
Click to expand...
Click to collapse
In bootloader mode AS will not recognized the PDA. As I see there is DES crash proof hard-spl on your PDA. Stay in bootloader mode, and try to flash an other rom, or the original offical rom. If does not work here is a useful link:
http://forum.xda-developers.com/showthread.php?t=308691
thanks for your quick reply!
how can i flash without the active sync is connected?
i have tried but the rom update utility says it cant find device and exits
or can it be done withot connection, if so how?
thanks for all input, as i said im not an experienced "flasher".
I don't know why, but after successfull cooked rom update (Schap, Faman, etc..) the last one didn't work and stick to 3-color (I'm under olipro 1.3)
I just made a spl update without any pb (take a look if on your pda screen it shows USB instead of serial) don't care about activsync
Then a radio update (1.40 instead of 1.50).
Shap rom update didn't work anymore (cache issue), so I'd just copied RUU_signed.nbh from SChaps replacing the one into Fman folder, and just working fine...
If it can help you.
Had this kind of problem
Simplest thing is to load rom from SD card (do search on this).
In short get the ROM you want - ROM***.nb file and rename it as TRINIMG.NB put it on the SD card. Launch bootloader and follow instructions. Otherwise check thread VISTA FLASH DISASTER...
Good luck,
Solved!
I reconnected the phone ( it sad USB in the bootloader btw)
Downloaded schaps wm6pro and unzipped, enterd the ruu and flashed, even thoug active sync was inactive.
I didnt have to go any further than this.
Many thanks, now i might dare to try som more roms, done ax3ls and karmba's so far looking forward to test schaps now.
Look in the Trinity Wiki. It describe how to flash from the SD card. this will fix you up.
Hi,
I bought a diamond a few days ago, and the touch screen recently stopped working. Before it's death, I flashed it with HardSPL 1.40 Olinex, but kept the rom and the radio stock. The problem now is that I would like to send it in for warranty to repair the screen, and I can't revert it back to the original SPL. I've read several threads about how to change it back to OEM specs, but all of them have resulted in the bootloader still displaying HardSPL 1.40Olinex.
Since my touch screen is broken and I recently performed a hard reset to try to fix the screen, I can't get past the align screen, so i've attempted all my upgrades from the bootloader screen(the screen with 4 colors is bootloader screen i think?). I've tried several SPL's from a thread which i beleive where 1.24 original, 1.37 original, 1.93Olinex, all of them still resulting in 1.40Olinex displaying on the bootloader. I also tried installing an official ROM, but that did nothing. I'm desperate for any help or advice so I can get this phone fixed and start enjoying it.
Thank you
Try make connection via AS ( not bootloader ) and shipped rom with not patched custom_ruu
Did you read this single post by cmonex?
HERE
kvm55 said:
Try make connection via AS ( not bootloader ) and shipped rom with not patched custom_ruu
Click to expand...
Click to collapse
I'll try that. I think i've tried it before, where I could make a connection but was not able to update due to me being stuck on the align screen? I'll give it another go.
R3PUBL1K said:
Did you read this single post by cmonex?
HERE
Click to expand...
Click to collapse
Yes I have thanks. That was where I tried using the RUU-SSPL-withoutNBH.zip along with the 1.37 from the first attachment, which still ended up as 1.40OliNex. I'll give it another go from the active sync rather than bootloader.
Thanks guys
Ok so I tried from AS, here's what i got:
Using CMONEX's post, with all the roms and the custom ruu I was able to detect the phone version and press update, but before it starts updating it gets an error [202], connection.
Using a shipped ruu with the 1.37 from CMONEX's post as well as the shipped nbh, the device loaded into bootloader and updated, but still displayed 1.40OliNex. It was able to install from AS though.
I really have no clue what's going on. Any suggestions?
EDIT:
I was able to magically get the touch screen to work to get past the align screen after updating to a different rom, and I was able to update it normally following CMONEX's post.
Thanks for your help guys.
Great News
Glad you got it sorted
i have flashed my diamond with the official htc rom
im on 1.40 olinex, now i can only access boot mode.
sometimes if i leave the phone without a battery for like 2 hours, when i turn it on i see the "touch diamond" logo, if i leave the battery for a whole day i see the windows mobile loading screen, but then suddenly the phone turns off
plz if you have any idea about this problem help me
If you can acces bootloader, then your diamond isn't bricked.
Try the unsigned version of olinex' hard-SPL and flash the ROM again.
Good luck!
hey ElCondor, im on 1.40 olinex, i cant flash it because it is protected
how can i flash the unsigned 1.40 olinex one?
Here is a link to the unsigned hard-spl.
Make sure you download "Unsigned-Hard-SPL-Diamond-OliNex.zip".
Follow the instructions:
1) Download, extract to an empty folder.
2) Run RomUpdateUtility.exe, Have Phone Synced with PC (go into bootloader, connect your cable, then the word "serial" in bootloader will change into "USB".
3) follow steps, check device for prompts after PC shows loading bar. it should go to black screen now.
4) SPL flashes, device automatically reboots, job done.
5) to confirm you got it installed, go into bootloader mode (volume down + reset, i.e. press volume down button and reset then keep holding the volume down key until you see tricolour screen) and verify the screen shows 1.40.OliNex.
note: you will not see the SPL version during normal boot, that is the OS version, not SPL!
Installing this will hard-reset your device.
Best Regards,
ElCondor
when i flashed the unsigned 1.40 olinex, the device rebooted
windows mobile is preparing your phone for first use
htc logo
phone went off :S
will try flashing rom again
flashed ROM again, now it wont boot up no htc diamond logo no nothing
i can access boot mode (1.40 olinex unsigned now i guess)
is there no way i can boot the rom? what seems to be my problem?
mzaouar said:
flashed ROM again, now it wont boot up no htc diamond logo no nothing
i can access boot mode (1.40 olinex unsigned now i guess)
is there no way i can boot the rom? what seems to be my problem?
Click to expand...
Click to collapse
Hi
If you can access the bootloader then your device is not bricked. Therefore download a rom of your choice then connect to the usb when on the bootloader then use a Diamond custom RUU (normally come with the rom) follow the steps. After rom updated make a hard reset. I hope it will run ok.
Looks your symtons are showing like your rom corrupted.
Good luck
i am flashing this ROM
RUU_Diamond_HTC_Europe_1.93.401.2_Radio_Signed_Diamond_52.29.25.12_1.00.25.05_Ship
the newest one i downloaded from htc. com is giving me rom update error
would you recommend a good rom for my phone?
after flashing and reflashing and hard resetting with the ROM showed above
still cant boot in ROM mode, only in boot mode
el condor sabes, anything ???
should i flash with a new rom, and if yes with which?
(diam100 olinex 1.40 unsigned)
Perhaps try a custom rom?
I found when flashing to an official rom from a different provider (my phones telstra and was flashing 3) I had issues with the rom booting and had to follow a post on here somewhere to get it working, however When I had this problem I could still flash any custom rom with no issues.
Unless its for warrenty purposes then its probably not worth flashing the "original" perhaps flash A.Z.T.O.R. = Alpha Zero Tweaked Official Roms which are close to the original but with benifits of being modded for faster speed etc.
Anyways Im no pro but I know what you are going through and I am trying to find the link to the fix to your problem as I also had the problem. But recommend trying a custom rom to confirm the problem is the same as mine.
For the record now I do not use official roms anymore, with WM6.5 running well for the most part on the diamond its a great step backwards when you revisited 6.1
flashed to SwiftBL-WWE-Diamond-v7.5-Full-16MbPP
still same problem can only go to boot mode
i am feeling there is no solution to my problem ?
is the phone bricked? :S
If you haven't done yet, flash the hard-spl I posted. Just do it, re-instal the hard-spl! Then, flash another ROM, maybe (as said before) your rom is corrupted.
The problem here is, that you first installed the unsigned hard-spl, and then flashed a corrupt rom. In that way, the hard-spl can be damaged too, so flash the hard-spl again and flash another rom should work.
Good luck!
I did :S but to no avail, I will do it again fingers crossed :S !
update: weird, everytime after i flash the hardspl unsigned, it boots up, i can see the "touch diamond" logo
windows mobile booted.. preparing your device..
update 2: windows mobile booted, installing everything
omgomg it looks it might work this time, fingers still crossed !!
el condor !! haha fingers crossed
update 3 :S : windows mobile installed properly, phone rebooted, went again and opened it, then i heard a sound from the speaker and the phone turned off :S
it must work what could the problem be now? last step !
Okay try a hard-reset, maybe that works.
If not, then flash hard-spl again, then hard-reset, then flash another ROM. Then hard reset. Then try again if it boots.
Is your battery enough charged? That could also be a reason.
did not work, wont even boot up
when i said if i leave battery out and such, I thought it might be hardware/heat related
http://www.htcwiki.com/thread/2069847/HTC+Diamond+-+Severe+Crashing+Problem,+maybe+heat+related
could this be it? will i have to send my phone for repairs?
because maybe when WinMo was loaded, the phone started to heat up and it shut down
so basically my solution is not a software fix??
If none of the tips worked, and you have the same problems as described in the site you linked, then you probably have to send it back.
One thing you could do: Try if the other hard-spls (1.37 and 1.93 unsigned) are working for you.
I'm sorry for you, maybe someone more skilled than me (like cmonex or olipro) knows how to solve your problem.
it's alright :S i thank you for all the help you have offered !
( it is customizing right now) but i expect it to reboot anytime now
worked, 5 minutes into winmo it restarts
mzaouar said:
worked, 5 minutes into winmo it restarts
Click to expand...
Click to collapse
oh,does it worked?how can you get it work?Please tell me....my diamond could only get in the bootloader yet....
mzaouar said:
worked, 5 minutes into winmo it restarts
Click to expand...
Click to collapse
OK good to hear that, if you have any more questions in future, just ask!
Glad to be of some help
msvb007 said:
oh,does it worked?how can you get it work?Please tell me....my diamond could only get in the bootloader yet....
Click to expand...
Click to collapse
Ive sent you a pm, there's no need to use this thread for your questions because the problem in this thread is solved.
So take a look at your pm!
Hello,
afther an update on my p3600 with an error.
I have only the bootscreen of the rom.
I cant flash any new rom , every time i have connection errors.
is there any chance to correkt the problem or to delet the phone completly?
A Hardreset doesn´t bring anything.
Please help me i cant do anything with my p3600.
take a look:
http://forum.xda-developers.com/showthread.php?t=572747
i read the thread,
but i have tested to update the hard spl but it doesn´t work.
The update software always told me that there is an connection error.
But when i want to install the rom 6.1 manila 2g the software found an connection and start to update but when the software is at 1% the update software told me that the rom is corrupt
This is the reason you should always install HardSPL BEFORE you start flashing any roms at all.
Once you have bricked it, then it is too late to put HardSPL on there.
The whole point of HardSPL is to ensure that you will always be able to get a connection to the device even if you have a broken rom on there.
If the phone is bricked, with no HardSPL on there, your only remaining option would be to try using an unbricking exploit procedure like this:
HTC Trinity Stack Overflow exploit - how to unbrick any Trinity stuck in bootloader!!
^^^ Sorry I have never had to do this myself and have no experience or advice on how to use that exploit utility ... hopefully there is enough help in that thread to get you going again.
Good luck.
EDIT: I thought I'd better just check you do realise that you can get the Tri-colour SPL screen up manually by holding down POWER + CAMERA buttons and 1sec press of STYLUS RESET button. Quickly reading through that splxploit thread I was disturbed to see just how many people didn't even know who to do that
Maybe it's just my paranoia from owning an "i" model but I have never done a single rom flash without first using that 3 button trick to get into SPL screen.
praefke1986 said:
...But when i want to install the rom 6.1 manila 2g the software found an connection and start to update but when the software is at 1% the update software told me that the rom is corrupt
Click to expand...
Click to collapse
Try flashing the Stock ROM that came with your phone. It may get you going again. Can be downloaded from the HTC website.