to whom that can help me.
My XDA just shows WALLABY Boot Loader v5.17, GSM OK.
And my active sync is not working.
I need to know what are the steps require to get my XDA working again.
Any help willbe greatly appreciated.
zeroone said:
to whom that can help me.
My XDA just shows WALLABY Boot Loader v5.17, GSM OK.
And my active sync is not working.
Click to expand...
Click to collapse
too few details
to understand what could be the cause.
Try hard reseting your PCC (you will LOOSE all non original application and data)
or uninstall and reinstall ActiveSync and see
and see what it says !
Nb : The source of the problem could be in your PC HW as well
Tried reinstalling actice sync, and hard resetting it but xda still not communicating.
The last version I flash is Rom version 4.00.01 ENG,Radio version 4.2.1.
I am trying to change wallaby 5.17 to 5.15. i have no success in doing so, even with the sd card.
I downloaded XDAtool but do not know what is required to get my xda to work.
Can someone help.
To my perception, active sync is not involved in your problem.
It is really down to the OS interfacing with your device.
What was the latest version of PCC OS that was working fine?
Which OS did you then try to upgrade with ?
What steps did you perform.
When and which error message did you get ?
Related
i want update radio update but its locked at %10 then i restarted
and i want to enter bootloader but nothing come to screen. no power no bootloader!
how can i solve this problem...
albetratz said:
i want update radio update but its locked at %10 then i restarted
and i want to enter bootloader but nothing come to screen. no power no bootloader!
how can i solve this problem...
Click to expand...
Click to collapse
You should have read the instructions before trying the upgrade. ROM upgrade goes first, then the radio stack. I don't know if there's something you can do yourself to fix your device, or if you need to have it reflashed by your supplier. Anyone else?
bamse said:
albetratz said:
i want update radio update but its locked at %10 then i restarted
and i want to enter bootloader but nothing come to screen. no power no bootloader!
how can i solve this problem...
Click to expand...
Click to collapse
You should have read the instructions before trying the upgrade. ROM upgrade goes first, then the radio stack. I don't know if there's something you can do yourself to fix your device, or if you need to have it reflashed by your supplier. Anyone else?
Click to expand...
Click to collapse
Hi,
Seems like you are another of the many victims who got problems
after trying to upgrading new ROM & Raidio stack. Hope you still
got that warrant and get it replaced with a new one. Otherwise
you might have to try what some crazy guys do here trying to fix
it by doing all sort of bootloader etc.. Hope those who are trying
to get the upgrade ROM and Radio stack be very careful and make
sure your device are from the same supplier or distributor where
you got the new upgrade. Otherwise it will be screwed. Dont learn
your lesson the hard way.
same problem here.
i've got the O2 NL XDA
downloaded the 3.15 and radio updates from O2 NL website
installed updates as per instructions
1st update went without a hitch
2nd update totally screwed my xda.
now it takes a long time to start up, and when it does it just displays a white screen with a blue taskbar.
tried the bootloader way of flashing the rom, but still no luck
luckily I can send it back in to O2 to have it fixed.
I may try to do it by backup up another XDA, and reflashing mine.
Same prob with me..
I've got exactly the same problem. I downloaded the Rom update 3.15 and the new radio update. First I installed teh Rom update and after a hard reset I "installed" the radio update.
While updating the XDA hang and I waited for about ten minutes to see if the XDA was really hanging. I gave the XDA a hard reset but then the XDA didn't work anymore (white screen and blue bar on top).
I can still access the bootloader. I installed a Rom from a XDA which still works. Still no difference. When I tried to write the Radio rom to a sd-card I got that message that I have to connect one or another RS cable.
The XDA still doesn't work anymore. I have contacted O2 but they told me that they couldn't help me because they can't find my IMEI number in their system. I contacted the company where we ordered all the XDA's but I still don't have an answer.
Thank you O2 for being so nice with not helping me out with my one week old XDA without any scratch. I hope my XDA could be replaced as soon as possible since the XDA will not sold anymore when O2 changes to Telfort !
If you can make the ROM update work, you should be able to install the corresponding radio as well.
Try this:
1. Make sure you have the latest version of ActiveSync (=3.6)
2. Make sure the battery is fully loaded.
3. Extract the ROM update and Radio update to different folders.
3. Connect the cradle to AC-adapter and computer.
4. Put the device in the cradle and make sure it connects to ActiveSync.
5. Run the ROM installation application. Should take 5-6 minutes.
6. Run the radio installation. IMPORTANT: When you are prompted to remove power supply, pull the power plug from the cradle. If you do not disconnect power, the update will fail. I think this update took a little more time than the ROM update, and the device may seem "dead" for a while.
Good luck!
Hy Guys.
Are there any news about the problem flashing the XDA?
Tried last night to update my XDA to the last Qtek-Versions (ROM 3.16.52.....)
ROM Update works fine, but after the RSU Update the phone didn't work any more.
Have the same white screen with the blue taskbar and the little keyboardicaon down the right side.
Entering Bootloader mode there comes the Error Message "GSM Error"
Nice screen is the qtek "Booting Screen".
It shows
G <empty>
R <empty>
3.16.52
Hope there are any other hints to resolv this problem.
Have anyone got some experiences with sending it back to O2 with an "unoffical" Softwareversion?
Or is there any posibility to change the ROM Version to an old (original) O2-RomVErsion?
Thanks for any help....
Regards
Stefan
Hi Stefan,
I would suggest to try upgrade you device with any XDA ROM version by bootloader's CE to SD backup/restore and after try again to upgrade RUU by PC.
I know that upgrading/degrading by bootloader is the more safety way to do it.
Regards,
Riccardo
Riccardo said:
Hi Stefan,
I would suggest to try upgrade you device with any XDA ROM version by bootloader's CE to SD backup/restore and after try again to upgrade RUU by PC.
I know that upgrading/degrading by bootloader is the more safety way to do it.
Click to expand...
Click to collapse
SD-Card Writer just orderd
But I don´t know if it will work. Since the Bootloader says GSM Error, I think there will be no other posibility to restore it.
Let´s wait for some days, hope and we will see.....
Stefan
Hi everyone, I'm using an Asian O2 XDA and was running the 3.20.06 OS. I messed around with the ROM from Yorch's kitchen - the T-Mobile WM2003 upgrade, version 4.00.21.
My current problem is that I am unable to flash back to my previous version of ROM, or any other versions. My O2's running the version 6.22 bootloader and I have been unable to get it to boot from the SD card despite many attempts. Anyone out there that has managed to solve this problem ??
Regards
Maybe...
I dont know but maybe u need to use fixboot from XDAtools ?
it should help but i dont really know cause i didnt have such problem...
Boot loader 6.22 doesn't detect ROMs on SD cards. Try the XDAtools with any cooked ROM from the kitchen here and it will update your boot loader to 5.15 which doesn't have this restriction.
I've tried flashing the ROM using XDATools but the it kept giving me a message that the connection was reset by the device.
Is there something that I'm doing wrong ??
Try connecting your device to the PC and sync ... then from the XDAtools directory run this command:
pnewbootloader.exe bootloader_v5_15.nb0
oldwrym said:
I've tried flashing the ROM using XDATools but the it kept giving me a message that the connection was reset by the device.
Is there something that I'm doing wrong ??
Click to expand...
Click to collapse
XDATools won't work for flashing under T-mobile 4.0.21
cgigate said:
oldwrym said:
I've tried flashing the ROM using XDATools but the it kept giving me a message that the connection was reset by the device.
Is there something that I'm doing wrong ??
Click to expand...
Click to collapse
XDATools won't work for flashing under T-mobile 4.0.21
Click to expand...
Click to collapse
Is there any chance to get the XDA back to flashing?
I have bought a used XDA and it was working fine all unlocked until I preformed a hard reset to flush the memory out. After that, a hard or soft reset I get an error message "this program only works with Windows Mobile 2003 (4.20.1081), I have tried loading the rom I got from this forum and I get a connection error while installing the rom, in the dos box "connection terminated by remote host" I cannot seem to install any upgrade though active sync, although activesync seems to work fine otherwise.
O2 XDA - Tmobile OSD
Radio 4.21.00
Rom 4.01.16
Re: XDA Is there any other way to upgrade other than actives
The error Message comes from "Fix 'multiple resets make device slow' bug" that have been included in you ROM. You can just delet the file "wm03hotfix.exe" in \windows\startup
The T-mobile roms looks like they have an barrier for downgrading their ROMs via ActiveSync. You can also use SD-Card method for flashing the ROM.
HTH
Stefan
Re: XDA Is there any other way to upgrade other than actives
Stefan thanks, the error message is gone but the phone service icon has an exclamation mark next to it, I only have only have orange and vodafone sims and this XDA was on Tmobile, would there be a chance that the unlock has been lost? If so how do I unlock via SD card or serial comms cable.
Is it worth me changing back to the earlier roms as I have read that this could be dangerous.
thanks
Re: XDA Is there any other way to upgrade other than actives
I would say, the problem ist the frequence of your phone. On some devices the phones will be set internally to 900/1900. Enter the bootloader and set the frequency manually back to 900/1800 (if it is a PW10A device). Then it should work.
Attention: Entering the bootloader has the same effect as doing a hard reset. All data will be gone...
HTH
Stefan
Re: XDA Is there any other way to upgrade other than active
Stefan, great help. As I'm a newbie how do I get into the bootloader and reconfigure the frequencies - it is a PW10A1
Thanks
Re: XDA Is there any other way to upgrade other than active
digiq said:
Stefan, great help. As I'm a newbie how do I get into the bootloader and reconfigure the frequencies - it is a PW10A1
Thanks
Click to expand...
Click to collapse
http://wiki.xda-developers.com/wiki/ChangingBandsWithBootloader
Re: XDA Is there any other way to upgrade other than active
All working OK with no more errors,
Great thanks to Stefan.
:lol:
i tryed downgrading my xda to 1.5 so i will be able to use appz on it but now it just locks up on the O2 screen says the software version is 1.3 now but just locks up tryed about 100 different updates but nothing working is there a fix so i can get a custom rom on to it .................
now its just a brick is there a way to fix this problem
thanks
blueflash said:
i tryed downgrading my xda to 1.5 so i will be able to use appz on it but now it just locks up on the O2 screen says the software version is 1.3 now but just locks up tryed about 100 different updates but nothing working is there a fix so i can get a custom rom on to it .................
now its just a brick is there a way to fix this problem
thanks
Click to expand...
Click to collapse
you have to provide more (and more accurate) information (IPL and SPL 1.3 isn't correct. Is it 1.03? You really need to be accurate about what you post or someone could tell you to do something that will truely brick your phone). Your best bet at this point is to get the most current rom from your provider and then flash that. From the way you are describing it, you'll probably have to put it in bootloader mode to flash it.
Follow this guide and see if it helps:
http://forum.xda-developers.com/showthread.php?t=298613
nead a hand pls
ok here is the problem I tryied to flash a rom in my G4 cid locked and after it flashed correctly using the shell tool; I had to do a hard reset; when I did the hard reset my phone starts and freeze in the booting screen. with the o2 logo but doesn't seem to start; is there a solution providing that it can't recognize the active sync?
thanks
gonzalo
I was trying to upgrade my SX66 from the factory Windows2003 to WM6 with this HELMI_BA_WM6_R0_ installer. I started the install and it crapped out giving me an error saying that it could not communicate with my device and that I needed to plug my device back in and retry it. My SX66 is now stuck on the bootloader as I'm sure the ROM isn't complete, and the installer does nothing now. Can someone please help this noob out? I'd really like to have my phone back lol.
N1cholas said:
I was trying to upgrade my SX66 from the factory Windows2003 to WM6 with this HELMI_BA_WM6_R0_ installer. I started the install and it crapped out giving me an error saying that it could not communicate with my device and that I needed to plug my device back in and retry it. My SX66 is now stuck on the bootloader as I'm sure the ROM isn't complete, and the installer does nothing now. Can someone please help this noob out? I'd really like to have my phone back lol.
Click to expand...
Click to collapse
Did you unlock the device first?
In any case, just try to reflash your device back to WM2003 with a stock rom. It does seem to be a bad flash. Also, which OS are you using (XP or Vista)?
Follow this in order to perform the upgrade properly...
Good luck!
egzthunder1 said:
Did you unlock the device first?
In any case, just try to reflash your device back to WM2003 with a stock rom. It does seem to be a bad flash. Also, which OS are you using (XP or Vista)?
Follow this in order to perform the upgrade properly...
Good luck!
Click to expand...
Click to collapse
I'm running windows version 7. and no i didn't unlock the device. i just ran the installer application (i hadn't found a detailed install manual) i'm not entirely sure how i can re-flash now, because i can't get a usb connection made because it's stuck in the bootloader.
N1cholas said:
I'm running windows version 7. i'm not entirely sure i can re-flash now, because i can't get a usb connection made because it's stuck in the bootloader.
Click to expand...
Click to collapse
By bootloader, do you mean the three colored screen?
egzthunder1 said:
By bootloader, do you mean the three colored screen?
Click to expand...
Click to collapse
no, the screen that says serial/usb at top and 2.07 at bottom
I just wanted to make sure that we were on the same page
In my opinion (and this is just a theory), Windows 7 (since it is a beta) does not have the necessary drivers to recognize the "usb device". Hence, when you put it in the cradle, it just doesn't see it. Again, this is just a theory...
You may want to get a hold of a machine with XP (that is if you didn't make the one you are using a dual boot). You should be OK if you try to flash via XP.
If everything else fails, you can always use mtty and flash via SD card (the procedure can be found in the wiki).
I had the device synced up before the install. it's just having issues syncing while it's in the bootloader mode. The device actually appears in the usb devices, but doesn't sync. i was thinking that the device might have to be authenticated with local software(on the sx66) in order to sync. I'm using the windows vista drivers. I do have this machine dual boot, but it's not any other version of windows i'm using
Your device does not have to sync in order to up/downgrade. Think about it this way... the RUU will put the device in bootloader anyways.
Just run the installer of the stock rom (the upgrade from Cingular).
@N1cholas: Please correct me if I'm wrong. I'm just a little confused. Are you expecting MS Active Sync to show as it usually does when you are syncing your phone? If that is the case, it won't happen when on boot loader. Are you getting any error when trying to flash or you haven't tried to flash yet?
Advise:
1. Keep your hopes, don't get despert. Egzthunter is a master
2. Make sure you follow the guide... Step by Step to upgrade.
3. If it'll take you too long to complete the reading and flashing, reset your phone and put it to charge. You won't be able to flash with a dead backup battery. Main and Backup battery won't charge while on bootloader.
Edit: @Egzthunder: Sorry mate, while I was thinking, drinking coffee and writing you had already replied Like I said, your the help master. Once again, I encourage the MODS to propose you to be part of their teem. You're always there to help.
Mark
i'm going to head off to school, but it's not working. when i try to run any mods i get an error saying that it cannot communicate with device.
Yeah! Egz for MODS!!! Woohooo and Xplode too and someday..me! LOL (no i mean it!)
windows 7 uses the same drivers as vista
beakybal4 said:
windows 7 uses the same drivers as vista
Click to expand...
Click to collapse
Why do you think I don't trust it?
@N1cholas,
I apologize since I ended up going to bed yesterday night.
I think your best bet will be to find yourself a PC running XP and try the reflash in that since it seems to me that something is going on with the OS.
@red and mark
Thanks for the support, guys!!! But you guys are awesome as well!
yeah, it's weird, it's just not working anymore. It appears in the device list and everything, but in WMDC it doesn't show up, and the rom install wizzards can't communicate with it either. I have been unable to find the upgrade ROM from cingular as it seems that the siemens' page has been removed. Also, I have a 2gb SD drive, but haven't been able to find information about flashing the SX66 from the SD.
N1cholas said:
yeah, it's weird, it's just not working anymore. It appears in the device list and everything, but in WMDC it doesn't show up, and the rom install wizzards can't communicate with it either. I have been unable to find the upgrade ROM from cingular as it seems that the siemens' page has been removed. Also, I have a 2gb SD drive, but haven't been able to find information about flashing the SX66 from the SD.
Click to expand...
Click to collapse
You will not see the device in any type of sync software (call it ActiveSync, WMDC, etc). I hvae uploaded the SX66 stock installer from Cingular, so give that a shot
Here you go
SX66Update.exe
Like I said... XP computer. Also, for the SD flashing, you need to look for something called mtty and instructions on how to use it.
the proper solution
1.MTTY method for unblocking bootloader mode
2.Upgrade the same way as in Vista to stock rom
3.Sim Unock, Repartition DOC
4.Upgrade vista way to any rom you like
there are guides in WIKI about this
egzthunder1 which version extrom version and radio are in this rom - the one you sharing? As you know i make public BA shipped rom collection, and any rom which is not there is welcomed
xplode said:
the proper solution
1.MTTY method for unblocking bootloader mode
2.Upgrade the same way as in Vista to stock rom
3.Sim Unock, Repartition DOC
4.Upgrade vista way to any rom you like
there are guides in WIKI about this
egzthunder1 which version extrom version and radio are in this rom - the one you sharing? As you know i make public BA shipped rom collection, and any rom which is not there is welcomed
Click to expand...
Click to collapse
Hey xplode,
To be perfectly honest, I haven't flashed 2003 since 2006, so I would be lying if I told you. Feel free to add it to your database if you wish. FYI, this is the upgrade that Cingular Wireless used to offer when the SX66 was still available in the at&t website.
MTTY doesn't have a USB option, it's only giving me COM1, COM2, COM3...
N1cholas said:
MTTY doesn't have a USB option, it's only giving me COM1, COM2, COM3...
Click to expand...
Click to collapse
Did you try the update that I gave you?
i ran it, and it said it was trying to get the settings from the device, then it just disappeared lol. now when i run it, it extracts the install data to the temp folder on my pc, then just disappears