I have installed the Hima Upgrade Pact on the XDA IIs, the screen blacked out. I cannot even hard reset, the screen just displayed serial V2.07
i remember when i was installing it, it did display, saying this upgrade is not for this model.
What should I do.
Pls help.
All you have to do now is flash your device with an XDA IIs device. Just plug it into your cradle, and "serial" will change to "USB". Then, run the BaUpdateUt.exe of a XDA IIs rom, and it will flash. Hard reset, and you are good to go.
Thank you very much. You are such a darling.
I'll try that right now.
Related
Hi all,
Im looking for some advice to restore my XDA2S. My pc crashed through the o2 upgrade process and Im stuck in bootloader - I cant create an active sync session to run the upgrade again. Any help appreciated.
Sorted It.
OK, sorted. There were lots of similair posts with no reply, so here goes.
Disconnect from cradle
Disconnect battery.
Reconnect battery
Hard reset the device
Insert into cradle - activesync wont start.
Run the upgrade.
Be patient, it takes a while to recognise (at least a few minutes).
Thank God!!! Now have a copy on my SD card.!!!!
Rom upgrade
Thought I'd broken mine within 6 hours of having it too! It all goes wrong if you don't power the docking station. You method for recovery is quite right and it's how I got mine back from the boot loader. Are you suggesting that you can upgrade from the SD card as well?
how long does it exactly take to respond?
PLEASE HELP! i have a xdaIIs i only see on the screen serial v2.07 when i press on, soft reset button and the volume bar nothing happens! i have the rom on a SD card. what am i suppose to see on the SD card? PLEASE HELP!
not to worry, bogs
i had the same problem once, just follow the procedures eskimofisherman gave in the 2nd post and it'll be ok
hope this helps
upgrade problem
had exactly the same thing happen to me!
hard reboot the xda2s
powerbutton held, push bottom reset.
reboot PC reload software ie Xda_IIs_v131139_upgrade.exe then when asked put pda in cradle.
worked for me.
although i have to say the upgrade is ****E! tom tom navigator doesnt like it at all, we were better off with the old one.
I'm trying to find out where to get a copy of it.
http://wiki.xda-developers.com/index.php?pagename=BA_Upgrades
ok my xda locks up (nothing new there!) soft rest and all i get is a white screen! try again and the same thing happens. So i decide to do a hard reset. This appears to be working until it's loading applications and settings (O2) when it hits a .per file (i think) and tells me i need to find the source .cab file.
the 2 choices i then have are ok or cancel, niether work the bloody thing is locked up again! so i soft rest it and it's back but with no O2 settings. I try and run a back up from my pc and it all works apart from about 15 files that it cannot reinstall (mainly to do with contacts). I then sync my contact list as that is missing and all looks good! 2 days configuring it back to my liking and all looks good once again!
This morning no alarm to wake me up (bugger im now half hour late for work! lol) the xda had been on charge all night and it appears to be dead! All i can see is the O2 logo like you get at start up but with no back light. the unit does not respond to anything. I've tried taking the battery out, soft and hard reset all with no response! I try and put it back on charge and all i get is the red light come on for 2 mins then go off again! can't turn it on while on charge!
Please help as phoning O2 is really like banging our head against a brick wall!
thanks guys
i'm not to sure but i would say you have two options either download the rom from the o2 website or download the rom Modified_XDA_IIi_Upgrade_V1.11.162_Radio_1.04.rar i installed it yesterday and i haven't had any problems hope this helps
ty but if i cant turn the phone on or connect it to the pc how can i do that????
i might give O2 a call anyway and see what they say. they might offer me a new one which is always good!
o2 could offer you a new one but i read somewhere on this site that the xda IIi has been discontinued so they might upgrade to the xda exec
When I first got my 2i, I had it for a week and then out of the blue it decided to do this after a soft reset one day - got stuck at the O2 splash screen, no backlight, frozen forever. Had to take the battery out to turn it off.
Took it into the shop, the store manager said "yeah, we've seen this happen more than once", and just went into the storeroom and got a me a brand new one.
This did happen the day after I'd run the simunlock tool found on this forum, which worked successfully (I tried my Virgin mobile SIM in it and it worked first time, but I then took it back out and put my O2 SIM back in)... I'm not sure if it was just coincidence or what, but I'm not feeling too eager to run simunlock on my Alpine again until I sell it
thanks guys i thought it might be fried!
called last night but got cut off and then was after 7 so couldn't speak to anyone! :evil:
will try again and see what they say!
when i put it on charge it charges for a few mins then turns onto splash screen for a few mins then turns off and charges again and so on in a loop! really quite annoying! lol
Another thing to try is to put the device into bootloader mode and force a firmware upgrade. It can be connected to the PC but it will no longer use Activesync so the upgrade will work fine.
Once this is done it will be using more up to date firmware if you download the ROM from this sites FTP and should work better in general.
well carphone craphouse couldnt do anything with it so has had to go back to O2 went on the 10th dec and still no word
Hi everybody and sorry for disturbing you guys.
I've got a very strange problem with my friend's O2 XDA IIs (BA Device). The unit was upgraded to WM 5.0, however, I could not HR it. When I Reset the device and press Camera and Record button simultaneously (to make three lines appear), it is possible for me to move up and down and change the options but I can't finish the HR process by pressing the Messaging Button (it does work normally, not a physical prob). Besides, when I tried to upgrade the unit to another ROM (my friend was fed up with the current ROM since it was too slow), the unit couldn't recognize an USB Connection when it was in Bootloader mode (it could sync normally with my PC, already tested this). The screen kept showing Serial at the top and v2.06 at the bottom. As the result, no ROM upgrade Utility could do its job.
I've been using Pocket PC Phones for 2 yrs and this is the 1st time I've seen this problem, even though I used to use a MDA III for half a year.
Looking forward to hearing from you soon.
Tks and rgds.
Same here - device no longer recognized as USB in bootloader mode Previous ROM? helmi_c 2.3
In one of helmi's posts, he mentions something called "clearstorage". This might be what you are looking for. See here:
http://forum.xda-developers.com/viewtopic.php?p=356258#356258
After some playing around I have noticed that my BA hangs in BL mode, sometimes before I put it on the cradle, sometimes after I do that :/
try mtty software
it might be helpful in your case
search the forums for it and for available commands
Hi,
I have a huge problem.. I just wanted to install a new ROM on my MDA Vario
and during the update process I accidentaly knocked the phone of my desk.
Causing the USB to unplug and crash the update.
The Vario now stops booting @ the red, green and blue screen..
Hard reset didn't work and Windows won't recognize the phone when I plug in the USB cord..
Eerrrr.. HELP!
Can I fix this? If yes; HOW?!
The red/green/blue screen is a good sign, when you plug in your USB cable, you should see a USB icon on the bottom of your Wizard's screen. At this point, run the RUU for the ROM again from your PC. This re-flashing should fix it.
If the icon doesn't appear, check to see that the fall didn't break the phone's USB connector. If it did, send it for repair.
The next step would be to reboot your PC, and remove the battery from your phone for 5 minutes or so. Then try to reconnect again, and see if that works (To display the aforementioned icon).
Good luck!
omg dude..
I could kiss you right now.. Before your reply, I tried the same thing already (without the reboot) but that didn't work..
The USB icon did show up on my Wizard's screen, but Windows didn't recognize a USB device, so there was no
way of re-running the RUU to continue/retry the upgrade..
Obviously Windows had a lot of 'update' programs still running in memory..
And I couldn't 'kill' them.. So I reboot my PC, plug in the USB connector and YES! it's updating!!
The phone didn't fall on the USB connector.. It sort of bungee-jumped of my desk
Phew.. man I'm reliefed You just made my day!
Good to hear that you fixed your phone, Darkone.
I recently bricked a Cingular 8125 using an update from Cingular's website. Turns out my phone was a G4 and the ROM update was for G3 phones (Cingular neglected to state this information. I got my replacement phone in the mail, it's a refurbished G3 phone with a messed up, sticky keyboard. My bricked G4b(brand new, in immaculate condition) is stuck in boot loader mode(RGB screen), but I've tried about 6 different G4 ROMs and it appears that there is no way in hell it's coming back from the dead. I think my mistake was not CID unlocking it prior to the ROM upgrade. Glad your upgrade/bricking story had a happier ending
So am I gumbydude.. So am I..
I'm sorry to hear your phone is bricked beyond repair..
But isn't it possible for Cingular to fix your bricked one?
They caused the problem in the first place, they didn't inform you in any way that the ROM was for G3 phones..
I wouldn't agree to use a refurbished, sticky G3 phone if it's their fault you bricked your brand new G4b in the first place..
gumbydude said:
Good to hear that you fixed your phone, Darkone.
I recently bricked a Cingular 8125 using an update from Cingular's website. Turns out my phone was a G4 and the ROM update was for G3 phones (Cingular neglected to state this information. I got my replacement phone in the mail, it's a refurbished G3 phone with a messed up, sticky keyboard. My bricked G4b(brand new, in immaculate condition) is stuck in boot loader mode(RGB screen), but I've tried about 6 different G4 ROMs and it appears that there is no way in hell it's coming back from the dead. I think my mistake was not CID unlocking it prior to the ROM upgrade. Glad your upgrade/bricking story had a happier ending
Click to expand...
Click to collapse
First, if you get the RGB Screen that is the bootloader so your phone IS NOT BRICKED!
Second, the Cingular 2.25 Rom works with both G3 & G4 devices, it contains two complete bootloaders.
Third, you do not need to CID Unlock your device to flash an official Cingular Rom onto a Cingular 8125/8100.
Fourth, you should return the replacement device telling Cingular Returns that it is not in acceptable condition.
Fifth, download the Cingular 2.25 Rom from here: http://www.htcamerica.net/support/8125/software-downloads.html
Well, my problem is kind of similar, so I won't post a new threead, but write in this one instead.
So, what's the story... I upgraded my G3 Wizard to PDAVIET's v4 WM6 ROM and it worked like a charm. Changed the default boot logo with a custom one and after a while I tried to flash again with the same ROM (because I had restored backup from Windows Mobile 5 and had been experiencing a few bugs; however, I had done hard reset before this flashing) - it stuck at 2%; I waited 10 minutes and reset the device, saw the bootloader, pluged the USB and started the flasher - It didn't see my phone is connected to the computer. It turned out that when I plug the USB cable, the device hangs, so if I pull it out, it won't give any indication and the display will still read "USB". So, there is no way to access my phone and reflash it, nevertheless it can go in bootloader mode (however, no LED or keys are flashing) - it will just hang upon connecting the USB cable... Tried to remove the battery for a while and it still hangs just the same way...
Does anyone think there is a way to repair the device and what advice would give me to try to work the problem out?
Howdy, i have looked at all the guides, done loads of research into upgrading my Ignito.
I have tried to use the Olinex 1.40 and also the signed version....
But when i load it all up, go through the correct steps etc.. My phone screen looks like its just had some dodgy virus and looks like its about to die and then slowly turns off...
It then does a full reboot and its like i have a brand new phone again...
I am at a loss as to why it does this..
Anyone have any tips or tricks as to how to get around this problem ?
Any help at all will be very very welcome
Cheers
Sam
when you do the hard spl, you will only get a black screen and then it will reboot, just as you describe.
Hold the volume down key and then soft reset, if you see OLI anywhere, then it worked.
The problem is when i try the upgrade the screen seems to die aftera bout 10secs and then it says its fully done.
So there isnt enough time for the Hard SPL to be upgraded....
Anyone ?? Please....
The problem is when i try the upgrade the screen seems to die aftera bout 10secs and then it says its fully done.
So there isnt enough time for the Hard SPL to be upgraded....
Anyone ?? Please....
Click to expand...
Click to collapse
Maybe you could give more detailed information, what exactly are you doing, what does the PC end of the process say etc.
Can you take any screenshots, what SPL do you have now - the guide suggests that 1.93 could be better for you than 1.4?
Kim
It says complete after about 10seconds and then the phone reboots fully.
The current one i believe is 1.93.....
I have tried both of the Olinex versions to no avail at all.....
......
MuDvAyNeX said:
......
Click to expand...
Click to collapse
I guess no one is helping because you're not giving us enough information, procedure, XP or Vista, have you tried Hard-SPL 1.93, screenshots or better description of the problem.
Screen goes funny and then reboots just isn't enough
Kim
Well i have tried both of the Olinex versions both the 1.4 and the 1.93.
I am using windows vista and the mobile device center, its fully connected as i do a sync etc before hand.
I then load the Romloader that does the usual tick this, tick that etc.
Once that has happened i click the upgrade button, it then confirms i am going from the current SPL do the one i have chosen.
I click ok and then it goes to the progress section where it says it could take upto 10min, the screen on the phone then looks like it has got a virus and starts to look like its dying.
Meanwhile after about 10 seconds it tells me that upgrade is done, this is while the phone reboots and starts like its a brand new phone again with no changes that i can see...
In all honesty i can't see what i am doing wrong
Scrath what i just put, as i was typing that i was trying the upgrade via my mates XP laptop and it now says in the bootloader 1.93 Olinex...
I am going to guess this is upgraded... lol
MuDvAyNeX said:
it now says in the bootloader 1.93 Olinex...
I am going to guess this is upgraded... lol
Click to expand...
Click to collapse
Great, glad it's sorted, I was gonna say I don't have much experience with Vista (an' I don't want to )
I'm sure that I've read that there can be issues with the Vista device center(sic), A quick search of XDA-Dev will help.
If you want to eliminate the PC <-> Ignito pitfalls maybe try Suillers method of upgrading direct from the device Internal Storage.
Kim