78 replies to this topic

[cmh714]

They are there. ???

Turbo Driven Comment

I believe these are hosted elsewhere Kaos. I was having some issues as well but not with drdevs.com

[livinginkaos]

No, I was talking about dhacker's which I assume they were talking about since that is the start of the thread

Turbo Driven Comment

[cmh714]

the nprevette version was having issues

[livinginkaos]

Ah

Turbo Driven Comment

[ibolski]

Lately, I've been having issues with the radio not turning back on after a reboot or upgrading to the latest version of CM12. A few reboots seems to cure it, or if I wait, it might return on its own in 5 minutes. Another fix is to go into airplane mode and then switch out of airplane mode.

 

Anyone else experiencing this? I never had an issue with the radios in the earlier releases, but I had read about others having an issue with it.

[Not_A_Dev]

Lately, I've been having issues with the radio not turning back on after a reboot or upgrading to the latest version of CM12. A few reboots seems to cure it, or if I wait, it might return on its own in 5 minutes. Another fix is to go into airplane mode and then switch out of airplane mode.

 

Anyone else experiencing this? I never had an issue with the radios in the earlier releases, but I had read about others having an issue with it.

 

Yes, I experience the same issue. It's hit or miss. Not a big deal for me, as I chalk it up to CM 12 still being an alpha version. I'm sure they'll get it sorted eventually.

[ibolski]

Has anyone gotten GPS to lock? I cannot for the life of me get it to work. I even flashed back to stock, made sure GPS got a lock, and then flashed CM12 and nothing.

 

CoPilot says it cannot find the GPS signal and Google Maps is WAY off (when I'm driving, it says I'm always pointing NW and I'm always driving in the grass off the left of the actual road I'm one or at least, so says Google Maps).

 

I'm on the latest build (12/02).

 

