Related
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.
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
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".
i recently unlocked bootloader and flashed lineagos 16 on the phone, after booting insantly and non stop a message saying 'Bluetooth Stopped Working' and then `Bluetooth keeps stopping`, I then tried the resurrection remix ROM and the blutooth stopped working sign didn't appeardes but Bluetooth didn't work anyways. After a bit I remembered seeing a Bluetooth partition on TWRP, and I tough that maybe something missing in there for the phone to recognize the bluetooth module, as the phone didn't showed the bluetooth adress either.
Then when I tryed to flash the stock rom back I realized I forgot to Backup, and going around on the internet I couldn't find anyone that work, or at least I couldn't flash it with the adb loader.
The Phone Model is the XT1929-6 and I don't know if it's useful but in the fastboot mde the baseband version is M636_29.59.01.96R BECKHAM_LATAM_CUST.
Everything else works without problem.
Try reflashing the Bluetooth firmware..
If all else failes then the Leveno LMSA will allow you to download & flash factory images
https://support.lenovo.com/us/en/downloads/ds101291
NOTE: it wipes userdata
Do i download the bluetooth firmware from the LMSA or where can I get it?
MadMan29729 said:
Try reflashing the Bluetooth firmware..
If all else failes then the Leveno LMSA will allow you to download & flash factory images
NOTE: it wipes userdata
Click to expand...
Click to collapse
..
Nevermind I used the LMSA and got everything working, Thanks!!
D15F16UR3 said:
..
Click to expand...
Click to collapse
........................................................
The saga starts with a successful rooting of my MI 8. After the Android Q update, the rooting was wiped out. I tried to repeat the root using the previous procedure but the TWRP could not read the file system. I tried a sideload of Magisk. This gave no errors but ended badly with no OS bootable. I could use TWRP to choose to restore the factory image. After the restore and OTA updates, everything looked ok but phone calls had an echo of my voice and the other party could not hear anything. I found a version of TWRP that could read the file system and decided to try an install of Havoc OS. After a wipe of recommended partitions, TWRP could no longer read the file system. I suspect that a format (no option to avoid) wiped out the ability to read the file system. I have now no OS, TWRP can not read the file system, and MiFlash gave no errors but does not load an OS. MiFlash was tried to install a factory ROM, only takes one second, gives a success result, but no go and the phone only has a boot loop now. I have an OTG adapter on order. I suspect I may need a different TWRP specific to Android Q. Any better options?
Update: Success! After finding a post highlighting a better version of TWRP I was able to format the encrypted folders which destroyed the data but allowed a successful install of Havoc OS. Phone is working again. Now on to troubleshooting voice issues. Below is the relevant post.
https://forum.xda-developers.com/mi...3-2-3-1110-t3869729/post78221593#post78221593
Udopia said:
The saga starts with a successful rooting of my MI 8. After the Android Q update, the rooting was wiped out. I tried to repeat the root using the previous procedure but the TWRP could not read the file system. I tried a sideload of Magisk. This gave no errors but ended badly with no OS bootable. I could use TWRP to choose to restore the factory image. After the restore and OTA updates, everything looked ok but phone calls had an echo of my voice and the other party could not hear anything. I found a version of TWRP that could read the file system and decided to try an install of Havoc OS. After a wipe of recommended partitions, TWRP could no longer read the file system. I suspect that a format (no option to avoid) wiped out the ability to read the file system. I have now no OS, TWRP can not read the file system, and MiFlash gave no errors but does not load an OS. MiFlash was tried to install a factory ROM, only takes one second, gives a success result, but no go and the phone only has a boot loop now. I have an OTG adapter on order. I suspect I may need a different TWRP specific to Android Q. Any better options?
Update: Success! After finding a post highlighting a better version of TWRP I was able to format the encrypted folders which destroyed the data but allowed a successful install of Havoc OS. Phone is working again. Now on to troubleshooting voice issues. Below is the relevant post.
https://forum.xda-developers.com/mi...3-2-3-1110-t3869729/post78221593#post78221593
Click to expand...
Click to collapse
When using Android 10 , the best method for rooting is using the patchboot method, and usually it does not require formatting your data.
tsongming said:
When using Android 10 , the best method for rooting is using the patchboot method, and usually it does not require formatting your data.
Click to expand...
Click to collapse
Thanks for the intro to the new technique. I am rooted again through TWRP but I will keep this in mind for the future.