yashsingh1/xdaforums huggingface dataset:
[Moto G General] Lemagex:
I've seen a lot of threads saying we cant downgrade from lollipop to kitkat, bricking, blah blah blah.

But earlier today I downgraded to the Asia Retail 4.4.4 firmware (.xml.zip) and also to the Brazil Retail 4.4.2 firmware (.xml.zip) from Lollipop (brazil soak)....

So I want to know everyone else's experiences, let's get a thread of the known SAFE ways to downgrade.

Also yes, there are other factors that may contribute to a brick, so

people who have bricked tell what you've done in order to brick your phone

.

I was lead to believe that flashing 4.4.2, or 4.4.4 asia retail, over lollipop would cause a brick...

TL;DR: Let's try clear up some confusion on downgrading the Moto G

I can only confirm for the

XT1033

but I am willing to post whats needed.

[MENTION=5127197]plantator[/MENTION] gave some useful information "if you try to flash motoboot and gpt it will give you error and can make some troubles, in this link you run only bat file , it flash gpe 4.4.4 without motoboot and gpt , and next step you flash stock and again without motoboot and gpt. As I said i flash 5.0.1 GPE to 4.4.4 GPE and then to 4.4.4 stock"

And yes if you downgrade from Lollipop to Kitkat you WILL have that weird bloody flickering line going through your screen. the only solution i see so far is turning the screen off and on (lock and unlock) once, and itll disappear. but it comes back everytime phone is booted.

It seems the only safe way to downgrade is to make sure no matter what you do, do not install any over the air update for a version starting with 4, or simply just don't OTA from 4.4.2 to 4.4.4. if you need 4.4.4 to upgrade to 5.0.0 then download the 4.4.4 XML.ZIP firmware.

I'll make the assumption that when 5 hits official OTA rollout itll be safe to download through 4.4.4 unless someone can correct me otherwise.
[Moto G General] plantator:
I downgraded my moto xt1032 from BR soak 5.0->GPE Lollipop 5.0.1 to GPE 4.4.4 using this link:

http://xdaforums.com/moto-g/general/guide-xt1033-downgrade-lollipop-5-0-to-t2969729

and next i just flash stock EU 4.4.4 without flashing motoboot and gpt.bin and it is working! remember do not flash motoboot and gpt.bin

so I back to stock retail EU without problems
[Moto G General] KDB223:
What was your "safe" way?

Did you just directly flash everything from 4.4.4?

If not, then what exactly did you do?
[Moto G General] W3ND31:
Bro, when you have downgraded to 4.4.2, the screen still flickering? (like in 4.4.4)
[Moto G General] t4n017:
You can go back to 4.4.2 or 4.4.4, just avoid flashing bootloader (motoboot.img) and partitions table (gpt.bin).

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.
[Moto G General] brainscollector:
Almost all peoples who bricked their devices was ones who flashed 4.4.2 and OTA to 4.4.4 (which makes no sense to me and it's idiotic), most of peoples with other problems simply didn't apply to tutorials and flashed custom recovery after changing to 4.4.4 and trying to push OTA zip. Another are peoples with bootloops after pushing and installing 5.0/5.0.1 which was easily fixed with gpt file.

So just to put together - you can brick device if you will downgrade to 4.4.2 (which made troubles even when there was KK release before lollipop), other problems are just mostly bootloops and connection problems (which can be fixed with flashing gpt file in first case and/or flashing modems for second).
[Moto G General] jman1234:
Can you use moto tool to downgrade to 4.4.4
[Moto G General] jazzh:
If i make a cwm nandroid backup while in crdroid kitkat, then upgrade to cm12 and return afterwards back to crdroid from backup... Would that be OK?
[Moto G General] MarckozZ:
I've downgraded from GPE 5.0.1 and everything goes right but I want to know, what about logo.bin? Is it safe to flash it? When I turn on the phone it shows the Google logo and the open lock because it was from GPE lollipop, but I didnt dare to flash logo.bin from Moto 4.4.4 firmware, since that file wasnt listed anywhere with the files that were safe to flash...

So is it safe to flash logo.bin? Has anyone succesfully flashed it?
[Moto G General] plantator:
flash logo without problems, it is only bootlogo file nothing more, i downgraded 5.0.1GPE to 4.4.4GPE and than 4.4.4retail

without touching motoboot.img and gpt.bin, do not flash them!
[Moto G General] MarckozZ:
Thanks man! Im not a total noob, it was just a doubt I had.. ;) Thanks!
[Moto G General] andresesm:
I have a little question, if i accidentally flash motoboot or gpt, i can't flash again to lollipop then downgrade again? i don't do it, is just in case.

