Develop Bugs

[Help] White-Screen after 3-26 LVSW firmware flash

Sorry to open a new thread, but I want to ask is there any method to fix this problem apart from using Mitty?
I tried flashing LVSW 3-26 firmware using SPL 1.06 or the 1.1x, both gave me the end results of white screen.
I am newbie to Mitty and worry of bricking my device with Mitty.
Can anyone suggest what I could do to cast the white screen away?
Desperately in need of help.
Thanks

I see by the sorry for a new thread you have read
http://forum.xda-developers.com/showthread.php?t=299644
I am with you. Right now I would go to a different version. The previous LSVW or another build. I am trying the mtty thing but I am running vista and cannot get NBHextract to work.
If you do not want to risk it maybe holding off a day and checking back for an update. These guys are fast. Also like I said go to a different version. I flashed the revious LSVW os only and it worked 3 times in a row perfect

When you say white screen what do you mean?? You get a white screen and the device doesnt boot?? or the device has a white today screen?

people
for black 1.3 i will release two versions
one with SPL and OS (with RUU 3.6)
and
one with only OS using standard RUU (assuming you already have HardSPL)
this will give u an option

jasjamming said:
people
for black 1.3 i will release two versions
one with SPL and OS (with RUU 3.6)
and
one with only OS using standard RUU (assuming you already have HardSPL)
this will give u an option
Click to expand...
Click to collapse
Hell yes. Makes the guide clearer to make (i will mention the value of embedded HardSPL and radio though )

mrvanx said:
When you say white screen what do you mean?? You get a white screen and the device doesnt boot?? or the device has a white today screen?
Click to expand...
Click to collapse
The White Screen for me is i can see the HTC Flash screen, but the Windows Mobile screen becomes white without me even seeing it and the Today screen is also white also.

Also, i was wondering if using Hard-SPL might help?
Thanks

nope i am using hard spl and tried it still white screen

Me too....
I also got the white screen of death. lol.
i used the version that was posed on the main page. After the update and initial boot the white screen comes on.
I was able to bypass this after several resets. Then it will start the customisation process. After which it will restart and go to a white today screen with no icons. I do have the task bars at top and bottom but no dialer.
My fix. I went and dl RUU_HER_6.20.100.0_0.00.00.00_XDA_WWE_XBOW_Custom. I installed it and works like it did before.
I will wait till there is a fix for this...
BTW I have a cingular 8525

I WANT TO OFER YOU GUYS SOMTHING
those of you who got white screen do you have language on boot?
i mean do you have diffrent language pack that need to be boot when you make hard reset?
cause i notice that when my language pack boot with new rom igot
white screen the language pack stuck it
then i remove my language pack from booting then its ok!!

After 1 whole day 24 hours non-stop fidgetting with my device, still NO LUCK...
Flashed it so many times, but still white screen.
Anyone can help me out?
Thanks

HKFreak said:
After 1 whole day 24 hours non-stop fidgetting with my device, still NO LUCK...
Flashed it so many times, but still white screen.
Anyone can help me out?
Thanks
Click to expand...
Click to collapse
Think this should help, I did cut the quote down a bit.
mxlaser said:
After hours and sleepless night, and so many flashes i think the NAND in my dopod was hot enough to fry a breaky for me, i've come to the comclusion, i have 100%, no issue success with all ROMS, using 1.01MFG and MTTY flashing each part seperatly. Not one time has a white screen appeared, with ANY rom, and i've tested all the current WM6 roms.
I d/l'd and tried the latest LVSW rom (26/3) and have exactly the same issue when using the packaged RUU to install it. However, when i use MTTY, its perfect every time.
I would suggest the following steps
1. Load into the bootloader mode (HOLD POWER/OK buttons and press soft reset)
2. Flash SPL-1.01MFG onto your device (Read wiki info and file links here)
3. Once flashed, reboot and do step one again to get back into boot mode. You should now see your boot as 1.01MFG
4. Use NBHextract to extract 06_OS.nb file from RUU_signed.nbh file found in downloaded rom package.
5. Load up MTTY, follow steps in the wiki for the 1.01MFG on how to flash OS.nb (OS.nb is the 06_OS.nb file renamed to make it easier)
6. Once flash is complete, the latest rom is installed and you won't have a white screen
7. Now flash Hard SPL v4 onto your devic for safety reasons.
And this fix is EASY to do, 100% works every time.
Click to expand...
Click to collapse
It worked 100% for me first time.

