Database Develop

Not a happy bunny...

Well, it seems that my BA finally broke (WM5 anyway). It happened when i was flashing back from a test rom to ivans latest version, i flashed, booted up and got to the wight screen, and stayed there... for 30 minutes. undettered i then tried every WM5 rom i could lay my hands on, but to no avail. in final desperation i downgraded to wm2003se and lo and behold it worked!
Anyone got any idea how to get wm5 working again on my ba?

just reflash back to WM5
thi is a rare bug, which occures, and the fix is downgrade to 2003 and then upgrade to WM5

done that, twice

have u tried to format your extended rom ?
there is topic out there, but show how to do it.
u could give that a try.

reflash everything including radio and ext rom, use radio 1.13, after flashing WM2003 try to flash WM5, please post the result. If this does not work i think it is a bootloader issue, if you can get the same version of boot loader and flash it maybe all will work.I am too scared to mess with bootloader yet.

http://forum.xda-developers.com/viewtopic.php?t=46867

Does anyone have command reference for BA bootloader trough mtty

[curse]
**** **** **** **** **** **** ****
[/curse]
right, i ran the mtty thingy, and reformatted the flash, i then went back to 2003se and storage and extrom were working , but then when i tried to go back to wm5 i kept getting a model id error even though i used xda3nbftool.exe to set the same one as in deveicedata.txt but to no avail, when i gave up to go back to wm2003se i found i couldnt exit bootloader! so i tried connecting again via mtty, it all went fine, ran the commands again etc but still stuck in bootloader. out of desperation i took out the battery, but now to my horror the phone wont even turn back one (yes, i've put the battery back in ). has anyone got a clue how to fix this?
Many thanks in advance....
edit - I just tried a bit of percussive maintanace on it and lo and behold... it began to boot
The only problem now is that the boot screen is f*cked up and i get a model id error whenever i try to upgrade roms (even the official orange shipped extract with no modifications wont run )

http://forum.xda-developers.com/viewtopic.php?t=49611&highlight=model+id+error

@Midget_1990
edit - I just tried a bit of percussive maintanace on it and lo and behold... it began to boot
Click to expand...
Click to collapse
"Percussive Maintenance" rarely fails. Nice term though - I'm sure I'll quote it.
Do post a link to the mtty command reference when you get it.
Cheers

- it just sounds better the 'i threw it at a wall'

Forcing Bootloader Mode

Maybe some of you are already aware of this procedure, maybe not.
Anyway, it worked for me and I decided to share how to do it. Simple.
This procedure should only be used in case you really need enter into a bootloader mode and all other ways to do it has failed! Hold Camera button is one of these I am mentioning.
My Wizard was almost bricked at that time and after I speak with an I-mate technical guy, I got the following:
1. Make sure your i-mate™ K-JAM is not Connected to the PC and remove the dummy card or SD/MMC card
2. On your Desktop PC, open Microsoft ActiveSync, then go to File >Connection Settings >Remove the Selection from “Allow USB Connection with this desktop computer”
3. Reconnect your i-mate K-JAM to the Desktop PC using the USB Cradle and the Charger MUST be Connected to the Cradle (Don’t use the IrDA or Bluetooth for the Upgrade)
4. Run the Upgrade again and it will work fine without any problems.
While upgrading, the ActiveSync program will not go on, however the upgrade is running.
Hope it helps!

this realy worked for my (ex)bricked dutch tmobile mda vario !!!!
tip: REALY make shure that there is no wcescomm.exe running all the time and realy remove the sd card else is nogo
btw: my wizard is CID locked! and works like a charm

Thanks buddy!
I'm happy that worked for ya!
Take care!

I'm having a problem
The power went out as I was upgrading my Wizard (Cingular) so now it just turns on at the boatloader screen. I've tried running updates while it was in this screen (it did show the "USB" in the white bar) but most of the time it tells me there is a connection error. Even if I kill Activesync, I notice that when I run the update utility it still runs Activesync. I've tried disabling the USB connection but still get the connection error.
The only time I haven't gotten the connection error was twice it asked me to update but then told me I had the wrong file. This only happened when I tried "upgrading" to 1.05 as I was trying to start again. After it tells me that if I try running it again it gives me the connection error.
Any ideas?

Hi!
Have you already flashed your device once?
Which ipl/spl do you have?
I had problems over 1.05 ROM in the beggining.
If you stuck on bootloader mode, that's a good signal your device is not bricked.
I'd recommend you to disable activesync as you did and reflash it again! Check also if your device is CID unlocked! Search for a thread in the xda developers root.
Try to upgrade to ipl/spl 2.26 first and later to others you want.
Regarding the old file error...can be related to a missing file called enterbootloader.exe.
Hope it works for ya!
Take care
Ironman273 said:
I'm having a problem
The power went out as I was upgrading my Wizard (Cingular) so now it just turns on at the boatloader screen. I've tried running updates while it was in this screen (it did show the "USB" in the white bar) but most of the time it tells me there is a connection error. Even if I kill Activesync, I notice that when I run the update utility it still runs Activesync. I've tried disabling the USB connection but still get the connection error.
The only time I haven't gotten the connection error was twice it asked me to update but then told me I had the wrong file. This only happened when I tried "upgrading" to 1.05 as I was trying to start again. After it tells me that if I try running it again it gives me the connection error.
Any ideas?
Click to expand...
Click to collapse

My device is unlocked as I've been trying different ROMs as of late. I had gone back to the Cingular 2.25 ROM for a couple days to sort some things out and was going to flash Farias AKu 3.3 when my power problems happened. My Current IPL/SPL is 2.25
I've tried flashing the TMobile 2.26 but keep getting connection errors. In fact, I've tried flashing with every ROM I have pdviet 3 and 4, CIngular 2.25, TMobile 2.26 and Custom 1.05. Everything (except twice in the custom) gives me connection errors.
Any other trick I can try?
BTW, I used to live in Sao Paulo years ago...
Edit: OK, so I tried the 2.26 TMobile ROM after I typed this and it worked!! I'm back up but I was having trouble with that ROM beause of some incompatibilities with Cingular. I'll go back to Cingular's ROM and play it safe for now.
I believe part of my problem was I kept trying different updates one after the other. Now that I think back, the 2 times I got the update to almost work was after I turned off the device and turned it on again, which is what I did this time around also.

I had the same problems as mentioned by Ironman before. I followed the steps and with a few slight changes, I managed as well to "unbrick" my wiz. THANKS A LOT for the great step by step manual!!!
Still I wanted to know WHY i bricked my device:
I was trying to upgrade to the underground WM6 ROM. I got the same situation as ironman:
Quote:
The power went out as I was upgrading my Wizard (Cingular) so now it just turns on at the boatloader screen. I've tried running updates while it was in this screen (it did show the "USB" in the white bar) but most of the time it tells me there is a connection error. Even if I kill Activesync, I notice that when I run the update utility it still runs Activesync. I've tried disabling the USB connection but still get the connection error.
The only time I haven't gotten the connection error was twice it asked me to update but then told me I had the wrong file. This only happened when I tried "upgrading" to 1.05 as I was trying to start again. After it tells me that if I try running it again it gives me the connection error.
Unquote
I then followed the instructions by epimazzo as written above. I also tried the T-Mobile ROM 2.26 which was not working for me. PANIC!!!! Error messag was that I had the wrong Vendor ID. THerefore no upgrade to TMob 2.26 was possible. I tried it then my original qtek ROM in my language and see it worked!!! This IMHO means that I did not put the device in a proper IPL1.xx and SPL 1.xx status which is required for a clean system in irder to unlock it! So if it is bricked, try your native AKU2 ROM and make sure you unlocked it properly. Maybe you have to run the 1.05 ROM for a second time after the unlocking.
I hope this helps you guys.

Sounds great to hear that!
I had play around with pdaviet3, underground and another ROM just today without any problems at all. I don't think that this is the case. Now you get your device back to normal, try to reflash it again. Hope it works this time!
BTW,...São Paulo is a nice city. Thanks! Let me know if you decide to come here!
Take care
Ironman273 said:
My device is unlocked as I've been trying different ROMs as of late. I had gone back to the Cingular 2.25 ROM for a couple days to sort some things out and was going to flash Farias AKu 3.3 when my power problems happened. My Current IPL/SPL is 2.25
I've tried flashing the TMobile 2.26 but keep getting connection errors. In fact, I've tried flashing with every ROM I have pdviet 3 and 4, CIngular 2.25, TMobile 2.26 and Custom 1.05. Everything (except twice in the custom) gives me connection errors.
Any other trick I can try?
BTW, I used to live in Sao Paulo years ago...
Edit: OK, so I tried the 2.26 TMobile ROM after I typed this and it worked!! I'm back up but I was having trouble with that ROM beause of some incompatibilities with Cingular. I'll go back to Cingular's ROM and play it safe for now.
I believe part of my problem was I kept trying different updates one after the other. Now that I think back, the 2 times I got the update to almost work was after I turned off the device and turned it on again, which is what I did this time around also.
Click to expand...
Click to collapse

It seems you got the idea!
You did the right thing! Sometimes, use the official ROM can solve many issues out there!
Keep walking!
enlite_de said:
I had the same problems as mentioned by Ironman before. I followed the steps and with a few slight changes, I managed as well to "unbrick" my wiz. THANKS A LOT for the great step by step manual!!!
Still I wanted to know WHY i bricked my device:
I was trying to upgrade to the underground WM6 ROM. I got the same situation as ironman:
Quote:
The power went out as I was upgrading my Wizard (Cingular) so now it just turns on at the boatloader screen. I've tried running updates while it was in this screen (it did show the "USB" in the white bar) but most of the time it tells me there is a connection error. Even if I kill Activesync, I notice that when I run the update utility it still runs Activesync. I've tried disabling the USB connection but still get the connection error.
The only time I haven't gotten the connection error was twice it asked me to update but then told me I had the wrong file. This only happened when I tried "upgrading" to 1.05 as I was trying to start again. After it tells me that if I try running it again it gives me the connection error.
Unquote
I then followed the instructions by epimazzo as written above. I also tried the T-Mobile ROM 2.26 which was not working for me. PANIC!!!! Error messag was that I had the wrong Vendor ID. THerefore no upgrade to TMob 2.26 was possible. I tried it then my original qtek ROM in my language and see it worked!!! This IMHO means that I did not put the device in a proper IPL1.xx and SPL 1.xx status which is required for a clean system in irder to unlock it! So if it is bricked, try your native AKU2 ROM and make sure you unlocked it properly. Maybe you have to run the 1.05 ROM for a second time after the unlocking.
I hope this helps you guys.
Click to expand...
Click to collapse

Excellent post. I messed up with my own cooked ROM and could only get the bootloader screen. Tried the tips here - didn't work first time but I pulled the battery from the KJAM to reset it rather than using the reset button and it worked fine.

In my opinion this thread is so helpful to people who brick their device, it should go "sticky". Mods anything you can do about it?

Thanks buddy! I really appreciate!
We survive here over tips like that!
jt_armstrong said:
Excellent post. I messed up with my own cooked ROM and could only get the bootloader screen. Tried the tips here - didn't work first time but I pulled the battery from the KJAM to reset it rather than using the reset button and it worked fine.
Click to expand...
Click to collapse

Help me similar problem
I upgraded Super Rom, then my Wizard run very slow and no signal (no call out and in- no network at all). And Terible thing is PC could not dectect PPC thought Active Sync. I've soft and hard reset but no use.
So I donot know where to start to re install Rom again.
Please help me....

Hi there!
It seems that you just need to enter into the bootloader mode and reflash it again!
I had similar problems and more during my brick "false" stage!
So, just try to follow my steps here and you should be fine! Once you get into bootloader mode, just use any ROM out there to reflash.
Good [email protected]
thaiphong said:
I upgraded Super Rom, then my Wizard run very slow and no signal (no call out and in- no network at all). And Terible thing is PC could not dectect PPC thought Active Sync. I've soft and hard reset but no use.
So I donot know where to start to re install Rom again.
Please help me....
Click to expand...
Click to collapse

I was about to start a EMERGENCY HELP thread, but I *think* this is the right place instead.
The "touch" of my screen went dead today. It got progressively worse over a few hours, starting with difficulty in using the phone dialer, then random incorrect stuff getting triggered by screen taps.
So I hard reset, and got no response on the fifth alignment cross, meaning 1) "Tap on the screen...; 2) center; 3) top left; 4) bottom left; 5) bottom right. In that I could not proceed with alignment, I hard reset again, and now, at the first alignment screen, i.e. "Tap on the screen...", I have no screen response at all.
I called T-mo, and they are being great about sending a replacement ASAP (and getting me a loaner in the meantime).
BUT, I am running Faria+ AKU3.3 V2... so I clearly have to flash back to T-mo 2.26. I can;t figure out how to do it though, as no matter what I do I am stuck at the first alignment screen!!
HELP!! EMERGENCY!!!
(I have three or four days to get this done, so it's not THAT urgent)

Do a search for Broken Screen. Someone (either in Wizard Upgrading or in the Wizard forum) just had a similar issue with a cracked screen. They downloaded something that allowed them to get around the welcome page.

Actually, if you are just trying to flash a new ROM, don't even mess with it. Go straight to the Boot Loader screen (see the first post of this thread). No tapping necessary until the new rom is on (and that will be the Tmobile then so you would be good.

Thanks for the quick reply. Charging up to green now, and then will try to enter bootloader and flash T-mo 2.26. Will report back.

Worked great. Back to T-mo she goes!!!

BootLoader Mode
Excellent thread but you left out one thing.....exactly how to place your device in bootloader mode.
To clear up any misunderstanding because this is very important....this is how you do it:
Perform a soft reset, when the screen goes blank hold the camera button until a multi colored screen comes up .... That's it !!!!!!
When the unit is connected, USB is displayed at the bottom left.

Trinity running 6.1 Elegance- totally bricked - please help me!!

Hi all,
I have been visiting these forums for 2 years now and have downloaded some great tools and ROMs to enhance my Trinity, however something all of a sudden has gone very wrong!
I upgraded to WM6.1 Elegance edition about 3/4 months ago, CID unlocked the phone about a month ago and everything has been working like a dream.
However just today, I attempted to turn the volume down on my phone during a meeting (I always forget to normally!) and there was no display. After few battery resets, again no display. It starts up, loads the the Elegance splash screens and then hangs on the screen before when the OS should appear.
My decision was to flash the ROM again. I cant flash using Activesync as it wont pick up on the hung screen, so I started the bootloader and got as far as 1% of the flash and it will restart. So I tried the SD Card method when resulted in a "loading" screen appearing for a few seconds and then it goes back to the standard bootloader and displayed a 00068002 error.
I am out of ideas, I hear mtty.exe is a good program for this kind of thing, but what I want to know is if this is fixable or if I should give up!
I have been working on this since 2pm today none stop!
Can any of you guys give me any suggestions please?!?!?
Kind regards,
Jonathan

Should be a cinch
Did you SPL the Phone before flashing roms?
If you put the phone into the bootloader mode The RGB screen and kill of activesync you should be able to run one of the flash update programs.
If I have flashing problems its usually Active sync so I kill it then run the flash program.
I've got a sneaky suspision your battery might be causing the problem.

Hi there, thanks for the reply. As I was new to upgrading I havent used SPL on the phone before flashing the ROMS. I did use an unlock tool recently as i wanted to try a different network SIM to see if it worked when I was in South America, so the phone is unlocked to all networks. Are you saying if I SPL now it should sort the problem out? If so how do I do this withour ActiveSync working - can you use SD?
Another thing I failed to mention was that when I start an upgrade and it follows all the steps, it doesnt say the current ROM on the screen where you press update ROM. It just gives the name of the new ROM and the current one is left blank.
I have disabled Active Sync before attempting the update. It seems to go through fine and then the phone restarts wafter 1% of the update.
What makes you think it is the battery? I am happy to spend under 20 pound on ebay if you think it will fix the issue!

try unbrick.bat.......my trinity was also stuck.......unbrick.bat save my day....

The same happened to me several time....I could not find a solution other than this one:
1. Flash the official HTC ROM.
2. Flash the required ROM then.
it works for my TrinTy.

Restore from Bootloader?

I tried to upgrade my 8125 using Shelltool earlier this week. I used the tool successfully before and so I was assuming that things would just go well.
Unfortunately, I ended up being stuck on the bootscreen. I can also still go into Bootloader mode and so I figured all I need to do is to download the Wizard Love ROM, go into Bootloader mode and apply the ROM to restore an older version. Well, for some reason the RUU utility keeps telling me about a communication issue even though I already disabled USB in Active Sync and I also killed the program using Task Manager...
What am I missing here? I am hoping that someone can enlighten me...
Thanks,
Jens

For some reason I was finally able to flash my 8125 with the Wizard Love ROM this morning. Flash completed and I was back to an old working ROM.
Unfortunately, when I flashed it with the latest CR86 it flashed fine, but then I am stuck on the Bootloader screen. Already tried it twice and just running it a third time, but I am puzzled...
Any help?
Thanks,
Jens

jstraten said:
For some reason I was finally able to flash my 8125 with the Wizard Love ROM this morning. Flash completed and I was back to an old working ROM.
Unfortunately, when I flashed it with the latest CR86 it flashed fine, but then I am stuck on the Bootloader screen. Already tried it twice and just running it a third time, but I am puzzled...
Any help?
Thanks,
Jens
Click to expand...
Click to collapse
its on its last flashes my friend(or maybe just tire of custom roms)
but just before mine died, it would do that, until i was stuck on the bootloader and the screen would just die, i would have to leave it off then turn on but the same, after that i just left it alone
i could not flash anything on it and i could not see it suffer anymore
i still have it but dont have time to bring it back to life, at least it blinks at me

That's what I was worried about...
Strange thing is I probably only flashed it about 10 times... Very frustrating!
Thanks for your reply!

Hmmm, I just tried the old Wizard Love ROM again and it worked right away.
What am I missing here? I am trying to get to the new CR85 6.5 ROM, but I always end up being stuck on the bootscreen loader. I mean it shows me the HTC screen, but then it goes straight to the bootscreen...
Any suggestions?

I am back in business!
It turned out that flashing back to an older ROM disabled my HardSPL. I guess a case of user error on my end...
Anyhow, I also experienced the fading display mentioned above and I think that's just a sign of a weakening battery. It seems that the phone doesn't charge fast enough over USB in Bootloader mode.
So, if you run into the same problems like me:
- Charge your phone using the charger when you are stuck in Bootloader mode for extended amount of times!!!
- Flash an old provider ROM or Wizard Love ROM
- Re-apply HardSPL if needed
- Upgrade to a newer ROM
Cheers,
Jens

Stuck in bootloader loading screen.

Im about to flash my ROM from original 1.56 to Duttys new, but when i enter bootloader the white loadingscreen gets stuck in my face. Nothing happens and i need to remove the battery to shut down device. Anyone? Freakin frustratin´.

Before I flashed my first rom, I read wiki.xda-developers.com to make sure I understood what I was doing, and used the search button, instead of risking turning my phone into a paper weight.
Since then, Crackwhore has written a very helpful post at the top of this forum about how to use HSPL and USPL to allow you to flash roms.

yeah i know all that. not my first time flashing a phone but the first time it got stuck loading the bootloader. and specially when i´ve only used the HTC update.

darfor said:
Im about to flash my ROM from original 1.56 to Duttys new, but when i enter bootloader the white loadingscreen gets stuck in my face. Nothing happens and i need to remove the battery to shut down device. Anyone? Freakin frustratin´.
Click to expand...
Click to collapse
you mean you couldn't get to boot loader page?

So you already have HSPL 1.56 installed (or have SPL1.54 and used USPL)?
If you have HSPL you could try renaming the .nbh file to blacimg.nbh and copying it to the SD card and entering bootloader

Same problem here. Stuck in bootloader mode. Loading progress indicator never moves beyond 0%. Have always used the card method (blacimg.nbh), but this time it doesn't work and nothing flashes. No matter what I do the system goes to tricolour bootloader screen and says ROM update error. Have tried 3 microSD cards, all in working order, so this isn't the problem. The full problem description is here. Help!

AFW said:
Same problem here. Stuck in bootloader mode. Loading progress indicator never moves beyond 0%. Have always used the card method (blacimg.nbh), but this time it doesn't work and nothing flashes. No matter what I do the system goes to tricolour bootloader screen and says ROM update error. Have tried 3 microSD cards, all in working order, so this isn't the problem. The full problem description is here. Help!
Click to expand...
Click to collapse
try dnloading the rom again amd try.
the file might be corrupt

Have tried that many times. File is not corrupt. I'm getting really worried this is now a brick...

OK, if you can get phone into bootloader, it is not bricked
What does your SPL say in bootloader? Do you get any errors when trying to flash rom? Are you using USPL or HSPL? If USPL, you have to use it before every flash to new rom or radio. If HSPL, are you using correct version?

Was on Dutty's 3.9 XT, but decided to revert to standard WWE 1.56. I flashed the Std 1.56 ROM successfuly, and then tried to restore the ship SPL 1.54 using the card flash method. This failed, and now I'm stuck on the bootlader screen forever.
No matter what I do the THD always goes to bootloader (red-green-blue-white screen), with following text:
BLAC100 32M
SPL-1.54.0000
MicroP-BlackStone (LED) v6
Upgrade ROM code error
Please try again
USB
Click to expand...
Click to collapse
When I start blac_uspl.exe (USPL 2.5), a window flashes (Vista64) for a split second and then nothing else happens. The Vista64 system's USBs work with THD and have been used to sync over past few months.
When I try to run HSPLWrapper_Blackstone_156OliNex.exe and step through the preliminary screens, the Verify that you want to update ROM version screen has the From Image Version as blank and the To Image Version as 1.56.Olinex. When I click to commit the flash the THD screen switches to white with a progress indicator that always stays at 0% until it times out. Recovery does nothing and the same thing always happens. Using Vista64. .Net installed and fine. I can't use the card method (BLACIMG.NBH) - the system also stays on "Loading .... 0%" and nothing else happens.
When I try to flash anything (have tried HSPL1.56, Dutty's 3.9 ROM, stock 1.54 spl) using the card method, the system says "Loading . . ." and hangs there forever without a progress indicator showing.

Your SPL says 1.54.0000. When you try and run USPL.exe have you remembered to disable your antivirus?
Have you tried usb method instead of card for flashing rom?
I know you have said that youi have used usb for syncing, but when in bootloader does it change from 'serial' to 'usb' when you connect HD to PC?

Fallen Spartan - I want to thank you for taking the time to help me resolve this problem. Very much appreciated!
1. Yes, anti-virus disabled and indeed removed from the PC.
2. Yes, have tried the USB method at least 20 times.
3. Yes, the bootloader changes from Serial to USB. It then goes to the progress indicator screen and hangs on 0%. The progress indicator on the RUU on PC also stays at 0% and eventually times out. I've gone through the Recovery routine at least 20 times, with no luck.
When I try to run SSPL-Manual-TouchHD.exe it says "not a valid Win32 application".

I'm a bit perplexed by this.
You have obviously successfully flashed Duttys V3.9 so drivers are fine, you know how to use USPL, both flashing methods (SD card and usb/pc), disabled anti-virus, phone in bootloader.
Have you tried to reflash 1.56 rom or possibly performing a hard reset before trying to use USPL or HSPL. I doubt this would make a difference though.
Have you tried cRaCKwHoRe's USPL GUI v 2.5 Application?
You don't get any code errors?? I'm struggling to find a solution here.

Yes, this is most vexing. I've flashed innumerable times before and never had an issue. I suspect the SPL is fine, but somehow the actual WM ROM image is corrupted. Will now try to load Std 1.56 ROM image again...

Success! The 3rd attempt at reflashing stock 1.56 ROM worked. I don't know why the system bombed out before. Perhaps one of those inexplicable brain farts..
Anyway, all seems to be fine now. Fallen Spartan, you have my endless gratitude for at least responding. Let me know if you need accommodation at next year's FIFA World Cup in South Africa (though I'm a rugby fan).

AFW said:
Success! The 3rd attempt at reflashing stock 1.56 ROM worked. I don't know why the system bombed out before. Perhaps one of those inexplicable brain farts..
Anyway, all seems to be fine now. Fallen Spartan, you have my endless gratitude for at least responding. Let me know if you need accommodation at next year's FIFA World Cup in South Africa.
Click to expand...
Click to collapse
No accomodation required, just glad you got it sorted

Im still stuck. When i installed HSPLWrapper_Blackstone_156OliNex my screen changed colors but would go back to normal when i would turn the screen off and back on so i didnt see it as a problem. I installed the EnergyROM BLACKSTONE 20090608 Standard an tried to go back stock using RUU_BlackStone_HTC_WWE_1.14.405.0_Radio_52.49a.25.26_1.09.25.14_Ship but it gets to 1% then says this update utility cannot be used for you PDA phone. Please check your update utlity.
Then the phone boots up and at the black smart mobility screen in the bottom corner it says
R 1.09.25.14
G 52.49A.25.26U
D 1.14. 21010
the phone boots up with the funny colors again and goes to align screen but it keeps staying there even after i align it.
The bootloader screen says
BLAC100 32M
SPL-1.54.0000
MicroP-BlackStone (LED) v6
USB
Am i tryin to install the wrong stock ROM. I purchased the HD from phonesource-usa if that helps also

can anybody help me at all

Adamsville: perhaps you're stuck in bootloader mode because the WM ROM image flashed on your system has become corrupted or disabled, ie the only thing the system can boot into is the bootloader.
Try flashing a new compatible WM ROM image and see if that works.

AdamsvillE said:
Im still stuck. When i installed HSPLWrapper_Blackstone_156OliNex my screen changed colors but would go back to normal when i would turn the screen off and back on so i didnt see it as a problem. I installed the EnergyROM BLACKSTONE 20090608 Standard an tried to go back stock using RUU_BlackStone_HTC_WWE_1.14.405.0_Radio_52.49a.25.26_1.09.25.14_Ship but it gets to 1% then says this update utility cannot be used for you PDA phone. Please check your update utlity.
Then the phone boots up and at the black smart mobility screen in the bottom corner it says
R 1.09.25.14
G 52.49A.25.26U
D 1.14. 21010
the phone boots up with the funny colors again and goes to align screen but it keeps staying there even after i align it.
The bootloader screen says
BLAC100 32M
SPL-1.54.0000
MicroP-BlackStone (LED) v6
USB
Am i tryin to install the wrong stock ROM. I purchased the HD from phonesource-usa if that helps also
Click to expand...
Click to collapse
a hardreset followed by a 1.54 base rom will solve all ur probs.
or lower spl to 1.14 cos ur stock rom is a 1.14 base as suggested by th name..
cheers