Database Develop

Upgrade went wrong, Vario bricked?

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?

Color Bars Help Please

Tried to flash button rom with full battery. Comunication error. Only boots to 3 color bars. Every time I retry the flash the phone starts flashing on and off.

Mmmmmm
What is the problem....?
Does your wizard dont begins... so it wont wake up... dont start ?
You cant turn it on?
What do you mean with turn on and off?
is blinking?
If the problem is its blinking and dont stands on... it is a serios problem but if the wizard saty on ... what ipls and spl got?
What did you do?
Men we need to much info..... than it is on bootloader, i cant upgrade etc etc etc.

FUUUUUUU******@@@@@
while flashing the button rom, i got a communication error. At random times after connecting the phone via usb the screen flashes on an off and communication is lost. sometimes the phone gets mostly through the flash, sometimes it wont even start to flash. But here is the f-ing kicker, while trying to recover in the button flasher proggie, my computer locked up and WILL NOT TOUR BACK ON. thats right, i lost my phone and computer in 5 minutes thanks to this flasding sh*t. i am only able to access this forum via a blackjack II smartphone.

OK, Feeling better
Sorry about that.
I got my computer back on.
It wouldnt even go to cmos so I traded out my cpu, still didnt work.
Put the old cpu back in and it booted just fine. Not sure why that happened but at least my computer is back on.
Ok so back to the phone. It boots to the 3 color bar screen and shows IPL/SPL as 2.25. After connecting the USB cable it will sometimes start flashing, not always. If I restart the button rom flasher it will start to flash, after getting to some % the phone starts flashing.
By flashing I mean the screen flashes on and off. Likely the phone is rebooting itself constantly.

Undo?
Is it possible to just undo what ive done? Is the old info still on the phone? IPL/SPL are still the same as before.

No, your old info is not on the phone anymore. The first thing that is done when the flashing process begins is deletion of your flash on your phone. This may seem like a n00b question, but have you tried using a different USB port? DO NOT flash with a port off of a hub, they are usually under powered when compared to direct board connected ports. Try one on the back of your tower(or directly in your notebook whatver.) and see if that works.

It also failed on the back usb port.
All is not lost is it?
I believe that this phone might need a new battery.
I had some problems with the phone turning off when it wasn't supposed to but it hasn't done it in a long time so I though I was ok. Do you think that a new battery might allow this downgrade to complete?

Its possible. The Wizard is kind of a tempermental device....it flashes when it wants to some time. You can try and see if a new battery is what fixes the problem, but in all honesty, it could be anything.

Xtrange
ok
try to get connecte with that cable other device, maybe is broken the cable...
try another usb port...
download again the button rom, maybe is corrupted.
lets wait what happen

Its your battery , replace the battery and it will charge and then you can flash it,you can get two batteries for a tenner on ebay

Battery
OK, so once the new battery comes, it will charge via usb and wall charger just as it would with the OS installed? Im not sure if charging is dependent on the OS at all.
Thanks for all of your help guys.

Does it charge?
It charges??????
in bootloader dont charge men....
if the phone stuckson welcome screen maybe charges, on htc logo dont, neither on splash screen.
All we do is try to help people to upgrade and try to found solutions for those who made a bad upgrade, but i didn't cook, and dont develop anything so my only contribution is for experiences.
Hope your wizard revives.

My wizard does not bootup...only three color bars
I was trying to flush with new ROM and it stopped after 100% and in the mean times, my system rebooted. Now I got this MDA with three color bars, battery is OK but important thing is that it does not connect to computer thru Active Sync............any help>

[PROMBLEM] Diamond stuck in restart loop.

