Database Develop

BlueAngel Total Failure - Request for advice.

Hello,
I believe I have a real 'tough' scenario:
My BA (WM2003) was running normally till yesterday where it simply 'froze'. I tried restarting it, (soft and hard) and it kept stalling on the (IMate) splash screen and didn't proceed to WM. I left it to battery drain completely.
I came to work this morning, and literally tried everything:
Standard Upgrade using the Imate original exe (PDA2k_WWE_14000_176_11200). doesn't recognize the phone anymore.
Tried the MaUpgradeUT_noID with the nbf files (radio, ms and nk). In all cases the upgrade starts and gets interrupted in the middle with a 'weird' error and the BA display fades as the signal led goes RED (constant, no blink). I have to take the battery out, back in.
Tried the mtty set 14 0 / task 28 sequence with no result. (The info commands return a garbled sequence which makes me assume that my bootloader got corrupted).
Any advice would be appreciated.
Thanks a lot.
W.

wzaatar
Read in another post that you got no reply on this one.
Well it seems like nobody can come up with anything that would make more sense than what you have done.
My wording is when everyting else falis go back to the original rom and start from fresh.
If you can't flash an original rom in the ship.exe or the extract form you need to send it in.
Does your device react to hard reset ?? at least you should get a boot screen.

Have you tried Bootloader mode?
I know that this is a really stupid idea.. but have you tried putting it in bootloader mode, and then trying to upgrade? Or maybe throw a WM5 rom on there, and downgrade again! Worth a try until you send it in!

Thanks for the replies guys, I really appreciate the help.
I figured out that I had two distinctive problems:
1. The constant red led light, after a lot of research, it turned out that the battery was defective. Changing it solved the problem.
2. Now, I am able to flash the ROM (Tried it a couple times so far) with the orginal or another one. It flashes correctly, but only if I use the NoID flash program, else it will return a MODEL ID error. And when I reboot it, it stays stuch on the 'Imate' or the bootscreen and I don't get the WM to load (As if it freezes)...
3. I don't think I can upgrade to WM5 as I need to shrink the EXTROM size? Can this be done through some 'task' or other command in mtty for example?
Thanks for your suggestions.
Cheers,
Wadih.

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.

Bootloader question/trouble

Hey there everyone, I am pretty new to this forum so I must apologize for throwing you all into the deep end. I recently purchased an o2 XDA mini S second hand from a guy on boards.ie here in Ireland. I got the phone and really liked it because it allowed me to get rid of my Dell Axim X3i and mp3 player and keep it all in one device.
After a little bit of more research I discovered that I could remove some of the bloatware from the o2 xda mini S by just hard resetting and choosing the basic option which I than did. Still not satisfied with the overall performance of the XDA I decided to try a rom upgrade. Not wanting to do a totall overhaul I decided to just do a radio upgrade first.
My device is sim unlocked, it was like that when I bought it. I used the latest wizard service tool to CID unlock the device before I even flashed the phone. I also used the wizard service tool to change the nk.nbf file within the o2 mini S radio update into 96000000-GSM.nb. I then used this file to write to the GSM radio code (Bdk 1) according to the wizard service tool in the hopes that it would upgrade my radio version.
Well when I restarted, nothing of the sort happened, on the boot screen I noticed I was now missing my GSM version and when the phone finally got into windows mobile, it did not pick up any signal even though beforehand it could. The phone also became super slow to the point where it was unusable.
I have gone into bootloader mode subsequently after reading on this forum and tried to reflash with a number of updates with active sync disabled and nothing else running with the phone connected via usb to the pc. None of the updates would even pick up the phone or allow me to flash it.
My phone is pretty much screwed, I have a spare so it is not that big of an issue but I would like to make this usable again if at all possible. So my question is how do I flash a rom while the phone is in bootloader mode?
P.S I forgot to include the Current boot screen details:
IPL - 1.05
SPL - 1.05
OS - 1.5.4.2

Hi,
You can use the Wizard Love Rom from here http://rapidshare.com/files/17792050/Wizard_Love_2.26.10.2_WWE_Novii_CF2.rar

Hey there, thanks for the advice, I did download that ROM but like I said before, none of the roms manage to flash my XDA because they all cannot seem to connect to it. Activesync does not even pick it up in windows mode, and even when I have it connected in bootloader mode via usb and I double click on the love rom, it goes through the motions but never managed to "verify the information with the pda"

Try a stock Tmobile ROM but not from bootloader. Also, I would check the activesync app on the device. Make sure it's set to use USB as the default connection method.
A few other steps to try...
Uninstall ActiveSync and install an older version. If still no go, try a newer version.
Try a different USB cable and/or USB port.
Try a different computer with XP, not Vista.
Try flashing it without the SIM card or any memory cards.
If all else fails, you can try the SD card flashing method. There are instructions in the Wiki on how to do it, but always a stock ROM.
Try this one... http://forum.xda-developers.com/showthread.php?t=311027
Updated IPL/SPL and radio 2.69

