Database Info

Convert to GPE and upgrade to Lollipop, how to?

I have a MotoG GPE (I buy from Google Play Store) but when I get it I convert from GPE to non GPE so I can install ROM like Cyanongen or others. Now I'll like to test new 5.0.1 via OTA since there is no factory images yet I I'll like to know which are the steps I should follow in order to do this. I have this files in my power: 4.4.2(Android) KOT49H(Build) 41.05(Bootloader) 1032.340.63.00R(Baseband), 4.4.4(Android) KTU84P(Build) 41.13(Bootloader) 1032.390.81.01P(Baseband), 5.0.1(Android) LRX21Z(Build) 41.18(Bootloader) 1032.3108.94.00R(Baseband) so should I downgrade to 4.4.2 then upgrade to 4.4.4 and then upgrade to 5.0.1? Is that the right flow? If this is is the right flow then for downgrade to 4.4.2 I should do it using this:
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Then repeat the whole process for 4.4.4 and then sideload 5.0.1 OTA update? Is that right? I have fear since I see many bricked their phones and I tried some days ago and get stuck on the Google boot logo for at least 5 min and get back to TWRP recovery for restore the previous backup was tedious almost 5 hours to get back my phone, so I need some advice from experts here. What are the right steps to update my phone and what you would say for this 5.0.1 will be good to leave a custom ROM for get into this one?

Moto G (2013) GPE 5.0.1 to Motorola´s 5.0.2

Hello guys, I´m in doubt here, and although i´ve been reading some posts, I cannot seem to understand the procedure to install Motorola´s 5.0.2 in my Moto G, actually on 5.0.1 GPE.
As far as I know, I need to wipe it off, then convert partitions to f2fs and then flash via custom recovery?
I´ve tried twice, but cannot install TWRP, will try with Phillz.
BTWy, my device is rooted and bootloader unlocked.
Thanx for any guidance you may lend me, I´m at work and cannot dwelve deep into hundreds of threads. I have already downloaded Blur_Version.210.12.40.falcon_umts.Brasil.en.BR.zip the official Motorola 5.0.2.
Thanks!!

you need the 4.4.4 firmware first and mfastboot v2 files to go back to stock motorola firmware.
and since you updated to 5.0.1 GPE, your bootloader has been updated, so when you downgrade to 4.4.4, you will see screen flickers.
Here are the commands,you must enter these commands one by one using command prompt (hold shift, and right click and choose open command window here) in the folder where the firmware files are (including the mfastboot files)
connect your phone to the computer with usb cable and type the command to go into the bootloader
adb reboot bootloader
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
and you need this firmware to be installed first before installing the lollipop update
XT1032_RETAIL-BR-SS_4.4.4_KXB21.14-L1.40_42_cid12_CFC_1FF

Thanx!
Well thank.you sir, very informative response.
Just to be super super-sure, no need to un-root or lock the bootloader right?
AgentChaos said:
you need the 4.4.4 firmware first and mfastboot v2 files to go back to stock motorola firmware.
and since you updated to 5.0.1 GPE, your bootloader has been updated, so when you downgrade to 4.4.4, you will see screen flickers.
Here are the commands,you must enter these commands one by one using command prompt (hold shift, and right click and choose open command window here) in the folder where the firmware files are (including the mfastboot files)
connect your phone to the computer with usb cable and type the command to go into the bootloader
adb reboot bootloader
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
and you need this firmware to be installed first before installing the lollipop update
XT1032_RETAIL-BR-SS_4.4.4_KXB21.14-L1.40_42_cid12_CFC_1FF
Click to expand...
Click to collapse

Hello guys I would like to do the same, I have the Gpe and install Motorola 5.0.2, but before I want to know how to fix the flicker screen, I don't get it using android but when I'm on twrp, it's annoying, do you have any idea how to fix it?
Sent from my XT1058 using XDA Premium 4 mobile app

nice!
So i´ve flashed 5.0.2, with the method described here, it was *too* easy.
I did not, how ever, get the flickering screen bug...
So thanks again. and this is a safe way to go from gpe 5.0.1 to moto 5.0.2.

donlloreda said:
So i´ve flashed 5.0.2, with the method described here, it was *too* easy.
I did not, how ever, get the flickering screen bug...
So thanks again. and this is a safe way to go from gpe 5.0.1 to moto 5.0.2.
Click to expand...
Click to collapse
Which recovery do you have?

antarix said:
Which recovery do you have?
Click to expand...
Click to collapse
Stock recovery mate, well my happy story has come to a misterious error I cannot by any means sort out..
please see this post: Weird issue

