(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.
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 all... got kind of a big problem that i at the moment don't have an answer to,..
inastalled advanced configuration tool 3.2 on HTC Polaris, the first crash i had was when I enabled animation for menus... (the start menu turned black and the polaris froze), but when i managed to start the advanced configuration tool i unchecked it and it was ok,...
the MAJOR PROBLEM accured when I set the touch screen sensitivity, because the touch part of the screen is inresponsive,.. meaning it does not work at all,.. tryed very hart pressing but it doesn't do it.. the problem is because i can't reach eg start menu or the lower 2 shortcuts with hard button cursor (the wheel)... gestures work however, so i can call the touch flo cube but am not able to select anything, and sam thing goes for enetering pin,.. so i'm not able to make phone calls at the moment.. did few hard resets, and uninstalled the adv. conf. tool but nothing helped... can anyone tel me where (and how to get there) can i adjust this back to normal, i wanted to do this in the advanced configuration tool 3.2 but the problem is you cant make any changes since the screen doesn't work,.. same with reinstalling the program, i can select to install it on a card but canot "click" on next since the screen doesn't do it and the hard keys "can't go there"
so really really someone help me please...
thnx
Are you sure you hard reset and this problem went away or did you mean soft reset?
Maybe aligning the screen will help reset the pressure? Click the button in the middle of the wheel and the GPS button at the same time, the Windows align screen pops up. See if that helps.
I find it very hard to believe that you hard reset and the touch screen sensitivity is still not there. That can't be right.
Hi,
thanx for the reply,... another problem that accoured afterwards was that my friend held the end button (wich locks the keys, screen) and the phone was additionally locked... and literally nothing (again NOTHING ) helped, spent 5 hours trying to save the situation,.. i did soft reset (so your assumption was right) but when later tryed hard reset it probably wasn't done since the instructions say you do it with holding gps and iExplorer buttons while soft reseting it... this resulted in getting the "hard reset screen" wich says to confirm hard reset with hitting the send button, wich unfortunatelly i wasnt able to find in hard keys, and nothing else but this warning text was on the screen as well.. so in the end it probably ended upo wit soft resetting it, anyways it didn't help,... i decided to reinstall the rom i downloaded on htc official site,... it went thru ok and the phone is , though out of the box at least functional,... but in the end, i must admit that am a little surprised this happened with this tool pack (i actually avoided altering the registers just in order to avoid this kid of situations since i don't really know much about these things)... was expecting it to work (in my case) a bit better, more stable. All i wanted really was to get a bit louder speaker volume when ringing and ability to alter the HTC home toolbar, since i find the weather screen totaly irreliable and never really use it, so i thought I would have sth there that i might really have some use of..
well nevertheless.. the phone is working, that's all that matters at the mom so i can again start finishing my phd wich i am defending in a week
PS. the fact that you can not do practically anything without the touch screen just sucks big time, if i compare it to the mouse on pc,... i saved the situation many times with the keybord .. in 1 word strange
take care
My Mobile
Perhaps you should have tryied out the "My Mobile" aplication that allows you to use your mobile from a PC.
It shows a windows with the mobile screen and you can touch it and use the mobile like if you was touching the REAL mobile...
Late for that solucion, perhaps another with that problem can solve it this way...
Chears
@gastonfama: am not sure this would help, since a friend that has htc diamond has this tool pack on and it work k ok on his phone,.. that's why i predicted that it is going to be stable enough on mnie as well,.. so in my thinking, if the 2 htc that are rather alike had such different "reaction", than an emulation would be even less comparable to mine, thanks though
Had the same problem with Schaps_AdvancedConfig and wrong HKEY_LOCAL_MACHINE\Drivers\TouchPanel\PressureThreshold setting.
XML I used had "200" as advised value (system default is 2908!),
after changing you could hit it with a hammer and nothing.
Managed to set is back to recommended value 9000 using MyMobiler app and all problems gone.
See also HKEY_LOCAL_MACHINE\Drivers\TouchPanel\PressureThreshold
sys default is 18866, I use now 19866 and I'm happy
Check tips&tricks thread
I got the same problem, I wanna to install "My Mobiler" but due to the screen is locked, I can't continue the installation, any help ?
well as far as I see here (forgot how i installed it after previous post) you have an exe here :
http://www.mymobiler.com/downsafe.aspx
so you will install it from the pc anyways, but how will you make the confirm on where to install it (mybe if you put storage card out and there will be only 1 memory option, but you will still have to confirm installation i guess).. i wasnt able to confirm without the screen on polaris,.. maybo on some other phone
double post...mistake
I had that same screen not working problem after tweaking the phone with advanced config 3.3, 3.2, 3.1, only hardware buttons work.
Problem can only be solved by Hard Reset. Version 2.2 I think is the only one that works (not thoroughly tested though)
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.
I suspect it's a software problem and not related to the hardware models. We have htc inspires though.
Wife and I have identical phones. She came home from work and told me hers crashed; she said she charged it on her way in to work and when she reached to use it saw the root/boot/recovery/whatever screen. (She described it and then when it came up when I looked at it, confirmed that was the screen she'd seen.)
We've got android 2.2.1, if that helps.
Anyway, the phone crashed and won't restart. I pulled the battery out, waited, and popped it back in, and nothing happened. Pulled it out, waited, popped it in, tried the method described here *edit: apparently too new to post links. it was at the htc community.* of trying to bring up the recovery menu. Looks like we have fastboot enabled, which a mod describes as being a known thing. I do the keystroke method as described here, and it brings the menu with the 4 options - reboot, recover, factory reset, and something else, but it doesn't let me navigate with the volume key the way the site and the bootscreen on the phone tell me I should be able to.
So - what went wrong, how can I fix it? I'd rather not have to schlep out to an AT&T store if I don't have to, especially if we can figure it out here. I'd rather not have to do a factory reset, as probably nothing is backed up or saved to the sim, but at this point, I'm worried that's not even an option I can select.
Cliffs:
1. Android phone crashed and won't reboot.
2. Can't make selections in the boot menu using the volume key as I'm supposed to
3. Phone runs through fastboot and fails to start up - I tried the thing I'm supposed to do in response to that as described here *edit: apparently too new to post links. it was at the htc community.*
4. This should be an easy fix / probably something someone here has encountered before.
edit: Don't know if this means anything diagnostically, but while the phone should be fully charged right now, it reads as at 0% when I plugged it in. I figured the utility that measures that probably isn't available at this level in the start-up?
edit2: She mentioned just now that it looked normal when she got up for work. Was at work and tried to use it but it was in airplane mode and she hadn't put in airplane mode herself. She clicked the airplane mode icon to switch out of it and the icon animation just sort of hung. She put it back on her belt like that, it sounds like. When she picked it up again it was in that root menu.
We're not rooted, and these should be vanilla installations.
If this is the wrong place to ask about this, can someone direct me to the right section? I wasn't quite sure where to post this. I reviewed the instructions and did a quick search... but my search-fu might suck.
hello, i have an INCO aurora iis tablet, everything was fine, BUT, suddenly i changed the wallpaper and the next time i turn it on, my screen was black, but no other problems, this happened 3 times, and on third time, i got an error, it says: system.ui has stopped working, i can continue using my tablet, i uninstall a lot of things, cleaned cache, but it still pop up, i was able to play, but the shortcut touch buttons dissapear and appear, but i was using the tablet like that, then it got worse:
next i cant do anything, the error dont stop appearing, i can press quickly some buttons like menu or things and touch on clore the error, and when i tried to change the wallpaper, it said: (name of the animated theme) has stop working, if i dont put an animated background, the tablet reset, then of course, it got worse, i cant tap on anything, the error is so fast i cant press nothing, and if i managed to tap on config or something, tablet restarts, i installed some programs on my pc, and i was able to backupp my images and some other things, BUT
this is the main problem, it will be short:
my tablet isnt rooted, and there is a game called teaching feeling, that i couldnt find the game data, it is there, on my tablet, but i think i need to root my device to get them, but, i already read some info here and around the web, that i can backupp that stuff using adb, but my windows xp isnt the best for that, i use a windows 7 pc and cant do anything, when i run 'adb devices". it dont show nothing or it says it isnt a command or something like that
the question is: i will be able to backupp that game data?
2 what causes the error? i uninstalled all google updates and some of google software, but it didnt fix anything
actually the tablet dont go beyond the inco logo, it keeps restarting, hard reset will fix it?
but , i cant hard reset everything and lose my important game data sorry for my grammar and the long post, thank you for your help.