Just for the record I used ROMbaker to get the 06_os.nb then just rename it to os.nb.
Also if you are not sure and feel nervous about bricking it, then just wait for a proper fix.
Finally I got the white screen a few times and everytime I flashed the previous LSVW os only the device worked perfect. From my reading Olipro may have found the problem haveing to do with bad blocks. Nothing major but I believe they are working on it currently.

If you follow these directions and install 1.01MFG, you can BRICK YOUR DEVICE with ANY mistake!
We're not talking about a brick that can be fixed either. You precious phone will become a paper-weight forever more! Really.
I DON'T CARE WHAT THE N00BS ON HERE SAY; FLASHING 1.01MFG IS **NOT** A RECOMMENDED WAY TO FIX THIS PROBLEM! DO NOT INSTALL 1.01MFG UNLESS YOU ARE OK WITH THE CHANCE THAT YOUR PHONE WILL BE BROKEN FOREVER!!

bubu23 said:
I WANT TO OFER YOU GUYS SOMTHING
those of you who got white screen do you have language on boot?
i mean do you have diffrent language pack that need to be boot when you make hard reset?
cause i notice that when my language pack boot with new rom igot
white screen the language pack stuck it
then i remove my language pack from booting then its ok!!
Click to expand...
Click to collapse
No, I have never installed any language packs on my phone. I use good ol' english.

HKFreak said:
After 1 whole day 24 hours non-stop fidgetting with my device, still NO LUCK...
Flashed it so many times, but still white screen.
Anyone can help me out?
Thanks
Click to expand...
Click to collapse
Just go back to a previous version of WM6.
It only takes several minutes to put back XDA- Live.

mzahiri said:
Just go back to a previous version of WM6.
It only takes several minutes to put back XDA- Live.
Click to expand...
Click to collapse
I tried going back to WM5 firmware.
Flashing the firmware is a success but I still got the white-screen-of-death.
Any other options?
Thanks

SPL-1.35.Olipro will be released shortly; this should address the issue of the whitescreen error, all those having problems under 1.30 should no longer encounter it if they were able to flash fine with old SPL's

Olipro said:
SPL-1.35.Olipro will be released shortly; this should address the issue of the whitescreen error, all those having problems under 1.30 should no longer encounter it if they were able to flash fine with old SPL's
Click to expand...
Click to collapse
Go Oli Go!

Question ?
Hi All,
Sorry N00b alert at this .. but very IT literate
Just a quick question off the cuff, what was the last(est) version (can you provide a link) that i can flash to now .. (not mucking around seperating stuff etc) that wont give me the white screen issue.
I am currently sitting on LSVW 25/3 1.38.10 radio and 1.13oli
Thanx test

Did I Brick My Phone?

Ok I've flashed close to a dozen times using various great ROMS everyone has provided and never had a problem. Today I realized that ATT/HTC released their official ROM yesterday and I thought I would give it a try. I followed their instructions but it did not work.
My phone looked as though it was updating and it got stuck at 11%. Followed the instructions to recover and it still did not work. Now my phone is stuck at the Triple Color Bar screen and I cannot do anything.
Did I brick my phone?
Can I use some of the options to try to unbrick in the xda wiki?
Thank you in advance.
- Monty

Have you tried flashing a different rom or using a different pc to flash with?

i managed to revive mine from that state the key is getting the usb to let you update again dont plug in the cable until after the ruu is looking for the connection might take a couple tries but that worked for me.

Hi
Try this:
1) Turn your phone off completely
2) Hold the side OK button and the power button, at the same time push the reset button at the bottom with your stylus.
3) this should get you into the bootloader (the three colour screen)(dont be lazy and just let it load into the bootloader, actually run the key sequence ive just mentioned!)
4) on your PC run the update, i would reccomend the latest official update for your handset, BUT, do the following:
a) Make sure you have WinRAR installed
b) Right click on the update file you have just downloaded
c) 'Extract' the update file to the folder it makes
d) within that folder should be ANOTHER executable file that has the same icon as the original update
e) Extract this file again
f) open the folder it makes and within that there should be a RUUSIGNED.NBH and also the RUU utility itself
5) Run the update utility in the second folder
6) once the utility has loaded, plug your phone in (the text will change from 'SERIAL' to 'USB')
7) proceed with the update and see what happens
hope that helps
good luck.

