After flashing a GPE ROM on a non-GPE device, I get these results: http://webmup.com/naZUn/vid.webm
Basically it is a weird horizontal transparent line that moves down the screen... After flashing the 4.4 GPE ROM got those symptoms -- But even after going into TWRP recovery, the line is still there!
Also, once I decided to revert to stock to try and fix it, there is still this annoying line after booting!! This includes stock ROM, CM, and TWRP ( But once booted, locking and unlocking will fix it temporarily)
I don't think its a hardware problem because the fastboot screen does not face the issue :\
Please can anyone give me some guidance? Im really desparate.
The cause of this phenomenon is the Bootloader (BL) included with Lollipop. Your current BL is 41.18, the KitKat version is 41.13. There is no way to return to the KitKat BL, and I suggest you avoid trying. The issue will disappear when using a Lollipop ROM and Kernel.
right now i'm on GPE 5.0.1 and when ever i flash cm12 over it i get like this screen flickering
and my question is we wont be able to use cm12 over 5.0.1 or what? Please some one explain
The issue is kernel-related and I expect can be resolved with a custom Lollipop Kernel. Current CM12 ROMs need to take into account the new bootloader - then the problem will be fixed.
Thanks for the explanation!
Shouldn't CM 12 already be using a lollipop kernel though? What sort of changes to the kernel are required to fix the issue?
marcoms said:
Thanks for the explanation!
Shouldn't CM 12 already be using a lollipop kernel though? What sort of changes to the kernel are required to fix the issue?
Click to expand...
Click to collapse
Yes, but as you have observed; CM12's current Kernels (or any KitKat Kernel) are not fully compatible with the new Lollipop Bootloader (v41.18). The display problem does not occur with Stock Motorola Lollipop Kernels.
Perhaps @TeamMex can suggest what changes are needed.
lost101 said:
Yes, but as you have observed; CM12's current Kernels (or any KitKat Kernel) are not fully compatible with the new Lollipop Bootloader (v41.18). The display problem does not occur with Stock Motorola Lollipop Kernels.
Perhaps @TeamMex can suggest what changes are needed.
Click to expand...
Click to collapse
well i don't have time to investigate what i need change to make fully compatible with new bootloader.
maybe when motorola release his kernel for lollipop I can check...
for now we need wait.
Can someone experiencing this issue try the following?
Settings > Developer options > Tick "Disable HW overlays"
Reboot may be necessary.
Unfortunately ive flashed back the gpe rom, but if no one else can do it then I guess I can try at home with CM
Apparently disabling 'HW overlays' makes no difference. I guess the only way to remove this effect is to use a Kernel that is fully compatible with the 41.18 Bootloader included with Stock Lollipop. As suggested above, we have to wait for Motorola to release Lollipop Kernel sources before DEVs can figure out a solution.
lost101 said:
Apparently disabling 'HW overlays' makes no difference. I guess the only way to remove this effect is to use a Kernel that is fully compatible with the 41.18 Bootloader included with Stock Lollipop. As suggested above, we have to wait for Motorola to release Lollipop Kernel sources before DEVs can figure out a solution.
Click to expand...
Click to collapse
Thanks for finding this out lost101 - we can expect a kernel release in early 2015 then
Hi there! First of all thank you guys for all the effort you're putting into this. I've got the same problem with the horizontal line looping down and wanted to ask if anything changed since the last post of december. I don't really like Lollipop, flashed back to 4.4.4 and am stuck with the line issue.
Thanks for any updates!
:good:
is there no update on this issue as of 18/02?
funster_ said:
is there no update on this issue as of 18/02?
Click to expand...
Click to collapse
Nothing will change until custom kernels for stock are available. Maybe then a kernel DEV can find a work around. Motorola have not yet released any kernel sources for Lollipop - which they legally have to.
lost101 said:
Nothing will change until custom kernels for stock are available. Maybe then a kernel DEV can find a work around. Motorola have not yet released any kernel sources for Lollipop - which they legally have to.
Click to expand...
Click to collapse
yeah, that was what i mean.. is there no updates about motorola releasing the source for the kernel anytime soon?
funster_ said:
yeah, that was what i mean.. is there no updates about motorola releasing the source for the kernel anytime soon?
Click to expand...
Click to collapse
After bricking my moto g by "downgrading" from Android 5.0 to 4.3, I recovered it by going to 4.4.2, but got this horizontal line issue. However, it seems to have pretty much cleared itself up. The last time it occurred, I allowed the screen to enter sleep mode, then woke it and the problem had fixed itself.
Just leave it for a while
Hey bro don't worry about a thing. I had the same issue. Just leave your phone for a while and the looping will disappear. From experience.
I got horizontal line on recovery.
I have 41.18 bootloader.
What is the problem?
Im on cm12.1 xt1033.
There is no problem on Rom though, its only on the recovery.
Here is a fix for the issue:
http://forum.xda-developers.com/moto-g/help/solution-to-moto-g-2013-tearing-t3408447
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.
Hello.
Lollipop wasn't doing it for me, so I decided to downgrade to 4.4.4 and why not, try the Cataclysm ROM.
Problem is, after installed, the middle home button is not working and even though I play with the toggles to display, I just simply have none at all.
Had to install a stock 4.4.4 although I was really looking forward to Cataclysm.
Any ideas on how to fix this?
Thanks.
(I have a Nexus 5, just in case).
That's not a Cataclysm bug. It can happen when a phone isn't wiped properly before flashing.
Wakamatsu said:
That's not a Cataclysm bug. It can happen when a phone isn't wiped properly before flashing.
Click to expand...
Click to collapse
I did a wipe. Is there anything specific needed?
Followed this video: https://www.youtube.com/watch?v=nmC4hk4_Mds
Gonna try again now, just in case. Will report back.
Dax01 said:
I did a wipe. Is there anything specific needed?
Followed this video: https://www.youtube.com/watch?v=nmC4hk4_Mds
Gonna try again now, just in case. Will report back.
Click to expand...
Click to collapse
You can't install a KK ROM on top of Lollipop. Of course you're going to have problems mixing a KK ROM with the LP kernel, bootloader, and radio. If you want to go back to KK you have to flash the 4.4.4 factory image before flashing a KK ROM. That being said, why not give Cataclysm LP a chance before completely writing LP off? It doesnt have all the features of KK yet, but atl4ntis is a soldier, he's working on implementing everything that's possible with LP.
That's because you wiped internal storage.
BirchBarlow said:
You can't install a KK ROM on top of Lollipop. Of course you're going to have problems mixing a KK ROM with the LP kernel, bootloader, and radio. If you want to go back to KK you have to flash the 4.4.4 factory image before flashing a KK ROM. That being said, why not give Cataclysm LP a chance before completely writing LP off? It doesnt have all the features of KK yet, but atl4ntis is a soldier, he's working on implementing everything that's possible with LP.
Click to expand...
Click to collapse
I''ve been giving LP a chance for the last 5 weeks. I just don't like too much about it. I'll wait for the next flavor, or at least check the CT for LP in a couple months.
Thanks for the advice, I'm wiping it as we speak.
EDIT: I think the problem was between what BirchBarlow and Wakamatsu said. I installed stock KK and wiped the cache as well, now it works wonders.
Thanks a lot.
Get Terminal Emulator and type -
SU (enter)
am start -n com.google.android.setupwizard/.SetupWizardTestActivity (enter)
Sent from my Nexus 5 using Tapatalk (the older 4.9.5 not that new 4.10 abomination they released for god knows why reason)
General Lollipop Information Thread
Since many users asking the same questions over and over again i'm going to start with many "basics" answers for you
Why? because you guys won't use the search button :silly:
Can i revert back to kitkat safely?
Yes And No, If you have upgraded the bootloader.
If you have upgraded with Bootloader you might have some IMEI issues, And afaik there is none that has fixed this. Thus who hasn't updated the booloader can still revert back.
I got no baseband or WIFI
Go to More > About Device
Scroll down until you see baseband. if you don't have HOA7 in the end that means you're wifi won't work with stock kernel
Make sure that you always read the OP and if OP hasn't stated it, you need to update your modem and NON-HLOS.bin
Make sure to uncheck auto reboot before flashing!
Battery life is terrible
Yeah ofc you haven't had the rom for more than x days so it hasn't been fully set.
Can i use CF-Auto Root
NO! People who used this also flashed update-su in recovery, however flashing CF-Auto root isn't needed and it will not work due to old binaries.
How can i root?
http://forum.xda-developers.com/galaxy-s4/general/guide-t3018625
Why does X And Y FC
because you didn't provide logcat.
Why does it takes 2x minutes for it to boot first time?
because samsung made some changes which i can't tell, i've never seen such a slow upgrading screen on lollipop neither on stock versions.
LastStandingDroid said:
General Lollipop Information Thread
Since many users asking the same questions over and over again i'm going to start with many "basics" answers for you
Why? because you guys won't use the search button :silly:
Can i revert back to kitkat safely?
Yes And No, If you have upgraded the bootloader.
If you have upgraded with Bootloader you might have some IMEI issues, And afaik there is none that has fixed this. Thus who hasn't updated the booloader can still revert back.
I got no baseband or WIFI
Go to More > About Device
Scroll down until you see baseband. if you don't have HOA7 in the end that means you're wifi won't work with stock kernel
Make sure that you always read the OP and if OP hasn't stated it, you need to update your modem and NON-HLOS.bin
Make sure to uncheck auto reboot before flashing!
Battery life is terrible
Yeah ofc you haven't had the rom for more than x days so it hasn't been fully set.
Can i use CF-Auto Root
NO! People who used this also flashed update-su in recovery, however flashing CF-Auto root isn't needed and it will not work due to old binaries.
How can i root?
http://forum.xda-developers.com/galaxy-s4/general/guide-t3018625
Why does X And Y FC
because you didn't provide logcat.
Why does it takes 2x minutes for it to boot first time?
because samsung made some changes which i can't tell, i've never seen such a slow upgrading screen on lollipop neither on stock versions.
Click to expand...
Click to collapse
Can u port soundcamp to s4 ?
i've flashed cf autoroot and it works perfectly
i did a completly downgrade,also bootloader and no issues
Sent from my GT-I9505 using XDA Free mobile app
i have installed official lollipop 5.0.1. If I root my phone, I will be able to flash official updates from samsung in the future? or I won't because of triggered knox
ViPER4Android
I managed to install Viper as system app but problem is How do I Activate it? In Sound settings there is No Music fx, (although it's installed), so I don't have the option switch Viper on, let only see Adapted Sound and in custom profile doesn't select it either. Am I missing something or is it because this update is so terrible
great info Droid! saw this thread in your signature
Revert from LL 5.0.1 to KK 4.4.2 is possible even if you flashed the Bootloader!
Personaly tested and working like charm!
No IMEI lost, no issues soo far found....
re
Is it possible to flash i9506 lollipop ROM on E330S?........... They are same hardware wise?
Xain47 said:
Is it possible to flash i9506 lollipop ROM on E330S?........... They are same hardware wise?
Click to expand...
Click to collapse
yeah..they are the same but i don t know if modems are diferent. i think you should not flash i9506 on E330s
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