Hi,
I have an ipaq hx2790. Last time, it was completely out of battery ( this happened several times before, with no troubles at all). I charged it overnight.
After fully charged, I turned it on. It turned on normal. But when status bar ( the small bar running left from right when booting) run for about 1/10 of the whole bar. The screen slowly appeared small dot with different colors, and then lines, after all, it became green-dark color with vertical lines.
I tried to soft-reset, hard reset. The same thing happen. Funny thing is, when I connect this device to my computer, I can still browse it folder, SD card through Windows Mobile Based Device in My Computer.
My hx2790 is preload with WM5
First, I thought it's something to do with software. But after soft-reset, hard-reset, same thing happens. I tried to install WM5 official rom for hx2790 from HP. No thing changes. Screen ok at the very first part of boot up. Getting worse after that. I can still browse it folder from computer.
P/s: It was once, booted normal into windows mobile screen (but after about 5 seconds, its screen slowly become worse).
Anyone have any ideas what's happening?
Thanks.
You can try to flash WM6.1 for HX2000 series to see if the same thing happens:
http://forum.xda-developers.com/showthread.php?t=383173
If there's the same - then probably LCD is bad or there's something wrong with motherboard.
I'm downloading the file.
I dont know whether it's LCD problem 'cause when at the very first of booting and in Pre-BL mode, it displays perfectly. Especially in Pre-BL mode and during the ROM update process, nothing's wrong with it.
I'll inform the result with this new ROM soon
Thanks.
Ok
I have had similar problems when there is something wrong with Windows upadate (ROM) file. Screen just fades out on starup
ROM Update was successful but can't help
So, I decided to try Ultimate X2 BetaII. Here's my problem:
I decided to flash to OEM ROM first, as I've read this is better with some ROMs, but I think I did something stupid. Instead of using the .exe file to install (_ATT Tilt_RUU_Kaiser_CINGULAR_WWE_3.57.502.2_radio_sign_25.88.40.05_1.65.21.18_Ship.exe), I decided I wanted to install with my SD card, so I extracted the .nb file (KaiserIMG_CINGULAR_WWE_3.57.502.2_radio_sign_25.88.40.05_1.65.21.19_Ship.nbh) and renamed it "KAISIMG.nbh" and copied it to my SD card. I installed with the standard SD card method, and now I'm stuck at a (seemingly) endless screen alignment that loops over and over. The only posts I've found so far on this topic seem to deal with hardware issues, but my screen has worked okay until now, so I'm guessing I screwed something up software-wise by impatiently trying my own idea, instead of following instructions.
Mind you all, this is only my second attempt at flashing a ROM, and the first one I flashed was months ago, so you can consider me somewhat of a newb.
By the way, I just tried going through the screen align twenty times to see if there was any change, and I'm still stuck there. I haven't tried making a welcome.not file yet, but I'll give it a shot now. It seems like even if that works, there should be a way to fix my problem properly. Any ideas?
welcome.not
Welcome.not does get me past the align screen and into the Ultimate X2 Beta II ROM. This does, of course leave me unable to align my screen with the WM app. Still looking for a "proper" fix.
Did you try a different ROM?
RE: Did you try a different ROM?
I first had the screen alignment problem after flashing the OEM ROM. Afterward, I flashed Ultimate X2 Beta II, and the problem persisted. I flashed back to OEM, and the problem was still there, so I flashed back to Ultimate X2, and after conferming the existance of the same issue, I used the welcome.not bypass. I suppose this will be okay, if I can find another way to align the screen, besides the WM screen alignment utility. I saw a post regarding a possible Reg key that changes the max screen alignment repeats. Perhaps altering that key would make it save my initial alignment and end the infinite loop?
P.S. Does anyone know of a screen alignment utility that works from the device and saves the settings, a way of working around the WM utility?
Registry Keys?
Are there registry keys I could alter to fix my screen alignment?
You do have a correct HARDspl right? When you enter bootloader you should see hard spl. Flash another spl and see what happens. Sorry im not of more help but im on my phone.
I have HardSPL 3.29. Ultimate X2 Beta II is running quit well. Radio's working fine, too. I just can't figure out my screen alignment issue. If someone could hook me up with a screen alignment file or registry settings, and perhaps clue me in a little on how to implement, that would, perhaps, be a temporary fix.
Well then think old school. If the cross is moving when you press it i would think the digitizer is ok. So clean the edges around the screen really good. Maybe some lint or dust around the edges. Also maybe loosen the screws on the back a little in case the screen is in a bind.
Yeah, I think the digitizer is fine. I already cleaned the edges with a business card. I don't have a torx kit with me, but I'll keep the screw loosening in mind. I figured the problem must be a result of extracting the .nbh file from the OEM install file, rather than running the .exe. However, flashing again (I used the .exe files for the OEM and Ultimate X2 the second cycle of flashing, rather than using my SD card) hasn't helped. I ran across the following thread, and am downloading the app now. I don't know if it will help, but maybe if someone else runs it and extracts their alignment settings, they can post them for me to try out?
http://forum.xda-developers.com/showthread.php?t=396466
Reg Key
Here's another instance of the same type of solution:
corollatercel said:
So i've been having problems with the screen alignment on mine since i had one spot on my MDA screen that was dead and my screen was cracked so the alignment wizard basically got stuck in limbo when I tried to calibrate it. SO basically what I had to do was download PHM Registry Editor and change the registry key touch referenced in here.
kernelguy said:
My touchscreen had a crack only at the bottom. After skipping the 'align screen' during initial ROM load, I lived with a non-functional touch screen for a day or two. I then remembered the post from equinoxe that had registry settings for his phone. I took those settings and updated my registry. I now have a decent touch screen - at least the top 3/4 works fine.
The key and settings are:
[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\TOUCH]
"CalibrationData"="1922,1957 3330,639 3317,3276 600,3230 609,677 "
I could surmise that the screen is being treated as a square of 3900 x 3900 dots. 0,0 seems to be the top, right corner.
kernelguy
Click to expand...
Click to collapse
Afterwards I used the remote alignment tool (attached) to retrieve the correct settings from the correctly aligned mda(after changing the registry key then rebooting the device) then made sure the file was saved on my pc....normally it's saved by default in the C:\Program Files\Code Factory\Remote Screen Alignment directory. The file was called WIZA200.dat. I did a soft reset then when the alignment screen came up I did the skip function in the remote screen alignment application and it automatically read the proper calibration from the wiza200.dat file and then properly calibrated my mda now my screen is properly calibrated even though i never ran the alignment wizard.
So here are the Instructions folks:
1. Download the latest activesync and connect your mda to your computer and verify your device is connected(not as guest)
2. Perform a soft/hard reset on your MDA then tap your screen to start the screen alignment wizard
3. Download the remote screen alignment tool attached and install it on your machine.
4. Download the wiza200.txt file attached and rename it to WIZA200.dat then put it in the C:\Program Files\Code Factory\Remote Screen Alignment directory on your computer
5. Ensure your MDA is connected to your pc(A green activesync Icon usually indicates a connection )
6. Open the remote screen alignment tool on your pc meanwhile your phone be displaying the alignment screen wizard.
7. Click SKIP in the screen alignment tool.
Assuming everything went fine a message box displaying "The operation has been completed successfully. Your device will be restarted." should pop up on your computer and your device should restart. Afterwards your phone will run the files it always does when you do a soft/hard reset then you touch screen should be properly calibrated and work fine.
Click to expand...
Click to collapse
If someone could do a fresh, accurate screen alignment and report the registry key settings, I could try editing them for myself and see if that does it.
check your pm
check your pm
Thanks!
Thanks for the help, guys. I found the kaiser.dat file in the program's directory, opened with notepad, and copied the string into the appropriate reg key:
2002,1944 3292,635 3352,3272 681,3268 624,673
Thanks, lewnetoons, for providing your info, as well:
1862,1960 3131,673 3129,3260 628,3291 635,655
I suspect my digitizer may need replacement because it wasn't terribly accurate before I encountered this problem, but I'll have to find a proper solution for the "Align Screen" loop for a new digitizer to even matter. This is enough to appease me for now, as my screen is now responding semi-accurately, but if anyone can come up with a fix for my align screen loop, so I won't have to rely on the "welcome.not" fix, I would appreciate it a LOT.
A little off-topic, but it seems to me that five points isn't enough to align the whole digitizer in the first place.
Thanks a lot, guys, I'm good for now.
Bob_Beard said:
Thanks for the help, guys. I found the kaiser.dat file in the program's directory, opened with notepad, and copied the string into the appropriate reg key:
2002,1944 3292,635 3352,3272 681,3268 624,673
Thanks, lewnetoons, for providing your info, as well:
1862,1960 3131,673 3129,3260 628,3291 635,655
I suspect my digitizer may need replacement because it wasn't terribly accurate before I encountered this problem, but I'll have to find a proper solution for the "Align Screen" loop for a new digitizer to even matter. This is enough to appease me for now, as my screen is now responding semi-accurately, but if anyone can come up with a fix for my align screen loop, so I won't have to rely on the "welcome.not" fix, I would appreciate it a LOT.
A little off-topic, but it seems to me that five points isn't enough to align the whole digitizer in the first place.
Thanks a lot, guys, I'm good for now.
Click to expand...
Click to collapse
glad you got it fixed my brother
It occurs to me that I may not have been clear in my first post. I didn't use NBHExtract or anything. I opened the exe with 7-Zip, extracted the larger of two nbh files, renamed it, copied it to my SD card, and flashed it to my phone. I don't know why I did it that way, and it seems like it sort of worked, but something was lost in translation. I've done half a dozen or so flashes since then, but the problem still exists. Any insight into a possible permanent solution for this semi-permanent problem would be very much appreciated.
So, I've gone through a few flashes and my screen alignment still works for the most part, but it can be a pain in the ass using programs that have have small expandable menus or buttons at the bottom of the screen. I can fine tune this a little better using my slow, primitive hand-modify the registry method, but I would still appreciate any input on fixing the problem.
I guess I'm looking for one of two possible solutions:
1. A program that does exactly what the built-in screen alignment utility does.
2. A way to fix whatever I ****ed up, so I can use the screen alignment utility without it looping infinitely.
So, once again, does anyone have any helpful input?
Bob_Beard said:
So, I've gone through a few flashes and my screen alignment still works for the most part, but it can be a pain in the ass using programs that have have small expandable menus or buttons at the bottom of the screen. I can fine tune this a little better using my slow, primitive hand-modify the registry method, but I would still appreciate any input on fixing the problem.
I guess I'm looking for one of two possible solutions:
1. A program that does exactly what the built-in screen alignment utility does.
2. A way to fix whatever I ****ed up, so I can use the screen alignment utility without it looping infinitely.
So, once again, does anyone have any helpful input?
Click to expand...
Click to collapse
try flashing abu's new rom that doesn't require screen alignment. see what happens.
I flashed it within hours of its release, but I'm not sure how it's affected me, since I still keep "welcome.not" in the root directory of my SD card, and I input my alignment config into the registry after every flash. I may expirament with it, though, by removing "welcome.not" and/or reflashing.
Bob_Beard said:
I flashed it within hours of its release, but I'm not sure how it's affected me, since I still keep "welcome.not" in the root directory of my SD card, and I input my alignment config into the registry after every flash. I may expirament with it, though, by removing "welcome.not" and/or reflashing.
Click to expand...
Click to collapse
yeah give it a try and see what happens
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.
Hello, I have a XDA Orbit 2 (screen res 240x320). I wanted to install Android on it. I did a quick search and found a few things....
My Tutorial:
http://forum.xda-developers.com/showthread.php?t=625200
I had a read though that. Got a rough idea on what I was doing.
(1º CHOOSE YOUR ANDROID BUILD) I decided to use:
Warm Donut (Donut): http://forum.xda-developers.com/showthread.php?t=619980
(2º INSTALL THE OS LOADER TO NAND) Now this was my problem, I visited the website "http://it029000.massey.ac.nz/vogue/files/?C=M;O=D" to choose my .NBH file. I choose the latest ones. And the selection was:
polaimg-panel1-320-08-04-10.nbh
polaimg-panel2-320-08-04-10.nbh
polaimg-panel3-320-08-04-10.nbh
I tested ALL 3 and non worked (unless I was doing something wrong) all i got was when it restarted it went to a fizzy kind of screen then came straight to a white one.
But I did try another .NBH file what was near the bottom called "polaimg-240x320-03-02-10.nbh " that didn't work but it was close.... when it restarted it vibrated once then went to a black screen then vibrated twice then came to another screen with a animal in the top left and under niethe they was loads of white numbers letters scrolling down the screen then it just got stuck on that and nothing happened from there.
EDIT:
I have got a bit closer now. I decided to try run it through haret, Well... I click Run. see black screen with letters scrolling, I get to the bit where it says "Hold down Volume Up or DPad center to launch installer. And before I have chance to do that this appears under:
Code:
sh:2: unknown operand
losetup: /dev/block/loop 1: No such file or directory
Failed
Failed to reach system.img on SD card.
Can anyone help me? or point me in the right direction to get android installed on my xda orbit 2?
Thanks, James
Just try a earlier nbh i use polaimg-panel3-320-29-03-10.nbh most of the later ones have either problems with sound or wifi.
If you get a white screen it's prob wrong panel depends on you phone pola100 or 200.
Thanks, But I have tried that.
I have a new problem now. Might be easier to solve.
can't anyone help? kinda in a rush for it.
Hi,
i had the same problem with another build.
You should try to get into the installation menu and install Android.
This helped for me.
I found the solution here on xda-developer.
Since I am too new or too stupid to post a link the post seems to be this one:
showpost.php?p=5602064
Have fun,
René
People, I've tried a bunch of assemblies and options for your phone after the display is changed to the Chinese and found that only 3 boot penguin display and inscriptions at boot true test, with those two idit load equally, and one with the other inscriptions but also hangs. These feeders: 1) polaimg-panel3-240x320-2.6.32-froyo-06-09-10_22 2) polaimg-panel3-240x320-2.6.32-froyo-09-09-10_21 3) polaimg-panel3- 240x320-2.6.32-froyo-27-08-10_23.
All three normally pick up the screen but the writing bug usb_vsync.
Founded on the Internet has the very first assembly androyda, who works in the demo rezhime.Reshil try to install it and wonder, android has started without any problems.
Here is a link to the installation package that will install this demo on your phone: hxtps://rapidshare.com/#!download|304l34|123389441|RUU_Polaris_Android_DEMO_v1_0.exe|72394|R~EC5F7C5EBDDD628BF8BFF91F71607033|0|0
Those who say they say android does not support Chinese screens, just a lie or do not know. At this assembly it is clear that androyd runs perfectly, and on the phones with a Chinese screen.
Most likely, DZO, or what the other developer of the kernel is not corrected. Suggest to write a petition to save money and to develop a normal boot. Let's say it can do the same DZO or what the other developer. I do not think it would be very difficult and time consuming. Who can help me in this, please come forward!
But there's more, I decided to try to run through the HARET andriod 1.5 on the same firmware WM and you think, android has started well!!
At the moment, try to build a working version of Ecler, I do not know whether I can or not but the fact that at least 1.5 works already happy!
That it happened. All the same I managed to run Android on my devayse 2.1-2.2. Of course there are problemma, and a large - is not responsible for nozhatie touch screen, but the fact that he obsalyutno normally displays everything on the screen is great plshyusom and proves once again that all the matter in the loader, which local craftsmen or they can not fix! !
Below we will explain how to start. If you do not get something right the first time, try again, I got yed)
1) Download the assembly android_by_polyrhythmic-beta3.zip (Look on the internet, I think problemma not be found)
2) Download the assembly polymod.rar.
3) Unpack android_by_polyrhythmic-beta3.zip and copy the folder on the SD android.
In the folder are 2 files android default and default-s, files and zImage-15-12-09 and zImage3. The file default by one run android in Haret changing the panel on 1,2,3. Each time you start when you have to wait for the LED zamegaet either blue, green or yellow, and goes off the screen. This would mean that the android booted and shut off the screen. After clicking on a retreat or off you will see a white screen.
After running all three panels so turn off your phone zaydmite to stick and move to folder android Fail of the default-polaris zborki polymod and change it to default. Replace the old Fail them, and then rename the zImage-15-12-09 in just a zImage. Now run the android. Wait until you have a light starts blinking LED goes off and the screen. As it happens, click on the rebound a few times. You will see a line of code and then the welcome screen android. Since the touch screen is not working I could not go further, but pressing the buttons can be issued to the soglashatsya message.
Here vprintsype all.
Try it. The point I was told, then I welcome your ideas and results!