MontyV77 said:
Ok I've flashed close to a dozen times using various great ROMS everyone has provided and never had a problem. Today I realized that ATT/HTC released their official ROM yesterday and I thought I would give it a try. I followed their instructions but it did not work.
My phone looked as though it was updating and it got stuck at 11%. Followed the instructions to recover and it still did not work. Now my phone is stuck at the Triple Color Bar screen and I cannot do anything.
Did I brick my phone?
Can I use some of the options to try to unbrick in the xda wiki?
Thank you in advance.
- Monty
Click to expand...
Click to collapse
You should not update using the Oficial ROM release Update because you put in the boot loader from here (Hard-SPL-V7) and it will try over righting the entire rom if you do and is probably what messed up your update attempt. Use Dutty's NBH tool and just decompile the NBH of the official rom, then recompile the windows, splash screens and radio into a new NBH then flash using the RUUwrapper from this site to flash the phone.

TooSharp said:
Have you tried flashing a different rom or using a different pc to flash with?
Click to expand...
Click to collapse
Yes I've tried two different Official ATT ROMs and on different computers but same problem. Actually the only one that will attempt to start loading are the ATT ROMs and none of the cooked ROMs here are loading. Maybe that has something to do with the way they are packaged.
Jefem24 said:
i managed to revive mine from that state the key is getting the usb to let you update again dont plug in the cable until after the ruu is looking for the connection might take a couple tries but that worked for me.
Click to expand...
Click to collapse
Yeah I've done this now over a dozen times since yesterday and still no luck.
duke_stix said:
Hi
Try this:
1) Turn your phone off completely
2) Hold the side OK button and the power button, at the same time push the reset button at the bottom with your stylus.
3) this should get you into the bootloader (the three colour screen)(dont be lazy and just let it load into the bootloader, actually run the key sequence ive just mentioned!)
4) on your PC run the update, i would reccomend the latest official update for your handset, BUT, do the following:
a) Make sure you have WinRAR installed
b) Right click on the update file you have just downloaded
c) 'Extract' the update file to the folder it makes
d) within that folder should be ANOTHER executable file that has the same icon as the original update
e) Extract this file again
f) open the folder it makes and within that there should be a RUUSIGNED.NBH and also the RUU utility itself
5) Run the update utility in the second folder
6) once the utility has loaded, plug your phone in (the text will change from 'SERIAL' to 'USB')
7) proceed with the update and see what happens
hope that helps
good luck.
Click to expand...
Click to collapse
This looked the most promising maybe because it felt like I was doing something and I was using the ATT ROM again to update, and it actually started updating again. But it stopped at 11% again and gave me the 262 error.
Below pulled from readme.txt file.
"ERROR [262, 276, 284, 302] : UPDATE ERROR
This error occurs during the CE ROM code upgrade process.
Solution: If this happens, you can just soft-reset the device and run RUU again. The update process will then continue.
Note: At this stage, the Wince is destroyed; instead, it is in upgrade mode."
Click to expand...
Click to collapse
Tried to soft-reset and reinstall but same problem.

Scrambler001 said:
You should not update using the Oficial ROM release Update because you put in the boot loader from here (Hard-SPL-V7) and it will try over righting the entire rom if you do and is probably what messed up your update attempt. Use Dutty's NBH tool and just decompile the NBH of the official rom, then recompile the windows, splash screens and radio into a new NBH then flash using the RUUwrapper from this site to flash the phone.
Click to expand...
Click to collapse
Haven't yet tried this because I am having a hard time getting details on this. I've been searching looking for "duttythroy nbh tool", "nbh tool", "dutty nbh tool", and "dutty's nbh tool" and I can't find it.
If this helps anyone this is what I have on my tri-color screen:
HERM100
IPL - 1.04
HERM100
SPL - 2.03
Click to expand...
Click to collapse

