Related
Everything was going along so great.
I used lokiwiz to unlock my cingular 8125. I did both option a (unlock) and option c CID unlock.
Worked great.
I then flashed the latest summiter rom (one with 217...AD2P_fixed)
Again, went flawlessly. Everything was working and I was a happy camper.
Installed a few mods including:
- smartskey
- nullkeyboard
- tcpmp
- flash capable from Macromedia
I checked each app after installing and everything was working great.
Later that day, I added RegistryWizard and its associated OpenNETCF file and made just a few setting changes:
- 802.11G on
- default to nullkeyboard
- changed a setting for improving performance from 4K something to 8K something.
I clicked on okay and it asked for a restart and I said OK.
It never woke up. I tried a hard reset, tried removing the battery. All I occassionally get is a white screen and then back to blank screen.
I tried to reflash but since I can't connect via Activesync, I can't reflash.
Can someone help! I've only had this phone for 2 days!
Take it back to Cingular and tell them the phone just up and quit, and can they just give you a replacement phone.
whew. problem fixed.
I searched and searched and finally found the solution.
I guess there is this thing called bootloader mode (rainbow colored screen).
This allows a connection via usb even though Activesync doesn't sense the pda.
To get in this mode for the Cingular 8125, I took the battery out to shut it down. Then put the battery back in and while holding the camera button, pressed the power button.
This turned on the 8125 in bootloader mode. I could then plug in the usb cable and reflash with no problem.
Had the same problem. Hard reset actually worked for me in terms of resetting the phone in order to reflash.
The problem you're having is related to NullKB and Registry Wizard. As soon as I set NullKB as the default through Registry Wizard, phone died on reboot. Happened three times, and at that point, you know, shame on me.
Reflashed, set everything back up, did not set NullKB as default, and no problems (except a random reboot in the middle of phone calls).
jonty12 said:
Had the same problem. Hard reset actually worked for me in terms of resetting the phone in order to reflash.
The problem you're having is related to NullKB and Registry Wizard. As soon as I set NullKB as the default through Registry Wizard, phone died on reboot. Happened three times, and at that point, you know, shame on me.
Reflashed, set everything back up, did not set NullKB as default, and no problems (except a random reboot in the middle of phone calls).
Click to expand...
Click to collapse
I sort of suspected that. I only changed a few registry wizard settings. I basically reinstalled everything and only changed the 802.11g setting for now. Working great again. I thought the problem might be with null keyboard or the fact that registry wizard gave me a warning about being for an older version of windows mobile. Had me worried for a while. Did lots of searches and had no idea to search for bootloader.
For others searching... white screen, frozen, locked up, can't install rom, lost activesync, can't restart.
Hi,
I have a Qtek9090 which I upgraded yesterday to Helmi BA WM2k5 AKU2.6 Beta (v.1.1.2 Beta).
Everything went fine and I do like it (apart from the usual problems with WiFi, BT,...).
However I got into a shock-state when I turned it on this morning after leaving it in the craddle during the night for charging:
It would turn on, but the screen was completly f..ked up!!!
I did a Softreset -> screen still messed up
I did a Hardreset -> screen still messed up
I did reflash the upgrade -> screen still messed up
I took out the battery for half an hour and put it back -> still the same
After many resets and so on, suddenly I got the color stripes again and the phone booted normaly. I did not even loose any data.
Next I put it to charge again and after a while (the screen went off meanwhile), I turned it on and guess: scrambled screen again.
This time, I did the Reset this way: battery-notch off, kept the Softreset pressed and simultaneously put the battery-notch on again.
Is this a known problem (shouldn't be - I searched the forum!)?
Why does this happen?
Any ideas???
Also, I have these questions:
- What is this selection one has to do after the upgrade for (2. and 3. item YES)? What should the first item be: YES or NO? Can this be the cause for my problem?
- Would it be wise to downgrade again? (In case this is a defect -> so I can try to claim warranty, if things get worse...)
- What is the patch for energy management for? Where can I download it, as the link in the Wiki does not work? (Has this to do with my problem?)
Thanks,
vma
The problem remains.
It does not seem to depend on the charging, but happens when the device is turned off for some time.
When I turn it on it will either work fine, or funtion with a wild flickering screen.
Arrggghhhh!!!
Am I the only one with this problem?
Cheers,
vma
Hi,
Some month have passed on this issue. The reason I did not post about it, was because I had to send my BA for repair and one never knows if the "enemy" is listening... Now the warranty has expired anyway and mey BA is fully working.
It may have been a coincidence, but one day after the upgrade the screen went mad and totally messed up. Only 1 Hardreset in about 100 tries would bring it back to normal for some period of time and even reflashing it with WM5 or 2003SE would not make it work normal again.
The screen would get messed up suddenly for no particular reason, normally during a standby.
At the end I had to send it in for repair, which was actually a good thing, as I complained about the loose stylo and bad working hardkeys, all within warranty.
I got a new key-pcb, backside and they reflashed the device with 2003SE.
I am almost sure that I must have done something wrong with the upgrade to WM5.
Strangely I was able to flash 2003SE onto it, though it did still not work properly: hours with messed screen and sometimes out of the blue I would turn it on and the screen was OK again for a few hours.
Could it be a bad cable connection, which got repaired as well? Was it just a software problem?
One of the things I was in doubt with: when you enter this menu to format the device, the instructions say to switch two options, but the menu on my device had three options. Sorry - I do not exactly recall the details.
Anyone with an idea, why my device went mad?
As a side-note: while WM5 was great, while it worked during the one day it worked. I specially liked to be able to turn the device completly off or being able to remove the battery without loosing data.
However: not having my beloved BA fo two weeks made me reconsider doing experiments on it. Since I have it back I did not reconsider flashing it again.
But I would like to understand what had happend...
Cheers,
vma
May I assume from the lack of replies, that this was a pure coincidence on my device?
Nobody else experimented this weird problems after upgrading to WM5?
I am considering upgrading my phone again, essentially because I am tired of being afraid of discharging the battery and thus losing all data...
Cheers,
vma
The following (long!) post was originally posted at the PointUI forum, but I thought it best to cross post it here. I've tried to organize it as best as I can and appreciate those with the patience to read it and the good will to offer help.
------------------------
My AT&T Tilt (HTC TyTN II) is basically out of commision right now, and I can only track the source of the problems back to the latest update of PointUI (v1.02b, Feb. 4th 2008), as I've done nothing else with the phone since. However, seeing as how I've uninstalled PointUI and the problems persist (and are getting worse), I suspect a virus is afoot, or some other lovely problem.
Since the update, I've experienced the same problems as everyone else on this PointUI thread (system hangs on "running apps" screen and randomly), but in addition to that, several other things. I am running the stock AT&T ROM without the bloatware. These have been my symptoms for the most part since then:
Periodically, animations between menus would slow down considerably and sometimes freeze for a moment, even when I had nothing else running in the background. This would happen for any menu: the cog, the bottom bar, favorites, etc.
The touchscreen would stop working (usually, only within PointUI). This usually happened when animations would slow down, but it would also occur alone, randomly. The hardware buttons would still work during touchscreen failure, usually, but sometimes they wouldn't, and I would have to soft reset.
Sometimes, the power button wouldn't work, and I would press it several times thinking I didn't do it hard enough the first few times. After ~20 seconds, the screen would turn itself off and on. When the screen was on, it would not responding to touches.
The PointUI top bar that appears when using any application would, at random, not work. By this I mean when I would tap it, it's like it wasn't even there -- the Start menu would come down, or the volume control, date/time, etc. depending on where I tapped it. Also, the top right button (red X, or the check mark) would not display correctly in programs or the today screen (a check mark when it should be an X, etc.), randomly, and would not be responsive.
Yesterday (Feb. 23rd), things took a turn for the worse. Here's what happened:
When I started up Tom Tom, the screen went completely non-responsive. Only buttons would work.
After exiting Tom Tom (in an attempt to restart it), the touchscreen would continue not to work, both in PointUI and regular old Windows.
Shortly following this, buttons would stop working, and the entire phone would freeze up. Couldn't turn the touchscreen on and off. I did a soft reset.
During startup, when it showed the AT&T logo, the screen dimmed itself to the lowest brightness setting (it never does this). It would remain this way all the way through the bootup process and into Windows as well, never getting any brighter. Even after going to the backlight settings and increasing the brightness, the screen would get brighter, but would never turn off.
Once in Windows, the touchscreen was completely non-responsive. Buttons would still work, but everything would move really slow.
The screen would never turn itself off. Also, when pressing buttons, the screen would never get any brighter.
After mashing the buttons a bit (in anger, yes, but lightly), the touchscreen alignment application came up, asking me to touch the screen in a few places. This worked.
Then, a call came in. The screen froze during the animation for the notification of an incoming call. Also, the phone started to ring, but within 1 second stopped. However, it would vibrate nonstop (my phone is setup to ring and vibrate at the same time) till the end of the earth!
At this point, none of the buttons would work, not even the power button. Did a soft reset.
This was followed by the same exact symptoms ~4 times (touch screen not working, never turning off and staying at the same brightness level, etc). Outgoing calls would work ok, but each time, a call would come in and freeze up my phone.
Eventually, after several resets, the touchscreen would work without having to mash the buttons to get the touchscreen alignment app running. However, it would still freeze on incoming calls (only).
Somewhere between all the resets, I realized that sliding out the keyboard would never switch the screen to landscape. I can still type and my text would show up on-screen, and screen taps still work properly (even touchflo), but all of this would occur while still in portrait mode.
Lastly, the power button would only work once. It can turn the screen off, but not back on, ever.
Somewhere, between the resets, I uninstalled PointUI, which did nothing. I also tried running Sprite Backup, which would never open (and still doesn't at time of writing)!
Before the PointUI update, none of these symptoms were present (earlier release was v1.01b, used since early January). After the update, they began creeping up, getting worse over time. I have installed nothing else since the update, and have only ever sync'd the phone with my computer to charge it.
Today (Feb. 24th), it started getting a little worse...
When I make calls, sometimes the microphone doesn't work at all. I can hear the person I'm calling, but they can't hear me.
Sometimes, the green phone button won't start the phone application.
Power button isn't turning off the screen anymore at all.
This is the current status of the phone. Weathered, battered and beaten, it marches on, still capable of opening the HTC Audio Manager and playing my MP3's in consolation.
Any help regarding the source of these issues is greatly appreciated.
Some additional notes/summary:
I am running the stock AT&T ROM without the bloatware.
I haven't dropped the phone or let it get wet.
I may hard reset sometime this coming week, probably Monday. The first thing I'll do is reinstall PointUI v1.02b, and maybe TomTom. We'll see how that goes.
You know, the more I read this post, the more it seems like a virus.
Man... just hard reset/flash a new rom and be done with it.
SH4YD33 said:
Man... just hard reset/flash a new rom and be done with it.
Click to expand...
Click to collapse
I thought the above was the reason we DIDN'T have WM viruses?
Virus + Hard Reset = Problem solved?
SH4YD33 said:
Man... just hard reset/flash a new rom and be done with it.
Click to expand...
Click to collapse
I agree, at least that way you know if its hardware or software related and you stop fighting a losing battle
MM
tsadek said:
I thought the above was the reason we DIDN'T have WM viruses?
Virus + Hard Reset = Problem solved?
Click to expand...
Click to collapse
That's why I haven't bothered with any of the anti-virus programs out there. Why bother having a constant drain on the system resources when you can do a hard reset, and restore all the cabs & hacks in under 30 minutes?
-Jay
Just an update here, my phone started acting up again ~5 days ago: freezing on incoming calls, not switching to landscape when sliding out the keyboard, never turning the screen off, etc. 3 days ago it got better, and I was able to run Sprite Backup and tried to restore the phone back to my pre-PointUI days. It had to reset, and on that same reset, Sprite didn't run -- the phone just booted into Windows, and all my problems came back.
Last night, I got a call that froze up my phone again. So I reset it, and by surprise, Sprite Backup ran and started restoring my phone. Now it's back to the way it was in January, and everything works perfectly! This backup was made before I ever installed PointUI.
Bottomline, no PointUI, no problem.
However, I should say that with v1.01b, I never experienced any of these issues. Because of my experience, I'm not giving any test versions a try, but I may install 1.03b, when it comes out. Definitely doing another backup before that too.
Thank you everyone.
Sounds to me more like a hardware issue, perhaps with your SD card.
I had the same issues you were havingh, but without ever having installed PointUi on my Kaiser.
I was using Dutty's Rom version 7 with radio 1.27.xx
only installed aps : TomTom and SPB brain training
So it would seem this is a WM or TomTom triggered issue....
My Kaiser just started doing this very same thing today. I'm running the standard AT&T WM6.1 ROM and have been successfully since December 07. I have a 6GB SD card with TomTom on it, also have had no issues until now. Today, the screen didn't switch into landscape upon sliding the keyboard out; the camera freezes and/or is unresponsive; power button doesn't work (on OR off; with or without SD card inserted); couldn't pick up a call earlier today; TomTom freezes when loading; WM player freezes while loading media.... I have not installed any apps on this thing since January. Seems to me like some memory corruption going on, possibly page file related.
I *did* notice that I had about 45MB worth of temp internet files cached and cleaned those up earlier today after these symptoms started. Didn't fix the problem though, but being low on main storage may have contributed to the corruption problem.
I had hoped I wouldn't need to hard reset my phone but here we go....
Hello guys!
I'm having some trouble with my HTC Touch Diamond. I am running the latest ROM, and the phone has worked perfectly since I've got it!
But one day it suddenly powered itself of during a phonecall and I was not able to power it on again. I removed the battery, put it in again, didn't work. Took out the battery and waited for almost 30 minutes, tried again and now it worked!
Since then the phone locks up in no systematical pattern (when I wake up in the morning it mybe locked itself, sometimes when I listen to the radio or typing an SMS..). Do you have any idea what the problem might be? Can't type in the serial number as I just have managed to turn it on.
What should be mentioned is the behavior when trying to start it. Either the phone gives no respons, or it "buzzez" and the display shows "touch diamond", but the rom version is not appearing down to the right. When it starts, it starts just as it should and no error messages is displayed.
I have not tried doing a hard reset yet, which I must say is considered the last option.
Have anyone experienced something like this? Or does anyone have a suggestion about what might be causing this?
Thanks on beforehand
Edit: have performed a hard reset now (did not format the 4gb). But the problem is not gone.. The phone just died while surfing. Now it locks at the green windows mobile-screen just before the homescreen loads (if it even boots at all...)
Please help anyone!
Dear buds,
I've bought a TD2 with WinMO 6.5 lately. I had lots of bugs and fixed them all but one...
After some time from bootup (after 1 or 2 hours) the sound of phone goes off without a reason. No sound from speaker, headset or volume control buttons. However everything goes well instead sound. Phone vibrates when get call, notifications and alarms vibrate without sound etc. My only solution to get back the sounds is soft reset. After soft reset everything gets fine...
I think this is a sound driver issue but... If someone to help or show the way on forum please help (because I couldn't find same issue on search)
Thanks in advance.
If there aren't any other programs causing this by adjusting your volume levels, It may be a driver issue and you'll probably have to hard reset.
This is a common issue when flashing a new ROM without hard resetting after.
Dear Bruce,
Thanks for solution suggestion.
I hard reset three times until I bought the phone but nothing changed. I'm using the official shipped ROM and I didn't flash any other ROMs.
Extra programs list:
Klaxon
SKTools Lite
Garmin Mobile XT (Because my Copilot runs only after first installing then crashes forever)
Sportypal
Google Translator
Could that happen because of wrong flashing at factory or service etc.? I mean, this phone is a Vodafone version.
In Turkey, Vodafone signal often goes off and usually my phone gets stuck when the signal is off. Could this be the reason for unloading driver?
The digits of my phone are here:
ROM version: 2.16.468.4 (67041) WWE
ROM Date: 11.12.09
Radio Version:4.49.25.17
The fact that it works for a short while after soft reset perplexes me.
You have verified your volume is on when the sound turns off? (Sorry I have to ask this)
Any other programs running at the time is stops?
GPS software can conflict with system volume and backlight, so maybe make sure Garmin is set to dynamic settings.
Other than that, I really have no suggestions as a hard reset has not helped.
Perhaps hard reset, test for a while and see if it fails w/o any programs. Then install one prog at a time until you find the cause.
There is a slight possiblity that it was a bad flash and the driver is corrupt, which would mean reflashing the stock ROM.
Sorry I couldn't be of more assistance.
Dear Bruce
Sorry for very late answer for your last post
It's sure the phone volume is on
I've been examining the phone for one week and tried some possibilities and still no way for the bug
First I hard reseted again, then didn't install any other programs. After 6 hours, the same issue occured.
I uninstalled CoPilot (which I didn't use after hard reset) then soft reset and wait, just only some hours later, the sounds went off again.
After several soft resets, I decided to play music and monitor if it happens. Then BINGO! The sound went off just after poor GSM signal. When the phone lost the signal, it temporarily locked itself. After 2 or 3 issue, the phone sounds went off.
I think, phone starts a search after signal loss, then it tries to execute rest after 10 or 30 seconds either the signal comes back or not. After some trials it cannot reload sound .dll and sounds lock forever. But after soft reset, everything gets fine again.
To be sure about signal loss, I took the phone in flight mode for one day and wait for the same bug and the second BINGO came Phone didn't show the same bug.
After all, I reflashed the official ROM of TD2 and tried the same things but nothing changed. It's sure that the bug is not due to the wrong flashing the ROM.
For now, I'm sure that the bug occurs because of poor GSM signal of Vodafone in my region. So the question comes
Is there anything (such as a registry tweak or vice versa) to make the phone not to lock itself while loosing the signal and searching? Or do I have a way to increase the signal sensitivity?
Thanks for the worthful answers.
Regards