also, i have a XT1032 with 5.01 GPE lollipop, i can downgrade to 4.4.4 without flashing motoboot and gpt then go to stock 4.4.4? thanks!
[Moto G General] plantator:
if you try to flash motoboot and gpt it will give you error and can make some troubles, in this link you run only bat file , it flash gpe 4.4.4 without motoboot and gpt , and next step you flash stock and again without motoboot and gpt. As I said i flash 5.0.1 GPE to 4.4.4 GPE and then to 4.4.4 stock
[Moto G General] flyjazz:
Your post is the most sensible one for people to use. I honestly have no idea why anyone would flash 4.4.2 unless they don't have the 4.4.4 firmware. What seems to be happening to those that update from 4.4.2 to 4.4.4 OTA and have problems is that the bootloader was upgraded in 5.01 to version 41.18 Have you done the downgrade yourself and did you get the screen flicker issue? I'm running 5.01 GPE on a XT1032 and for the most part see no reason to downgrade. I will however consider flashing the Motorola stock 5.01 firmware once it's released.
[Moto G General] plantator:
Why I downgrade? only to check if it possible in easy way and sure it is. I like Lollipop very much , and back from gpe to stock only for waiting for stock ota when it arrives, not to flash everything when it comes, im ready now for it:P
[Moto G General] OldYellowBricks:
Pls answer: did you get the screen line moving/flicker problem after downgrading?
[Moto G General] Boss442:
You can't flash OTA if you downgrade, ex: if you downgraded from 5.0 to 4.4.2 and update with ota to 4.4.4 the phone will brick
[Moto G General] rizki_Alkaf:
What if i do like this:

I'm on XT1033 ASIA, convert to 4.4.4 BR, OTA update to soak 5.0 and then 5.0.1. So the bootolader is updated

And if the OTA is already rollout for ASIA version, then i flashed back to asia 4.4.4 retail without flashing motoboot and gpt, then OTA update to lollipop

How?
[Moto G General] MarckozZ:
Then you can flash OTA because you earlier flashed 5.0 soak test, so bootloader will be the same as the rollout OTA...

You can OTA to 5.0 comming from a downgraded 4.4.4 firmware!

I mean, 5.0 to 4.4.2 to OTA 4.4.4 = brick

But 5.0 to 4.4.4 to OTA 5.0 = will work because you have 5.0 bootloader already! :good:
[Moto G General] deeplyyoung:
Y u so eager to jump here n thr, I mean Braz n then Asian, a good suggestion bro, either stick with Braz as no issues me too facing on Braz 5.01 or else wait for official Asian OTA.. don't make ur mind in two ways that I'll jump Braz n den Asian... Or do what my plans, rite now m on Braz soak LP 5.01 n I'll use it till we get Asian LP stock images for secure jump...

+ 1 but knowingly taking risk is not a good idea... Cheers
[Moto G General] rizki_Alkaf:
Thanks. That's what i'm thinking :)