You can also try to flash from the SD card:
- format a SD card with FAT32
- extract the .NBH file from the rom image you like (for your device of course)
- rename the .NBH to HERMIMG.NBH and copy it to your SD card
- put SD card in phone and start it in bootloader (hold OK button on left side and POWER button at same time and stick with stylus in RESET on bottom)
- confirm flashing on screen
- flashing might hang after some time but this is normal. Just wait. Complete flash takes about 30 minutes.
This also works for normal (non preproduction) devices but keep in mind that if the CID does not match the flashing might not work. - this was taken from one old thread
- notes - you should backup everything on your SD card to your PC (because except for HERMIMG.NBH it should be blank)
- you can not get USB related error because it loads from a card
- if you flash official ROM you flash it with everything - radio ROM, Windows and bootloader
I am not really sure about bootloader you should have but for official upgrade official bootloader should be ok (it is first thing to be flashed - so I think you have bootloader from ATT ROM already.
Hope it can help somehow...

hey, what is your spl version?

it should say on your bootloader mode
and then read this http://wiki.xda-developers.com/index.php?pagename=Hermes_Unbrick
that really helps a lot, it has the solution and stuff. hope you unbrick your phone! all i did was download the update and it reloaded to wm5 update on my 8525 then after that, i went for olipro's 2.10 so i dont unbrick it anymore =) then flash all you want!

oh yea the factory update for my 8525 that unbricked my phone was this http://www.htcamerica.net/support/8525/software-downloads.html
try loading that in your phone =)

Ok that was the oddest thing but it worked. I've been trying to possibly unzip some of the packages by way of what duke_stix instructed. My last ROM was Schaps most recent 4.0. I unzipped what he had and ran the RUU file. What was funny though is that it started updating up to 3% then gave me the 260 error but this time my phone restarted and booted back up. I don't know what happen but it works now. If this is suppose to go in as a fix I don't know what happen.
Thank you everyone for all your help. I want to reflash my ROM but I will wait until I see this working for a while.
- Monty

asianr0cker said:
...i went for olipro's 2.10 so i dont unbrick it anymore =) then flash all you want!
Click to expand...
Click to collapse
How do I change my SPL to 2.10 now?

Here is nice tutorial how to flash HardSPL v7 (a.k.a. bootloader 2.10 Olipro). Glad to see you are out of brickland

KarhU said:
Here is nice tutorial how to flash HardSPL v7 (a.k.a. bootloader 2.10 Olipro). Glad to see you are out of brickland
Click to expand...
Click to collapse
Thank you just finished flashing it. Thanks again to all that helped.

MontyV77 said:
How do I change my SPL to 2.10 now?
Click to expand...
Click to collapse
See mrvanx.org
... Edit: That's what you get for waiting 10 minutes before posting. Doh!

Thank You So Much !
I did all pricedures and it worked perfectly. You are the best dude!
duke_stix said:
Hi
Try this:
1) Turn your phone off completely
2) Hold the side OK button and the power button, at the same time push the reset button at the bottom with your stylus.
3) this should get you into the bootloader (the three colour screen)(dont be lazy and just let it load into the bootloader, actually run the key sequence ive just mentioned!)
4) on your PC run the update, i would reccomend the latest official update for your handset, BUT, do the following:
a) Make sure you have WinRAR installed
b) Right click on the update file you have just downloaded
c) 'Extract' the update file to the folder it makes
d) within that folder should be ANOTHER executable file that has the same icon as the original update
e) Extract this file again
f) open the folder it makes and within that there should be a RUUSIGNED.NBH and also the RUU utility itself
5) Run the update utility in the second folder
6) once the utility has loaded, plug your phone in (the text will change from 'SERIAL' to 'USB')
7) proceed with the update and see what happens
hope that helps
good luck.
Click to expand...
Click to collapse

if its an official rom you may need to hard sol it first as i had the same problem updating to original after a chefs special

blowfeld said:
if its an official rom you may need to hard sol it first as i had the same problem updating to original after a chefs special
Click to expand...
Click to collapse
what is a hard sol and how do I do it? I wanna go back to the OEM Official ROM to see if it fixes my no service phone problems.

Ok, I've tried everything that was posted in this thread and nothing worked so far.
My last setup before trying to reinstall the Radio is:
AT&T 8525 (location - Hawaii)
Black Majik's WM6
Herm Radio 1.43.00.00
Hard SPL-V7
The OS has been working great until this previous Monday. Also just in case if this is any relevant, Hawaii has just recently upgraded and turned on it's 3G network just a couple of weeks ago. They are still tweaking the whole thing to make sure all is well. Unfortunately it seems that something they did this past Monday seemed to really screw up the 8525's.
The reason I'm trying to reinstall my radio is because I happened to go to the phone settings, and saw that there was no Radio version on the screen. Thought this might also add to the problem.
Well where I'm at now is that I'm stuck at the Tri-Color loader screen. I've read the Wiki regarding fixing a bricked phone. Doesn't seem to help.
So I'm now stuck and need expertise of more knowledgeable members who might have been in the same situation as me.
Please, really need help as this is a company phone and I've got to get it working cause I don't wanna have to pay for it.

