Yesterday I flashed CM-12.1-20160822-NIGHTLY without any issues...followed by Gaaps.
I am using ThunderZAp-4.16 kernel.
I found no significant bug other than that I can't switch on the WIFI now. I am sure there is no problem with my WIFI because I have been using it for the past one year.
I did a clean re-installation but the problem with the WIFI still persists.
Can anyone please help?
What stock rom version were you on before? And don't use tz, it is outdated now.
so, first, i flashed the basic taoshan kernel that comes along with cm12.1
i read in one of the xda threads that the wifi problem can be fixed by flashing stock rom and then flashing cm12.1. i tried to flash C2104_15.3.A.1.17_Generic, but there are some issues with my Flash Tool because, in the flash window I can only see the device name. All the other options are greyed out. Even the contents section is empty.
Now i recoverd a recovery using TWRP. so currently i have a rooted and bootloader unlocked 15.0.A.2.17. I have unrooted and relocked my bootloader so that I can update upto 15.3.A.17 using the official updates.
After getting 15.3.A.17 this way, I plan to root and unlock bootloader again...followed by flashing cm12.1 nightly using twrp.
Will doing all of this make the wifi work on CM 12.1?
newguyknowsnothing said:
What stock rom version were you on before? And don't use tz, it is outdated now.
Click to expand...
Click to collapse
so, first, i flashed the basic taoshan kernel that comes along with cm12.1
i read in one of the xda threads that the wifi problem can be fixed by flashing stock rom and then flashing cm12.1. i tried to flash C2104_15.3.A.1.17_Generic, but there are some issues with my Flash Tool because, in the flash window I can only see the device name. All the other options are greyed out. Even the contents section is empty.
Now i recoverd a recovery using TWRP. so currently i have a rooted and bootloader unlocked 15.0.A.2.17. I have unrooted and relocked my bootloader so that I can update upto 15.3.A.17 using the official updates.
After getting 15.3.A.17 this way, I plan to root and unlock bootloader again...followed by flashing cm12.1 nightly using twrp.
Will doing all of this make the wifi work on CM 12.1?
Wow I'm not sure. Why don't you try older version of flashtool (0.9.11). This ver works well for me.
Flashed stock rom using Xperia PC Companion. But now i am confused as to which Cyanogenmod ROM i should flash.
Is there a stable version somewhere? All that i could find were nightlies.
xperiajack28 said:
Flashed stock rom using Xperia PC Companion. But now i am confused as to which Cyanogenmod ROM i should flash.
Is there a stable version somewhere? All that i could find were nightlies.
Click to expand...
Click to collapse
Yes their is not stable version on cyanogenmod ,you can find more stable releases at Free experia community but still they aren`t that stable and they are pretty old..... http://fxpblog.co/
Related
Hi
Just moved onto the Moto G from a couple of Huawei devices, G300 then Y300... (bye bye Modaco!) - So I'm pretty used to flashig, wiping etc using TWRP and CWM...
Anyhow, got the Moto G (XT1033), booloader unlocked, done a full restore to clean 4.2 and let it update to 4.4 fine, no problems.
Installed the latest CWM, got root, all fine... again, no problems...
But EVERY rom I try - slim, CM11, always install OK but on booting come up with phone process failures and I have to abandon.
I tried putting the 422 modem zip from the CM11 thread on, made no difference.
So I've rewiped back to stock and updated to 4.4.2, and flashed CWM, but still can't install a custom rom, getting the phone process error on startup.
Any suggestions?
Resolved myself! Revert to factory, install CWM and flash new roms without doing the ota to kitkat first.
TangerineTractor said:
Resolved myself! Revert to factory, install CWM and flash new roms without doing the ota to kitkat first.
Click to expand...
Click to collapse
So you installed CM11 from stock jelly bean??
Sent from my XT1032 using Tapatalk
xheon said:
So you installed CM11 from stock jelly bean??
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
Yes. Originally I let it run through the ota update, then installed CWM and tried to install various roms. All gave me a FC on outdoor process as soon as I booted.
tried again with TWRP, same thing. third time lucky, I restored to factory, let it boot but didn't do the ota update, installed CWM for 4.3 bootloader, and all has been find since, flashed several roms with no problems.
So you have a dual SIM version and you flashed a custom ROM which means only one SIM works now. Am I right? How is everything else, no issues with performance just because yours is a dual SIM variant?
Ok, this is weird, a while ago i didnt had any problems installing any kind of custom rom, used CWM while wiping everything... eveything was OK, ROM worked OK, etc... But one time i installed a ROM (Slimkat) and i lost signal, tried to use my recovery of stock android but it didnt work, so i tried a lot of things untill i got bootlop without being able to install anything since some files were missing, bad luck
After that, i just reflash stock 4.3 and upgrade from there 4.4.2, everything fine again... except that i cant install any kind of ROM, every ROM says "installation succesful" but everyone is stuck into bootloop.
While i havent tried ALL ROMS i have tried the same ones i was using (Nexus G+, LiquidSmooth and CM11), so i guess this problem is coming from my device.
On a side note, i tried to factory reset, but no luck... it shows the Android working but it inmediately turns the screen off, and then it shows it again and then off again... in an infinite loop
Same problem!
Bump.
I just got my Moto G yesterday (European XT1032), updated to 4.4.2, unlocked bootloader, rooted with superboot and flashed Philz Touch CWM.
Seems I have done everything by the book, wipes included, but no luck. I tried Slimkat, Paranoid and Codename Lungo (latest builds as of 3/12).
Liberr said:
Bump.
I just got my Moto G yesterday (European XT1032), updated to 4.4.2, unlocked bootloader, rooted with superboot and flashed Philz Touch CWM.
Seems I have done everything by the book, wipes included, but no luck. I tried Slimkat, Paranoid and Codename Lungo (latest builds as of 3/12).
Click to expand...
Click to collapse
Hmmm... Pay attention to which version of Bootloader you are using.
You might want to try both 4.3 and 4.4 to see which one would work.
Extract the motoboot.img from the stock .zip image for your phone, then flash with mflashboot flash motoboot motoboot.img
Good luck!
neozen21 said:
Extract the motoboot.img from the stock .zip image for your phone, then flash with mflashboot flash motoboot motoboot.img
Click to expand...
Click to collapse
Thanks. I'll give that a try. Is there a way to check bootloader version on the phone? If that doesn't work out I'll start from scratch and report back in this thread..
Liberr said:
Thanks. I'll give that a try. Is there a way to check bootloader version on the phone? If that doesn't work out I'll start from scratch and report back in this thread..
Click to expand...
Click to collapse
Hmmm.. I see there is a version number on mine, 41.05 dated 2013-12-06, but I'm not sure if that's the version or not.
And yeah... if changing the bootloader doesn't help, you probably would have to restore from the stock image and start over..
Got root and custom roms working after I 1.) downgraded to 4.3 and 2.) flash TWRP (instead of CWM).
So I'm not sure what the problem was. Besides the two main rooting methods (superboot and custom recovery), there are some other methods described on the forum specifically for people who already did a international variant OTA to 4.4.2. and one that is absolete (here) but apparently works for some when the two main methods fail.
However I'm still not sure if this solved everything. I am not sure if I can flash Cyanogenmod (which is 4.4.2) over a 4.3 firmware. Maybe I need to manually flash a 4.4.2 radio or something... Gonna check that out next...
EDIT: No need to downgrade. Not sure how it works but two main root methods (superboot and custom recovery) didn't work for me. Somehow I got stuck in boot animation. Just installed TWRP instead of CWM after Kitkat firmware (EU Retail) and rooted (/installed Super Su) from there. Everything works fine now.
I am perplexed:
I had previously installed many custom roms after updating to stock kitkat, including CM 11. However, I am not able instally cyanogenmod, AT ALL. I have gone through all the steps and all the recoveries, CWM & TWRP all versions. After the installation, the phone hangs on the boot logo, always.
Any clue would be appreciated. Thank you.
U sure u flashed/fastbooted the recommended kernel correctly and did a full wipe before installing the Rom?
Sent from my MT25i
I highly doubt you installed CM11 with the KitKat kernel installed. It won't work. The only way it would work is to FXZ back to JB and then install the previous version of CWM or TWRP.
Currently, there are no ROMs working with the KitKat versions of CM11 or TWRP, although dhacker is working on a new CM11 using the latest KK kernel for the RAZR HD phones and the developer for the Nexesque ROM is also working on an updated version that uses the KitKat kernel as well.
iBolski said:
I highly doubt you installed CM11 with the KitKat kernel installed. It won't work. The only way it would work is to FXZ back to JB and then install the previous version of CWM or TWRP.
Currently, there are no ROMs working with the KitKat versions of CM11 or TWRP, although dhacker is working on a new CM11 using the latest KK kernel for the RAZR HD phones and the developer for the Nexesque ROM is also working on an updated version that uses the KitKat kernel as well.
Click to expand...
Click to collapse
It was very strange situation. I ended up getting CM to work by using CWM 6.0.4.4. FMI (for my information), I need to use CWM 6.0.4.4 will be needed to install custom roms.
Thanks for the advice..
Hello,
I keep trying to update to the latest nightly to get cyanogenmod 12 on XT1302. However they don't work. I get weird scan lines, even during the boot logo and animation. Everything is slow and unstable. During installation it always says root access possibly lost, fix, yes or no. Thankfully I have a working backup, but it's stuck on an old 2014 cm 11 snapshot and I want to upgrade
I suspect there is a problem with gapps since I get incessant "X app has stopped working error" messages and it's always a google service. However I do not know what the procedure is. I downloaded the cm12 gapps and flashed them after flashing the nightly as said in faq but it doesn't seem to work. Sometimes even Trebuchet stops working, making the phone totally unusable.
Any help would be greatly appreciated. :good:
Are you running with a lollipop bootloader? I think the latest CM12 requires it.
audit13 said:
Are you running with a lollipop bootloader? I think the latest CM12 requires it.
Click to expand...
Click to collapse
I've been googling this and I think you have correctly identified the issue. If I install the lollipop bootloader, will I be able to go back to my cm11 backup in case of an emergency?
Just to confirm, to update the bootloader, you have to flash the brazil lollipop rom and it should work?
If you unzip the stock ROM, the bootloader is the motoboot.img file.
I don't think you need to flash everything, just the bootloader file. If that doesn't allow you to use CM12, you may have to restore your CM11 nandroid and then flash CM12.
I am running 4.4.2 I installed the 20g bootstack I believe that's what it's called and then installed cloudy. Every time I try to flash any cm based ROM it gives me an error or doesn't boot at all and gets stuck in the lg boot screen. I ready that I have to change the boot loader or the radio but I can't seem to find which one is correct. I am also choosing the right d801 version for cm based roms. Any help would be much appreciated thanks.
Sent from my LG-D801 using XDA Free mobile app
Hey did you figure this out yet? For the CM 12 nightly, after I flashed the 20g bootstack, I flashed the D801 JB bootloader from blastagator http://blastagator.ddns.net/bootloader.php. Then I was able to install CM.
This worked for me. Thanks.