Problems updating ROM - G 2014 Q&A, Help & Troubleshooting

Hi.
I didn't use my old Moto G2014 for a while. Now I wanted to update to lineageOS 16. When i try to Install via twrp the Error message attached in the screenshot appears. Any Idea how to solve this? If i try to boot into the old LOS15.1. I get a bootloop.
Thanks

harrymcqueen said:
Hi.
I didn't use my old Moto G2014 for a while. Now I wanted to update to lineageOS 16. When i try to Install via twrp the Error message attached in the screenshot appears. Any Idea how to solve this? If i try to boot into the old LOS15.1. I get a bootloop.
Thanks
Click to expand...
Click to collapse
Did you edit the zip? Perform a clean flash by wiping data, cache, dalvik cache, system and internal storage. You have to format internal storage every time you change your android version for a successful flash.

Hi,
Wiped all partitions but still no chance to write the ROM. Seems there are already problems wiping/formating the data partition.
I read that there are massive problems once the moto g´s battery is completely empty (like mine was).
Many users report that the device was bricked afterwards. some of them sent the device to a guy in india for a few dollars to have it "reanimated".

Related

Bricked XT1072

Hi Guys,
I stupidly did not realise my device (XT1072) was a different slightly different model to the moto g 2014.
I unlocked the bootloader and installed TWRP, then tried to install Cyanogenmod 12.1, this failed giving an error "Error executing updater binary in zip" Which I guess is due to it being a different model, right? After receiving this error I did some googling and found on a few sites that I should wipe data, system, cache & dalvik cache to resolve this. I did this and tried to flash it again, with the same error. Now my phone is stuck on the "warning bootloader unlocked screen" I can boot into fastboot mode, but is there any official Motorola images for my device anywhere? I have had a look online and cant find anything. :crying:
Any help would be much appreciated.
Thanks
Format system is completely wipe previous android version,
You need a custom ROM (I'm assuming you have custom recovery for your device model)
Or fastboot a original image for you're device
Hi
ohmygoddude said:
Hi Guys,
I stupidly did not realise my device (XT1072) was a different slightly different model to the moto g 2014.
I unlocked the bootloader and installed TWRP, then tried to install Cyanogenmod 12.1, this failed giving an error "Error executing updater binary in zip" Which I guess is due to it being a different model, right? After receiving this error I did some googling and found on a few sites that I should wipe data, system, cache & dalvik cache to resolve this. I did this and tried to flash it again, with the same error. Now my phone is stuck on the "warning bootloader unlocked screen" I can boot into fastboot mode, but is there any official Motorola images for my device anywhere? I have had a look online and cant find anything. :crying:
Any help would be much appreciated.
Thanks
Click to expand...
Click to collapse
Hi,
I am facing exactly the same problem here. Could you please let me know if you find any solution!!! please
Thanks
omarhowlader said:
Hi,
I am facing exactly the same problem here. Could you please let me know if you find any solution!!! please
Thanks
Click to expand...
Click to collapse
You might want to take a look at this thread: http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3054303
omarhowlader said:
Hi,
I am facing exactly the same problem here. Could you please let me know if you find any solution!!! please
Thanks
Click to expand...
Click to collapse
Hi,
I too faced this issue. I've seen this error mostly with the Team Win Recoveries(TWRP). Switch to philiz recovery touch.
Still no luck
kishorebvs said:
Hi,
I too faced this issue. I've seen this error mostly with the Team Win Recoveries(TWRP). Switch to philiz recovery touch.
Click to expand...
Click to collapse
Hi,
Thank you for your reply. I also tried with CWM_Touch_Titan_v2 recovery image. But when I tried to flash the stock rom RETGBALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml using mfastboot method, it shows on the phone screen "image too large".
As you have faced the same problem, would you be kind enough to give a step by step instruction to solve the issue. My phone is just stuck to unlocked bootloader warning screen for days.
My phone is Moto g XT1072 4G LTE.
Your help could save my days...
Thanks.
omarhowlader said:
Hi,
Thank you for your reply. I also tried with CWM_Touch_Titan_v2 recovery image. But when I tried to flash the stock rom RETGBALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml using mfastboot method, it shows on the phone screen "image too large".
As you have faced the same problem, would you be kind enough to give a step by step instruction to solve the issue. My phone is just stuck to unlocked bootloader warning screen for days.
My phone is Moto g XT1072 4G LTE.
Your help could save my days...
Thanks.
Click to expand...
Click to collapse
Why are u flashing an xml file? XML files are not rom files
The link provided above by mic_he has step by step instructions to restore phone back to stock
Your phone is not bricked. You deleted your system so there is no os to boot. The link should restore you back to stock
mic_he said:
You might want to take a look at this thread: http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3054303
Click to expand...
Click to collapse
Thank you,
I have tried those instruction earlier. when I enter "mfastboot flash bootloader bootloader.img" is says "Bootloader preflash validation failed" and when I enter "mfastboot flash system system.img_sparsechunk.0" onthe phone screen is says "Image too large". After going through all the steps when I reboot, it does not ever get past unlocked bootloader warning screen.
I really do not know which other option to try??
---------- Post added at 07:30 PM ---------- Previous post was at 07:26 PM ----------
Moto G User said:
Why are u flashing an xml file? XML files are not rom files
The link provided above by mic_he has step by step instructions to restore phone back to stock
Your phone is not bricked. You deleted your system so there is no os to boot. The link should restore you back to stock
Click to expand...
Click to collapse
I could not find any zip file of the stock rom. I downloaded the stock rom from that link but I am having error as i posted earlier.
Thanks
ohmygoddude said:
Hi Guys,
I stupidly did not realise my device (XT1072) was a different slightly different model to the moto g 2014.
I unlocked the bootloader and installed TWRP, then tried to install Cyanogenmod 12.1, this failed giving an error "Error executing updater binary in zip" Which I guess is due to it being a different model, right? After receiving this error I did some googling and found on a few sites that I should wipe data, system, cache & dalvik cache to resolve this. I did this and tried to flash it again, with the same error. Now my phone is stuck on the "warning bootloader unlocked screen" I can boot into fastboot mode, but is there any official Motorola images for my device anywhere? I have had a look online and cant find anything. :crying:
Any help would be much appreciated.
Thanks
Click to expand...
Click to collapse
Unmounting system before flashing usually stops that problem. What I like to do is wipe data, system, cache & dalvik then reboot to recovery before flashing the rom.
Sent from my GT-P5210 using Tapatalk
could you solve the problem with the XT1072?
hello sir! could you solve the problem with thw XT1072? Can you give me some instructions? cheers
It works!!!!! I could restore my system back with these steps!
Here´s the info
http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3054303
I followed the steps and when I was triyng to Flash each of the partitions in sequence using mfastboot get an error
I get an error with one of the files, (don´t remember now but I think was with the mfastboot flash logo logo.bin line
This give me an error, try to fix it and i couldn´t so I continue with the other files in the order listed and when the process was finished the phone was working again!!!!
Enter twrp recovery
Wipe system data cache dalvik
Put any rom like cm in microsd card or usb
And flash it using twrp
ohmygoddude said:
Hi Guys,
I stupidly did not realise my device (XT1072) was a different slightly different model to the moto g 2014.
I unlocked the bootloader and installed TWRP, then tried to install Cyanogenmod 12.1, this failed giving an error "Error executing updater binary in zip" Which I guess is due to it being a different model, right? After receiving this error I did some googling and found on a few sites that I should wipe data, system, cache & dalvik cache to resolve this. I did this and tried to flash it again, with the same error. Now my phone is stuck on the "warning bootloader unlocked screen" I can boot into fastboot mode, but is there any official Motorola images for my device anywhere? I have had a look online and cant find anything. :crying:
Any help would be much appreciated.
Thanks
Click to expand...
Click to collapse
Hi, I have facing this problem too on my XT1063. My phone do boot to system but all the app are getting FCs, so I decided to flash another ROM like usual and All of this give me that "Error executing updater binary in zip", so I trie to wipe AND format all partition from TWRP and FASTBOOT with no success. Via Fastboot says: "File system type raw not supported." So I cant change to a new ROM, I cannot even flash other recovery....
So if you guys find a solution of this problem very users like me will be very thankful.

[Q] Moto X 2014 5.0.2 update broke my phone

Hello everybody,
I'm new, I hope someone can help me here ... I'm quite sure somewhere on these forums there must already be answers for my problem but I'm too dumb to find them.
I have the European? 2014 Moto X (not sure how to get the exact model now?!)
Unlocked bootloader, rooted.
Everything was fine, except today I got the 5.0.2 (?) OTA update ...
I didn't want to do it, but it kept asking. The moment I pressed "don't ask again" the phone rebooted
and now it's stuck at the white bootup screen (Motorola logo)
I somehow managed to get into the fastboot? mode once, by somehow pressing buttons at startup ... but, well
My two questions are:
1. Can I still backup my data, photos, textfiles, etc etc
2. How do I go back to a working system. (maybe without loosing my data)
Please tell me if it's possible, and how ... or please push me into the right directions.
But as I'm half panicking detailed instructions would be so fantastic.
Personally, how I would recover data, is boot to fastboot and flash TWRP again (since you indicated you were unlocked boot loader). In TWRP, plug in the device to a computer via USB and your files will be there. Then you can reflash the stock firmware and be good to go. If you are comfortable flashing the firmware through fastboot, you can choose to not wipe data and you should be all set.
It may be worth trying just clearing the cache and seeing if you can boot.
Sent from my Moto X 2015 Pure Edition using Tapatalk
xKroniK13x said:
Personally, how I would recover data, is boot to fastboot and flash TWRP again (since you indicated you were unlocked boot loader). In TWRP, plug in the device to a computer via USB and your files will be there. Then you can reflash the stock firmware and be good to go. If you are comfortable flashing the firmware through fastboot, you can choose to not wipe data and you should be all set.
It may be worth trying just clearing the cache and seeing if you can boot.
Click to expand...
Click to collapse
Hey! Thanks a lot!
I did fastboot boot twrp, and managed to backup my data on the internat storage! Yeah! Thanks!! <3
Now to part 2, I tried to wipe the cache partition in TWRP, but it doesn't help; when I reboot it still only shows the white logo..
Should I wipe other partitions aswell? (davikcache?)
If there's a way without loosing the phone setup, it would be great.
(Installed apps ... open tabs in firefox etc ...)
I also have a "online nandroid" backup, I think from back then, right after I rooted.
Would I restore the system.img from there?
Will this remove installed apps?
Or should I restore all partitions made by online nandroid backup?!
(I thought this would be better than... or how would I find the right stock firmware online for my device?)
Sorry for being such a beginner!!!!
psssss said:
Hey! Thanks a lot!
I did fastboot boot twrp, and managed to backup my data on the internat storage! Yeah! Thanks!! <3
Now to part 2, I tried to wipe the cache partition in TWRP, but it doesn't help; when I reboot it still only shows the white logo..
Should I wipe other partitions aswell? (davikcache?)
If there's a way without loosing the phone setup, it would be great.
(Installed apps ... open tabs in firefox etc ...)
I also have a "online nandroid" backup, I think from back then, right after I rooted.
Would I restore the system.img from there?
Will this remove installed apps?
Or should I restore all partitions made by online nandroid backup?!
(I thought this would be better than... or how would I find the right stock firmware online for my device?)
Sorry for being such a beginner!!!!
Click to expand...
Click to collapse
Lollipop actually doesn't use dalvik, so that won't help. If you have a nandroid, you of course can restore to that but it would likely lose your apps/settings. You can try restoring just the system, it sort of depends on what went wrong. In my experience being stuck not booting, I generally just reflash everything. Not the most convenient but it is the most effective.
Sent from my Moto X 2015 Pure Edition using Tapatalk
xKroniK13x said:
Lollipop actually doesn't use dalvik, so that won't help. If you have a nandroid, you of course can restore to that but it would likely lose your apps/settings. You can try restoring just the system, it sort of depends on what went wrong. In my experience being stuck not booting, I generally just reflash everything. Not the most convenient but it is the most effective.
Click to expand...
Click to collapse
Hey xKroniK13x,
thanks a lot for caring!
Of course, catastrophy happened:
I did fastboot boot twrp and tried to restore system from there, didn't work so I restored system _and boot from my nandroid backup there
guess this was very stupid because
Now my phone boots right into the fastboot mode, and I can't fastboot boot TWRP anymore,
it says "incomplete boot image for booting"
partition sizes wrong, etc etc ...
what I did now was flashing TWRP, at least this worked and I can boot it from the phone now.
So, please, one more time help (for a very stupid user ):
1. I guess keeping my apps and settings is out of discussion now, haha
But is there a way, with unlocked bootloader, TWRP installed to go back to stock?
2. Now ... given my phone is not completely broken, I just thought about installing CM?!
Would this be recommended? is it working fine?
I'm just thinking about it, because with Cyanogenmod I won't have problems like this in the future, right?
(OTA updates destroying my phone because of root....)
Whoa, I'm sorry for posting this here, but ... :angel:
psssss said:
Hey xKroniK13x,
thanks a lot for caring!
Of course, catastrophy happened:
I did fastboot boot twrp and tried to restore system from there, didn't work so I restored system _and boot from my nandroid backup there
guess this was very stupid because
Now my phone boots right into the fastboot mode, and I can't fastboot boot TWRP anymore,
it says "incomplete boot image for booting"
partition sizes wrong, etc etc ...
what I did now was flashing TWRP, at least this worked and I can boot it from the phone now.
So, please, one more time help (for a very stupid user ):
1. I guess keeping my apps and settings is out of discussion now, haha
But is there a way, with unlocked bootloader, TWRP installed to go back to stock?
2. Now ... given my phone is not completely broken, I just thought about installing CM?!
Would this be recommended? is it working fine?
I'm just thinking about it, because with Cyanogenmod I won't have problems like this in the future, right?
(OTA updates destroying my phone because of root....)
Whoa, I'm sorry for posting this here, but ... :angel:
Click to expand...
Click to collapse
If you've been contemplating installing a ROM, now would be a good time to do so. Just remember to wipe the data on the phone even though it doesn't boot. And CM OTA shouldn't cause issues like this, it just flashes the zip file in your recovery. Doesn't care about root or anything of course. Otherwise, if you'd like to do stock, just use MDM to get the firmware and flash away. Hope this helped!
Sent from my Moto X 2015 Pure Edition using Tapatalk
Hi !
I have exactly the same problem.
Can you tell us how you did to fix the bootloop ?
Thank you
benjo22 said:
Hi !
I have exactly the same problem.
Can you tell us how you did to fix the bootloop ?
Thank you
Click to expand...
Click to collapse
Try clearing your cache in a recovery/fastboot, or reflash the firmware! No guarantee the cache will fix it, but sometimes it will.
Sent from my Moto X 2015 Pure Edition using Tapatalk
Thank you for your help.
Clearing the cache doesn't work, so I'm searching for others ways...
Can you tell me how to flash the firmware with adb ?
Thanks
Edit : I have an European version
benjo22 said:
Thank you for your help.
Clearing the cache doesn't work, so I'm searching for others ways...
Can you tell me how to flash the firmware with adb ?
Thanks
Edit : I have an European version
Click to expand...
Click to collapse
That is answered in the FAQ thread... It is a guide for Moto G but it is applicable for this device too. http://forum.xda-developers.com/showthread.php?t=2876769
Sent from my Moto X 2015 Pure Edition using Tapatalk
@xKroniK13x
Hey, thanks for somehow guiding me through this :victory:
MDM didn't work, so I just went for the CM 12.1 nightly.
I also had concerns because in my attempts to clear cache etc etc I had "wrong partition size" etc etc
But CM installed without problems!
(Just one more question- there can't be any problems in the future because of messed up partitions, right? Does CM fix this by installing? Or should I stop caring, if it works, it works, right?!)
In fact, CM runs great, fantastic on my phone.
I lost some app data, and most annoyingly my SMS, but ...
Other than that, I'm really happy with CM :laugh:
@benjo22
Hey, I tried to fix it by clearing cache partitions from a fastboot TWRP (I don't know how you call it, I just booted TWRP without installing it)
This didn't work, so I tried to restore a nandroid backup,
but this made it even worse. (partition errors, only fastboot mode, etc etc)
Just booting with TWRP without installing also didn't work anymore,
so I put TWRP on the phone, which luckily worked, downloaded CM 12.1, installed it via TWRP,
never did it before, but I was lucky, it seems like it worked great!
Even kept my "SD CARD" data, but lost apps and some data ...
So I didn't fix the bootloop, but I hope I made it better, futureproof...
Glad you got up and running. CM shouldn't cause any future issues as far as partitions and such.
Sent from my Moto X 2015 Pure Edition using Tapatalk

Completely wiped OS during reset :(

Hello, I'm new to these forums and have come to them under some unfortunate circumstances.
I went to update my device (MOTO G 2014) and had an error (cant remember what it said), anyway I rebooted my device and it wouldnt load after the 'BOOT LOADER UNLOCKED' warning screen. I went into TWRP and went to reset my device and wiped the system. (feel like an idiot, then again I am..) So then I downloaded all the USB drivers and Android SDK along with adb+fastboot and attempted to sideload. during the sideload I got this error..
* failed to write data 'protocol fault (couldn't read status): Invalid argument' *
EDIT: the error is no showing up at * failed to write data 'protocol fault (no status)
I have swapped USB ports and tried a different USB cable, does anybody have any tips or do I have a paperweight on my hands?
Thanks in advance
Flash stock firmware.
motofirmware.center
Sent from my XT1031
If I understand, right now you have wiped system, and bootloop in Motorola logo.
If you can boot in recovery, then transfer a ROM to an microsd and flash from there.
UPDATE: managed to put 3 ROMs onto my sdcard but only one of them actually allows me to install it, but after I install it I am stuck at the boot screen, guessing I got the wrong ROM for my model, cm doesn't flash, it just says 'Failed!' and so does the most recent one from the website previously linked. Any tips? Model is XT1072. I have been sat at the boot screen for around 15-20 minutes, is it taking so long because of me clearing the dalvik cache?
PJT95 said:
UPDATE: managed to put 3 ROMs onto my sdcard but only one of them actually allows me to install it, but after I install it I am stuck at the boot screen, guessing I got the wrong ROM for my model, cm doesn't flash, it just says 'Failed!' and so does the most recent one from the website previously linked. Any tips? Model is XT1072. I have been sat at the boot screen for around 15-20 minutes, is it taking so long because of me clearing the dalvik cache?
Click to expand...
Click to collapse
Lemme guess u tried to flash "titan" CM and not "thea" one?
LuK1337 said:
Lemme guess u tried to flash "titan" CM and not "thea" one?
Click to expand...
Click to collapse
I have tried both, both are returning the same error
"E: error executing updater binary in zip"
Is this something to do with my TWRP being at v2.7.1.1?
PJT95 said:
I have tried both, both are returning the same error
"E: error executing updater binary in zip"
Is this something to do with my TWRP being at v2.7.1.1?
Click to expand...
Click to collapse
http://forum.xda-developers.com/mot...recovery-twrp-2-8-6-0-touch-recovery-t3088800
get this recovery.
LuK1337 said:
http://forum.xda-developers.com/mot...recovery-twrp-2-8-6-0-touch-recovery-t3088800
get this recovery.
Click to expand...
Click to collapse
Thanks for your help and thank you to everyone else who replied to the thread. To anybody else who will maybe see this thread and who are stuck with the same errors, I fixed this by simply flashing the latest recovery using 'fastboot flash recovery [NameOfRecovery].img' then proceeded to install the ROM compatible with my device which I downloaded to my external SD Card.
Again, thanks

I think my MI8 got bricked

1. yesterday, i was using lasted PE 9.0 as my daily driver.
2. My phone got a little lag so I tried to reboot my phone but it couldn't so I hard reset it.
3. The phone got into bootloop
4. Access TWRP, it seems like my date got corrupted cause i lost all my data and internal storage show nothing
5. Tried format date but got error: Can not mount persist
6. Use MIFlash to flash the 9.6.20, 9.6.27 (global) and 9.5.9 (china) and the phone still got stuck in the MI + android logo screen.
P/s: as i checked the phone still got unlocked. i can still install TWRP in fastboot but flash any rom got error 7
Update: every TWRP i tried got bootloop and made me lost persist except this https://drive.google.com/open?id=1HiQsS5bZOKA4AV89S9CieQfphzCRSYcj
I think this is the best for fixing any errors in Android 9. After fixing u can install another TWRP
Now using PE, it seems i cant flash any MIUI
That wasn't a brick/ It was a encryption issue
Go to Wipe, Format Data, type yes, reboot to recovery, wipe system and flash any rom you want!
Glad you fixed, miui, is **** anyways, who needs it lop
huytoan9882 said:
1. yesterday, i was using lasted PE 9.0 as my daily driver.
2. My phone got a little lag so I tried to reboot my phone but it couldn't so I hard reset it.
3. The phone got into bootloop
4. Access TWRP, it seems like my date got corrupted cause i lost all my data and internal storage show nothing
5. Tried format date but got error: Can not mount persist
6. Use MIFlash to flash the 9.6.20, 9.6.27 (global) and 9.5.9 (china) and the phone still got stuck in the MI + android logo screen.
P/s: as i checked the phone still got unlocked. i can still install TWRP in fastboot but flash any rom got error 7
Update: every TWRP i tried got bootloop and made me lost persist except this
I think this is the best for fixing any errors in Android 9. After fixing u can install another TWRP
Now using PE, it seems i cant flash any MIUI
Click to expand...
Click to collapse
You can try changing all partition to f2fs (or any other format) and then changing back to ext4.
It worked for me...
Aronfjil said:
You can try changing all partition to f2fs (or any other format) and then changing back to ext4.
It worked for me...
Click to expand...
Click to collapse
Can you tell me how?
Now i just flash the twrp then flash persist again. Then everything is fine
huytoan9882 said:
Can you tell me how?
Now i just flash the twrp then flash persist again. Then everything is fine
Click to expand...
Click to collapse
Boot in to twrp Wipe/advanced wipe/select system + cache + data(one at a time) then press change or repair system file and select f2fs and continue as I mentioned before.
Updates please....

Phone keeps booting into twrp

I tried flashing evolution x 11 today, after wiping i realized i forgot to update the vendor, so i tried restoring thr backup but that didnt work so i downloaded the latest vendor and flashed it followed by the rom but it still didnt work. So i flashed an old android 10 rom but that didnt work either. Anything i do, it just keeps booting into recovery.
is formatting data gonna help?
SatouKazuma said:
is formatting data gonna help?
Click to expand...
Click to collapse
Yes. Also read this thread, mainly posts 2 & 3. It has very useful info about backup, restore, etc for encrypted phones.
format first, download latest vendor for your phone https://downloads.akhilnarang.dev/MIUI/raphael/ from here. flash vendor, reboot recovery, then flash everything else.

Categories

Resources