Is this happening to anybody else? My phone reboots several times a day and I cant seem to pinpoint the cause of the problem. I have tried various kernels and versions of CM7 (running latest RC now). My phone is not overclocked and is not having any heat issues. Does anybody have any ideas on how to fix the problem?
I have not had a single reboot since I put 1.5.2 on my phone. I did not wipe coming from 1.4 but I didn't have any issues on that build either. Have you tried wiping data and cache yet and reinstalling?
Sent from my ADR6400L using XDA Premium App
You mentioned it isn't overclocked, but is it undervolted by your own modding at all? Other than that only thing I can think of are the reboots people were just experiencing in general (most likely due to the handoff between LTE and CDMA).
To answer the two previous comments. First, my phone is not undervolted. Second, I have erased everything and done a fresh install several times. Thirdly, I live in Richmond VA so I don't even have LTE enabled. I just enabled it yesterday and it seemed to decrease the number of reboots today. Yesterday I have about 4-6 while today I only had one. I think that all this began when I switched to the MR2 radio.
Is there a proper way to go from an earlier radio to the current or is it like flashing anything else?
Flashing the radio is pretty much just like anything else. Go into the bootloader and have the radio .zip on SD card named correctly and that's basically it.
You flash radios from hboot.
Pull battery, hold power and vol down
courtesy of my rooted bolt
Ya, that's how I've been flashing my radios. I just don't understand why the Mr2 and 2.5 radios would cause my phone to reboot.
Not too familiar with AOSP Roms, but have you tried the official OTA radio?
courtesy of my rooted bolt
Related
Why did VZW pull the MR2 update? I have it and my phone works with no reboots.
When did it get pulled?
g00s3y said:
When did it get pulled?
Click to expand...
Click to collapse
Oh, I thought it was pulled. My mistake.
they delayed it because the first RC didn't fix the reboot problem. That's what I've been told anyways.
Not all phones had reboot problems. Mine did and MR2 didn't help one bit. MR2.5 did fix my reboot problem and that's what I'm rocking now.
I haven't had any reboot problems unless I use the Freedom Pro keyboard (in SPP mode, of course). While using that I had two reboots in under 30 minutes though the reboot problem went away (and stayed away) as soon as I stopped using the external keyboard.
I had the reboot problem and flashed MR2. It's been extremely stable since. However, I am having some minor radio problems. It occasionally drops to 1X, or even no data (I live in a strong 3G area). However, the only real issue I've had with MR2 is that the market doesn't recognize my phone as compatible with all apps and won't let me install some of my purchased apps. Anyone else?
Will MR2.5 radio fix my data issues?
Anyone else experience the market problems? (My understanding the market issue is that MR2 is not an official VZW release and therefor not recognized by the Market)
I'm running stock, not rooted. Only mod is having flashed MR2.
So I have gotten a 3d 2 weeks ago as a replacement through asurion for my broken evo 4g and like most people on xda it is only natural to root it and slap on a rom the second you get your hands on it. I checked the hboot and to my hearts content it was 1.4, and easy as cake to root since I was coming from evo 4g. The dilemma is that I have tried several roms and everyone I have loaded would give me random reboots and eventually it would just keep rebooting as soon it loads to the home screen. Realizing maybe if I just loaded it back to stock it would help. The random reboots have cut down but I still get it and it's really frustrating. I have checked the battery and it is not loose, and at this point I don't know what to do. I realize that if I go to the sprint store I have to be able to show them the problem. I am also worried that they will update my hboot to 1.5 and claim that I didn't update system software and just send me on my way. Anyone experiencing the same symptoms as mine? Should I just bring it in to sprint to see if I can get a new one?
Thank you
Sent from my PG86100 using Tapatalk
They will update it I suggest you use a format all zip and flash a haus stock rooted ROM or run a ruu hour that works the got me that way updated my phone cause it was over heating
Sent from my PG86100 using Tapatalk
Without more information it would be hard to diagnose it without playing around with the device. It also sounds like it could be the kernel, or overclock settings causing instability because of the voltage either being too low, too high, or heat related. Do you have a custom kernel? If you are, is the device also being overclocked?
The first thing I would do is stop overclocking if you do have a custom kernel. If that doesn't fix it, change the kernel. Remember, some ROMs install their own kernel and you may not even be aware of that. While our devices run the same hardware design there are two possible differences between our device compared to another's. That would be flaws and differences caused by the manufacturing process, and different revision numbers. So while one device runs kernel A @ frequency B very well, another device may have problems and run kernel X @ Y frequency better.
So that could be the issue, and using those diagnostic steps you could easily determine that is the issue, or not.
Yeah I loaded the RUU on it and turned S-off back on. Just sucks because when it doesn't random reboot or bootloop it works great.
Sad Panda said:
Without more information it would be hard to diagnose it without playing around with the device. It also sounds like it could be the kernel, or overclock settings causing instability because of the voltage either being too low, too high, or heat related. Do you have a custom kernel? If you are, is the device also being overclocked?
The first thing I would do is stop overclocking if you do have a custom kernel. If that doesn't fix it, change the kernel. Remember, some ROMs install their own kernel and you may not even be aware of that. While our devices run the same hardware design there are two possible differences between our device compared to another's. That would be flaws and differences caused by the manufacturing process, and different revision numbers. So while one device runs kernel A @ frequency B very well, another device may have problems and run kernel X @ Y frequency better.
So that could be the issue, and using those diagnostic steps you could easily determine that is the issue, or not.
Click to expand...
Click to collapse
I am currently running everything stock, reverted back with RUU and turned back S-on, and it still does it, although less frequently. Before I reverted back to stock, I did use android revolutionary 1.1.1 and on boot up it would run unstable. I then applied his stock clock zip, and it seemed to allleviate the problem at first but would again random reboot. After decided to try InfectedRom which worked great but after a day it would just reboot and eventually just bootloop. Unlucky with both decided to try MIUI and ran great for a few days and kept it on the stock kernel, but again the issues have returned. I have properly wiped the phone each time before applying any ROMs and followed the directions with everyone of them. Before trying another new ROMs I would also battery pull each time it bootlooped to see if it was just a fluke, but it would always come back. I am interested in to see what revision it is, how would I check that?
Thanks again for all the advice!
Is your battery loose?
I thought I had this problem at first too but I just popped a business card behind the battery and Viola no random reboots
Sent from my PG86100 using xda premium
bakarus said:
I am currently running everything stock, reverted back with RUU and turned back S-on, and it still does it, although less frequently. Before I reverted back to stock, I did use android revolutionary 1.1.1 and on boot up it would run unstable. I then applied his stock clock zip, and it seemed to allleviate the problem at first but would again random reboot. After decided to try InfectedRom which worked great but after a day it would just reboot and eventually just bootloop. Unlucky with both decided to try MIUI and ran great for a few days and kept it on the stock kernel, but again the issues have returned. I have properly wiped the phone each time before applying any ROMs and followed the directions with everyone of them. Before trying another new ROMs I would also battery pull each time it bootlooped to see if it was just a fluke, but it would always come back. I am interested in to see what revision it is, how would I check that?
Thanks again for all the advice!
Click to expand...
Click to collapse
Not a problem at all, that is what the community is all about. Free exchange of information, open source advancement of the platform and technology. Everyone gives a little, and takes a little.
I know there is a dialer code that works to give you that information without the need to install any application, or the need for root access, but after lots of research I was unable to find which one would give that info. However, there is a very useful app that you might want to have anyway. It is called "elixir 2", available on the market for free. Once installed, information > click"processor" > more information > processor: (mine says: ....rev. 2 (v71))
Let us know what yours says [for curiosity sake] please
Quick note, if you replaced the phone through asurion and try to replace it doesn't sprint, don't they refer you back to asurion?
Sent from my PG86100 using xda premium
I would take it to see and request them not to update it they wont ask why not don't worry...
Sent from my PG86100 using XDA App
kpsingh said:
I would take it to see and request them not to update it they wont ask why not don't worry...
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
I requested then not to and they still did the update
Sent from my PG86100 using Tapatalk
So just an update, I finally decided to bring it in store today with it rooted and s-off. I was just so sick and tired of it randomly rebooting I just walked into the Sprint store. Technician brought it in, updated the hboot 1.5 =*(. I checked bootloader, and of course I see the locked in capital letters, but I am still s-off. Does that mean I can still load TWRP and root it? Or do I have to follow the HTC method to root it? Thanks for all the help guys!
If it still says s-off, i believe you are good! but that sounds odd, because otherwise we should all be able to update are hboot after rooting? If anyone knows about this...but anyway...
It was not the hboot upgrade but the firmware upgrade that you needed. You did not have to take it to sprint to do that, they have the firmware update without hboot flooting around the dev threads. 2.3.4 and above roms require the new firmware or you'll get the problems you had. No that you have the firmware a lot of the more cutting edge roms still get reboots with most advanced kernels, you have to watch your rom kernel combo, or stick with the stock kernel.
As for flashing, if you really are s-off still, then you can flash anything you want just like on the ol 4g Let us know. Lucky bastard, have fun
[edit] Found this a few threads down:
"I did what you did, had 1.40 and flashed the wrong update, got 1.50 LOCKED with S-off. You can still flash ROMs and Kernels with no issues. I just had to reload TWRP recovery. Then I flashed the 1.40 Bootloader and all was well.
You can grab 1.40 and flash from here: http://forum.xda-developers.com/show...eng+bootloader
***To others reading this...do not flash this, unless you are S-OFF with 1.50 hboot***
You do not need to UNLOCK using the htcdev method. Just flash the 1.40 hboot and you will be fine."
So reinstall twrp, flash 1.40, and have 1.40 s-off and flash the good way
Yep just flashed old hboot 1.3 and merrily rooted, so far so good running cleanrom 2.9 and taking sad panda's advice trying to figure out if it's app related. I am suspecting that it is groove ip running in the background. So far just installed cleanrom and added tapatalk and SwiftKey
Sent from my PG86100 using Tapatalk
Ive used CWM to install different roms over a couple months since I have gotten my GS2. Ive never had a problem with Bluetooth connecting and playing music at all. But I find that since I started running the latest ICS XXLPH roms its been an issue.
Or can switching many roms over a course of time damage the antenna? or hardware? Any suggestions?
I am going to revert back to my stock roms after I send this message. The only reason I am sending this before I try it is because nobody else really seems to be running in to this problem after searching the GS2 thread.
Ive tried a couple ICS roms and all cause my phone to randomly reboot when using BT paired with my stereo either on a call or streaming music.
When it reboots enough times it starts to corrupt the ROM/install. Because after a while it will start to just randomly freeze on its own forcing me to reset the phone.
Ive searched all over I havent pin pointed anyone having the exact problem as me so that is why I wonder if its possible to damage the BT device after multiple custom rom installs.
Thanks in advance.
Chakker3D said:
Ive used CWM to install different roms over a couple months since I have gotten my GS2. Ive never had a problem with Bluetooth connecting and playing music at all. But I find that since I started running the latest ICS XXLPH roms its been an issue.
Or can switching many roms over a course of time damage the antenna? or hardware? Any suggestions?
I am going to revert back to my stock roms after I send this message. The only reason I am sending this before I try it is because nobody else really seems to be running in to this problem after searching the GS2 thread.
Ive tried a couple ICS roms and all cause my phone to randomly reboot when using BT paired with my stereo either on a call or streaming music.
When it reboots enough times it starts to corrupt the ROM/install. Because after a while it will start to just randomly freeze on its own forcing me to reset the phone.
Ive searched all over I havent pin pointed anyone having the exact problem as me so that is why I wonder if its possible to damage the BT device after multiple custom rom installs.
Thanks in advance.
Click to expand...
Click to collapse
You are using a leak or *beta* rom which is far from stable
And no installing many roms can not damage any hardware
Sent from my GT-I9100 using xda premium
Thanks for your response.
I am just concerned because like I said, from what I can tell, nobody else is running in to this problem.
Ive tried /format system along with full data/cache wipes. I wiped dalvik cache.
Im waiting for my phone to fully charge to put stock rom back on so I can test this completely.
But a bit nervous, because I need my phones BT as I am on the road often.
Chakker3D said:
Thanks for your response.
I am just concerned because like I said, from what I can tell, nobody else is running in to this problem.
Ive tried /format system along with full data/cache wipes. I wiped dalvik cache.
Im waiting for my phone to fully charge to put stock rom back on so I can test this completely.
But a bit nervous, because I need my phones BT as I am on the road often.
Click to expand...
Click to collapse
Having a similar, if not identical issue on latest Westcrip ROM. Near as I can tell, seems to be related to memory management: while on BT, RAM space drops almost 200Mb. While changing songs, or surfing the tracklist/phonebook, it can cause the RAM to reach a critical level. This causes the OS to crash and the phone to reboot (my case a soft reboot from the animation only) in order to create space. I would chalk this up to inefficient memory management by a beta ICS rom. Look for this to be sorted out in the future with official releases and custom kernels/roms.
Thanks for your response.
Yeah when I installed resurrection, I also ran in to that problem. I had no idea how to diagnose it. But it makes sense, bottling up the ram to the brink of reboot.
Thats what initially was happening to me, soft boot, took a few seconds and was back in. But extended crashes seemed to cause corruption.
Yeah so the XXLPH seems to have an issue. Because I also tried foxhound and got the same result.
I just got back in from testing my BT on my car stereo using my stock rom of KG2 and it played for 20 minutes and i chatted for 19 without any problems.
So I am glad it wasnt anything seriosu. But only reason I was concerned is I found nobody else to have the problem and I felt a bit isolated
But im reading the official ICS rom is out in Europe so im sure we will see some new roms out in the next little while.
I "flashed" the stock ICS leak 3.11.605.22 and it worked awesome for like 2 weeks. Today I restarted the phone and it never came back on, it never booted up no matter what I did. I now have the replacement rezound and want ICS again, was this just a freak accident or did the RUU mess up?
Did you try a different battery? Id say the ruu had zero to do with it.
I certainly will not flash the leak on my phone. Its working too perfect to risk messing with uncertainties.
Personally, with all the reports of bad devices I would just wait a week or so to make sure your new phone doesn't have any issues before flashing anything.
I really wonder how many people blame the leak for bad phones. Seems like HTC had bad quality control when it came to the rezound. I feel lucky to have had no problems with my phone after reading all the reports of returns and heating issues.
I have had the ICS leaked RUU on my phone since the day it came out and have not had the first problem with it. The RUU didn't mess your phone up, a dead or faulty battery probably did.
It wasn't the battery, the Verizon rep tried a new one and he also tried both batterys in the new phone and they worked fine in the new phone.
The phone that messed up, I had for about 3 weeks or so with no problems. Then I used the RUU and it worked flawlessly for about 2 weeks, then BAM! now I have a brick.
since flashing the RUU i have radio issues galore. data just stops working. sometimes on wifi, sometimes on 3g, whatever.
tspderek said:
since flashing the RUU i have radio issues galore. data just stops working. sometimes on wifi, sometimes on 3g, whatever.
Click to expand...
Click to collapse
See I never had problems with the RUU itself. The radio worked tons better than it did before the RUU.
Now my new rezound won't read my sd card. I tried reformatting still doesn't read it.
For those of you who have flashed the RUU and are having problems, try flashing it a second time.
I paid particularly close attention during the flashing process and hand verified the versions of subsystem I could after the update. It turned out that the first flash only applied the hboot, kernel/boot, and a few minor systems successfully. After a second flash, everything applied correctly.
For instance, a number of people reported that the radio versions didn't change from the update, when in fact the radio changed significantly (currently running @ 1.22.10.0310r, 1.22.10.0308r).
After the update, I've found my battery life is significantly better than the GB kernels (I used BAMFs modified, Incredikernel and the Stock OTA). My reception is noticeably better, but I can't give a qualitative judgement other than that. And, most importantly, the phone is easily 100% more responsive. I used the stock OTA and BAMF 1.0.2 on and off for a while and unless I repeatedly killed background tasks my home screen (ADW Launcher EX) would stutter and lag, games would periodically slow down, web browsing would periodically freeze, etc. Now, my phone consistently has 300MB of RAM free (before it was usually less than 100MB). The leaked RUU is the best thing to have happened to the Rezound so far.
Note: despite my complaints above, my phone was always more usable than my OG Droid and my wife's dinc2, I'm just giving a comparative description.
Hi,
I have been having a having an issue with my Evo3D since I got this replacement phone and I am trying to figure out if it is the phone or the software/firmware.
Simply put,
when the phone's screen is off (asleep and locked), sometimes when I press the power key to wake it up and then swipe to unlock, about a second later, the screen goes black, then I get the HTC splash screen, ie it does a full reboot;
at other times, the phone will be in my hip case or in my pocket, I won't touch it or do anything to it and the thing will reset itself, I am fairly sure this occurs when it is scanning for a tower or when it is changing to/from roaming as this occurred mainly while I was in the middle of nowhere this past weekend; and
this can happen immediately after a phone call, or right after I turn off/on one of the wireless subsystems, but this is less common.
I am unlocked, I downgraded using the bricking method, I have used both Freeza's and TreVe's firmware packages, I have used the 2.17 stock RUU twice.
I have run Mik's 3.6 rom, D3rp's 3.6 rom, dropzeroc's ROM, MeanRom's ICS and gingerbread ROMs, and some others and I still get this problem. I have also tried multiple different batteries. I always superwipe between ROMs.
Because I have used so many different ROM's, I am fairly sure the issue is either firmware or hardware.
Anyone have any thoughts before I send this back to Sprint for 2nd replacement because I REALLY don't want to have to brickroot ANOTHER phone. Took me 8 f***ing hours to get this one done.
Thanks,
Osiris
My first suggestion would be flash a new radio.
If the radio and firmware doesn't get along that well, it can cause problems like the ones you're having.
Moonbloom said:
My first suggestion would be flash a new radio.
If the radio and firmware doesn't get along that well, it can cause problems like the ones you're having.
Click to expand...
Click to collapse
Which radio would you use if you want to run ICS Sense 3.6? I guess I am confused though, wouldn't the 2.17 radio jive with the 2.17 firmware (radio 1.06 should be fine with 2.17 firmware right?)
I had the same issue. My phone would randomly reboot on screen on or sometimes i would check it and would see it restarting.
I went back to full stock and still had the same issue.
Took it to sprint and they get me another replacement.
I suggest you take it back.
I am trying the radio suggestion but thank you for the suggestion and I will probably take that advice if it continues having issues.
Well, I am not sure what to say.
Like any BAD troubleshooter, I changed two factors at once.
I switched to PKMN and downgraded the radio to .97
Well, it hasn't reset itself since.
Who the hell knows why either thing would fix my issue.
Downgrading the radio to .97 (from the 2.08 ruu) when everything else is 2.17 ruu makes no sense.
Going to Sense 4.0 ROM makes even less sense as a fix.
Anyone have a clue?