Guys, I got the OTA to android 5.0.2 about a week back, but I'm tired of the poor performance. Nova 3 is now unplayable at parts where transparency is used. So, I was thinking to revert back to KitKat 4.4.4.
Will the performance improve after the next update, i.e., 5.1??
The dilemma I'm facing now, is to whether flash back to stock KitKat 4.4.4, or to flash cyanogenmod 11 using cwm recovery. I also want to know which one of the two will be easier and less problematic.
Thank you.
OK, problem solved.
I installed cm11 using philz recovery. Now, the phone is blazing fast!
Did not downgrade to stock 4.4.4. Instead to cm11 4.4.4.
Related
I had some trouble rooting after I first did a 4.4.2 OTA. So I downgraded to 4.3 and got root and installed TWRP without any trouble.
So from a 4.3 firmware I went to Cyanogenmod (Android 4.4.2). Is that ok ? Or do I need to upgrade radio, boot or other parts that dont come with a custom rom? In other words: is a (rooted) 4.4.2 firmware a precondition for installing alternative 4.4.2 roms?
Well, everything might not work perfectly as many things (though little) changed from 4.3 to 4.4. Yup, most of those things (radio,etc) change, flashing a cm11 rom wont change those and cm will most likely need them. Better to upgrade to 4.4. Also, does ART (new kitkat runtime) need anything new from kernel or anything? I don't see anyone who seems to have tried this and might mostly not work.
Also, What root trouble did you have? Easier to solve that issue than deal with any new issues that might arise from this.
hemanthmahesh said:
Well, everything might not work perfectly as many things (though little) changed from 4.3 to 4.4. Yup, most of those things (radio,etc) change, flashing a cm11 rom wont change those and cm will most likely need them. Better to upgrade to 4.4. Also, does ART (new kitkat runtime) need anything new from kernel or anything? I don't see anyone who seems to have tried this and might mostly not work.
Also, What root trouble did you have? Easier to solve that issue than deal with any new issues that might arise from this.
Click to expand...
Click to collapse
Thanks. I will look into that. The kernel is included in a ROM though wright? So that wont be an issue I guess... But just to be save I'll flash 4.4.2 firmware and start from there. My problem was I actually got root, but flashed custom roms always got stuck in the boot animation. The thread on that is here.
Guys, I got the OTA to android 5.0.2 about a week back, but I'm tired of the poor performance. Nova 3 is now unplayable at parts where transparency is used. So, I was thinking to revert back to KitKat 4.4.4.
>>Will the performance improve after the next update, i.e., 5.1??<<
The dilemma I'm facing now, is to whether flash back to stock KitKat 4.4.4, or to flash cyanogenmod 11 using cwm recovery. I also want to know which one of the two will be easier and less problematic.
Thank you.
I want to ask if there is any problem (flicker screen, red notification on booting up...) when I install CM11 from stock 5.0.2 on Falcon Moto G XT1032? (follow this official guide on CyanogenMod: http://wiki.cyanogenmod.org/w/Install_CM_for_falcon)
Thank you.
I've done this recently and the only issue I've noticed is the screen flickering problem. The solution is to simply press the power button to lock the screen then unlock it and it should be fixed. You only have to do this once but if you reboot your phone you will have to lock/unlock again on first boot.
Thank you for your answer. Just to be sure, did you follow CM guide? Is there anything important which I should be careful about? (I did the same thing with several phones but still noob)
I just booted into custom recovery (I use Philz) and wiped the different partitions along with /cache and /dalvik. You can follow the guide and use the push method or you can use sideload which I did.
I did that and now i have problems with the mac address (i was using 5.1.1) my shows me a different mac and i don't know how fix it, but if i back to LP the problem is solved.
It's a bootloader issue for sure and general happen because you're bootloader is updated to Lolipop 5.0.2 and now you install kitkat as cm 11 over Lolipop.
In simple words your bootloader is new while the software is old
screen flickering issue can be resolved by downgrade bootloader but "BE EXTREMELY CAUTIOUS" failed to upgrade bootloader make your device permanently dead and downgrading is not recommended....
I will recommend try cm12.1 it's rock solid stable as cm11
I finished installed CM 11, firstly the prob is screen flickering. Then after installing all my apps, the android.com.systemui was crashed over and over and cannot use anymore. I reflashed CM and gapps and reinstalled apps but it happened again. Finally, I had to returned to Lollipop.
Anyway, thank you all for your help
Same thing happened to me unfortunately but I've found this one here and it is working beautifully. Try it and see if it works for you without the constant systemui errors.
Thank you. At the moment i am quite happy with GPE version. It seems that this version GPE 5.1.1 is better than Moto stock one.
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
Sup guys,
I've rooted every phone I've had, but I do it so infrequently that I always have to refresh my memory with it. Current situation is that I have a rooted M8 running mostly stock 4.4.4 ROM, but with a bunch of Xposed mods and a few system tweaks - it's dialed in just the way I want it, but the screen is separating so I've got my hands on another M8 running 4.4.2. I basically want to get the 4.4.2 M8 to the state of my 4.4.4 device. I've already made a complete backup ROM from the 4.4.4 phone and I want to restore that ROM to the 4.4.2 device. With the 4.4.2 device, I plan to:
S-Off (Try Firewater. May or may not work. If doesn't work, try Sunshine)
Install recovery - CWM or TWRP
Flash Super SU
Update firmware from 4.4.2 to 4.4.4 from here: http://forum.xda-developers.com/showpost.php?p=52017763&postcount=2
Flash my complete backup ROM from my current device
Sanity check? Am I missing anything here? When I rooted my current M8 (4.4.2), weaksauce actually worked, and I flashed CWM recovery and Super SU by placing them on the SD card. That is what I plan to do again since that was so easy. Recommendations?
Cheers guys!
j006 said:
Sup guys,
I've rooted every phone I've had, but I do it so infrequently that I always have to refresh my memory with it. Current situation is that I have a rooted M8 running mostly stock 4.4.4 ROM, but with a bunch of Xposed mods and a few system tweaks - it's dialed in just the way I want it, but the screen is separating so I've got my hands on another M8 running 4.4.2. I basically want to get the 4.4.2 M8 to the state of my 4.4.4 device. I've already made a complete backup ROM from the 4.4.4 phone and I want to restore that ROM to the 4.4.2 device. With the 4.4.2 device, I plan to:
S-Off (Try Firewater. May or may not work. If doesn't work, try Sunshine)
Install recovery - CWM or TWRP
Flash Super SU
Update firmware from 4.4.2 to 4.4.4 from here: http://forum.xda-developers.com/showpost.php?p=52017763&postcount=2
Flash my complete backup ROM from my current device
Sanity check? Am I missing anything here? When I rooted my current M8 (4.4.2), weaksauce actually worked, and I flashed CWM recovery and Super SU by placing them on the SD card. That is what I plan to do again since that was so easy. Recommendations?
Cheers guys!
Click to expand...
Click to collapse
firewater sever is taken down, even if you have an old version of it laying around it is useless.. you must pay for sunshine.
but other than that everything looks good.
you have your nandroid backup, on the new m8, s-off using sunshine, then update the firmware from 442 to 444, then flash custom recovery (TWRP is recommended), and then wipe and restore the nandroid and you should be good to go. :good:
(no need to flash supersu as the ROM you have backed up using nandroid is already rooted)
Many thanks! A couple of years ago when I did this I remember it being fairly straightforward. Do you personally find any real benefit in upgrading to one of the Lollipop ROMs this go 'round? Seems like it's more trouble than what you gain, though I may be uninformed of course..
Cheers!
j006 said:
Many thanks! A couple of years ago when I did this I remember it being fairly straightforward. Do you personally find any real benefit in upgrading to one of the Lollipop ROMs this go 'round? Seems like it's more trouble than what you gain, though I may be uninformed of course..
Cheers!
Click to expand...
Click to collapse
I find many benefits to LP over KK personally.
If you like a stock ROM we have stock based LP ROMs, and firmware.zip you can flash and you are up an running a stock LP ROM within 10 minutes. Sure you need to set things up, but most can be backed up and if you take some screen shots of everything it's pretty easy to get everything set up to your liking.
If you want some customization there are ROMs like mine, that come mostly stock with some benefits like root, busybox, etc, and then offer you a MOD Pack.
See ROM thread here
If you want to customize pretty much every aspect of the ROM you have Venom at your fingertips.
Venom ROM thread
There is the benefit of having all the security updates with the newest firmware.
We also have Marshmallow 6.0 ROMs out already that are rock solid.
A Google Play Edition ROM found here
And a Sense based ROM found here
You can also run some Sense 7 ROMs that are very stable, you can find one in my linked thread posted above, and in the Development area.
I personally would try things out, that's the great benefit of root/s-off/custom recovery/ROMs
You can always make a nandroid backup of your current ROM, and flash the older firmware to get right back where you left off.
Best of luck, enjoy your flashings