My XT1032 was on GPE 5.0.1 and decided to flash official CM12
I tried to flash but it wont worked (maybe because of the small /system partition idk) so i flashed via Fastboot the 5.0.1 Moto GPT and i was able to flash it
But now i get a weird line on my screen which goes from top to the bottom every boot like in TWRP on 41.18 (5.0.1) Bootloader which only disappear until the next restart when i lock the screen
Is there any solution to remove it permanent or will that happen forever also for next (stock-)roms?
Im a bit confused :/
This is due to Kernel and Bootloader incompatibility. New custom kernels need to be created to take into account the new Lollipop bootloader. When and if this ever happens depends on the kernel developers. The only solution at the moment is to return to Stock Android Lollipop, either GPE or Retail Brazil / Asia.
Related
Hi there,
I have had a long search through both Q&A and the General forum but I can't seem to find the answer I am looking for.
I converted my stock XT1032 to a GPE and then OTA flashed the 5.0.2 update onto it (not via a sideload but via the OTA updater in settings). I found that then trying to install TWRP recovery via fastboot (both 2.8.1.0 and 2.8.4.0) I could access the recovery once I had installed it but there was a wavy line passing through the screen from the top to the bottom and when I restarted the device to try to get back to recovery I could only get the stock one.
I am unsure about the safety of flashing a new ROM onto this recovery due to this.
I think there may be a problem with the gpt.bin file as I had to flash this fix when I updated the 4.4.4 GPE to 5.0.2 (http://forum.xda-developers.com/showpost.php?p=57444986&postcount=1) to get past the Google logo.
I was wondering if anyone has experienced the same problem? I am on the 41.18 bootloader if that helps.
I would really like to be able to flash cyanogenmod onto my device (I just love CM it's so much better than stock IMO) and some advice would be much appreciated.
Many thanks.
Hi all,
About a month ago or so I updated my Moto G 2013 from 4.4.4 GPE to 5.0.1 GPE.
Then I rooted it using Chainfire Autoroot.
What I didn't know back then was that CF auto root screws your stock recovery.. (with all due respect to this great developer)
Auto root also prevents my from installing custom recoveries. (They just won't work).
I faced the same problem on my Nexus 7 2013. That problem could easily be solved by flashing again stock ROM image.
But since there is no 5.0.1 GPE image available for the Moto G it seems impossible to fix this..
Unluckily, Motorola doesn't allow us to downgrade to KitKat or Jelly Bean. (Yes.. I know there are ways to downgrade by skipping some commands, but there are several reports that it will cause screen flickering because the new Lollipop bootloader doesn't work properly on stock Kitkat ROM.)
So I guess I'm pretty stuck right know.
I guess factory resetting my phone would already hard brick the phone (because of the bricked stock recovery by cf auto root)
I would like to have Lollipop 5.0.1 GPE with TWRP recovery, so I can install custom kernels etc.
Do I have to wait for the Lollipop image? Or are there other ways of reaching my goal?
Any idea when we can expect the image to be released?
Thanks in advance!
I installed stock KK on a my Telus moto g with the L bootloader and the flickering was still be there. Just don't flash the motoboot.img file in fastboot.
I always found that the easiest way to get root is to flash supersu from a custom recovery.
Hello forum, basically, when I got my moto G, it was on 4.3, so I did all the bits, and the step i did after all the rooting unlocking etc was upgraded my bootloader to the lollipop one (ending in 8 i believe) - which i wish i didnt do, and cant downgrade to 4.4.4 (or can I without bricking)......right back to the story.......the problem now is, whenever i try uninstalling apps, or wiping data in any app etc, my phone does a reboot, I installed the brazillian 5.0.2 flashable rom (the optimised one) which worked perfectly, did all the correct wipes etc, but it reboots when uninstalling apps......, and thought i would try dirty unicorns....works well except the rebooting problem...... help....what can I do????????
I read somewhere that maybe to solve it, you gotta change runtime from dalvik to ART, but there is no option to change this....
There are no 5.0.2 uk images available that i have read (so i cant completely get back to complete factory settings)
I really wished i kept the KK bootloader!!!! so who can help me????? I want to try some of the great CM11 builds!!!
Since your bootloader is unlocked and you have the lollipop bootloader, I suggest flashing the stock 4.4.4 (not 4.4.2) ROM for your xt1032 (you will not be able to flash the motoboot file so don't bother trying), upgrade the Motorola apps via Play store, and take the 5.02 OTA update.
FInd your stock ROM here: http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=filename&order=ASC&show=100&page=1
audit13 said:
Since your bootloader is unlocked and you have the lollipop bootloader, I suggest flashing the stock 4.4.4 (not 4.4.2) ROM for your xt1032 (you will not be able to flash the motoboot file so don't bother trying), upgrade the Motorola apps via Play store, and take the 5.02 OTA update.
FInd your stock ROM here: http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=filename&order=ASC&show=100&page=1
Click to expand...
Click to collapse
do i have to update to 5.0.2 again? as i want to try cm11 again
@audit13 is this a flashable zip, or do you need to do it via fastboot? as its got a bootloader included in the zip (4.4.4 kitkat bootloader)
The files from filefactory need to be unzipped and flashed via fastboot or mfastboot.
You do not need to do anything with the stock ROM if you want to install a custom ROM. All you need to do is install a compatible custom recovery and a custom ROM. I suggest flashing right to the latest CM12 rather than using CM11.
I suggested flashing back to the stock for your phone and upgrading to 5.02 via OTA to see if the uninstall problem goes away.
yep understood @audit13 read your other posts on this matter too, the reason I want to use a cm11 rom, is I had a moto g about 8-9 months ago, and there was a rom i loved, and it was cm11 based......will i brick if i do flash this cm11 rom? i know about flickering bug, and possible hard brick if i went back to versions below 4.4.4 ...... and i love cyanogenmod roms, as i dont get irritating moto updates etc
Flashing CM11 should not be a problem as CM11 ROMs do not touch the bootloader or modem.
so basically, downgrade to the 4.4.4 firmware file, and cm11 and im done? yeah?
You can try to flash cm11 directly over stock 5.02. If it doesn't work, you may have to flash back to stock 4.4.4, install recovery, and then flash cm11.
Hey guys, so I've unlocked the bootloader, flashed TWRP 2.8.6.0, got a rom, kernel and some minimal gapps.
I found out that flashing any CM12 rom directly will bootloop on the moto G. So I flashed a CM11 snapshot build (M6), but now the screen has a flicker, sort of an analog, old TV flicker that goes up and down, distorting the image.
I've also found out that in order to fix that you have to flash stock 5.0.2. Since it's a xt1032 that came with KITKAT 4.4.2, I thought that flashing this would fix it, but gives me an error.
Therefore, what is the adequate way to flash a stock 5.0.2 rom in order to upgrade the rom, bootloader and modem? Can they be done separately? I figure that's what's missing in order to fix the flickering.
Thank you.
Choristav said:
Hey guys, so I've unlocked the bootloader, flashed TWRP 2.8.6.0, got a rom, kernel and some minimal gapps.
I found out that flashing any CM12 rom directly will bootloop on the moto G. So I flashed a CM11 snapshot build (M6), but now the screen has a flicker, sort of an analog, old TV flicker that goes up and down, distorting the image.
I've also found out that in order to fix that you have to flash stock 5.0.2. Since it's a xt1032 that came with KITKAT 4.4.2, I thought that flashing this would fix it, but gives me an error.
Therefore, what is the adequate way to flash a stock 5.0.2 rom in order to upgrade the rom, bootloader and modem? Can they be done separately? I figure that's what's missing in order to fix the flickering.
Thank you.
Click to expand...
Click to collapse
First tell me your bootloader version
And you don't need to flash stock lollipop to correct the screen flicker issue you just need the updated bootloader
sjandroiddeveloper said:
First tell me your bootloader version
And you don't need to flash stock lollipop to correct the screen flicker issue you just need the updated bootloader
Click to expand...
Click to collapse
How can I find the bootloader version exactly? The device came with kitkat 4.4.2, so I guess it's that!
Choristav said:
How can I find the bootloader version exactly? The device came with kitkat 4.4.2, so I guess it's that!
Click to expand...
Click to collapse
Boot into bootloader and see there it should be like 41.xx
Is it possible to downgrade the bootloader for my moto g from lollipop to a KitKat compatible version?
The mobile radio active bug is draining my battery quite badly and I want to go back to KitKat to get rid of it.
I'm on the using the XT1032
It's completely unnecessary to even touch the Bootloader. Every time you do anything with it, you risk destroying your phone.
Simply flash the Factory Firmware Image from here: (excluding the command to flash motoboot.img (Bootloader))
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Or flash one of these zips via Custom Recovery (TWRP):
http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688