A little background, I've run Alien 4 for a few months with no issues whatsoever. About three weeks ago, CM7 (the stable atrix build Ba2TF), and shortly after I Flashed Neutrino 2.1GT (1.3), with the patch and assorted addons.
Within the last 1-2 weeks, my internal speaker began going in and out. I flashed 2.2 EE last week, and still had the speaker issues. In that last week, I've also been virtually unable to connect to a PC in any capacity. It's worked at random a couple of times, but that's it.
I reverted back to CM7 attempting to fix the issues, and no luck (this was before the charging issues).
Yesterday, I flashed Faux's Unified CM7 024_r2, thinking maybe it was just wigging out on me. No luck there, so I reverted back to a stable (with the exception of the speaker issue) restore.
Now, my phone will not charge, except when the demon inside it wants too. I've done a factory restore, manually formatted everything but the SD card via CWM, and restored back to the supposed stable CM7 restore. I've tried Neutrino 2.1 & 2.2, CM7, and am currently downloading the MFBSR stock restore.
If it helps, I'm using Rom Racer's current recovery.
Any thoughts here? I'm still pretty new to all this. Could the overclock to 1.3 (Neutrino 2.1GT) have done some damage? My phone was in an otterbox defender. Is there anyway to tell that you guys can think of?
Dumbass me procrastinated on getting my usual Square Trade insurance, and they've now stopped insuring phones past 60 days of purchase. I've had this one since June.
Sorry for the long windedness. If I missed anything, please let me know.
From a powered off state, when I plug the phone in to the PC, it turns on. I'd think this would mean it's seeing something via the data cable, right?
Anyone?
Related
Hey guys could anyone help me out, I received a refurbished phone from Verizon 5 days ago and it keeps rebooting. I managed to root my phone using "BAMF GingerREMIX v2.0 Beta #6", Radio: 1.39.00.0430. The most I can use my phone is for about 10 min. unless I leave plugged into a charger. Can anyone help me out???
Are you sure your battery is any good?
Yeah my battery is good, i got a brand new one and its still acting up..
Change the radio to the mr2 radio. Seems the most stable of the gb radios. That might help
Sent from my thunderbolt
This happened to me as well as soon as the screen went off. Rebooted. If I kept playing with it it was fine.
Had to go back to Froyo roms because of it. Happened with MR2 and 2.5 radios.
Sometimes when I mess with the kernel settings a lot this will happen. Try flashing a new kernel or even the same one and see what happens.
Mine has started doing the same thing after receiving refurbished from VZW. My old one never rebooted with same setups. Something quirky going on with it. I can flash back to stock and stops. Its not the rom or kernel i'm using because i have tried all combinations that used to work flawless on old device.
Hi.
I am about to unroot and go back to otb stock. I am wondering if anyone knows for sure when the random reboots that I, and several others encounter, first started because I need to know whether to do the OTA after I go back to stock.
From my memory....... :
Wasn't there 2 OTA's?
And the random reboots started after installing the 2nd one?
So should I just install the first one.......orrrr......does it automatically only give one OTA direct to the 2nd one released?
Or should I not install any OTA's at all and patiently wait for Gingerbread........
Thanks!
We have MR1, MR2, and MR2.5 but I think only MR1 was an official OTA (dont quote me on it tho since I have been rooted since I got the phone and have never received an OTA). I think the reboot issue has been a problem for a lot of people for the entire time and isnt a new thing. IIRC MR1 caused quite a few reboot issues but not for everyone. I personally ran w/o any reboots until I got to 2.5 and even then I have only ever had 1. Its just what works best for you.
You will be waiting patiently for quite a while for official GB from what I have heard on the boards but you can always try out some of the GB ROMs that we have already.
Beastclaw said:
We have MR1, MR2, and MR2.5 but I think only MR1 was an official OTA (dont quote me on it tho since I have been rooted since I got the phone and have never received an OTA). I think the reboot issue has been a problem for a lot of people for the entire time and isnt a new thing. IIRC MR1 caused quite a few reboot issues but not for everyone. I personally ran w/o any reboots until I got to 2.5 and even then I have only ever had 1. Its just what works best for you.
You will be waiting patiently for quite a while for official GB from what I have heard on the boards but you can always try out some of the GB ROMs that we have already.
Click to expand...
Click to collapse
You are correct Beast there has only been one official OTA. My wife is not rooted but I am
Well I went back to stock because I was gonna try to go to Verizon today and swap it out.....
I find it funny this exactly what I was going to ask today myself. I'm also running bamf remix 1.8, have tried all the radios and even installed bamf 2.0 for GB with the Mr 2.0/2.5 radios. Still got reboots. Now I want to go back to stock and unroot so I can go back to the store and swap it
Just wonder if its worth it, maybe if they let me swap SD cards
I just un-rooted my phone about two days ago. After, I did the OTA update. I hadn't seen any problems until today. I live in a 4G area and work in a (up until Monday) 3G area. Since Monday they have been testing out a 4G tower. I have had 4G until this morning, I just figured that they were still testing it out and had switched it off. Well, about an hour ago I got my first Reboot. When the phone came back up I noticed that the 4G had just came back on. I'm pretty sure that's what triggered my reboot. So in short, as long as they keep the 4G going I don't have any issues.
Just curious is the update worth doing? And if i do it do i go ahead and install the GB bamf rom and radio? or just go back to my current 1.8 remix?
im curious what you guys have your phones overclocked at? I am rooted on the RC3 bamf 3.0 and the only time I have seen reboots is when i had my phone overclocked to high. now that im at 1.42 on the bamf cpu (I disabled my setCPU) and it has been solid.
I am a flashaholic. I flash any new rom on my fassy whenever a new one is released. I recently did TSM Res 2.0. I always flash by the book. I made many mistakes as a rookie and I try not to repeat oopsies. All was well and I found the rom to be stable and well put together. The next day I rebooted for an unrelated issue. After that, as the day progressed my data connection fizzled. By the next day I had lost it completely. I flashed back to stock and nothing. Then Superclean, CM7 and still nothing. Called Verizon and got a replacement. My last day with the phone, day 4, my ability to call also went. I called Verizon. I did an activation and had it authenticated. Rebooted phone and ta-da. All was well.
So WTF? Any ideas folks?
I kept the replacement anyways.
Sent from my SCH-I500 using XDA App
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 had a stock EVO 4G LTE running ICS, I upgraded OTA to Jellybean....had problems with the proximity sensor after the upgrade, so I put CM10 stable on it - and that worked fine for a month. Worked very well actually!
For curious reasons, I wanted to go back to the stock ROM and see if I was just imaging the issues (which Im not, others have reported), so I downloaded the "RUU_JEWEL_CL_JB_45_S_Sprint_WWE_3.15.651.16_Radio_1.12.11.1119_NV_2.87_003_25007_release_299302_signed"
I relocked the bootloader and installed the RUU. Installed fine. However, the phone was SUPER slow. The camera had problems too...but for example, Id make a call and it would ring and call time start, but 10 seconds later the phone would vibrate indicating the call went thru, even though I was a good 4-5 rings in.
So I went back to CM10 - the same exact version I went to before. It was still on my SD Card. Totally unstable. Freezing, rebooting, screen goes blank for no reason...just all sorts of weird problems. Would freeze and reboot during a call, but the caller would still be on the line!
I reflashed the ROM like 5 times, ever time clearing cache, davlik, factory reset, and system. Still completely goofy.
I read there was a problem with the 3.15 RUU, so I followed these directions here.
http://forum.xda-developers.com/showthread.php?t=2097150
But that still didnt help.
Right now Im back on the STock JB ROM. At least I can take phone calls with it, but I'd like to return to CM10.
Any suggestions would be VERY apprecaited!
Thanks.
More things I am noticing:
The Flashlight app doesnt work anymore
Camera doesnt work then causes the whole phone to become unresponsive.
Bump!
Can anybody help me out? Im dying over here without a phone that works.
the phone app keeps crashing. If i reboot, things work ok UNTIL I make a phone call....then nothing works.
Very strange!
I would try wiping 3 times
Sent from my EVO using Tapatalk 2
---------- Post added at 09:44 AM ---------- Previous post was at 09:35 AM ----------
Also are you restoring things from the titanium backup?
Sent from my EVO using Tapatalk 2
MerkoPCS said:
I had a stock EVO 4G LTE running ICS, I upgraded OTA to Jellybean....had problems with the proximity sensor after the upgrade, so I put CM10 stable on it - and that worked fine for a month. Worked very well actually!
For curious reasons, I wanted to go back to the stock ROM and see if I was just imaging the issues (which Im not, others have reported), so I downloaded the "RUU_JEWEL_CL_JB_45_S_Sprint_WWE_3.15.651.16_Radio_1.12.11.1119_NV_2.87_003_25007_release_299302_signed"
I relocked the bootloader and installed the RUU. Installed fine. However, the phone was SUPER slow. The camera had problems too...but for example, Id make a call and it would ring and call time start, but 10 seconds later the phone would vibrate indicating the call went thru, even though I was a good 4-5 rings in.
So I went back to CM10 - the same exact version I went to before. It was still on my SD Card. Totally unstable. Freezing, rebooting, screen goes blank for no reason...just all sorts of weird problems. Would freeze and reboot during a call, but the caller would still be on the line!
I reflashed the ROM like 5 times, ever time clearing cache, davlik, factory reset, and system. Still completely goofy.
I read there was a problem with the 3.15 RUU, so I followed these directions here.
http://forum.xda-developers.com/showthread.php?t=2097150
But that still didnt help.
Right now Im back on the STock JB ROM. At least I can take phone calls with it, but I'd like to return to CM10.
Any suggestions would be VERY apprecaited!
Thanks.
Click to expand...
Click to collapse
i say you should flash MEANBEAN, its a stable JB rom and some of the bugs like the proximity sensor have been fixed thanks to the devs here at XDA. its running very smooth for me. the only issue for me is that google's navigation doesnt work, but telenav works just fine. just wipe your phone about 3 or 4 times (i always do that to ensure i get a clean install on any rom). good luck!
I would re-download CM10 and verify checksum since you didn't mention that.
Sent from my EVO using xda app-developers app
Thanks for the replies.
Really all I want to do at this time is go back to stock, which I currently am on.
But even on the stock 3.15 ROM, it is very very unstable. The phone is majorly delayed. I get 1 ring on incoming calls before it goes to voicemail - but the person calling hears the normal 5-6.
For CM10, I used the same zip file (stayed on my SD card) that I used without problem for almost a month.
I took the phone to sprint (back to stock) and they couldnt figure it out. Getting a replacement tomorrow.
Could I just have a coincidental hardware problem? Seems odd if that is the case, the phone was working perfectly until I went back to stock using the 3.15 RUU
I got my replacement phone last night, did an OTA upgrade to JB in the store and the proximity sensor didnt work...
was about to tell the rep to just order me a GS3, but I said hold off....I really prefer the 4GLTE over the S3
Went home and flashed Meanbean......WOW!
Just like stock, and the prox sensor works!
so my plan is to just keep this ROM until HTC fixes the issue in their next maintenance release.
in TWRP, i made a backup and selected all the options Is this sufficient to get me back to stock, then do an OTA upgrade for the maintenance release, if and when it comes out?