android.process.acore resulting to frozen screen - HTC Sensation

I am having this freaking problem after upgrading to 3.33 firmware and installing Elegancia 2.7. My sensation keeps getting this error "Android.process.acore has stopped" and after this my touch screen keeps on freezing.
I am unable to use touchscreen.
After restarting my phone, i still keep on getting same error :crying:
I have pull out battery from the set, kept it off for almost 6 hours and still got same error after rebooting.
Is there any solution for this issue ?

Even if i reboot to 4ext recovery, i am unable to use touchscreen.

Does the touch screen work in recovery?
It happened to me a couple of months ago, touch screen didn't work anywhere with that same error.
I thought it was the digitizer at first and sent it to a lab.
Switching it didn't help and it turned out to be the board which switching to a new one fixed it.
I don't know if we have the same problem but thought I'd let you know.
Sent from my HTC Sensation using Tapatalk 2

Badflash. Check md5 and then reflash if md5 matches. Happened to me once. Go into recovery, do wipe data/factory reset, then format partition on all except sd card. Fullwipe (you can get it from coredroid) then run superwipe. Then reflash. I always do it that way to ensure i dont get any leftover files/bad flashes.

I looked this up and it said its related to apps that use the same sync function. There solution was to close all tabs in manage applications, clear data and cash in contacts, then clear data cash in contact storage. But I don't know how you can try that if touch screen is not working. I wish I could be of more help. I do. Hope you get it working and figured out! Best wishes .
Sent from my HTC Sensation 4G using xda premium

my touchscreen is just not working. even in recovery. anyways managed to re-install stock 3.33 rom but still then touchscreen isn't responding

Anyways i dont know why the hell has it started working again after i tried to install 3.32 it rebooted and i was able to work. Lets hope it continues to work. But anybody... please let me know what had actually gone wrong and how to avoid it in future...
Running 3.33 stock rom now

Related

[Q] [HELP] The process com.android.phone has stopped unexpectedly

i recently bought a htc Desire S. it was working fine, for day or so. now every time i start it i get 'The process com.android.phone has stopped unexpectedly' if i press wait.. it lets me get through a few of the setup options, then it does it again, and sometimes does the same for process .com.htc.bgp (but only once). if i press force close, it keeps rebooting and just shows the htc logo.
so i cannot start the phone.
ive tried a factory reset (twice) with no luck, i have tried 'solutions' from many threads, none seem to work. is there a way i can re-install android 2.3 or something?
does same thing in safe mode.
thankyou.
If you've only just bought it then I'd take it back for a replacement, it sounds like a hardware fault to me.
Only other thing I can think it might be would be a faulty SIM card. Have you tried booting it without a SIM in?
Could try without sim and sd card
You could r flash an ruu, but as it's new you'd be better off to just take it back and ask for another one
Sent from my HTC Desire S using XDA Premium App
delicious.cake said:
ive tried a factory reset (twice) with no luck, i have tried 'solutions' from many threads, none seem to work. is there a way i can re-install android 2.3 or something?thankyou.
Click to expand...
Click to collapse
Some days ago I messed up my buttons (i was deleting some files with root explorer), touch screen was working fine but all buttons not ! I did 2 factory reset but nothing. I ended to reinstall ROM which solved my problem so maybe could help you to.
I'm doing well, you have to pull out a battery for a while and then come back it goes.

[Q] Device hangs and cannot format /data

