Recently my phone has been suspending the screen and not bringing it back when I press the power button. I was running 3.2.6 before, reverted to 3.2.3. Tried hard-resets, taken out the battery, tried running with just the rom and nothing else installed after flashing, still doesn't work.. I've also tried taking out my memory card and running without that.
The power button still works because it will still turn the phone on, and bring the phone out of sleep sometimes, but if it doesn't work on bringing it out of sleep it seems that I have to soft-reset or the phone just doesn't work...
Any suggestions? Also.. I this is a bell phone, they have stock roms available on their site, but am I able to get the stock bootloader back on in case I have to warranty this thing?
You've tried most things that people could suggest, however have you tried a different ROM?
I know this used to be a very common problem when the Tilt came out, but once everybody started changing ROMs, it slowly disappeared.
My suggestion in short: Try relocking the bootloader
My Two Cents:
This is actually the most evil bug ever for this phone. I got this bug on my Sprint Mogul and couldn't get rid of it. Some people say it's because Java is running and then causes the phone to hang, but I never found that to be the issue. I got a Verizon XV6800 and experienced this problem only when I was flashing from stock to dcd 3.2.6. It occurred after I unlocked the bootloader, but after I flashed to dcd it went away. It was between having the stock and dcd roms that I found that most people experienced this problem when the loaded they new bootloader.
If I had to guess, based on my knowledge of operating systems, that some process is taking up a lot of resources, mostly CPU time, and is not allowing the phone to come out of standby. I guess this because sometimes I have had this happen and the screen would come on after a LONG delay.
Related
I don't mean to cause any alarm...but I just convinced my friend and coworker to upgrade his ROM to one of the latest builds here to enable GPS support. Upon installing the 2.40 bootloader he has been experiencing a rather high frequency of lockups on his Mogul when the screen is off (i.e. the device's screen will not turn on, although he still has the flashing green LED indicative of a cell signal). He only upgraded to the 2.40 version and hasn't done anything else and I have firsthand experience seeing this happen. The only thing he has changed in weeks is the bootloader, suggesting it's the culprit.
What's funny is that I've also been experiencing this, although far more sporadically, since Monday afternoon or evening. Anyone else experiencing this recently?
Same here. I have Olipro 2.40 loaded waiting to pull the trigger on loading the ROM. Since I'll probably wait another day or two for a verizon 3.16 rom with WM 6.1, I'm probably just going to relock the phone until then. On the other hand, if you just reset the phone first thing in the morning, it seems to be fine for most of the day, so no big deal.
Have HardSPL installed on phone. Got phone on eBay - has very few hours. Came with a Rom that displayed TEST ONLY which was WM5. GSM radio worked, Bluetooth worked and Wifi worked. Tried installing shipped HTC WM6 Rom - did it through ActiveSync - should have used MSD card. - Rom installed though everything was ok but didn't install a SIM card to test phone - used it as PDA and WIFI for a week no freezes. Now this morning wanted to switch phones over and inserted SIM - saw NO GSM on boot - never really noticed it before.
Checked in ABOUT section to see if a radio was loaded - comes up blank. Read some things about NO GSM errors - got a little nervous - so I thought I'd reflash entire ROM tonight with SD.
Followed directions and get into update process and it seems to freeze at GSM with progress bar at about 15% - for about 30 minutes.
Removed battery and it boots to TRICOLOR. (I freeked out at this point)
Put a HardSPLv7 on SD card and did the above - update was successful
Phone boots up to OS still with no GSM
Tried the update process again with the same ROM - still has problems and never gets past the same point as before. Will try another ROM but I'm a little doubtful. If I can recover it back again will try just upgrading radio to see if it makes a difference.
ANY SUGGESTIONS or is the hardware fried?
Thanks.
OK, think it may be back and I was able to reflash using a wm6 stock HTC ROM. Think either my original flash of the same ROM was bad - downloaded a new file and flashed with the SD - originally did it via ActiveSync.
To get it to work I did a couple of hardspl reflashes and got into the OS. DID a couple of hard resets and magically GSM appeared. Turned phone off and then NO GSM appeared again. Did the hard reset again - came back. Not taking anything for granted put in a SD card and reflashed. Held my breath and for some reason it did a complete flash and never really hung up for more than a minute or two. Soft reset - GSM was there. Turned phone off and on a few times and its still there. Phone now finds the GSM radio much faster than before. Can make and receive calls (does wake out of sleep) - signal strength is same on my other Cingular 2125. Will try out tomorrow and see how it goes. Either the reflash does it or something is loose in the hardware but if it works a few hours tonight it should be good.
Will be a little hesitant to reflash after this but will see after a stress test.
Hold both softkeys and hold the power button
You can also hold both softkeys and put the stylus into the reset hole. Tell me if that works.
Initially no. When I attempted to flash the HTC Factory Rom it froze. Prior to that I did a couple of hard resets using the two softkeys and reset pin. With the resets couldn't get the GSM radio to turn on. Tried the ROM flash but it froze (about 1/10 of the way) - so I basically OS bricked it by removing the battery when it was at this stage. Got to the bootloader screen. Tried to flash OS again with SD card - still froze. SO I thought reflash HardSPL and the OS magically appeared and did the steps above.
After a couple of hours - call made, turned off and restarted device no problems still have GSM radio. Can receive a call when in standby. May try to do another hard reset and see if it still works after a day or so of testing phone but I want to try it for a few days by turning it on and off and making and receiving calls. If I can do another hard reset and everything works I think it was just a bad initial flash through ActiveSync. May get bold and flash another ROM as a test.
Since the phone worked with the TEST OS when I got it I think the only factor is the WM6 flash that I did. More than likely the hardware is OK but only time will tell.
I don't believe you will recover your radio rom now as you interrupted the flash. It generally takes 30 MINUTES to flash a complete rom. You stopped it during the radio rom flash, BIG MISTAKE....
If you can find the SHIPPED STOCK ROM or the original radio rom then you might have a small chance at recovery, we're talking about you winning the lottery 10 times in a row chance...
If you try to flash anything but the original radio rom then you can kiss the phone functionality goodbye....
Good luck finding the right roms...
Cheers...
Its not bricked. In my post said I did a full recovery and its working with the stock HTC WM6 ROM with the HTC radio. I can receive and make calls. Able to ActiveSync with the PC and have hard reset a few times just to make sure all is well. I believe there is still a hardware problem - either a loose connection inside or something else is going on but I think its definately hardware. When the stylus is out of the holder EVERYTHING works fine - have a signal - can sync - can charge it - no issues. If I put the stylus in part way no problem - push it in all the way during a call it will still say connected yet will hear nothing and can't disconnect. Pressing end has no effect yet the phone will still function - just the in call symbol stays and the green led still flashes.
Turn it fully off and back on with stylus out - shows GSM radio code and phone will now work.
Have to check the service manual to see if the stylus holder when the stylus is inserted pushes on anything vital. Can't imagine thats it. But so far with the stylus out everything is ok. Will attempt to use it tomorrow see if thats it.
Know it sounds stupid but thats what I'm observing so far. Its late here see what happens tomorrow
Thing is running and can use the phone (no static, three bars) but last night had a few no GSM messages during a cold boot. Ran it all night and it seems to be working - booted a couple of times, charged it, sync'd it and actually put the stylus in (don't know if thats the problem) and still working. May be a loose connection that is currently ok but who knows when it will stop working. Other possibility is heat or a failing radio. Could also be battery but thats doubtful. Could have messed up the stack during the initial flash so I'll see over the next few days. This one is starting to drive me a little crazy because it works then for no reason it will stop then resume after a hard reset or reset. Could also just be the version of the ROM I'm using but it came from the repository on XDA-Developers. Just rebooted it when I was typing this and it still finds GSM radio.
Tried it for a day and I think the radio is fried. Started out finding GSM then when driving around with my Bluetooth heard a bleep which indicates loss of signal - saw it hunting then it finds the signal. During a call for about 3 minutes just drops call and on the screen the dialer won't let you disconnect the call.
Rebooted got the NO GSM message - eventually found it - briefly then NO GSM again.
Tonight opened it up and reseated and cleaned motherboard contacts including radio. After hard reset got GSM again - briefly. Then no GSM
Tried upgrading and downgrading radio via SD card - no go would only hang up Tried complete with OS - same thing. Tried through ActiveSync method SSPL and got same.
So I think the phone is pretty much not really a phone - can still boot into OS. May try some more but I think its definately a motherboard issue. Shouldn't be that hard to flash and the GSM should at least be stable.
When I bought it on eBay and first turned it on saw a TEST ONLY message on boot with a WM5 Rom. The seller was a little vague just said it freezes sometimes. Got it cheaply thankfully so I'll keep hunting around for another unless someone has a suggestion?
The Radio seems to be the touchiest part of the Hermes. When it fails theres nothing that seems to be able to fix it. Look for another cheap Hermes. At the very least you will have spare parts.
how weird is this I have just gone through just the same problem and took a day to sort it out . ok here is what I did in the end . now what you need is any official rom pref wm5 . I can send you a link if needed to the one I used ... now try flash it from the pc it will stop at 12 percent ....... now take battery out and boot in bootloader mode .... now flash any rom that's wm6 etc .... devise will restart .... now take battery out and re boot it may take two or three boots to get it working prop without the no gsm error but trust me it will boot . when its booted up flash the original wm5 shipped rom run through the rom sequence and when its waiting to flash saying zero percent manualy put your phone in bootloader and wait 30 odd min tadaaaaa phone is now perfect ... now flash any rom you like as the radio is fixed . its something to do with the 12 percent bit it hangs on .??!!! sorry its long and complicated but I have my hermes back to life through doing it ................... let me know how you get on bud. if needed 07832999919 uk . so its 0447832999919 oh I have hard spl 1.40 spl 1.1 or something lol can't remember . anyway good luck
Ok, think I initially really messed up my flash and the WM6 which was the official HTC version may have been corrupted but showed full flash. When I tried again I would also get the 12% even with a SD flash. So I tried flashing just a RADIO ROM which did complete. The NO GSM message still would pop up maybe 50% and not necessarily everytime.
When to MTTY.EXE and did a bad block check - no problems
In MTTY did a FORMAT/CLEAR.
Left everything alone and again reflashed just the RADIO - things seemed to be better - less NO GSM.
Tonight - just before you posted I successfully did a complete reflash with the HTC WM6 rom with Radio 1.48. Very surprised it worked this time - no hangups except during the GSM part which only stopped a minute or two.
Complete reflash in about 10-12 minutes with the SD card method.
SO far things are working - tried a reboot a few times and now radio is found every try. Will try for a few hours and try again tomorrow.
What I did have is a white screen/with image once - it was cleared by just pressing briefly the power button. So it may be heat related - don't know.
Keep me posted in this thread whats going on and I'll do the same.
What ROM WM5 did you flash to get yours to work?
Spoke too soon! Put in a sim card - powered up and it worked. Tried making test call and it worked. Tried again and it showed dialer and dialing and never connected. Could not use the dialer to hang up. Also showed drop in network. Tried turning phone radio off in dialer and back on - showed !X. With the phone off hook image at the top bar. Tried again - same thing. Expected to see no GSM when power cycled and it did show NO GSM.
Right now its working even after a few power cycles but honestly I think the successful flashes may be due to the GSM radio being found. If it doesn't find the radio and you attempt to flash thats why it hangs. If you phone works for a few days or day I'd be very surprised. The real test is to try it when moving from tower location to tower location. Thats where I noticed the radio was acting up. With a bluetooth headset it will beep indicating a drop in carrier. When its doing this the radio isn't working properly and can't lock on to a signal
If your phone does work PLEASE post what you did and what files were flashed.
For my phone I think its heat related. Possibly the heat from the circuitry is opening up or stressing out a component causing it to fail. I really think my motherboard is faulty and reading on the HERMES this isn't that uncommon. Being that the phone has so little hours I think it must have been a return or factory reject.
More than likely I'll have to purchase another phone needing a screen or one thats in poor shape to salvage the motherboard and attempt to put it in my case since the housing and screen are pristine with little to no use. I've been told that any 8525 motherboard will work but I doubt it since the Dpad is different and I have a front video camera.
No, ANY Hermes mainboard will work... Hermes are identical internally, even the 8525 is able to use the front camera, it just isn't included in that model.
Cheers...
Thanks, makes my life easier!
ok mate i used htc orig rom by orange uk google the words,,,, orange spv m3100 update ummm ok hang on il grab the link for you ...
http://www.orange.co.uk/business/downloads/SPV_M3100_ROMUpdate_1007.exe then flash hard spl then update your rom to whatever you like ,,, hope this helps buddy
Might try it tonight but I really think I need a new mainboard. I am able to flash only when it finds the GSM and I think any hangups are due to the GSM radio circuity failing or some strange power flux on the motherboard. I am having strange multiple freezes/slowdowns as well as NO GSM errors. Tried a WM5 and WM6 specific for my HERM200 and no change. When it works it will work and make and receive calls but after a while without a load but under load - multiple calls, running excel or other things the radio will drop or it will attempt a call, not connect and will not let me hang up. No software update will fix this issue - it has to be hardware.
If I have successfully done base HTC ROM flashes - complete with radio phone should theoretically work. I have to face reality with this one which although looks pristine is a lemon and have to buy a working beat up 8525 and try the motherboard as long as the seller assures that the phone can make and receive calls without problems.
Also have other issues with screen fadeout which I know is tied to the dPad controller - but I can live with that for a while and I have a source for a part replacement and can try a quick fix to verify its just the dPad.
You got lucky so far - but if you try to use the phone all day running multiple programs or CPU intensive tasks your radio still may fail. You could also try upgrading the ROM again to something that is MFG and see if it takes.
It is possible to flash the OS without flashing the radio, It will be a cooked rom but they're better in most respects than a stock rom. Faster, leaner with all the bloatware removed.
No software change is going to fix this. Its not a software bug its a flaw in the hardware. Can't flash a radio Rom - thats a chip problem. Its basically a low level format and write to eprom. Thats pretty basic. Also making and receiving calls is also pretty basic. The dialer has been around for a while and is pretty stable.
Hello all,
I've had the same touchscreen? issues with 2 different Evo3D's. The first phone I had replaced even though when I took the phone to a Sprint repair center, the Slate machine said theres nothing wrong with the phone.
What happens is quite simply is the phone starts acting crazy. It acts like Im pressing on the screen, making tons of selections, calling people etc...I can click on the power button to make it stop. But then it will act up again in a few minutes. The first phone I had the store flash back to stock, turned s-off etc... It didn't make a difference. No matter what ROM is on the phone it continues to do it. So I had that phone replaced.
The second phone does the exact samething. If I didn't have the first phone in front of me when I received the second one, I would have thought they sent me the same phone back to me. I rooted this one right away as the other one so I dont know if the phone had the same problem before the root process. I've stuck on a ton of different ROMS to various degrees of success. I'm running Eternity right now because it allows me to at least use the phone semi functionally. The touchscreen problems are limited to the upper 20% of the screen where its unresonsive most of the time. But the craziness clicking is down to a minimum comapred to other roms.
I fixed the problem once when I was flipping ROMS and kernels. I put on ViperROM2.1 then flashed the Tiamat kernel. I was like yesssssss, I found the right combo. But alot of the phones functions didnt work like voice reconition, 4g, etc... So I cleared storage to start again and all the problems of the touchscreen as before came back. I've tried flashing kernels like Tiamat, stock, dual cores, single cores. Always have the same result. Last bit of info is I tried to superwipe and that failed. So maybe theres something in the internal memory thats causing all these problems? any help would be appreciated.
Thanks
kdub2000 said:
Hello all,
I've had the same touchscreen? issues with 2 different Evo3D's. The first phone I had replaced even though when I took the phone to a Sprint repair center, the Slate machine said theres nothing wrong with the phone.
What happens is quite simply is the phone starts acting crazy. It acts like Im pressing on the screen, making tons of selections, calling people etc...I can click on the power button to make it stop. But then it will act up again in a few minutes. The first phone I had the store flash back to stock, turned s-off etc... It didn't make a difference. No matter what ROM is on the phone it continues to do it. So I had that phone replaced.
The second phone does the exact samething. If I didn't have the first phone in front of me when I received the second one, I would have thought they sent me the same phone back to me. I rooted this one right away as the other one so I dont know if the phone had the same problem before the root process. I've stuck on a ton of different ROMS to various degrees of success. I'm running Eternity right now because it allows me to at least use the phone semi functionally. The touchscreen problems are limited to the upper 20% of the screen where its unresonsive most of the time. But the craziness clicking is down to a minimum comapred to other roms.
I fixed the problem once when I was flipping ROMS and kernels. I put on ViperROM2.1 then flashed the Tiamat kernel. I was like yesssssss, I found the right combo. But alot of the phones functions didnt work like voice reconition, 4g, etc... So I cleared storage to start again and all the problems of the touchscreen as before came back. I've tried flashing kernels like Tiamat, stock, dual cores, single cores. Always have the same result. Last bit of info is I tried to superwipe and that failed. So maybe theres something in the internal memory thats causing all these problems? any help would be appreciated.
Thanks
Click to expand...
Click to collapse
My guess is that something is screwing up kernal wise or your flashing. If your phone was fine stock then something got dicked during the flash.
Is there anything I can do to a clean wipe and start fresh again? Or should I try to figure out why the Superwipe isnt working? Or do I have to flash all the stock back on and turn the s-on and get a new phone? I think the digitizer is causing these issues.
Hi guys,
Lately I've been having problems with the WiFi and BT.
I know it has been like that for a while but I only noticed it yesterday.
The BT on the phone doesnt work - when I try to turn in on it just doesnt... I press the button and it stays the same way.
The WiFi doesnt work - when I try turning it on it says ERROR. and stays like that... not on and not of.
And not only that, another thing is that my phone started crushing A LOT.
I have no idea what's going on... it can crash at any moment without worning... not always coming back (sometimes I have to pull the battery out).
it can happen after 1 minute or after 3 hours...
the 2 things that changed on the phone lately are:
1. swiched from neutrino 2.8EE to 2.9EE.
2. I was in a vecation and when I tried to charge the battery it got only upto 82%. didn't cross it no matter how long it was in...(it was like that for a week).
I have to phone for like a year and a half.
help? anybody?
This is a known problem and it's been reported countless times already. Unfortunately the most likely reason is that your wifi/bt chip is fried. This is a hardware issue (more specifically, a design flaw) and there is no workaround. It has affected many others and they are just as pissed off about it as I'm sure you are. Some even say all Atrixes will sooner or later end up this way because of this design flaw.
Not sure about the crashing, but it could be related to broken wifi/bt.
Hi
I have same problem. I have Atrix 4G from UK Tmobile, with stock froyo. I flashed the stock 2.3.4 with RSD successfully, and i unl*cked the carrier.
Then i noticed, that Wifi don't work good. I don't know turn on: Wifi (error). The other problem, that the finger print scanner isnt work...
These actions do not help: factory reset, unlock BL, custom ROM (i tested Nottachtrix, any ICS ROM, stock froyo), erase all at fastboot, full wipe with CWM...
I am sure, that it is a software bug! (before flash 2.3.4 and carrier unlck, phone works fine...)
Some solutions? (I think, if we restore back to stock, the problem is solve) How can i make a fully reset, which is stronger than RSD flash stock sbf?
edit: http://forum.xda-developers.com/showthread.php?p=13754274#post13754274
or
http://forum.xda-developers.com/showthread.php?t=1035139
rain91x said:
Hi
I have same problem. I have Atrix 4G from UK Tmobile, with stock froyo. I flashed the stock 2.3.4 with RSD successfully, and i unl*cked the carrier.
Then i noticed, that Wifi don't work good. I don't know turn on: Wifi (error). The other problem, that the finger print scanner isnt work...
These actions do not help: factory reset, unlock BL, custom ROM (i tested Nottachtrix, any ICS ROM, stock froyo), erase all at fastboot, full wipe with CWM...
I am sure, that it is a software bug! (before flash 2.3.4 and carrier unlck, phone works fine...)
Some solutions? (I think, if we restore back to stock, the problem is solve) How can i make a fully reset, which is stronger than RSD flash stock sbf?
edit: http://forum.xda-developers.com/showthread.php?p=13754274#post13754274
or
http://forum.xda-developers.com/showthread.php?t=1035139
Click to expand...
Click to collapse
looks promising... did you try it?
I donnot if I can even try it... the first step is "close WiFi"... and I can't. it doesnt go off and doesnt go on... just stays on "Error".
should I just except the fact that I have to get a new phone?
should I send it to Motorola?
Alonleibo said:
looks promising... did you try it?
I donnot if I can even try it... the first step is "close WiFi"... and I can't. it doesnt go off and doesnt go on... just stays on "Error".
should I just except the fact that I have to get a new phone?
should I send it to Motorola?
Click to expand...
Click to collapse
I try it later, but i dont know now SD card. I hope, that it is a correctable bug.
edit: i tryd it, but still not good. Other solutions?
I have the same problem (wifi error, bt does not open). I guess it is a hardware problem but when I installed TopSmart rom (coming from Neutrino) they worked for 10 minutes then they crashed again. If it is a software problem (but i dont think so) there must be the answer that everyone's looking for. I hope it ends up as a software problem.
Sent from my Motorola Atrix 4G
It's most certainly a hardware problem. Clearly the WiFi chip in this phone just dies. This is also why your phone is crashing. You'll just have to leave WiFi off (if you can get to the switch before the phone crashes).
This issue started a couple months ago for me, and today I managed to accidentally flip the WiFi switch on again, sending my phone into an endless cycle of crashing and rebooting. I had to factory reset and re-flash CM10 about three times just to get it to stop rebooting repeatedly (which sucks because I didn't have a recent TiBu backup...). You might have to do this as well if your phone doesn't stop crashing.
I'd say just get a new phone. Don't send it in to Moto because even if you're in warranty they'll likely send you back a unit with a permanently locked bootloader, which isn't worth it.
It is frequent bug on Android phones. (wifi - error)
https://www.google.hu/#hl=hu&gs_nf=1&tok=EBl1OHx7E49rfa9s8zPj_A&cp=13&gs_id=1f&xhr=t&q=android+wifi+error&pf=p&output=search&sclient=psy-ab&oq=android+wifi+&gs_l=&pbx=1&bav=on.2,or.r_gc.r_pw.r_cp.r_qf.&fp=aee7b1a090091e6a&biw=1680&bih=949
MdX MaxX said:
It's most certainly a hardware problem. Clearly the WiFi chip in this phone just dies. This is also why your phone is crashing. You'll just have to leave WiFi off (if you can get to the switch before the phone crashes).
This issue started a couple months ago for me, and today I managed to accidentally flip the WiFi switch on again, sending my phone into an endless cycle of crashing and rebooting. I had to factory reset and re-flash CM10 about three times just to get it to stop rebooting repeatedly (which sucks because I didn't have a recent TiBu backup...). You might have to do this as well if your phone doesn't stop crashing.
I'd say just get a new phone. Don't send it in to Moto because even if you're in warranty they'll likely send you back a unit with a permanently locked bootloader, which isn't worth it.
Click to expand...
Click to collapse
I did turn it off... eventually.
but my phone still crashes... at the same frequency...
*added alogcat files of 2 of the crashes... if anybody can understand it...
My Evo just found itself a new vice. Every now and then it reboots. Only happens when it's locked, never when I'm using it.
So far I've tried reflashing it to stock, and tried a few different ROMs, with no effect.
I've also tried shaving a bit of plastic off the door by the power button, thinking that if the phone bends in my pocket a bit, it could push the power button. That didn't help, and wasn't even a very sound theory, since the phone reboots rather than just powering off.
Anyone got any ideas?
Thank you!
I had that happen on stock ROM, custom ROMs. However, it's not happening on CM10 at all. I didn't find a reason for it, but maybe it's Sense related?
i had the same problem with my evo 3d.. i tried everthing.. last thing i did was unroot and ran RUU and it went away.. after running the ruu i was still s-oss so all i had to do was flash a custom recovery and then a custom rom and i was good to go.. the reboots stopped :good: