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
Related
I mean, i uptaded my moto g to Lollipop. But i didnt like it so much, so i've downgrade the phone to kk. But my device doesnt reboot anymore. It got stucked on 'Warning bootloader unlocked' screen. Tried restoring so much firmwares, roms, etc, no solutions.
How can i revive my phone? Hope you understand my fking english.
aybarchu said:
I mean, i uptaded my moto g to Lollipop. But i didnt like it so much, so i've downgrade the phone to kk. But my device doesnt reboot anymore. It got stucked on 'Warning bootloader unlocked' screen. Tried restoring so much firmwares, roms, etc, no solutions.
How can i revive my phone? Hope you understand my fking english.
Click to expand...
Click to collapse
I think the only way to revive is to go back to lollipop
OldYellowBricks said:
I think the only way to revive is to go back to lollipop
Click to expand...
Click to collapse
Cant. Tried flashing again dual sim br and then the ota but i get ' Installation aborted ' everytime.....
It sounds like your Bootloader has been updated so you can no longer boot the KitKat kernel. Can you please state what version your Bootloader is now?
For example mine is: 41.13
This weekend I will try to build a Stock ROM based on Retail DS BR Lolliopop. That should get your phone back, as long as you have a custom Recovery installed.
Perhaps you could try to flash the full latest 4.4.4 Brazil rom; the OTA update to Lollipop might work on this one. Just not sure if it is safe to revert to an older bootloader on Moto G, never tried this myself.
If this doesn´t work or you don´t want to try, you will need someone to upload a full 5.0 ROM and look for a backup phone until then
My bootloader ver. is 41.18
i've tried reflashing br dual sim version and then the 5.0 ota. But it doesnt work.
Instructions: http://forum.xda-developers.com/showthread.php?p=57297928
lost101 said:
Instructions: http://forum.xda-developers.com/showthread.php?p=57297928
Click to expand...
Click to collapse
Doesnt work that instructions. Tried every known method
lost101 said:
Instructions: http://forum.xda-developers.com/showthread.php?p=57297928
Click to expand...
Click to collapse
Follow the instructions here http://forum.xda-developers.com/mot...33-ota-5-0-lollipop-brazilian-t2963565/page47 by @AgentChaos
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.
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.
I have reflashed(clean install= wiped data/cache/system) 5.0.2 Asian lollipop stock rom,which doesnt upgrade bootloader i.e im on kitkat bootloader. after flashing, i lost root access and i'm on stock recovery. And Now I got 5.1 OTA, can i install it or not? Because while turning on my device, i get custom image first and then motorola animation,i get this custom image because i have made it by moto g boot logo creator + flasher.
[TIA]
pagadalachetan said:
I have reflashed(clean install= wiped data/cache/system) 5.0.2 Asian lollipop stock rom,which doesnt upgrade bootloader i.e im on kitkat bootloader. after flashing, i lost root access and i'm on stock recovery. And Now I got 5.1 OTA, can i install it or not? Because while turning on my device, i get custom image first and then motorola animation,i get this custom image because i have made it by moto g boot logo creator + flasher.
[TIA]
Click to expand...
Click to collapse
Yes you can flash the OTA update without any issues. Considering your bootloader is 41.18 you wont be having any trouble and obviously since you clean flashed 5.0.2 surely your bootloader must have updated itself automatically
thuva06 said:
Yes you can flash the OTA update without any issues. Considering your bootloader is 41.18 you wont be having any trouble and obviously since you clean flashed 5.0.2 surely your bootloader must have updated itself automatically
Click to expand...
Click to collapse
Thanks thuva... My bootloader version is 41.08 I.e KitKat bootloader
I wanna Downgrade back to Stock 5.1 but my question is, do I have any problems with bootloader, flickering or OTA's if I downgrade from 6.0.1 CM13 to 5.1 Pure Stock?
And should I think about something before I downgrade?
Push
You can do it through MFastboot method, and you won't have any problem at all. Just download right version for your region and you're done.
razor001_ said:
You can do it through MFastboot method, and you won't have any problem at all. Just download right version for your region and you're done.
Click to expand...
Click to collapse
I got a flashable zip?
can i flash it or do i need to use the mfastboot method?
It will be fine with that flashable ZIP... it's just like another ROM. I told you MFastboot method because that way you're making sure that everything is stock and not Modified.
razor001_ said:
It will be fine with that flashable ZIP... it's just like another ROM. I told you MFastboot method because that way you're making sure that everything is stock and not Modified.
Click to expand...
Click to collapse
Is a factory reset/ all wipe not enough to flash it normaly?
or why mfastboot?
Well, If you want everything Stock then you must do it through MFastboot method. with the ZIP that you have it will be a stock ROM; but your Recovery and Bootlogo still are modded (Recovery will be CWM or TWRP, and your bootlogo stays the same you have right now, not the warning you get when you unlock the Bootloader)
Edit: both ways to do it are fine... Just different results at the end.
razor001_ said:
Well, If you want everything Stock then you must do it through MFastboot method. with the ZIP that you have it will be a stock ROM; but your Recovery and Bootlogo still are modded (Recovery will be CWM or TWRP, and your bootlogo stays the same you have right now, not the warning you get when you unlock the Bootloader)
Edit: both ways to do it are fine... Just different results at the end.
Click to expand...
Click to collapse
So what are the results if I only flash it instead of mfastboot?
Flash Zip: Stock ROM, modified recovery, and if in the past you flashed a bootlogo it will stay the same. (If in the future you want to flash again CM or any other ROM this is the best)
Mfastboot: Stock ROM, stock recovery, and stock bootlogo (the one with the warning of unlocked bootloader) (if in the future you want to flash again CM or other ROM you'll have to flash the recovery first and then flash your ROM)
Sent from my Moto G using XDA Labs
razor001_ said:
Flash Zip: Stock ROM, modified recovery, and if in the past you flashed a bootlogo it will stay the same. (If in the future you want to flash again CM or any other ROM this is the best)
Mfastboot: Stock ROM, stock recovery, and stock bootlogo (the one with the warning of unlocked bootloader) (if in the future you want to flash again CM or other ROM you'll have to flash the recovery first and then flash your ROM)
Sent from my Moto G using XDA Labs
Click to expand...
Click to collapse
Okay thx for the Info
But my phone will not get bricked or flickering because of bootloader?
I know it gets bricked if I go from MM to KK.
It won't... Flicker happens because some kernel implementations changed from KitKat to Lollipop. And the bricked devices were because people tried to flash KitKat bootloader (motoboot.bin) and partition table (gpt.bin or something like that) on top of Lollipop.
But as our Moto G 1st gen didn't get past Official Lollipop there isn't a new bootloader version released. And CM13 is implemented over the same Lollipop bootloader. So don't worry about bricking your device if you wanna downgrade to Stock Lollipop.
Sent from my Moto G using XDA Labs
razor001_ said:
It won't... Flicker happens because some kernel implementations changed from KitKat to Lollipop. And the bricked devices were because people tried to flash KitKat bootloader (motoboot.bin) and partition table (gpt.bin or something like that) on top of Lollipop.
But as our Moto G 1st gen didn't get past Official Lollipop there isn't a new bootloader version released. And CM13 is implemented over the same Lollipop bootloader. So don't worry about bricking your device if you wanna downgrade to Stock Lollipop.
Sent from my Moto G using XDA Labs
Click to expand...
Click to collapse
Okay Thanks
I think not brick