Database Develop

Holy shizznits, cannot enter bootloader, HELP

So I was playing with the loons kitchen and got called away for a bit...I left my phone plugged in and the kitchen on the desktop (groan now)...my kids wanting to get on the pc did something...not sure what, but my husband says he walked by and said that the ruu was up...I thought ah crap...so I grabbed my phone and saw it was stuck on the splash screen. I rebooted, nothing, splash screen only. I tried getting into bootloader, finally got the message to "restore factory defaults press send" which I did...still, it won't go past the splash screen. I tried the directions found in the "force a bootload" thread...nada. It WILL NOT read as plugged in, and I cannot get it to flash to ANY rom, not button's not the official Tmo, none...PLEASE PLEASE help!!!!!
Thanks in advance.

akashastrega said:
So I was playing with the loons kitchen and got called away for a bit...I left my phone plugged in and the kitchen on the desktop (groan now)...my kids wanting to get on the pc did something...not sure what, but my husband says he walked by and said that the ruu was up...I thought ah crap...so I grabbed my phone and saw it was stuck on the splash screen. I rebooted, nothing, splash screen only. I tried getting into bootloader, finally got the message to "restore factory defaults press send" which I did...still, it won't go past the splash screen. I tried the directions found in the "force a bootload" thread...nada. It WILL NOT read as plugged in, and I cannot get it to flash to ANY rom, not button's not the official Tmo, none...PLEASE PLEASE help!!!!!
Thanks in advance.
Click to expand...
Click to collapse
Just compose yourself for a sec while we ascertain whether it is an actual brick or not. We need to determine two things:
Can you safely assume that your battery has sufficient charge to try a few things? We dont want a completely flat battery to make matters worse.
Only if you have plenty of battery left. Tell us what happens when you enter bootloader mode by holding down camera button and pressing the soft reset hole with the stylus. If your able to get into the tricolour screen then you should be fine.

peter petrelli said:
Just compose yourself for a sec while we ascertain whether it is an actual brick or not. We need to determine two things:
Can you safely assume that your battery has sufficient charge to try a few things? We dont want a completely flat battery to make matters worse.
Only if you have plenty of battery left. Tell us what happens when you enter bootloader mode by holding down camera button and pressing the soft reset hole with the stylus. If your able to get into the tricolour screen then you should be fine.
Click to expand...
Click to collapse
I had at least 80 percent battery. I cannot get into the tri-color screen. Tried holding camera and soft reset, tried comm, camera, power, tried talking sweet to it...it just goes to splash screen each time. HELP!!!
This is a G3 wiza200 IPL/SPL 2.26 and it IS unlocked.
Thanks in advance

If your trying to get into bootloader mode, the device shouldnt boot like normal up to splashscreen. If your getting this far then theoretically the bootloader shuold be fine. I'm going to explain the process in simple terms. I'm not treating you like a child I just want to clarify then we can move on to trying other methods.
1.hold down camera button
2.press little hole on side with stylus
3.release camera button.
Your device should reboot to bootloader mode. Then next thing you see should be the three coloured screen.

peter petrelli said:
If your trying to get into bootloader mode, the device shouldnt boot like normal up to splashscreen. If your getting this far then theoretically the bootloader shuold be fine. I'm going to explain the process in simple terms. I'm not treating you like a child I just want to clarify then we can move on to trying other methods.
1.hold down camera button
2.press little hole on side with stylus
3.release camera button.
Your device should reboot to bootloader mode. Then next thing you see should be the three coloured screen.
Click to expand...
Click to collapse
Yeah, I know...in theory it SHOULD, it's not, hence the freaking out. I am attempting to charge it on the main plug, but it begins to charge then dies. I did have a loose usb port, which I thought got fixed, as my phone charged fine last night, and sync'd fine today. I'm not a pro, but not a noob either...so I am getting frustrated because trying the things I do know, aren't producing the results they should.
**The splash screen is one I made, independent of an OS...after any rom change, I flash my custom splash screen...it has always worked...however, it is making me think that it is the ONLY thing on the MDA, and any signs of a rom were somehow killed by my kids flashing the phone with a very incomplete kitchen rom.**
I will try again. Any help that can be offered would be MUCH appreciated.
PS---I LOVE Heroes!!

