Related
So I updated my DInc to CM7 and updated the kernel to the latest Incredikernal version.
Two days ago, I noticed that I had no 3G connection at all, but could still make phone calls/send SMS. I updated to the latest build (33 I think) and the issue still persists. What next?
Try goin to rc4 see ifit fixes wait to flash kernel cw just may hav not wiped properly
sent from dinc
I heard there were problems with RC4 and Build 33 so im still on build 32.
Just a quick update - I did a *228 after posting this question - thought it might have something to do with Verizon as they are updating my area to the 4G LTE and my wife's phone (DInc - unrooted) was having similar issues. Upon doing the *228 and waiting about 15 minutes, everything was back to working normally. Just a heads up if others are having similar issues.
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.
My wife and i got our GNex phones at the same time in April through the Amazon wireless store. Both of our phones had to be repalced by amazon within the 30 day window for 4g/3g/1x signal drop issue. 4g radio would just totally crap out, then would wipe out the 3g and then i would have a complete signal loss. Everything was fine after we got the replacement phones. My wifes phone is totally stock and has had zero issues. Mine is rooted running AOKP toro IMM761, Android 4.04. 4 days ago it started having the rampant 4g signal crash issue again. I've turned off the 4g radio for now, but according to NoSignalAlert, with just the 3g radio on i've had complete signal loss 7 times today. I'm in the same area as usual, my house and my office where i normally have 2+ bars of 4g. I'm thinking the radio has gone bad in this phone, like it did in both of our previous GNex phones, it just took this one 6 months to die. Now i have to deal with Verizon Wireless to get a replacement. They are wanting to make sure i'm on the most current build, baseband etc. Here are my questions.
1 - What is the most current stock ROM, radio, build etc. that i an put back on my phone to both a)make sure that a rooted app/baseband etc. is not all of a sudden causing this issue and b) i can talk to VZW and they won't know i've rooted the phone.
2 - Once i return the phone to a stock ROM, i assume that I will have to do an OTA to satisfy the VZW tech. If the phone does not need to be replaced, i.e. the OTA fixes it, will i still be able to root back to an AOKP ROM?
3 - Is there some other update i should try before going the "unrooted" route and trying to talk with Verizon?
Thanks for your help.
Chris
http://forum.xda-developers.com/showthread.php?t=1890585
Here are the VZW radios for the Gnex. Personally I would try flashing the new one [4.1.1 (JRO03O)] with a JB ROM. I was on AOKP for pretty much the entire life of my Gnex, 8 months, and never tried CM10. Flashed CM and besides the Nav bar, which I like better in AOKP, I have seen substantial improvements in performance, stability, and even better battery life. If you are determined to stay with AOKP I would still update to the JB version and try those "new" radios.
I started having the same problem a couple days ago when flashing a ROM went bad so I had to restore to an old (4+ mo. old) backup. From there I flashed factoryrom jb and then flashed the new radios today Cuz I just noticed the lack of signal. Still no bars anywhere. Any other thoughts? Do you think flashing a CM would fix it? If so, why?
Elvis_Marmaduke said:
I started having the same problem a couple days ago when flashing a ROM went bad so I had to restore to an old (4+ mo. old) backup. From there I flashed factoryrom jb and then flashed the new radios today Cuz I just noticed the lack of signal. Still no bars anywhere. Any other thoughts? Do you think flashing a CM would fix it? If so, why?
Click to expand...
Click to collapse
What is selected in settings-more-mobile network-network mode?
data enabled is checked, and network mode is LTE/CDMA
I was gonna try to find a fix today and if i can't find one, flash to complete stock, reroot/mod etc.
Elvis_Marmaduke said:
data enabled is checked, and network mode is LTE/CDMA
I was gonna try to find a fix today and if i can't find one, flash to complete stock, reroot/mod etc.
Click to expand...
Click to collapse
Well, your settings are good to go. Did you check the md5 sum of the radio file after you downloaded it? If you have root explorer hold down on the .zip file and choose properties to check the sum and make sure it matches.
hahaha i guess that's what I get for trying to download a radio on crappy mall WiFi... the MD5 was bad :-/ works good now! thanks!
---------- Post added at 11:42 PM ---------- Previous post was at 11:05 PM ----------
Hmm, it did this "need to restart SIM to work properly" crap, restarted and stopped working. Any thoughts? I'm installing franco kernel to see if that helps
Welp I ended up just flashing the factory image hahaha, will reinstall ROM and see how it goes. Everything seems to be working fine right now though
Glad it was something simple like that to get you back up and running.:good::highfive:
WiredPirate said:
http://forum.xda-developers.com/showthread.php?t=1890585
Here are the VZW radios for the Gnex. Personally I would try flashing the new one [4.1.1 (JRO03O)] with a JB ROM. I was on AOKP for pretty much the entire life of my Gnex, 8 months, and never tried CM10. Flashed CM and besides the Nav bar, which I like better in AOKP, I have seen substantial improvements in performance, stability, and even better battery life. If you are determined to stay with AOKP I would still update to the JB version and try those "new" radios.
Click to expand...
Click to collapse
I d/l the 4.1.1 radio and flashed it in clockwork, and though the flash said it completed successfully, i don't see a way to check the radio version. I don't see 4.1.1 JR03O listed anywhere in the About Phone information...Where should i be looking?
Further, my prboblem seems to have further degaded ...With the 4g radio on, i get random total shut down of the phone, as opposed to simple radio crashes. Just goes to off with black screen. I'm up to try anything. I assume i can easily locate one of these JB ROM's in the dev section?
TurbineTester said:
I d/l the 4.1.1 radio and flashed it in clockwork, and though the flash said it completed successfully, i don't see a way to check the radio version. I don't see 4.1.1 JR03O listed anywhere in the About Phone information...Where should i be looking?
Further, my prboblem seems to have further degaded ...With the 4g radio on, i get random total shut down of the phone, as opposed to simple radio crashes. Just goes to off with black screen. I'm up to try anything. I assume i can easily locate one of these JB ROM's in the dev section?
Click to expand...
Click to collapse
The baseband i think. Mine is I515.09 V.FF02 / I515.FG02.
I'm not all that knowledgable about the radios I just know my reception/data was poor on JB ROM with ICS radios. When I flashed the JB radio, my issues were fixed. I believe the ROM and radio versions should match, so if you flash JB radio I would flash JB ROM. All the info should be in the thread that is linked.
WiredPirate said:
The baseband i think. Mine is I515.09 V.FF02 / I515.FG02.
I'm not all that knowledgable about the radios I just know my reception/data was poor on JB ROM with ICS radios. When I flashed the JB radio, my issues were fixed. I believe the ROM and radio versions should match, so if you flash JB radio I would flash JB ROM. All the info should be in the thread that is linked.
Click to expand...
Click to collapse
I am such an idiot, this whole time you've been talking about JB ROMs i assumed you meant some particular brand of ROM, like AOKP or Myn etc... It didn't dawn on me until i saw JB next to ICS that you meant Jelly Bean ROM.
Ok i'm running an AOKP Jelly Bean ROM with Android 4.1.2
baseband is the same as yours
Build is aokp_toro-userdebug 4.1.2 JZo54K
The radio problem seems to be resolved. Thanks for the point in the right direction!
oops, accidentally wiped my sd card when i was restoring back to factory... TOTAL back to factory hahaha.... which isn't so bad i guess... after a year it's about time I guess
I seem to lose signal when leaving wifi though, have to either airplane mode or reboot. Because I had my phone so long, I don't know if there was connection or dust issues, so I did the classic NES/SNES/Sega Gen trick, took the sim card out, blew in there and all that. Seems to still be going ok.
Fyi.. i a simple restart doesnt disconnect u from the towers.. u need to turn off, pull battery, pull sim, and wait for 10 20 sec. That will disconnect u fully..
Sent from my Galaxy Nexus using Tapatalk 2
After fumbling around all day I discovered that i basically lost my IMEI and its been corrupted/ set to 0. I have the number from my battery, could someone point in the right direction from here?
Recently, my rooted phone ( I was on clockworkmod recovery and stock rom) became rather volatile and would randomly reboot and get stuck in a bootloop. This lasted about a day and then the phone stabilized on its own and eventually returned to normal. Once it returned, the cell service was spotty and 4G was gone, i only had the occasional E in the top right corner.
This progressively worsened into me having no cell service, however I did not have the circle with the line through it. I had full signal bars all while this was happening.
I decided to unroot my phone and return to stock everything , hoping this would solve the issue. Still nothing.
I did a factory wipe and still nothing. Very rarely ill be able to sneak a text message or two before everything stops working again.
Anyone encounter anything like this before? I'm considering just resetting my flash counter and running over to an AT&T store pretty soon
If you're on 4.3 try flashing this modem here through CWM or TWRP http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 I had the same problem when I updated to 4.3 and after I flashed the modem I got data 100% working
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Is there anybody out there that can help?
I've had a SGN for over two years and it seems like I have always had problems with it. I've been through mulitple SIMS, devices, ROMS, and various apps. Most recently, I had to get a new device. It took several steps of troubleshooting, but I finally rooted the phone. Got Rootchecker Pro and was able to confirm with no errors. For a while now, when I wipe, CWM skips over Android_Secure because it can't be found. About a month, after rooting the phone, I flashed the CRDroid (based on Cyanogenmod) ROM. It was then that I would get bootloops after checking on the Mobile Networks setting. It didn't always do it right away. When it didn't restart immediately, I wouldn't be able to make phone calls. Shortly after, I went through the Developer Options and updated to CM 10.2. The Mobile Network Bootloops stopped and I thought everything was great. But, there has been about three times that the phone will randomly restart and go into a bootloop at the CM splash screen. It's happened a couple times randomly and yesterday after taking about 45 pictures over a 45-minute span.
Luckily, I've been much better about making Nandroid backups and it hasn't been a big deal to restore. You can imagine, though that it is incredibly annoying and critical sometimes. I've been trying to rack my brain about what is consistent about the bootloops and can't figure it out.
It's a Toro with CM 10.2 on 4.3 Android. I flashed Golden Kernel and PA 4.0 GAPPS.
I would love to see what everybody thinks the problem could be. Thanks again.