Hey all, having a very odd issue here. I flashed Flinny's 4.2.1 AOSP rom a few days ago, worked absolutely perfectly, today when I turned the radio to use 2g for an app I was testing then rebooted it just bootloops constantly. I have tried wiping/flashing the same rom again, a build of CM10 and another rom in the forum (a sense build), same issue on all, it boots to the welcome screen on AOSP and CM10, and to the home screen on the other rom, then just reboots. I flashed AOSP again without gaps and managed to get to the home screen, I enabled aeroplane mode and it is absolutely fine (as in it doesnt reboot), then if I enable a data connection it just reboots as it had been doing.
Anyone else experienced this as I cant really pin it down to be anything other than a radio issue, even though I have not changed radio image.
This is the link for the logcat, initiated when I disabled aeroplane mode to when the device reboots. http://pastebin.com/R6SpZwWz
Any help very much appreciated.
Cheers
Related
Well, this sucks. Upgraded from the Hero to the Desire Z 1.5 weeks ago. Downgraded it, rooted it, tried out a few ROMs, settled on Virtuous Unity and all was happy.
I used the phone in the car this morning as a GPS, 3G data connection was working fine, etc. I had a couple of client meetings, after which I pulled out my phone to check for messages. I noticed there was no mobile signal at all. I figured it was building interference, so I went outside. Still nothing. Wifi was working fine, GPS was working fine. I enabled airplane mode, then disabled it again to see if that would kickstart things. Still no go.
I decided then to power cycle the phone to see if that would help. It went through the usual reboot cycle, displayed the lock screen, then the SIM unlock screen. Then no matter what I do or don't do, about 5 or 6 seconds later, the screen suddenly goes black and the phone reboots.
Now it just does the same thing over and over again. The phone boots up fine, displays the lock screen briefly, then the SIM unlock screen, then it crashes and reboots. Whether I unlock the SIM or not doesn't matter. Within 5 or 6 seconds, the phone will reboot. I can see notification icons popping up, so everything appears to be working fine otherwise.
I have not changed anything on the phone this morning: it was sitting in my pocket the entire time. Same ROM, same radio firmware. I restored last night's nandroid backup just in case, but it didn't help. I thought perhaps it was VU's built-in overclocking that wasn't agreeing with the phone, so I restored a MIUI-based backup. No go. I went all the way back to the stock (but rooted) Bell Desire Z image I took when I first got the phone. Still no go.
I've tried booting up without the SIM card, and without the SD card. Nothing works. I'm guessing the phone suddenly developed a hardware problem. It would be something that is triggered soon after the OS has successfully loaded. Maybe something to do with the 3G radio?
There are no obvious errors or kernel panic messages in logcat. Everything appears to be proceeding normally, until it just comes to a dead stop. Anyone have other suggestions I can try?
Search this forum for "boot loop" and you'll find some things to try.
Thanks, burtcom, but none of the threads I checked apply here. Other boot loop problems more often have to do with the phone rebooting while the boot animation is still playing. My phone successfully boots and is in the process of loading user apps when it crashes. Also, most reports come as a result of something attempting to root their phone and then installing a ROM. I've already made it past that stage. I am able to boot into CWM, do my nandroid backups and restores, etc. The ROMs have all been working fine up until some point this morning. The fact that several different ROMs now all have the same problem makes me suspect a hardware issue.
Moved my SIM and SD card back over to my Hero, and everything works fine there, so I strongly suspect some hardware just broke on the DZ this morning. I'll try flashing a new radio firmware, but I can't see how that would fix anything, since the old version was working just fine all along.
taob;15238893I'll try flashing a new radio firmware said:
Huh... so I flashed the latest Bell Canada 26.06.02.25_m2 radio.img, (up from my old 26.03.02.18_m3 firmware), and now the phone no longer crashes. I'm thinking maybe it isn't an issue with old vs new firmware, but that the old firmware was somehow corrupted during the course of the day. Re-flashing the original radio probably would have worked too, but now I have the latest one...
Hopefully this will help someone in the future with the same problem.
Click to expand...
Click to collapse
The phone no longer reboots, but I still had the problem of not picking up any signal whatsoever (voice or data), even though wifi and GPS work just fine. APN settings were verified to be correct. It turns out I had to go into Settings -> Wireless & networks -> Mobile networks -> Network operators -> Search network and manually re-register my phone on TELUS. Bizarre.
I had the same problem, update your radio and flash this zip on the Unity Thread
"For people experiencing random phone Freezes, this is due to overclocking, it's solved by lowering max speed.
Just flash this patch over: (link is on the thread)"
That's a different kind of problem, sengalang. My phone was working just fine overclocked to 1.2 GHz for over a weeks, so why would it suddenly start crashing like this? Problems due to overclocking tend to result in reboots at random times, and not at 100% predictable times like my problem. I did also boot with the MIUI and stock DZ ROMs, which do not overclock... same problem. Thus the root cause was not CPU speed.
I have massive problems using WiFi.
If I activate it, the phone spontanously "crashes", means it reacts extremely slow and is totally unusable till restarted.
It's always when WiFi is on, just the time till it starts differs. I've tried some different ROMs (MIUI with LordMods kernel or stock kernel with vanilla ROM-settings and no apps, CM7.1 stable with stock kernel) and also different WiFis and settings and can say it's independent from an established connection, so it also occurs when there is nothing in sight to connect to.
I can't remember since when I got this problem as I only recently activated WiFi again for usage. Before I never had such problems. I accidentally flashed a zip file as a radio some time ago o) and then flashed the right radio again after I got the battery out for some time. Possible the phone got damaged somehow or is there a possibility that it's a software related issue like a module that doesn't work well with more recent radios in combination with my phone?
I tried radios 12.59.60.26_26.11.04.21_M and 12.62.60.27_26.13.04.19_M, same problem.
Thanks
See if the official software works, try to install a 1.32 RUU.
Good Afternoon,
I flashed my phone with a bunch of stuff a few weeks ago, and it's been running spectacularly, but the past few days, I've been having some issues getting my phone to boot completely. ADW would keep force closing, and my phone would randomly reboot, and I'd sometimes need to battery-pull to restart it from being frozen completely. Also, my volume buttons no longer work, and the screen occasionally goes 4-split screen from the keyboard opening ( I'm assuming flex ribbon ). Now today, after the the splash screen, the phone screen just goes black and stays like that. From reading around, I think I know what the problem is, but I was wondering if anyone more knowledgable could give some insight as well, specifically, if there's any chance it could be a software issue and **crosses fingers** not a hardware issue. I attached what I could get of the adb logcat.
Also, if it helps, here's some info about my phone:
Rooted & S-Off, with newest radio
Rom: nickmcminn60's XM-8 Vr 1.1
Kernel: Miguel's
Mods: darktremor A2SD & ?Firerat's? Custom MTD Partition
Any help or advice would be much appreciated.
1) don't use Miguel's kernel with these latest builds.
2) did you fix permission with rom manager to help with fc's.
3) I don't think this will fix the screen issues, that's is mostly hardware related.
Sent from my fingertips using Android.
Thanks for the help! I hadn't done fix permissions yet, as last time it somehow broke my rom. Unfortunately, I tried doing a nandroid backup first, yesterday morning before trying fixing permissions, and after my phone finished and rebooted, the phone just froze, and I couldn't reboot into recovery ( my volume buttons don't work ), and after a few reboot attempts, my screen died. I'm going to try ADBing into it tonight if I can.
In case I can get it fixed though, what kernels should I be using instead? I tried drowningchild's, but I seemed to have fewer issues with Miguel's.
Use stock cm kernel when using cm roms if using sense I believe nbetcher has a good kernel
Sent from my fingertips using Android.
I have the Verizon Galaxy Nexus running on CM10; and just this morning my phone began to randomly reboot. I had been running this configuration stably for the past month or two.
The random reboots manifest themselves as a frozen/locked screen for a few seconds before the phone reboots. It looks to be a hard reboot, since it does go back to the Google screen. I have found that using my phone heavily (e.g. gaming) seems to slow the frequency of these reboots(if not stop them completely). At worst; they appear to happen every couple of minutes.
Coincident with the random reboots, my phone appears to have lost all cell network connectivity - it does not even report a signal strength anymore. No phone calls, nothing.
So far, I have tried re-flashing CM10 with ROMManager; fixing permissions, and uninstalling some apps. I don't know enough on where to look to fix the issue, and any help would be appreciated.
you try to flash a custom kernel?
k786 said:
you try to flash a custom kernel?
Click to expand...
Click to collapse
No. I haven't done any major tinkering lately. Never even tried a custom kernel.
FWIW, when I get to the screen with the Android on its back (on the way into recovery mode), it says that my CDMA baseband version is Unknown. Is that normal? Realted maybe?
What radio are you using? Check to make sure it's the latest, I don't know the Toro radios but if it's the same as Toroplus its FH05.
[I posted this yesterday in the wrong forum, and with fewer than 10 posts I can't post this in the developer forum. Sorry if this is the wrong place, again, but I need help.]
I have rooted my Inc 2 and was using CM 7.2 for a time; everything worked. Recently I installed a new ROM, Evervolv. I first installed the 2012.12.13 release, which didn't work well, then two nightlies: 2013.07.01, then 2013.07.03. Everything has worked on the nightlies except for a weird WiFi error. When I scrub the phone and install the Evervolv zip file, along with gapps, then reboot into Evervolv, WiFi starts right up and works normally. I can download files, sync my accounts, no problems. Then I turn off WiFi, either through the widget or through the slider in system settings, and it shuts off permanently. There is no way to turn WiFi on again. Pressing the widget makes it light up for a few seconds then go dark, and the WiFi "wedge" never appears in the top bar. Alternatively, through system settings, I will slide the WiFi bar to On, the message will appear that WiFi is turning On, but then the slider goes to Off and WiFi does not turn on.
I love this ROM and don't want to get rid of it. Can anyone suggest what the problem is? Thank you!
Kernel version
3.0.84-evervolv
Mod version
ev_vivow-eng 4.2.2 JDQ39E
----Update---
Someone on the developer forum experienced the same thing and just posted a solution: an alternate kernel http://forum.xda-developers.com/showthread.php?t=2044824&page=93
Wifi now works as it should.