Related
I've read lots of comments, these very unwanted random hard-resets are suppose to be a common bug, however the suggested fixes dont seem to work for me, anyone else having the same issue?
Note: The issue must be software related, it only started happening to me immediately after a ROM update a few months back.
What usually happens:
- Install a ROM -> Configure It -> Install Apps... all looks good
- At some random point (could be days or weeks) the phone will lock up (usually on the password screen)
- A soft reset is required to rectify the lock-up
(i.e. the red button on back of phone)
- Phone hard-resets itself
Suggested Solutions:
1) Upgrade to HardSPL 1.93 - made no difference
2) I have tried running MTTY a few times, also no difference
3) Try different ROM's, I thought it might be just a bug with the WWE ROM, but it happens with the Energy ROM too
Just out of interest:
Interestingly, my wifes phone, which I do exactly the same updates on (same phone, same ROM, same Radio, etc), is working completely fine...
Hi
i had the same problem...for solve the problem, just flash the stock rom...you can download from htc website...than you can flash any rom you like and everytjing will work fine.
for any help just ask!
businello2000 said:
Hi
i had the same problem...for solve the problem, just flash the stock rom...you can download from htc website...than you can flash any rom you like and everytjing will work fine.
for any help just ask!
Click to expand...
Click to collapse
Hi, thanks for suggestion, although yep I tried that too. There is no stock ROM for an imported phone on Optus, but I just used the stock Telstra one that was on the forums, then after a while went back to the WWE ROM, and the same issue still occurs.
No other ideas for resolving the hard reset issues?
Next time it happens, I might try pulling the battery out instead of using the reset button on the back of the phone.. but clearly something is wrong :-/
i have had this a couple of times, about 6 months ago and last week. i just flashed a different ROM, flashing the same one again didnt help, so just downloaded a different one and went with that.
seems to be ok now
flash this rom and do a hard reset after flashing:
http://uploading.com/files/WY03RBG2/Stock rom noSPL no Radio.rar.html
I've also posted the same link here:
http://forum.xda-developers.com/showpost.php?p=4057376&postcount=3
matrix77 said:
flash this rom and do a hard reset after flashing:
http://uploading.com/files/WY03RBG2/Stock rom noSPL no Radio.rar.html
I've also posted the same link here:
http://forum.xda-developers.com/showpost.php?p=4057376&postcount=3
Click to expand...
Click to collapse
Thanks again for suggestions so far, but above fix only lasted about 5 days before another intermittent phone crash & subsequent hard reset, much the same as I have had experimenting with a range of stock and other ROM's :-/
I don't think the fix is as simple as just putting a Stock Rom -> Hard Reset -> MTTY -> New Rom -> Hard Reset. Im pretty sure its a software problem, but I dont see how the problem can survive such rigorous formatting...
Is noone else having the problem? Sounds like most are solved with 1 use of MTTY.
I searched a lot and found your thread.
I was upgrading my friend's Diamond, when he tells me that it hard resets itself without a reason. At first I thought it was the ROM's problem, so I switched to another one. But after I flashed the ROM, during the process of setting up the phone (settings, softwares), at some random point of installing random software, the phone says that the software was not installed successfully. After several re-flash, re-install, and ROM switching, it appears to me it's not a software problem.
It seems that it's at some point when the internal storage (not the NaviNAND) reaches a specific size, the device would fail and hangs (or not, randomly, but you can't install anything further), after a soft-reset, it will hard resets itself instead, it looks like some "badblocks" (sort of) on the internal storage NAND to me.
Is there a way to figure out if my theory's correct? I'm wondering if there is any tool that can run some diagnose on the internal NAND. If I'm correct and there is tool that can do so, it must have the ability to mask the bad pages on the NAND, right?
EDIT: There's a way to re-produce the situation. Just download some big apps (several MBs big) and install them in order. It will almost always hang at the same point.
The only solution is:
1st MTTY and run task 29 to format the device to make it clean and no left over stuff from the last ROM.
2nd Install different ROM
If you have bad sectors in the device, MTTY might not help much here, I guess.
Hi maddie, yes you might be onto something, I assume you already tried the usual fixes: (Stock Rom -> Hard Reset -> MTTY -> New Rom -> Hard Reset)? You can tell it to format the NaviNAND during the hard reset.
I think my issue might be different to yours though, as mine does not happen 'when installing software' mine happens days/weeks after setting up the phone.. It usually goes down like this: I pull the phone out of my pocket -> its locked on the password screen usually (cant type) -> pull the battery out or press the soft-reset button -> bang.. phone hard-resets.
I will make 1 suggestion though, instead of using all the nice fancy mods, and SPB Mobile Shell (looks like sense ui), I went back to a boring old stock rom, and well after 1 month its still going.. I absolutely hate it, but I dont want to buy another phone quite yet, so gonna go old-skool.
Let me know how you go, and as above if you did all the standard suggestions? It sounds like you need to somehow instruct the phone not to use those bad memory spots, but ive no idea if such a tool exists im afraid.
maddie said:
I searched a lot and found your thread.
I was upgrading my friend's Diamond, when he tells me that it hard resets itself without a reason. At first I thought it was the ROM's problem, so I switched to another one. But after I flashed the ROM, during the process of setting up the phone (settings, softwares), at some random point of installing random software, the phone says that the software was not installed successfully. After several re-flash, re-install, and ROM switching, it appears to me it's not a software problem.
It seems that it's at some point when the internal storage (not the NaviNAND) reaches a specific size, the device would fail and hangs (or not, randomly, but you can't install anything further), after a soft-reset, it will hard resets itself instead, it looks like some "badblocks" (sort of) on the internal storage NAND to me.
Is there a way to figure out if my theory's correct? I'm wondering if there is any tool that can run some diagnose on the internal NAND. If I'm correct and there is tool that can do so, it must have the ability to mask the bad pages on the NAND, right?
EDIT: There's a way to re-produce the situation. Just download some big apps (several MBs big) and install them in order. It will almost always hang at the same point.
Click to expand...
Click to collapse
I got the same problem recently and I am still trying different way to solve it.
My Hard-reset happen:
After flashing new rom -> Installation of software ->
-> launching programs -> when some got may holding or loading without response
-> Soft-reset (red bottom) -> It automatically Hard-reset....
Similar thinking with you, I think that maybe one of those reasons leading the hard reset:
1. Device got bad sector while flashing for different roms;
2. New Radios got bug and crash with the new version of roms;
3. Too many things stored in Internal Storage;
kenleekwanho said:
1. Device got bad sector while flashing for different roms;
2. New Radios got bug and crash with the new version of roms;
3. Too many things stored in Internal Storage;
Click to expand...
Click to collapse
I like this logic, im in the position of owning 2 HTC Diamonds with identical ROM, Radio, Applications, 1 works perfectly, 1 is resetting.
It 'probably' indicates that its hardware related, I doubt its Radio (due to the other phone working fine), so could be Internal Storage or Bad Sector.
Im not even close to filling up my internal storage though, so if its storage related, perhaps a particular sector is the problem (like maddie was mentioning).
Thanks for all your opinions!
It's the first time for me to think it's the Radio's problem. It comes to me now it seems this situation starts when I flashed the 1.15.25.14 radio. I will try another radio and update here.
I dont 'think' its Radio, but worth a shot.
I cant consistently reproduce my issue, so it could take me a month to find out if ive fixed the issue.. and there are a lot of variables in a month. But sounds like you have a way of reproducing it consistently, gl.
OK, it doesn't seem to work. I think that's it..
Maybe I should start looking at the bootloader commands..
ive got the same issue, but only with some ROMs, for example, the AZTOR X3 and GEN.Y D2 didnt work, but gen.y 1.4 worked for me.
I tried MTTY method to re-flashing, it seems fine to my diamond right now.
i have the same problem, i have tried about 10 different roms, but i don't think it's software related, i think it might be the phone overheating causing a faulty component, it started 2 days ago for me and usually after 5-10 min it crashes, and it started happening when the weather heated up and it will crash quicker if i try to charge it, anyone notice this?
Has anyone found a solution to this?
For me it started when I installed the Gen Y rom with the android dual booter (but not android itself). I have tried MTTY, Stock ROM but Im still experiencing the problem. I suspect it has something to do with the dual boot.
I get the same thing. soft reset = hard reset.
I have tried several ROMs but now the phone hangs on the loading screen
The UK 3.4.2-117 froyo showed up not to be as stable as first seen, some apps crash all time and the phone to from time to time, especially the screens keeps to timeout alot and sometimes freezing the phone totaly when doing it.
Anyway, when trying to install the sbf rom with eclair 2.51 with RDS i am able to install it but not able to make the phone to start after that. Any suggestions to why, is this due to the current 2.51 eclaire version beeing branded? I started out with a 2.21 version before going to the new gb froyo rom. Pherhaps not downgradable meant exactly what it said
Thanks for suggestion...!
I have had no problems whatsoever with the UK Froyo release. In fact, I find it to be the smoothest release yet, as I have mentioned in its respective thread; Even without overclocking, it is a lot smoother than the Chinese Froyo and 2.34.1 and 2.21.0 before that. Ofcourse the quadrant 'score' is lower, but as I do not use my phone mainly for benchmarking, I do not mind in the slightest.
Anyway, before I go off-topic too far..
Have you made any modifications to the release after you put it on your phone? Did you perhaps not wipe the data/cache? Is it possible that you are overclocking your phone to such an extent that it is no longer stable?
And for some specifics - which applications crash all the time for you?
And indeed - you can not downgrade unless you've followed the instructions in this thread by Higgsy, but I doubt you have.
Incidentally, nor have I, but I have no problems whatsoever with this release and since we have the same phone, I suspect you have changed or installed something to cause your problems.
Hi!
Yes basically i got a new defy, UK retail, it was never rooted or anything and i just applied the new ROM with RDS. So no, I had not done any changes to the version what so ever and i reinstalled it twice, always making sure to offcoures wipe it also.
My main issue is actually that the screen times out alot, and sometimes locks the phone so i need to take the battery out. Also a music app (spotify) crash inevitably all time, it comunicates with the memory card as it catch up the music as you listen so thinkning that it may be some issue there. Have seen some of my other apps also force close, and this has never happen to me on this or my second (my gf's) defy i had had for some months now.
I to however are supprised about this as I can see that no other is experience this issue, espeically the screen timeout issue wich is very annoying and happens alot especially when using the browser
Will try to find a new microSD card later tonight to see if my memory card pherhaps have been somehow dammaged during the ROM installation... (dont belive at all this would have happend but worth a try i guess)
Thanks
Hm. That is quite the pickle you are in.
Can you install Catlog, filter on Errors, and tell us what it reports? You can run the application after you start the phone and have it log to file - you can put the file in
Code:
tags here to make it easier on the eyes. There may, or rather - should be a clue in there.
Alternatively, you can use 'adb logcat' from a command prompt in the Android SDK/platform-tools to get the log files to display outside the phone.
another reinstall of sbf did the trick! Will try to run the logcat to later to figure out what the app problem could be (maybe sd card read write issue I think as sameprobkem with second card) but now the phone works otherwise perfect, many thanks...
Good to hear - enjoy the shiny new release
Same problem help.
Hi I flashed the UK 3.4.2-117 froyo ROM with RSD.
My Defy was T-Mobile UK, 2.51 ROM.
After flashing the phone starts but I only get a black screen.
The softkeys are not responding but I can tap down the notification bar and open a task manager program that I had pre-installed which allows me to switch through applications. I can open various applications and the phone seems to be working like this.
I rooted successfully and then I tried to reboot into recovery using Clockwork Mod but the phones stays at the motoblur logo.
Is there anyway to downgrade or at least make this rom working?
Michalis
I have experienced some things like you sayed; some apps get closed, and frozen phone and can't even turn off the phone
so i uninstall some apps that i don't need, and get a app name SystemPanel that monitorize the CPU use to see whats going on
Since then, i don't see more those things. I'm watching see whats going on
Hi guys,
I need your expertise and ultimately your help!
So i was running Lee droid for months, it was all good, did loads of flashing of roms without never any (massive) issues.
Last week, i decided i wanted to try gingerbread, so I flashed gingervilain and the kernel that went this it. I din't really like it, i missed sense too much so i decided to go back to Lee Droid.
I did a clean install after wiping everything as i've done dozens of times in the past. But ever since a problem has arisen.
Whenever I'm on call, when i move the phone away from my face, the screen doesn't turn on and I can't turn it on at all, even when i press on the power button. Which means i can't hang up. So if i call someone and end up on voicemail, I need to remove the battery to finish the call, and whenever I am on the phone with someone I have to ask the person to hang up as I have no control over the phone.
The phone is to be totally irresponsive.
I tried to re-install gingervillain and had the same problem. So I reverted again back to Lee's rom, from a clean install and the problem persists!!
Last night I tried to format the card and I installed snq's new kernel, but it still doesn't work.
I have no clue what's going on. Could it be a voltage issue???
I'm s-on by the way.
I'm seriously confused at what the fark could be going on!?
Anyone has any idea?
On Lee's rom forum, a poster told me to flash a RUU or WWE rom. But I don't really wanna do that for two reasons :
1. I'm not sure it will work since installing Lee's rom on a clean install didn't solve anything
2. I don't really wanna go through the hassle of rooting my phone again
Thanks!
Using an RUU is your best bet since no one knows wtf is going on. I would say to do that as well and I'm sure maybe a few others would. Yes, you would have to root again (not like it takes forever and not like you have to do anything other than plug your phone into your PC and run the unrevoked utility, seriously). That would be your best chance for fixing it. BTW, using an RUU would wipe everything out and start fresh so it probably would fix the issue.
If it doesn't... well, that's for another time.
u can try go into settings turn off senser
exit settings
then go back in settings again set the senser on again
I see more and more people having the deep sleep bug, rooted or not.
Wish I knew how to fix the damn thing! The only sure thing is that if the phone is at stock condition (rooted or not does not matter), it doesn't have the problem.
When I install some apps, it would start doing this!
Alright, I guess I don't have much choice then! I'll flash a ruu.
Thanks a lot fo your help guys
The problem I'm having is now that I have Leedroid 3.3.3 installed on my Desire HD my phones camera will no longer auto-focus.
Before you ask have you made sure the auot-focus is selected in the phones camera menu yes I have.
The things I have done to rectify this are:
I've made sure I have the right Radio & Kernal for the Rom I'm Using
I've downgraded my Leedroid Rom to previous versions but nothing works
I've asked for help and left bug reports on leedroids mini site and no help
I've tried to install the Madaco 17/Nov 1.32.405.6 r1 - HTC Desire HD Stock ROM with Online Kitchen but I can't boot past the HTC screen even performing a factory reset, battery stat rest, and a dalvik wipe still no luck.
I'm not sure if Leedroids new Roms uses a different EXT format like "EXT4" where stock Roms use "EXT2" and this is why I cant get MOdacos stock rom to boot and therefore I need to wipe a EXT2 to my phone? I wouldn't know how to do that anyway.
I've done google and xda searches for how to get the auto focus to work again and all I come up with is I should go back to stock and see if this helps. Unfortunately I can't get a stock Rom to boot properly so I'm left with asking for help here.
If I'm in the wrong forum or posted in the wrong place I do apologize I believed since I'm on a Desire HD this is the most appropriate place.
Hi!
Did you solve it?
I have the same problem, the camera don't make the focus, don't know why.
thanks!!
Any solution in sight?
I have similar problem on my classic Desire (Bravo).
Autofocus fails on far away objects, everything closer than ~1m is ok, anything else I recognize some focus action in the live image but it stops on the blurry side
Using InsertCoin 1.1.1 with the latest Radio.
Seitchin ROM to an older LeeDroid didn't help)
No luck yet I'm afraid I'm in the process of backing up my phone and trying different roms to see if that helps.
I'll post here if I come up with a solution.
Solution
So I called HTC here in the UK and was told the phone needs to go back which I sent to them but before you do there are two important things to remember.
1) s-off needs to be turned to s-on
2) you need to send the phone back with the latest os version
I got my phone back and the lovely guys at the service centre even replaced the entire shell, battery cover and sim cover for free how nice.
I'm going to guess it was a hardware issue rather than a software issue because the phones software came back exactly as I sent it with t-mobiles splash screen with no sound because the sound files were never on my phone to start with.
I tried everything before sending it back updating, different roms going back to stock rom etc etc but the only thing that worked in the end was HTC fixing it.
Luckily the phone was still under warranty and the shipping and repair was free phew!
Good Luck
Hello and good afternoon,
I received this Xperia Arc (LT15a) from my dad to fix and I can't get it worked out so here it is
When you unlock the phone the screen responds to touch, I can swipe back and forth as one would expect. If you keep your finger on the screen or touch it atleast every second the screen stays responsive. If however you stop using the screen, sometimes for 10 seconds most the time just 1 second and the screen will no longer respond. In order to get the screen to respond you have to lock the device and unlock it again, as if refreshing it or restarting the touch screen service in the phone is the fix... temporarily.
I saw a thread somewhat like this and the fix was to downgrade to make sure no bad firmware had been put on so I downgraded to the 4.0.2.A.0.42 that the phone shipped with. This didn't solve the issue. I tried all sorts of firmwares thinking perhaps one would work. My dad tells me that this started happening when he updated the phone to 4.0.4 through the Sony upgrade software.
Has anyone run into this or do you guys believe this is more likely to be a hardware problem (which seems strange because I would think the screen should either work or not)
Thank in advance.
Hi @Laydas,
This is a weird one, for sure.
I've seen something similar on my phone, and for me the problem was definitely linked to an "upgrade / downgrade" kind of thing.
My solution was to install another rom.
So now I guess your bootloader is locked (because the phone is not rooted).
So the best thing to do is to try flashing a stock rom using "flashtool".
Here's some pointers to help you on your way...
Try this thread - http://forum.xda-developers.com/showthread.php?t=1304634
you're looking for info on flashtool, and on stock roms (I think that some stock roms are available in post 2 of the thread)
On top of that, there is an older thread (so a bit outdated) here - http://forum.xda-developers.com/showthread.php?t=1133650
It has good background reading thread to get a grip on all the ideas involved.
Good luck
I forgot to mention that I had already rooted the phone
I have used flashtool to restore the stock rom which didn't solve the issue either.
I have now taken the phone apart to check for loose connections, everything looked good.
I put the phone back together, tried it out, I still have the same screen issue.
Laydas said:
I forgot to mention that I had already rooted the phone
I have used flashtool to restore the stock rom which didn't solve the issue either.
I have now taken the phone apart to check for loose connections, everything looked good.
I put the phone back together, tried it out, I still have the same screen issue.
Click to expand...
Click to collapse
OK, wow. This problem is really sticking around.
So my next question is: - Do you have an unlocked bootloader?
If yes, then try flashing a custom kernel and a custom rom.
My favourite ICS based rom is JJ's Hybrid - http://forum.xda-developers.com/showthread.php?t=1537717&highlight=jj+hybrid
It works 100% with the ArcKnight kernel.
If your bootloader is locked, then you cannot flash a custom kernel. You can still try try the JJ Hybrid rom to see if it sorts out the problem.
At this point I'm running out of ideas. For me this issue was software related, so flashing a different kernel and rom fixed my problem.
It seems like your issue is software related too (because it popped up after an upgrade), but if you flash a rom and a kernel, then there's not much else that you can try flashing,,,
OK, maybe there's also a base-band you can try flashing - There's a base-band thread here - http://forum.xda-developers.com/showthread.php?t=1688049
So try a custom rom and a custom kernel, and if that fails try updating your baseband to 72 or 77.
That's all I can think of to completely overhaul your phone's software.
Please let me know how it goes...
Take care,
Hotfingers
The bootloader is locked on this phone unfortunately.
This phone is not like my other phones, even trying to get a custom rom onto it is a hassle as installs from zips in CWM almost always fail.
Pushing roms from flashtool works but I couldn't find the JJ hybrid rom in a ftf format for flashtool.
At this point I will continue trying to get a custom rom onto this phone when I have time but it has dropped off my priority list as it is being so difficult haha.
Thanks for the help, hopefully sometime next week I will be able to go through some of these steps and get back to this post on what helped
Laydas said:
The bootloader is locked on this phone unfortunately.
This phone is not like my other phones, even trying to get a custom rom onto it is a hassle as installs from zips in CWM almost always fail.
Pushing roms from flashtool works but I couldn't find the JJ hybrid rom in a ftf format for flashtool.
At this point I will continue trying to get a custom rom onto this phone when I have time but it has dropped off my priority list as it is being so difficult haha.
Thanks for the help, hopefully sometime next week I will be able to go through some of these steps and get back to this post on what helped
Click to expand...
Click to collapse
OK, thanks for the feedback. This isdefinitely weird...