Help ASAP... Dash can not flash to any roms

Hey, currently i have kavana rom installed from a long time ago and it seem like when i turned it on this morning the whole rom is messed up.. my two left and right soft key doesn't work and i can't even go to settings or anything.. I try to flash it back to its original tmobile rom but it doesn't work... anyone have any suggestion? i haven't used this phone for a long time and i need to lend it to my uncle so i need a answer asap. thanks!

btw... it keep saying the image file is corrupted!

stuck on HTC screen!!!
i tried doing the hard reset but after i press the send button it just stays at the htc screen. I was flashing the original tmobile rom and i accidently dropped it and lost connection, after that it gets stuck on the htc screen and wont start up... what can i do? is this fixable?

i believe if you go to the bootloader screen you can flash back to the original t mobile rom. ummm use the wiki tab to find the rom and how to get to that screen. hope this helps

Yes it is fixable. All you have to do is hold the camera (sym) button down for about 10 seconds, then plug the usb cable in while still holding it down. You now should see a tri-colored screen. When you see this screen you can flash you phone with the OFFICIAL ROM (the rom the phone came with).
This rom could be found below (in my signature).
Hope this helps.
Also, once you have the original rom on there you can always reflash to the new 6.1 rom or whatever rom you would like.

Try to download the Tmobile Rom from below (in the official rom section) I have this posted in my signature.

jdoggraz said:
Yes it is fixable. All you have to do is hold the camera (sym) button down for about 10 seconds, then plug the usb cable in while still holding it down. You now should see a tri-colored screen. When you see this screen you can flash you phone with the OFFICIAL ROM (the rom the phone came with).
This rom could be found below (in my signature).
Hope this helps.
Also, once you have the original rom on there you can always reflash to the new 6.1 rom or whatever rom you would like.
Click to expand...
Click to collapse
i did exactly as you have told me but it is still stuck on the HTC screen. I turned on the phone, held down the sym button/camera for 10 seconds i tried holding it longer and then plug the usb cable back in but it is still stuck on the HTC screen. thanks

Ok take out the battery, then insert the battery in. Hold the button down and make sure the usb is plugged in the computer and then plug it in to the phone.

jdoggraz said:
Ok take out the battery, then insert the battery in. Hold the button down and make sure the usb is plugged in the computer and then plug it in to the phone.
Click to expand...
Click to collapse
alright thanks got it to the boot loading screen/tri color. ok as you have read my previous post... now i can't flash it to any rom. it keep saying the image file is corrupted.. i downloaded everything again and it still says the same thing. When my dash was able to start up i ran the CID bypass and then run the rom installer and it worked but like i said, i accidently dropped it and lost connection. now i can't even run the CID bypass cause i can't even start up the phone... what should i do?

Well you will need to flash it with the original rom the phone came with, i.e. if its a tmobile phone, then you must reflash with the tmobile rom... Once you have the tmobile rom up and running then you can reflash with any other rom i.e. the 6.1 rom.

and you can find the original roms under offical roms below.

jdoggraz said:
Well you will need to flash it with the original rom the phone came with, i.e. if its a tmobile phone, then you must reflash with the tmobile rom... Once you have the tmobile rom up and running then you can reflash with any other rom i.e. the 6.1 rom.
Click to expand...
Click to collapse
alright.. i kinda got it working and its flashing right now.. thanks for ALL your help.. i appreciated!

porkch0p said:
alright.. i kinda got it working and its flashing right now.. thanks for ALL your help.. i appreciated!
Click to expand...
Click to collapse
Oh no problem, once you have the rom all working then you can download the new 6.1 from below. I recommend using it because its awesome. Also once you install this rom make sure you run connection setup under the tools folder to get the network working.

Would I need the unlock code again?
How do I use that T-Mobile download? It only has a single file? Any guidance welcome.

