(First off, sorry that this is all jumbled. This is a post mixed with another post I made on another forum, and I've been trying to figure this stuff out for hours now and I"m just burnt out.)
Might need to reinstall Windows Mobile?
I was told maybe the previous owner tried to flash them to a different ROM and had a problem. I'm not good with Pocket PC's, so I have no idea.
When I do a hard reset, it does the whole reset thing, makes me click the middle/top/bottom to align the screen, teaches me how to cut and paste, makes me choose my time zone, then loads up windows. I can see the start menu and all of that for a couple seconds, then it goes to install certain things. I think when it goes to install macromedia flash, it gives an error about it might have errors because it was made for a previous version. Then, after that, regardless of whether or not I cancel the flash install, it reboots and then ends up back at the dumb screen with the wireless-type icon, with no start menu where I have to hold a round button and press the middle button to get the start menu.
I got two X30's and a charge dock for $5. But, I didn't get any disks.
When I start it up I get the following error:
Tour Error
(System) Could not load remote XML file: [183]
The main thing it's stuck at is a screen that either says "charging..." (orange) or "ready." (green), with something that looks like a wireless logo. The bottom left has
Version 1.5.6
Dell Axim X30
Untagged
The bottom right has battery info.
I manage to get things to show up, even got one of them to use the net, so they're not bricked or anything.
However, there's no Start menu constantly on the screen, I have to hit any one of the four round buttons then the button in the middle to bring up the start menu. I guess the start menu is supposed to be at the top of the screen, but like when windows on a regular pc starts to crash, all that's there is whatever was last on the screen. Right now after opening it, I just see Today and part of ActiveSync. The windows all seem to be doing the same thing, as where when I try to get rid of something it just won't go away, and things keep stacking.
I've tried a hard reset, I just get errors. It's kind of odd how both can have the exact same problem, but that's what it seems like to me.
I've tried googling for hours, haven't found anything. I'm not even sure if I can buy windows mobile seperately because I haven't found that either.
Anyone got any ideas? If the windows installs are just completely corrupt, I wouldn't have a problem using linux or something else.
I've never had a Pocket PC before so I'm not really sure what other types of info you'd need, but if anything else is needed just let me know.
Not sure if this is relevant but i have used it on my Alpine to remove the network specific customisation so it might just be worth a shot.
Once you have done the hard reset thing and when it says "Customisation in 3 secs" or something similar, do a soft reset. That should stop all the stuff in the ExtROM from running and leave you with a totally vanilla WM install.
The fact both are exibiting the same probs implies, well to me anyway, that the previous owner tried the same ROM on two PPCs.
I've got a MDA which has a broken lcd. Its just cracked slightly, but still displays fine. I did a Clear Storage and now the phone has reset and is giving me the "tap here to set up your device" wizard. I need to bypass this and any screen alignment that may come up since the LCD touch feature no longer works. I've done it before when I got the phone, but I cant find the thread nor remember the steps.
Any help is appreciated.
you really can't. i heard theres a way you can flash a rom where the config has already been done, but i don't remember where i saw it
fzzyrn said:
you really can't. i heard theres a way you can flash a rom where the config has already been done, but i don't remember where i saw it
Click to expand...
Click to collapse
create a file on the root of your storage card called welcome.not
TylerC161 said:
I've got a MDA which has a broken lcd. Its just cracked slightly, but still displays fine. I did a Clear Storage and now the phone has reset and is giving me the "tap here to set up your device" wizard. I need to bypass this and any screen alignment that may come up since the LCD touch feature no longer works. I've done it before when I got the phone, but I cant find the thread nor remember the steps.
Any help is appreciated.
Click to expand...
Click to collapse
I believe this should help you.
http://www.freewarepocketpc.net/ppc-download-my-mobiler-v1-2.html
At least I hope it does.
Just create a file named WELCOME.NOT on your storage card and do a hard reset.
HI , I had this problem with all my old crashed PPC ,,, so delete this file and reboot ,,, /Windows/Startup/Welcome.exe
U can use the "Activesynce Explorer to browse the Windows Directory
Enjoy..........
use "Remote screen alignment" tool and bypass your start screen easily. search this tool in forum. you will get it easily..
Regards
welcome.not and http://www.freewarepocketpc.net/ppc-...iler-v1-2.html
THANK YOU SO MUCH kfletch and le_cactus. I'm not sure which of these worked since I did both but the welcome screen FINALLY went away. it took a while. i had to install the Mobiler software and I had problems getting my ActiveSync up but I created the welcome file by going to the desktop of my pc, right click, new , text document, i changed the default name "New Text Document.txt to Welcome.not" then I right clicked to copy it. Next---Once the Microsoft Activesync came up, I clicked on Explore --> My Windows Based Device ---> Storage Card then I selected paste to paste the welcome.not file. After this it gets a little tricky because your device has to sync again to filter the file back down to the phone. This took a while. Then after a few resets, the Mobiler software finally read 'connected', then it gives you a screen shot of your mobile device, i did a soft reset a few MORE times and it worked. It's not as cut and dry as previous posts made it sound. it's a pain in the butt.
My touch screen (T-Mobile Wing) stopped working after I used it in the bathroom while in the bathtub (I don't know what the heck I was thinking), well later that day the screen stopped working and the genius at tech support had me do a hard reset and software upgrade, which did NOT help. (whatever you do, don't call tech support, especially if the white dot beneath the battery is another color---you're screwed!!!)--AFTER tech support messes up your phone they won't bother to help you if they think it's due to water damage! I'm going to see if I can locate the forum regarding reloading the touch screen drivers. I think that may be the problem.
thanks dear I try i350 gSMART and working.
how do you select "YES" when mymobiler tries to install on the phone?
my screen is also broken, and i bypassed the welcome screen, but when i tried to install mymobiler, i cannot let the phone install remote.exe
any help?
this is ur answer
go to this its my room iam build it and not have align screen
http://forum.xda-developers.com/showthread.php?t=546422
Thanks a lot folks from XDA! I had screen broked and this works just fine! Cingular 8125 WM5. tks
ah_hin said:
how do you select "YES" when mymobiler tries to install on the phone?
my screen is also broken, and i bypassed the welcome screen, but when i tried to install mymobiler, i cannot let the phone install remote.exe
any help?
Click to expand...
Click to collapse
Buy a not broken screen
HTC TYTN(Hermes 200)
Hi there i have an HTC TYTN, happens that i'm suposed to have the same problem (maybe broken screen).
The phone was working fine untill today.
I can't bypass the screen alignment; i tryed both ways.
What can i be doing wrong?
Thanks in advance.
Bypassing with "logic"
Hi there;
In my case; i found a way to bypass it.
My screen has a 4mm scratch in the top left of the screen.
so i just pressed the bottom of the cursor (NOT IN THE MIDDLE WHERE IT'S SUPPOSED TO PRESS - "in the top left cursor" - where the scratch is)
after that i could use my phone again.
Also after this try finding the correct registry screen alignment and save it.
It will work properly.
welcome.not works for TyTN II with unresponsive touch screen . Blank micro SD card with just one blank file welcome.not. You can insert the sd card just before you hard reset
It worked in OMNIA II and passed the screen calibration..Thanks a lot guys!!!
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
Hi all,
I bought a second hand Raphael on eBay. The previous owner said he flashed WinMo 6.5 and a HardSPL. Something seems to have gone wrong somewhere, because WinMo starts up and shows the welcome screen and then the touchscreen alignment dialogue over and over. As soon as I touch all five points, the alignment process starts again.
I have already re-flashed WinMo 6.5 an 6.1 with the same results. I have also added a WELCOME.NOT file and tried a soft reset. The file just disappears after the reboot.
The boot loader says as version numbers:
R 1.14.25.05
R 52.63.25.34u
D 5.00.00.00
I'd be glad for any pointers. Maybe a pre-calibrated rom?
Also, I actually want to run Android on the little fellow. Could I just try to flash LightNHB and run Android from there?
Thanks for your help.
Regards,
Kevin
That's not the bootloader screen numbers, but I don't think that's the problem. It may just be a crappy rom on there. Getting to the alignment screen is a good sign that the device isn't bricked. I would say just flash another rom; use one of the android-starter roms if that's what you want on there.
Thanks for the answer, unfortunately it seems the touch screen is broken
I managed to install Android using LightNHB, worked a treat. Androids calibration screen seemed to take all five poinst, but the coordinates it printed out where all on the same y-coordinate. The touch screen doesn't work in Android after that (I mean, how could it ).
I'll have a look around to see if I can buy a new screen for cheap.
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!