Hi,
Today during a call my Inspire 4G froze with no apparent reason. I rebooted and I always had freezes, so I decided to do a factory reset.
I'm rooted and have Virtuous Unity 1.24 installed (never upgraded because it had been working fine).
When I try to format /data it hangs for a while and I get an error saying "error formatting data".
I'm just downloading latest version of the ROM hoping this way it'll get fixed.
Just before messing more with the phone, has anyone had this experience with the Inspire 4G?
Regards
Try doing a full wipe/factory reset in recovery, if same error, your sd card could be trashed. There's a recall on some newer sd cards that came with inspire. Google it.
Sent from my Inspire 4G using Tapatalk
Well,
Now it won't even reboot into recovery. I only can boot into HTC white screen, but clockwork died, seven vibrations when I try to go into recovery.
Now I'm trapped, tried installing PD98IMG.zip that comes with the rooting files, seems to install well but doesn't work.
Any other suggestions before I assume my Inspire died?
Take out your SD card. Then trybooting Into recovery. Once in recovery you can insert SD card. Wipe and flash. I saw that this worked for a couple of people in another thread somewhere
no hay de queso no mas de papa
No luck, just 7 vibrations when I go into recovery, with and without SD card, even tried without SIM card which should not have anything to do...
I had the same error with motorola atrix. I have flashed the firmware again to resolve this issue
Sent from my MB860 using XDA App
Maybe try a different pd98 or maybe the ruu.
no hay de queso no mas de papa
Tried with the RUU but it cannot detect the phone, will see if I can do something else, just strange thing, never had this kind of issue with any Android Phone...
Is there a way to extract the PD86IMG.zip file from the RUU?
Well, after alot of trying out, I'm pretty sure the device is hard-bricked due to some HW problem, will still do some attempts to recover the phone, but it is strange:
1. It worked great a few days ago, I installed no updates, radios or anything other than Market apps.
2. In the last days, I've had some random hangs on the phone, just pulled battery and rebooted.
3. Today it hanged during a phone call, pulled battery and every time I rebooted it would just hang again.
4. Went into CWM Recovery, was able to ADB and everything, but any attempt to format /data or /cache would cause an error.
5. After playing around with CWM, suddenly I wasn't able to see the menus anymore, when I rebooted, any attempt to go into recovery from the HBOOT screen would result in seven short vibrations, a wile after that screen would go black.
6. Downloaded various PD86IMG.zip files, all of them install and give no errors, but the phone always keeps sending those 7 vibrations when trying to boot or go into recovery. HBOOT screen still works, any PD86IMG.zip file apparently installs fine (no errors), but when I reboot it is dead.
I am thinking that something bad happened to the internal storage, the symptoms show in that direction and I can't find any post that seems a bit related to this issue. This might be my 6th or 7th Android phone and I often root other phones for friends, in fact I have rooted 4 or 5 Inspires and have had no issues.
I just want to see if there's anything else I can do...
Thanks and regards...
Have seen the 7 vibrate occurrance mentioned a few times. It is hardware related and there is not much you can do about it. Sounds like the solder connections between the processor and the motherboard are separating. By chance has the phone been real hot in the recent past?
Real hot not, but I dropped it once a few weeks ago, I was really surprised that nothing broke, it was not a nice drop...
Well, will see how much I get for the phone listing it as "for parts"...

HTC stuck on splash screen

Im really hoping someone can help me please...
ever since viper 1.6.x sometimes my phone will shut down, or if my phone battery runs completely dead of battery, and then when i try and turn the phone on again it will go into a boot loop where is gets stuck on the senasation splash screen...
can someone tell me why this is happening and how i can turn my phone back on after this happens...?
info
i am on vipers had this problem since 1.5.x - 1.6.x with multiple kernels, but the last kernel i was on when this happen was faux 10b9
this most often happens when the battery run completely dead, but has occasionally happened on a random reboot swell
things i have tried...
pulled battery...
clearing dalvik and cache - this will get me past the splash screen once, to the android is upgrading page (as i have cleared dalvik and cache) only to reboot at the end and finally get stuck on the htc sensation splash screen again
formated system
installed the rom again with the restore option (the last of the 3 options stating to use it if you have a corrupt operating system)
reflash the kernel
install same rom without wiping
the only thing i know i can do and that ail work is going back and restore an old backup via 4EXT but i no longer have any back ups (dont ask why i did this! i thought it was working now!)
is my only option a full format?
why is this happening?
anyone know a way around it?
does this mean i can never go back to ViperS as i will always have this problem or is the problem from somewhere else??
thanks so much in advance...
i suggest to format all partitions except sdcard
flash viperS rom
see then if your issue exists
otherwise try different rom
also if you are S-ON enable smartflash from 4ext before flashing the rom

[Q] [Help] Stuck on HTC boot screen, other issues in thread