T-Mobile Dash
1.22.531.6 (T-Mobile USA, WM6)
http://www.mediafire.com/download.php?z4vjgzxisrz
1.22.531.4 (T-Mobile USA, WM6)
http://www.mediafire.com/download.php?yygkw1d5xmc
http://member.htc.com/RuuDownload/T-...eDownload.aspx Valid T-Mobile IMEI Required
1.11.531.1 (T-Mobile USA, WM5)
http://rapidshare.com/files/10464194...531.1.exe.html
T-Mobile MDA Mail
Files Needed to Upgrade or Downgrade (With only the .nbh file)
----------------------------------------------------------------------------------------
Click to expand...
Click to collapse
Where it says "Files Needed to Upgrade or Downgrade (With only the .nbh file)" Click on that and there should be a text file giving you instructions on how to continue.

I get the fundamentals of Simunlock v/s AppUnlock etc.
It was SimUnlocked using Unlock code I had got from T-Mobile.
1. It already has the latest Official ROM version on it (i.e. I tried doing it with the latest T-Mobile) and it shows the version I have is the same.
Do I need to reflash it with the ROM that is aleady present on my DASH? Is it worth trying that?
2. Now the step called AppUnlock? Which tool should I use given that I would have the T-Mobile Carrier 6.1 ROM on it (either already or reflash with T-Mobile 6.1 AGAIN)
3. After AppUnlock should I go for the FLASHing guide? Which one would that be?

HTC Diamond bricked?

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!

[Q] How to revive a BlueAngel?

