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.
Related
I bought my xda in working condition a few days ago from somebody I know. It's a month old, and worked fine for a day. I left it on while I went out and when I got back it was off. I assumed the batteries were dead and placed it in the charger.
When I got back, it was still dead. It wouldn't turn on. I have not tried to flash or tamper with my device in any way...
Here's what i've discovered so far:
- Soft and hard resets do nothing.
- When in the cradle, the charge lights do not come on.
- Bootlogger works, so the screen is alright and there is power to the device.
- I don't quite understand the stylus in the sim card issue, and how it damages the device. Since it's been broken, I have put the stylus in and pressed down the switch (I was told to and even the woman in the O2 shop did it when i took it in! lol). But as far as I can tell the reason you're not meant to is because you can break the switch - however the phone will only go into bootlogger mode with the switch depressed (the sim card door closed) so I assume that means I haven't broken the switch in any way. Also, I didn't touch the switch before this trouble started.
- I can connect with my device via activesync and browse the windows folder, etc.
So as far as I can tell - it isn't the sim card slot switch, it isn't the screen, it isn't the cradle, it isn't the battery, and there is no problem as far as connecting with my computer.
But my device still won't turn on when I press the on/off switch and hard and soft resets have no effect.
Please help me/give me suggestions/tell me if it's truly french connectioned so i can go batter the guy I got it from for my money.
This phone cost me 2 months wages and I waited forever and drove 600 miles to get it. And it stopped working after a day. It's proper depressing lol.
Oh alos, if the phone is fc'd, will the factory be able to repair it for me if I pay (i'm not sure I have the receipt for guarantee). If anyone knows, thanks.
Thanks a lot in advance;
Mat.
i don't understand how you can browse the windows folder via active sync if you cannot turn it on.
have you tried a different sim card. ie was your 'friend' using it on o2 or something different.
the switch beside the sim card slot is a detector ie if the door is open - no power if the door is closed - power. possibly if the switch is broken - no power.
as to a factory repair - pass. it depends on the damage.
ian
cheers - but the switch doesn't seem to be broken - because i can boot into bootlogger mode with the door shut, but not with it open. which suggests to me that the switch is alive and well. i've no idea what's wrong with it. gonna have to be a factory repair unless flashing the rom from bootlogger mode might help... that's the only thing i can see might be wrong with it.
There's no sim card in it, i haven't bought one for it yet. I don't know what network he used it on, but the phone came from europe.
I can browse the folder via activesync on my pc - when i go into the connect mode on bootlogger.
MaT.
mr_mat_cool said:
There's no sim card in it, i haven't bought one for it yet. I don't know what network he used it on, but the phone came from europe.MaT.
Click to expand...
Click to collapse
this is the answer to your problem, no sim card no power, if the 'phone is unblocked then any will do if not try any anyway, you never know.
ian
phone always worked before without a sim card. i'll try it though, thanks.
mat.
no mate, still not working with a sim card - the phone is unlocked..
:-( thanks anyway;
mat.
What is being displayed on the screen during your resets soft or hard (details please)?
You say the bootloader is working, Right! So do us a favor and check your GSM and report what it says.
To get to the GSM settings "while in bootloader mode" just press the Calender button.
Looking forward to your reply,
sorry, i'm slightly technically challenged, but i'm getting there.
if i take the device from its cradle and perform a soft reset, the green and red hang up/answer lights come on together for a few seconds and then go off. nothing else happens and i cannot turn on the device. if i try to, nothing happens at all.
If I perform a hard reset, aboslutely nothing at all happens except that I have to put the device back into its cradle and take it out again if i want to do a soft reset. If i do a soft reset straight after a hard reset, it does nothing (the lights don't even come on).
if i load bootloader, it says "GSM ERROR" where it says "GSM OK". I assume this is because I have no sim card in my device.
Well, i'm finding out things as I write -it seems to behave differently every time. I put it in bootloader mode to find out my gsm settings, and placed it in the cradle whilst it was loading... and it said "GSM OK". I soft resetted, the lights came on for a couple seconds and i'm back to where i started.
Confused!! Thanks for all your help though
mat.
note: for some reason, after taking the device from its cradle or placing it in, after a period of about a minute, the device chimes. i've no idea why or what it's trying to tell me. (the red and green hang up/call lights also come on for a second when this happens)
alright, update...
if i go into bootloader mode, and at the screen where it says "wait" i put the device into the cradle, and take it straight out again, the device says "GSM OK" (maybe it confuses it.)
Otherwise, the device says "GSM ERROR".
Mat
i managed to get onto the flash menu, and copy "BOOT TO SD", and then i went into bootloader mode and downloaded it from the sd card and it said succesful, cold reset to complete...
my device is now in the cradle, the buttons are doing nothing when pressed and the call.hangup lights are permanently on.
if i press the calendar button, a menu comes up saying...
UTLITIES
===GSM OFF===
DEBUG/CALI.
GSM TURN ON
GSM TURN OFF
GSM RESET
GSM 900
GSM 1900
GSM 900 / 1800
GSM RECAL
GSM NORMAL
this is really confusing me. i think i need to take this thing to O2.
yes? no?
thanks again;
Mat.
"GSM Error" seems to indicate there's something trashed with your radio stack. I had this same problem this week with a failed update to the T-Mobile 6.24 radio stack. Even with no SIM card inserted, you should still get "GSM OK". The only time I saw "GSM ERROR" was while the radio stack was hosed.
Try this: First, take out your SIM card, and in the menu you describe above, choose TURN GSM OFF. Then, reflash the ROM via the SD/bootloader method (look for the thread in the ROM Updates forum for help). I recommend the 4.00.05 ROM (Windows Mobile 2003 from 02). Once that's done, you need to get it to boot into the OS. With a corrupt radio stack, this can take 15-20 minutes or more. Do a soft reset, then let it sit for at least 30 minutes or so, and see if it boots into the OS.
Once you are in the OS, you should be able to connect via activesync, and re-flash your radio stack. I don't know what carrier you're on, but I'd suggest getting the latest radio stack update for your carrier's network, and not using a radio stack for another network.
It's a long shot, but I think if you can successfully re-flash your radio stack, you might be back in business.
Good luck!
JoshB
you are god mate :wink: .
First thing i'm gonna try is squaling like a girl for somebody else (O2 or an independant company) to fix it for me. Failing that, i'll try your method and anything else anybody suggests... Failing that i'll tell people it's some kind of space age weapon and hold up a bank for the money for a new one :lol:
here's what technical support said:
"It doesn't sound like anything I've come across before in the past. What I would suggest is for you to call the XDA warranty line anyway on the off chance that they can give you some advice."
Thanks a lot;
Mat.
NEWSFLASH! Took my phone from the cradle, put it back in and the orange charger light came on... This is weird as i've done nothing to it. It seems to be recovering bit by bit as if it got wet and is drying out or something... but it didn't get wet. I hope this helps somebody, someone else must be having the same problem. I read about one other guy who's phone has gone tits up, and even though his problem is different from mine, it seemed to be caused by the same thing - just leaving the phone on until the batteries died.
Mat.
aaaannnndd it's gone again. no charging light. it's weird, like my phone just decided it didn't wanna work for me any more and stopped.
i'll take it to get it repaired, see what they say. if not, it'll make a nice paperweight or maybe i can flog it to some blind kid
Mat.
Hello XDA-Users....
I've got a little problem with my xda-device.
It's just doing not much. If i attach the device to the cradle. The system turned on and is beginning to start the ROM (I see the T-Mobile screen). I-ve got the hint that the installed ROM is 3.13. Radiostack and Protocol is empty. -> should be then GSM-Error in the bootloader.
After all this messages i've got an short "pling" (beep) of the device, and it all begins from starting....
I can not enter bootloader (nothing happens) and the battery won't be charged..... (There is no light)
I've checked already the fuse of the device. Looks good. What else do i have for possibilities to get the device working again? That the GSM-Part does not work is not important. I need the device just for testing and installing new software to include in the kitchen. So the phone function is not needed.
The battery semms to work, I still got some Volt if i check it with the multimeter.
Anyone have some tips for me?
Stefan
Have you looked at the connector on the base of the xda under magnification, it may be a bent pin on that or on the cradle that is preventing charging.
Connector looks good.
If i conect it, the device is getting power.
When i disconnect the cable / cradle the device stops doing anything and goes off.
If i do an hard reset with connected USB-cable, nothing happens.
If i try enter bootloader the display is flashing until i refuse the power button. Than endless "booting" starts again...
Stefan
It does sound like a low power situation, I think the gsm will not switch in unless there is sufficient power. If you need a battery I have one here that was removed from an xda a few months ago but should be fine, send me your address if you need it and I will give it to you.
That previous post was from me. Also have you checked that you dont have a stuck button.?
The buttons looks fine. tested them already. So that isn't the fault *damn*
If you can send me the battery, that would be very nice.
Maybe it's really the probelm. But i think, if the battery is in bad condition, there should be anway going a light on to show "going to load tthe battery".....
STefan
Stefan
If a hard reset doesn't solve the problem, then try this.
DO A FULL BACKUP FIRST!!!
Open the XDA, and remove the battery
(together with whatever circuit is attached)
Put the battery in the freezer for about 20 minutes.
Remove it, and reinstall it.
Now put it back in the cradle and it should charge.
Then to a restpore from the backup.
This just happened to me and it brought my XDA back to life.
A chemical process happens to rechargeable batteries that
prevents them from receiving a charge. Apparently freezing
the battery for a very short time (20 minutes) corrects this.
Try this at your own risk, but I did it to my only XDA and it is working fine
for about a week now. Otherwise I would have had to scrap my XDA.
Let me know how it works for you.
Joe
Joe_PDA said:
Stefan
If a hard reset doesn't solve the problem, then try this.
DO A FULL BACKUP FIRST!!!
Click to expand...
Click to collapse
--> Not able. Device doesn´t start.....
Joe_PDA said:
Open the XDA, and remove the battery
(together with whatever circuit is attached)
Put the battery in the freezer for about 20 minutes.
Remove it, and reinstall it.
Click to expand...
Click to collapse
--> done.....
Joe_PDA said:
Now put it back in the cradle and it should charge.
Then to a restpore from the backup.
This just happened to me and it brought my XDA back to life.
A chemical process happens to rechargeable batteries that
prevents them from receiving a charge. Apparently freezing
the battery for a very short time (20 minutes) corrects this.
Try this at your own risk, but I did it to my only XDA and it is working fine
for about a week now. Otherwise I would have had to scrap my XDA.
Let me know how it works for you.
Joe
Click to expand...
Click to collapse
Thx for the tip. Tried it, but didn´t work for me....
Stefan
Stefan
Sorry to hear it didn't work.
Its been over a week and mine seems to be holding up.
I'd have to guess you battery is completely dead.
i have the same problem
you seem to be having the same problem as me m8 do you have no radio
or information on the radio task bar.
my unit keeps on re-starting the same as yours and i cant access setup even after hard reset. i attempt to charge the unit and the pwr light comes on briefly then goes out after approx 10 secs the unit then starts itself up and as mentioned before turns itself on and off randomly.
(i have no software for this unit just the unit and charger no memory card)
i am new to pda's do i need any softwares if i get it working?
any feedback appreciated
Hi all,
I've successfully recovered from the dreaded GSM error and have been using my resurrected wallaby for about 3 months now (since the gsm error). I have a WM2003SE, 4.21RSU and a PW10A1 device. Everything worked great until I've experienced this "weird" problem.
Problems:
1. Suddenly becomes "slow", delayed response to stylus taps
2. Backlight becomes "turned off"
3. If I do a soft reset (and hard reset) I end up on the bootscreen with "no radio" again (apparently gsm error)
4. All symptoms of a gsm error are evident here (can't charge and sync)
5. When I am able to revive my device and charge it; battery status remains at "charging" state or "unknown" even though i've already removed it from the charger
6. I've charged last night; when I woke up (after 7hrs) it is still in charging state
What's weird:
1. If I do a series of soft and hard resets (even entering bootloader); this gets my Wallaby back "surprisingly" with the radio on again
Questions:
1. Is it possible for the device not to detect a working RSU even though it is still there? I've done a number of RSU upgrades (all 4.21) still the problem persists
2. Can this be caused by a dying battery? I think I have a 2.5 year old battery and I don't know how to check if it is still ok (using spb plus shows good battery life though but when you run battery test in bootloader diagnostics; it indicates a charging error)
3. Can the rocker switch in the sim door be the culprit? I have a broken sim door that is just being held up by a scotch tape in place
I have read through the forum and reading through gets me more confused. I want to exhaust all efforts first before buying a new battery (which may not solve the problem). Sorry for the long post; I just want to give all the details in anticipation for a detailed solution. Thanks!
Problem solved! (I hope)
Before tinkering with the hardware and buying a new battery; I reflashed my RSU for the nth time. What I did differently this time was to remove the AC power while doing the RSU upgrade (because RSU 4.21 exe prompted me to do so, first time it happened). After this, I was able to soft and hard reset without losing my radio.
Second, I checked my OS (WM2003SE) and under device information/hardware, my data bus was set to 0. I think I corrupted my OS. Also reading from the forum re: WM2003SE bugs, I downgraded to WM2003 4.01.12 (the most stable rom so far accdg to some posts). Now my Wallaby is up and running again for 2 days without glitches. No hanging, freezing, losing backlight and signal.
I also did not re-install SPB Pocket Plus 3 thinking this causes conflict re: battery state. Saw some posts having problems with SPB applications.
Well, I still got the 2.5 year old battery (charging and working fine right now) and the broken sim door. :lol: Saved a few bucks instead of buying a new battery. Thanks to the forum, lots of useful information. Just have to piece them all together. Nonetheless all my problems with my Wallaby were successfully resolved (and hoping I don't encounter them anymore!)
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
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