So this is bizarre. I just rooted my uncle's Droid X. He was running the 2.2 stock ROM. The root seemed to go fine, but now he is having an issue with having to "double-click" items in settings in order to see them. I don't have the phone with me at the moment so I'm going with what he told me. He can still make calls and everything else is running fine I guess. Is anyone else aware of issues like these?
Related
I have installed several of the 2.1 roms out there. Each one that i install causes my phone to randomly restart. Is this a common issue with anyone else? As soon as I go back to 1.5, the restarting stops.
I am having the same issue on the stock 2.1. The only answer I have gotten from HTC is hard reset. But I have already done this twice. So I am going to root my phone and hopefully get rid of this problem. It only started after I updated to 2.1.
BigDiz007 said:
I have installed several of the 2.1 roms out there. Each one that i install causes my phone to randomly restart. Is this a common issue with anyone else? As soon as I go back to 1.5, the restarting stops.
Click to expand...
Click to collapse
Silly question perhaps, but are you completely wiping data and dalvik cache before flashing any of these 2.1 ROMs? Sometimes this happens if you don't do a full wipe before installing new ROMs.
I'm having the same issue, and I did a full wipe, installed several different roms and finally settled on aloysius
i've had the same problems with every 2.1 rom with the exception of darchdroid.
for me it usually happened after i placed a phone call and tried to hang up
and yes everything was wiped before flashing....
im having the same issue i knew i wasnt the only one, has anyone figured out why this is???
I am getting that error trying to install ZenEXP.
Same issue here, only mine's been doing it out of the box, as I got mine the day the EVO was released. I've rooted it and attempted to install several ROMs hoping to get rid of the issue, but had no luck so far. Never had the luxury of having 1.5, as mine came with 2.1, so I just thought it was the phone, honestly. Interesting to know the issue doesn't occur with 1.5...
Anybody got a copy of the stock 1.5 from original release? I'd like to give it a shot.
I do not have any issues that have been listed here. I am running fresh rom and everything is working great.Just wanted to make sure all views arebeing represented in this thread
hmmm....had a thought, did the phone get really hot when it happened....cause that is what happened when i was on fresh....
NomadHellfire said:
Same issue here, only mine's been doing it out of the box, as I got mine the day the EVO was released. I've rooted it and attempted to install several ROMs hoping to get rid of the issue, but had no luck so far. Never had the luxury of having 1.5, as mine came with 2.1, so I just thought it was the phone, honestly. Interesting to know the issue doesn't occur with 1.5...
Anybody got a copy of the stock 1.5 from original release? I'd like to give it a shot.
Click to expand...
Click to collapse
You won't be able to go back to the stock 1.5 original. That has been tried already by a bunch of developers here and it didn't work. You would probably be able to flash a 1.5 ROM (browse way back into the Development pages forum here), but since you had stock 2.1, there's no way for you to go back to stock 1.5.
For all the rest of you, not sure why you are getting random reboots, but as mentioned in the previous post, sometimes the Heros do that when they get overheated or overworked. It would be best to root and start with a very stable, non-overclocked ROM. A couple of the most stable and reliable stock-based ROMs here in this section are DamageControl 2.09.1 and nfinitefx45's Stock 2.27.651.6. I recommend you try either of those out if you haven't already -- hopefully that will fix/solve some of your troubles.
Please report back if any if you have success or more problems with these...we want to make sure you get the help you need
overheating is defiantly not whats causing my restarting. im not trying to thread hijack so ill provide a link to the thread i started about this same issue. in my thread i have attached bug reports (i think thats what they are) and now i have stopped receiving help just when i provided the info needed to see whats casuing this
http://forum.xda-developers.com/showthread.php?t=684727
Im not any good at code so i cant read the big reports well. but i believe its a hardware issue because there is a small presentage of people having these errors and i cant seam to get anyone to be able to reproduce this if it doesnt happen to them.
shawnwojcik said:
overheating is defiantly not whats causing my restarting. im not trying to thread hijack so ill provide a link to the thread i started about this same issue. in my thread i have attached bug reports (i think thats what they are) and now i have stopped receiving help just when i provided the info needed to see whats casuing this
http://forum.xda-developers.com/showthread.php?t=684727
Im not any good at code so i cant read the big reports well. but i believe its a hardware issue because there is a small presentage of people having these errors and i cant seam to get anyone to be able to reproduce this if it doesnt happen to them.
Click to expand...
Click to collapse
Sorry, I don't understand much of the code myself. And I think a handful of our devs here who understand all that coding have already moved on to the EVO. I read your other thread too but don't know what else to suggest. Wish I could help more. You could just be one of the unlucky few who got a bad, buggy phone right out of the box.
Have you thought about just calling Sprint customer service and asking for a replacement phone? Certainly with all the trouble you're having it may be worth it. I think even if you don't have the insurance plan, a replacement phone is only around $35.
@chromiumleaf, yeah sadly i think its time for a different phone.
Hey guys... Yesterday I upgraded the baseband to 2.15 from the original stock 1.0 I was running one of the CM nightly builds and also did the unrevoked forever root method to install it. After I did that I installed CM6 RC3 and later I realized I cannot hear out of the headset while making a call or receiving. So I then installed Skyraider and I still get the same thing. I can turn on speaker phone or connect to bluetooth and it works fine... but nothing through the handset.
Today I reverted to an old backup to see if that would help/work and still nothing. I guess my questions are can I fix this? Or do I have to downgrade to 1.0 baseband again and is that even possible?
Any help would be great, just a little annoying having to talk on speaker phone.
You have to revert to 1.0 radio. This happened to a few of us, it seems fairly isolated my replacement will be in tomorrow so I will know soon just how isolated.
I see.... well that sucks...
What did you say to get a replacement sent to you? Because obviously saying that I updated the baseband probably won't go over too smoothly.
My rooted MT4G started constantly locking up for no apparent reason a few days ago (although I have noticed it occurs a lot when downloading). Everything is fine, then the screen locks up, no buttons are responsive, and it never goes to sleep. Battery pull everytime.
It has happened with the Desire HD ROM, CyanogenMod 6.1, ICE Glacier... I have done wipes, re-installs, permission fixes and it keeps happening.
Not sure what to do... I am out of remorse period and didn't get the insurance. I hope my phone isn't totally borked.
Gonna do a complete restore and see what happens, but if that doesn't work is there something that I am missing? If this phone takes a dump on me, I am pretty much screwed... should have got the damn insurance.
Is anyone else experiencing this? Have you found the cause? Is there a fix?
I can say that rooting your phone via the steps outlined in this post, won't on their own, 'cause the phone to freeze up.
I'm running the stock ROM and the ONLY non-standard issue thing I've done to any of the 6 MT4G's in my possession, is root them via the post above. So I feel pretty confident that rooting your phone isn't the cause of the issue.
The different ROMs though, the processes in installing them etc. I cannot vouch for. Maybe someone else will be able to verify your steps, but I wanted to post my two cents and clarify root vs. everything else.
I've rooted 3 different times and none of them have caused lockups. My phone works fine.
But I can only speak for myself.
I've been searching for the last few days and have yet to really find anything to help me fix my problem.
the story:
Phone was rooted, back in Jan and I was running GummyJar 2.5, no problems, went to Apex V 1.3, no problems, but it ran a little slow. Today I decided to switch to something else to attempt and fix the speed problems, first I tried Incredibly Re Engineered v1.0, the phone ran well, but every 2-3 minutes it was rebooting me and sending me to the clockwork screen. So then I figured it had something to do with the ROM, so I went to Fission 2.5.7. Same problem, the phone runs great when it's on, but the constant restarted is unreal. I've done a factory reset, unrooted then rerooted the phone, then reinstalled the ROM, same problem.
Anyone ever have this issue and have a solution?
Thank you,
Eric
edit: Phone acts fine while plugged in to the computer or wall charger. Also made and attempt with SBF, to no avail.
Try an sbf....then go back to fission.
Just my thoughts. No overclock at first.
Running the SBF restore again...we will see what happens.
Hopefully someone else will stop by with thoughts.
Fission for me is real stable, ran it for long time now.
Worried it may be hardware problem....?
Might want to only install important apps at first also.
Try wiping data from Clockwork several times.
If that doesn't work you should definitely try SBFing and wiping data several times afterward.
Sent from my DROIDX using XDA App
I agree, I also loaded several ROM's and had a growing list of issues, SBF took care of everything for me.
Mine reboots when I pause video playback when connected with hdmi. But only since gingerbread, and I'm on my fourth version of gb. They have all done it so far, hoping official .596 will fix.
DX 2.3.3
Did the SBF'd it. Phone works flawlessly. I am now running Fission and Launcher 7, all without a hitch. Guess the phone just had to much going on and needed a fresh start.
Thank you all for the input. After I get a few more posts, I will post links and a DIY on how to do what I did. It was difficult for me to find anything with all of the steps and links in one spot, I want to make it easier for the next person experiencing this problem.
Yay! ....
Hey I been having the same problem with my droid x mines runnin stock 2.2.1 tho but it just keeps restarting and I don't know how to fix it lol. Im kinda new to this phone so does anybodyy have any suggestions?
Sent from my DROIDX using XDA App
CHip0,
SBF it...it's fairly easy and you can even find a youtube on how to do it....
http://www.youtube.com/watch?v=c58XaWnr6XE
Thank u very much! Lol
Sent from my DROIDX using XDA App
Ok I'm not a complete newb but I can't figure this out and its been driving me nuts for over a week now...
SGH-1337M (Rogers)
Up until last week I'd been running the nightly builds of CyanogenMod and loving it, the phone was fast had lots of functionality then I did a nightly upgrade and my phone stopped working. Incoming calls would ring but when I picked up the call I couldn't hear the caller and they couldn't hear me. After much frustration I ended up flashing back to stock. This fixed the problem but the phone was useless as far as I was concerned for everything but making phone calls. It was laggy, I couldn't listen to music (it was staticy) and just generally full of all of the extraneous crud that Rogers seemed to think I should have on my phone. (I honestly couldn't suggest the phone to anyone who was going to run it as a stock device if this was how it came out of the box!)
Now On Sunday I decided to try again and after setting everything back to defaults I reloaded Cyanogen and at first it seemed that things were working properly... until last night. Again I got a call and when I answered it there was no audio.
I can't figure it out, I'm running the correct radio now after flashing to stock (I337MVLUAMG1) but I just can't seem to get it to work and stay working. Besides Cyanogen I'm only running two other "root" apps Fantastic audio installer and AdAway.
Any suggestions would be great, I just can't go back to stock on this phone...
Any ideas?
I think I have the problem figured out...
Seems like it was a combination of a bad build of CM and the "Fantastic Audio Installer"
Beware of compatibility issues with apps like this...