Database Develop

Recovering from a bad flash...

I was running xelencin's latest custom rom. I have used his previous versions and all was good.
This one hung at 98%. I was just letting it do its thing when out of nowhere, BSOD. So now my phone is just sitting at 98%. I thought there was a forum post here about recovering but I'm not able to find it.
Thanks.

Update: After a soft reset, I am back to the multicolor screen. When I plug it in, it says USB in the bottom left hand corner. Device manager shows a PocketPC USB Sync device as well.
When I perform a hard reset (Comm Button + Voice Dial held, then press soft reset with stylus), I am taken right back to the same multicolor screen.

You're at the bootloader.
This is a Good Thing(tm).
At this point, you should be able to rerun any (assuming you are CID unlocked) any RUU ROM upgrade. Let it do its thing and you'll be good to go.

gamescan said:
You're at the bootloader.
This is a Good Thing(tm).
At this point, you should be able to rerun any (assuming you are CID unlocked) any RUU ROM upgrade. Let it do its thing and you'll be good to go.
Click to expand...
Click to collapse
For those that get stuck here in the future:
I had to extract the installer so as I could get past the CID unlock. I then ran "ROMUpdateUtility_Wizard_NoID.exe" and all went well!

rosewood said:
For those that get stuck here in the future:
I had to extract the installer so as I could get past the CID unlock. I then ran "ROMUpdateUtility_Wizard_NoID.exe" and all went well!
Click to expand...
Click to collapse
Yep, I went thru the exact same thing yesterday when trying to upgrade to 2.24. My PC decided to shutdown (not restart, a complete instant shutdown!) at 8% flashing. I decided to grab the "Mr Clean AKU2.3 ROM" which already had the ROM flash program available separately and then just put in the .nbf file I wanted and it was good to go

if your not cid unlocked, then what? xtract what? to wherehow can i transfer any thing, it seems though the device screen says usb, the avtivesync doesnt detects my phone. n?m, ive got it

What happen when your not CID unlocked? I had removed my hardspl before I tried to again flash a rom. I am stucked with the bootloader now...
Pls help

xpxj said:
What happen when your not CID unlocked? I had removed my hardspl before I tried to again flash a rom. I am stucked with the bootloader now...
Pls help
Click to expand...
Click to collapse
Only Official stock rom or the wizard_love rom will get flashed,no other wm6 rom is possible.

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.

Stuck in Bootloader Mode /-> ERROR [264, 274] : CONNECTION

HELP ME OUT GUYS, IM TRYING TO FLASH THE WM6 ROM TO A CINGULAR 8125: IPL 2.25, SPL 2.25 AND SEEM TO BE STUCK IN BOOTLOADER MODE. I FIRST GOT AN UPDATE ERROR AT 99%, PERFORMED RECOVERY - AND GOT THE SAME ERROR AGAIN. NOW THE RUU WON'T EVEN START AND I GET ERROR 264 : CONNECTION ERROR. ACTIVE SYNC NO LONGER IS GREEN, ETC. I DOWNLOADED THE XDA MOBILE 6r2a.zip FROM THIS SITE. NOT SURE WHAT I DID WRONG. I THINK I NEED TO GET BACK TO AN ORIGINAL ROM AND START ALL OVER BUT NOT SURE WHERE I CAN FIND ONE. THANKS.

ditto
ensophalic said:
HELP ME OUT GUYS, IM TRYING TO FLASH THE WM6 ROM TO A CINGULAR 8125: IPL 2.25, SPL 2.25 AND SEEM TO BE STUCK IN BOOTLOADER MODE. I FIRST GOT AN UPDATE ERROR AT 99%, PERFORMED RECOVERY - AND GOT THE SAME ERROR AGAIN. NOW THE RUU WON'T EVEN START AND I GET ERROR 264 : CONNECTION ERROR. ACTIVE SYNC NO LONGER IS GREEN, ETC. I DOWNLOADED THE XDA MOBILE 6r2a.zip FROM THIS SITE. NOT SURE WHAT I DID WRONG. I THINK I NEED TO GET BACK TO AN ORIGINAL ROM AND START ALL OVER BUT NOT SURE WHERE I CAN FIND ONE. THANKS.
Click to expand...
Click to collapse
That was the same rom that toasted my Qtek 9100 and now I'm stuck at the 99% mark before I get update:[302] error. Sorry didn't mean to steal your thread m8 but when I aksed the forum if they could help me out I got zero response ...so mines a brick right now.
BTW: I've tried the Wizard Love ROM but that was spanish I think and comes up with "INVALIDO" or something similar. I've fully charged the battery, removed the SD card and disabled "allow USB connections" in activesync, along with killing off wcescomm.exe ...but still no joy. Hope you get sorted with yours soon.

Original ROM's are easy to find, just go to either your phone service providers website and it should be on there, or go to HTC's website and they'll either have it or have links to where you can get it. Before you tried flashing XM6r2a, did you CID unlock your phone? That may be your problem.
ADD+, your phones not a brick yet if you can get in to the bootloader, which since you said that you tried to flash the wizard love ROM I'm guessing you can still do. You should also re-flash the original ROM that was on there and see if you can at least get that one to load back on there.
Also, for Original ROM links try this link - http://wiki.xda-developers.com/index.php?pagename=Wizard_Upgrades

xeno1 said:
Original ROM's are easy to find, just go to either your phone service providers website and it should be on there, or go to HTC's website and they'll either have it or have links to where you can get it. Before you tried flashing XM6r2a, did you CID unlock your phone? That may be your problem.
ADD+, your phones not a brick yet if you can get in to the bootloader, which since you said that you tried to flash the wizard love ROM I'm guessing you can still do. You should also re-flash the original ROM that was on there and see if you can at least get that one to load back on there.
Also, for Original ROM links try this link - http://wiki.xda-developers.com/index.php?pagename=Wizard_Upgrades
Click to expand...
Click to collapse
Got mine fixed by using the Xda_MiniS_LaunchROM_v154102.exe from the link in the definitive guide sticky. So as they say RTFM!!

Wizard (MDA) will not get past the boot screen

Hi, i have been trying to upgrade my mda to the wm6 <http://forum.xda-developers.com/showthread.php?t=324632> and now my mda will not get passed the boot screen. i have tried reverting back to the tmobile 2.26 version to no avail. i have also tried using mtty to set 14 0 with no response from the device and task 23, etc does nothing either.
Anyone ever have this happen when these resolutions will not work?
Please help!!!

did you put your phone into bootloader by pressing and holding the camera then pressing the reset button?

Yes, i can get into the bootloader and load images, its just that they will not get past the boot screen on a normal boot.

dgrandestaff said:
Yes, i can get into the bootloader and load images, its just that they will not get past the boot screen on a normal boot.
Click to expand...
Click to collapse
I have seen this happen in 2 different sitations. One is that you installed software while the HTC Home Plugin is enabled on your today screen, and the other is installing 3rd party software not compatible with WM6.
My reccomendation is to hard reset the device and i you are still having the same problem afterwards, put the device in bootloader mode and flash your carriers latest rom. If that will not work then try Wizard love rom.
Also another option is to flash the button rom and then try the t-mobile 2.26 rom.

dharvey4651 said:
I have seen this happen in 2 different sitations. One is that you installed software while the HTC Home Plugin is enabled on your today screen, and the other is installing 3rd party software not compatible with WM6.
My reccomendation is to hard reset the device and i you are still having the same problem afterwards, put the device in bootloader mode and flash your carriers latest rom. If that will not work then try Wizard love rom.
Also another option is to flash the button rom and then try the t-mobile 2.26 rom.
Click to expand...
Click to collapse
He can't get past the boot loader so it's not a matter of applications errors
@ dgrandestaff
Is your phone CID unlocked? If so then try the SD card method : http://forum.xda-developers.com/showthread.php?t=276963

i have tried hard resetting hte device and reflashing with the button rom and tmobile's latest rom (2.26). They install but when i try to reboot, it just hangs on the initial boot screen.
I did run the cid unlock wizard as suggested when i started this process but i suspect that maybe that did not work correctly.
i'll try the sd method shortly and see what i get.
Thanks...

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