UPDATE: Well, I went back to stock, locked GPS via Google Maps (as I've done before), then clean flashed CM12 and all is well.

 

I'm wondering if all the dirty flashing of previous CM12 nightlies caused the issue? Wiping the modems would always result in my cellular radio never being able to connect (would always tell me I have no service) and then I'd have to flash back to stock to get my cellular data back.

 

UPDATE #2: So far, so good. Once thing I'm loving is the notifications on the lock screen. it's nice to be able to double tap the notification, enter my pin to unlock and it launches straight into the app.

 

You know, it's the little things that matter.

 

UPDATE #3: Uh oh. Bad problems that seem to have borked my VZW account and device ID.

 

As of 12/02, for some reason, my phone on the VZW website shows as being a non-VZW device. I called support and they said for some reason, my device ID was removed from my account. They filled out a form to re-instate my device ID so I have to wait 12 to 24 hours. We'll see if that fixes some issues I'm seeing.

I have not been able to keep CM12 on my phone since last night. I have been using it as my daily driver and I was running the 12/02 release from Kitstalk. But last night, I went to flash the latest version which seemed to go fine. When it booted up, I went through all the normal steps of activating it. When it got to the WiFi section, it hung and then rebooted. After that, the CM logo shows up, spins for about 30 seconds, freezes then reboots again and that's what happens from there on out.

 

I can only get into the desktop on the initial boot after flashing (clean - wiping data, system, cache, dalvik cache) but then it reboots (never can get done with the registering) and then the vicious boot-loop cycle.

I have to then either flash back to stock or I can flash CM11 and all is fine. So, I'm wondering if part of the issue is:

1. CM12 at some point wiped my device ID. Not sure how that happened, but right now VZW is saying my device is a non-VZW device and the device ID was wiped/removed on 12/02.
2. Because my device ID is gone, is that why CM12 for some reason cannot finish registering the device and goes into a vicious boot loop? But then why does it corrupt the install at that point that I have to flash back to CM11 or stock and can't get back to the beginning to start registering the device?
3. Even more curious, why does CM11 and stock work and why do they not bootloop? Is it because both are based off of the KK kernel and maybe that's part of it?

Again, I have been running CM12 since dhacker first released it last month without this issue, but on 12/02, that is when VZW says my device ID was wiped from my account. Again, not sure how this happened or why, but it seems to coincide with when I flashed the 12/02 image of CM12, so I'm wondering if that's it? Not sure why else it would have happened.

[ibolski]

Okay, CM12 might not have been the issue with wiping my device ID. Per tech support, when I powered on my phone as he was monitoring, he noticed the SIM was returning to Verizon a garbled device ID and the said whenever he sees this, it means a bad SIM.

 

So, I went to Verizon, got a new SIM and it reregistered my device correctly.

 

As for CM12, I clean flashed 11/28 first because that was the latest version that worked from a clean flash. I then flashed 12/04 on top of it and everything works fine. I haven't tried clean flashing the latest since I got my new SIM. I might try it just to see.

[Playb3yond]

I think the reason my Maxx HD is having issues is because I've unlocked the gsm radio for net10 (basically T-Mobile) and setup has crashed on all builds except for 11-28. I've tried twrp 2.8.1.0 & 2.8.2.0 and nothing has worked since. I get no WiFi networks at all during setup (which is where it usually crashes) and sometimes I get HSPA, sometimes I get the insert sim screen. I'll try BlissPop when I get home. When Cm12 was working for me, even the alpha was the best ROM I had. And being an app-a-holic, had very few issues with it. I can't wait for a more polished version though. I just hope some method of installation will be found because I'm stumped. I've done full wipes before installation, I don't see what I could be doing wrong

[XE_Nerd]

So far none of the recent builds of CM12 have been playing nice when I have my T-Mobile card in my phone. Locking up and rebooting. I throw in a Verizon sim card and the freezing and rebooting goes away.

[soocold]

To me that says it's a gsm problem

Sent from my Nexus 6 using Tapatalk

[steelystan]

I've been trying to flash the newest CM12 ROM (12/12) with no luck. I've updated CWM to 6.0.4.7 and am getting this error every time:

Please Login or Register to see this Hidden Content

I've flashed the latest PhilZ CWM. 

[ibolski]

I've been trying to flash the newest CM12 ROM (12/12) with no luck. I've updated CWM to 6.0.4.7 and am getting this error every time:

Please Login or Register to see this Hidden Content

I've flashed the latest PhilZ CWM. 

 

Did you ever upgrade your phone to the official Kit Kat OTA or are you still running the Jellybean bootloader? That message says you are still on JB.

[steelystan]

I never received any OTA updates. How would I get KK bootloader installed?

[RikRong]

I never received any OTA updates. How would I get KK bootloader installed?

Install the latest FXZ.

[steelystan]

Before I screw anything up this is what I'm running right  now (from About Phone):

 

CM Version: 11-20140721-NIGHTLY_moto_msm8960

Android Version: 4.4.4

 

Is it possible to have Android 4.4.4 on CM11 and still be running a JB bootloader?

[ibolski]

Before I screw anything up this is what I'm running right  now (from About Phone):

 

CM Version: 11-20140721-NIGHTLY_moto_msm8960

Android Version: 4.4.4

 

Is it possible to have Android 4.4.4 on CM11 and still be running a JB bootloader?

 

No, once on KK bootloader, you have to run ROMs built against the KK bootloader. But, those ROMs are the norm now.

 

Also, unless your bootloader is unlocked, you better go and search the other forums here on how to unlock the bootloader first or you won't be able to flash the ROM. If you haven't unlocked the bootloader, here is the post to help with that -> 

Please Login or Register to see this Hidden Content

 

The big tip off if a ROM is KK bootloader for CM is if it has moto_msm8960 in the file name. The older CM11 based on JB has JB in the filename I believe.

 

The msm8960 is a unified build in that it is built for all variants of the RAZR phone, RAZR M included I believe. But, the one you were trying to flash is specifically for KK bootloaders, hence the msm8960 in it's name.

 

Still, before you upgrade to KK, read the post I pointed to above on how to upgrade the correct way to unlock your bootloader if you haven't already. I'm not going to hash it out. Many of us have hashed it out hundreds of times. Just go to the link above and it will get you started.

[figure9]

No, once on KK bootloader, you have to run ROMs built against the KK bootloader. But, those ROMs are the norm now.

 

Also, unless your bootloader is unlocked, you better go and search the other forums here on how to unlock the bootloader first or you won't be able to flash the ROM. If you haven't unlocked the bootloader, here is the post to help with that -> 

Please Login or Register to see this Hidden Content

 

The big tip off if a ROM is KK bootloader for CM is if it has moto_msm8960 in the file name. The older CM11 based on JB has JB in the filename I believe.

 

The msm8960 is a unified build in that it is built for all variants of the RAZR phone, RAZR M included I believe. But, the one you were trying to flash is specifically for KK bootloaders, hence the msm8960 in it's name.

 

Still, before you upgrade to KK, read the post I pointed to above on how to upgrade the correct way to unlock your bootloader if you haven't already. I'm not going to hash it out. Many of us have hashed it out hundreds of times. Just go to the link above and it will get you started.

If I remember correctly, M10 was the first KKBL Snapshot for msm8960. M9 was skipped pending the unified build and KKBL nightlies didn't first appear until about mid-August. The only reason I remember that is because I was super excited to finally get the KK OTA, run it for a few months, watch my phone's performance deteriorate, and then made the decision to root/flash 

 

I also remember being highly annoyed because I kept getting boot loops, not realizing M8 was for the JBBL (noob lol), and I would have to revert to JB or wait for further development with Nightlies.

 

Anyway, given the ROM's date, it could be possible he's running KK on a JBBL with an msm8960 name... 

[dvgb131]

...Anyway, given the ROM's date, it could be possible he's running KK on a JBBL with an msm8960 name...

That last sentence hurts my head. :-(

[Playb3yond]

That last sentence hurts my head. :-(

Its KKBL only