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.
Dear Gurus ...
I need help. During the upgrading process, the connection was disconnected and my XDAII is currently not showing any sign of life.
I ran through the forum, and tries a lot of stuff:
1) try to reset it to bootloader (pwr+joy+reset) - nothing
2) change USB port - nothing
3) setting in MsActiveSync - nothing
There is no display on the screen right now. Even if I put it in to charge there is nothing, no flashing blue led etc ... just dead ....
One thing I noticed is that after removing the battery, and putting it into the cradle, there is a red led light up.
Currently I ran out of options and can only think off taking out the battery for the XDAII to drain completely (not sure if this could help me get into the bootloader mode).
Any one out there who has any bright ideas? Pls help as I am desperate to fix my XDAII .... thanks ....
alvinlim28 said:
Dear Gurus ...
I need help. During the upgrading process, the connection was disconnected and my XDAII is currently not showing any sign of life.
I ran through the forum, and tries a lot of stuff:
1) try to reset it to bootloader (pwr+joy+reset) - nothing
2) change USB port - nothing
3) setting in MsActiveSync - nothing
There is no display on the screen right now. Even if I put it in to charge there is nothing, no flashing blue led etc ... just dead ....
One thing I noticed is that after removing the battery, and putting it into the cradle, there is a red led light up.
Currently I ran out of options and can only think off taking out the battery for the XDAII to drain completely (not sure if this could help me get into the bootloader mode).
Any one out there who has any bright ideas? Pls help as I am desperate to fix my XDAII .... thanks ....
Click to expand...
Click to collapse
I had the same problem but I didn't loose hope. I kept on resetting it until I was able to get into the bootloader mode. It was black with some writings "SERIAL 1.06". When I put it back on cradle, Serial changed into USB 1.06. Tried to do the upgrade over and over again but didn't work. I put AC Adapter to my cradle and hard reset my unit, put back to the cradle, started the upgrade again and it worked. :wink:
twinkle said:
I had the same problem but I didn't loose hope. I kept on resetting it until I was able to get into the bootloader mode. It was black with some writings "SERIAL 1.06". When I put it back on cradle, Serial changed into USB 1.06. Tried to do the upgrade over and over again but didn't work. I put AC Adapter to my cradle and hard reset my unit, put back to the cradle, started the upgrade again and it worked. :wink:
Click to expand...
Click to collapse
Thanks!! I tried hard reset after 30mins with the battery out, nothing works. After I out in the AC adapter for 5 mins and tried a couple of times of hard reset, the screen came out with "Serial" !!!
YAHOOooo ... now I'm in the middle of uploading the ROM back ... thanks twinkle .... that just saved my day ..
alvinlim28 said:
twinkle said:
Thanks!! I tried hard reset after 30mins with the battery out, nothing works. After I out in the AC adapter for 5 mins and tried a couple of times of hard reset, the screen came out with "Serial" !!!
YAHOOooo ... now I'm in the middle of uploading the ROM back ... thanks twinkle .... that just saved my day ..
Click to expand...
Click to collapse
No problem... have fun! 8)
Click to expand...
Click to collapse
plz give me te steps coz i had the same problem, what do i have to do???!!
red LED when plug it to carger without battery........... plz
Same problem
@NightmarE
I have exactly the same problem!
If you find solution please PM
So many people have their XDA II gone dead while upgrading to the second edition rom. What went wrong during the process ?
adad said:
So many people have their XDA II gone dead while upgrading to the second edition rom. What went wrong during the process ?
Click to expand...
Click to collapse
There are several Golden Rules when upgrading - not just to SE, but any upgrade.
Always make sure the cradle is attached directly to a USB port on the PC and not through a hub.
Always make sure the power supply is connected to the cradle.
Disable USB in Activesync connection settings.
Disable any screensavers
If an error does occur, putting your device into bootloader mode and restarting the upgrade often proceeds OK.
Bootloader mode can be a little tricky to obtain as the multi-directional button has to be pressed directly down in the middle - not tilted up, tilted down, tilted left or tilted right, at the same time as pressing the power button and the reset switch.
It is very easy to assume bootloader is not working when it may just take several attempts before you get it right.
adad said:
So many people have their XDA II gone dead while upgrading to the second edition rom. What went wrong during the process ?
Click to expand...
Click to collapse
My qtek2020 dead because it's my mistake I upgrade it to SE correctly but with Chinese Version and before DCS post his ROM when I saw it's working better than my PDA2K I try to flash my qtek2020 with the PDA2K ROM ( I make some HEX editing ) but with no luck my qtek2020 is totally dead
Any body have solution !
How I recover from my dead XDA II ..
I have to agree with DCS that those are the rules and you need to follow them properly. It's not the ROM that's having the problem but the procedure needs to be followed.
In my case I didn't have the Sync cable properly connected (I bought a new sync cable & I didn't use the cradle) to upgrade the XDAII (duh!).. and I paid the price of having my heart droped on the floor ..
My nightmare started when the cable came loose halfway through the upgrade, so the XDA kind of "hung" and when I tried to reset it, it refuse to show any signs. Do a small test. My guess is as long as you take out the battery, put the XDA II into the charger (without a battery), and the red light comes on, that's a good sign.
For those who is stuck in this situation try this steps:
1) Remove the main battery
2) Leave it out for at least 30mins (to drain the backup battery)
3) Go make your self a coffee or watch TV (time flies faster than staring at your XDAII)
4) Put the battery back (at this stage it still won't work)
5) Put the XDAII into the AC Charger (give it a good 5mins charge)
6) Then keep doing the hard reset (just don't give up, it's like doing CPR, your XDAII will show "Serial 1.06" after a good hard resets ...)
Those steps above did work for my XDAII .... and it should work for most cases as I believe when we upgrade (the ROM) we don't touch the bootloader. Sometimes when we screw up, the XDAII got "hung" and it needs a good "cold boot". Taking the battery out won't help because the backup battery is still in. After a good "cold boot" the XDAII will boot into the bootloader and you can resume your upgrade ;-)
NOTE : Do keep your fingers cross through out the entire process.
PS: Thanks to DCS, Twinkle, mamaich and many others who contributed to this fine forum ... Long live the XDA I, II, IIs, III .... beyond ....
How to upgrade my BOOOTLOADER VERSION (it shows USB 1.01)
Is there a way to change my bootloader version from USB 1.01 to 1.06? I'm currently using T-Mobile MDA-II.
Thanks beforehand!
I have a big problem: this summer i dropped my MDA2 on a concrete floor and i broke the power button so I cant make anything but soft reset, or to remove the battery for 30 min for hard reset.
Re: How I recover from my dead XDA II ..
alvinlim28 said:
I have to agree with DCS that those are the rules and you need to follow them properly. It's not the ROM that's having the problem but the procedure needs to be followed.
In my case I didn't have the Sync cable properly connected (I bought a new sync cable & I didn't use the cradle) to upgrade the XDAII (duh!).. and I paid the price of having my heart droped on the floor ..
My nightmare started when the cable came loose halfway through the upgrade, so the XDA kind of "hung" and when I tried to reset it, it refuse to show any signs. Do a small test. My guess is as long as you take out the battery, put the XDA II into the charger (without a battery), and the red light comes on, that's a good sign.
For those who is stuck in this situation try this steps:
1) Remove the main battery
2) Leave it out for at least 30mins (to drain the backup battery)
3) Go make your self a coffee or watch TV (time flies faster than staring at your XDAII)
4) Put the battery back (at this stage it still won't work)
5) Put the XDAII into the AC Charger (give it a good 5mins charge)
6) Then keep doing the hard reset (just don't give up, it's like doing CPR, your XDAII will show "Serial 1.06" after a good hard resets ...)
Those steps above did work for my XDAII .... and it should work for most cases as I believe when we upgrade (the ROM) we don't touch the bootloader. Sometimes when we screw up, the XDAII got "hung" and it needs a good "cold boot". Taking the battery out won't help because the backup battery is still in. After a good "cold boot" the XDAII will boot into the bootloader and you can resume your upgrade ;-)
NOTE : Do keep your fingers cross through out the entire process.
PS: Thanks to DCS, Twinkle, mamaich and many others who contributed to this fine forum ... Long live the XDA I, II, IIs, III .... beyond ....
Click to expand...
Click to collapse
I'm trying and trying to hard reset it I can't see the bootloader, I discharged the backup batt already. Can you help here or is there any other suggestion?
Ps: If I remove the battery and plug the Ac.Adpt I can see here the red light , but if I put back the battery there won't be red light , is that normal ?
Bum pp
Sanity saved
Thanx to dcs i was able to get my device working again.
During upgrade (wich was also possible due to time and effort by DCS) my laptop went into standby for unknown reason.
So my xda got stuck in T-Mobile bootscreen
It was this thread and especially the posting by dcs wich saved my ass (and xda)
for i did not know about the reset with third button to get into bootloader.
Now i finally upgraded to 2003SE.
Thanx DCS!!
hello ,
i have the same problem.. somebody can help me or us??
thanks !!
qtek 2020 dead
i tried upgrading the 2020 to the diamond v1.2 but in the middle of it, the pc based application said that it isn't designed for my version of the phone and now i cant get out of the bootloader mode can any1 help me with it i have the original 1.66 rom from the qtek site but the problem is that it too requires activesync to be started initially ... how do i get outta this mess cuz the hemaupdate and the update utility i got from the qtek site requires the phone to be synchronized using activesync first... can any1 help me with it i need help urgently ....
upup... if somebody can help us ..
Re: How I recover from my dead XDA II ..
alvinlim28 said:
I have to agree with DCS that those are the rules and you need to follow them properly. It's not the ROM that's having the problem but the procedure needs to be followed.
In my case I didn't have the Sync cable properly connected (I bought a new sync cable & I didn't use the cradle) to upgrade the XDAII (duh!).. and I paid the price of having my heart droped on the floor ..
My nightmare started when the cable came loose halfway through the upgrade, so the XDA kind of "hung" and when I tried to reset it, it refuse to show any signs. Do a small test. My guess is as long as you take out the battery, put the XDA II into the charger (without a battery), and the red light comes on, that's a good sign.
For those who is stuck in this situation try this steps:
1) Remove the main battery
2) Leave it out for at least 30mins (to drain the backup battery)
3) Go make your self a coffee or watch TV (time flies faster than staring at your XDAII)
4) Put the battery back (at this stage it still won't work)
5) Put the XDAII into the AC Charger (give it a good 5mins charge)
6) Then keep doing the hard reset (just don't give up, it's like doing CPR, your XDAII will show "Serial 1.06" after a good hard resets ...)
Those steps above did work for my XDAII .... and it should work for most cases as I believe when we upgrade (the ROM) we don't touch the bootloader. Sometimes when we screw up, the XDAII got "hung" and it needs a good "cold boot". Taking the battery out won't help because the backup battery is still in. After a good "cold boot" the XDAII will boot into the bootloader and you can resume your upgrade ;-)
NOTE : Do keep your fingers cross through out the entire process.
PS: Thanks to DCS, Twinkle, mamaich and many others who contributed to this fine forum ... Long live the XDA I, II, IIs, III .... beyond ....
Click to expand...
Click to collapse
Just searching through the old threads and I found this post by alvinlim28. I have the same simptoms, white screen, won't start, I get the red light when I remove the battery and place the hima in the craddle, so I guess I'll be up all night trying to get into bootloader and reflash. Thanks all for the contribution in this forum, and thank God for the search option
J.
No luck tonight, I'll keep trying tomorrow gtg to sleep now.
cheers,
J
damm*t still nothing
I've been tryin' all day, and I'm unable to enter bootloader mode
Hi All,
My Prophet just died...
I made a RadioROM upgrade and after a reboot I did an IPL upgrade. I did a soft reset and now it doesn't want to turn on. I'm really confused what did I make wrong and how can I redo it.
I'm looking forward to a helpful info.
Thanks
Does your screen stay black or does it display anything? Can you enter bootloader? And why would you want to upgrade your IPL???
My screen is dark black, I can not even turn it on. I doesn't matter what sort of switch I press on the dev. So I can't see the bootloader and I think it's a serious problem...
After the IPL upgrade the reboot was succesful and on the startup screen it says IPL 2.20.0001 and worked for a while.
I've changed my local settings, which reqiures a soft reset, so I did it. After this, no aswer...
I'm very dissapointed because of the pda and your help dear all...
Is your battery dead? Try it with your charger.
No, my battery was fully charged before I ran into this major problem...
I had a similar issues which was misteriously resolved after a few plug ins and battery removals. I also let the battery completely drain and removed it from phone for a few hours. It worked when connected to wall charger but not with battery. It seemed like interior phone battery was dead. One day I connected it to the wall charger and the battery status when from zero to 98% and it stayed there. Really weird stuff. I ordered another battery and so far so good. One of the batteries did die and i discarded it, but I still use the other old battery plus I have a new spair.
Yamilrx, thanks the info...
I'll try it, but I've lost my faith in this device. It's in clinical dead state for 2 days from now, and it looks like doesn't want to wake up or alive.
This is a very misteroius issue.
I don't understand it, if I upgraded wrongly somebody tell me, why was the device started after? And if it was a wrong update, how can I turn it on and make calls, etc. and after a soft reset it DOESN'T reply for anything?!
I bought it almost 2 years ago, so I assume the battery could cause similar problem. But it was almost fully charged. The Star Wars was less incredible then this thing...
Except this, I'll accept your advice. I'm going to try it.
try the following, as your device is dead and curently noy useable.
-remove the battery for a day and just leave it there
- put in the battery and connect the charger
- hold your camera button while turning the device on
do you get into the 3 colored screen? if so, the device can now be downgraded etc.
particular reason why you have not tried a HARD reset?
Dhirmadi said:
try the following, as your device is dead and curently noy useable.
-remove the battery for a day and just leave it there
- put in the battery and connect the charger
- hold your camera button while turning the device on
do you get into the 3 colored screen? if so, the device can now be downgraded etc.
particular reason why you have not tried a HARD reset?
Click to expand...
Click to collapse
Thanks, I'll try it first after go to a shop and buy a battery.
Anyway, when I mentioned I've tried all the combinations of the buttons, I meant i did a hard reset too. But my Spleeping Beauty is still doing the same...
The problem hasn't been solved by the solutions you have mentioned before, so I've called the HTC technical support, they were very friendly - they must be because I'll pay for it - and 2 days from now they will tell me how much does it costs or it is repairable or not...
Thanks for your help.
mazeee said:
Thanks, I'll try it first after go to a shop and buy a battery.
Anyway, when I mentioned I've tried all the combinations of the buttons, I meant i did a hard reset too. But my Spleeping Beauty is still doing the same...
Click to expand...
Click to collapse
I did that with mine to see if it would reset device once the internal battery is totally discharged. Like I said earlier, mine came back to live. Make sure you install the WM 5 rom used for downgrading and don't try any of the WM 6 roms until the device is fully functional with wm5. The batteries are $8 on ebay but they take 1 week to get here from Hong Kong.
If winter comes,can sping be far away?
Hi All,
The service technician examined my Prophet and he said, I have to change a mainboard. Have you ever run into this kind of problem? If I want a repair, it'd cost me 300 Euro!!
Luckily I still have a warranty, so I hope I don't have to pay for the service.
Take care your Prophet...
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