Hey Devis, I think I have come one step closer, I tried all the suggestions that you made. Except well now my phone will not even go into the operating system when I switch it on. It will boot and the version numbers show but then it just resets itself.
I tried a different usb cable and I am not using vista, tried a different pc and the same result. The one place I did have some marginal success was the sd card method.
Basically what happened is that It backed up the OS from my phone and then reloaded it, not exactly what I wanted since the OS and rom are both screwed on the phone so my question at this point is, is there anyway using the SD card method to load one of the stock roms onto my phone?
I searched around the net and found the opposite to the "r2sd all" function, would be the "s2d" function, would that allow me to flash the phone with a stock rom?
Thanks for your time, I am going to call it a night here in ireland and head to bed.

Ok, if the phone resets then you probbably have a dead/dying battery. Charge it for about an hour or so using the wall charger, not the USB cable. Try to restart it and see if you can get in the OS. I was looking in the SD card method thread and some guy was successful at restoring the image from the SD even though his OS had died. He then had a fully functional phone.
The other thing to do would be to get the image file from someone that has a living and breathing wizard, preferably one with a stock ROM. Since this method is the equivalent of making an image of a PC using Ghost, the restoration of such an image to your Wizard should work just fine.
Just make sure that the other Wizard is SIM and CID unlocked. Or just go buy a Wizard from the store, unlock SIM and CID, copy the image on the SD and flash your device. Or... since u've got a new Wizard in your hands, just take the freaking thing appart and swap the guts return the store bought wizard to the store saying that the thing just doesnt freaking work!
As for the AT commands... it is possible that s2d would workfor you, it doesn't work in my wizard. from what i have been reading it appears that the bootloader is password protected and that password is randomly generated. I haven't played long enough with it to figure out how to get the password.
It looks like you've got some "trial and error" processes ahead of you. There is a wealth of info on bootloader AT commands on Wiki, nothing for the Wizard though. But something may work... not sure.
I could try to get you a ROM dump from my Wizard but I already am on SPL/IPL 3.08 and running WM6. the SPL/IPL version alone wouldn't allow you to restore from my backup.

Hey Devis, thanks for your time, just woke up here, will work some more on the phone today and let you know what is going on

Hey Devis, I did not even get a chance to fiddle around with the phone today, from being able to switch on less than 24 hours ago, it does not even want to switch on now so I am going to officially declared it a brick and move on. Will see if anyone can fix it for me, spent way too much time already when I should be working on my dissertation, thanks alot anyway

Sorry to hear that...
I have bricked one phone myself in the past... my old Pana GD87 and I absolutely loved that phone. I know how you feel.
Good luck with your dissertation.

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

Is it too dangerous to flash this kaiser?

Currently I am running the Sleuth1.2 ROM in a sick Kaiser.The Kaiser works fine but has the two issues described below (with the work around I use).
I have two issues which are causing me concern if I try to flash
1. If the SIM door is closed when I soft rest the 'Smart Mobility' screen appears for about 3 seconds and then the device shuts down.If I open the SIM door press the power on or reset button then close the SIM door while the 'Smart Mobility' screen is still showing it boots perfectly to the today screen.
2. If while soft reseting and following the workaround above the SDcard in in the device the kaiser boots to the spash screen then powers off.If I remove the SDcard first it boots OK and then I can insert the SDcard and all is well,I have tried 3 different SDcards and they all react the same.
I can backup and restore using SPB backup and the SDCard by using these work arounds so I think I may be able to flash-but I need to assured by someone who knows more than I.
As I say it is sick,but not yet beyond use.
What I am thinking of doing is flashing a new SPL,Radio and ROM (probably
the TPC V11) but I am concerned one or other of theses faults will cause the flash to fail and give me a brick.
Can anyone advise me if I should be able to flash OK using my Windows7 PC and USB (or preferably even the SDcard)
M
many thanks in advance for the advice you offer.
Ashley

Moved as not ROM Development.
If you have any doubt in your device being able to stay alive during the hard-spl flash then don't do it.
Same with flashing a ROM as normally you can recover but then if you don't since you seem to already have problems it's a brick.
Might just be time to check out ebay for a cheap Kaiser

Thanks for the reply,it is much appreciated
What I was wanting to know is whether in the flashing process having to perform the work around with the SIM door will cause a problem.If it will I'll have to stick with Sleuth1.2,but it is not my prefered ROM-I've only flashed once and think it is time for a change.
I know the kaiser is well past its best but I cannot replace it yet.
Ashley

Had to re-read:
Only on a reboot you get this problem.
Ok i'd say it's fine as after you flash and it reboots if the battery is popped it will just start off from beginning again "not that i make a habit of it"
So flash hard-spl it reboots, will get stuck on splash do your tweak get back into OS, flash ROM resets gets stuck do your tweak and all should run fine.
All this is a "should" as i don't have the device in hand to know exactly how this will go.

Thanks,
Now pass me a shot of alcohol to help my courage! and I'll roll the dice.
Best Wishes
Ashley (Canvey Island,Essex,UK)