I know that a stock image will be a more secure way to go back to asian rom. This is just in case i can't wait until it released :p Usually it will take more times after the OTA, right?
[Moto G General] deeplyyoung:
yes we need to wait for atleast one month after Asian official OTA LP, so if you need you can switch to Braz & njoy bugless LP & stick with it..
[Moto G General] ganeshkmr21:
screen flickering

i once downgraded from lollipop 5.0 to 4.4 with bootimage. It worked but having screen Flickering effect while booting & in Recovery.

will my phone be like that forever..? :(
[Moto G General] deeplyyoung:
Upgrade to LP n yr flickering issue will be solve, n don't try to downgrade to kk cuz as of now no secure way to do so...you may brick yr device...
[Moto G General] BryanByteZ:
First thanks to all to make easy info for newbies,second what is the best tutorial to upgrade to the GPE version 5.0.1 a XT1033 ? i am afraid if i upgrade to L and i can not back (if i don't like) to a custom rom or BR Retail (currently using) and if in L i can flash zips (TWRP) and root + Xposed.

Sorry many questions and thanks in advanced
[Moto G General] hafizimtiaz:
I have an XT1033 Asia retail. I flashed the Brazilian firmware (4.4.4) first and then flashed the soak test OTA. After some days I downgraded my phone to GPE 4.4.4. I flashed everything except the gpt.bin (including boot.img and motoboot). The screen was flickering at first and then I flashed the GPE OTA to 5.0.1 and the flickering was gone. I don't think downgrading is a problem because no matter what, you cannot flash the gpt.bin and thus your partition table is intact. The only thing that might brick a phone after downgrading is that if Motorola disables the booting with the old boot.img while on the new bootloader.
[Moto G General] Gur Kada:
Bricked

​

Xt1033 asian.

My first Android device.

Came as 4.4.2, if I remember correctly. I brought it to 4.4.4 with downloaded OTA. Then transferred it to 4.4.4 BR and onward to 5.0 BR.

LOVED my Lopipop!!!

Then news of 5.01, and in my excitement, I misread.

I applied a small update ( less than 50mb) that was for 5 to 5.01.

I missed that one should uproot and lock and also, in retrospect, I don't think it's for the XT1033

---------- Post added at 12:13 AM ---------- Previous post was at 12:08 AM ----------

Point being, short of sideloading 4.4.2 for fear of death, I've tried all else.
[Moto G General] ryanguy426:
In theory, would this work with the xt1028 with a locked bootloader?

I'm trying to look into ways to help this device get root via a downgrade (risky as it may be)
[Moto G General] Lemagex:
In all honesty the only way i feel safe doing a downgrade is the 4.4.4 stock image .xml.zip... i was rooted on 5.0 too but wanted 5.0.1 so i downgraded to asia 4.4.4 by mistake, switched to brazil 4.4.4, applied the 5.0.0 update, then the 5.0.1 update without root and tada win
[Moto G General] Lemagex:
Wouldn't know because I don't use that device, and this thread being marked as XT1033 I'd doubt the chances of getting help for that device here, try post a Q&A thread, or you might get lucky.

Either way that sounds extremely risky... :rolleyes:
[Moto G General] settu_kliwon:
Hello everyone,

I'm from Indonesia. My device is XT1033, but I already convert it to GPE Lolipop 5.0.1 without dual sim supported. XT1032 is displayed in the About Phone.

How can I upgrade my device to Moto G that support dual sim card? I don't care if it is KitKat or Lollipop.

I prefer KitKat by the way. Thanks
[Moto G General] Gur Kada:
Bricked.

HELP!!! XT1033

After the wrong 5.01BR success load and no boot, I somehow (along the way) loaded clockwork mod recovery 6, and I think did something where the firmware required changed to asia 4.4.4 .... I have tried every stock option (sideloaded) with NO success.

Done/ Doing something wrong.

Please get me back in !!!!!!

If anyone knows how.
[Moto G General] Gur Kada:
Bricked

This is what did me in ..... carbontesla (can't post address) said and offered link 'Motorola Moto G first-generation is now getting updated to Android 5.0.1 Lollipop – build LXB22.46-25 – in Brazil through a small 11 MB OTA, bumping its firmware version from v220.21.16 to v220.21.25. You can download LXB22 OTA package for your phone via the direct download links given below.'
[Moto G General] ficki yahya:
Tes
[Moto G General] settu_kliwon:
Finally I solved this by my self after following this steps.

Screen is flickering when I downgraded to 4.4.4, but everythings worked like a charm after (re)upgrading to Lollipop. The only problem is I can't use Xposed anymore
[Moto G General] justplayeR:
That what happen when you do not follow step by step the threads ..

Cheers guys,

Just confirming what other users say: I downgraded from GPE 5.0.1 to 4.4.2 and OTA'd to 4.

4.3 and in the way bang, black screen and dead phone. Sended my G to the assistence last monday and gonna pass Christmass without my boy :crying:

The only way to fix this kind of brick is with MBM 5.0 right?

Sorry for the bad english :D
[Moto G General] yash.sharma99@yahoo.com:
Stil having telephony issues

When I've downgraded from this to ASIA 4.4.4, The other person whom I've called or if they've called me, they're able to hear my voice in a very low volume.:confused:
[Moto G General] hafizimtiaz:
You can go back to 4.4.4. Just don't flash the gpt.bin and motoboot.img while you are at it. There are plenty of threads in the General section about downgrading. But you might experience screen flickering.

You can flash the Brazil retail 4.4.4 and then flash the OTA to 5.0 via stock recovery. In that way, too, you will have dual SIM functionality.
[Moto G General] iyengar:
Thanks, could you be kind enough to point me to that direction? I mean the thread which is noob friendly. I am currently running gpe version 5.0.1. I would like to restore back to Asian aka Indian version of stock,

Thank you once again
[Moto G General] flyjazz:
Everyone was a noob at one time. I don't take credit for the following,hope it's of some use.

gpt.bin - this is the partition table, it goes hand in hand with the bootloader

motoboot.img - this is the bootloader

logo.bin (or clogo.bin) - this is the lovely boot screen before the boot animation

boot.img - this is the kernel

recovery.img - this is the recovery

system.img - and finally this is the actual system update Example:system system.img_sparsechunk0 1 .0 .1

NON-HLOS.bin - this is the other half of the modem

fsg.mbn - this is the first half of the modem

* Downgrade: Basically you want to stay away from gpt (partition table) and motoboot (bootloader),

then you should be okay, again, do this at your own risk *

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 0 .1 .0

mfastboot flash system system.img_sparsechunk2 1 .2 .1

mfastboot flash system system.img_sparsechunk3 2 .3 .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

As a final thought,if you're switching to Asian 5.0,keep in mind it's a multi-step process. I think someone explained how they did it in this thread: http://xdaforums.com/moto-g/general/how-to-revert-5-0-1-gpe-to-4-4-4-5-0-5-t2988565
[Moto G General] NextGenGTR:
Im getting the error "Image is too large" and apparantly this is from the difference in the partition tables and too fix this i need to flash GPT and Motoboot but this is a big no right since it has messed up others devices? Now the OP said that he went from 5.0.1 GPE > 4.4.4 GPE > 4.4.4 Stock Motorola and i don't get how since im trying the same thing but the partition table is different.... Just doesnt make sense how its the same phone but some can do what some cant, Racismmmm!! :D

OMGGGGGGG I JUST WENT FULL YOLO AND FLASHED GPT AND MOTOBOOT AND NOW ITS BOOTING UP STOCK MOTOROLA, GIRLS IF YOU LIKE DANGEROUS MEN THEN COME TO MEEEEEEEEEEEE :D
[Moto G General] flyjazz:
I haven't tried it myself,but I think it's a bit confusing.

1. Yes you have to downgrade to gpe 4.4.4 first and not touch the .gpt or motoboot.

2. You now go laterally to stock 4.4.4. At this point you must flash the Motorola .gpt partition file system. Exclude the motoboot file as you can never downgrade the bootloader.

3. If all went well you should be able to OTA to stock 5.0
[Moto G General] andogeek10:
You can flash gpt and motoboot. I did flash both of them when I downgraded to 4.4.4. gpt.bin will be flashed succesfult but moto boot will fail.
[Moto G General] NextGenGTR:
Now the big question, will I be able to update to lollipop through ota without facing a brick? From my understanding the brick is occuring from the OTA forcing a bootloader downgrade or change and this is the cause, so will OTA updating lollipop cause the same issue?
[Moto G General] andogeek10:
Well I have upgraded back to lollipop without any problem. So no, you should not have any problems.
[Moto G General] jman1234:
Could some steps be provided on how to go from GPE 4.4.4 to Motorola 4.4.4?
[Moto G General] NextGenGTR:
What i did basically from the start which im going to make it simple is

From 5.0.1 Flash 4.4.4 GPE leaving out GPT and Motoboot

Then from 4.4.4 GPE if it boots go back to bootloader and flash 4.4.4 Motorola as usuall including Gpt and Motoboot and you should have Stock 4.4.4 Motorola back :)
[Moto G General] flyjazz:
From what I've read the bricking occurs because some people have flashed from 5.0.1 to 4.4.2 then OTA to 4.4.4,that's when the bricking seems to occur. Had those that bricked simply downgraded to 4.4.4,they likely wouldn't have had any problems.
[Moto G General] NextGenGTR:
Yes, that is correct, but why? In my previous comment i stated my theory, however, i am no expert and therefore will the same problem happen with lollipop? The above user has answered this and has said that he has successfully upgraded to kitkat with no problems, now i do not know if that was achieved by flashing it manually or an OTA update.
[Moto G General] flyjazz:
My best guess is that it's okay to downgrade to 4.4.2,the problem is the OTA to 4.4.4 Looking at the difference between OTA and manual flashing,you could conclude that the OTA is sending one or more flashing commands that shouldn't occur as it will cause a bricking situation. Based on what we know,once you upgrade to 5.0.1 you have then also changed the bootloader version to 41.18. The 4.4.4 OTA will try to flash the 41.13 bootloader thinking that's it's an upgrade from 41.05 when in reality it's still 41.18,perhaps that's what's causing the bricking. I don't think it's occurring due to a dirty flash as a wipe should occur after flashing a different firmware.
[Moto G General] hafizimtiaz:
You can try the Brazil Retail firmware. You will regain dual SIM functionality that way. Here is the post on XDA forums. You can also follow the tutorial on my signature.
[Moto G General] andogeek10:
The same should not happen since we already have the lollipop boot loader. My best guess as to why the 4.4.2 OTA update to 4.4.4 cause bricks is that the OTA update tries to write to partitions related to the boot loader but is denied/stopped in between due to some check in place by Motorola, which results in a semi bricked state. I say semi since the damage is reversible by using appropriate tools.

Edit : And to answer the question, I had returned to 4.4.4 GPE stock from 5.0.1 GPE to try a few ROMs ( vanir was the only rom which I could successfully flash) and then reverted to 5.0.1 GPE by downloading the OTA update side loading it on the 4.4.4 stock firmware.
[Moto G General] jman1234:
Has anyone tried downgrading to 4.4.4 gpe and then going back to 5.0.1 through system settings?
[Moto G General] NextGenGTR:
i tried that and it gave me an error while flashing.
[Moto G General] jman1234:
Really? I was just about to try it too.
[Moto G General] scotttiger:
I was using xt1033 Asian retail. I flashed KitKat 4.4.4 Brazilian and than lollipop. Currently I am on Brazilian 5.0.1. As of now lollipop is being rolling out in india .

If I go this way Brazilian 4.4.4>asian 4.4.4 then ota 5.0.2. Will it succeed..
[Galaxy S 4 Q&A, Help & Troubleshooting] Altorn91:
Hello guys , I'm stuck in this situation . I counter that is passed by one, there is no recovery installed and are completely blocked . I do not know that firmware mounted on first . You help me ? I have attached pictures.

With Odin:

<ID:0/007> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> I9505XXUGNG8_I9505YXXGNH2_I9505XXUGNG8_HOME.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/007> Odin v.3 engine (ID:7)..

<ID:0/007> File analysis..

<ID:0/007> SetupConnection..

<ID:0/007> Initialzation..

<ID:0/007> Get PIT for mapping..

<ID:0/007> There is no PIT partition.

<OSM> All threads completed. (succeed 0 / failed 1)

<ID:0/007> Removed!!

I tried different firmware but nothing.
[Galaxy S 4 Q&A, Help & Troubleshooting] jeffrey268:
Install Kies start it and connect the phone to the pc by the stock USB cable, it should detect the phone and offer you to repair it.
[Galaxy S 4 Q&A, Help & Troubleshooting] MAX 404:
Hi mate,

Easiest way out is to reflash stock rom again ( i can see your knox bit is set already) follow this guide

http://xdaforums.com/showthread.php?t=2265477

There you can find PIT files for your phone , flash same type of rom you had or newer , older stock roms will fail
[Galaxy S 4 Q&A, Help & Troubleshooting] Altorn91:
I solved using a different cable. :)
[JASJAR, XDA Exec, MDA Pro General] Guru Meditation:
Hi I have an O2 XDA Exec (personal contract) with the BB Connect software up and running. I also have a Blackberry 8700 that connects to BES at work on the O2 network (BT Mobile I think). I can get BB Connect to work with regards to email, and everything works well :-)