When plugged into either usb or main plug, does either light (green/orange) stay on? If not then this symptom combined with a general loose fitting of the usb/main plug would indicate a malfunctioning loose usb socket. The thing is though, even with a loose socket you should still be able to enter bootloader mode. This puzzles me.
Other rescue options include sd-card method, but if you dont have one already, a non-functioning usb will prevent you from composing one because you need communication between the pc and your device.

peter petrelli said:
When plugged into either usb or main plug, does either light (green/orange) stay on? If not then this symptom combined with a general loose fitting of the usb/main plug would indicate a malfunctioning loose usb socket. The thing is though, even with a loose socket you should still be able to enter bootloader mode. This puzzles me.
Other rescue options include sd-card method, but if you dont have one already, a non-functioning usb will prevent you from composing one because you need communication between the pc and your device.
Click to expand...
Click to collapse
I can get brief and random orange lights (my phone was not 100% but at least 80% when I first began)...it takes a lot of sweet talking though to get it to connect to charge. I tried a backup battery as well. Pushing the camera and soft reset either produces my custom splash, or nothing at all (no boot whatsoever). I am truly stumped.
EDIT
I am not aware of the SD card method. I do have an SD, but if I need a special program, I do not have it.

The fact that no light remains on when you connect usb or mains plug makes me think that the usb socket is loose again. In which case I'm doubtful that you can flash via bootloader mode.
The fact that you cant get into bootoader mode suggests that it was somehow corrupted when the flashing process was interrupted. This could be unrecoverable.
From here I'd suggest you investigate the sd card method. I've never relied on this method so this is uncharted territory for both of us.
Read this thread here and here. I think we're running out of options...

Semi success, I got into the quad colored boot (white bottom)...but cannot get it to recognize the usb. I am getting an error message about an unrecognized device, so I will try to fix active sync first...any suggestions for me now that I am at least in a bootloader screen

thats awesome.that means you do in fact have a bootloader still.
You need it to display USB in the little corner. When your in bootloader mode try removing and inserting the USB cable, we need it to show USB in the corner. Without this, you cannot flash.

peter petrelli said:
thats awesome.that means you do in fact have a bootloader still.
You need it to display USB in the little corner. When your in bootloader mode try removing and inserting the USB cable, we need it to show USB in the corner. Without this, you cannot flash.
Click to expand...
Click to collapse
it shows usb in the corner, however it is not producing any charging light, nor does my pc recognize the usb. So...I don't know if this will matter, but as I said...I have the RGB + white bootscreen with usb in the corner...is there still a chance????

yes there is a slim chance.
this will improve your chances by a small margin. Remove the memory card, kill wcescomm.exe in task manager on your pc, turn off any firewall/AV.
Now this is the hard part. I dont own a G3 device so I'm not sure what rom to flash that would save your device. I'd suggest you get the latest rom from the company that shipped your device eg Dopod, Tmobile, Imate etc. If you have a rom that you use in times like this to rescue your device then flash it now.
Good Luck

peter petrelli said:
yes there is a slim chance.
this will improve your chances by a small margin. Remove the memory card, kill wcescomm.exe in task manager on your pc, turn off any firewall/AV.
Now this is the hard part. I dont own a G3 device so I'm not sure what rom to flash that would save your device. I'd suggest you get the latest rom from the company that shipped your device eg Dopod, Tmobile, Imate etc. If you have a rom that you use in times like this to rescue your device then flash it now.
Good Luck
Click to expand...
Click to collapse
wcescomm.exe is NOT showing in Task Mgr...I will try to flash anyway. I killed the firewall and the sd had been removed already. Any other suggestions??
EDIT
ruu error 260 update error
It cannot connect, please check to make sure it is cradled blah blah blah

Thats ok. I forgot that the previous flashing attempts would have killed it off anyway.

So I get ruu error 260
I have rebooted my pc, deleted any connections in active sync (leaving only guest)...
UgggH
It is NOT recognizing the usb
the usb port is as tight today as it was last night after my hubby repaired it...I'm backed to stumped
EDIT**
I had to reboot MDA, now I have lost the little corner usb...but I still have the quad bootscreen

