Related
For some reason HTC sense has stopped working, I restarted my phone just a bit ago and when it booted back up it said launching sense but it never launched and then later said it was unable to launch sense.
I've tried turning sense off and back on as well as resetting a couple of times.
I haven't done anything with my phone since it stopped working, not installed any cabs or edited the registry just all of a sudden it has stopped working. For some reason programs that use sense for example the dial pad and contacts page (or at least I assume they use some part of sense) are working.
Luckily I can still use default windows screen until I find a possible answer to hopefully save me from a dreaded hard reset.
Anyone have any ideas on how to solve this without a hard reset?
I had this problem about 2 weeks ago. I flashed the phone back to stock ROM but it didn't fix the problem. So I had to take it in for repair. I would recommend you do the same mate.
Give this ago.
I've tried using that program above but unfortunately didn't work, so I did a hard reset and thankfully sense did work so it isn't as serious as some people where sense still doesn't work after a hard reset.
But luckily I did a complete backup before hand with spb backup, restored the backup hoping that maybe it would work but like I thought sense stopped working again.
Now just wondering if anyone knows what would be the best things to start disabling from the restore that wouldn't alter sense but yet keeping the phone as close to what it was before it started working?
Used SPB Backup? There uve got the option to customize ure restoring process.
Try to uncheck all/some manila files, uve edited, especially cookies manila files.
I had this. Turned out something on my storage card was giving me problems. Take your SDcard out, then reboot the phone. If Sense loads, format your storage card. If not, then it's another problem.
I've tried removing my memory card but the problem still persists, I then tried to restore certain parts from SPB backup until the problem starts happening again. Restorying everything but the registry and the databases that the problem exists.
Restoring the databases and not the registry leaves sense in a half working state and restoring the registry and not the databases leaves sense completely not working.
Is there a way of restoring all registry values that are related to htc sense and keeping all other values that are related to all other apps
aLlamaWithARifle said:
I've tried removing my memory card but the problem still persists, I then tried to restore certain parts from SPB backup until the problem starts happening again. Restorying everything but the registry and the databases that the problem exists.
Restoring the databases and not the registry leaves sense in a half working state and restoring the registry and not the databases leaves sense completely not working.
Is there a way of restoring all registry values that are related to htc sense and keeping all other values that are related to all other apps
Click to expand...
Click to collapse
Not sure about the registry. You might be better doing a task 29 and re-flashing your ROM.
Theres a method which involves deleting manilafull.xml from the windows folder that some people have reported as working...... It didnt work for me....
Ive had this a couple of times...........Once for no reason (I can think of)
The second time was because i took my sd card out while the phone was on.....Unless it just so happened to be a massive conincidence.......
Sorry to say but the only solution I ever found that works is......... the one you dont wanna do....
Yeah thought it would have to be a hard reset, ah well looks like I'll have to spend all day reinstalling a ton of stuff
Thanks anyway
happened to me the other day after i tried booting android. had to hard reset
I had that after booting the phone with a wrong SD card .. other one then i original use .. after putting in the original one again, it wasnt fixed .. had to hard reset
it happened twice with me. but when i flashed my ROM again it worked each time.
im having a problem like this...how can I hard reset without going thru manilla settings?
EDIT: jeez im such a dummy sumtimes....
With your phone powered off, press and hold the VOLUME UP and VOLUME DOWN buttons.
While holding the volume buttons, press the END/POWER button briefly and then release it.
When you see a warning message on screen, release the VOLUME UP and VOLUME DOWN buttons.
Press the VOLUME UP button to perform the reset, or press any other button to cancel the reset.
Hi, i have a problem. so i put darkstone froyo on my htc hd2. Everything was working perfect even windows mobile and right now when i restarted my phone from android to go back to windows mobile my phone just showed "launching htc sense" but it does load up!:/ the phone and some programs work but i seem to be having a problem with sense as well I have cookies home tab installed as well as bsb tweaks. anyone have any suggestions? i really dont want to hard reset my phone.
hi guys
I'm not really sure what my hd2 is doing.
I wanted to listen to music but it couldn't find any music files (I use the simple music player from within htc sense). So i turned it off and forgot to turned it back on. 2-3h later (now) I reminded myself and turned it back on.
The starting process war so slow and suddenly I expected something strange and it really happened:
Windows Mobile started complete new like after an rom upgrade or your very first starting.
Calender,mails,configurations,installed software - it all rolled by my mind.
But no,everything is still there.
Ok,I need to configure WLAN again and it forgot my mail password and some minor configurations are different but it seems everything is working...
Microsoft My Phone can't be started...
"is not responding and needs to be closed due unexpected errors.go to "all programs -> my phone" to start it again"...
my HD2:
rom version: 3.14.407.2 (GER) (the "latest" official rom from htc)
mila version: 2.5.20181527.0
So...
I have no idea how this is possible. I just turned it off and on again.
And I thinks it's very strange that My Phone isn't working anymore.
Maybe broken flash memory inside my device?
Time for a hard reboot methinks
I agree with johnerz it sounds like house need to do a hard reset of your HD2. But I sugest trying to vet Microsoft My Phone working first. Have you set up hour MSN live on your HD2 sense this strange acorrance? If not do so cause you have to set it up first before Microsoft My Phone willsign in and work. Also try downlodind and reinztalling Microsoft My Phone frimths market place. Wish youluck.
I have had the same issue, had to flash back to stock, then !twice! to the rom I wanted. This solved it.
Unfortunately there was no My Phone download in the market place. So I try surfing myphone.microsoft. com. It deleted the old version of My Phone and needs to restart the device.
After restarting the date is suddenly at some time in Nov 2009?!
Anyway...it's working and I can make my backups.
But what about the hard reset?
There are two ways to do a factory reset. One way is perform a clear storage process through the phone settings. The other way is to perform a hard reset by pressing certain buttons on your phone, in cases when you are unable to start up your phone and enter the phone settings.
Click to expand...
Click to collapse
there is no difference between these two methods,right?
I will remove Sim card and memory card (just in case).
And you really think this will solve my problem?
Hopefully it's not a hardwarebased problem -.-
So,I will try the clear storage process via settings...
My 4G will be 2 years old in February. It is quite buggy now, it likes to lag a lot or glitch, it's definitely not the lightning machine that it used to be. I saved all of my data and am going to perform a wipe/factory reset and wipe the cache partition (hopefully I am allowed to do that, if not, oh well too late).
Is there something more potent then a factory data reset using the Android Recovery mode while not in the phone OS? It resets the phone but I have the latest OS, which I think could end up keeping all of my bugs. Can I go back to the original OS when the phone shipped and legitimately start over and re-update everything? I logged back in and an app widget was still there with writing on it, some of my pictures, and some icons I moved around. this is after I did a rest outside of the phone, then went in the phone and did another reset. So much for wiping all of my data I guess.
So, if this does not fix the buggyness of the phone, what should I do? The phone likes to press buttons randomly and I have to hit the power button to lock it, and then unlock it for the magic button pressing to stop. This is common. Apps are slow or time out a lot and it takes the phone FOREVER to reboot. It love to randomly restart, especially using pandora or spotify. It takes a long time to connect to Wifi, sometimes I have to go to the wifi settings to wait for it to automatically choose my saved network, which baffles me like crazy.I did have the most recent update of course. I think the finger print scanner also stopped working... or it never did work. Lastly, the vibrating unit doesnt always vibrate, it likes to vibrate on a few keystrokes and it randomly stops, then starts up again. **** this phone. It really makes me want to go to an iPhone... and I am a hardcore windows computer tech and I hate apple, but ****, why cant anyone build a stable OS?
So, assuming my phone works correctly, what should I do to it once it's up and running? I am ready to Root the phone and try some new apps and hacks and what not, especially if it makes the laptop dock mode faster, cause right now it's slow as ****.
Factory reset basically wipes the /data partition.
I would also recommend you do a format of the internal sd, after the factory reset (see storage in the system settings). This way, files on the sd will have no impact on apps as you reinstall things.
Regarding returning to an earlier Rom version, I would not recommend as being part of the solution. Newer Rom version are better usually. Gb by motto is solid.
Sent from my MB860 using Tapatalk 2
Hi.
My Galaxy S3 is frequently getting into hotboot looping state for no apparent reason. The only way to get it out of this state is to wipe the phone or restore a backup of the "data" folder only.
After that, it might work for a week, but it might not work for a day (not work = start to hotboot loop).
It happens when after the phone screen is locked, it doesn't wake up anymore. It doesn't answers to any calls (like if it's off) or notifications. Just dies.
Forcing a reboot (by holding the power button) or removing the battery ables me to reboot it, but enter in hotboot looping state. I can make it go thru the whole booting state and I see the homescreen (And that's weird because I'm supposed to see the lockscreen first). Some widgets animation works but the device doesn't answer to touch (two softbuttons vibrates when touched, they do vibrate but don't render anything on Android) and then hotboots. Keeps doing this forever. Booting into safemode USED to work, but it doesn't work anymore, I don't know why.
After wiping the device or restoring the Data backup, device turns on as expected (restoring data takes it back to working state exactly like it was before the backup, even the same lockscreen pattern). I've tried to leave a terminal running logcat to catch the error, but it doesn't write in realtime, so when the bug breaks out, the logfile is empty.
I even thought it could be the S3 memory issue with firmware, but I'm using the "fixed" kernels. Also, it is recoverable, and not permanently dead.
I suspect of some rogue app, but I have too many apps to just go through installing one by one (and waiting even weeks to install the other one). Is there any way I can get a postmortem logfile or make logcat write in realtime?
Thanks
GTMoraes said:
Hi.
My Galaxy S3 is frequently getting into hotboot looping state for no apparent reason. The only way to get it out of this state is to wipe the phone or restore a backup of the "data" folder only.
After that, it might work for a week, but it might not work for a day (not work = start to hotboot loop).
It happens when after the phone screen is locked, it doesn't wake up anymore. It doesn't answers to any calls (like if it's off) or notifications. Just dies.
Forcing a reboot (by holding the power button) or removing the battery ables me to reboot it, but enter in hotboot looping state. I can make it go thru the whole booting state and I see the homescreen (And that's weird because I'm supposed to see the lockscreen first). Some widgets animation works but the device doesn't answer to touch (two softbuttons vibrates when touched, they do vibrate but don't render anything on Android) and then hotboots. Keeps doing this forever. Booting into safemode USED to work, but it doesn't work anymore, I don't know why.
After wiping the device or restoring the Data backup, device turns on as expected (restoring data takes it back to working state exactly like it was before the backup, even the same lockscreen pattern). I've tried to leave a terminal running logcat to catch the error, but it doesn't write in realtime, so when the bug breaks out, the logfile is empty.
I even thought it could be the S3 memory issue with firmware, but I'm using the "fixed" kernels. Also, it is recoverable, and not permanently dead.
I suspect of some rogue app, but I have too many apps to just go through installing one by one (and waiting even weeks to install the other one). Is there any way I can get a postmortem logfile or make logcat write in realtime?
Thanks
Click to expand...
Click to collapse
Try flashing another ROM for S3 and doing a full wipe.
TenKoX said:
Try flashing another ROM for S3 and doing a full wipe.
Click to expand...
Click to collapse
Thanks for the reply.
I already did. It started to happen out of nowhere while I used the Android Revolution HD ROM, then after a few wipes and reinstalls with the same problem, I gave a shot to WanamLite ROM. Exactly same problem. Both are based on the original 4.1.2 Android.
I'm pretty sure it is being caused by some rogue app, because the only thing in common between those ROMs is that I "batch-install" all my apps back from Google Play.
So far, I'm suspecting about Vine (it's the last install that I remember since it started to have this issue) and I have already uninstalled it, but it might have been caused by some app update that broke hell to my phone.
If there were some kind of "black box" that I could retrieve after a crash, it could be the solution
GTMoraes said:
Thanks for the reply.
I already did. It started to happen out of nowhere while I used the Android Revolution HD ROM, then after a few wipes and reinstalls with the same problem, I gave a shot to WanamLite ROM. Exactly same problem. Both are based on the original 4.1.2 Android.
I'm pretty sure it is being caused by some rogue app, because the only thing in common between those ROMs is that I "batch-install" all my apps back from Google Play.
So far, I'm suspecting about Vine (it's the last install that I remember since it started to have this issue) and I have already uninstalled it, but it might have been caused by some app update that broke hell to my phone.
If there were some kind of "black box" that I could retrieve after a crash, it could be the solution
Click to expand...
Click to collapse
If you wipe data, your apps disappear, so I think this is not the problem.
Do another full wipe and DON'T restore your data. Just download again from Google Play and see if the problem appear again.
TenKoX said:
If you wipe data, your apps disappear, so I think this is not the problem.
Do another full wipe and DON'T restore your data. Just download again from Google Play and see if the problem appear again.
Click to expand...
Click to collapse
Thanks for the reply.
I started doing this the first time, but it still crashes it. And as I was wasting too much time with this, the backup option came as a option to not have to click to download over 200 apps one by one. Also, it once happened during a long holiday, and I was in a friend's ranch with no decent internet connection for downloading. All my apps were gone and I was stuck with a default phone for five days.
The backup is exactly the point where I finish downloading all the apps and they're installed. There are no cracked programs or adapted (e.g. Nexus camera). Every single app is obtainable from Play Store, so it's pretty fresh
Funny (actually sad) thing is that it's a system-wide error that a wipe solves it. If I don't wipe data and reinstall the same ROM (which under normal condition is no big deal), it doesn't get past from boot screen.
The worst is it happens instantly. It's working now, but then it crashes. Bam, gone. Few hours ago I was texting my gf and I left the phone for a while, waiting for her answer. After some time I knew something was off, picked up the phone and it was pretty warm (first signal), with the LED blinking some Facebook notification. Tried to wake up but it is in coma. I force a restart and it hotboot loops like I described on first post
It -only- happens when screen is locked. I disabled the screen lock for now to see if it's a workaround, but I'm not holding my breath
It could be a hardware malfunction if it can carry through all the roms you flashed and even when you tried a fresh install without your apps it still happened.
WildfireDEV said:
It could be a hardware malfunction if it can carry through all the roms you flashed and even when you tried a fresh install without your apps it still happened.
Click to expand...
Click to collapse
That's pretty much discarded. Wiping data instantly solves it. It did indeed run for 5 days with no external app without a single problem.
But also it ran over one week with external apps without a problem. I've executed some memory integrity tests and they all reported a-OK.
I'm kinda ruling out the "rogue-app" issue. I thought that recovering "data" from NAND backup was the /sdcard/android/data. But it's deeper than that. Now I don't even have a lead.
Phone already crashed today, without Vine and lockscreen, so that's not the problem. I really need to get some logs out of him. Just need to know how. Only if it could write a realtime log, so I could pull through ADB.
My last resort will be a fresh-fresh android installation, default S3 i9300 ROM, with only essential apps. Already have it triggered for the next crash.
If it goes rogue even this way, I'm running triangleaway and returning it (will be a profit too, the silver border is stripping).
This time around, I'm trying running it without a external sdcard (several files were being corrupted in it, don't know if it's due to force restart by removing battery, or some real issue on the card)
It's a problem within the Facebook social app or Youtube.
I've managed to run the phone flawlessly for weeks without signing in on Facebook, suspecting it might be it.
Today I logged in on Youtube app accidentally, and had to login on Facebook app to retrieve some info. Three hours later, phone went mad again.
I don't know which app caused it, but I think there's some relation to Facebook due to a greater ~involvement~ (couldn't find a proper word.. forgot it) with Android.
I've changed ROMs, launchers, system versions.. but not Kernel. I'll try another kernel and report on Boeffla main thread to see if there's some known bug
Hello
I've had a Samsung Galaxy S3 for ages, unfortunately for me, the phone recently just switched off, then on, then won't go past the "Samsung" screen. Ah, I thought (well, something a bit more sweary) - but I had a backup identical model phone in case one broke, so I started using that. Moved all my apps, installed banking app etc, and then happy.
Or so I thought...
The new (well, it's an old phone, but one I haven't been using, bought as back up) phone now switches off when charging every night, an issue which was going to switch to me charging it during the day when I can stare at it and see if anything happens to make it switch off, but then I realised it switches off each night even when it isn't charging.
I have a bigger battery to hold a charge for a few days, and so even when I don't charge it, just have it next to me as I sleep - and next morning it will be off. I presume it might be switching off around 5am... this is only a rough guide as if I switch it back on, and flick through the phone, I see my unread emails are up to around 5am, and then after a few minutes it logs back into the internet etc and brings me newer emails.
I first thought it was that it kept switching off when charging... but now I know it does it at (I presume) the same time every night even when it's not charging. Can't use it as an alarm clock anymore, as it's off before the alarm goes off. Anyone have any idea what's happening?
Did you copy all of your data and settings?. Most likely you have a software conflict going on.
I highly recommend you backup your data from all 3rd party apps. Do not backup your system apps data, google data, apps or games that cloud sync or phone settings, ie wifi passwords etc.
You must allow samsung apps, google and other cloud apps to sync their own way and you must calibrate the phone for wifi manually.
Beyond that you'll need to reflash stock firmware and start over using the guidlines I have given you above after restoration of the firmware (and root if required).
Beamed in by telepathy.
I assume when I installed on the other phone, it switched settings when I log in to various things. Because I installed everything asap, I've no idea if one thing is causing the issue.
How do I get the phone to calibrate manually? Apologies, I'm not great with techie stuff I add the wifi details, and logged into settings - is that manually? Things are backed up to themselves, so when I log back in it resets to previous settings when it syncs. Should I try and work out how to prevent all things from backing up manually? Haven't logged back into any games, although they might be installed, haven't actually signed in or used them.
How would I go about reflashing stock firmware? Doesn't sound like anything I've ever done before, but up for a challenge
By manually i mean just setup wifi yourself rather than allowing a backup. Same for system apps.
The app data will contain references to the old phone which will confuse it. All of that must be rewritten on the specific device to match the phones identity.
3rd party apps are usually OK with backups but still shouldn't be trusted, but they don't usually bootloop the phone. They just force close instead.
Flashing firmware will reset the phone back to factory and rewrite the operating system, removing any software bugs in the process. To learn how to use odin you can find countless guides online too.
A straight forward "factory reset" via either the phone software or the recovery menu could solve the problem rather than flashing.
If I were you, I'd just factory reset it and then allow the phone to run for a few hours to see if the problem reoccurs in a factory state. If the phone asks for a google login just use the normal account and allow all updates to happen but switch off backup and sync for the short term. If all seems good then you know there was a bad app somewhere.
Beamed in by telepathy.
shivadow said:
By manually i mean just setup wifi yourself rather than allowing a backup. Same for system apps.
The app data will contain references to the old phone which will confuse it. All of that must be rewritten on the specific device to match the phones identity.
3rd party apps are usually OK with backups but still shouldn't be trusted, but they don't usually bootloop the phone. They just force close instead.
Flashing firmware will reset the phone back to factory and rewrite the operating system, removing any software bugs in the process. To learn how to use odin you can find countless guides online too.
A straight forward "factory reset" via either the phone software or the recovery menu could solve the problem rather than flashing.
If I were you, I'd just factory reset it and then allow the phone to run for a few hours to see if the problem reoccurs in a factory state. If the phone asks for a google login just use the normal account and allow all updates to happen but switch off backup and sync for the short term. If all seems good then you know there was a bad app somewhere.
Beamed in by telepathy.
Click to expand...
Click to collapse
Ahh, cool, gottcha! Ok, will try soon. Surprisingly, I've switched off the phone every night instead of it auto-switching off at around 5-6am, and surprisingly it's so far going well. Had it on for 3 days and only at 47% now, so it's promising, still does switch off occasionally during the day, but I've just ignored that. Will do a factory reset in the next couple of days and report back Thanks for the help