[Solved] Stuck at bootlogo no matter what rom I flash

Hi everyone,
I follow this awesome forum for several years now. Unfortunately, I currently have a problem which I do not get solved on my own and hope for your support:
My xt1032 (non GPE, non LTE) is stuck at bootlogo no matter what rom I flash! :crying:
Background:
Some time ago I successfully converted my device to the GPE edition using MotoTool. After Lollipop was finalized and penetrated me to update, I did him the favor. As some apps were no longer compatible, I restored my nandroid backup and lived with the ongoing update message.
Now that I leave the device to my wife, I'm trying to flash a factory image of desirably 5.1 GPE.
First I tried to flash GPE_5.1_XT1032_LMY47M.M001_CFC.xml.zip using fastboot:
Code:
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe reboot
... stuck in Google bootlogo.
Then I tried to flash XT1032_FALCON-RETEU_5.0.2_LXB22.46-28.1_1_cid7_CFC_1FF.xml.zip also using fastboot:
Code:
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe reboot
.. stuck in Motorola unlocked bootloader warning.
I also tried to flash GPE_XT1032_KTU84P.M003_CFC.xml.zip again using fastboot:
Code:
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe reboot
.. stuck in Google bootlogo again.
I even tried to 'convert to GPE' in MotoTool as I did before using the same image as it was then. Unfortunately with the same result...
I'm a bit desperate right now! My research into threads with similar problems have led to no result. Solutions like flashing gptfix.bin didn't to the trick. What am I doing wrong? Can anyone point me to the right direction please?
Thanks in advance!
*nikon

*push*
I tried this and that in the meantime... all I get are bootscreens in multiple versions. After all I still have fastboot access.
My wife is getting nervous and so am I! Do I have a brick now?
Thanks in advance!
*nikon

I'm gonna make an educated guess its probably formation the GPE-rom uses ext4 in /data and the motorala uses F2FS (those are linux file-systems). GPE doesn't work with F2FS and Moto doesn't work with EXT4.
And assuming you use the TWRP as your recovery? If not install it with Mototools or fastboot to recover your phone (I'm not 100% sure if this is the only method but is the only method I can think of).
Step 1) Download the right recovery from this thread. If you want GPE-rom download GPE otherwise download falcon. Instructions are given in this thread.
Step 2) Start your recovery via fastboot and than choose recovery (use sound button down to scroll, up to select). If everything is allright your booting to a recovery menu with touchbuttons.
Step 3) Choose wipe -->> Advanced wipe -->> select data -->> Repair or Change File System -->> Choose F2FS or Ext4 depending on your choose for moto (F2FS) or an GPE rom. (Ext4). Repeat this steps for /system and /cache.
Step 4) Do a factory reset just to be sure (not sure if necessary, better safe than sorry)
Step 5) Flash your rom of choose
Step 6) Report back to me when succeeded if not report back with more information.
I like this thread its friendly and much information is given and your seem very polite (Learn from this man you screamy panicking kids). There is how ever some essential information missing.
-Which recovery did you use?
-What is your bootloader version?
-From which rom are you coming?
P.s. I never used Fastboot to flash an complete rom only for recovery's (except for my oldskool G1, but that was long ago). I like flashing via recovery most roms are tested and made for flashing via TWRP or CWMR (mostly specified from dev).
P.s.s. I tried my best English! Its not my first language.

@*nikon - provide a fastboot log of the entire flashing process. I want to see any message fastboot is presenting.
Also, you do not need to change the format of /data manually - flashing the gpt.bin does that automatically.
EDIT: Using TWRP to flash a custom ROM is much safer than flashing fastboot images. A flashable GPE 5.1 ROM is available here: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510

Shortly beforehand: thanks a lot for your responses! Very nice to have some feedback!
After being quite busy this weekend, I now have the time to dig into this again.
@Xacky: My apologies for the missing information.
I've tried different recoveries, mainly stock recovery or TWRP depending on my current flash try. Thank you that you have pointed out to me on the recovery thread where I became aware of the GPE edition of TWRP. I'll take this one in the future if I get this hopefully running sometime.
My current bootloader version is 41.18 because last time I tried to downgrade again to 4.4.4. But I also had version 41.19 running with my Lollipop tries.
Concerning the rom I was coming from, I thought my description was relatively detailed. The original was a (NON-GPE) Moto rom, upgraded to 4.4.4 GPE by Moto Tool, then OTA upgraded some time to 5.0.1, downgraded by naindroid backup restore and then tried to flash a 5.1 GPE factory image via fastboot. Then the journey began...
@lost101: Thanks for the information that the format is no issue since it is defined by gpt.bin. I'll give the images from your thread a try and get back in when my battery is ready for flashing again. I also try to save a log which I can post here, if necessary by hand.
Greetz
*nikon

