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.
hi
I tried to upgrade my pda2k to 2005, but I get hang
then when I tried again it show this message
http://www.600kb.com/uploads/20aac64ad6.jpg
can i get help please
sarab
Strategies for dealing with radio ROM update 114 errors
I had this problem last week and recovered from it. At first it looked pretty bad, nothing seemed to work. I looked the Internet up and down and in most forums, including this one, people agreed that nothing could be done about error 114, the mainboard of the BA needed replacement, etc.
When I finally did fully recover from this situation, it was from a combination of measures that I took and as I don't really know which one actually did the trick, I'll try to describe all of them even though not all will probably apply to others. Another problem is that I probably won't be able to remember them all, but anyway, here goes:
1) I downloaded the latest full official ROM update from site of the carrier this phone was branded for, in this case T-Mobile. It included a radio ROM, albeit version 1.13.0, not 1.15.0 which is the one I had been trying to flash. I decided it would be best to go back to that official version first.
2) I had been trying to do the radio ROM upgrade from a Macintosh (OSX) under Virtual PC. I have since done several ROM installations (without the radio part) from the Mac/VPC which worked fine, but since people had observed that radio ROM updates seem to be more sensitive than fiddling with the normal ROM, I decided to fire up my "real" PC, which runs WIndows XP, SP2, with Active Sync 4.5.
3) As others had suggested, I made sure that I had my cradle connected directly to a USB port on the computer; before I had been trying to go trough a hub. I also made sure the cradle was connected to the power adapter.
4) I had unlocked my device before to work with a non-T-mobile SIM card, but since I wasn't sure wether or not SIM/Net lock problems might still interfere with radio upgrades, I took my SIM card out of the unit, as well as the SD card -- trying to eliminate as many potential sources of screw-up as possible.
5) I think I tried to set my BA into as much of a defined state as I could by hard-resetting it and THEN invoking boot loader mode. I don't remember whether or not this was possible as the device was not reacting much to anything at the time.
6) On the Windows PC, I opened Active Sync, then went to Connection Settings and explicitly disabled the USB connection. I then quit Active Sync and invoked the Windows task manager (Ctrl-Alt-Del) to check that no other processes were running. Trying to cut out interference as much as poosible ...
7) I then proceeded to flash the official ROM version, which went flawlessly including the Radio ROM, took less than fifteen minutes in all. To be honest, I don't remember which ROM upgrade utility (BaUpgradeUt/MaUpgradeUt_noID) I used ... sorry. I know I tried whatever was included with the T-Mobile download first.
After that, I verified that everything was working again, then immediately flashed Radio ROM 1.15.0 as I had originally intended. This time it went uneventfully.
Hope some of this helps, I know how frustrated you must be at this point.
Good luck!
thanks a lot
i'm going to follow your instruction today.
regards to all
[email protected] said:
thanks a lot i'm going to follow your instruction today.
Click to expand...
Click to collapse
So did you have any luck?
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.
Hi, first of all let me begin by saying that I have spent a long time reading around through the guides and forums about flashing rom/radio to my Rohdium but still face problems. I have successfully flash my old TyTN II and Orange E650 but am at a loss as to why Im struggling this time round!
I flashed the Hard SPL which went 'fairly' smoothly, got there in the end after having problems on WIndows 7 64bit and then succeeded using Xp 32. However when trying to flash a new rom and/or radio I am greeted with an error, that being Error 284. I have tried like I say on Win7 64, Xp32 and when the error pops up my phone gets stuck on the process bar and forced to pull battery out. I then put it back in and it freezes on bootloader. The RUU software trys to recover but it is a loop of the same thing happening (attempts and then crashes). The only way to get out of this mess was strangely reflashing HardSPL which recovers it and allows me to boot to Windows. I have tried flashing a radio and/or rom whilst in sync within windows, I have tried flashing when manually forcing the phone to enter bootloader, I even paid the £10 to get the unlocker which would patch the special radio but that even returns the same error. I have the sim card out and storage card, battery charged over 50%. I even tried the Mtty program (sorry if mispelled, at work now and can't fully remember name!) when it was stuck at bootloader and using the "boot" command it boots as far as Touch Pro 2 logo but then doesn't progress, then i resorted to reflashing HardSPL which allowed me to boot properly. I just don't know what else to try!
Like I said Im sorry if this is obvious to someone but I have tried alot!
Many thanks in advance if someone could help!
* Update: Just tried flashing a radio on my works computer (XP 32) and it flashed no problem!? Wonder why my operating systems had an issue?
** SOLVED! ** - got home and randomly tried again on Win7 64 without using my USB extension cable and plugged into a different USB port directly and it worked! Faulty cable maybe, bad luck, who knows, it works!
Thanks.
Sound like maybe your RUU/update utility may have gotten corrupted. I would try to re-download the rom you want to flash over to your home pc again and try to re-flash.
If that doesn't work, you can always flash your rom through the storage card.
hmmm yea thats possible, will try when I get back in couple of hours thanks! Just seemed weird how nothing was working, different roms (cooked roms or shipped roms) and even the security/sim unlocker that I purchased......mystery!
USB cable tends to go bad easily! That might be the reasion why!
I have succesfully upgraded my Tmobile MDAIII to Win 6.1 via the mentioned above method. And now I want the start-button-in-the-bottom
So I downloaded the image file, put MDA into a bootloader, plugged it into craddle, started maupgradeut_noid and... the second screen didn't show any data about the device. (in FAQ "something went wrong, start over again" is advised). Several attempts were of no use. The fresh XP SP3 also didn't help. What is wrong??
By the way, the official upgrading software (that one that shows Invalid country ID later) does show the device info screen correctly.
you should re-download the rom and the RUU and try again. in general, the way you're doing it, is right. remember to take out the sim and sd card though or you might mess up your radio.
i would say, i know everything, there is to know, when it comes to flashing the BA, and still last weekend i spend hours on up- and downgrading, because sometimes, it just wouldn't show the info, mostly, when a download was corrupt, although no error message was given.
Chef_Tony
You were right, it was the radio-file. When I deleted it everything went as it should. But the radio still needs an update I think (I've 13th version) since the bugs are freaking me out sometimes.
Thank you!