Ok, so first off, I upgraded to 6.1 from 6.0 a year ago. I am using SPL 2.40 and radio 3.27
I was looking at the 6.5 roms and thought maybe it was time to upgrade again. I tried the last 2 6.5 roms and found that after flashing my camera and speaker stopped working. So then thought I may as well down grade back to 6.1
I was using dcd 1.3.0 (I think) originally but then saw that the next stable version was 2.3.2 so decided to use that.
After flash all was good with the world. Camera ok, speaker ok, all good. about 24hrs later my phone shut down (with a fully charged battery). I tried to turn it on and nothing happened. Plugged in the wall and then the PC still nothing. I also tried to boot into the boot loader (power+Camera+reset) still nothing.
Am I out of luck? Can I get a service doc to trouble shoot myself? or do I now own a PPC paperweight?
Thanks for any help (I did try searching the forums but found nothing like this for the 6800)
Big mistake. That old of a dcd rom is probably 6.0. You might have messed your phone up good. Does it light up if you plug it in? If so what color? You need something like DCD 3.3.4.
Can you put your phone into bootloader?
No it literally will not power on at all. Boot loader or otherwise. Also no led when plugged in the wall or in the PC. I think it fried a chip or something. But it did work fine for about a day or a day and a half. As well when it shut down I wasn't even using it. It was in stand-by mode. If I could track down a service manual I may be able to trouble shoot the chip, but have already paid for one site with no luck and don't want to repeat that (could add up )
Pull the battery, make sure it's unplugged. Put the battery in. (You need to press power button for 1 second to turn it back on) See if any lights come on, if so press power + camera and hit reset, if it gets you to the Bootloader screen, you can just flash up to a newer rom.
If you had 6.1, you probably had a GPS enabled radio, and therefore can install any V3.x rom from DCD and be back up and running.
When you first power it on, it has some numbers in the bottom right corner, if they will show up, write them down and post them back here, from that we can determine which rom you need to install.
BTC
if you can get it into bootloader, i would flash a newer radio before anything else. youre doing some serious version jumping, but generally any custom rom you flash should be using radio 3.42.50. also, 3.2.5 or 3.2.6 are completely stable.
Nope, still not powering on... tried everything I could think of and some stuff I didn't. As far as firmware goes I was using 3.27.00 with SPL 2.40 Bootloader.
If I can't figure it out, I need to decide if I am going to buy out the last year of my contract, get it repaired (if possible), or buy a new one at full price (ouch).
After this phone nothing else will do for me LOL... I love my WMPPC!
I'd try charging the battery with another Titan or with a battery charger.
Another thing to check is whether you get a red LED light when you have the charger plugged in to the phone, but no battery installed.
Ok, so it seems that it is totally unrelated to the flashing process. I opened the phone today to see what I could see. A few weeks ago the vibrate stopped working and I figured that the motor burned out and didn't worry about it. Well it turns out that the little bit of glue that holds the motor in place gave out and it was moving around in the phone. It finally crossed a couple of terminals and shorted out the board. Thanks for the input guys. Got another Titan on the way to play with now
Related
The SX56 GSM/RADIO STACK BOOT ERROR is definitely a battery issue, and I
think all of these RSU upgrade workarounds fail to take this into account.
Here's my 2 day hell experience with my SX56, PW10B1 originally AT&T, bought
on Ebay and with the help of this forum, unlocked and flashed new rom
switched to T-mobile with no problems. I used this phone for 5 months with
this Romset, without any glitches whatsoever.
ROM 4.00.21 ENG 8/11/03
Radio 6.12
GSM 324e4
Saturday night I'm driving down the highway, talking on the phone, I get another call, switch over, tell em I'll call em right back, finish my original phone call, go to call the other caller back, and my screen is FROZEN. I pull over and do a reset (soft), no GSM or Radio stack. Phone hangs on boot screen. Only displays ROM# on hanging boot screen.
I get home, do a hard reset, wallaby bootloader 5.15 says GSM ERROR. I reflashed the rom from an SD backup I had saved, still no GSM or Radio stack, but It boots after waiting for 20 minutes. NO GSM, RADIO, OR IMEI# in system info.
The one thing that stood out is the fact that the bootloader had no GSM, so any upgrading of the stack RSU or otherwise seemed pointless, since the bootloader had no idea the phone was even a phone. But I tried those rsu upgrades and got to the 1% screen of death. After 4 or 5 attempts that proved useless, no matter what I installed, then deleted from the
windows/startup folder, IT JUST WOULDN'T WORK.
I was convinced that somehow the chip became physically corrupted, since at the bootloader level the phone was not aware of it's radio, gsm, or IMEI#.
I gave up after many many hours and called SIEMENS tech support monday morning.
I described the problem to them (GSM ERROR AT BOOT) and they told me that the GSM chip needed to be reflashed by them, that there was nothing I could do for the phone to fix it myself.
My phone's build date of 12/02 put it out of warranty, and since I bought it 2nd party (on EBAY) the repair would be handled by their out of warranty department. They gave me that phone number (it's a subcontractor, not SIEMENS that does the repair).
I called them and explained the problem, they told me that this repair would cost $US 215.00. I asked them if they had a special rate since so many people were having this identical problem, no sir 215 is the price. In order to get an RMA#, they wanted my credit card# so that they could authorize the funds (BEFORE RECEIVING AND DIAGNOSING THE PHONE). I told them to give me a day to think about it, and that I'd call back.
One thing I noticed during all of the booting/rebooting was the fact that the CHARGING light was dead. My battery had plenty of power, but the phone was reporting battery status "UNKNOWN". When I switched between cradle power or battery the indicator never changed, simply saying status "unknown".
I had an old nokia cell that I took apart when I broke the charging socket off of the circuit board. I opened the phone and with rubber bands, held the socket on the board and charged the battery with the phone out of it's case.
This got me thinking about the sx56 battery, and I had a brainstorm!
I did a google search for SX56 battery replacement and found
http://www.pdainternalbattery.com/siemensinstall.html
I took the phone apart (TORX #6) and removed the battery. with the battery out and the back off of the phone, I held in the rocker switch that checks if the back is on.
I connected the phone to my PC for power via USB, and it started right up!
The GSM and Radio stacks came back, and the charge light went from off to green!
I put the battery and back on the phone, rebooted and the battery charge light turned amber, the phone said charging. The IMEI # is back, and I put in a SIM and can make calls.
I bet a lot of people are having this battery issue, and when they lose that Radio stack, immediately try to upgrade it.
By removing the battery, my Stack AND IMEI came back, proving that it was never really gone in the 1st place.
I don't know about all of the STACK upgrading, but this worked for me.
Anyway siemens was going to charge US$215.00 to fix it,
and all they would do is open and close the case......
hello. Thanks for sharing. But in this case you just need to reset the battery hold and wait about 2 minutes then press it again. But most of our situations are the radio stack is need to flash. or problem with battery circuit. Anyhow, thanks.
should i?
Hey man!
I have the same problem.
I was upgrading the RSU and it froze. I did a soft reset and it hangs at 1% while installing the programme B again.
No RSU, No IMEI and no battery right now.
Let me know if I should try this. I would try anything now to bring my phone back to life....
My girlfriend is trying to call me and she can't She'll kill me!!!!
Hey!
I tried this and it worked.
XDA is back but still no RSU and no IMEI!!! The phone still is not working and it works only if the charger is attached and there is no light in LED.
Anything else?
I am desperate and would try anything now!
Cheers guys!
You help a lot!
hi. I think there is notthing we can do to fix this problem.(I have same problem). When the Radio Stack die it means the light indicator will not turn on. It turn red then no light appear. The only one thing we can do is to hope someone creates a radio stack on the SD card so we can fix it in the loading mode. There is no way we can upgrade the radio stack in the window if the radio stack dies.
Regards,
hoanghon
P.S. Someone please correct me if I am wrong.
I Fixed this EXACT problem. Re-Read my original post (top of thread)
GET RID OF ANY RSU UPGRADE FILES FROM THE \WINDOWS
AND WINDOWS\STARTUP BEFORE YOU DO ANY OF THIS.
I took the battery out of my phone, left the back off of phone. hooked it up to charging cable. There is a small switch in the phone that is held closed by the phone's back cover. HOLD this switch in, and power up your unit. The charging light turns green, and the GSM and RADIO #'s will display on boot.
SEND ME PM's if you still have trouble, and I'll try to help you further, or you can mail me your unit.
hi. when the radio stack is error. you can't do anything to fix the radio stack. even you change a new battery it wont help. Trust me. You can search for this problem on this site. re flash the radio stack in bootloading mode is one sollution. Second solution is to replace the chip.
or change the mainboard.
SX56 GSM ERROR, But....
Ok, I'm gonna type this once more, and again, this is what worked in MY situation, if it doesn't work for you, good luck trying to reflash the radio stack, you can't, and here's why.
My phone froze after handling a call-waiting phone call.
When I rebooted, the GSM and RSU and IMEI were gone.
Bootloader said GSM ERROR. You can't flash anything when the bootloader doesn't see the GSM, RStack, or IMEI.
Compare your home PC to your XDA, and follow the process.
Take your home PC, boot to the BIOS (BOOTLOADER) . Set the PRIMARY HD to "NONE" .
Reboot. Your PC will be dead, it will say insert system disk, (GSM ERROR) why? Your BIOS (IE BOOTLOADER) doesn't see your HD.
Now try to use software (IE SD REFLASH) to find the HD, you can't. Any work on the HD (GSM RADIO STACK) is impossible.
Try to upgrade software on a PC if the BIOS can't see the HD.
For whatever unknown reason, my phone (BOOTLOADER) lost it's ability to see the GSM IMEI and RADIO. From all of the talk about this design error, it is obvious that the power circuit is involved.
You are saying
hi. when the radio stack is error. you can't do anything to fix the radio stack. even you change a new battery it wont help. Trust me.
Click to expand...
Click to collapse
When I did my trick removing the battery from the loop, the GSM REAPPEARED in the BOOTLOADER. How could this happen if the chip was bad? The GSM Error appeared because of a fluke in the power circuit, not because of a chip error.
Resetting the circuit (Removing battery and powering up without it) allowed the BOOTLOADER to see the GSM and IMEI and RADIO. They were ALWAYS THERE, just not seen by the BOOTLOADER.
THE GSM ERROR IS A RESULT OF THE CHARGING CIRCUIT ERROR, NOT THE CAUSE OF IT
SIEMENS THEMSELVES told me there was nothing I could do to fix this problem, and that I NEEDED a NEW CHIP. They were ready to take my $215.00. My solution proves, that in my phone, the CHIP was never the problem, only a symptom, do you get it yet?
Im sure there are phones out there with bad chips on the board, maybe thats what you have, and why nothing works for you. Don't be so quick to say my way won't work, because it did work, it saved me a lot of money, and it will probably work for someone else, will you believe it then?
The number of people that face this issue leads me to believe it is a hardware error, in the charging circuit, not with the chip that holds GSM IMEI RS data.
You know, my phone works. You should fix yours (or have someone else do it for you), then call me, and we'll continue this debate there.
hi. Thanks for your post. but our situation is not yours. We killed the radio stack by upgrading the radio stack. Result dead radio stack. As I said, your situation is easy-just press the battery button and wait 60 seconds and re-press it again. The solution is solved. If the radio stack was easy to fix, we would never spend money to fix on it.
Best Regards,
Hoanghon.
P.S. I believe that you fix you pda phone. but it is not the same our case.
My brother brought me his O2 Prophet a couple of weeks ago because he said it randomly turned off. I assumed, obviusly, a faulty battery, and replaced it with a new one, fully charging it with an independant desktop charger before putting it in. Still the problem persisted.
I hence came here, and trawled through the xda bible, concluding that since the thing would turn off even by leaving it on a table and looking at it, it could very well be a software problem, as so many before me have had. No biggie, methinks - it's flashing time!
And here's where the phone decided it wanted to be a cute white paperweight: before it could finish flashing pdaviet, it turned off, voiding the process. Since, it's stuck in bootloader, and every time I try to flash (and I'm positive I'm doing it right), it will turn off, normally even before it reaches 50%. What could be the problem?
I've checked the connectors to see it they were dirty, and connectors 3 and 4 seemed slightly recessed, but I don't know if this is normal (they're very neatly recessed).
So, finally (I'm a long typer, sorry!) if anybody has any ideas, even maybe apparrently stupid ones, please post - my computer wiz reputation is at stake.
Try a different computer if you can, or even just a different USB port.
If that fails, re install active sync, get a different WM5 NVID ROM, Manually put the device into bootloader, disable connect through USB in active sync and then connect the device. Then run the RUU from the ROM you downloaded.
Thank for your reply l3v5y.
I tried all of your suggestions, but it still turns off all the time - I'm starting to think it really is a harware problem, but I can't figure out where.
Any other ideas come to mind?
Does it start up (and run WM5) properly? If yes, and it persists to reset, I would assume there is a faulty connection between the battery and the device. Check the battery connectors on the device to see if any are further depressed than others.
WM5 doesn't start at all - it's stuck in bootloader. The two middle connectors are slightly depressed compared to the other two - should I pull them out a bit?
I would suggest pulling the pins out slightly, but do not overdo it. Try a different WM5 ROM (an official one is probably best).
I know it may be silly but check if the soft reset button didn't stuck, maybe someone was pressing it too hard and that is causing problems
I have flashed the latest HTC update with Windows mobile 6.1 onto my T-mobile MDA touch plus. But I have a problem and I don't know if this is about the firmware, the phone or the battery.
I bought this phone recently (secondhand) and actually flashed this update directly, so I don't have experience with the phone how it came.
Right now, the battery doesn't last for a day without actually using it (even without a simcard inserted). It is clean of software, only flashed the firmware and that's all.
After a day, when battery is empty, the device won't turn on with the charger connected. Even when I keep the charger connected for a whole day. Then I try some things like unplugging the charger, remove/insert the battery, press reset button, connect/disconnect usb and it eventually turns on (I don't know what the real trick is). Battery is empty then, so it didn't charge at all...
Current firmware is Nike_HTC_NLD_2.09.404.1 with its default radio (1.65.28.25). Camera works.
Does this have to do with the software, hardware or do I have a 'almost-dead' battery?
I also like to try to flash the stock firmware, but it won't flash when I have run the sspl 1.16.jump executable on my mda. Or can I just flash the phone with the new stock 1.22 spl ?(fixed)
you need hardspl first ... try again!
I did try that preciously, but the problem was that the 1.16.jump executable booted up the bootflash menu without showing usb. But I did a second try now, and it worked
I am now running the default t-mobile firmware (but I don't get a t-mobile bootscreen.. so it's not a real shipped rom I think).
Battery is 95% now, let's see how long it takes to get empty again...
Battery is empty now, so this had nothing to do with the firmware.
I try to charge the mda with a different charger, because the one that I had was an aftermarket type.
I have another question. When I charge the phone, should the orange light in the speaker turn on? It stays off here...
When in charging mode, via charger or USB cable, the light will be orange, turning yellow once fully charged.
rling said:
When in charging mode, via charger or USB cable, the light will be orange, turning yellow once fully charged.
Click to expand...
Click to collapse
That doesn't happen.. It charges, but it doesn't show any light
Is there a way to check the battery instead of buying a new one ?
I have bought a new battery, but the problem persists
The last thing I want to try is flashing another or original radio. I have read that battery drain can be the result of having the wrong radio version. I hope this is the case.
My device is a niki200 and it is currently running Nike_HTC_NLD_2.09.404.1 with its default radio (1.65.28.25).
I'm unsure if a niki200 device needs a different radio than niki100's. Therefore I like to get a original T-Mobile MDA Touch Plus rom (Dutch/NLD) or a radio that is 100% compatible with the phone. Which radio do I need? And where can I get an original T-Mobile rom, or do I have to request it?
I hope the problem is in the radio, otherwise the hardware itself is faulty
Problem is fixed. It was a hardware issue. The keyboard lights and gsm/charge status leds didn't work at all. Only when I moved the display housing a little bit, I sometimes got these lights working. I have disassembled the phone, reconnected everything.. and it all works fine again . Battery is 95% after 16 hours standby! I'm happy again!
all nike can use the same radios ... only japan nikes use different radios!
I want to say thanks to tuti fruiti, I had the same problem with my touch dual, followed instructions as give, and everything is fine now.
Cheers
Tutti-frutti said:
Problem is fixed. It was a hardware issue. The keyboard lights and gsm/charge status leds didn't work at all. Only when I moved the display housing a little bit, I sometimes got these lights working. I have disassembled the phone, reconnected everything.. and it all works fine again . Battery is 95% after 16 hours standby! I'm happy again!
Click to expand...
Click to collapse
Yes; I flashed the ROM on my XV6800 (Verizon's Titan) to DCD 3.2.6, Radio 3.42.50 and ran the Verizon cab. The phone was mostly running fine for a few days (except for a few "normal" WM freezes).
Then my phone's battery recharging mechanism went crazy (as per this post). Until one morning I found that the phone wouldn't start anymore...
Removing the battery didn't wake it up. Soft- and hard-resets don't do anything. I even bought a new battery, hoping that it's just a battery issue or some mini-USB port issue. With the new OEM battery fully charged (with OEM charger), the phone still doesn't want to start.
When I plugged in the USB cable to the device today, the RED (right) LED lighted up for a few seconds; then disappeared. I couldn't get the red LED to light up again on subsequent tries.
Unfortunately, I bought this phone second hand and noticed that the manufacturer's warranty expired just two months ago.
Is my phone really dead? Anything else I can try to revive it?
Any guess on how the Verizon technician would handle this if I were to bring the dead phone to a Verizon store?
PeekPoke said:
Yes; I flashed the ROM on my XV6800 (Verizon's Titan) to DCD 3.2.6, Radio 3.42.50 and ran the Verizon cab. The phone was mostly running fine for a few days (except for a few "normal" WM freezes).
Then my phone's battery recharging mechanism went crazy (as per this post). Until one morning I found that the phone wouldn't start anymore...
Removing the battery didn't wake it up. Soft- and hard-resets don't do anything. I even bought a new battery, hoping that it's just a battery issue or some mini-USB port issue. With the new OEM battery fully charged (with OEM charger), the phone still doesn't want to start.
When I plugged in the USB cable to the device today, the RED (right) LED lighted up for a few seconds; then disappeared. I couldn't get the red LED to light up again on subsequent tries.
Unfortunately, I bought this phone second hand and noticed that the manufacturer's warranty expired just two months ago.
Is my phone really dead? Anything else I can try to revive it?
Any guess on how the Verizon technician would handle this if I were to bring the dead phone to a Verizon store?
Click to expand...
Click to collapse
I had the exact same thing happen on my Vogue. It was because I hosed the flash. Oooops.... I did recover very easily however. This may or may not work for you so good luck in advance.
Try to put the phone in "boot loader" mode by pressing camera and power at the same time then use your stylus to press the resert hole at the bottom. This will bring you to the infamous try color screen. Just flash an official OS ROM back to the phone and start all over.
If it does not go to boot loader then I would be concerned.
Thanks. Can't get to bootloader. Sigh...
PeekPoke said:
Thanks. Can't get to bootloader. Sigh...
Click to expand...
Click to collapse
that happen to me your phone is in a state of download mode its blank i still have not found a fox for that yet i still got a brand new moguel stilling here
PeekPoke said:
Thanks. Can't get to bootloader. Sigh...
Click to expand...
Click to collapse
Sorry to hear. I would continue to search. Do you have a warranty on it? If so just call them and say it wont power up. No need to volounteer why. They will replace it after they do things like have you remove the battery, etc.
Good luck to you.
mrchezzy said:
that happen to me your phone is in a state of download mode its blank i still have not found a fox for that yet i still got a brand new moguel stilling here
Click to expand...
Click to collapse
Let me know if you find a fix. I heard that there is not one available on these boards. If you find please let us know.
PeekPoke said:
Unfortunately, I bought this phone second hand and noticed that the manufacturer's warranty expired just two months ago.
Click to expand...
Click to collapse
Double check that.
Didn't the xv6800 get released in November of 2007? Hard for the one year warrant for be expired by 2 months.
Sure sounds like you have bad hardware and you aren't likely to fix it.
This last weekend, my TMOUS HD2 started having problems charging. With the phone on, it will remain at the same charge level. With the screen off, it might trickle up a few percentage points over time, but nowhere near what it used to. If I charge while the phone is off I can get it fully charged.
What scares me is that the phone gets noticeably hotter on the back near the bottom while plugged in and the phone is on. (The battery does not get warm, the actual phone get warm.)
After the weekend I plugged it in to my computer and it would not get recognized. The usual prompt for Sync/Drive/Internet Sharing does not come up and the computer does not react like a USB device was connected. The charging light comes on, and the screen shows its charging, but the battery does not charge unless I turn off the phone.
I have tried several different cables, charger and computers with the same results. I even hard reset the phone. I have flashed my phone many times and I am currently using Energy Rom from July 7. I have also been testing the various Android builds.
My question is if this could be caused by software somehow, or is this most likely a hardware failure. I know that I have not hit nor bent the USB connector, just normal plug-in/unplug for normal usage. The plug is not loose, and wiggling it somewhat does not change anything.
Any other troubleshooting tips before I start flashing back to stock for warranty repair?
I put the phone into bootloader tricolor screen, then connected the USB. Still no reaction on computer nor on device. Looks like this is a hardware issue. If I cant connect via USB to a computer, will I be able to revert back to stock bootloader and ROM via SD Card?
Has anyone else have their USB port just go bad with normal use?
Try All Settings--->Conections--->Usb To PC--->UNCHECK Enable faster syncronization data...
nonpaq said:
This last weekend, my TMOUS HD2 started having problems charging. With the phone on, it will remain at the same charge level. With the screen off, it might trickle up a few percentage points over time, but nowhere near what it used to. If I charge while the phone is off I can get it fully charged.
Click to expand...
Click to collapse
Hi,
I think this is a solution for your problem:
(manila) settings tab -> menu -> all settings -> system -> power -> battery
Uncheck: "when phone is on, do not charge the battery when connected to a PC" checkbox.
I've just recently had the same problem myself..
Sorry to be the bearer of bad news but you will probably find it is a hardware fault.
Not long ago I got home, plugged my phone in to charge and left it, thought nothing of it.. Came back 10min later to find it said it was 100% charged (from 15% left) thought it charged quick but thought nothing of it.
Sat down that night to test some more mods i had downloaded at work, only to find my HP netbook wouldn't see it. Tested on 2 different laptops, a PS3, 2 difrent chargers (one original,one 3rd party) nothing...
Sent it back through O2 store as it was still covered.
When it came back the report stated it had a board malfunction and that my IME had changed.
Sounds like you might have the same problem...
I think I traced it back to the office, I had to leave in a rush for a bus and unplugged it (from xp) without safely removing hardware.
(god i hope O2's tech guys don't recognize me here fessing )
I think it fried the connection.
I will point out that since they have returned my baby, she ain't working soo good. They updated my Rom ext but my GPS hasn't picked up a satellite since.
So back she goes....... Sigh.....
Hope this helps as I don't normally venture over in to the "Q&A" section of XDA but I'll keep an eye on this thread.
Good luck with your phone buddy, I know how it feels not to have it.. Limb missing....
DanijasDub and dzukela, thanks for the troubleshooting tips. tried both, but neither applied. I already had "Do Not Charge when connected..." unchecked, and unchecking "faster sync" didn't help.
I think i have to agree with snowblind2142 on it being bad hardware. The fact that the computer would not recognize the USB connection while the HD2 was in Tri-color mode convinced me that at least part of the USB components may be busted (also the overheating near the connector.) I'm going to need to try a warranty exchange.
Why is it that all these phone manufacturers had to standardize on such a flimsy connector?
They're just cheapskates..
Do anything to save a buck, just one of those things..
Hope your exchange/repair goes well, i was bricking it as i had a custom rom on for a while. Had to revert to stock rom before returning it.
What did make me laugh, when i went in to enquire how their return process works, I explained what was wrong with my phone, so he asked to look at it....
My heart sank when I realized... OH NO!! IM STILL ROCKING MY DUSK THEME!!!
So he's like WTF?!? smiled and told him no different to downloading a game or app..
No mention of it on the problem description when i got the receipt back
PHEW! close one, so make sure its same as you got it, I've heard some horror stories....
Good luck!
Speaking of that.....
What's the best way to revert back to stock.... Revert HSPL first or Rom to stock. I can't affort to brick it at this stage.
Plus, I need to so it all from SDCard, since my USB won't connect.
nonpaq said:
Speaking of that.....
What's the best way to revert back to stock.... Revert HSPL first or Rom to stock. I can't affort to brick it at this stage.
Plus, I need to so it all from SDCard, since my USB won't connect.
Click to expand...
Click to collapse
Well, all i could do was Rom to stock as didn't think you could revert HSPL by SDCard. Seemed to be fine. On the plus side its really easy to do via SDCard.
Sorry, really cant remember where i went through the walk through but if you Google it I'm sure you'll find it. My advice is be careful, I managed to borrow a stand alone battery charger so i still managed to charge mine as you need over 50% battery to flash or you WILL brick it.
I must admit I was a bit laid back about it at the time but I guess they might of picked up on it... I'm keeping mine stock rom till the bug's are ironed out.
Hope this helps..
Sad to hear that, hope you can exchange the device.
If you extract the leoimg.nbh from the official ROM and put it on the SD card root, then go into bootloader, it should ovewrite ROM, Radio and HSPL (at least it did for me).
So how do I extract the NBH from the official stock rom? Its an EXE file, which is supposed to self extract the files before flashing. The problem is that it first checks the phone connected by USB, which unfortunately I can't connect. Does anyone know where I can get the NBH file only from a stock ROM (TMOUSA) for flashing via SD Card?
Just download the offical ROM from the HTC site and use winrar to extract.
Never mind... I figured it out.
The Installshield for Stock RUU extracts the contents to the temp directory at the point where it asks to "Connect phone to USB". I just copied the file
"RUU_signed.nbh" to another directory, then renamed to LEOIMG.nbh. I am now waiting for my phone to charge so I can flash via SD Card.
Sorry buddy, have been at work..
Seems like youre gettiting there. Hope all goes well!
Good luck to you!
Success!!
To add closure to my saga, and reference for future searchers....
I was able to flash from SD card using the extracted NBH from the official TMOUSA 2.13 Rom update, renamed to LEOIMG.nbh.
The official NBH changes everything back to stock.... the ROM, Radio, SPL, and boot wallpapers (Oh how I hated the TMO stick together animated startup.)
I called for service. Once the rep heard that the phone was overheating when plugged in she offered the warranty exchange. Now waiting for it in the mail.
I hear that warranty exchanges are actually refurbished units. I hope I get a good one. I also now know how fragile the micro-usb and the charging electronics are. I dont want to do another exchange, so looks like I have to be careful when plugging in for sync or charge.