Hello everyone!
I'm new at these forums, so excuse me if I'm being a "noob". I've searched all over the forums and found some instructions for my problem, but none of them helped.
My story is:
I have a T-Mobile MDA III device (I think it's also called HTC BlueAngel). It had the stock ROM, without any modifications. It was WM2003 I suppose.
I wanted to upgrade it to WM6, using this. In that thread it was recommended to use the updater given there, so I downloaded everything and tried to flash. After about 30 seconds of verifying information on the PDA, I got to a screen where it was supposed to say From and To version numbers, but everything was blank. I also have successfully flashed a HTC Trinity P3600 and those fields were blank there too, so I thought it's OK and pressed Continue. The program started to process, but after a while it said isn't designed for my device. I have tried numerous ROMs and RUUs to update it, but all of them gave some sort of error, some said "Congratulations, update complete" even if it didn't do anything.
The problem is, that my PDA is now stuck at the bootloader (?) screen. The backlight is off, the top of the screen says Serial (USB when cradled) and on the bottom I can see a version number (v2.05). I have read about key combinations (Camera, power, reset, record, etc) which are used to exit this state, but none of them worked. If I cradle my device, Windows (Windows 7, 64bit) recognizes the device as "Microsoft USB Sync", but WMDC doesn't see my device at all. On the forums I've read that in this state the device allows ROM updating, but I haven't found anything that could work, and the RUUs don't seem to recognize my device.
So if anyone has a ROM and updater that can work with this device, please link it to me, it's very important. I don't want to lose my PDA. If you haven't got a WM6 ROM, it can be even WM5, or even the stock ROM of this device, I just want to somehow revive it. Really, any ROM will do, just give me the proper updater and ROM. Or if you think the ROM wasn't erased from the device, please help me getting back to it.

JiGSaW_HTC said:
Hello everyone!
I'm new at these forums, so excuse me if I'm being a "noob". I've searched all over the forums and found some instructions for my problem, but none of them helped.
My story is:
I have a T-Mobile MDA III device (I think it's also called HTC BlueAngel). It had the stock ROM, without any modifications. It was WM2003 I suppose.
I wanted to upgrade it to WM6, using this. In that thread it was recommended to use the updater given there, so I downloaded everything and tried to flash. After about 30 seconds of verifying information on the PDA, I got to a screen where it was supposed to say From and To version numbers, but everything was blank. I also have successfully flashed a HTC Trinity P3600 and those fields were blank there too, so I thought it's OK and pressed Continue. The program started to process, but after a while it said isn't designed for my device. I have tried numerous ROMs and RUUs to update it, but all of them gave some sort of error, some said "Congratulations, update complete" even if it didn't do anything.
The problem is, that my PDA is now stuck at the bootloader (?) screen. The backlight is off, the top of the screen says Serial (USB when cradled) and on the bottom I can see a version number (v2.05). I have read about key combinations (Camera, power, reset, record, etc) which are used to exit this state, but none of them worked. If I cradle my device, Windows (Windows 7, 64bit) recognizes the device as "Microsoft USB Sync", but WMDC doesn't see my device at all. On the forums I've read that in this state the device allows ROM updating, but I haven't found anything that could work, and the RUUs don't seem to recognize my device.
So if anyone has a ROM and updater that can work with this device, please link it to me, it's very important. I don't want to lose my PDA. If you haven't got a WM6 ROM, it can be even WM5, or even the stock ROM of this device, I just want to somehow revive it. Really, any ROM will do, just give me the proper updater and ROM. Or if you think the ROM wasn't erased from the device, please help me getting back to it.
Click to expand...
Click to collapse
Remove the battery and look which model you have....
something like PH20B or the FCCID: xxxBLUEANGEL...

d-two said:
Remove the battery and look which model you have....
something like PH20B or the FCCID: xxxBLUEANGEL...
Click to expand...
Click to collapse
It says:
PH20B MDA III
FCCID: NM8BLUEANGEL

JiGSaW_HTC said:
It says:
PH20B MDA III
FCCID: NM8BLUEANGEL
Click to expand...
Click to collapse
Please look here for install the right driver for windows 7 64x

d-two said:
Please look here for install the right driver for windows 7 64x
Click to expand...
Click to collapse
Thanks, I've downloaded the PDFs and tried to follow the steps, but there were some problems.
The first strange thing I noticed was that the driver said it was already installed to my computer. I think that's not a problem, but still worthy to mention.
I have completed the driver installation, so I moved on to the ExtROM tutorial. Unfortunately this step failed completely, because it needs a working BA, and as I've said I'm stuck on the bootloader screen. Also I've tried to reflash the WM2003 that was in the tutorial, but it said that the Updater is not designed for my device. So I moved on to the final step, flashing - I downloaded the Updater and tried to flash the WM2003 you provided. I kept pressing Continue - but after getting to the last page, and pressing Continue for the last time, after about 10 seconds, the updater said Congratulations! The ROM have been updated successfully. But that was just a message, my BA acted like nothing happened. I'm still in the Bootloader and can't do anything. What am I doing wrong?

JiGSaW_HTC said:
Thanks, I've downloaded the PDFs and tried to follow the steps, but there were some problems.
The first strange thing I noticed was that the driver said it was already installed to my computer. I think that's not a problem, but still worthy to mention.
I have completed the driver installation, so I moved on to the ExtROM tutorial. Unfortunately this step failed completely, because it needs a working BA, and as I've said I'm stuck on the bootloader screen. Also I've tried to reflash the WM2003 that was in the tutorial, but it said that the Updater is not designed for my device. So I moved on to the final step, flashing - I downloaded the Updater and tried to flash the WM2003 you provided. I kept pressing Continue - but after getting to the last page, and pressing Continue for the last time, after about 10 seconds, the updater said Congratulations! The ROM have been updated successfully. But that was just a message, my BA acted like nothing happened. I'm still in the Bootloader and can't do anything. What am I doing wrong?
Click to expand...
Click to collapse
You have not read the tutorial right... you must install the driver manual!!!!

JiGSaW_HTC said:
Thanks, I've downloaded the PDFs and tried to follow the steps, but there were some problems.
The first strange thing I noticed was that the driver said it was already installed to my computer. I think that's not a problem, but still worthy to mention.
I have completed the driver installation, so I moved on to the ExtROM tutorial. Unfortunately this step failed completely, because it needs a working BA, and as I've said I'm stuck on the bootloader screen. Also I've tried to reflash the WM2003 that was in the tutorial, but it said that the Updater is not designed for my device. So I moved on to the final step, flashing - I downloaded the Updater and tried to flash the WM2003 you provided. I kept pressing Continue - but after getting to the last page, and pressing Continue for the last time, after about 10 seconds, the updater said Congratulations! The ROM have been updated successfully. But that was just a message, my BA acted like nothing happened. I'm still in the Bootloader and can't do anything. What am I doing wrong?
Click to expand...
Click to collapse
Can't you exit bootloader screen by simultaneously pressing power and reset?
Did you disable USB-Connection in activesync? Is important to do.
If update runs till "congratulations" in very short time (update usually takes about 10 minutes - estimated ), it seems like updater didn't see the nk.nbf file, which should be 32.769KB.
Please don't throw bricked phones at me, but- is the file unzipped? (note: i don't mean opened)
And: though d-two has given you the drivers for Win7 (and he's the one you can really trust he's got the right stuff) you may just try
another PC. Many people have trouble when trying to update with Win7. I still use XP.

B-44 said:
Can't you exit bootloader screen by simultaneously pressing power and reset?
Did you disable USB-Connection in activesync? Is important to do.
If update runs till "congratulations" in very short time (update usually takes about 10 minutes - estimated ), it seems like updater didn't see the nk.nbf file, which should be 32.769KB.
Please don't throw bricked phones at me, but- is the file unzipped? (note: i don't mean opened)
And: though d-two has given you the drivers for Win7 (and he's the one you can really trust he's got the right stuff) you may just try
another PC. Many people have trouble when trying to update with Win7. I still use XP.
Click to expand...
Click to collapse
If I press power and reset simultaneously, the screen goes dead for a second, then bootloader comes up again.
Tried disabling USB connection in WMDC (No activesync for Win 7), it changed nothing.
The nk.nbf is EXACTLY 32.769KB, so I don't know why it won't see it. With some versions it sees it but gives me an error 150 (RUU not designed for this device).
If by unzipped you mean extracted, yes, all the files (EnterBL.EXE, nk.nbf, MaUpgradeUt_noID.exe, etc.) are extracted to a folder, it looks the same as in D-Two's tutorial.
Unfortunately I don't have an XP PC. Will using a Vista laptop do any better, or should I use some kind of emulator of XP and update from there? If so, can you link me to one of those?

