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.
Related
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
When I was using Helmi's 1.3.2 rom (I have since switched back to the latest WM2003 rom) I had some odd, seemingly hardware related, Issues:
*Back light randomly turned on and off, programs opened and closed and did random things, then the device would reboot.
*It would just randomly reboot.
*I would get a "Problem with bluetooth hardware" Error message when trying to scan for new devices some times, and I would have to soft reset.
*I could not turn off the screen in WMP while using A2DP
*The device would shut off completely and wouldn't turn back on occasionally, and the only way I could get to turn back on was to plug it in. After doing that, all the version numbers on the first boot screen would read "NONE" and I would have to soft reset the device several times to get the wireless working again.
I have taken very good care of my SX66 (I have only dropped it once), and these problems worry me...has anyone else experienced these?
I had also a lot of trouble after having installed a new version of WM5, because I forgot to wipe the memory clean (check step 9 - and especially 9.2 - in http://wiki.xda-developers.com/index.php?pagename=Helmi). Just repeating this step will solve it... it dit for me. that's another thing I won't forget anymore
Hello everyone,I have the Vanilla ROM. 1.4 I believe, what has happened is that I had a friend look at my blue angle because he was considering getting one himself, he went to my Mobile Shell application from SPB, activated the portrait view (took time to load and he did not know that) so he decided to press is like a lot!!
So it tried to do landscape/portrait mode a lot! so we rebooted the thing. Then another problem came that the phone locked itself, and when trying to unlock the phone nothing worked, (press the "*" again to unlock the phone) that did not work at all.
After spending a lot of time I fixed that, then the screen alignment/navigating with the D-Pad was all screwed up, I managed to get to the screen alignment program and fixed that. Now I have this serious problem.
The phone cannot connect to my service provider (Cingular). And here is the funny part... Hard Reset does not at all!! very strange. Using a backup file I had useing SPB backup that also did not work.
(also I tried draining the backup battery and that did not work as well, guess the volatile memory thing in WM5 worked).
Please someone help me in this problem as I cannot use my phone! :'(
Fixed
Sorry about the post, I have fixed it by doing
http://forum.xda-developers.com/showpost.php?p=1164331
worked perfectly, reset the phone easily and now restoreing with a backup.
But if anyone can please tell me why Power/Reset did not do a hard reboot?
Hard reset is not enough
I've flushed my phone about 50 times during last two weeks.
I think, that there are some cases, that same data or state of "things" can survive flashing and hard reset. At least using helmi_c or my ROM.
Simply test: flash any helmi rom, turn on wifi and/or set button lock to wake up only using power button and perform hard reset. State of lock button is not changed, wifi tries to connect to any access point. Even reflashing with the same rom is not enough.
I'm guessing only: I think, that there is small bug - reset procedure checks validity of any particular block (or blocks) of data and skips initialization of same data it if is looks valid.
Maybe you have got the same.
Today I got my Kaiser back from repairs. I got my mainboard replaced because of connection issues. It came back with it's original 'software'.
After installing Hard-Spl (white screen edit) I successfully flashed "Dutty's Official WM6.1 5.2.19209 Release" to my Kaiser.
I wanted to Hard Reset my device using the soft-buttons and soft-reset method, but it seems to be broken (?). I managed it in the past (before flashing and repairs) but for some reason it doesn't work anymore. Soft-resets and Bootloader mode still work.
Anyone got an idea?
Thanks in advance
P.S.: In the meantime I hard-resetted my device by going to Settings => System => Clear Storage
Dr. Strangelove said:
Today I got my Kaiser back from repairs. I got my mainboard replaced because of connection issues. It came back with it's original 'software'.
After installing Hard-Spl (white screen edit) I successfully flashed "Dutty's Official WM6.1 5.2.19209 Release" to my Kaiser.
I wanted to Hard Reset my device using the soft-buttons and soft-reset method, but it seems to be broken (?). I managed it in the past (before flashing and repairs) but for some reason it doesn't work anymore. Soft-resets and Bootloader mode still work.
Anyone got an idea?
Thanks in advance
P.S.: In the meantime I hard-resetted my device by going to Settings => System => Clear Storage
Click to expand...
Click to collapse
Few Tricks, Make sure you are not plugged in USB. Make sure you are not "fat fingering it." Some people use chopsticks to be sure. And Hold it for long after the Screen goes Black.
Believe me, I've already tried the things you said.
Although I successfully mananged in the past to hard reset my phone, I checked the threads and the following vid:
How To Hard Reset Kaiser:
http://www.youtube.com/watch?v=fZPzT_L2FZQ
Usually I am the problem, but this time I can't figure out what I'm doing wrong.
Just wondering:
Which part of the Phone (ROM) is in control of the Hard Reset part? (e.g.: Bootloader, Radio Rom, Regular Rom,...)
Use "Clear Storage". It does the same thing.
Also, JM is most likely correct. It is most likely an issue of how you are pushing the buttons. Make sure you hold only ythe soft keys first, using your fingernails, then push the reset tab on the bottom & hold it. Don't just push the reset & release, but keep it held down.
Based on your previous message about your phone being haunted - mine is too btw, I think it's because the soft buttons aren't being acknowledged by the OS - which implies some REAL big problems.
I took mine back to the T-Mobile store today where I got told that it needs to be sent back to their workshops to fix it... and then got told that "mostly they just send out a new phone".
My phone is exhibiting the following symptoms.
1) Green and Red phone buttons do not work.
2) Soft buttons do not work.
3) D-Pad and wheel work intermittently.
4) (and most strange) the back-space key on the slide out keyboard does nothing, and on the virtual keyboard it flashes (to suggest that the key is being pressed) but still does nothing.
I've tried to access the bootloader, and perform a hard reset. I'm now looking for the original T-Mobile ROM to install (which was why I went into the shop), as the issue around the backspace key implies to me that the issue is in the OS not in the hardware.
Jon
Thanks already for all the input.
I've been trying all weekend in every different possible way to perform a hard reset. Fat fingering is really no possibility anymore. I've used every possible tool I had (needle-nose pliers, chopsticks, pens,...) to eliminate fat fingering.
But nothing helped. Jon (a nice guy) might have given a possibly correct diagnosis for my problem. But it wouldn't explain why I still can get into the bootloader.
Problems since receiving my phone from repairs:
Backlight changed out of itself => performed Hard Reset
Phone pad pops up and seems to start dialing => flashed new ROM
Wakes up constantly after a few seconds from standby => performed Hard Throw against the wall
As you can see, my latest problem is that the phone automatically wakes up from standby after a few seconds. The weird thing: it only does this when I put it in standby, but it doesn't wake up if it enters standby by itself.
=> NOTE: This may support the 'fat finger'-theory: the Kaiser gets some sort of keyboard input due to faulty hardware. Therefore I cannot Hard Reset my device, because of the additional faulty input.
I've used the "Clear Storage" method to perform one of my hard resets, but this has to be solved. I will be sending the phone back for yet another repair.
Thanks again for your input everyone.
Problem found?
I think I found the problem:
I just noticed that the camera button is already pushed in halfway (like when you focus the camera before you take a picture). If I push the button gently, it immediately takes a picture without focussing (it does automatically focus before taking the shot, but not on my command).
Also, when I enter the camera app, it sometimes instantly focuses. Other times I cannot focus at all.
Hard reset is still no go.
Yet another thanks for your useful help.
Maybe found the solution?
Hi Guys...
I found that by tapping the base of the phone, it "unlocks" itself, thereby making it work. It's become *S*L*O*W* as hell, and I'm really tempted to ask them to take a look at it, but right now I need all the functions, so I'm holding off.
But, give that a try and see what happens!
Jon
Thanks for still answering my question. Go community!
Dr. Strangelove said:
...
I will be sending the phone back for yet another repair.
...
Click to expand...
Click to collapse
Last week I finally received a fully functional and working Kaiser (have been waiting for that since december...). I couldn't accept a disfunctional Kaiser coming back from repairs.
The problem did indeed seem to be the camare button that was stuck. I tried really hard to get it to unblock, but I didn't work. I must say, I didn't try your method (didn't think of it).
Still thanks a lot.
I am experiencing exact same issues on my Kaiser (Tilt), it randomly starts to type stuff in the phone application on its own and I can't do anything to stop it, I have replaced ROMs, SPLs, Radios, now using a shipped rom with shipped radio but still that problem comes up after a few days of usage and doesn't go away until I hard reset, anyone knows what I can do to fix it? it's probably out of warranty. I checked the camera button and it seems fine.
I'm sorry to have to ask, but I'm at a loss at this point, I've fixed this problem 3 times, and it keeps coming back.
AT&T tilt, unlocked, Solace 3.1 ROM
HardSPL 2.97
The phone works perfectly fine, except when I have to restart it, then it gets locked in the Bootscreen....and becomes very difficult to get it out. I try a soft reset, hard reset, nothing seems to work.
When this originally happened, I reloaded Solace 3.1 only to have it continue to be locked in the boot mode. Finally I I noticed the camera button and the power button appear to get locked into the on position, so i would manually create space between the button, and the actual activating button within the phone. It has worked 3/200 times I have had this problem. Overall I solved it by never restarting or resetting the phone, but eventually even with a ram cleaning program it becomes a problem.
If I'm thinking of the wrong solution let me know, it now appears to be stuck again in the on position for the power button....I basically ripped off the outer camera button, and now have to manually press the small one within the phone to activate it manually. I still can't get it off the bootloader, and its quite a frustrating problem.
Again, everything software wise works like a charm, I would have to think it isn't software related. Any ideas? I'm at a loss at this point, and using my phone from 2 years ago as a result.
Have U tried using another ROM besides the Solace ?