However, when I use the blackberry I can use Opera Mini to surf the web and Google Maps Mobile, so I know I have access to data.

When I put the SIM card in the XDA I can't seem to get the data connection working. I have tried several APNs - o2.wap.co.uk; mobile.o2.co.uk and blackberry.net, but none seem to give me access.

I am aware that my compnay may well have blocked some ports/protocols, but as I can access Opera Mini and Google Maps from the blackberry there must be data there somewhere. Anyone got any ideas as to how I could do it?
[JASJAR, XDA Exec, MDA Pro General] KarmaNP:
As far as I know blackberry and internet are two different connections. As you can use blackberry on your universal you need to get the internet connection setting from your provider (It should be here in the forum as well) and manually create a connecting setting and you should be able to view the web pages as well.

When you use the internet connection your BB connection will be disconnected as you cannot have two connections at the same time.

Hope this helps.
[JASJAR, XDA Exec, MDA Pro General] Guru Meditation:
Right, it's taken me a while, but I've got a bit further with this. The reason my blackberry can access data, but using the same SIM in my Universal it can't is all to do with the blackberry connect client.

As my companies SIM won't enable 'data' (ie the WAP or internet APN) the data is coming via the Balckberry BES MDS service. This allows the BES to act as a kind of proxy for data.

The bad news is that the Blackberry connect client on WM5 doesn't support MDS. The good news is that the Blackberry Suite for WM6 that has just been announced http://www.techatplay.com/2007/04/24/blackberry-to-run-on-windows-mobile-6/ should.

Bring it on!
[Moto G Q&A, Help & Troubleshooting] plantator:
I want ask you for past of moto G updates, when 4.4.4 kk enter to Europe which retail get it first? GB? DE? EU? what was with 4.4.2? and if 4.4.4 go first GB is there any chance to again get Lollipop on GB first in Europe?
[Moto G Q&A, Help & Troubleshooting] eemgee:
With other releases Germany has got the first European release.
[Moto G Q&A, Help & Troubleshooting] plantator:
and GB was next?