Any of the CM 12.1 nightlies after 7/21 render my device unable to recognize the SIM card--I know it is the nightly because when I roll back to 7/21 the SIM card returns to functioning. Does anyone else have this issue? Is it/can it be addressed?
Have you tried to flash the "radio" files with mfastboot?
Sent from my XT1039 using XDA Free mobile app
johan111 said:
Have you tried to flash the "radio" files with mfastboot?
Sent from my XT1039 using XDA Free mobile app
Click to expand...
Click to collapse
Oh my, forgot to update my thread! Shortly after posting this, I discovered this thread on the CM forums: http-colon-slash-slash-forum.cyanogenmod.org/topic/112969-no-sim-card-xt1039-nightly-20150723-and-20150724/. (new user, can't post links yet lol) Newer versions of CM 12.1 require you to update the radio firmware along with the bootloader. this fixed the problem exactly!
Related
Guys be careful when trying the new nightly, I cannot revert back to stock, won't let me fastboot flash any firmware.. Now I'm stuck on Cyanogenmod
Sent from my Moto G using XDA Free mobile app
Clarkiieh said:
Guys be careful when trying the new nightly, I cannot revert back to stock, won't let me fastboot flash any firmware.. Now I'm stuck on Cyanogenmod
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
I think you cant revert to lower android versions right now because of changed partitions oder something like that... im not sure whats the problem! restore with cwm should help but it's a temporal fix
fl4m3y said:
I think you cant revert to lower android versions right now because of changed partitions oder something like that... im not sure whats the problem! restore with cwm should help but it's a temporal fix
Click to expand...
Click to collapse
Eh? I've just tried flashing SlimKat 4.2.2 to see if I can flash over with stock but when it boots I get encryption unsuccessful?
Sent from my Moto G using XDA Free mobile app
Clarkiieh said:
Eh? I've just tried flashing SlimKat 4.2.2 to see if I can flash over with stock but when it boots I get encryption unsuccessful?
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
Oh my mistake then... i thought you came from android 4.4.4 and some (including me) have problems with reverting back to lower android firmwares
sorry buddy
fl4m3y said:
Oh my mistake then... i thought you came from android 4.4.4 and some (including me) have problems with reverting back to lower android firmwares
sorry buddy
Click to expand...
Click to collapse
Yes your still correct, I was on Moto GPE 4.4.4
Downloaded and flashed CM11 4.4.4
Now I'm stuck on CM11 no other ROMs work in get encryption unsuccessful and when I try flash stock I get endless errors
Sent from my Moto G using XDA Free mobile app
I ported CWM using CWM for GPE and CWM Touch for Motorola Edition images.
How to install:
Connect Moto G with GPE firmware to computer in bootloader mode, open CMD or Terminal (for Linux and Mac OS X), choose file location as current folder and paste this:
Code:
fastboot flash recovery CWM_GPE_touch_falcon.img
Bugs:
On Lollipop have some screen freezes, but touch and all features work fine.
Download:
See attachments
So basically this recovery supports lollipop gpe??
I mean no graphical glitches??
Sent from my XT1032 using XDA Free mobile app
Flashhhh said:
So basically this recovery supports lollipop gpe??
I mean no graphical glitches??
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, it is fully functioning, only graphic bugs in the form of floating strip on the screen.
kromuch said:
Yes, it is fully functioning, only graphic bugs in the form of floating strip on the screen.
Click to expand...
Click to collapse
So i can now flash other roms including cm12 which were not working previously??
Sent from my XT1032 using XDA Free mobile app
Flashhhh said:
So i can now flash other roms including cm12 which were not working previously??
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
I used this recovery with CM 12 earlier and currently I use it with official GPE 5.0.1.
kromuch said:
I used this recovery with CM 12 earlier and currently I use it with official GPE 5.0.1.
Click to expand...
Click to collapse
Are u able to flash other roms while on gpe 5.0.1??
Bcoz everyone is facing issue while flashing on gpe!!
Sent from my XT1032 using XDA Free mobile app
Flashhhh said:
Are u able to flash other roms while on gpe 5.0.1??
Bcoz everyone is facing issue while flashing on gpe!!
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
I didn't flash other ROMs instead installed GPE, but it flashes other zips fine.
Maybe CM 12 must begin support GPE file system, if everyone have problems with it.
So does this work any better than TWRP ??
Sent from my moto g
xxAirwickxx said:
So does this work any better than TWRP ??
Sent from my moto g
Click to expand...
Click to collapse
Is there TWRP for GPE? I only saw for the Motorola Edition.
kromuch said:
Is there TWRP for GPE? I only saw for the Motorola Edition.
Click to expand...
Click to collapse
It works for both, as long as the recovery is built with f2fs support, /cache and /system still use ext4 on xt1032.
kromuch said:
Is there TWRP for GPE? I only saw for the Motorola Edition.
Click to expand...
Click to collapse
Yes the X1302 TWRP works
Sent from my moto g using XDA Free mobile app
I have a Moto G (XT1032) running 4.4.4 GPE, and it will not update to Andoid 5.0.1 GPE. I go to install the update, and then it powers off and boots to recovery mode and says this:
Code:
PhilZ Touch 6.55.0
ClockworkmodMod v6.0.5.0
Finding update package...
Opening update package...
Installing update...
Package expects build fingerprint of motorola/falcon_gpe/falcon_umts: 4.4.4/KTU84P.M003/18:user/release-keys or motorola/falcon_gpe/falcon_umts:5.0.1/LRX21Z.M002/15:user/release-keys; this device has motorola/falcon_retgb/falcon_umts: 4.4.2/KLB20.9-1.10-1.9
E: Error in /cache/update.zip
(Status 7)
Installation aborted.
/tmp/recovery.log copied to sdcard/clockworkmod/philz_recovery.log
Send file to Phil3759 @xda
I honestly have no idea what to do as my device is running 4.4.4 not 4.4.2 and it even says my build number is right in About Phone.
bump
Try flashing stock GPE recovery on your device.
SamsungAdmire said:
Try flashing stock GPE recovery on your device.
Click to expand...
Click to collapse
I'll give it a try, although I've done that once.
SamsungAdmire said:
Try flashing stock GPE recovery on your device.
Click to expand...
Click to collapse
Do you have a link to the stock recovery?
SamsungAdmire said:
Try flashing stock GPE recovery on your device.
Click to expand...
Click to collapse
I have flashed the stock recovery, I'm now waiting for the notification to update to 5.0.1 and after that I'll get back to you.
I have the same problem with the german 5.0.2 retail update.
Strange error, i only flashed 4.4.2 manually some time ago. 4.4.3 and 4.4.4 were OTA updates.
Did flashing the stock recovery work? Unfortunately i haven't enough time at the moment to test it myself.
Flashing stock recovery has not worked, although I have never had nor have flashed 4.4.2
Sent from my Moto G XT1032
Damn it.
I don't really understand this. We updated from and to different versions and got the exact same problem.
I know, it's really weird. In wondering if anyone else on XDA is having this problem
Sent from my XT1032 using XDA Free mobile app
Bump
Did you try updating all apps using the Play Store? I had to update my Moto apps before I could get the 5.02 update for my xt1032.
I'll give it a try
Sent from my XT1032 using XDA Free mobile app
Didn't work, it's still giving me a status 7.
Sent from my XT1032 using XDA Free mobile app
It's not worth trying to upgrade to lollipop unless your phone is rooted.
My phone is rooted
Sent from my XT1032 using XDA Free mobile app
A rooted phone may not take the ota update properly. Try unrooting first.
I'll give it a try later today, thanks!
Sent from my XT1032 using XDA Free mobile app
audit13 said:
A rooted phone may not take the ota update properly. Try unrooting first.
Click to expand...
Click to collapse
How to unroot the phone ?
Thanks.
I'll get back to you on that later
Sent from my XT1032 using XDA Free mobile app
After updating my boot loader to 0x4118 in order to continue running CM12 on my XT1032 and to prevent screen tearing when booting, screen tearing effects now occur within my recovery (TWRP 2.8.6.0). Does anyone know if this is an issue with the recovery being incompatible with the boot loader or if its CM12.1 related, and any fixes if possible? Thanks in advance
I thought 2.8.6.0 had already fixed this? I had 2.8.6.0 on my mate's XT1031 and no flickers. It doesn't affect the way you use it, anyway...
Sent from Google Nexus 4 @ CM12
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
Use TWRP latest version available in Moto G development section... Official TWRP will cause issue Moto G
padhu1989 said:
Use TWRP latest version available in Moto G development section... Official TWRP will cause issue Moto G
Click to expand...
Click to collapse
Ahhh thanks a lot, fixed now!!
LSPandaaa said:
Ahhh thanks a lot, fixed now!!
Click to expand...
Click to collapse
press Thanks button instead of typing it
Hello,
I have the Moto G with Cm 12.1 nightly, can I dirty flash CM12.1 stable build onto my nightly. Im asking because I want to keep my apps, call log and viber messages therefore wiping is not really an option.
Thanks you.
Pls correct the thread name. Its not CM13
Sent from my MotoG3 using XDA Premium 4 mobile app
it should work yes, but make a backup if it goes wrong.
and please change the name from cm13 to cm12.1