Greetings,
I have a huge brick problem.
Have installed TCPMP .81 (my PDA:wm6 AP One Touch rom) on the grounds that it would solve interference issues. Once installed, it started up in portrait. So, whilst perusing for a suitable fix I ‘inadvertently’ installed ATIFix.cab expecting it to have some indirect beneficial effect. However, I now have a situation where during the initial boot sequence the loader hangs.
Is there a get out of jail free on this one or am I looking at some major FUBAR.
Any assistance would be greatly appreciated.
R.
Have you tried to re-flash the Rom?
I'm a new user of an Ameo and have had the boot screen hang twice now- not using ATIFix, but in my case it was trying to change the default SIP to Touchpal the 1st time, and having an incorrect GPS assignment in the other (I think!)
Only way out was a cold boot- luckily I had SpB Backup installed & current
Cold boot is: hold volume slider down, while pushing soft reset button.
Seems like the OS loader is a bit sensitive!
Related
Hi,
seems I have nailed down one situation, when trion refused to boot through. Whenever I have WLAN active and the system hangs (happened last time today when trying to start up avantgo) its very likely the xda won't boot correctly after soft reset.
Usually I solved it by going to bootloader and softreset again. Today this didn't help, also booting with and without SIM/battery in all combinations didn't help.
So I connected the phone in bootloader mode and sent some commands via mtty.
Don't know why, but this helped the phone to boot again. Weird.
Now - is there a way to switch off WLAN via mtty in case it happens again?
Dirk
P.S.: never give up when the xda hangs, I refuse to use a hard reset (unfortunately it required xx reboot trials and 1 hour of my time...)
Hi,
still there are occasions, where my TyTN hangs at Windows Mobile screen while booting. I couldn't find any system behind it...
I had several suspicions:
- HTweakC while Power Saver Tweak was enabled,
- pBar, when being set to automatically load,
In both cases, removing this options seemed to help, but shortly after that the hangs came up again.
Did anybody else also experience frequently hangs while booting and could isolate some reasons for that?
P.S.:
I know some of the hangs are related with today plugins. The only I have currently is Birthdays 1.2.10. I just removed this as well, but the XDA seems to hang after the reboot again.
How likely are hangs at bootup time hardware related?
Is it a common problem with AKU2.3 and could an upgrade to 3.3 help?
I just don't want to mess around and waste a lot of time - would you suggest to send it in for repair?
(My operator claims, that I should do a hard reset. After that everything is fine. But why should I use an XDA without adding any more program and risking that behaviour?)
thedsp said:
How likely are hangs at bootup time hardware related?
Is it a common problem with AKU2.3 and could an upgrade to 3.3 help?
I just don't want to mess around and waste a lot of time - would you suggest to send it in for repair?
(My operator claims, that I should do a hard reset. After that everything is fine. But why should I use an XDA without adding any more program and risking that behaviour?)
Click to expand...
Click to collapse
I have only ever had one hang on boot up. I have AKU 2.3. Used to get lots of freezing at other times, but it appears I have cured all that and it has settled down very nicely. I also have several today plugins spread over multiple desktops using WAD.
I just wonder (and I am no expert here) whether you may have a little corruption in boot up files. Have you actually tried a hard reset yet?
Having learned several lessons I took mine back to scratch with a hard reset and used SPB backup at each stage as I reloaded software. This way I am able to return to a nicely working setup (within 5 minutes) if I load something duff along the way.
Mike
Yep, did a hard reset and installed some programs. I will try to adopt your way of adding programs. Even if it takes a lot of extra time. Now I need at least 5-6 soft resets, until one works.
However - did anyone ever notice, that sometimes between the operator splash screen and windows mobile splash screen, there is a scrambled splash screen with vertical lines in windows mobile splash screen colors?
thedsp said:
Yep, did a hard reset and installed some programs. I will try to adopt your way of adding programs. Even if it takes a lot of extra time. Now I need at least 5-6 soft resets, until one works.
However - did anyone ever notice, that sometimes between the operator splash screen and windows mobile splash screen, there is a scrambled splash screen with vertical lines in windows mobile splash screen colors?
Click to expand...
Click to collapse
Do I understand you correctly - even after hard reset you still need several soft reset attempts to get it going?
Mike
Hi,
no... if its "O2 virgin" ROM its working.
okay, seems to answer my question regarding HW problem. It seems not to be one.
This is the SW I then installed (maybe in different order):
- Avantgo
- Flashplayer 7
- tcpmp
- SPB Gprs monitor (came with the hardware)
- Clearvue PDF viewer (came with the hardware)
- Birthdays plugin
- HTweakC
- SK Tools
- pBar
I removed battery and communication manager Icon from frontscreen with HTweakC and tried the battery saving tweak. More I can't remember.
I will pay attention now with setting it up again. Did some of the above ring a bell?
dirk
thedsp said:
Hi,
no... if its "O2 virgin" ROM its working.
okay, seems to answer my question regarding HW problem. It seems not to be one.
This is the SW I then installed (maybe in different order):
- Avantgo
- Flashplayer 7
- tcpmp
- SPB Gprs monitor (came with the hardware)
- Clearvue PDF viewer (came with the hardware)
- Birthdays plugin
- HTweakC
- SK Tools
- pBar
I removed battery and communication manager Icon from frontscreen with HTweakC and tried the battery saving tweak. More I can't remember.
I will pay attention now with setting it up again. Did some of the above ring a bell?
dirk
Click to expand...
Click to collapse
Nothing obvious but I wonder about pbar given it appears to monitor a lot of actions and will load at start up.
I'd also do the following with backups before and after. It's a pain doing some of this from scratch if things go pear shaped.
[FONT=Geneva, Arial, Sans-serif]http://forum.xda-developers.com/showthread.php?p=1078848#post1078848[/FONT]
[FONT=Geneva, Arial, Sans-serif][/FONT]
Mike
man! this 'cking device is doing my head in! I think it's the worst I had! my list of gripes are:
1) the 3g (umts) connection sucks balls! drops after about 5 minutes! ony way to fix it is a soft reset (see below)
2) if I do a soft reset, any sms or pushed email disappear!
3) after using some website forms, the pull out keyboard is on caps lock constantly meaning I have to soft reset (resulting in lost messages as above).
4) no matter what settings I use (backlight and power) the device is constantly powered on, even after specified time for backlight and power off.
I'm sure there's more but can't think of them at the moment!
anyone else getting the same trouble as me? if so, what did you do to fix it?
gibster said:
Don't know what build etc, but it works!
Click to expand...
Click to collapse
Sound like you need to look at what you have loaded closer. Do a hard reset and figure out what radio and Rom versions you have loaded. Then someone may be able to help you because your problems are not normal.
lol. sell it to me for $20. glad to take it off ya hands.
gibster said:
man! this 'cking device is doing my head in! I think it's the worst I had! my list of gripes are:
1) the 3g (umts) connection sucks balls! drops after about 5 minutes! ony way to fix it is a soft reset (see below)
2) if I do a soft reset, any sms or pushed email disappear!
3) after using some website forms, the pull out keyboard is on caps lock constantly meaning I have to soft reset (resulting in lost messages as above).
4) no matter what settings I use (backlight and power) the device is constantly powered on, even after specified time for backlight and power off.
I'm sure there's more but can't think of them at the moment!
anyone else getting the same trouble as me? if so, what did you do to fix it?
Click to expand...
Click to collapse
"Don't know what build etc but it works"
I beg to differ - it obviously dosen't work.
I would suggest calming down and doing some ligical trouble shooting. These issues are specific to you so it is obviously not the device (don't blame it). You have given no info on your setup so don't expect too much help.
Ditch any cooked rom you might be using and go back to std manufacturers rom. A hard reset fixes most things - then install only necessary apps, one by one and checking that things are still OK. Cooked roms are only for those who are good at/have the time to/inclination to, trouble shoot.
Caps lock is probably related to the way you use the Shift and Function keys. Experiment with double cliking those keys - it can be confusing but there is a logic to it. Experiment and you will work it out.
ok...
rom version: 1.18.255.3
rom date: 22/07/06
radio version: 1.03.03.10
protocol version: 32.34.7010.01h
It's completely standard (didn't have the balls to try upgrading the rom). I've hard resetted a billion times. experimented with no apps installed and still the same kind of things happen.
apps i usually install are:
skype
spb backup
spb insight
tom tom 6
pieplus
lingvosoft japanese dictionary
lingvosoft japanese phrasebook
So not alot installed (and all on sd card, so plenty of room on the device).
Hope this gives some clues!!
Cheers guys
gibster said:
man! this 'cking device is doing my head in! I think it's the worst I had! my list of gripes are:
1) the 3g (umts) connection sucks balls! drops after about 5 minutes! ony way to fix it is a soft reset (see below)
2) if I do a soft reset, any sms or pushed email disappear!
3) after using some website forms, the pull out keyboard is on caps lock constantly meaning I have to soft reset (resulting in lost messages as above).
4) no matter what settings I use (backlight and power) the device is constantly powered on, even after specified time for backlight and power off.
I'm sure there's more but can't think of them at the moment!
anyone else getting the same trouble as me? if so, what did you do to fix it?
Click to expand...
Click to collapse
I'm making some assumptions...
1) This could be your area, but might be worth looking at your Radio ROM?
2) Don't use the reset button at the bottom of your device. Hermes uses some caching and if you hit the reset button it doesn't get time to flush. What you need to do is hold the power button on the side for awhile until it asks if you are sure you want to completely turn off your device, which of course you do. Once it's powered off (it takes a little while sometimes while it saves everything) you can press the button if you like then power on again.
3) On the slide out keyboard, hit the round circle button on the very button left of the keyboard, then press the caps button above it.
4) Do you mean the screen is lit up (the backlight) all the time? Or that the backlight goes out but you can still faintly see the today screen? The Hermes is always meant to be on, just like any other phone, or how else would you be able to get a call?
So I am having to flash back to a previous version due to some issues with the camera and battery.
Flash back to a Telstra official ROM from HTC website - it installed fine - however when it goes to the 'align screen' it doesn't register any taps at all.
If I try to reflash with an older original rom it comes up with a connection error
Any ideas?
--- Update ---
I have updated to the original stock rom for Telstra + original SPL 1.15 - when I boot however it does the 'first time setup' - and the align screen comes up - if I 'rub' my finger around the location it will move - but no single tap works - after going through the five spots - it will just then loop again... really frustrating!
Similar symptoms
After updating my touch HD I noticed a similar effect. When my phone was new the screen align requested 5 taps then proceeded, however after flashing to newer ROMs the screen align intermittently repeats itself.
I've found however that it suceeds more often (and quicker) when I use the stylus to tap the center of each cross and make sure each of my taps are 'long-holds' (like when holding the 'tap' for the context menu).
I have put it down to an update perhaps trying to more accurately align the screen to the user? But I would be interested to find out if in fact it is a problem with the software, or something with the screen maybe?
Unfortunately though, my only offer of a solution to your current problem would be how I got passed it; patience, and firm screen taps (with the stylus).
i think it's best to use the stylus whenever you align the screen. i usually tap-and-hold until the crosshair moves to the next spot. i've never been able to align with my finger.
I would recommend a hard reset and try again. Worked for me!
yeah I tried a hard reset - and tried holding for ages as well - no luck so far
Gil-Dale said:
yeah I tried a hard reset - and tried holding for ages as well - no luck so far
Click to expand...
Click to collapse
are you using a stock ROM along with a stylus? also, if i recall, you were wanting to reinstall your stock ROM to get your device serviced? correct? was the screen one of the issues you wanted to fix? and finally, if you applied the stock 1.15 SPL, be sure you flashed the ORIGINAL Telstra ROM. i'm not sure of this (and it could be a moot point) but flashing to the newest Telstra ROM could update your SPL. sorry for all the questions; this is my way of brainstorming via user forums.
Hello,
I recently configured ActiveSync E-Mail on my HTC HD mini. Everything works fine until I power off and power on the device. The startup sequence is paused with the following text:
"Company policy has enabled device encryption. Startup is suspended. Select unlock to continue. Emergency calls: Press talk."
When I select Unlock then nothing happens (the button is pressed).
The device cannot be turned off by power off button (it only goes to sleep).
The problem is not solved by removing the battery, putting it back and powering on.
The only way to get the device working is to hard reset the device by the special sequence of keys.
Device: HTC HD mini
ROM: RUU_Photon_HTC_WWE_EastEurope_1.36.479.1_Radio_Signed_32.2803.05.06_0.63.05.36_Ship.exe
I reproduced this problem 3 times.
I downgraded from RUU_Photon_HTC_WWE_EastEurope_1.36.479.1_Radio_Signed_32.2803.05.06_0.63.05.36_Ship.exe to RUU_Photon_HTC_WWE_EastEurope_1.32.479.2_Radio_Signed_32.2802.05.06_0.63.05.35_Ship.exe which seemed to remove the problem. However, it appeared after several power cycles also on 1.32.
Any idea how to correct this?
I had exactly the same problem when I purchased the HD minn a few months ago. It happened 3 times in a row that I had to hard-reset and re-install for exactly the same reason (no unlock keys after start-up.) I called my corporate's IT department. They said they changed something on my MS exchange policy profile that may help. Frankly, I can't believe that this was the real root cause of the issue but ever since then it works fine. Never had this problem again for 4 months.
Sorry that I don't have a real solution for you.
CM
Thank you for you reply. May I have additional questions?
1. What ROM release do you have on your HD mini? As you had the problem a few months ago it might be 1.32, right? I have the problem on ROM 1.36 when I first time power cycled the HD mini. It survived many power cycles on ROM 1.32 until the last one which caused the problem again.
2. Is there any chance asking your corp. IT dept. about the change they did?
==
edit:
It seems that the responsible one is HTC Sense. I upgraded from ROM 1.32 to 1.36. I decided to test this with HTC Sense turned off. The problem is no longer present on 1.36 when HTC Sense is off. However, it is a workaround only. I informed HTC support and I hope they will fix it.
Same problem as the others, only I found the cause!
Everything works fine on mine (1.36) until I change the lock screen wallpaper. As soon as I change that the device hangs on the unlock screen at start-up.
If you look at the way it all works, on start-up when you are prompted to unlock, you get the standard unlock screen with the slide down option, and a background picture. I'm guessing the default picture is held in un-encrypted memory, and so it works. If you change the picture, the new picture is held in encrypted space and can't be accessed until you add your key. Only you can't because the device has crashed.
One work around may be to assign it a background picture from the SD card. But having only just got the thing to work I don't feel like trying it in case it puts me back to square one.
Update: Yes copy the image you want to SD card and then change the lock screen wallpaper to point at that. Device boots normally with the new wallpaper.
Hopefully this will help someone.
radar: Thank you for your input. The explanation sounds reasonable. I'll test it once I need to reinstall the device. I'll stick with the working status I have for now.
I am in the middle of waiting for my hard reset to complete as I type. I just had the same exact issues as you all described. I wanted to add though that the background I was using when this happened was from my storage card so I dont know if that will fix anything.
Ill try to add anything else I find out. I am going to try this one more time and then forget about my work email if the same thing happens. Or I might try to find a new rom - but I like what I have
Edit: I actually just saw that you (radar) said the image on the card worked... weird. I'm goign to try again. If I could get around this everything will be working perfectly and I'm not ready to give up.
Try disabling HTC sense. It helped me.; I am running months (done several power cycles) without the problem.
this is a new problem for me. I have been using the most recent Dutty ROM together with Mdeejay Android ROM without any problems. All of a sudden, when I try to unlock the screen after STANDBY, it just wont register my touch, as if I am not touching it. It boots up fine, and on the first unlock works fine, but when the screen lock goes on again (after every standby) it just wont unlock. So I am stuck (I use Exchange and our policy forces the lock after standby, so I have to use it - and its worked fine for ages).
If I boot into Android, it works fine, the unlock works fine, yet strangely when I try to shut the power down, THAT screen also doesnt register me touching it.
I have hard reset but even before I load an app or do anything, the problem exists.
I also reflashed a DUTTY ROM. Same problem.
I tried CHT lockscreen - same issue. After Standby, screen doesnt register my touch.
Anyone have any ideas?
Same problem for me.. Restoring a backup image after being forced to hard reset this morning and now suddenly my HD2 won't wake up after sleeping. Pressing my end key only lights up my buttons but I have to pull the battery to reset. I'm thinking it's related to me having CHT installed, yours however might be a different problem.
I had something similar. It was right after I had installed CHT 2.0 and was looking to make the top and bottom bars transparent. I found a cab that claimed it would do this and installed it. Sorry, I don't recall what cab it was and I have deleted it. When I rebooted Sense would hang and if it got into a lock it would only move the slider a little where it would stop. Luckily, I had done a backup that morning right after I installed CHT 2.0 with Sprite so I restored and all was well.
I don't know if this is of help but I figured I'd throw it out there.
it wakes up, but wont register when I try to swype the unlock screen.
ekerbuddyeker said:
it wakes up, but wont register when I try to swype the unlock screen.
Click to expand...
Click to collapse
Your lucky you get that far lol.. I don't get any waking up. Plus I now uninstalled S2U2 and still no change. Disabled all locks of any kind and still frozen with sleep of death with in 1 min of hitting power to sleep it. I REALLY don't want to to a hard reset and install everything from scatch.. UGH.
weird update...
It has something to do with which key i witch the device on with. If I use the phone key, I can swype the unlock. If I use the power key, it doesnt register.
Another related issue: when i hold the power key to switch off, it wont register me touching power off or reboot etc. so I have to take the battery out to switch off. Its the same in Android.
Anyone know? Hardware issue?
ekerbuddyeker said:
weird update...
It has something to do with which key i witch the device on with. If I use the phone key, I can swype the unlock. If I use the power key, it doesnt register.
Another related issue: when i hold the power key to switch off, it wont register me touching power off or reboot etc. so I have to take the battery out to switch off. Its the same in Android.
Anyone know? Hardware issue?
Click to expand...
Click to collapse
bump this is horrid
same
im having the exact same issue. I have flashed 3 different roms and flashed to the newest radio (2.15).
I started out using energy rom, didnt help. Flashed a newer energy rom, didnt help. Now im using the dusk rom, same issue.
SOMEONE PLEASE HELP!!!!
It's a quite common digitizer problem lately... it seems the HD2's digitizer is failing on some units, possibly because of usage with android? my father's device acted the same way, only it sometimes did register touch and other times, not.
My device doesn't have these problems, yet. But seeing that a lot of people here are experiencing these issues, and with the notion that I use android pretty much all the time since I first booted my device, i'm pretty sure i'll experience it soon as well..
Make no confusion thou, the assumption that android effects the digitizer are purely my own thoughts on this matter, no such thing has been proven and the conclusion that android is effecting our HD2s is based purely on the statistics of touch screen failures in the last few months since android has been made publicly available in a working form.
EDIT:
Those seeking A solution, as far as I know, the only solution is sending your unit to HTC for repairs, you'll get it back with a note that says that they replaced your digitizer or your screen, at least these are the reports I heard from the other folks whom followed this procedure.
Good luck.
HTC HD2 Screen Lock
I have only used Android a few times on this 'phone and it has a standard HTC/O2 ROM installed so it must just be a problem with the top part of the digitiser. With android running the unlock is at the bottom and is unaffected.
Is there any way of testing the digitiser before deciding whether to get a repair sorted,
Ta,
link:
htcphones.net/htc-hd2-problems-with-touchscreen
short version :
change digitizer
ekerbuddyeker said:
weird update...
It has something to do with which key i witch the device on with. If I use the phone key, I can swype the unlock. If I use the power key, it doesnt register.
Another related issue: when i hold the power key to switch off, it wont register me touching power off or reboot etc. so I have to take the battery out to switch off. Its the same in Android.
Anyone know? Hardware issue?
Click to expand...
Click to collapse
A friend was complaining to me about something like this since last week. I could not figure it out so I went ahead and installed Android cm7 and still have the same issue.
Until I read this post after searching through the forums all over Screen now unlocks perfectly fine but only using the green Phone icon. If I try to wake the screen with the red Power button, the screen is unresponsive.
Thanks for the info.
Already happened tome its a hardware issue can't be fixed so if you still have warranty on ur phone send it to htc for repairs b because it tends to get worse n worse soon other keys will start to give in I think that's one reason why most android phone been switching to capacitive buttons because hardware causes this sorta issues and send it in for repairs to get it fixed
Sent from my SGH-T959 using XDA App
the same issue with me , is there is any solution for that .
Wakeup the phone using the send button.it will work