Related
Hi all,
I have one of the original O2 XDA's (64mb), and it has been fine, but over the last 6-8 months the xda keeps resetting (similar to pressing the reset on the left with the stylus) and the phone switches off.
I do not loose any data, but I have to re-enter the code for the phone. It does it randomly, diverting calls to voicemail, till I turn the phone back on.
I thought mine was a one off, but my brother has the same model and he said he has been getting the same problem.
The details are:
ROM Version 3.14.13 ENG dated 10/09/02
Radio Version 4.08
Protocol version 32S54
Any ideas ?
All help will be appreciated.
Thanks
AA :?
PS It is not Sim locked. ( Thanks to this site)
Sounds like a software program, it might be worth using the xda without any additional software for a while, backup first, do a hard reset and use the phone as normal. If this cures it then you will know that one of your programs is causing the problem.
This might be a long shot in the dark....check the reset button to make sure it isn't damaged in some way. I haven't heard of a PPC reset button being jammed in the reset position but it could be a viable theory.
Good Luck
Hi
I have tried this, but keep getting the same problem.
I set the phone to manual selection of network, and when it reset itself, the phone part would not come on again.
In the end I had to take out the sim, and put a different one in before the phone part would come on. could there be a problem with the GSM bit ?
Ta
It might be the sim-door switch which automatically switch off your phone when you open it. There was a solution of similar problem on this forum
I have searched this and could not come up with any fixes, but here goes.
On my 8525 most of my front buttons would quite working (Send, End, OK, Start Menu, and Both Top Menu select buttons) on every Cingular 2.06 Rom. This would be a daily thing that could be fixed by a soft reset. Then I upgraded to XDA Live 2.0 everything worked great for a while when all of a sudden all of the front buttons stopped working, all of them except the dpad. I did a soft reset and even a hard reset, and every time it would still not be working. I freaked out the only thing I could think to do is to downgrade to the original Rom 1.34 that was on it when I received it so I could try to send it in for warranty. After the downgrade all the buttons have been working now.
So in my mind I am thinking this is a software issue rather than a hardware problem. But if that is the case what would cause this? Is there any kind of fix?
I really want to put WM6 back on my device, but not at the cost of my hardware buttons.
Any help or advice would be greatly appreciated.
Aww cmon nobody has anything to say and nobody has ever run into this? Should I just try to reupgrade with different radio and BL. Would the BL or the Radio have any remote relation to this problem?
Need your help here GuRu's.
Never heard of this problem before. There is a fix for the 8525 keyboard in the XDA Live extras, but I'm almost certain it doesn't affect the front buttons.
I'd almost say that its a problem physically with a broken/barely connected button membrane or something similar.. and the action of you moving the phone to reset it/pressing the button is enough to connect it again.
If you're sure its working 100% now, try flashing XDA Live again and seeing if it kills it again!
Philux-X said:
Aww cmon nobody has anything to say and nobody has ever run into this? Should I just try to reupgrade with different radio and BL. Would the BL or the Radio have any remote relation to this problem?
Need your help here GuRu's.
Click to expand...
Click to collapse
Just a couple ideas. First, what 3rd party apps have you installed after upgrading and have you changed anything in the "softkey" program? Also, when you said you did a hard reset, was it a real hard reset, or just a power down? Some people at first get the two mixed up.
Also, the radio and bl wouldn't have anything to do with a problem like this.
Like TAURUSBulba said, I would think that it HAS to do with some cab/registry or executable you install that is common to all the ROMS that makes it do this. I would suggest you check out your installed applications and research what might create this problem.
The Rest was an actual "hard reset" with nothing else installed on phone except for system files (fresh system). I did not think the BL or Radio would have anything to do with it, I just wanted to be sure. I will try to re-upgrade to XDA Live 2.0 again when I can find some extra time. I will post results if anything changes or I continue to keep having this problem.
I appreciate your feedback.
Thank You
Hey I've been having this problem with my Titan. I have Keys 1.31 rom and every once and awhile when I turn on my Titan it gets stuck on the the windows mobile start screen. Im able to get my phone working again if I reflash Keys rom.
So far this has happened 3 times in the past month.
Any ideas on what could be causing this?
Bell 6800
Keys 1.31 ROM
3.35 radio
Just for future reference...never has your phone been a brick. A bricked phone is just that...a brick, a paperweight, won't do anything at all. It can't be turned on, it can't boot, it can't be reflashed or fixed. It's obvious you're having a problem with something, but I constantly see people on a daily basis saying their phone is bricked when in actuality, very very few people have actually bricked phones.
Sorry, but I have no idea. You're apparently alone in facing this.
Have you tried reflashing to another third party or stock radio/ROM combination to help rule software or a bad flashing out as a cause?
mrfantastic said:
Hey I've been having this problem with my Titan. I have Keys 1.31 rom and every once and awhile when I turn on my Titan it gets stuck on the the windows mobile start screen. Im able to get my phone working again if I reflash Keys rom.
So far this has happened 3 times in the past month.
Any ideas on what could be causing this?
Bell 6800
Keys 1.31 ROM
3.35 radio
Click to expand...
Click to collapse
What bootloader are you running? Maybe a bad install of the bootloader?
no, that's not a possibility, the bootloader isn't like a copy of Windows... besides, it's getting stuck on the windows mobile logo, that means its at the kernel.
my advice is to dump that ROM and flash something else.
Olipro said:
my advice is to dump that ROM and flash something else.
Click to expand...
Click to collapse
In case that is interpreted negatively, quite a few are using builds from my kitchen and he's been quite alone in reporting this.
Sorry, I just had to chime in to defend my work.
That said, if one is facing such problems the first avenue to problem solving is not to keep flashing the same radio/build of an OS ROM into perpetuity. Mix things up. Isolate.
I'm not saying i'm 100% positive on this one, but sounds like to me he's using some kind of software that is coded poorly, or something that is corrupting his kernel or the necessary files that boot the os. Sounds like the phone is getting hung up right when it's trying to execute these files at boot.
My advice to you, that is if you want to keep using key's rom, is to create a CLEAN rom, and don't install any software. Run it for a while clean and see if the problem goes away...if that's the case, you need to re-evaluate which software you use.
HTC home. The silly green screen that says windows mobile? Yeah, HTC home is causing it to fail to boot, this has been covered before.
This is a very misleading title for this post. You can't unbrick a true 'brick' - unless it was a brick because you left the battery out.
A true 'brick' can't ever be turned on. It's a dead paperweight. So, there's no chance of unbricking it.
Flashed Keys rom to few phones....never had a problem !
I used olipro 2.40
Right now the phone is fine, it appears to happen randomly, Keys rom is great otherwise (no insult intended). What was meant by the problem with HTC home?
HTC home. The silly green screen that says windows mobile? Yeah, HTC home is causing it to fail to boot, this has been covered before.
Click to expand...
Click to collapse
The windows mobile splash screen or the "silly green screen that says windows mobile" as you put it is not HTC Home. It is not HTC Home that is causing him to lock up at boot time.
To the OP, read my post, it's some piece of software that is causing your lockup. Guaranteed, if you make a clean rom (no software installed except the rom, with nothing cooked into it) I bet you see your problems go away. I then would install each piece of software one by one testing to see if you see the lockups after each one.
help
Can Any One Tell Me How To Go Back To WM 6.0 From WM6.1 I'm HAVING More Problems Then I Want With 6.1 But I Have No Idea How To Change It Back.
kaos29205 said:
Can Any One Tell Me How To Go Back To WM 6.0 From WM6.1 I'm HAVING More Problems Then I Want With 6.1 But I Have No Idea How To Change It Back.
Click to expand...
Click to collapse
Kaos,
You will find you get more answers by posting in the appropriate thread. This is not a WM6 thread so chances are that most ppl would ignore your post.
As you are probably on dcd 3.0.x, I have answered your question over there in the dcd 3.0.4 thread. http://forum.xda-developers.com/showpost.php?p=2177772&postcount=459
Apart from the fact that your are more likey to recieve an answer when posting in the correct thread, it will also help others with the same problem find the answer wheb they do a SEARCH.
Also another good place to find general information is in the titan wiki (see the sticky at the top of the titan upgrading section).
Lastly, you could try starting a new thread if you just cant seem to find the appropriate place to get your answer.
Hi there all,
<rant>
So I finally got around to flashing WM6 onto my hermes... to give you a bit of background; I had completely stopped using my hermes and had gone back to my ancient (in tech terms) Nokia 6230i after WM5 had become perishingly slow. It had become so much of a pain to connect to my parrot handsfree that I had stopped using that too... (£114 wasted). Also on every phone call there was at least a three ring delay from someone calling me, to my phone realising it should be ringing... not impressed.
So I thought that a flash to a WM6 rom might help, after having a look around for a little while, I went for Schaps 4.31, initially, its a massive improvement, the phone is quick and responsive, and generally runs much quicker, plus there are lots of nice little things like HTC home...
However the delayed phone ringing still seems to be an issue... when I am in the middle of using the phone or if the phone is out of standby and I receive a phone call, it seems to react much quicker than WM5 ever did, almost instantly realising that it should be ringing, much better. However, if the device has gone into standby, then it will completely ignore that there is an incoming call... It simply does not ring... I have just tried 3 or 4 times and my phone hasn't rung once, after I have hung up on my home phone I have been bringing the device out of standby to see if it has registered the call at all, as soon as I turn the device on there is a missed call on it...
This is so intensely irritating! As I am sure you can appreiciate! At least with WM5 there would be a wait of 3-4 rings beofre it brought itself out of standby and then it would ring, but with WM6, nothing! Surely I can't be the only one experiencing this? I can't even say that this might be just my hermes, as I had it replaced by vodafone about 2 months ago...
Sadly... I will be reverting back to my Nokia after I have written this, at least it is able to send/ receive calls without falling over... I cannot belive that I have a piece of hardware sitting on my desk that is, after all the bells and whistles, supposed to be a phone, and doesn't work as one!!! If an old Nokia can manage it why cant my hermes? At this moment there is a hermes selling on ebay of £139, I am very tempted....
Annoyingly my friends iPhone seems to do all the phone functions flawlessly along with lots of lovely web and data integration... It is still apple though..
Does anyone have any suggestions to improve my woes?
Sorry for the massive <\rant>
trinityj5
Update...
About half an hour ago I completed a radio ROM update to 1.56.70.11, I thought that updating the radio stack might go some way to solving my delayed call issues.
Well it hasn't helped at all. The acquisition of signal, and the strength of that signal seems improved, but if my device is in standby then it simply doesn't wake up if there is a call coming in. This effectively renders my tytn totally useless...
Does anyone have any ideas on what might be causing this? I am sure I can't be the only person experiencing this...?
For reference my phone is now running:
Rom: Schaps 4.31 LITE
Radio: 1.56.70.11
Any help would be hugely appreciated...
Trinityj5.
You could try updating the os to fix the standby problem... Schaps 4.31 LITE is fairly old now, If I was you I'd try a wm6.1... They're fairly stable now and are pretty quick too. You could also try to update the .net framework on your PDA to 3.5 but this may require you to do some registry tweaking. Easier to find a cooked os with .net 3.5 already cooked in.
I've always had my phone wake up when a call comes in - even in standby so not sure why yours doesn't. Could be a setting you or your network have imposed.
Make sure you've Hard SPLed your phone before flashing though...
Cheers...
Thanks for your reply ultramag, I think I did at some point have a 6.1 ROM on my hermes, and I don't think it made any difference to the call delay issues. I will flash one again tonight and then report back...
Which 6.1 rom would you recommend?
Why would updating the .net help with incoming call issues?
Cheers.
For the wm6.1 roms I prefer the PDAViet roms and PDACorner roms. Other roms are good too but I like these ones best...
I don't know if updating the .net framework on your phone will speed it up but it does seem to speed up windows. I may be wrong, but if you can speed up the time it takes windows to register the call then wouldn't it speed up the time it rings?
I believe you can change the call forwarding time up to 30 secs if the network only gives you 5 or 10. Its in settings>personal>phone>services>call forwarding.
Hope this helps...
Cheers...
Will upgrade to WM6 lock phone again?
Greetings to All and Thank God For this Forum
I successfully unlocked my Cingular 8525 >year ago. I am still running WM5. I would like to use a micro sd card greater than the 2Gb now installed and believe that is possible with WM6 OS. I'm concerned that I not lock my phone if I upgrade with AT&T's download of WM6. TIA-
docwollf, not sure posting in here will get you very far, try posting in the main forum...
ultramag69, thanks for your suggestion about the PDAviet and PDA corner roms, I tried both, and still my phone doesn't want to work.... Do you think that flashing an "official" rom might help? There has been some mention on here that if your phone starts to become unstable then flashing an official ROM may help, do you think it might help me?
Does anyone have any idea at all why my phone might not ring when it's in standby? Its starting to become intensely annoying to be honest....
Trinityj5.
Try flashing the official rom first, then flash your phone with hardspl, then try the new rom. That may work, but it almost sounds like you have a hardware issue.
Thanks for your reply backspacepc,
When I said to install an official ROM, I meant one like the at&t one or the dopod aisa one, I don't have a WM6 ROM for vodafone, they never released one... would going back to the Voda WM5, then hard spl, then a WM6 ROM help do you think?
I am thinking the same as you about hardware... is there a firmware upgrade at all? I have tried over 10 different ROM's now, some WM6 some WM6.1, still no improvement on the ring delay....
If I hadn't have voided the warranty by flashing etc, I would be sending it back....
Any help is hugely appreciated, as you can probably tell, getting quite exasperated with it now...
Trinityj5.
If you downgrade the SPL back to stock and the original os back to stock then you can take it back under warranty. There are instructions in the wiki on how to do this. I believe you may ALREADY have Hard SPL on your Hermes (to check go to bootloader - hold power, OK button above flywheel and reset with stylus, hold in untilyou get to the tri-colour screen. If your SPL is 2.10 olipro, its Hard SPLed) which means you're gonna have to downgrade the SPL. Unless you supercid your Hermes.
You can find the downgrade instructions, I believe, in mr Vanx's tutorials...
Cheers...
Thanks for your reply ultramag,
I do indeed already have Hard SPL on my hermes, I put it there...
I have been looking at downgrading back to stock and then seeing if I can get it replaced, I find it unlikely that voda will even consider it to be honest... HTC might though...
Is there a hardware upgrade that I can try out at all?
Cheers,
Trinityj5
If you open it then you will DEFINATELY void warranty... If you still are within the warranty period its better to send in for repairs than to fiddle yourself.
There are manuals floating around (HTC service manual) that tells you how to take apart and put your Hermes back together, just do a search. Or if you want try Mike Channon's webpage, found at the bottom of his posts. However, if you still have warranty, thats the best way to go...
Cheers...
Sorry! I didn't mean hardware upgrade, I meant firmware....
Are there any firmware upgrades around? It strikes me that the phone doesn't know how to handle a call when it is coming in, so it just ignores it... A firmware issue?
Cheers, sorry again for the mix up!
tj5
1st thing I'd do is to check all my settings. Both phone and volume. Maybe, if you back up and restore the same settings, you've backed it up for silent or vibrate only.
I know that when a call comes through that its slower to wake up from standby when it also has to access the sd card for an MP3 ringtone....
Check out, with Schapps advanced config, how long it takes the battery & AC to resume from timeout. I set mine to about 10 secs.
Also, you should check how much time it takes before call forwarding kicks in. Go to settings>personal>Phone>services>call forwarding. You can set it to a maximum of 30 secs.
These may or may not help, I'm just throwing ideas out.
Hope they help...
Well I didn't back up my settings, it was a brand new phone when I started so I didn't have any settings to restore.
I have mine set to 10 secs too...
My call forwarding is also set to 30 secs...
Thanks for all your suggestions, I think I might downgrade everything back to stock and see what happens from there...
I'm still wondering what exactly is going wrong in my device... It must be some kind of programming setting that has been set wrong... utterly bizzare... can anyone offer any advice to this end?
tj5
So I accidently installed darkys rom in my vibrant. But funny thing is is that this phone looks EXACTLY like a i9000 except that its original firmware is the vibrants (I can post pics if people want to see this). Anyways my problem is that upon installing darkys rom, my volume buttons seem to have switched around, meaning up is down and down is up. I was wondering if this is an easy fix? Cause if so, any help will be greatly appreciated. Thanks you!