Develop Bugs

[Q] Time for another "My EVO keeps mysteriously rebooting" thread!

You know em, you love em, random semi-reproducible problems!
I have been playing with my phone and enjoying the freedom of root access every since the original 2.2 OTA root method was posted (the downgrade unrevoked method). Its been great, but I started to have an annoying reboot issue that popped up every now and then. At first it was annoying, but now it is getting worse.
It SEEMS like it is temperature related. It started happening while the phone was charging, 4g was on, and wireless tethering (pre8) was running. First the connection between my computer and the phone would drop, then I'd reconnect, surf for another 5 mins or so, and the phone would reboot. Battery temp was reporting ~44C. After I let the phone cool down everything was fine.
I found that if I didn't have the phone on the charger or if I put the phone (battery side down) on top of a cool metal surface, the problem would not arise.
But then it started happening more often and under circumstances where it had previously not had any problems. Things like turning off my alarm, answering a call, playing alchemy. Under those cases, the battery was sometimes warm, but usually cool.
Last night it entered a reboot loop, where it just returned to the white HTC EVO screen over and over and over. It eventually turned off and the green light began to flash. I could not boot it up until I removed the battery and cooled both the phone and battery down. It was charging with a file downloading over 3g.
The problem is defiantly getting worse.
--------------------
I know that people are going to fire at me to wipe and reinstall (like in all the other threads) but that is the craziest part: I have. Many times. When it started to happen I thought it was the ROM, so I would change ROMS when it happened, but now I realize the problem is independent of the ROM in use.
I have used (and hit rebooting issues while the batter is hot and cold)
Stock (rooted) 2.1 and 2.2
Ava V5, V6, and V7
Fresh 3.2 (and a previous version, I don't recall which)
BakedSnack 1.6 and 1.7
Evo Zone 8.29
Vaelpak 1.3 and (I believe) 1.2
A couple of Virus' ROMs
I have used the stock 2.1, 2.2, and 3.2 HTC kernels and King's #s 6, 8, and 5, all with the same problems.
I even nandroided to backups that I had previously NOT had the issue with, only to immediately reboot. It really looks like software is not the issue, but I'm not sure.
As you may gather from this, it has been an on going issue for quite some time. I always do a full wipe (all caches, dalvik, et all) between ROMS. I'm out of ideas, do I need to S-ON and OTA then return this bad boy to sprint? Any ideas?
EDIT
Forgot to add, I am using ClockWork recovery, and flashing ROMs manually (through recovery, not a ROM manager app)

Quick bump for interest and posible solution. I'm pretty sure it's a hardware issue, but I just want to be sure.

Even though I'm always going on about how clockwork always works fine for me, and wipes everything correctly, I'll be the guy here to suggest trying to flash with amon ra a few times. If you still run into issues, I'd say that your battery is borked. But before returning the whole thing, maybe pick up a cheap extra battery off of ebay, and see how it works with that?

Just so I am clear on what to do, if I want to return the phone for service, I need to run the S-ON tool from unrevoked, then accept the OTA and I should be good to take it in, right?

Yes flash s-on then run RUU

i am having exactly the same issue
i've been on cm6 for over a month and it started about 2-3 weeks ago, at first i thought it was the temperature too but recently it started rebooting at completly random moments. I flashed baked snack yesterday and put a new battery in, same thing, random reboot
i flashed deoxed newest update with no mods today to see if that would fix the issue, 3 minutes after i did, i was signing in to my google account - reboot
turned the phone on, and 1 minute later reboot and loops....
any ideas?
using RA recovery btw, wiped everything before i flashed.

It's the HARDWARE
Guys,
Just thought I'd share a little of my experience with this phenomenon.
I had a HW003 Nova since the release of the Evo. I started experiencing random reboots every so often about a month or so later.
These progressed regardless of what version of Android, or which rom, or which kernel, bootloader, OTA update, S-ON, S-OFF, Bone stock or rooted.
After barely managing to get the phone back to it's factory state, I replaced it no questions asked on my second visit to Sprint repair center.
My refurbished replacement (Also HW003) was fine for a whole 5mins before it started doing the exact same thing. I gave it back to the technician, and put in the order for my second replacement. As per the advice of the technician, if my next replacement has any problems at all, I'm supposed to call Sprint customer service directly in hopes of a longstanding solution (read: Ask for a brand new phone)
Not trolling or starting ****, because I love my Evo, but let's be realistic.
These phones are built like garbage. At least the original crop of them is.
They use some good parts, but they are manufactured in a cheap manner.
Probably in cheap factories using cheap labor, and cheap materials.
While not every Evo is junk (my girlfriend hasn't had any problems with her's in over 3 months) you have to figure that one out of every few thousand is probably going to have some kind of defect, be it light leakage, bad screen grounding, broken USB connector, or even the infamous nonsensical, irrational, arbitrary reboot/power-cycle.

Sounds like what was happening to me too. I just took it to repair center and after a couple trips they replaced it. First they put a new battery in, said they couldn't reproduce the reboot but in three minutes I did. After that they ordered a new one.
In the beginning it was so random and appeared to be a heating issue too, then it just got worse and worse. Seemed like I could use the phone without issues if I wasn't taxing the phone too much but it progressively got worse and got to the point of it being maddening. Then it was hanging on splash screen and boot looping. Uprooted and took her in. Sounds like thats your best bet. I tried different ROMs, stock, etc etc.
Just take it in after doing what you need to do. Good luck.
SWYPED from my SUPASONIC

POLL: Have you ever had reboot problems?

Have you ever had intermittent reboot problems on your Incredible?
Did you do a warranty exchange or were you able to fix the problem?
This is regardless of what ROM you use, it could even happen when completely stock. If it is happening when completely stock and/or you were never able to fix the issue, it is most likely a hardware defect (failing/overheating 3G radio?). I'd like to see the prevalence of this problem and if it pertains to one version of the Incredible in particular.

I hesitate to vote "never", because CM was initially pretty shaky, but you asked regardless of ROM. The stock ROM was fine for me, and CM has been great since the RIL update.

Yes
Random reboots on multiple ROMs. Haven't been back to stock because from what I've read, the problem won't go away.
Unlike many others I've read about, my reboots are completely random and are just as likely to happen while idle as while doing heavy processing.
AMOLED screen, Build Number FRG83

CUViper said:
I hesitate to vote "never", because CM was initially pretty shaky, but you asked regardless of ROM. The stock ROM was fine for me, and CM has been great since the RIL update.
Click to expand...
Click to collapse
Yeah if yours was fixed after the RIL update and if the stock ROM was fine, you're definitely not having the hardware problem. In your case, it is just from CM.

Yes and No
My first DINC went back due to reboots which were based on overheating which was, in turn, based on a bad hardware radio (present in many first batch DINC's).
My current DINC has rebooted only a small handful of times, and always when the signal is super poor.
So my 2 cents is ... check you temperature ... if its high and you reboot RMA; if its low and you reboot, check your signal.

That must be what happened to me too. I pre-ordered the DINC and had an early AMOLED version obviously. I do agree that it was because of an overheating/faulty 3G radio, that's the best explanation I've come to so far.

My first Incredible was great for the first 6 months but then it got a spot on the screen that wouldn't register touch inputs anymore so I got a replacement. The replacement from the day one has had rebooting issues. It's happens when I use 3G. I think the phone is overheating and reboots. It doesn't happen very often when I'm on wifi though. The replacement was stock ROM.

Blacklight17 said:
My first Incredible was great for the first 6 months but then it got a spot on the screen that wouldn't register touch inputs anymore so I got a replacement. The replacement from the day one has had rebooting issues. It's happens when I use 3G. I think the phone is overheating and reboots. It doesn't happen very often when I'm on wifi though. The replacement was stock ROM.
Click to expand...
Click to collapse
I would get a replacement for that one as well. It is most likely the 3G overheating issue.
Here's my story:
I had an original AMOLED version back when they first came out, it was rock solid until whenever I made this thread. This was after rooting, custom ROMs, etc. The phone would reboot whenever it wanted to.
I asked for a replacement, and they gave me a refurbished AMOLED. This one was even worse, as soon as I took it out of the box (completely stock) it would start rebooting when I tried to turn it on.
Finally, I got another replacement, and so far I have been happy with it.
Of course, all 3 were AMOLED versions, they always give you a replacement of the version that you already own.

I had this problem for two months ... I tried everything. I changed ROMs, I changed kernels, i changed batteries, i *228, I performed a ruu... nothing worked.
I went from a 1 to 4 reboots a day to now none! I have no idea why. It actually stopped when I started using Athena but I think its just coincidence.
I've been reboot free a month.
Sent from my ADR6300

The reboots seem to be pretty random even when using completely stock incredibles. Without even a history of rooting it is possible to have a reboot issue. The problem is the phone/hardware itself and not user error.

[Q] Galaxy Nexus Dropping Data?

So normally I run my phone on Wifi because it saves battery when i'm on my university campus all day. So last night I headed off campus and so I turned off WiFi, and it didn't want to connect to data. Just sat there (with full service) but no data connectivity. So I rebooted the phone. still no connection, turned on airplane mode and then back off, now it worked but only for about 3 minutes I had 4G with blue sync and everything, then it dropped off. I went out into a rural area and I kept having full signal but no 3G. So I thought it was the rom. I was running AOKP b25 (Team Kang) so I just updated to Milestone 4. Everything was going well in initial setup of the phone, I had 4G signal, then halfway through setup the 4G dropped off. So I turned on Wifi and got everything setup. Turned off Wifi and it hooked to 4G almost immediately. Then about 3 minutes later, it dropped again. So at this point i'm really hoping it's not my phone and it's Verizon. I've never had a single issue before (i've had the phone since December) with data not connecting like this. It just started last night, which made me think it was Verizon and maybe it had to do with the Solar Flares or something? Has anyone had a similar issue and have any idea of what I might try?

Hi
I was just about to post the same thing. I'm experiencing the same, Data and service keeps dropping, I just got the phone Wednesday and since then It's been doing it. It's very frustrating, and I'm also on Verizon.
Someone else experiencing the same? Could Verizon be the responsible here and not the phone?

And if it helps, i'm located in Norman, OK

JGeZau said:
Hi
I was just about to post the same thing. I'm experiencing the same, Data and service keeps dropping, I just got the phone Wednesday and since then It's been doing it. It's very frustrating, and I'm also on Verizon.
Someone else experiencing the same? Could Verizon be the responsible here and not the phone?
Click to expand...
Click to collapse
It's the phone, there's numerous threads about it (the Verizon version.) There's an expected software fix supposedly coming out this month sometime to fix it, that's all we know.

If it's the phone and an update will fix it, then why is it still doing it with a custom ROM? Do the custom ROMs not have the fix in place? I was under the impression that most of the things Verizon releases OTA to fix issues dont' happen in custom ROMS.

zacelliott said:
And if it helps, i'm located in Norman, OK
Click to expand...
Click to collapse
Hey, we are 4hr away from each other. I'm in Rogers AR
spencer88 said:
It's the phone, there's numerous threads about it (the Verizon version.) There's an expected software fix supposedly coming out this month sometime to fix it, that's all we know.
Click to expand...
Click to collapse
Thank you I'll start digging up in some other threads

zacelliott said:
If it's the phone and an update will fix it, then why is it still doing it with a custom ROM? Do the custom ROMs not have the fix in place? I was under the impression that most of the things Verizon releases OTA to fix issues dont' happen in custom ROMS.
Click to expand...
Click to collapse
Samsung is going to hopefully release a radio update that fixes it, which isn't found in custom rom's because it hasn't been released outside of samsung yet.

It's kinda weird though that this JUST happened last night suddenly, the signal has been flawless since I bought it so that's why I thought it was Verizon because I guess I figured if it was the phone it would have been doing it all along and not stop working all of a sudden.

It's the phone and a software update won't fix it. I've tried every radio out there, none solved the issue. I got the phone swapped over a week ago, it is still stock, and the issue hasn't returned. Theres an ongoing thread over at rootz about this.
I can't post the link but it's there. many members are reporting that replacing the device solves the issue.

this was verizon. it happened to me, went away by itself.
that being said, ive had the best handoffs using the 4.0.4 and 4.0.3 radios. try one of those, or a hybrid package.

I went to the Verizon store and they gave me a new SIM Card. Now it works!

willstilson said:
It's the phone and a software update won't fix it. I've tried every radio out there, none solved the issue. I got the phone swapped over a week ago, it is still stock, and the issue hasn't returned. Theres an ongoing thread over at rootz about this.
I can't post the link but it's there. many members are reporting that replacing the device solves the issue.
Click to expand...
Click to collapse
First of all you don't know what you're talking about. It may be a hardware issue it may be a software issue. There is no way to tell at this point. You are trying leaked radios, good job that proves nothing. If Samsung is aware of the issue and working on a new radio you haven't tried it yet. Sit back and relax until the update comes out. Then we can go from there.

SirVilhelm said:
First of all you don't know what you're talking about. It may be a hardware issue it may be a software issue. There is no way to tell at this point. You are trying leaked radios, good job that proves nothing. If Samsung is aware of the issue and working on a new radio you haven't tried it yet. Sit back and relax until the update comes out. Then we can go from there.
Click to expand...
Click to collapse
Wow dude, no need to get insulting. I was merely sharing my experience with a frustrated OP. If you want to blindly believe that there can't be anything wrong with certain devices, until the manufacturer comes out and says it, then more power to you. You are the consumer that ever manufacturer loves. Myself and many others over at Rootzwiki have found success by having our devices replaced. When I tell you that it is night and day difference, it is not a lie.
I agree with you about the leaked radios. If they don't work then it proves nothing. They are leaked and probably not finished. The reason I mentioned them in the first place is because many people tend to suggest trying them to solve signal issues. I was explaining that I have tried them and it did not work. What worked was swapping the defective phone.

No Network Signal After Flash to 4.1 on Verizon Galaxy Nexus

I just updated to 4.1 and can't seem to get a network signal on any of the ROMs I have tried. Anyone else had this problem or found or know of a solution?
Thanks.

Rarazuh said:
I just updated to 4.1 and can't seem to get a network signal on any of the ROMs I have tried. Anyone else had this problem or found or know of a solution?
Thanks.
Click to expand...
Click to collapse
Was this an OTA uprade? If you did an manual upgrade, you should make a backup before going forward.

Are you sure you used the correct ROM? Cross-flashing between a Toro/Maguro/Toro+ will often have the phone but up but with the radios not working

did you check your apn?

I just bought this phone on Thursday and the bestbuy rep had the same problem on two different phones and had to call the Verizon help desk. She managed to get it working and of course my signal went in and out as soon as I left the parking lot. I went home and immediately rooted and flashed 4.1 and had the same issue. I was on the phone with tech support and they couldn't find the problem.
I then did a quick search online and found that this is a common issue. The problem is that when updating to 4.0.4 the galaxy nexus has a hard time with the 4g connection. It then drops to 3g and then it realizes 4g is available and switches back just to start this never ending cycle. This causes a signal to be held for seconds at a time before dropping completely until it switches to the other.
The temp fix is to disable LTE and run your phone on CDMA full time. This worked for me and I have constant signal everywhere. Eventually I know a patch will arrive so I'm content with 3g for the time being.
What puzzles me is how come this doesn't happen to everyone? Its a big enough issue that I found the solution within 3min of searching for a fix but not big enough for Verizon to be aware of.
Sent from my Galaxy Nexus using xda premium

mclaughlin47 said:
I just bought this phone on Thursday and the bestbuy rep had the same problem on two different phones and had to call the Verizon help desk. She managed to get it working and of course my signal went in and out as soon as I left the parking lot. I went home and immediately rooted and flashed 4.1 and had the same issue. I was on the phone with tech support and they couldn't find the problem.
I then did a quick search online and found that this is a common issue. The problem is that when updating to 4.0.4 the galaxy nexus has a hard time with the 4g connection. It then drops to 3g and then it realizes 4g is available and switches back just to start this never ending cycle. This causes a signal to be held for seconds at a time before dropping completely until it switches to the other.
The temp fix is to disable LTE and run your phone on CDMA full time. This worked for me and I have constant signal everywhere. Eventually I know a patch will arrive so I'm content with 3g for the time being.
What puzzles me is how come this doesn't happen to everyone? Its a big enough issue that I found the solution within 3min of searching for a fix but not big enough for Verizon to be aware of.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I have the same issue. it burns your battery as well by switching back and forth. I used to leave my nexus uncharged at night and the sleep mode would allow it to only lose a a few percentages but now if i leave 4g on with 50 percent battery.. Its almost alway dead when I wake up

Sad to say I have the same experience
The story told by mclaughlin47 is almost exactly what happened with me. Even rooted and running BAMF Paradigm 2.1, I still have the same problem. If anyone knows of a way to fix this, please let us know.
I can't believe Verizon isn't aware of this problem. I actually had better battery life and signal with my Thunderbolt running Vicious ROM. I may just be returning mine if I don't hear of a solution soon.
Thanks for any help, cause this is ridiculous!

I am rooted now, but even on stock ICS I was getting a problem where my radios just die. Requires a reboot to fix. But when I was seeing it, they always looked fine. You don't know they died until you try to use data or make a call.

Do you still have your imei
Sent from my SCH-I535 using Tapatalk 2

I saw the same issue with ics and jb roms. Tried several radios but always dropped data and voice when using 4g. From what I've been reading, it's a hardware defect.
Mine also works great and stays connected all the time when I leave it in cdma mode. Went back to my rezound since 3g mode there at least still let's me use data while talking on the phone. I like showering in as much radiation as I can

tbguy said:
I saw the same issue with ics and jb roms. Tried several radios but always dropped data and voice when using 4g. From what I've been reading, it's a hardware defect.
Mine also works great and stays connected all the time when I leave it in cdma mode. Went back to my rezound since 3g mode there at least still let's me use data while talking on the phone. I like showering in as much radiation as I can
Click to expand...
Click to collapse
Reflash the radio and the cdma radio. Samsung and Verizon Wireless both claim that hardware defects are not known issues.
Which hardware revision do you have? (looks on the label on the back should be 11.11, 11.12, or 12.0.)

i have 12.01
will try reflashing the latest radios

tbguy said:
i have 12.01
will try reflashing the latest radios
Click to expand...
Click to collapse
just to check back, did it work?

unknownzero said:
just to check back, did it work?
Click to expand...
Click to collapse
Have the same exact issue...just upgraded to a jelly bean Rom and my data drops completely and I barely have a signal, did a super wipe (radio-rom-Gnapps)...and went to my old rom of ICS and I still have the same problem...but for the most part I barely have any type of signal and calls are dropping, called Verizon and they told me something about a switch, and that there is no problem in ur area....I just called last night, I'm gonna call back today...wish there was a solution ...also tried that 3G switch I just read earlier and I still have a poor signal

Any updates? I'm having the same problem

Hi,
I'm having the same issue. I've had my Nexus for about a month now and have had nothing but horrible signal issues, while my old Droid 2 gets fantastic signal.
I'm using the latest Bugless Beast 4.1.1 with the latest radios that were released today.
People have mentioned it being a hardware defect. I'm assuming I should just go back to stock ICS and go into Verizon and exchange it for a different Nexus?

It may very well be a hardware problem, but my thought was a SIM card problem for the reason that rebooting often does not solve the problem for me. I have a passcode on my SIM card, so if my phone doesn't ask me to enter the code then I can assume it doesn't see the card. This often happens when I encounter the loss of data problem and reboot, and I usually have to remove the SIM card and fiddle with it a bit and put it back in and then it reconnects.
So I went to the Verizon store to try and swap my SIM card and they wouldn't give me a new card, saying that it's a known software issue that Samsung has already attempted to fix twice and they are working on another OTA update. I obviously made a ruckus about how I'm paying for service I can't access and I want a different device, blah, blah, blah. Basically he was incredibly unhelpful.
I've been on ICS AOKP and recently switched over the CM10 JB and that's when the problems started for me, but I switched because some type of battery issue (it lasted about 3 hours for a few days) caused my phone to reset itself and erase everything so it seemed like a good time to upgrade. So I may have unique hardware issues going on but according to vzw it is software-based. I'm not sure if this is something that can/will be addressed in a new nightly if that's the case.

PEOPLE, IT'S NOT A HARDWARE PROBLEM! IT'S SIMPLY A RADIO.IMG PROBLEM! A LOT OF PEOPLE WHO IS ON ICS, BUT FLASHED LATEST RADIO ARE SUFFERING FROM THIS!
What you can do is just flash to a older radio image. Not that hard. Will this stop the OTA? Probably, but you can either flash the latest version back or just manually flash it.
Have a good day.

I got mine the first week of Aug at Best Buy. The first one I got had all the problems described above. Radios dropping out and dropping every call I made. I returned it the next day, and the sales guy told me he was 100% sure it wasn't the phone. I asked him to exchange the phone and the card because I couldn't use a phone that couldn't make calls. He did the exchange, and the second phone was actually worse. Most of the time, I could not even make a call. So, the next day I took that one back. They gave me a third one that worked great for a week, then I started getting a no SIM card error message. The phone would reboot and work again for about 3 hours, then repeat error message. I took the card out, wiped down all the contacts with a soft cloth, and I have had no problems since. Great reception, no dropped calls. Great phone. I don't know if it is hardware or software, but I would keep returning the phone until you get one that works!
Once again, what is the point of having a phone that can't make calls.

T-Mobile Note3 randomly rebooting

So, I got my Note3 last week as soon as I heard CM11 nightlies were officially available. I spent zero time with the stock ROM.
Everything installed perfectly the first time. CM11 ran nearly perfectly, especially considering it's a nightly and there are no stable releases or RCs, yet, etc.
On Thursday I spent a full day at my desk at work. I noticed that my phone rebooted in my pocket. I figured "hey, it's a nightly...I've seen far worse"....then I noticed almost every 2 hours it seemed to reboot again, sometimes more frequently. It never rebooted in the middle of me using it...only while in my pocket.
So, I figured "hey, no big deal. Another nightly or two and this should be ironed out." So I restored my stock backup on Friday after work. All weekend long, no problems whatsoever. I figured it must have been something wonky in the nightly CM11.
Then on Monday, while sitting at my desk, it happened again...and again....and again. Same exact circumstances. I figured maybe I borked something so I got a restore-to-stock and flashed it via Odin.
Well, long story short this continues to be a problem whenever I spend any significant time at my desk at work. It doesn't happen anywhere else so far. It happens with any ROM I throw at it. I've Googled around and it appears that I'm far from the only person experiencing this problem however I don't experience froot-loops like a lot of people. Just semi-random reboots.
Now, I'm pretty convinced that a different (or new) modem would take care of this. I had the GS2 on Sprint and we had a problem we referred to as "LOS" (Loss Of Service) which typically required a reboot...even on my bone-stock phone...it seems to happen with the same randomness. One thing I do know about sitting at my desk, my phone is constantly switching back and forth between H, H+, LTE, DC and occasionally E...Edge being the only thing that gets solid service about 1 wobbly bar.
That's my own theory. This isn't a deal breaker for me. It only happens at work and if I wait a few seconds my phone is back in commission without any intervention.
Anyone else have a similar experience, tips, ideas, theories...? I'm more curious than anything.

Perhaps a Wi-Fi issue?

krelvinaz said:
Perhaps a Wi-Fi issue?
Click to expand...
Click to collapse
I keep wifi off at all times, wifi scanning set to off. I have unlimited data and my 4G speeds outclass my (relatively very good) cable modem speeds at home and at work (I live and work a stones throw from the NOC...I mean...literally, across the street from both places). I would prefer wifi if it wasn't sketchier than my cell connection.
So, it's not that.

How many files on your microSD card? Notice I asked how many, not how much space taken up. Android's media-scanner service seems to have huge stability issues once you cross the 10,000 files threshold. If that's your case, delete some files and see if it still reboots. I had about 10k files, deleted down to 6.5k and no more random reboots for me.

I have the same issue, and I don't have a micro SD card in the slot. The phone will randomly restart, usually after unlocking the phone. I have disabled wifi-scanning, auto app updates, and factory reset device, but nothing helps. It didn't do this before the kit kat update. It only happens maybe once a day or every other day. It's not terrible, just annoying at times. I'm thinking its a software bug.
Also, i'm running everything stock at the moment.

I have been on Cyanogenmod nightlies since I got the phone...and in the past week or two it does not reboot randomly with either Cyanogen or AOKP. At all. Still does with TW, I haven't taken the KK update so I don't know if that will help or hurt....and unless I absolutely am required to I won't be taking that update ever.

Maybe some kind of interference, that's kinda odd that it's happening only at your desk. And on stock.....
Sent from my SM-N900T using XDA Premium 4 mobile app