Right guys firstly i would like to make a massive shoutout to @fl4m3y
Brilliant work on your efforts for the community!!
Without his guide found HERE i would never have been able to leave any 4.4.4 custom rom!
Thankyou friend.
Disclaimer
I am not 100% this will work for you. Use at YOUR OWN RISK.
I will not be held responsible for anyone saying, "omg, my phone had a chance of coming back to life, now your guide has killed it off"
Because that wasn't and isn't the case for me. It has worked 100% STOCK flash by FASTBOOT
95% of this is @fl4m3y credits all thanks go to this guy. Nor will @fl4m3y be blamed as he has stated in his thread. .​Right i will tell you what i did.. everything i did, dont do anything i didnt do. or it probley wont work. same goes for skipping things out.
Firstly
I need you to follow this Guide.
Troubleshooting: (These are some errors i came across, managed to fix them these ways)
The CWM Backup won't push to /sdcard
This happened to me, i don't know why but i managed to fix this by going into 'Mounts and Storage and Mounting STORAGE'
it was unmounted for some reason. Double check this..
It wont start restoring i get MD5 sumcheck failed error.
You need to go into Advance settings in Backup and Restore and uncheck 'check md5sum' (Not sure what it was called just look for something to do with md5sum and make sure there isnt a x next to it)
I Get a Error Resoring /data or /system
go into Backup and Restore and select to do a Custom Restore. Now just as if you where fastboot flashing something, restore each of them speratly..
i started from the top. (Boot.img i think it was then selected to restore and them moved down the list)
now there should be 3 parts to all of them. i went through every single one just to make sure it went well.
so in system there was 3 diffrent files relating to system .. restore them all then move on..
Once you have followed this and your phone has rebooted Sucsessfully you need to download this Official 4.2.2 GPE Fastboot Firmware
Now this is a OFFICIALLY SIGNED FASTBOOT FIRMWARE.. i think thats why it has worked.
The Thread is HERE if you want to look where i found it
Now you need the fastboot files. If you dont have the here they are
I would download them anyways just to make sure its followed exactly how i did it.
I downloaded everything to my Desktop and extracted to my desktop. it makes it easy for me to organise.
Now put your phone into bootloader
Heres for the next part. Extract the Fastboot files into the folder with the Firmware files. There is a .bat file inside that autoflashes everything
Do not press it! We dont need all the files flashed!
Ok so i need you to go to the folder with the firmware in and: Press and hold Right Shift and right click on the file and select to open cmd window here.
Now Type: Fastboot Devices
this is just checking everything is working.
Copy each of these and paste them into your cmd window
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
fastboot erase userdata
fastboot reboot
Your phone should Reboot with 100% STOCK GPE.
i am going to try fastboot flash over this a UK Retail Firmware and see what happens.. i will report back if we can now sucsefully flash firmwares other then this one.
@gd91
Confirmed working
Nop its not working for me...I am stuck at google logo...but my moto is xt1033 maybe that is why its not working? ;P
Oh, maybe does everything flash okay?
Sent from my Moto G using XDA Premium 4 mobile app
Yeah everything flashed okay except those warnings that are allways there...restoring backup went well too thx to your guide on how to avoid those mount problems
Guys, can i use this guide to downgrade from GPE 4.4.4 to GPE 4.4.2 and then to stock 4.4.2 ?
No. You will have to wait for 4.4.4 stock partition. And boot loader. Its being pushed out now or soon.. Then you can flash over GPE to stock. This only putbstock GPE back on my phone
Sent from my Moto G using XDA Premium 4 mobile app
Clarkiieh said:
No. You will have to wait for 4.4.4 stock partition. And boot loader. Its being pushed out now or soon.. Then you can flash over GPE to stock
Click to expand...
Click to collapse
People keep saying this, but nobody explains the rationality behind it.
2 things:
1) How does having the 4.4.4 GPE files help in any way with downgrading? If I downgrade, I'd want to downgrade all components, including the bootloader, no? Are you thinking that it is impossible to downgrade the GPT and bootloader after they have been upgraded, even if your bootloader is unlocked, so you would flash the 4.4.4 versions of those but the system partition and modem/baseband from whatever version you want to downgrade to?
2) Even if what you are saying is true, that you would need the 4.4.4 GPT and bootloader in order to perform a successful downgrade to an earlier version, the fact is that the gpt and motoboot files are already available today, extractable from the OTA zip that has been making the rounds. They have already been extracted by others and posted elsewhere. So what more do you need/want out of the 4.4.4 fastboot-flashable release?
-- Nathan
You have miss understood.. We can downgrade to 4.4.2 GPE ( i don't think It was shipped with Jelly Bean) its a dodle
Although!
People who dont want to be on GPE 4.4.2 or 4.4.3 or 4.4.4, and want to go back to the Motorola Stock 4.4.2 will have to wait for the 4.4.4 Stock Motorola update to come to their region ATM it is only hitting certain areas for the time being..
Sent from my Moto G using XDA Premium 4 mobile app
The process will go like this..
Flash GPE 4.4.4 then flash over that the morotorola stock 4.4.4
Sent from my Moto G using XDA Premium 4 mobile app
Clarkiieh said:
You have miss understood.. We can downgrade to 4.4.2 GPE
Click to expand...
Click to collapse
Ah, okay, yes, I guess I did partially misunderstand. But I have been seeing people talk about the problems they have been having downgrading even to 4.4.2 GPE from 4.4.4 GPE. I see that people have stumbled across various convoluted workarounds, but for some reason it is not just as easy as reflashing all of the necessary files while in fastboot. I suspect that the fact that this doesn't work even when trying to go back to 4.4.2 GPE is related to the problems people are having when trying to return to 4.4.2 Motorola.
Clarkiieh said:
People who dont want to be on GPE 4.4.2 or 4.4.3 or 4.4.4, and want to go back to the Motorola Stock 4.4.2 will have to wait for the 4.4.4 Stock Motorola update to come to their region
Click to expand...
Click to collapse
Well, then I still don't understand. If you are running 4.4.4 GPE, why do you have to first flash to 4.4.4 Motorola before downgrading to 4.4.2 Motorola? If you can't go directly to 4.4.2 Motorola from 4.4.4 GPE, what makes you think that having access to 4.4.4 Motorola would make this procedure work? I guess that's the part that is missing for me. Nobody is explaining why they believe that having access to 4.4.4 Motorola will assist in a downgrade to older versions of stock Motorola.
Clarkiieh said:
The process will go like this..Flash GPE 4.4.4 then flash over that the morotorola stock 4.4.4
Click to expand...
Click to collapse
...and then flash 4.4.2 stock Motorola over 4.4.4? Why will that work if flashing directly from 4.4.4 GPE wouldn't?
-- Nathan
GPE and Motorola have totally different file systems.. I dunno.. Its all confusing I haven't really been told myself but just buy reading what others have said and what has worked for me, I cannot flash 4.4.2 over my GPE 4.4.2 that has been brick recovered I need the 4.4.4 boot and gpt.. I think when you convert to 4.4.4 there are files and partitions you cannot flash over unless you have the whole thing. I think the big issue isnt partitions it's the bootloader, I cannot flash any other but 4.4.4 I don't know why eve after flashing 4.4.4 gpt.bin
Sent from my Moto G using XDA Premium 4 mobile app
GPE edition mean only single sim working???
sanads said:
GPE edition mean only single sim working???
Click to expand...
Click to collapse
Yes there is only single sim variant of moto g gpe edition as I know of...
Yes but there are new way people have found
Sent from my Moto G using XDA Premium 4 mobile app
Related
So , i updated my moto g xt1033 to lollipop brazilian soak test , and i'm having problems with it , now i want KitKat back , but i noted some people hard bricked his phones , and i checked my twrp and i have a backup of ALL before update , can i restore it or it will hard brick my phone? [ Bad english cuz i'm brazilian xD ]
Sent from my XT1033 using XDA Premium 4 mobile app
lucas_silva2k said:
So , i updated my moto g xt1033 to lollipop brazilian soak test , and i'm having problems with it , now i want KitKat back , but i noted some people hard bricked his phones , and i checked my twrp and i have a backup of ALL before update , can i restore it or it will hard brick my phone? [ Bad english cuz i'm brazilian xD ]
Sent from my XT1033 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my XT1033 using XDA Premium 4 mobile app
lucas_silva2k said:
Sent from my XT1033 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i havent been upto date with 5.0 on moto but im sure theres a bootloader update,some claim to downgrade sucessfully, but you should wait till google/moto release the factory images. also potential isuues with custom recovery.
you have to wait till the images are released or risk a brick till theres a fix
http://forum.xda-developers.com/mot...33-ota-5-0-lollipop-brazilian-t2963565/page17
http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798/page3
downgrade isn't that difficult and definitely possible, though you get the screen flickering effect that is easily solved by locking and unlocking the device, though it comes back on every reboot, afaik there's no permanent fix for that.
You need to get a 4.4.4 image DONT TRY WITH A 4.4.2 ONE OR YOU GOING TO END UP BRICKING and flash it but don't flash gpt.bin and motoboot.img
Download mfastboot, and flash using this commands only:
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
Might have to adjust the syste.img_sparsechunk number accordingly depending on the image you use. some images use 1 as the first one etc, check that.
GL&HF
ianx47 said:
downgrade isn't that difficult and definitely possible, though you get the screen flickering effect that is easily solved by locking and unlocking the device, though it comes back on every reboot, afaik there's no permanent fix for that.
You need to get a 4.4.4 image DONT TRY WITH A 4.4.2 ONE OR YOU GOING TO END UP BRICKING and flash it but don't flash gpt.bin and motoboot.img
Download mfastboot, and flash using this commands only:
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
Might have to adjust the syste.img_sparsechunk number accordingly depending on the image you use. some images use 1 as the first one etc, check that.
GL&HF
Click to expand...
Click to collapse
Hey man, I'm from ARG too. Just few questions: Have you tested this method before? Were you on Brazilian Lollipop or in GPE Lollipop before downgrading? And which KK firmware have you flashed to downgrade? Thanks in advance..
ianx47 said:
downgrade isn't that difficult and definitely possible, though you get the screen flickering effect that is easily solved by locking and unlocking the device, though it comes back on every reboot, afaik there's no permanent fix for that.
You need to get a 4.4.4 image DONT TRY WITH A 4.4.2 ONE OR YOU GOING TO END UP BRICKING and flash it but don't flash gpt.bin and motoboot.img
Download mfastboot, and flash using this commands only:
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
Might have to adjust the syste.img_sparsechunk number accordingly depending on the image you use. some images use 1 as the first one etc, check that.
GL&HF
Click to expand...
Click to collapse
The problem isn't 4.4.2 itself. In fact, you can go back to 4.4.2 or 4.4.4, just avoid flashing bootloader (motoboot.img) and partitions table (gpt.bin) as you said.
But, don't downgrade via OTA! (WiFi/zip) or you'll hard brick your phone.
Don't do this: 5.0-->4.4.2-->4.4.4 (OTA) or the phone will get bricked in the middle of the update process.
t4n017 said:
The problem isn't 4.4.2 itself. In fact, you can go back to 4.4.2 or 4.4.4, just avoid flashing bootloader (motoboot.img) and partitions table (gpt.bin) as you said.
But, don't downgrade using an OTA zip! or you'll hard brick your phone.
Don't do this: 5.0-->4.4.2-->4.4.4 (OTA) or the phone will get bricked in the middle of the update process.
Click to expand...
Click to collapse
Hmmm so, installing for example, 4.4.4 retail from US AND THEN OTA to Lollipop will brick the device?? S...t man.. I dont know why I OTAed to GPE L... Hope to see 5.0 Moto images to go to Motorola firmware once again...
MarckozZ said:
Hmmm so, installing for example, 4.4.4 retail from US AND THEN OTA to Lollipop will brick the device?? S...t man.. I dont know why I OTAed to GPE L... Hope to see 5.0 Moto images to go to Motorola firmware once again...
Click to expand...
Click to collapse
No, you missunderstood it a bit. You shouldn't downgrade via OTA.
When you flash Lollipop your bootloader gets updated (41.18). After that you shouldn't flash an older bootloader or you'll brick the device.
When using a full firmware package you can simply skip flashing the bootloader (and partition table).
That's why lot of users reported that their phone gets bricked in the middle of the OTA update process when doing: 5.0-->4.4.2-->4.4.4 (OTA)
TL;DR: When downgrading, use fastboot and skip flashing an older bootloader/partition table to avoid bricking the device.
t4n017 said:
No, you missunderstood it a bit. You shouldn't downgrade via OTA.
When you flash Lollipop your bootloader gets updated (41.18). After that you shouldn't flash an older bootloader or you'll brick the device.
When using a full firmware package you can simply skip flashing the bootloader (and partition table).
That's why lot of users reported that their phone gets bricked in the middle of the OTA update process when doing: 5.0-->4.4.2-->4.4.4 (OTA)
TL;DR: When downgrading, use fastboot to skip flashing an older bootloader/partition table and bricking the device.
Click to expand...
Click to collapse
you are great. thanks for that explanation. So, there will be no problem if I downgrade from GPE 5.0.1 to Moto 4.4.4 and then OTA to Moto 5.0??
I mean, maybe there will be some differences on GPEs new bootloader and partition table with the new ones from Motorola.
And what do you reccomend? fastboot or mfastboot?
t4n017 said:
No, you missunderstood it a bit. You shouldn't downgrade via OTA.
When you flash Lollipop your bootloader gets updated (41.18). After that you shouldn't flash an older bootloader or you'll brick the device.
When using a full firmware package you can simply skip flashing the bootloader (and partition table).
That's why lot of users reported that their phone gets bricked in the middle of the OTA update process when doing: 5.0-->4.4.2-->4.4.4 (OTA)
TL;DR: When downgrading, use fastboot to skip flashing an older bootloader/partition table and bricking the device.
Click to expand...
Click to collapse
Well, I flashed older bootloader(from 4.4.4), ;(
Now, what do I do?? I am unable to do practically nothing! Pre-flash validation fails again and again!
whenever I try to flash partition! Please HELP!!
MarckozZ said:
you are great. thanks for that explanation. So, there will be no problem if I downgrade from GPE 5.0.1 to Moto 4.4.4 and then OTA to Moto 5.0??
I mean, maybe there will be some differences on GPEs new bootloader and partition table with the new ones from Motorola.
And what do you reccomend? fastboot or mfastboot?
Click to expand...
Click to collapse
Right, it shouldn't brick your device, but I didn't tried it yet so I'm not 100% sure.
Do it at your own risk or wait until someone reports it can be safely done.
I was running Retail Argentina KitKat (4.4.4) and upgraded to GPE 5.0.1 to taste official Lollipop.
The firmware is almost perfect, but I'll try Motorola Lollipop for sure as soon as it gets released.
I recommend you mfastboot, lot of users had problem while using fastboot (stuck at Google bootlogo).
I think imma flash GPE 5.0.1 but i have 2 sims ... :/
Sent from my XT1033 using XDA Premium 4 mobile app
SIDELOAD
what if we downgrade with sideload?
Ive tried with mfastboot and motoboot fails to flash and so do other partitions...
I dont know why we cant downgrade the bootloader... Its the main problem I think...
Just thought we could just sideload an OTA KK upgrade or firmware...
any sugestions?
MarckozZ said:
you are great. thanks for that explanation. So, there will be no problem if I downgrade from GPE 5.0.1 to Moto 4.4.4 and then OTA to Moto 5.0??
I mean, maybe there will be some differences on GPEs new bootloader and partition table with the new ones from Motorola.
And what do you reccomend? fastboot or mfastboot?
Click to expand...
Click to collapse
I did this the other day. Downgraded my gpe converted phone to 4.4.4 and then did the OTA update back to 5.0.1 through system settings. I went back to 4.4.4 this morning because I was missing the custom themes.
When I was first trying to get lollipop though, I accidentally downgraded back to 4.4.2 and then OTA'd to 4.4.4 and tried to update to 5.0. I don't know why but my phone didn't brick, I was just stuck at the bootlogo for a while lol. That was incredibly lucky for me.
Just read the OP and you'll be alright:
http://forum.xda-developers.com/moto-g/general/guide-xt1033-downgrade-lollipop-5-0-to-t2969729
jman1234 said:
I did this the other day. Downgraded my gpe converted phone to 4.4.4 and then did the OTA update back to 5.0.1 through system settings. I went back to 4.4.4 this morning because I was missing the custom themes.
When I was first trying to get lollipop though, I accidentally downgraded back to 4.4.2 and then OTA'd to 4.4.4 and tried to update to 5.0. I don't know why but my phone didn't brick, I was just stuck at the bootlogo for a while lol. That was incredibly lucky for me.
Just read the OP and you'll be alright:
http://forum.xda-developers.com/moto-g/general/guide-xt1033-downgrade-lollipop-5-0-to-t2969729
Click to expand...
Click to collapse
No need for that, Ive downgraded to KK days ago.. BUT my phone's display is broken so I need to replace it, but I need money. Anyway it has KK now..
Hy. I'm one of the guys that truly bricked the device (xt1032). Went from lollipop 5.0.1 (OTA) to 4.3 jellybean (factory image).
Then went the surprise. The device doesn't enter Fastboot anymore. I can find the device in device management as "Qualcomm HS-USB QDLoader 9008". Sience i had 41.18 bootloader all i can do is to wait until singleimage.bin appears from god to flash the bootloader with qboot.
The device is dead.
So remember. DO NOT TRY TO DOWNGRADE TO FACTORY, OR even any previous version if you are already on 5.0.1 via OTA. RISK OF HARDBRICK.
Sience we don't have any chance to get the original flash files from factory (bootloader and others persistent folders responsable for device specific IMEI etc..) , all we have to do is to research . Anyway i can't say Motorola would offer a software tool to help resurrect our bricked devices.
Good Bless our Moto G's hard bootloader bricked.
from argentina too... newby
hey guys! i've upgraded my moto g by ota to Lollipop 5.0.1, and then installed CM 12.1. But i want to go back to KK (stock or CM11... whats better?). But i dont know much and dont want to brick my phone. i have fastboot 4118. what should I do? thank youu very much... I'll wait for an answer.
Hi @ucas_silva2k,
I have followed all the procedure that you posted. There will not be any error on cmd prompt. But it is now in lolipop boot screen ?
I am sorry for reviving very old thread, despite the age this thread have a very interesting topic about how the phone reacted after flashing.
Few week ago I have trying to downgrade from stock lollipop in xt1039 to stock kitkat using mfastboot command and flash everything on zip file, lucky for me my phone is running well except for known bugs in kitkat and screen flicker due to incompatible bootloader, so after few days I am decide to upgrade the phone to MM using IdentityCrisis ROM via recovery and surprisingly the rom is flashed perfectly and my bootloader version still on latest version available, so i think the cause of hard brick is more likely corrupted image or different CID rather than flashing motoboot.img and gpt.bin.
SOLVED! SEE HERE!
So, I softbrick my XT1033 while I trying to upgrade from Motorola 5.0 to 5.0.1. After I tried many ways to solve the softbrick, the only solution was revert to 4.4.4 GPE and upgrade to 5.0.1 GPE.
So, please all understand that I did not want to install GPE (I already knew that I will lose dual sim on GPE), but was the only way to solve the softbrick.
But, I really don't like the GPE, and prefer the stock motorola rom for tons of reasons, but the main is the dual sim function and the camera/gallery apps.
So, my question is: Is there a way to return back from 5.0.1 GPE to stock 5.0.1?
Thanks!
Yes!
Try reading this topic:
http://forum.xda-developers.com/moto-g/help/xt1032-bricked-please-help-t2980601
Probably, you'll need to flash a new gpt.bin file. Once it's been done, you can flash the others files.
Cheers!
Ok... it works... but was a hard work to do...
1 - Downgrade from 5.0.1 GPE to 4.4.4 GPE(using fastboot, but without flashing gpt.bin and motoboot.img)
2 - Reboot into bootloader and reflash 4.4.4 GPE (now flashing gpt and motoboot)
3 - Reboot into bootloader and flash 4.4.4 Stock (flashing gpt and motoboot too). Start phone.
4 - Reboot into recovery and flash 5.0 Stock (adb sideload). Start phone, put 5.0.1 Stock update zip into internal memory.
5 - Reboot into recovery and flash 5.0.1 stock.
I had to download 6 differents roms and others files to solve this problem (about 2,2GB downloaded)...
And, WOW, now all is fine...
JAJAJAJA
Me too, brother. I had to download 4 or 5 different roms to make it run properly.
But, at least, I'm now running the 5.0.1!
Cheers!
danilocps87 said:
Ok... it works... but was a hard work to do...
1 - Downgrade from 5.0.1 GPE to 4.4.4 GPE(using fastboot, but without flashing gpt.bin and motoboot.img)
2 - Reboot into bootloader and reflash 4.4.4 GPE (now flashing gpt and motoboot)
3 - Reboot into bootloader and flash 4.4.4 Stock (flashing gpt and motoboot too). Start phone.
4 - Reboot into recovery and flash 5.0 Stock (adb sideload). Start phone, put 5.0.1 Stock update zip into internal memory.
5 - Reboot into recovery and flash 5.0.1 stock.
I had to download 6 differents roms and others files to solve this problem (about 2,2GB downloaded)...
And, WOW, now all is fine...
Click to expand...
Click to collapse
Hey mate, do you think the same process works in a xt1032 but with the corrects files?, thanks a lot
danilocps87 said:
Ok... it works... but was a hard work to do...
1 - Downgrade from 5.0.1 GPE to 4.4.4 GPE(using fastboot, but without flashing gpt.bin and motoboot.img)
2 - Reboot into bootloader and reflash 4.4.4 GPE (now flashing gpt and motoboot)
3 - Reboot into bootloader and flash 4.4.4 Stock (flashing gpt and motoboot too). Start phone.
4 - Reboot into recovery and flash 5.0 Stock (adb sideload). Start phone, put 5.0.1 Stock update zip into internal memory.
5 - Reboot into recovery and flash 5.0.1 stock.
I had to download 6 differents roms and others files to solve this problem (about 2,2GB downloaded)...
And, WOW, now all is fine...
Click to expand...
Click to collapse
Does step 2 downgrade the bootloader from 41.18 to 41.13?
Yeah Did some one with 41.18 bootloader tries this solution?
We cant go back to 41.13 bootloader...
I just downgraded my XT1032 (falcon) from stock 5.0 to stock 4.4 and it won't boot anymore. I did it using the fastboot method (flashing several .img or .bin files using fastboot), as I had done it many times before in order to revert the phone to stock.
But this time it won't boot no matter what I do. It may be related to the fact that I accidentally tried to flash 4.4 partition table and bootloader (now I see the downgrading tutorials recommend against that) but I don't know what to do.
I tried pushing another ROM (in the ZIP format) via ADB, but when I try to install that ZIP in TWRP recovery, it says "unable to mount data" or "unable to mount storage". It also used to say "unable to mount system" but I think I fixed that with "fastboot format system" (which you can't do for /data).
I think I'd need Android 5 .img and .bin files in orden to fix this via fastboot, but Android 5 doesn't seem to exist in that format.
Can anyone think of a solution? Thanks in advance.
Does your phone still have the 41.18 bootloader on it?
I'm surprised that it bricked because I flash every partition except motoboot when downgrading my xt1032 8 GB from LP to KK.
U did it with unlocked bootloader or locked one..?? I am looking for a tutorial on downgrading to 4.4.4. from 5.0.2 for locked bootloader..
Unlocked bootloader. If possible, unlock the bootloader as you may not be able to downgrade without unlocking.
i am also faced this problem......after reflashing the kitkat os my moto g is booted(dont flash motoboot and gpt)
seshuganesh2011 said:
i am also faced this problem......after reflashing the kitkat os my moto g is booted(dont flash motoboot and gpt)
Click to expand...
Click to collapse
How did u reflashed..?? Can u tell me the xact procedure..?? And on Locked bootloader..??
kaymaddy said:
How did u reflashed..?? Can u tell me the xact procedure..?? And on Locked bootloader..??
Click to expand...
Click to collapse
i flashed on unlocked boot loader
I have a XT1032. In the past it ran Motorola (not GPE or anything) Kitkat 4.4.2. Three months ago I upgraded it to GPE 5.0.1, because of my stupidity for not realizing what "GPE" meant. I hate this GPE and have already done with it. Could you guys, please, show me a way to go back to Motorola firmware Kitkat 4.4.2. I don't want anything relating to GPE anymore. :crying::crying::crying:
My XT1032 is en-us version, FYI.
Download the stock 4.4.4 ROM for your phone from here: http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=filename&order=ASC&show=100&page=1
Flash it manually using fastboot commands. Do no flash anything below 4.4.4 as doing so may brick your phone.
audit13 said:
Download the stock 4.4.4 ROM for your phone from here: http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=filename&order=ASC&show=100&page=1
Flash it manually using fastboot commands. Do no flash anything below 4.4.4 as doing so may brick your phone.
Click to expand...
Click to collapse
Thank you. Instead of downgrading, can I upgrade GPE 5.0.1 to Motorola 5.0.2, then wait for Motorola 5.1 OTA update? Is there any risk to switch between GPE and non-GPE (Motorola)?
The partition layouts are slightly different and I believe the data partition on gpe (ext4) and stock (f2fs) are not the same.
audit13 said:
The partition layouts are slightly different and I believe the data partition on gpe (ext4) and stock (f2fs) are not the same.
Click to expand...
Click to collapse
audit13, I really don't understand all the commands I need to type when using mfastboot. When upgrading my phone to GPE, I followed this post (http://forum.xda-developers.com/moto-g/general/gpe-ota-lrx21z-5-0-1-xt1033-xt1032-t2969847). Is there any difference? Could you show me some links to learn about how to use those commands? I don't know what I should type, what I should do step-by-step. Thank you.
This is a good guide: http://forum.xda-developers.com/showthread.php?t=2542219
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