I'm back with good news! :victory:
Unfortunately I still don't know what the problem was (and I really can't stand this!!), but it seems to be solved. I successfully managed to downgrade to 4.4.4 with the image from this thread and then I was able to flash GPE 5.1 as stated in this tutorial.
Afterall kind of weird because I am firm conviction that I've not done anything else manually in the beginning.
Nonetheless, thanks for listening!
Greetz
*nikon

Hey Nikon,
I'm running into the same issue as you. My only question is: is there still screen flickering once you've updated to 5.1? thx

Hey pables69,
sry for beeing late - I was quiet busy the last few days.
To answer your question:
No, fortunately screen flickering is also gone since the upgrade! :good:
Greetz
*nikon

Soft bricked Moto G and random reboots

I know the title is a bit confusing, but I will try to explain the context of my situation so you can understand it better.
I have a x1032 since the end of 2013. When the first image of the Google Play Edition went "public", I converted my device to it, and it stayed that way, doing all the OTA updates, until the 5.1 GPE appear.
When I did the update to this version (5.1 GPE), my compass didn't work with some apps (for example, GPS tools and c:geo), and as it is a sensor that I use most of the time, I decided do revert my device from fastboot to the 4.4 “stock Motorola” (don’t remembre if it was 4.4.2 or 4.4.4) and then update it to the 5.0.2.
In the process, I think that I had a soft brick: when I turned on the device, he stayed in the “unlocked bootloader” image, and he didn’t move forward. But, after trying, I saw that I had access to the bootloader menu and to the recovery, without any problem. I tryed to install the images via fastboot, even the new 5.1 GPE and 5.02 Motorola ones, but none of them works.
I searched, and searched, and finally understand that in this cases, the problema is the /system, /data and /cache partitions that need to be formated, and then I can flash any zip rom via recovery.
And now, this is where I stay: Via fastboot I installed the 5.1 GPE rom. Then I installed philz touch recovery, formated all partitions in ext4, wipe them all (just to be sure ), and did an adb push to have the GPE 5.1 zip ROM from @lost101 in my sdcard, and installed it. AND IT WORKS!
Now, the actual problem: I’m having form time to time some random reboots. They always appear after I try to turn the screen on, and after 3 or 4 seconds, the phone reboot.
Can this be related to the softbrick? I tought it could be a rom problem, but no one else have the same complains and @lost101 says that maybe this is from my phone.
Thanks in advance, and sorry for the long text and my bad english.

I suggest you try flashing the GPE 5.1 Firmware Image available here: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Make sure you use only the following commands and use mfastboot available here: https://www.androidfilehost.com/?fid=23578570567719065
mfastboot flash partition gpt.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot​
You should not need to manually format partitions. The above commands will do everything for you. The reason for your sensor issues are that the fastboot flashing previous was not successful.
Please do the fastboot commands manually, one at a time, and log everything and post it here.

