Database Develop

New To the recent phone pocket pc's

hi..i have a tmobile mda with the rom 2.26.10.x that i didnt know couldnt be cid unlocked...i found out after i upgraded which sux balls.lolz..i have a few questions...
1.What is the best rom i can upgrade or downgrade without bricking my mda...
2.why is the mda wifi reception bad most of the time resulting on always 1 bar for wifis around me...i even tried the wireless b mod.
3.I know your phone isnt dead if bootloader works but do ihave to use an sd with the rom saved on it in order to reflash my mda again...or can i just use an app that installs it via usb while bootloader is on?? <this one im definitely confused on... Please anyone help asap, thanks so much and much blessing

Here's an answer to part of your problem:
As long as you have a USB connection, you can re-flash your phone (provided it's in either the bootloader or connected to your system via active sync 4.1 (I don't know about the beta 4.5 of active sync - which changed the way your PC connects to your phone as I understand it)). You may have to try several different ROMs to re-flash, but generally, I have found that doing the following almost always guarantee's a re-flash:
1) remove the SIM card
2) after every attempt, disconnect the phone from your USB port and then reconnect it
3) between attempts, remove the battery while you are setting up your system (you can't flash a phone w/ a dead battery, so unless you have a way to charge the battery other than the phone, you need to protect the amount of charge you have like it's your lifeline!)
4) I have had more success re-flashing a phone that is in bootloader mode by using the original ROM .exe file instead of trying to extract the files from it and THEN run the update utility.
5) If your phone came w/ a 2.x ROM, I wouldn't try to downgrade it to a 1.x ROM as this has never worked for me. Try flashing it w/ a 2.x or higher ROM only.
Hope this helps (oh, and rumor has it you should use the USB ports on the back of your PC, not the ones on the side or front!)
Black-Wolf

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.

My radio is damaged

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?

unable to revert to O2 rom

Hi Guys,
i consider myself relatively experienced at flashing HTC devices having been using and upgrading for a few years but i've run into an issue on my CID locked G4. i upgraded to WM6 without issue and i tried to revert back to my O2 rom, the flash failed and i'm now stuck at the splash screen. I've tried to flash the original ROM from boot loader but i get a 101 error unable to connect(can see it in device manager). as i'm using vista i did a search and found some instructions and driver files but i get the same result. the only thing i can think of now is to CID unlock but i'm not sure it will help (unless it allows me to do the SD card restore). any ideas guys?
IPL:2.21.001
SPL:2.21.001
GSM:02.25.11
OS:10.1.0.811

OK., what you need to do is use a PC with XP, because i have read that vista PC's can get you into a lot of trouble. When you are at an XP PC, follow the instructions in my previous post
( http://forum.xda-developers.com/showthread.php?t=313354 ).
When you flashed the original ROM, and you succeeded in doing so, think real hard if you still want to upgrade to a new ROM.
If you still want to do that, stick to a PC with XP installed (no vista!).
If you did reflash a good ROM into your HTC you'll be one step closer to upgrading your ROM.
Read this post thourougly :
http://forum.xda-developers.com/showthread.php?t=298613
as this will help you in case you didn't CID unlock your device.
(thanks vippie; this is the clearest walktrough i could find!)
If you are really sure you CID unlocked your device, you can flash your device to any ROM you think is useful to you.
If your device is really CID unlocked, you should be able to flash any ROM that is posted on this forum.
I know that it is that easy, because i have tried every WM6 ROM that is posted on this forum
good luck, and i hope in the end you will have the ROM that you want....

thanks. my device IS CID LOCKED and i've tried to flash it from 2 XP machines so it is looking like its a brick thanks anyway.
for sale wizard with pretty 3 colour screen - sold as seen!!!

One thing you can try is use another USB to mini USB cable, i have had one cable that didn't connect really well.
Sometimes it worked but if i moved my phone the connection went down.
I just thought of that because it was a while ago that this happened - I threw away the faulty cable and had no problems after that.

tried 3 different cables too

knownuser said:
tried 3 different cables too
Click to expand...
Click to collapse
How much do you want for it? I need a new screen and body shell!

jabreu203 said:
How much do you want for it? I need a new screen and body shell!
Click to expand...
Click to collapse
was actually kidding i'd like to fix it but i'm open to offers PM me.

ok .....HELP
i've paid for the CID unlock which went well i then tried to flash the O2 default rom failed error 101 (connection) i then tried wizard love failed error (300) in italian.
so stage 2 was to use the sd card recovery i ran the utility and then followed the instructions r2sd all etc..all seemed fine i restored the image to the wizard and rebooted it still won't go past the splash screen i've tried re-flashing and hard reset still no go....please guys any help???

If you have a memory card take it out. Right click on ActiveSync and go to connection settings. Uncheck allow usb connections then try to flash. With windows XP...

tried to flash on a win2K machine (4 pc's thats the only one thats not vista) still get error 101 on the original O2 rom and 300 on the wizard love rom.
still no joy anyone have any ideas???
http://www.t-mobile.hr/mdasw/RUU_Pro...R_WWE_Ship.zip fixed i'm on a tmobile rom i'll try downgrading again.

What on earth am I doing wrong when flashing?? *SOLVED!*

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!