I believe my battery ran dead and i didnt notice, now my when you press the power button the blue o2 loading screen comes on then about 2 seconds later the device restarts and same thing over and over.
If i plug a an ac adpater in (i've tried 2 and an incar charger) the light ring goes up twice then then phone triggers a start up and gets stuck in the loop. I've tried leaving it in this loop for 10mins see if it would charge the battery but no luck.
I have tried doing a hard-reset 3 times now it says its done ok soon as i press vol up to boot it goes into the loop.
Is there anyway i can charge the battery if this is the case or is there another problem thats causing this?
Any help would be appreciated.

Are you sure the battery is dead?
If you left it in the loop for 10 mins I would have thought that it would flatten it such that it doesn't light up at all.

I know the battery was very low before it started doing this and i hadnt installed anything new in months.
Usualy on the o2 screen it shows red writing at the top and bottom, its not showing that right now if that means anything.
Its a stock o2 uk rom with no changes to the radio and official battery.

I've just installed the latest rom from the o2 website (keeping it stock incase i need to send it off to them) and still doing the reboot on startup thing.
Contacted o2 see what they say but if anyone else has any ideas im open to suggestions

i've got the same issue and the battery won't charge ...i suppose it could be a battery issue, but i'd be sure about it prior to buy a new battery..

Battery was fine, i sent the phone to the o2 repair centre got it back week later fixed

SMeK said:
Battery was fine, i sent the phone to the o2 repair centre got it back week later fixed
Click to expand...
Click to collapse
did you use a modified rom? ..i was told htc repairs only unmodified products, could you gimme more information about it?

No it was not a modified rom, default o2 xda ignito rom.

Me too!
I had the same issue. I tried soft-resets, hard-reset, swapping batteries with another phone (even tried warming the battery in my hands which was suggested somewhere!), reflashing a couple of different ROM's, including Shaks 4.30 and the latest Telstra ROM (2.07.841.2 WWE). I tried using MTTY to reflash the ROM, and reflashing using the DiamonCustomRUU.exe from the PC. (OliNex 1.40 SPL). All of the reflashes were in Bootloader mode (hold pwr and vol down) because I couldn't get it to the point of ActiveSync connection.
Nothing would work.
The winning step that bought me the joy (and relief) I was looking for was downgrading the radio from 1.09.25.23 to 1.00.25.05.
Also, I'm not sure if it is related, but I think the reset button under the stylus is stuffed because pressing it doesn't do anything.
Now I've escaped the reboot loop from hell, I'll run it for a few days before giving it back to my boss! If anyone's interested, I'll update you in a few days.
HD.

could you please tell me how you installed the radio, because when I use diamoncotumruu it stays at 0% and the finaly gives an error

yves_the_man said:
could you please tell me how you installed the radio, because when I use diamoncotumruu it stays at 0% and the finaly gives an error
Click to expand...
Click to collapse
I had to install the radio in Bootloader mode (hold pwr and vol down), but there was no issue with the install after doing this. Have you checked this thread? I don't know if that thread will help you fix your issue but it might be worth a look.
What exactly was the error message? Perhaps a search on that error message will help you.
HD.

I've tried it in bootloader mode, but it won't install...
the error number is 262. but that should be an active sync problem but I can't sync so I don't know what the problemm is

Not really on topic, but...
yves_the_man said:
I've tried it in bootloader mode, but it won't install...
the error number is 262. but that should be an active sync problem but I can't sync so I don't know what the problemm is
Click to expand...
Click to collapse
262 isn't an necessarily an ActiveSync problem, more of a connection problem. Try post 9 here. Or try uninstalling Active Sync altogether and installing radio and ROM via MTTY. Since it is a connection problem, you could even try a different USB cable.
But I suggest you post 262 queries here, here, here or here.
BTW, Are you using XP?
HD.

RHOD210 Won't Boot.

I was running one of the ENERGY ROMs on my TP2, so it's got a different SPL and all that. I then put it in the box for about 5 weeks. I took it out two days ago to install XDANDROID. I used XDANDROID for about an hour, until the TP2 started randomly shutting itsself off. I've tried flashing NRGZ28's ULTRA LITE ROM and the official T-Mobile USA 6.5 ROM for the TP2. It won't go past the boot loader a majority of the time. When it does, it goes on to act like it's flashing the RHODIMG.nbh on my MicroSD but almost instantly after it starts, it shuts off again. It doesn't always try to flash the .nbh, but when it does, it never finishes. It's the same story with a hard reset. I can't ever get it to turn on, and the only way it does turn on is to do a battery pull. If I'm lucky, it'll stay on for about 60 seconds and then shut off again. I'm really clueless as to what to do here and I'm hoping someone can help me.
The Bootloader reads as folows:
RUUNBH
RHOD210 32M SS-BC
SPL-0.85.OilNex
MicroP(LED) 0x0A
MicroP(KEY) 0x04
TURBO HW/TURBO SW
TP MFG DATA
[unreadable]
812,19...
217.855 Calibrated
The reason 1.5 of the lines is unreadable is because of the message over it: "Upgrade ROM code error. please try again."
http[colonslashslash]farm3[/url][dot]static[dot]flickr[dot]com/2726/4386331314_8036d882a6_o.jpg

try flashing hard spl 1.01 it looks like you got an old version of the spl. read the sticky on flashing for newbies i belive it tells you how to do the hard spl if you are having difficulty by usb connection other than that i wouldnt know what to tell you i nver had that problem only bad flashes but those could be solved by reflashing another ROM

Sorry, i should have explained that better. I can't connect to the PC. It won't stay in bootloader mode so I can't flash it that way either. From what i understand, the only way i can flash anything to it right now is to get the xxxx.nbh file, rename it to RHODIMG.nbh and place it on the root of my SD. When I do that, though, it won't finish the flash. It just keeps going in a loop. about every 5 minutes it randomly turns on and tries to flash the RHODIMG.nbh if present. If it's not present, it just flashes the boot loader for >10 seconds and shuts off again.
Also, I'm not sure if this makes any difference, but I've had TWO computers recognize it as a new device, "Qualcomm CDMA Technologies MSM."

Make sure the battery has a good charge, nothing else springs to mind
PS. the qualcomm thing is what appears when it's flashing via USB
also maybe try formatting your SD card and put the stock ROM back on there, or try diff card

chasejones8 said:
Sorry, i should have explained that better. I can't connect to the PC. It won't stay in bootloader mode so I can't flash it that way either. From what i understand, the only way i can flash anything to it right now is to get the xxxx.nbh file, rename it to RHODIMG.nbh and place it on the root of my SD. When I do that, though, it won't finish the flash. It just keeps going in a loop. about every 5 minutes it randomly turns on and tries to flash the RHODIMG.nbh if present. If it's not present, it just flashes the boot loader for >10 seconds and shuts off again.
Also, I'm not sure if this makes any difference, but I've had TWO computers recognize it as a new device, "Qualcomm CDMA Technologies MSM."
Click to expand...
Click to collapse
it sounds like you dont have your sd card formatted make sure its format to FAT32 go to your computer inserd sd card & reformatted (make sure its a micro sd & that its less than 2g) then transfer the ROM to the card already renamed to RHODIMG then inserd ur card on your phone & flash it. it should work. let us know what happens

MadBeef said:
Make sure the battery has a good charge, nothing else springs to mind
Click to expand...
Click to collapse
I wish I could. I have no means of checking the battery status. I've had it plugged in pretty much constantly for about the last two days.
MadBeef said:
PS. the qualcomm thing is what appears when it's flashing via USB
Click to expand...
Click to collapse
I figured that's what that was, I was just a little shocked that it said CDMA.
And I tried wiping the card and reflashing, but it did exactly the same thing.

See at the top of your bootloader readout, where it says RUUNBH? That means the RUU flag is set, and that needs to be unset before you can do other things. What you need to do is establish a connection with your device via MTTY. Follow the instructions here about how to do that. Once you get an MTTY connection established with the device (it may take awhile since MTTY is quirky sometimes), type
Code:
Set 16 0
You may need to manually soft reset afterward, but otherwise you should be in the clear

The TMO Stock ROMs can install via PC even if your phone has a faulty USB connection. The stock ROM installer will keep restarting the phone's USB connection automatically as needed if your phone can't appropriately flash in one straight attempt. You can get the newest stock ROM here. And definitely install HardSPL again after getting the phone up and running on the stock ROM.
You might also try MTTY.exe. When connected, run the command 'set 16 0' then 'task 8' then 'task 0'. If your phone doesn't automatically soft reset, then manually soft reset with the stylus.

will MTTY.exe work via parallels on a Mac? I haven't tried it yet, but I have limited access to a PC. also, I tried doing the HardSPL and the TMO rom via PC, but the phone just does the same thing. It will connect, but then the RUU tries to check the phone settings and the phone shuts off. this is the problem i am having. i just cant get it to say on long enough to do anything. I'll try the MTTY.exe through parallels and if it won't respond, I'll have to wait to try it on a PC. I'll let you know how that goes.

MTTY is quirky enough that it probably won't work through parallels, though there's no reason you shouldn't at least try and see if it works. You'll probably have to wait until you can get access to that PC. Best of luck

DaveTheTytnIIGuy said:
MTTY is quirky enough that it probably won't work through parallels, though there's no reason you shouldn't at least try and see if it works. You'll probably have to wait until you can get access to that PC. Best of luck
Click to expand...
Click to collapse
Thanks. I'll have to wait till i get back to the phone but i will let you know how it turns out.
also, in reading your sig, i see that i was using the same SPL that you are. have you had any problems with it?
I was also using the ENERGY LEO ROM [i now see that you are using it too.], which apparently was defective because the next day, the chef posted a new one because of "sleep of death." I read through the thread and didn't see anyone with the issues that i was having.

chasejones8 said:
Thanks. I'll have to wait till i get back to the phone but i will let you know how it turns out.
also, in reading your sig, i see that i was using the same SPL that you are. have you had any problems with it?
I was also using the ENERGY LEO ROM [i now see that you are using it too.], which apparently was defective because the next day, the chef posted a new one because of "sleep of death." I read through the thread and didn't see anyone with the issues that i was having.
Click to expand...
Click to collapse
I haven't had any problems with this SPL, but then again, this is the only end-user version of HardSPL for GSM devices that's been made available. The SPL isn't even your problem, the only problem is that a bootloader flag is set which shouldn't be.
As for the EnergyROM sleep of death problem, that's not what you're suffering from. The sleep of death problem is when your device won't resume after being put into standby, meaning one must soft-reset their Rhodium and lose any unsaved data in open programs. It's a somewhat common problem among many HTC devices, from the old ones like the Kaiser to the newer ones like the Rhodium (though I don't think any Android device has this problem).

jdep1 said:
try flashing hard spl 1.01 it looks like you got an old version of the spl.
Click to expand...
Click to collapse
Eh ? Sorry, but I think you're confused. He's running 0.85 HardSPL, which is the one and only version for GSM Rhodiums.

I got to a PC and tried MTTY.exe
I can't seem to get it to connect. It just says "USB port can not open."
Any suggestions?
EDIT: I can get it to connect to a different version of MTTY.exe for a short time, but I can't type anything. All I get is a blinking cursor.

chasejones8 said:
I was running one of the ENERGY ROMs on my TP2, so it's got a different SPL and all that. I then put it in the box for about 5 weeks. I took it out two days ago to install XDANDROID. I used XDANDROID for about an hour, until the TP2 started randomly shutting itsself off. I've tried flashing NRGZ28's ULTRA LITE ROM and the official T-Mobile USA 6.5 ROM for the TP2. It won't go past the boot loader a majority of the time. When it does, it goes on to act like it's flashing the RHODIMG.nbh on my MicroSD but almost instantly after it starts, it shuts off again. It doesn't always try to flash the .nbh, but when it does, it never finishes. It's the same story with a hard reset. I can't ever get it to turn on, and the only way it does turn on is to do a battery pull. If I'm lucky, it'll stay on for about 60 seconds and then shut off again. I'm really clueless as to what to do here and I'm hoping someone can help me.
The Bootloader reads as folows:
RUUNBH
RHOD210 32M SS-BC
SPL-0.85.OilNex
MicroP(LED) 0x0A
MicroP(KEY) 0x04
TURBO HW/TURBO SW
TP MFG DATA
[unreadable]
812,19...
217.855 Calibrated
The reason 1.5 of the lines is unreadable is because of the message over it: "Upgrade ROM code error. please try again."
http[colonslashslash]farm3[/url][dot]static[dot]flickr[dot]com/2726/4386331314_8036d882a6_o.jpg
Click to expand...
Click to collapse
I had this EXACT same problem a week ago. I fell asleep in the middle of flashing, the phone died when it finished. I woke up, turned on the phone, ENERGY leo was trying to run its install but kept dying. Smart me, I tried to reflash (by holding the vol down button and turning it on- not through usb) and it kept dying in the middle of trying to flash.
The problem is the battery. It can't charge when it's flashing and it can't hold a charge long enough to get past the flash.
I swapped batteries with my friend, restarted the flash and it worked fine.
I let my battery charge in my friends Sprint Hero
and voila, everything went on happily ever after.
tl;dr find a way to use a charged battery while flashing.
your phone's not bricked.

bfgarzilla9k said:
I had this EXACT same problem a week ago. I fell asleep in the middle of flashing, the phone died when it finished. I woke up, turned on the phone, ENERGY leo was trying to run its install but kept dying. Smart me, I tried to reflash (by holding the vol down button and turning it on- not through usb) and it kept dying in the middle of trying to flash.
The problem is the battery. It can't charge when it's flashing and it can't hold a charge long enough to get past the flash.
I swapped batteries with my friend, restarted the flash and it worked fine.
I let my battery charge in my friends Sprint Hero
and voila, everything went on happily ever after.
tl;dr find a way to use a charged battery while flashing.
your phone's not bricked.
Click to expand...
Click to collapse
That's the best news i have heard so far. I don't know anyone with a TP2, but i do know someone with a Hero. I'm assuming the GSM hero uses the same battery as the CDMA Hero and the TP2. I'll look into it and let you know how it goes.

chasejones8 said:
That's the best news i have heard so far. I don't know anyone with a TP2, but i do know someone with a Hero. I'm assuming the GSM hero uses the same battery as the CDMA Hero and the TP2. I'll look into it and let you know how it goes.
Click to expand...
Click to collapse
chin up, bud
I actually had a replacement sent to me.
That took a week. I fixed my phone the DAY AFTER i requested a replacement.
ohwell.
Brand new TP2 for ten dollars (shipping) I'm not really complaining.
&yes. The GSM Hero does use the same battery. I was just looking at my friends phone, decided to take a look at the battery and shat bricks when I saw it fit in my phone.
report back after you try your friends battery if it works or not!

bfgarzilla9k said:
chin up, bud
I actually had a replacement sent to me.
That took a week. I fixed my phone the DAY AFTER i requested a replacement.
ohwell.
Brand new TP2 for ten dollars (shipping) I'm not really complaining.
&yes. The GSM Hero does use the same battery. I was just looking at my friends phone, decided to take a look at the battery and shat bricks when I saw it fit in my phone.
report back after you try your friends battery if it works or not!
Click to expand...
Click to collapse
thank you so much! that fixed everything. they weren't quite the same battery, the one from the HERO isn't quite as wide. it did work, though. I'm charging my tp2 now. not sure if the battery is shot or not. everytime i unplug it, it shuts off. i'll have to charge it for a while and see if that changes anything. again, thanks so much!

O2 XdaIIS Dead while Upgrading

Hello All Expertz,
My 02 xdaIIs was dead while upgrading ROM.It was struck at 23 % and i was forced to disconnect.Now it is not showing any screesn even in full charged battery.I soft reseted but not working ITS DEAD.Can anyone pls help????
Thanks in Advance
MT

Milesht said:
Hello All Expertz,
My 02 xdaIIs was dead while upgrading ROM.It was struck at 23 % and i was forced to disconnect.Now it is not showing any screesn even in full charged battery.I soft reseted but not working ITS DEAD.Can anyone pls help????
Thanks in Advance
MT
Click to expand...
Click to collapse
Can you put it in bootloader mode? (white screen with the word "Serial" or USB and "v2.0x")

No..not able to put in bootloader mode.i tried to put in by pressing power+record+soft reset nothing happened.Only response i get is when i put in cradle for charging it shows a red light.pls help

in that case you should remove the battery and charge it in the back of the cradle (needs AC power supply, usb alone doesn't work). it might also show red at first, meaning the battery is completely dead now, but shortly after that, it will turn orange. if, during the charging process, it should turn red again, your battery is probably broken. maybe the battery dying was the reason your upgrade failed in the first place. i had a similar issue when i first tried upgrading in vista several years ago (before i came here). i removed the device from the cradle and it was still in bootloader mode. normally you should let the device stay in bootloader mode and just start flashing again. i didn't do it and neither did you, so all you can do is try everything to get it into bootloader mode again.
try everything you can do with the device at the moment:
- insert the battery, try bootloader
- reset, try bootloader
- power+reset, try bootloader
- battery out, battery in again...
eventually you will get the device back into bootloader mode and can try flashing it again. but before the next attempt to flash it, you should find out, what caused the error in your last upgrade to make sure, it does not happen again.

Milesht said:
No..not able to put in bootloader mode.i tried to put in by pressing power+record+soft reset nothing happened.Only response i get is when i put in cradle for charging it shows a red light.pls help
Click to expand...
Click to collapse
Chef is correct. The battery will not charge if it is on the device. Luckily for us, the BA cradle has the charging slot in the back for the "extra" battery. I would (regardless if it is dead or not) just buy a new battery on e-bay (they are dirt cheap nowadays) simply to rule out the possibility of the battery being dead, which as chef suggested might be the reason for the failure (especially if you cannot turn on the device).

Tony,
It worked lot of thanks.
1.Removed battery charged it.
2.Done hard reset(power+softreset)
3.Tried bootloader.IT WORKED .....
4.Flashed it with old stable wm6.1 rom.
IInd case.Finding the root cause.
After flashing I put that back again to the cradle.Then problem began BA went OFF.
Then I softreset and put again to the cradle before OS boots up Tried 3 times same result to make sure its cradle prob.
I take out frm the cradle
softreset the BA to boot.Now another problem.ITS not booting it reaches the FOUR COLOR SCREEN WITH RoM DETAILS then it FADES OUT with some markings(horizintal lines) here and there.
I waited for few minutes removed battery.Put it again then pressed power button got same results.
On the second attempt while locking the battery switch (pressing it up) That old RED LIGHT glows up.Then I pressed it down to unlock and removed battery.Then I tried again
This time it boots up and everything came to normal.(My HEART BEAT WENT DOWN) Thanked GOD.. And ofcourse you Tony.
Meanwhile I had given a small blow at the cradle and put my sweet Angel to cradle its working fine Now.
SO AM NOT SURE WHO IS THE real CULPRIT.. Battery,battery switch,or cradle?..
egzthunder,
I think battery is ok because I am getting the same backup just it was before..
So big THANKS to u two of you.
( I write this post frm my BA ) ;-)
Regards
Milesh James

egzthunder1 said:
Can you put it in bootloader mode? (white screen with the word "Serial" or USB and "v2.0x")
Click to expand...
Click to collapse
Hello,
I am facing the same problem on my xda iis showed on the screen only " Serial/USB v2.06"
I am really appreciated if you and someone can help me to solve the problem.
Many thanks for your kindness.

please don't double post, there was really no need to bump the other thread, since it is incredibly outdated and not helpful at all. being stuck at the serial v2.07 screen, the bootloader, you should try starting over from the very beginning, using the guide in my signature (if you are a windows xp user).