Hello:
I have searched to forums, but did not find a thread that addressed my specific problem. I'm hoping that someone here might be able to help...
I have a Fuze running the EnergyRom August 1st build. I have not had any problems to date except for the occasional lag and the battery drain. I've never had to reset or anything.
Last night the phone was working fine, I set the alarm, plugged it in and went to sleep. At 2:30 this morning I woke up to my voicemail message on the phone. The phone had somehow called my voicemail. I hit the end key - no problem - but after that my touch screen would not function.
At first I thought the screen was broken somehow. (There are no cracks or spots; it hadn't been dropped. I did not get the "broken screen" or any black/white "noise" that others referred to in their posts.)
I did a soft reset, no result.
Hard reset, no result.
Then I realized that the screen actually works, but so slowly that it is almost imperceptable.
Right now I am on the align screen part of the boot-up. It is taking approximately 8-10 minutes for the phone to register each touch of the target and move to the next.
I assume that eventually it will boot, but my questions are:
Where do I go from there?
Should I just reflash?
What the heck happened???
Any and all advice would be appreciated. Thank you!
Flash back to stock ROM, then reflash a custom one.
Your issue will be resolved
Hi, Bruce. Thanks for responding.
I tried what you suggested, but still no luck. I flashed back to the HTC OEM ROM, then to EnergyROM 'Genesis' (SYS 23016). Now I am stuck on the "tap the screen to set up your Windows phone" screen.
No response at all when I tap the screen.
Any thoughts?
There's an empty text file you can put on your sd card that will let you skip alignment, but I don't remember what you need to name it. Try searching for skip alignment in this forum. Also, there's another recent thread in this forum where 3-4 other posters had sudden screen problems with that rom or one in the series. They may have had black screens. The phones still worked, like with MyMobiler, but the phones were messed up. Search for that thread to see if there's any help. This may be return time, I'm afraid.
When you flashed back to stock, did you see the same issues or only on Energy ROM?
I would say try another ROM.
As Ted said, many users had issues like this on his ROMs.
I looked it up, and the file you need is called "welcome.not" (no quotes). Just rename a blank text file that and put it on the root of your storage card.
Here's another thread on screen issues with that rom.
Related
Ok, so far I've dumped the ROM and uploaded the kaiser-HardSPL and all was going lovely. However, after most of a day of pretty much inactivity I find the device suddenly goes very slowly. By which, I mean it can take several seconds to draw the screen.
Thinking this might be a rogue application using up all the processor cycles, I poked it up the bottom with the stick. (While doing this the first time, I held in power and camera just to see the boot loader text, but then I did it again with no buttons held.) It's a Vodafone device but it sat on the Vodafone splash screen for about 2-3 minutes then spent longer than that on the Windows Mobile screen before eventually dropping me into normality.
Except it's incredibly slow normality - I clicked on "start" and after a minute, it's not done anything yet.
Next step is a hard reset unless anyone has any better suggestion?
Help!
I assume you've pulled the battery?
Never assume anything... The full answer is, "No, but I have now"... I'm not sure that's going to do anything more than a soft (poke up the bottom) reset though. I'm now just waiting for the splash screen to subside while I'm typing this.
Having left it half an hour, while it went into standby and after noticing that the clock had stopped updating, I'm of the opinion that the already slow device has got slower...
Ok between 1 and 2 minutes to move from the splash screen to the "Windows Mobile" screen.
Now there's a turn up... After a further minute or so, I get a message, which has now cleared and gone back to the "Windows Mobile" screen before I had chance to copy it here. Basically it said that it had failed to boot either because I'd turned it off improperly or I'd installed something that it was opposed to. I should press send (I guess the green button) to reset to manufacturer's defaults.
Since that's my next stage anyway, I'll re-poke it with the pointy stick and press 'send' when it pops the message up. I'll put my trusty old Nokia N73 into flight mode and take a picture of the message so I can transcribe it here for everyone's amusement.
More news as it breaks.
I've now hit the 'send' button so it's doing a hard-reset. Meanwhile, here's the text it showed me:
Code:
The device is unable to boot be-
cause either you have turned off
the device incorrectly or tried to
install an application from untrusted
source. Press SEND to reset your
device or press any other button
to cancel. This operation will delete
all your personal data and restore
the device to its factory default
settings.
Nice. Ok, I'm at the 'tap the screen to set up your device' screen now.
Wonder what triggered all that nonsense then...
If you're like the rest of us and tooling around the all the fun programs in this forum, there's no telling.
I tell folks on computers, "Every piece of software you put on a machine is a liability to the operation of that machine." We can say that applies to this nifty little devices too.
I've had my phone experience the same symptoms you have posted here. Luckly for me a battery pull fixed mine. Sounds like the luck didn't spread much. Sorry.
Keep at it though. And don't fret the crashes. They do happen from time to time when you play hard.
So, a hard reset and a restore of a backup (Yes, I made a backup a few days ago even though I've been in the trade 20 years!) later, I'm back to normality. All I've done that's weird is install pof's loader and I can't see that's anything to do with it. What I was doing at the time of the slowdown was trying to connect to the wifi network at work. I thought the networking had just got itself tied in knots somehow but as the machine was even mega slow to boot, I can't really see that. At least I can still get back to square one at the moment.
I just need to create a .nbh out of the rom parts I dumped yesterday so that I can recover from anything more major...
Meanwhile, if you do a 'boot loader reset', would you expect it to say 'serial' if the USB isn't plugged in?
I'm starting to wonder if there is a major bug in the WiFi of the Tilt. There are some other threads on AT&T's site about this, and my work with WiFi on this unit has been dicey. Hmmmmm...
Hello Guys,
I started to have problems with my wing and end up in three-color bootloader screen. I can tell you that I am not playing around with my phone. I do not even install any software not to risk its basic phone functionality since I am using this phone as a business phone. So, no crazy rom flash or etc has been done prior to this problem.
My phone started to have problems with answering calls last week. When it was ringing, it was keep ringing and I was not able to take the call even though I was pressing every possible buttons on the phone. It was locking.
I noticed that phone was locking the buttons too. So, I selected "do not lock buttons when the device is off". But, this does not have any effect. Phone was keep locking my buttons.
Last night, I noticed that my phone was unresponsive once again as usual, I soft reset the device, and it booted to the three color screen (I think you guys call this bootloader screen?) where it says "IPL 4.26.0002" and "SPL 4.26.0000". Tried to soft reset probably another 10 more times. same thing...
I took out the battery, went to sleep. Put back the battery in the morning, it booted to the OS and phone is running. But none of the hard buttons were working. It also hangs up the incoming call after first ring. I soft reset the device once again and it went back to the three-color screen.
I went to the Tmobile website, and found that there is an upgrade ROM. I downloaded and ran that program. It said that it installed it to the device successfully, and then the device rebooted itself. Guess what, back to the three-color screen.
I have been reading your forum since morning, and read a lot about brick phones etc. I tried couple of the techniques for recovering brick phones, but nothing helped. Hopefully, someone here can tell me what is going on, even though if the answer is to throw the device to the trash.
Additional Observations
It looks like nobody is interested
I have other observations.
- When "do not lock buttons" is checked, phone starts acting even more weirder. it generates keystrokes by itself. Camera starts taking photos.
- If the battery of the phone is out at least an hour (I don't know why), phones boots fine. If you soft reset at the moment, it will always goes back to the three color bootloader.
Can this be a virus?
A friend brought me a good one today. He has an AT&T Touch Pro with a touch screen issue.
He brought me the phone months ago and I flashed the ROM. All was good. He then deleted a bunch of files one night accidentally and hard booted the phone in an attempt to get the files back. Upon hard reboot the phone hung at the calibration screen and he could not get past that. To describe, the screen calibration works on 3 of the 4 corners, if you hold the press the stylus to the screen quite firmly, but the top right corner will not calibrate however long I told the stylus to the screen.
He brought it to me today and I figured that a fresh ROM would resolve the issue. So I loaded a new ROM and the phone hung again at screen calibration. So I did some research and found a "welcome.not" work around to get us past the screen calibration issue. This was successful and I was able to get us to the home screen.
The issue is that the screen is very unresponsive and I have flashed the device so it's not a ROM flash issue. Is there a driver he might have accidentally deleted that is not reinstalled on a ROM flash? I know I am probably grasping at straws here but I thought this community might have some insight to what the issue is.
I have also considered the idea that I may need to replace the digitizer for this phone if that is the issue and am prepared to do so but thought I would throw this question out to the community for any tips/tricks or ideas you may have before cracking the case on this thing.
Thanks for your help in advance.
--Mike
Oh and I forgot to mention that sometimes the screen works if you tap it continuously but most times, there is no response.
--Mike
Moved as not ROM Development.
Hey Mike,same issue over here.I couldn't find any solutions so far.By the way,what's that "welcome.not" thing?
Well,after some google search i ended up with this.http://bittangents.com/2008/10/28/removing-welcome-message-doctors-appointment-on-pocket-pc-2003/
I suppose that you were meaning that...right?
Check out this one too
http://forum.xda-developers.com/showthread.php?t=355010
The calibration of the screen
IWPantel - Thanks for referring to my blog
To stop the welcome message, you need to put the Welcome.NOT in the root of a sd card or of the device. I don't believe this is your issue, however.
There are typically three reasons why the screen will become unresponsive.
#1 You have a bad touchscreen. Assuming that the screen was working perfectly, I highly doubt this is your issue.
#2 You are calibrating the screen with the stylus straight up. Believe it or not, the touch point changes if you are straight up and down, or if you have the stylus as if you are writing. The angle will affect the touch point.
#3 You have a conflicting .reg file in the Application or Platform directory of the handheld. The calibration settings are stored in the device's registry and they need to be updated. If you did a persistant registry tweak (where it exports the registry into NV ram, the calibration settings will overwrite the calibration settings you create on system startup.
Feel free to contact me with any questions.
-Brent
brentblawat said:
IWPantel - Thanks for referring to my blog
To stop the welcome message, you need to put the Welcome.NOT in the root of a sd card or of the device. I don't believe this is your issue, however.
There are typically three reasons why the screen will become unresponsive.
#1 You have a bad touchscreen. Assuming that the screen was working perfectly, I highly doubt this is your issue.
#2 You are calibrating the screen with the stylus straight up. Believe it or not, the touch point changes if you are straight up and down, or if you have the stylus as if you are writing. The angle will affect the touch point.
#3 You have a conflicting .reg file in the Application or Platform directory of the handheld. The calibration settings are stored in the device's registry and they need to be updated. If you did a persistant registry tweak (where it exports the registry into NV ram, the calibration settings will overwrite the calibration settings you create on system startup.
Feel free to contact me with any questions.
-Brent
Click to expand...
Click to collapse
Brent, I had the same problem here! My Fuze simply stopped responding to my touchs....
#1 Taking this as true
#2 I tried a hard reset, but nothing happens. I can not touch the screen to calibrate
#3 I just can not understand what you proposed.
Please, help me!
I don`t know why, but my cell just back to normal!
Now it's everything working!
@brentblawat - How come you are a Junior Member when your answer is so hardcore.
Anyhows, I have the same problem with my phone, I have tried all the software tricks I could think of. I guess your point 3 asks us to manually enter the calibration data in registry. Have tried it doesnt work.
I cant replace the hardware as I have Tmobile MDA and I dont get the spare parts for this here. the digitizer is different from the one in Touch pro.
I have a device that used to belong to a MSFT employee. At Microsoft you can just hand in your device and they will put a new ROM on it for you. So first thing I did when I got it is to HardSPL (OliNex 1.90) it and load up a new ROM (the one on it was a couple of builds back, and GPS didn't work etc.).
The strange thing is that ROMS seem to be 'loosing' files (as far as I can tell - apps won't open etc.) after a few days of otherwise great operation. If the device is rebooted, it's almost like a hard-reset; although the installation takes next to no time: and it gets stuck on the splash. Hard resetting the device makes it work for a few days more. The device didn't have these problems with the MSFT ROM (which I stupidly didn't backup).
I have tried a few ROMs and they all seem to have the problem:
MagicROM_23541_Sense25_Mar01
TAELROM_v4.23541_SENSE_2.5_28FEB10_LD
Timolol_5100207TH (awesome ROM)
So my current plan:
Flash stock ROM.
Flash stock SPL.
Flash stock ROM (hoping it will clear anything funny MSFT put on it).
Hard SPL.
Flash Timolol Stock-Like (seems to have the problems the soonest - 2 days max).
Does anyone have any other ideas?
Thanks guys.
I assume since you posted in the Touch Pro2/Tilt 2 section, that you own one of those devices. The roms you have mentioned below are (I believe) for a touch pro/fuze device. That could be your problem. Although, I would assume that you have one as I'm sure a rom for a different device would even flash to the device period. If you have the right rom/device combo and its a touch pro, then you should post in the thread for the roms. More details such as network and device will help the most.
Ah crap - the dangers of having too many tabs open. Can I move the thread myself?
moitoius said:
Ah crap - the dangers of having too many tabs open. Can I move the thread myself?
Click to expand...
Click to collapse
i moved it for you good luck at finding a solution
I don't think it's a hot idea to flash the stock spl. I'm not sure that it can be over-written with hard spl-you'll have to ask in the hard spl thread. If you do it, you might be stuck with the stock rom. Just try flashing the stock rom, then going to the custom one you want. That seems to work for a lot of people.
Farmer Ted said:
...Just try flashing the stock rom, then going to the custom one you want. That seems to work for a lot of people.
Click to expand...
Click to collapse
Thanks, that is significantly fewer steps . I will do that for now and report back in 2 or so days...
Small update - just flashed the latest stock Fuze ROM. Just before the customization app come up I saw that device.exe crashed... In any case, I will see what happens with the custom ROM.
You may need to reformat the memory of your phone. Having device.exe crash on a stock rom during bootup is kind of weird. I've never done it myself, but there are threads on it in the Leo forum. I wouldn't try the apps that they've put together, though. I guess you can search around for "Task 29" to find out how to do it properly.
Moved as not ROM Development.
@OP:
If the device was flashed on a regular basis, it's possible that the device flash memory is near end-of-life.
You could try running Raphael Diagnostics on it to see if that sorts it out.
HTH,
What is the lifespan (in terms of flashes) for a device like this?
Plus minus 2 days - it has been able to go as far as 5.
According to this post: http://forum.xda-developers.com/archive/index.php/t-514940.html
These are good options:
http://forum.xda-developers.com/showthread.php?t=435527
http://forum.xda-developers.com/showthread.php?t=491554
This one in particular: http://forum.xda-developers.com/showpost.php?p=3446141&postcount=16 (it applies to Rhodium, but people have had success with it).
Apparently Task 2a (equivalent of 29) is disabled on the OliNex 1.90 SPL - so I can't do a NAND format without reflashing the stock SPL (not that I would attempt that myself in any case ).
I'll run RaphaelDiagnostics and see if that comes up with anything.
Thanks for the help so far guys, I first want to see if the stock flash I did works (I smell a Wiki page).
I tried out the raphdiag-it's pretty cool. I've been having a few weird issues lately on my fuze. In particular, all of a sudden my boot-up time seems to have gotten slow (millisecond to idle thread went from 65-70 sec to 90-95 sec, and I hadn't messed with start up programs). Also, I have been having an issue with files on the main memory becoming corrupted, which has just been weird. Anyway, I ran an 'info 8' with mtty a few weeks ago, and it came up with 7 bad blocks, which seems normal. So, I ran raphdiag this morning, and ran the format nand routine. I was a little surprised, because after running it, I soft reset and the phone booted up normally like after a hard reset. I thought that it was going to wipe the entire rom memory clean, leaving only the radio, bootloader and splash screen. It didn't seem much different from a hard reset. The good news is that my startup is faster. With a setup I was using beforehand, the millisecond-to-idle-thread speed was 76 seconds, and after the format it was down to 71 seconds. However, I ran an 'info 8', and the memory analysis hadn't changed at all (same 7 bad blocks). I'm not sure if the formatting (task 29 or this) is supposed to clear that up, though.
I put both the raphdiag.nbh and a raphimg.nbh on the root of my normal 16 gb card. When you go into bootloader, it does a quick image update (takes about 2 seconds), then the screen tells you to push power for a rom update or push the action button to go into diagnostics. From there, you have maybe 4 or 5 choices. Scroll up and down with the up/down buttons, then push action. The first is a set of hardware tests, the second is something like 'run in/on', which appears to be a test scheduler. The 3d is the NAND format option, and I think the 4th and 5th options are 'calculate rom checksum' and then 'skuid', or something like that. To exit, I just soft reset, or used soft reset/vol down to go back to bootloader. After the format, I tried to flash (I think it called it re-flash), but it said there was no image present. You may need to do this on a clean card to get it to work (that is, format and then flash off the same card without swapping things out).
The diag tests are kind of cool. There's an auto mode that runs through all of them, but you have to do things to get it to work. The first is an LED test. The screen turns red, you stare at it for 5 min wondering what the hell is going on, then push the action button for the hell of it. Then the screen turns green. Push it a bunch more times, and it goes through shaded and checkered screens and whatnot, then it tells you it passed the test. There's a test for the slider, and you need to slide the keyboard in and out. The qwerty test was weird. It's configured for a touch pro (not a fuze), so I didn't know what the hell to do at first. The screen just says 'QWERTY_KBD_1', or something like that. I tried hitting the '1' button, and fn-1, and it did nothing. Then I just hit the top left button, and it said OK and prompted to hit 2. So, you just push all the keyboard buttons from left to right, top to bottom. There are also tests for the other hardware buttons, except for the 4 main buttons on the d-pad (home, back, send, end), which was kind of weird. If you think your power button or vol down button is effed, this tool will confirm/deny it for you.
Right, so the RaphDiag didn't brick your device. It's a bit risky - so I will first resort to less extreme measures - at least I know there is one success story.
I seriously wouldn't worry about it, but you may want to have a card reader available in case you need to remove raphdiag from you sd card to get a flash to work. It's possible that I didn't get the nand format to work properly, but I think I did it right, because the device definitely needed to cold boot. I was just surprised that there was still an OS there.
I'll take your word for it - BUT - in terms of gaining knowledge I am going to try the steps in the posts I found. If the NAND does need a format there is no doubt that I will land up doing it - but I will have first-hand experience.
This really needs a Wiki page once I am done; so I want to squeeze as much info out of the device as I can.
Can anyone else think of any gotcha's before I potentially brick it?
I ran the format a second time. It's really fast; it takes maybe 5 seconds. I haven't figure out how to exit from that part of the diag other than soft resetting, which leads to a cold boot. I'm surprised it's so fast. A hard reset takes about 30 seconds. I guess that it's working properly.
Farmer Ted said:
I ran the format a second time.
Click to expand...
Click to collapse
You are either very brave or very rich . Right, so here is hoping I have to go the final resort route - nothing yet though.
A bit of info to start off:
AT&T Fuze running an Energy ROM (March 10th I believe). No problems with the ROM and nothing changed on the phone before this.
Earlier today I felt my Fuze vibrate in my pocket. I figured it was a text and, because I was in the middle of on conversation, I ignored it. A few seconds later and it did it again. And again. And again. It was putting out these 1 second long vibrations every 2-3 seconds. The screen was black and it wouldn't respond to any buttons at all. Not even the soft reset. I had to pull the battery.
Now when it boots it seems to stay on the AT&T screen a bit longer than normal and when it finally boots up it makes it about as far as the HTC animated screen and then reboots instantly.
I tried a hard reset. It hard locks at the screen that says it is configuring, please wait. Have to pull the battery here too.
I get home and drop it in to the boot loader and try to slap the same Energy rom on it. This time it makes it to the same "Please Wait" screen then reboots. It is stuck in an infinite reboot cycle.
I figure I should try the stock rom and it does the same thing. It gets to the green Windows screen that says it is configuring TouchFLO and then it reboots. As soon as it gets back to that screen it reboots again. Infinite reboot cycle.
I tried the updated Energy ROM. Same issue. At this point I figure it is a hardware issue and it is probably dead. Before I throw it into a wall do you fine folks have any suggestions?
I had that once, too.
Second or third ROM after a hard reset every time worked.
There seems to be something wrong with the ROM you flashed.
Try running task 29. Just put a splash screen in the task 29 folder, run it, then re-flash the nrg rom (or any other rom of your choice). It should fix the problem. There's a task 29 thread in the raph rom forum.
shadow# said:
I had that once, too.
Second or third ROM after a hard reset every time worked.
There seems to be something wrong with the ROM you flashed.
Click to expand...
Click to collapse
I'm on ROM eight or nine now. Same thing. Even the stock ROM. At this point I'm almost convinced it is a hardware issue. Ah well, it was good while it lasted. At least I still have my backup HTC Wizard. That thing is a workhorse.
Farmer Ted said:
Try running task 29. Just put a splash screen in the task 29 folder, run it, then re-flash the nrg rom (or any other rom of your choice). It should fix the problem. There's a task 29 thread in the raph rom forum.
Click to expand...
Click to collapse
Would this be any different than flashing a new ROM at the bootloader?
Taelon said:
Would this be any different than flashing a new ROM at the bootloader?
Click to expand...
Click to collapse
Task 29 wipes the OS partition clean, so you no longer have an OS rom. A re-flash will give you a clean rom, and possibly the bugs will be gone.
Farmer Ted said:
Task 29 wipes the OS partition clean, so you no longer have an OS rom. A re-flash will give you a clean rom, and possibly the bugs will be gone.
Click to expand...
Click to collapse
Excellent, thanks for the info. I'll give it a shot momentarily.
With Task 29 I make it to step 7. and then I can't progress because my reset button is not responding. If I pull the battery and then enter the bootloader I can flash a new ROM but I still have the same problem.
If I use the stock ROM it makes it to the green Windows Mobile 6.1 logo screen that tells me to wait while it sets up TouchFLO, hangs there for a few seconds and then reboots. It makes it to that screen again and reboots. Infinite cycle.
If I use the newest Energy ROM it makes it to the Energy version of that screen and locks up and no buttons, including reset, respond.
Ok, let me get this straight-you ran task 29, and it worked? If it worked, then the device should've flashed, and then re-booted and just hung on the splash screen (no red numbers or anything appears). Then, you were able to re-flash a new rom. Is that correct? But, you run into issues because your reset button isn't working. Well, it sure sounds to me like you've got a hardware (not firmware) problem (edit-duh, just re-read your first post, and that's what you concluded a while ago). Maybe your reset button is stuck. Did you drop the phone recently, or get it wet? Try looking in the hole of the reset button and see if anything is stuck there.
If worse comes to worse, flash back to stock rom and then spl and return for warranty (may be too late for that, I guess) or repair.
Yup, it does look like a hardware problem. I was just really hoping it wasn't. The phone itself hasn't gone through any major drops and has never been wet. The reset button looks clear of debris and I can feel the button push in. Sadly, she is out of warranty. She was a refurb to replace one that had the screen go about a year ago. She was a good girl, I'm gonna miss her.
what do you mean by task 29 ?
where can i find task 29?
Look in the rom forum, just like it says above. Or, and I know this will sound crazy, try searching "task 29".
Same exact thing happened to me. Not sure what causes this...
I was at Bestbuy when I felt my phone vibrate, took it out of my pocket but it was off so I turned it back on and put it back in my pocket. Felt it vibrate again a few seconds later and figured the battery must have died so I took the battery out and didn't turn it back on until I got home. That's when I found out it was doing the same exact stuff as yours, constantly rebooting no matter how many times I flashed it. After many many hours of tinkering I was at least able to get a stock ROM and after even more hours, a stock SPL and call ATT for replacement. $50 and 1 day later, new Tilt 2 at my doorstep