Well I know it happens, and it happens to multiple people but I haven't pegged an answer why phones will just randomly soft reboot like this.
But more importantly I'm wondering why mine soft rebooted into a boot loop?
Currently reflashing the rom Open Eclair hoping it works cause I don't want to loose all the data BUT it looks like my phone won't go past the G1 screen now.
Hmf.
Well what do you know, lost all my data. That's fantastic.
Wipe + Flash.
Icebergxx said:
Well what do you know, lost all my data. That's fantastic.
Wipe + Flash.
Click to expand...
Click to collapse
:/ good thing contacts and stuff are in the cloud
Related
Suddenly my Sprint HTC Touch Diamond is running extremely slow. TouchFlo 3D will not start. Various things runs extremely slowly like tapping on the start menu takes like 20-30 seconds to come up.
Rebooted several times. Turned off TouchFlo. Phone's still as slow as molasses?
What to do? Flash the ROM? If so, which I'd hate to do, where do I get the original Sprint based ROM?
Update: For some reason \Windows\manilla.exe never gets run. If I run it by hand then Touch Flo comes up. But it's still kinda slow.
Who/What starts manilla.exe?
Simply do a hard reset, this will reset everything back to original rom as in a factory reset.
http://www.hardreset.eu/htc_touch_diamond_hard_reset_soft_reset_en.html
That would be wonderful if I didn't customize things. But I have - heavily. And I'll need to reinstall all my apps. I was hoping not to do that...
defaria said:
That would be wonderful if I didn't customize things. But I have - heavily. And I'll need to reinstall all my apps. I was hoping not to do that...
Click to expand...
Click to collapse
But this is the most likely reason it is running slowly... Needs a hard reset and start again - and be judicious with what you re-install.
Before doing a hard reset, have you tried a soft reset??
A soft reset for heavy users is almost required dally in some cases to release the memory from being attached to programs and the OS which is consider to be called "Memory Leaks." A typical problem for all 6.1 Roms.
This slow and sometimes unresponsive behaviour was what also experience as well. There are programs that help memory find it's home but sometimes a good old fashion soft reset is what's needed.
Last thing: Make sure that when you have flashed a new ROM to ALWAYS do a HARD RESET immediately. Not sure if you followed that procedure in your last flash. IF not, I'm afraid a soft reset might not be sufficient to remedy this issue for you.
Riker88 said:
But this is the most likely reason it is running slowly... Needs a hard reset and start again - and be judicious with what you re-install.
Click to expand...
Click to collapse
This is exactly what I was trying to avoid. A computer doesn't suddenly go from running OK to dog slow when you have not changed anything (I only rebooted/soft reset). The running of manilla.exe doesn't suddenly disappear.
Everything I install I install for a reason.
band27 said:
Before doing a hard reset, have you tried a soft reset??
Click to expand...
Click to collapse
Daily! If not hourly. WinMo is not known for being stable.
A soft reset for heavy users is almost required dally in some cases to release the memory from being attached to programs and the OS which is consider to be called "Memory Leaks." A typical problem for all 6.1 Roms.
Click to expand...
Click to collapse
I'm well versed in what memory leaks are. 'Round here we call them bugs. Being in the business for some 30 years now I can tell you that having to reboot an OS periodically is a sign of an extremely buggy OS. Unfortunately that's what WinMo is.
This slow and sometimes unresponsive behaviour was what also experience as well. There are programs that help memory find it's home but sometimes a good old fashion soft reset is what's needed.
Click to expand...
Click to collapse
There's a big difference between being slow and being suddenly SLOOOOOOOOOWWWWW.
Last thing: Make sure that when you have flashed a new ROM to ALWAYS do a HARD RESET immediately. Not sure if you followed that procedure in your last flash. IF not, I'm afraid a soft reset might not be sufficient to remedy this issue for you.
Click to expand...
Click to collapse
I've yet to flash this phone. I was hoping to avoid it. There are so many ROMs to choose from, some better than others. And I'm not looking forward to having to reapply all my customizations...
i get a problem like this occasionally after a restart. I need to hit the green dial key to get it to ask my PIN. after i enter my pin everything is back to normal.
just an idea
sprite backup
What you should do is when you hard-reset the phone and you have installed all your must-have apps (and the phone still runs smoothly) use Sprite Backup to make an image. This way when things go bad again, just restore the Sprite image to that wonderful time when everything still worked smoothly and you won't have to install all the apps again. Only the apps you installed after the image ofcourse... depends how often you backup
Works like a charm.
Be careful though, when you flash another rom, you CAN'T use the Sprite image anymore!! You have to make a new image then.
Hope this helps.
I'm running JAChero 2.3.3 and just have a few questions to see if what I'm experiencing is normal.
Firstly, when I'm at the home screen, the trackball cannot select any of the apps, just switch from one screen to the other. Kind of annoying sometimes cause I've gotten used to using it more than the touchscreen. I'm assuming this is a problem on all hero builds, but is there any way it can be fixed?
Secondly, every time I do an adb reboot, the phone boots up then about 5 or 10 seconds later, reboots again. Not that big a deal but just wondering whats happening.
That's really all the problems I have with it, everything else runs great.
Yes the first thing about selecting apps is normal. The second thing, could you be more clear? Do you mean like the htc screen shows again? or does your phone like actually vibrate and go through the 3 screens?
Yes the first thing about selecting apps is normal.
Click to expand...
Click to collapse
Thats depressing
The second thing, could you be more clear? Do you mean like the htc screen shows again? or does your phone like actually vibrate and go through the 3 screens?
Click to expand...
Click to collapse
After rebooting through adb, the phone goes through all the boot loaders, then it starts loading, and while its loading it reboots itself. The once it reboots, everything works fine.
The rebooting is not normal. Dont really have a solution except a fresh format of your ext partition, a data wipe, and then a reflash.
The rebooting is not normal. Dont really have a solution except a fresh format of your ext partition, a data wipe, and then a reflash.
Click to expand...
Click to collapse
I think I'll just live with it, don't really want to go through all the set up again and it isnt really causing any harm.
Thanks for the quick answers alritewhadeva
No problem Cash. Any other questions just PM me
I was using my phone a few hours ago (adding an icon from the application drawer to the home screen if that will help with solving the problem) when suddenly, the phone reset itself as though I had done a wipe from the recovery console. I had to sign back into Google and re-sync my contacts and calendar. All my settings were back to defaults. My home screen icons disappeared and changed to the default icons (browser, contacts, dialer, market, messaging, maps) as did the wallpaper. All my SMS messages were gone. Basically, it as was as though I had wiped and flashed the ROM for the first time.
However, and this is the weird part. Not only were all my apps still there but they were still installed. All the settings were lost but they were still there. I am not concerned with the restoration of my settings or anything like that. I've got that all covered with backups. My big question is why did it happen? Has anyone experienced or heard of this phantom reset? My ROM details are in my sig but just in case that changes and someone visits this post later, it will make more sense to them if I list it in the post itself.
Cyanogen 3.6.8.1 w/Recovery Menu v1.4. Radio v2.22.19.26i. A2SD on 550MB ext2 partition. Compcache enabled/24MB.
Has the only happened once with you? It could have been just a glitch.
supremeteam256 said:
Has the only happened once with you? It could have been just a glitch.
Click to expand...
Click to collapse
Well, I can tell you why your apps survived, because you have them on sd card so that's not weird, you can wipe all you want and they will survive.
I would say this is a glitch, don't worry about it unless it happens again.
borodin1 said:
Well, I can tell you why your apps survived, because you have them on sd card so that's not weird, you can wipe all you want and they will survive.
I would say this is a glitch, don't worry about it unless it happens again.
Click to expand...
Click to collapse
Yes, the apps on sd being the reason I didn't lose them makes sense. I had a different problem losing apps on the sd when I wiped but that was a mistakes in the way I was slinking and it was also on JF1.51 (a2sd is very unstable on that ROM). Anyway, I'm seriously hoping it was just a one time glitch because my setup is voodoo smooth otherwise. I finally got my G1 running perfectly and I'd hate to think something was wrong. Either way, Nandroid is always an option.
Phantom Reset Not a Glitch. Happened Again!
OK. So it happened again. The phantom reset that I described in the first post happened to me again. It's pretty annoying to have to perform Nadroid restores all the time. Anyone have any real thoughts other than telling me it was a fluke?
Possible Answer
I am pretty certain that this happened right after I used Backup for Root Users. I have my identical setup on my father's G1 and this has never happened. He has told me in the past that he does not use that app. I don't want to instantly blame the app but I want to provide as much info as possible. Cyan's ROMs are too good for this to be an issue.
aaronratner said:
OK. So it happened again. The phantom reset that I described in the first post happened to me again. It's pretty annoying to have to perform Nadroid restores all the time. Anyone have any real thoughts other than telling me it was a fluke?
Click to expand...
Click to collapse
The dev has reported that it has issues (if you can replicate the errors, send him a logcat)
hes on the forums on this site
SOLVED
Thanks a lot. I will try and write-up (on dev's site) of what I was doing when it happened. It happened to me twice so I don't think I will use it again (at least until it's fixed). I am a backup freak so I like to use multiple apps but nandroid seems to cover it all. I will stick with what seems to work (and work well) for now.
On a side note, Cyan's latest looks too juicy not to try out. Going to upgrade now.
Wonder if you guys could help me.
I've been using Froyo 2.2 on my Galaxy S for a while with no problems, upgraded through Kies.
All of a sudden today the screen stopped being responsive - ie I could swipe to unlock it but then the screen was that slightly grey/dull colour as if the screen was about to turn off. The touch screen basically became unresponsive with the only button that worked being the main home screen button, which would switch between the zoomed out view all of my homepages and my main homepage. Didn't think much of it so rebooted the phone (also I haven't installed any new apps or made any big setting changes lately).
However, when I rebooted apps like Titanium Backup, LaucherPro, NetCounter, Handcent etc kept force closing automatically making the phone almost unusable. I've tried restarting the phone, taking the battery out but to no avail. I then managed to switch to the default samsung launcher and reinstall some of the problem apps which sort of helped, but the more apps I try the more I find just crash upon starting.
What's the best way to solve this problem, preferably without loosing all my data/settings?
Seems like something has become corrupted, and I'm a bit worried this has happened so out of the blue....
Really don't want to have to a factory reset if possible, but looks like I'll have to
i think wiping the cache may do the trick, it happened to me after installing new theme. couldnt even use it for 5 mins to back up my stuff. i wiped the cache in recovery and that fixed it.
I tired wiping the cache in recovery mode but didn't help much (other than allowing me to use TWLauncher, and hence being able to semi use the phone).
Don't have a backup either , mainly because since upgrading to 2.2 I can't get any rooting methods to work oddly.
Could be in a for a long evening....
What really gets me is that it just happened randomly. I just tried to use the phone after it was in standby and it just wasn't responsive - after the reboot the force closing apps problem occured. I wasn't trying to install anything, bit worrying really.
i think the only way to get back to normal is a factory reset. i dont personally know any other methods. but its upto you to wipe the phone or keep searching for a solution.
the cause is probably through some sort of corruption or wrong setting in an application, i wouldnt panic about the phone dying or anything lol, just a ball ache restoring everything..
Hope you get it sorted remember to make a backup when its fixed. i make backups on a weekly basis as im constantly flashing and modding, and it makes life soooo much easier.
azzledazzle said:
i think the only way to get back to normal is a factory reset. i dont personally know any other methods. but its upto you to wipe the phone or keep searching for a solution.
the cause is probably through some sort of corruption or wrong setting in an application, i wouldnt panic about the phone dying or anything lol, just a ball ache restoring everything..
Hope you get it sorted remember to make a backup when its fixed. i make backups on a weekly basis as im constantly flashing and modding, and it makes life soooo much easier.
Click to expand...
Click to collapse
Yeah I had a feeling that was going to be the outcome , ah well!
I normally do backup, just I haven't been modding or flashing much lately so assumed android wouldn't just die on me! Lesson learnt, always backup!
The phone is still usable, so I should be able to do a backup of my apps.
if you can still do backup... all is not lost then.
Sorry for the vague title, but I couldn't think of a concise way of describing this.
I have a T-Mobile HTC One with the GPe ROM installed on it. I'm on 4.4.2 and using ART. I woke up this morning to find my phone in a boot loop. It would come up with the screen that shows the "Google" logo and the icon showing my phone is unlocked, remain on that screen for longer than normal, then reboot and do it again before getting to the actual ROM boot sequence.
I held down the power button to shut the phone off. When I turned it back on, it made it to the ROM boot, where the four colored circles fly around, but then came up with a screen asking for my disk encryption password. I've never set up encryption on the phone. I didn't want to try passwords I use in case this was some kind of phishing, though I'm not sure how that would be possible. At this point I wasn't really in the mood to do much troubleshooting so I did a factory reset from the bootloader and it seems fine now.
I'm just wondering if anyone knows what happened.
kernco said:
Sorry for the vague title, but I couldn't think of a concise way of describing this.
I have a T-Mobile HTC One with the GPe ROM installed on it. I'm on 4.4.2 and using ART. I woke up this morning to find my phone in a boot loop. It would come up with the screen that shows the "Google" logo and the icon showing my phone is unlocked, remain on that screen for longer than normal, then reboot and do it again before getting to the actual ROM boot sequence.
I held down the power button to shut the phone off. When I turned it back on, it made it to the ROM boot, where the four colored circles fly around, but then came up with a screen asking for my disk encryption password. I've never set up encryption on the phone. I didn't want to try passwords I use in case this was some kind of phishing, though I'm not sure how that would be possible. At this point I wasn't really in the mood to do much troubleshooting so I did a factory reset from the bootloader and it seems fine now.
I'm just wondering if anyone knows what happened.
Click to expand...
Click to collapse
Just don't use ART for now, stay with Dalvik. Much stable atm.
alray said:
Just don't use ART for now, stay with Dalvik. Much stable atm.
Click to expand...
Click to collapse
I wasn't planning on switching back to it. But that's not really answering my question about if anyone knows what happened. Unless you're saying that this is a known problem that happens to people who use ART, but it sounds more like you're just saying since I was using ART and something went wrong, it's a good chance that was why.
kernco said:
I wasn't planning on switching back to it. But that's not really answering my question about if anyone knows what happened. Unless you're saying that this is a known problem that happens to people who use ART, but it sounds more like you're just saying since I was using ART and something went wrong, it's a good chance that was why.
Click to expand...
Click to collapse
What most likely happened is ART corrupted the system and it forced a bootloop. You may have to full wipe and reflash. I would also advice to stay away from ART. It is not made for users.
zelendel said:
What most likely happened is ART corrupted the system and it forced a bootloop. You may have to full wipe and reflash. I would also advice to stay away from ART. It is not made for users.
Click to expand...
Click to collapse
I did a factory reset and so far everything is fine. Are you saying there might still be an issue and I should wipe and reflash to be safe?
kernco said:
I did a factory reset and so far everything is fine. Are you saying there might still be an issue and I should wipe and reflash to be safe?
Click to expand...
Click to collapse
I would just to be safe. Mainly with the pre-Alpha tag of the ART compiler. I mean it may not even make it to be official.