Sh*t.
Take out the battery for at least three days.
Then retry.
I lately had an VPA3 revived by this.
Always stuck in first step of bootscreen, already wanted to abandon it,
then after some days retried just out of some mood.
Worked.
XP emulator may be a good idea, but i'd have to google it the same way like you.
Because of my Siemens phones i haven't yet left original XP.

B-44 said:
Sh*t.
Take out the battery for at least three days.
Then retry.
I lately had an VPA3 revived by this.
Always stuck in first step of bootscreen, already wanted to abandon it,
then after some days retried just out of some mood.
Worked.
XP emulator may be a good idea, but i'd have to google it the same way like you.
Because of my Siemens phones i haven't yet left original XP.
Click to expand...
Click to collapse
he is not stuck at the 4 color screen he stuck in the bootloader mode..
If the bootloader mode active with software is he not wakeup after 3 days without battery or something else...
the BLENTER.EXE erase at adress 0x40000 the first 4 bytes and this will active the bootloader mode!!!
you must install the driver like in the PDF!!!
and than you can flash it with any rom!!
if you have install the driver correct it must like this...
sorry for my bad english

d-two said:
he is not stuck at the 4 color screen he stuck in the bootloader mode..
If the bootloader mode active with software is he not wakeup after 3 days without battery or something else...
the BLENTER.EXE erase at adress 0x40000 the first 4 bytes and this will active the bootloader mode!!!
you must install the driver like in the PDF!!!
and than you can flash it with any rom!!
if you have install the driver correct it must like this...
sorry for my bad english
Click to expand...
Click to collapse
No problem about your english, mine isn't perfect too
I realized what is the problem. When installing the driver manually, it says that the driver is not signed, and therefore I can't install it. I do everything the same as you did, but I fail at this step. I can't get it to install. Any solutions for this? :\ I'm starting to worry about this.

JiGSaW_HTC said:
No problem about your english, mine isn't perfect too
I realized what is the problem. When installing the driver manually, it says that the driver is not signed, and therefore I can't install it. I do everything the same as you did, but I fail at this step. I can't get it to install. Any solutions for this? :\ I'm starting to worry about this.
Click to expand...
Click to collapse
Reboot your PC and press before windows start "F8" and select the option "Start without driver signature" or something else...
I don't know what is the exactly word spelling in English i use my windows in German :laugh:

d-two said:
Reboot your PC and press before windows start "F8" and select the option "Start without driver signature" or something else...
I don't know what is the exactly word spelling in English i use my windows in German :laugh:
Click to expand...
Click to collapse
Found this option and I could install the driver You sent to me.
But the RUU still doesn't see my device. It acts the same as I was running it without my device.

JiGSaW_HTC said:
Found this option and I could install the driver You sent to me.
But the RUU still doesn't see my device. It acts the same as I was running it without my device.
Click to expand...
Click to collapse
have you use my updater?

d-two said:
have you use my updater?
Click to expand...
Click to collapse
Ignore my previous message. I just needed to reboot the computer. It updates now!! Thank you VERY VERY MUCH!! Finally I can use my PDA again Pressing Thanks button