This is progress at least, 1 hour ago we didnt even have bootloader mode. Perhaps you could try flashing another rom, but I think if error 260 keeps appearing then something is wrong with the USB socket.

somehow i lost bootloader again...
this is driving me insane!!!
am trying again, will update momentarily.
************EDIT*****************
Finally got it back into bootloader, but it will not read the usb. keep getting that stupid error message that it doesn't recognize the device, and if I try to flash it with a stock rom, I get error 260.
I have closed the wcescomm.exe
I have killed my firewall
I have rebooted my phone, my pc...everything a few times
I have deleted any connections in active sync
I have unticked allow usb in active sync
WHAT AM I MISSING???
The usb port on the phone does not feel loose again...could it have got fried somehow? I feel as if I can get the damned usb to be recognized, I can save my precious MDA.
Please...any other suggestions, brainstorms, whatever???
THANK YOU

I had a little problem with theloons kitchen doing the same thing to me last week where it would give me the 260 error. I'll upload a ROM flashing file for you to try. Probably the best thing to do right now would be to take the nk.nbf file from an official ROM and stick it in this file and then run the RUU in it. After that you should be ok again to try your luck at cooking with theloons kitchen again although you may want to wait 'til the kids are at school or something before you try it.

When in bootloader mode there's no charging circuit so you won't get any lights on top. The only way to see if USB is working is by watching that same word (USB) at the bottom of the screen.
Check the SD card method which was what saved me once from the 'freezing in splash-screen' problem: http://forum.xda-developers.com/showthread.php?t=276963
good luck

mestrini said:
When in bootloader mode there's no charging circuit so you won't get any lights on top. The only way to see if USB is working is by watching that same word (USB) at the bottom of the screen.
Check the SD card method which was what saved me once from the 'freezing in splash-screen' problem: http://forum.xda-developers.com/showthread.php?t=276963
good luck
Click to expand...
Click to collapse
absolutely right while in bootloader mode it wont charge,but to charge or verify status of usb connectivity,while in bootloader mode push power off button,it'll go in sleep mode but lights will show charging if usb cable is charging
usb cable might be charging but mini usb port of the phone has many connectors I think 9 connectors,I'm not sure,may be the connector for making connectivity relation with phone and pc is damaged.
try with another usb cable if possible,if the connectivity with usb is established than method in the link provided by 'mestrini' is a good option,good luck

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>

ATT Tilt Dropped on Floor, Dead ?

Hi,
I dropped my ATT tilt on floor 3 days back. Initially I was able to start-up mobile, but it used to reboot again giving me pop sound before rebooting. I also observed a '?' on battery status and noticed me of low battery before rebooting.
I recharged my battery using my bro's HTC. I also tried recharging with AA batteries. Yesterday the phone was completely dead. I was only able to see bootloader.
With the help of info available from different posts I tried to flash my mobile(-ATT_Tilt-RUU_Kaiser_CINGULAR_WWE_3.57.502.2_radio_sign_25.88.40.05_1.65.21.18_Ship). I was successful to upgrade my ROM.
However, once the mobile boots...it shows me Windows Mobile 6.1 with a notice " The device is clearing storage please wait..." and the red light blinking...then after few seconds it gives a pop sound and starts rebooting.
Here are the weird things I noticed.
-I was able to flash my mobile without HSPL.
-WDMC doesn't recognize my device.
-Whenever I connect my mobile to charge/USB it gets stuck at the ATT start up screen with orange light indicating battery is charging. I'm able to see my start up screen only if I disconnect from charger/USB and power on.
Now I'm not able to flash again. Help needed !
My device Info on boot loader :
KAIS1*0
SPL-3.56.0000
CPLD-8
I'm able to see USB on bootloader when I connect to USB.
Thanks in Advance !

Help Please

Hardware damage calls for a hardware solution
If the problem started since you dropped it on the floor then that indicates some physical damage to the device (perhaps internally where you cant see). No amount of ROM flashing or hard resetting will cure this, whats required is a visit to the HTC repair centre/knowledgable phone repair shop. They'll be able to inspect/test the device, come up with a solution and quote to fix it. There are many possibilities as to whats gone wrong and the only way to be sure is to have an expert check it out in person.

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