I recently purchased a D800 G2 off eBay, so I haven't the foggiest of this phone's history. When I got it, the stock firmware was pretty broken (Play Store not working, UID errors, ETC), so naturally I didn't hesitate to root and load TWRP via AutoRec (and subsequently updated to the latest unofficial TWRP). Unfortunately, once I flashed the latest snapshot build of CM13 (official), things took a turn for the weird. WiFi and cellular data will shut off sporadically--even at moments, leaving me internetless for 5-10 minutes--and this applies to all other snapshot builds of CM13. It will not turn back on manually; only time and patience can do that. Only on CM12.1 official or unofficial builds would internet hold.
I was wondering how I should approach this. My plan was to flash a KK tot and update the last LP firmware OTA; root with either OneClick or KingRoot; install recovery via AutoRec and bump update to unofficial TWRP 3.0.0.2; and finish with the latest official snapshot of CM13. I just wanted to make sure I'm going about this the right way or if CM13 isn't a good fit for the D800 variant of the G2. Any help is appreciated!
Related
Hi. After I posted this message, the problem seems to be that my ROM is hopelessly old. But after following the recommendations, I still couldn't update.
I tried to install "cm-11-20141112-SNAPSHOT-M12-moto_msm8960.zip" from ClockworkMod recovery. Got this error message:
Code:
This package is for device: moto_msm8960, xt907, scorpion_mini, smq, xt926, vanquish; this device is xt925.
(Status 7)
Installation aborted.
But I was told (and the message on the CM wiki confirms it) that builds have been unified.
What should I do?
Looking for installs for xt925 specifically, the last stable is the one I have, and the few nightlies are very old as well and I doubt would solve the problem.
There is the CM12 nightly for xt925 released today, but since I'm highly dependent on my phone functioning while traveling next week and can't afford things going wrong, I'd rather avoid nightlies and experimental versions unless I have absolutely no alternative to have my phone encrypted.
Advice?
Thanks a lot.
By the way, I prefer to not make a factory reset unless it's necessary.
Is it necessary? Do I have to wipe cache? Wipe dalvik? Some sites say yes, some sites say not needed.
Is the answer different depending on whether I would be upgrading to a more recent version of CM 11 or to CM 12 nightly?
Thanks!
@taylortm Please read again what I wrote to you here: http://forum.xda-developers.com/showpost.php?p=58132610&postcount=2
You can't use moto_msm8960 CM11 builds nor xt925 CM12 build unless you update your device to stock KitKat firmware by Motorola first.
While your device is still using JellyBean bootloader/modem firmware, you can update only to moto_msm8960_jbbl CM11 builds.
That's right, I overlooked that, thank you. Was able to upgrade now.
I thought that because my Android stock was KitKat before I flashed CM11, that the bootloader would also be KK. It was a jbbl, because now it worked.
Everything seems to be working just fine, was no need to clear caches or data or anything. My compass is also now fixed.
I just started encryption and it wasn't locked in the robot anymore, it booted and now shows a progress bar with 4% complete.
Thanks, kabaldan!
Just one more question, will there be CM12 for moto_msm8960_jbbl later, or if I want to upgrade to CM12 I will have to do this kkbl workaround you mentioned?
kabaldan said:
@taylortm Please read again what I wrote to you here: http://forum.xda-developers.com/showpost.php?p=58132610&postcount=2
You can't use moto_msm8960 CM11 builds nor xt925 CM12 build unless you update your device to stock KitKat firmware by Motorola first.
While your device is still using JellyBean bootloader/modem firmware, you can update only to moto_msm8960_jbbl CM11 builds.
Click to expand...
Click to collapse
Hi, so i recently bought an brand new (factory Unlocked) LG G2 32gb (D801). It is running stock firmware android 4.2.2. I want to put official CM12 on it. From what I have read, the nightly versions of CM12 are really stable, and they do not have a lot of problems (if anyone has any problems with theirs please share, Im really interested). I am going to use this as my daily driver. My past history of rooting and putting cm on phones only includes the Samsung Captivate (captivatemtd) which I installed CM 10 and 11 (no problems with it). Could someone provide me a detailed, step by step method of installing cm onto the D801? Youtube videos are also helpful. Thanks so much in advance.
P.S. What custom recovery would be better with the LG G2? CWM or TWRP? (I have only used CWM in the past)
P.P.S. Will I be able to update from the nightlies to the more stable build of CM12 (ex. snapshot), without wiping the whole phone and flashing the software from a computer?
mkondrak said:
Hi, so i recently bought an brand new (factory Unlocked) LG G2 32gb (D801). It is running stock firmware android 4.2.2. I want to put official CM12 on it. From what I have read, the nightly versions of CM12 are really stable, and they do not have a lot of problems (if anyone has any problems with theirs please share, Im really interested). I am going to use this as my daily driver. My past history of rooting and putting cm on phones only includes the Samsung Captivate (captivatemtd) which I installed CM 10 and 11 (no problems with it). Could someone provide me a detailed, step by step method of installing cm onto the D801? Youtube videos are also helpful. Thanks so much in advance.
P.S. What custom recovery would be better with the LG G2? CWM or TWRP? (I have only used CWM in the past)
P.P.S. Will I be able to update from the nightlies to the more stable build of CM12 (ex. snapshot), without wiping the whole phone and flashing the software from a computer?
Click to expand...
Click to collapse
I can't get it to work either. D801 with TWRP, tried installing the newest nightly and get an error.
GamerDaddy14 said:
I can't get it to work either. D801 with TWRP, tried installing the newest nightly and get an error.
Click to expand...
Click to collapse
This method worked fine for me - https://www.youtube.com/watch?v=py4pOmY2YQA
I'm using a OnePlus One, and the latest gapps and 12.1 nightly builds.
However, I noticed that every morning when i wake up, the install screen of cyanogenmod is back. It seems all data and so on is still on the phone, because it says I already provided a Google account and so. This is the third time I'm setting up the device from scratch to 12.1 stable nightly. Any idea why it keeps resetting? Using no custom roms or kernels, just the ones provided in the CM 12.1 Nightly builds (18/04) was the latest official one).
The device is rooted, but it's annoying to spend 2 hours setting it back up every time, re-installing everything. Any help would be appreciated.
gapps stock: http://forum.xda-developers.com/android/software/reborn-gapps-5-t3074660
nightly bacon (OnePlus One): http://download.cyanogenmod.org/?device=bacon
i had upgraded my mexi-maxx to lollipop a few months ago and could no longer stand it. outside of being picky with my phone, the GPS didn't work as I had hoped.
i reverted back to kitkat by means of a TWRP backup I had. Had some issues with doing so. some of my images would not work, but a stock on of KK did. could not use any of @ChazzMatt images either; nor factory images as RSD pinged a FAIL. started getting worried, but just about all good now.
the phone now boots directly to bootloader mode and i have to choose 'start' to boot into system.
is there a way to change this? thanks all.
You can try Brazil 22.34.16 lollipop build, it is the most stable 5.0.2 for moto maxx / turbo atm. Your issue is caused by the incompability with the lollipop bootloader and 4.4 kitkat twrp image. Take a copy of your nandroid backup to your pc and flash 4.4.4 images except gpt.bin.
http://forum.xda-developers.com/droid-turbo/help/tutorial-how-to-flash-official-firmware-t3074724 ( following 5.step )
Then flash twrp recovery and restore your 4.4.4 nandroid, it will be fine this time.
Semseddin said:
You can try Brazil 22.34.16 lollipop build, it is the most stable 5.0.2 for moto maxx / turbo atm. Your issue is caused by the incompability with the lollipop bootloader and 4.4 kitkat twrp image. Take a copy of your nandroid backup to your pc and flash 4.4.4 images except gpt.bin.
http://forum.xda-developers.com/droid-turbo/help/tutorial-how-to-flash-official-firmware-t3074724 ( following 5.step )
Then flash twrp recovery and restore your 4.4.4 nandroid, it will be fine this time.
Click to expand...
Click to collapse
Thanks. really dislike LP as a whole. are there advantages i'm not seeing? battery was the same, wasn't really faster, GPS terrible (used stock rooted and CM12.1)
want to make sure I understand what i'm doing. according to thread you linked to (thank you btw I could not find that earlier too busy freaking out) because i took the LP OTA i have the upgraded LP bootloader, but I do not need to downgrade it to go back to KK? meaning LP BL is backwards compatible?
snowboardwcu said:
Thanks. really dislike LP as a whole. are there advantages i'm not seeing? battery was the same, wasn't really faster, GPS terrible (used stock rooted and CM12.1)
want to make sure I understand what i'm doing. according to thread you linked to (thank you btw I could not find that earlier too busy freaking out) because i took the LP OTA i have the upgraded LP bootloader, but I do not need to downgrade it to go back to KK? meaning LP BL is backwards compatible?
Click to expand...
Click to collapse
You need to downgrade to 4.4.4 with stock images except gpt.bin or else, it is normal having issues like you're facing. Lollipop bootloader is meant to work on lollipop system. Anyway, just flash 4.4.4 full images with mfastboot except gpt.bin, then flash your twrp recovery and restore your kitkat nandroid. It will be fine.
I downgraded my xt1225 back in time with the same tutorial and it works fine.
this works perfectly. old twrps work again.
trying to the india version of LP as some are saying its vetter, installed and then put cm12.1 back on. gonna give it a week or so and see if GPS locks better. if not, back to kitkat. thanks for the help.
snowboardwcu said:
this works perfectly. old twrps work again.
trying to the india version of LP as some are saying its vetter, installed and then put cm12.1 back on. gonna give it a week or so and see if GPS locks better. if not, back to kitkat. thanks for the help.
Click to expand...
Click to collapse
India firmware is as bogus as a software can get and they didn't deploy patch ota's to fix its issues. Your best stock lolipop bet is brazil 5.0.2
Semseddin said:
India firmware is as bogus as a software can get
Click to expand...
Click to collapse
bogus as in not official or bogus as in crap sw&support? again, no interest in using stock LP. cm12.1 fits all my needs except the double swipe to pattern unlock, which from what i read i'm stuck with.
at this point i'm only interested in the best driver set for the phone. interested in getting better GPS lock and hopefully better reception at work, in the middle of a giant metal building (kitkat worked much better IMO WRT to reception and LTE/HSPA+ handover)
Semseddin said:
India firmware is as bogus as a software can get and they didn't deploy patch ota's to fix its issues. Your best stock lolipop bet is brazil 5.0.2
Click to expand...
Click to collapse
snowboardwcu said:
bogus as in not official or bogus as in crap sw&support? again, no interest in using stock LP. cm12.1 fits all my needs except the double swipe to pattern unlock, which from what i read i'm stuck with.
at this point i'm only interested in the best driver set for the phone. interested in getting better GPS lock and hopefully better reception at work, in the middle of a giant metal building (kitkat worked much better IMO WRT to reception and LTE/HSPA+ handover)
Click to expand...
Click to collapse
If you were just running stock LP -- which you say you do not want to do -- then @Semseddin is correct that Brazil and Mexico factory images are better than India. Just because they both have newer updates India was never given.
In my images thread you can see,
Brazil: QUARK_RETBR_5.0.2_LXG22.33-12.13_cid12_subsidy-DEFAULT_CFC.xml.zip
vs
India: QUARK_RETEU_INDIA_5.0.2_LXG22.33-12.11_cid7_subsidy-DEFAULT_CFC.xml.zip
Then, @Jaocagomez has an OTA which takes it to:
OTA to 22.34.16 Brasil Retail Stock Lollipop 5.0.2 /// Blur_Version.22.34.16.quark_retbr.retbr.en.BR.zip
But CM12.1 beats all that by having 5.1.1.
Yes, CM 12.1 (5.1.1) is still using the stock 5.0.2 kernel source -- because Motorola has not yet released 5.1 kernel source they gave to the XT1254 Droid Turbo back at the beginning of July. But it's still 5.1.1 with 5.02 kernel source, NOT 5.0.2. with 5.02 kernel source. It's a vast improvement! Stock 5.0.2 was too laggy for me.
So, for me running CM12.1 (or another 5.1.1 custom ROM) gives me the best of both worlds. I have the latest kernel source/radio that Motorola has released for our phones, while still having 5.1.1.
_________
Now having said all that, my wife and I have two XT1225.
I flashed both to India LP 5.0.2, then flashed CM.
I also re-flashed the India radio and bootloader (5.0.2) found in the CM12.1 op post just to make sure.
I have no problem with GPS. I use GPS every day. But I use TopNTP. See this post:
http://forum.xda-developers.com/showpost.php?p=62320192&postcount=624
_____
The only issues I have with CM12.1 is my phone seems to lock on to HSPA when leaving Wi-Fi network even though there are strong LTE signals around -- and even though I have "LTE Preferred" chosen. As I drive it will eventually move from HSPA to LTE, but takes like 15-20 minutes.
If I stop the car, remove and put back in the SIM card 2 or 3 times, then it finally locks onto LTE network that was there all along!
It was a change CM made to APNs/telephony back end of July that seems to cause this. (I kept my wife's phone on the July 29 nightly. We will be in the car, she will have LTE and I will have HSPA. Arghhh.)
But I put up with it, and keep flashing new nightlies -- hoping it will be fixed -- and also because other than that CM12.1 is very smooth and much better than stock 5.0.2. I don't want to flash my phone back to July 29 nightly. I still have it -- but I would have to wipe my phone completely and reinstall for it to work. I already tried just flashing that older nightly over a newer one and I got boot loops. I restored latest back up from recovery and haven't bothered since.
Fixed this issue. See here:
http://forum.xda-developers.com/showpost.php?p=63048064&postcount=696
ChazzMatt said:
The only issues I have with CM12.1 is my phone seems to lock on to HSPA when leaving Wi-Fi network even though there are strong LTE signals around -- and even though I have "LTE Preferred" chosen. As I drive it will eventually move from HSPA to LTE, but takes like 15-20 minutes.
If I stop the car, remove and put back in the SIM card 2 or 3 times, then it finally locks onto LTE network that was there all along!
It was a change CM made to APNs/telephony back end of July that seems to cause this. (I kept my wife's phone on the July 29 nightly. We will be in the car, she will have LTE and I will have HSPA. Arghhh.)
But I put up with it, and keep flashing new nightlies -- hoping it will be fixed -- and also because other than that CM12.1 is very smooth and much better than stock 5.0.2. I don't want to flash my phone back to July 29 nightly. I still have it -- but I would have to wipe my phone completely and reinstall for it to work. I already tried just flashing that older nightly over a newer one and I got boot loops. I restored latest back up from recovery and haven't bothered since.
Click to expand...
Click to collapse
I'm fairly new at using custom ROMs on my phone (Moto G 2013 XT1304) and I want to get some answers that I've not been able to find, at least clearly, on my own. I'll ask all in one go in case others might benefit. I appreciate any help or confirmation in response.
GAPPS
Following the guide on xda, I installed CM 12.1 successfully and also installed the gapps package from July located in the cgapps site (can't post links yet). I was confused about the other option being called "OpenGApps" and thought they were the ASOP vs Google version. Once booted, Google Play Services updated but I've still had a few "Google Plays Services has stopped working" issues. My question is this, should I reflash and use the latest nano install from OpenGApps or does the play store update these relevant apps and framework once up and running anyway? Which is best?
Nandroid Backups
I want a way to fully backup the entire phone and system so that I can fully restore if something should get botched - something like a full drive image on a computer. Using TWRP backup, if I were to backup the system, data and boot partitions, would restoring those to a completely wiped phone bring it back to the state it was in when backed up? And do those partitions need to be wiped before restore or does the restore process do that anyway? Last, is is this the best way to do this sort of backup?
ROM updates
First, if "Check for Cyanogenmod updates" is set on the phone, and I have a snapshot installed, will this only provide an update if another snapshot is released? If not, how does that work since there is a new nightly releases every day.
Second, I've read a lot of negative about downgrading ROMs, but it seems ok to flash a newer version of the same one while keeping the data in place. Is this correct? Is there a "best practices" post on this somewhere?
I'm experienced with Linux, and feel somewhat at home with Android because of that, but I only switched to CM12.1 recently because Motorola had done nothing about the choppy bluetooth audio in the Lollipop update for the Moto G 2013. I use the feature extensively and it was left too broken to enjoy, but works perfectly in the CM ROM. Now I'm hooked and want to go further. Thanks for any help or direction.
Moto G 16MB (2013)
CyanogenMod 12.1 (Snapshot 11/17)
TWRP 2.8.7.0 (h2064)