lost101 said:
I suggest you try flashing the GPE 5.1 Firmware Image available here: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Make sure you use only the following commands and use mfastboot available here: https://www.androidfilehost.com/?fid=23578570567719065
mfastboot flash partition gpt.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot​
You should not need to manually format partitions. The above commands will do everything for you. The reason for your sensor issues are that the fastboot flashing previous was not successful.
Please do the fastboot commands manually, one at a time, and log everything and post it here.
Click to expand...
Click to collapse
You are absolutely right: there were no errors (except the "normal" validation erros because it's a GPE image), and in the end, I didn't need to format the partitions manualy.
I think the problem was the fastboot (I was using the one from the sdk... my bad!).
Now I know that any problems don't come from the software side, because in that part, everthing is ok.
I will just ask you two more things:
- What custom recovery do you recomend?
- Your Low Memory Killer Tweak works without any problem in the 5.1 GPE installed via fastboot?
Thank you very much for your help. You really made my day.

RBras said:
I will just ask you two more things:
- What custom recovery do you recomend?
- Your Low Memory Killer Tweak works without any problem in the 5.1 GPE installed via fastboot?
Click to expand...
Click to collapse
Latest TWRP. Yes, the LMK Tweak will work in that case.

lost101 said:
I suggest you try flashing the GPE 5.1 Firmware Image available here: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Make sure you use only the following commands and use mfastboot available here: https://www.androidfilehost.com/?fid=23578570567719065
mfastboot flash partition gpt.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot​
You should not need to manually format partitions. The above commands will do everything for you. The reason for your sensor issues are that the fastboot flashing previous was not successful.
Please do the fastboot commands manually, one at a time, and log everything and post it here.
Click to expand...
Click to collapse
Unfortunately, random reboots are still present
I have installed 5.1 Google Play edition factory image, with the mfastboot you told me, but it still reboots randomly. Did the same with the 5.02 EU from Motorola, and it behaves the same way.
The random reboots happen more or less, one time a day, and it's when I try to turn the screen on, it doesen't respond, and after 3 or 4 seconds, the system reboots.
Any clue of what can be? Is there a way to grab some logs to try to understand what's happening, or it is too difficult and it's better I don't have too many hopes?

It would appear some sort of corruption has occured. I can't say anything with certainty - but I do believe Bootloader corruption could cause what you are experiencing.
It's possible you could fix this by reflashing the Lollipop Bootloader. I did not include the fastboot command to do this above.
Here it is: mfastboot flash motoboot motoboot.img
Try that and report back.

lost101 said:
It would appear some sort of corruption has occured. I can't say anything with certainty - but I do believe Bootloader corruption could cause what you are experiencing.
It's possible you could fix this by reflashing the Lollipop Bootloader. I did not include the fastboot command to do this above.
Here it is: mfastboot flash motoboot motoboot.img
Try that and report back.
Click to expand...
Click to collapse
During my time with Moto G, I flashed it using fastboot, dozens of times, but I was so desperate in the other day that I didn't even notice that your list with commands didn't have the bootloader one.
Now I undestand why the bootloader I have is the one from 5.1 GPE.
I'm gonna try it. In the last 2 days I didn't have any random reboot, but I will take my risk and flash the bootloader from the 5.0.2 EU, and I will report back in the next days.
I'm buying you a beer today, for being so helpful and nice. Thank you very much.

I'm reopening this thread to try to see what's happening with my phone.
So, after flashing the bootloader of the 5.1 GPE, the phone was really better than it was in the OP.
My Moto G didn't reboot anymore when I tryed to turn the screen on, but instead, it started to reboot randomly every 2 or 3 weeks, without needing to touch the phone (the phone was rebooting by itself).
In the last month or so, I'm using the XT1032 Retail EU 5.1 (Optimized) v1.0 from @lost101, and now the behavior is, once again, the described in the OP: I try to turn the screen on, the phone doesen't respond, and after 3 or 4 seconds, it reboots by itself.
And this is happening once every 1 or 2 weeks.
So, can anyone give me some help to try to understand what's happening? @lost101 @luca020400 @LuK1337 @matmutant
Usually, I have the original firmwares from Motorola or GPE, or I can have the optimized versions from @lost101 with TWRP.
Thanks for your help, guys!

Just for the record, I get occasional sudden / unexpected power off. It's rare, but stuff can happen when you are dealing with a complex device such as a smart phone. This is especially so, if you are rooting / modifying the operating system.
The problem could be related to something you are installing. Also, I recommend a clean install once every few months.

[Q] XT 1039 from O2 Store in August - Reboot Loop, android with spinning cogs.

Good Afternoon all at XDA,
Hoping that somebody here will be able to help me. In december I unlocked my bootloader using some instructions found on your website.
This allowed me to install some apps that weren't available via google play and this worked great.
However, I finally got tired of not being able to use Online Banking apps with my unlocked bootloader, so decided to revert to the factory moto g image which I backed up before unlocking.
This left me stuck in a reboot loop. between the unlocked bootloader warning and an android with spinning metal cogs in its chest.
I tried some other images, found on this site, but was left either in a reboot loop, or with the Moto logo, and the phone occasionally emitting a vibrate every couple of seconds.
I have tried loading the images using the built in Motorola recovery and/or clockworkmod recovery.
The outcome has been the same or similar either a reboot loop or stuck on moto logo occasionally chirping the vibrate.
I feel like XT1039 is not the full model number of my phone, or that I'm missing something else.
Please could someone shed some light on which Rom I should be using, and a step by step of how to get my phone back to life.
Many Thanks
Vinny

This is the firmware you need to download: http://www.filefactory.com/file/7df...S_4.4.4_KXB21.14-L1.56-1_cid7_CFC_1FF.xml.zip
Then follow this guide: http://forum.xda-developers.com/showthread.php?t=2542219
You need to perform the pre-requisites and steps 1,2,3b (This will restore to fully stock and delete any data you have on the phone)
In step 3b enter the following commands instead of the ones in the guide:
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Good luck!