Upgrade went wrong, Vario bricked?

[DaRKoNe]

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?!

[blazoner]

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!

[DaRKoNe]

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 :P
Phew.. man I'm reliefed :P You just made my day! :D

[gumbydude]

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 :P

[DaRKoNe]

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..

[kyphur]

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 :P

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

[XpuctoC.]

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?