(Just wrote a detailed post and when I went to post, it said I wasn't logged in and erased it...will give a quick run down and can supply more detail where needed as I work through fixing my phone)
Stuck on the white htc splash screen is my most recent problem. Sometimes it gets by that but then boots into recovery. I think bananagranola has the solution in their sig to flash a boot.img. and think I'm comfortable with how to do that, just need to find that file (in the ROM zip?)
What led up to this.
Successfully unlocked and flashed to CM7 back in late Jan/early Feb.
Started experiencing random freezing about two weeks ago.
A week later (last weekend) flashed Jellybean (R10). Worked great for a couple hours then started having the same random freezes.
If things froze I'd have to remove the battery and reboot. After a day or two of this though it'd get to the point that even that would leave me on a frozen jellybean boot animation. So I'd go and factory/data reset in CWM Recovery, wipe cache, wipe Dalvik then reflash the ROM. and I'd be good for a little while more.
Tried flashing back to CM7 but Recovery didn't like the file (it has a good MD5 when checked) Had tried my restore point from early Feb before to no avail, so decided this morning to try other restore points from the last few weeks, right before and after switching to JellyBean. They got further, the first step is something with boot then something with system. It failed on the system part. OK...so I wiped and reflashed jellybean again, and now I am to my splash screen freezes.
I should have asked for help much earlier (lesson learned!) but here I am asking now...what's the first step.
Do I test out and see if I hang on the splash screen again. I haven't turned the phone on in about an hour. Worried of screwing it up more.
Thanks all.
TL;DR Believe I'm stuck on splash screen and know solution to that. Have had phone flashed with new ROM with no prob for months, recently freezing, regardless of ROM. Hoping for advice on getting things working again, starting with whether fixing the splash screen thing first is where to start
splash screen issue seems fixed
Seems I fixed the issue with the splash screen. Booted into recovery and reflashed the Jellytime ROM.
Got all the way into Android. after a few minutes I rebooted into recovery and loaded the gapps. Rebooted, it updated apps (not downloading, the popup that says it updates) and was setting up my account when it froze again as I entered a wifi password. Pulled the battery and tried again, got through that and all the way to the lock screen. froze shortly after that.
Now when I reboot, it locks on the boot animation. The Jellytime screen flashes the brightness as few times as things are loading. after the 5th or 6th flash it just sits there frozen.
a new SD card is in the mail, so I may post again when that arrives to see what I can do with an almost clean slate.
irishpanther said:
Seems I fixed the issue with the splash screen. Booted into recovery and reflashed the Jellytime ROM.
Got all the way into Android. after a few minutes I rebooted into recovery and loaded the gapps. Rebooted, it updated apps (not downloading, the popup that says it updates) and was setting up my account when it froze again as I entered a wifi password. Pulled the battery and tried again, got through that and all the way to the lock screen. froze shortly after that.
Now when I reboot, it locks on the boot animation. The Jellytime screen flashes the brightness as few times as things are loading. after the 5th or 6th flash it just sits there frozen.
a new SD card is in the mail, so I may post again when that arrives to see what I can do with an almost clean slate.
Click to expand...
Click to collapse
That doesn't sound like an sdcard problem. Are you full wiping?
bananagranola said:
That doesn't sound like an sdcard problem. Are you full wiping?
Click to expand...
Click to collapse
I'm wiping data/factory reset and cache as well as the dalvik cache.
The steps to flashing a ROM by sashank at link mention to format /boot and /system. I didn't specifically do those...but don't see the option for /boot in any menus I've checked.
A week or so ago I was beginning to suspect there was an issue with the memory but I never found the right search terms to find out how to do a memtest if that's what would have found any problems. Yesterday I did come across some discussion of a corrupt partition/bad chips in some HTC devices. I followed the directions there and through adb ran dmesg | grep mmc0 and the output was similar to the 'normal' one given and showed none of the messages they claimed to indicate a bad chip.
I'm not too concerned with any data from the phone...I backed all that up long ago and the rest restores from my google account. So if I getting things running would normally raise concerns of lost data, that's not an issue for me.
Thanks for taking the time to read. I try to be brief...but don't want to leave anything out.
Wanted to update here before trying to start a new thread and clogging up the board. The title of this thread is not up to date though.
I can hboot just fine and boot into recovery just fine. My phone is unlocked and rooted, ENG S-OFF from when I used AAHK quite a while ago.
When trying to navigate from menu to menu in Recovery I will get the following error messages (best I remember from last time I was in there, I've let the phone be for the last 2-3 days now)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
This doesn't show up at first though, only after I do a Wipe Data/Factory Reset. And if I understand correctly, that wipes /cache so maybe that's causing these errors?
Anyway, after wiping the dalvik cache I can flash a ROM, I've been using Jellytime, I haven't been able to rollback to CM7, not sure why not.
Jellytime will run though...at first! the first couple of boots I can get in and get through registering my google account and have it begin restoring apps if i make that selection. The time I have to work on the phone before it freezes gets shorter and shorter though. I have to remove the battery to get it to reboot. Eventually I am left with the phone hung during the boot animation. I've left it for over an hour before...it's definitely hung there.
So my reading leads me to believe corrupt partitions. I'm not finding a lot on what I should do to reformat and maybe repartition or whatever I may need to do to recover a functioning phone. I don't care about any data on the phone. I just want to get things working again. I ended up getting a new SD card during all this that arrived earlier. If I can get my phone working, I'd prefer to use that from here on out too. I can use the adb in recovery mode just fine if that's necessary to rejigger things to work.
Can anyone help reset my partitions, if that's what this issue seems to be? If not...any ideas?
Thanks.
Recovery and version?
bananagranola said:
Recovery and version?
Click to expand...
Click to collapse
ClockworkMod Recovery v5.0.2.0
Full wipe?
bananagranola said:
Full wipe?
Click to expand...
Click to collapse
Yes. Everytime I've flashed, I've followed:
wipe data/factory resent
wipe cache
wipe dalvik cache
unless there's more I can do.
irishpanther said:
Yes. Everytime I've flashed, I've followed:
wipe data/factory resent
wipe cache
wipe dalvik cache
unless there's more I can do.
Click to expand...
Click to collapse
Maybe try a different ROM, preferably a stock-ish ARHD or similar ROM?
bananagranola said:
Maybe try a different ROM, preferably a stock-ish ARHD or similar ROM?
Click to expand...
Click to collapse
OK, I'll give this a try. The issue with the freezing is why I moved from CM7 though (which had been stable for four months) so it's reproduced itself in different ROMS. I'll post back once I give this a try. Thanks.
bananagranola said:
Maybe try a different ROM, preferably a stock-ish ARHD or similar ROM?
Click to expand...
Click to collapse
I gave Android Revolution a shot. During the flash it gave a message which might also be why I wasn't able to flash back to CM7. The MD5 did verify.
Code:
assert failed:write_raw_image("/tmp/boot.img","boot")
When I went to reboot, I ended up in Jellytime. Of course I had to sign back in to google apps and those things were reset from the dalvik wipe. Shortly there after the phone froze.
On reboot I tried a logcat. Didn't get it right from the start (you can send the command during the boot animation if I read correctly) but captured the failure of things. It's back around the 09:02 portion of the log. To my eyes it looks similar to others I've collected. Especially the message
Code:
Fatal signal 7 (SIGBUS)
though I haven't been able to figure out much about that, or identify what it is before that that could give another clue as to what is screwy since that's maybe (Probably?) related to the flashing issues.

[Q] failed restore/flash bricked phone

the short story- my htc inspire is frozen on white htc startup screen and wont go anywhere.
the long story- i got my htc inspire 4g stock (used) beginning of this summer. it was almost perfect except some annoying apps and features. so i successfully rooted it using advanced ace hack kit. it was great. but the battery life sucked and so did the speed. so i decided to flash to new rom so i can overclock and undervolt. i then backed up my rooted stock rom onto my sd card. i then installed android revolution 7.3 and overclocked to 1.5ghz and undervolted -50. it was great now, battery life was way better and phone was faster. it was almost perfect except one issue- every once in a while, it would randomly just shut down and restart, then get stuck in a bootloop displaying htc white screen then the beats audio, then repeating endlessly until i pull the battery. that solves it until it happens again randomly (not that often but still annoying losing my data) i tried different settings in setcpu and daemon tools and same problem.
i then decided its time to revert to stock rom and try a new rom and see the difference and if i like it more, ill keep it. so i loaded recovery from rom manager (because my power button dont work) and i wiped to factory default and did all the steps of clearing the cache and the dalvik cache, etc it said it did it fine. i clicked install from zip and chose dirty unicorns rom that i found on this site for my phone.
it said it installed without any problems. cool, i clear caches again and reboot.
but this is the wack part: when it restarts, it still loaded android revolution... all the data on internal memory was gone from wiping it and my superuser was gone. (rom manager stayed) i thought that was weird. i tried a couple more times and same thing. and then i put the backup i made of my stock rom before i flashed anything onto my sdcard-> rom manager-> backup.
but when i went to rom manager-> backup, my backup wasnt there. i then went to manage backups and restore. it said no backups found. i then thought maybe it has to do with superuser gone? i plugged in my phone and loaded ace. i noticed it had a load stock rom option on it. awesome, i clicked that, chose first one (htc inspire at&t) and it started doing its thing. but it said it had a problem downloading some package or something? it said it connected to th site fine but kept coming up with that error and a prompt saying "do you want to continue[y/n]" and i type y hit enter and same error. i tried another one but same error. oh well. i went back to menu and chose option 1 for rooting it, it did its thing with no errors. rebooted my phone. except now, its on htc start screen and wont go anywhere. its just forever stuck there. i did figure out just now that since my power button dont work, i could load hboot by taking out battery, and holding volume down while sliding battery in. but it wont go up and down on the menu with the volume keys. since my power button dont work i cant select one anyways but i should still be able to go up or down right?
well thats what happened and i feel like a retard.. if anyone might know whats wrong please help
ok i solved the issue after constant reading. i had to reformat my sdcard to fat32 and put stock pre rooted rom since i still had s-off. then it was just load hboot and it loaded files from sd card automaticly (took a moment, i thought it wasnt going to work) but it said found file (only file on the card now) and then accepted install. now im back to stock pre rooted rom. im so happy i didnt completely ruin my phone <3
im sorry for wasting everyones time. i should have read more before posting, as the thread that helped me solve this was on this site.
>>>> http://forum.xda-developers.com/showthread.php?t=1396229

Categories

Resources