Since this weekend my Himalaya hard-resets itself frequently. Before that I cannot remember when i last had the last unexpected hard-reset.
Nothing has changed in configuration or whatsoever.
I am running the 1.72 ROM
Any clues??
The obvious one would be faulty battery, loose battery,...but that would show up in the backup battery.
Do you restore each time ? thus restoring the problem?
or do you start from a fresh install?
I restore, but the basics of the backup are now 2 months old.
Havent had an issue at all in that period, until this weekend!
It's not my battery thats mal;functioning / empty. Could be loose contacts though (but then: wouldnt the backup-battery pick up then for some time).
Wisbar installed ??? this application sucks , it always makes Hreset on my device ....
no suspected apps installed. Agan: This exact config has been running without issues for months!! And now suddenly two spontaneous hard resets in 4 days.
new sd card has been mentioned as a cause of problems.
SD has been in there for more than 2 months also . . .
realy: nothing was changed (literally: when it resetted, it was on the table during weekend or in my pocket at work . . .)
I have the same problem recently. I sent it to the O2 workshop & the diagonse is faulty RPL connector. It was replaced & everthing is back to normal.
Related
Hi everyone, I'm new here, couple of weeks ago if you'd asked me what a prophet was, I'd I've talked about religion. I was given a hand-me-down imate jamin that i"m trying to get working properly.
The prophet in question was previously working properly without any issues, the previous owner had just gotten a new battery for it when the issues started. The phone slowed down to a crawl, nothing could get done with it, takes like 1 min to open a text msg, around 10sec to answer a phone call. Having gotten it and thinking its a firmware problem, I did a hard reset, nothing, then I upgraded the firmware to the latest JAMin_WWE_213923_2139123_022021_ship.zip again, nothing!
Funnily enough, this behaviour is erratic, do a soft reset, load sktools and the cpu usage app reports that all is fine, give it some time then ka-boom! the cpu usage gets maxed out by device.exe seemingly for no reason.
Anyone here ever seen behaviour like this? If you have or just have a suggestion on what I can try, please post. I'm not sure what to do now since I'm on the latest firmware and I don't know where I can get a rom for wm6 for the phrophet. I"m hoping upgrading to wm6 will fix this issue.
Thanks in advance.
John.
device exe
Same problem with my HCT Diamond.
Dia Duit Rom.
Trying to find a solution!
Firmware
You could try a cooked rom, but make sure you perform a hard SPL first as this will save your prophet from bricking.
The other thing is have you tried a different battery as a bad battery can seriously affect the phones performance espcially if it is a cheap copy.
If your'e worried about flashing have a deep read of the following link
http://wiki.xda-developers.com/index.php?pagename=HTC_Prophet
Hope this helps
Sorry mate, just seen your reply.
The phone eventually died, won't charge, nothing doing, looks like its bricked. I moved to a Kaiser, which then started having 3g problems, though I got a temporary fix by keeping it on 2g.
Now I have a mytouch which needs unlocking. I think me and htc should part ways, I'm yet to have a simple good time with any of their products.
As regards the prophet... is there a way I can resuscitate it? It wont' charge, no light shows either on usb or charging from a normal charger.
Thanks
John
It's not like that. HTC phones work good as long as you keep them good. I'm not saying you didn't keep it good but maybe some softwares ruined your Pocket PC. ANytime this happens, a hard reset and revert from backup should solve most of your problems.
Looking at your Prophet, smells like the battery is dead? Try changing and see if that helps.
Regards,
Carty..
This looks like a day that is going to be special. This phone has been in my drawer over a year now, I'd given up on it long ago. Well I stripped one of my old chargers down to the wire, charged the battery manually for a few mins and presto the phone has come on.
It's still slow as hell, so I see device.exe is still hogging cpu.
Time to review the prophet roms, been a while since I checked on it.
happens the same to me too
for me this issue rises up when i connect with my pc :S
due to the calnot or calpd or poutlook or someother exe ... it streches the cpu usage to a 100%
some ppl say that having the correct time zone helps u out in both, the pc and ppc solves the issue ... well i have windows 7 (UTC) and in ppc (GMT ... using http://forum.xda-developers.com/showthread.php?t=401161 ) does it make any difference ?
now the only option i got is to either hard reset although this happened with my previous ROM too :S
All,
I have had issues with my factory (1.14) ROM for my HTC Touch which resulted in the points outlined below. I thus decided to upgrade to the new official ROM (Orange HTC Touch HD ROM Upgrade 1.59.61.2) in the hope it would sort it out. However, it does not - symptom indicator is in the screen shots below.
I cannot find any threads on this matter, unless I am missing something (?), so I would appreciate some help from members here as I have seen occure in the past on my old Trinity model as well so it must be WM6 related and not ROM related.
1) I just upgraded my 1.14 ROM to the new ROM version and within 2 months I had trouble with it corrupting the internal MicroSD card.
This resulted in a format and reinstall of all data.
2) The Phone ROM seems to get regular corruptions on the display after a period of time where the Task Manager (upper right - see screen shots) has missing icons.
The resulting workaround is a reboot.
3) Same corruption issue causes the Wireless Internet to not work correctly.
The workaround is a reboot.
4) Sometimes during calls the phone will drop the call for no reason and it is found the same corruption has occured.
I never had such extensive issues with 1.14 except the minor corruption of the Task Manager so am very annoyed. Anyone else had this? By the way all data was backed up before any upgrade. The ROM worked for 2 months before it corrupted as above.
first up, i dont know about the data loss.
maybe rubbing salt into the wound, but they do say to ensure all data is backed up before flashing any device (be it pc, phone, or anything else).
did you flash with SD card removed?
the other faults sound like you need to perform a hard-reset.
i tend todo this twice, immediately after each other.
See my comments above
Bump as information has updated (25/01/10).
hi all, i resently got the hd2, updated it with the new rom, and thereby hoped to be free of errors... however i seem to experiense a whole lot of error, more than i had expected... sometimes it wont come back from sleep, it only turns on the backlight of the hardware buttons. then i have to kill it by removing the battery. also sometimes it wont establish connection to the net, then i have to turn off the radio and turn it on again. the phone is 7 days old, and i have had the battery out 20 times allready... is this unusual? should i contact htc? and what are your experiences with their support?
Samoht2003 said:
hi all, i resently got the hd2, updated it with the new rom, and thereby hoped to be free of errors... however i seem to experiense a whole lot of error, more than i had expected... sometimes it wont come back from sleep, it only turns on the backlight of the hardware buttons. then i have to kill it by removing the battery. also sometimes it wont establish connection to the net, then i have to turn off the radio and turn it on again. the phone is 7 days old, and i have had the battery out 20 times allready... is this unusual? should i contact htc? and what are your experiences with their support?
Click to expand...
Click to collapse
I would recommend a hard reset and not installing any software or doing any "tweaks" and test that for a bit.
You should find that fully functioning and stable (on 1.66 ROM) from there add the software that you need and see how that goes and don't bother doing the treaks, registry hacks unless
a) you know what your actually doing and what it changes andb) you actually need the change.
ok, I'll try that is the new ROM from htc that unstable?
as above.... test it with just the 1.66 rom, nothing added, and if it's still unstable get it replaced under warranty.
1.66 ROM is also unstable...
..or if I may refraise: Using ROM 1.66 is no guarantee for stability. My HD2 crashes or locks often when I use the phone functionality. No program or app have made the phone crash. I have tried to monitor what apps are running but I´ve not been able to conclude anything. Hard reset has been done followed by a backup restore.
Now I am uninstalling programs each at a time to see if this improves.
dont restore your backup, there could well be something in your backup causing a problem.
(depending on what you have backed up)
hard reset, or ideally task 29 and reflash then just use it as it is.....
use ms myphone to backup your contacts and sms if you need to.
I recently noticed that when I remover the battery for more than a minute, the clock (after starting up) would be late. The more I leave the battery out, the more the battery will be late. I recently tried several Android NAND roms & WP7. I have returned back to WM.
I don't remeber noticing this before, I have Hard-Reset the phone, re-flashed, HSPL, Task29, and still the same.
Is it my HD2 only? a Hardware problem (covered by warranty)? Or is it something normal?
Thanks for any feedback.
The internal battery on the board of your HD2 has run dry. You can send it back to HTC to get it repaired...but really all it does is run the internal clock, so it's not a huge deal if you can stand resetting the clock when restart your phone.
I was suspecting this, as I faced it with my Tornado. But I didn't read about any user with an HD2 who complained about it.
Any idea where I can buy one to try to replace myself?
omar302 said:
I was suspecting this, as I faced it with my Tornado. But I didn't read about any user with an HD2 who complained about it.
Any idea where I can buy one to try to replace myself?
Click to expand...
Click to collapse
It's not possible to replace it, unless you buy a new phone, because it's not really a battery, it's more like a small chip and its fix integrated on the motherboard. There's no way to change it without buying a new motherboard. I would say, this problem is not big enough to pay so much for it. And maybe you could think about it, if it's necessary to remove the battery. Unless you want to replace the SIM Card you don't have to. SD-Card Slot is not under the battery and for rebooting you have a reset button, and if you have to flash your phone, you have to set up everything so it's not a problem to also set up your time ^.^
Best regards
Is it something that should be covered under warranty?
I baught my HD2 from Clove.co.uk from 1 year back & at the time, warranty used to be 2 years from purchase.
Also, if it is a problem of the Inernal Battery, wouldn't the time reset to ROM date & time? My problem is that the time actualy goes back.
For example, it is 9:15pm & I remove the battery for 1 minute, the phone starts & time is 9:11pm. The more the battery is out, the more the time will be back.
Yeah I have this problem too! *feels less alone*
I noticed this problem after the first time I ran an Android build from SD, but that was probably coincidence...
I'm not really into sending it to warranty, my HD2 works great and sometimes they come from warranty worse than they go...
DeadVirus said:
I noticed this problem after the first time I ran an Android build from SD, but that was probably coincidence...
Click to expand...
Click to collapse
Now that you mentioned it, I did notice this problem after one of the Android builds from SD. Don't remeber which.
omar302 said:
Now that you mentioned it, I did notice this problem after one of the Android builds from SD. Don't remeber which.
Click to expand...
Click to collapse
I'm starting to think that it is related... Another guy complains about something similar after using Android SD...
Yes... Normally it should reset it.
But if you say it's only one year old, there's another hardware problem because such a battery has a lifetime from approximately 2 years.
Maybe - or better they must - will change it under the warranty conditions.
And I don't think that it has something to do with AD SD builds. I also used them for a long time and never encountered something like this.
Hello there.
I have the same problem with my HD2, which runs on a cooked ROM.
What I have noticed is that it actually goes back to the date and time of it's last boot (in fact the time and date SET after the last boot, since it changes and I have to reset it every time, by syncing or manually), regardless of the way the reboot was done. It is a little strange I guess...
Just thought to add this little piece of information.
Oh, and my phone is also quite "young", I have it for less than a year (don't remember the exact date of purchase).
Interesting. I was about to post a similar issue.
I had been using (SD) Android for about 3 weeks continuously. Had a crash and rebooted. I have some problems in Android now following this (corrupt Data.img I think) so booted back into WinMO and found the date was now 2nd Feb 2010 and some random time!
Reset the time and restarted and for some reason it refuses to recognise we are in BST (and I can't see how to change it to GMT +BST)
Same date/time showed when I booted into Android (doesn't seem to be getting the correct details from Network?)
Slightly better after a few reboots so that now everytime I reboot with a battery pull it is setting an older time (but correct date).
I have the same issue using WP7. The time changes backk like 6 hours or so to a completely random time.
And the annoying thing is that the phone seems to think its the right time, and theres no way to 'force' and automatic time update on its self, so i have to disable automatic update and enter the correct time manually!
That's the thing that gets me most - you can move between time zones and the phone gets the local time from the Network operator, but will not "check" if it is wrong by so much....
It must be the internal battery thingumijiggy.
Just confirmed that it only happens after a battery pull.
as long as no one has posted a theory yet, i'm gonna give it a shot!
i think the phone might have TWO regions of memory for storing the current date/time:
1. a "volatile" one (good as long as battery is present)
2. and another "non-volatile" one (survives between battery pulls)
my theory is, WM6.5 ROMs have something hidden in them that allows the date/time to be (periodically?) written to the non-volatile region in case the battery is pulled, following which the system might need to recall the last reliable date/time, as opposed to resetting to an arbitrary default date/time.
the volatile region is good as long as the battery isn't removed. the volatile region is initialized by the non-volatile region and is subsequently kept updated by the RTC (real time clock) chip, whether or not an OS is running (like android or WM or WP7).
but perhaps the little piece of logic that updates the non-volatile region is somehow absent in our android builds?
I have the same problem, and i just use clocksync a free app from market. The app sync the time every time you reboot your phone.
Sent from my Nexus One using XDA App
Dmxnet said:
I have the same problem, and i just use clocksync a free app from market. The app sync the time every time you reboot your phone.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I also use clocksync in android. But it doesn't solve the problem... :S
For the last several months I noticed that my Androind builds are hunging up, sometimes several times a day, sometimes once a month. While using it might just stuck/freeze and it doesn't react at all until I remove the battery and instert it back.
Recently I decided to browse the forums and read about possible bad sectors on my NAND memory. Somebody mentioned that I should use MTTY and do >task 2a, which actually confirmed that I have a bad block, bud it's only one. The issue is that now being tired of MIUI ICS which hungs quite often, and ICS CM9 builds which are quite stable but at some point are freezing as well, I decided to move to WP7, which earlier was running perfectly on my phone and was able to install those ROMs without any problems. Today I found out that while flashing WP7 ROMs I can't get over Flashing Partition 7, same error with 3 different builds..
Also today I flashed an original WM 6.5 build, which was installed correctly but after 5 minut had an unexpected reboot...
I trying everything I know, Task 29, reinstall HSPL, reinstall MAGLDR, different partitions for CWR, looks like nothing helps..
Does anybody has any ideas or hints?
hey
seems your battery was fault?
I have the same problem
anyway if you find how we can know if there any bad sector tell me..
for me I realize that after charging battery outside it restart
thxs
What I noticed that under normal usage (basic applications, internet browsing, email and listening to music) nothing bad happens, at least on ICS CM9 with HWA.. It freezes when it gets warm. Under heavy usage it might get stuck and while it's still hot I can't really load the system properly, as it will freeze instantly. Once it settles down, in about 15minutes, the system would work like nothing happened. I actually discovered yesterday that I still have 2 months of warranty left, maybe I should just return to the shop. But that means I need to flash back WM 6.5
nand problems or heat problem ?
hi
i have many freeze system on a day when working on my hd2
i tried many systems wm and android nand and sd its always the same problem
i have to remove battery and wait for a minimum of 20 minutes i f i want to boot correctly
can somebody help with a program to remove bad blocks on the nand of hd2 ?
thanks
I dont thing it's possible to fix bad nand memory blocks.
I'm guessing that the only way is to change the main board.
My HD2 works perfectly with stock WM6.5 and android, so i might not have any memory problems, but i have been reading about it and it seems that is not that uncommon.
Regardless, if there is a way to recover/block these bad sectors by some software tool, i would like to know also.
Well, in the end I had to return my phone to the shop today, as it's still under warranty.
I'm curious if there are going to do something with it, fix it, replace, or just return back, as I'm not really sure if they will find any errors, but I hope they will.
Just in case, I flashed the original WM RUU from HTC, and yesterday, while playing with it for a while, it rebooted a couple of times, and was quite hot as well.
Last week-end I've been to Lisbon, were we had 32 degrees at some points, so my phone was freezing every 5 minutes, when I put it in front of the blowing AC fan from the car it could work like that for hours without any issues, but I suppose it should work like that always and in all conditions. This made me understand that the overheating due to a faulty board could be the root cause of all problems. I suppose that even the bad blocks appeared after the overheating issue appeared
I will write here an update when I'll get my phone back from the service.
nickriley said:
Well, in the end I had to return my phone to the shop today, as it's still under warranty.
I'm curious if there are going to do something with it, fix it, replace, or just return back, as I'm not really sure if they will find any errors, but I hope they will.
Just in case, I flashed the original WM RUU from HTC, and yesterday, while playing with it for a while, it rebooted a couple of times, and was quite hot as well.
Last week-end I've been to Lisbon, were we had 32 degrees at some points, so my phone was freezing every 5 minutes, when I put it in front of the blowing AC fan from the car it could work like that for hours without any issues, but I suppose it should work like that always and in all conditions. This made me understand that the overheating due to a faulty board could be the root cause of all problems. I suppose that even the bad blocks appeared after the overheating issue appeared
I will write here an update when I'll get my phone back from the service.
Click to expand...
Click to collapse
What happened in the end? I'm facing the same problem, 5 bad blocks...how do I know where those bad blocks belong? I mean, which partition? Thx