TWRP 3.2.1-0 for Motorola Moto X - Moto X General

I noticed that @androidlover5842 built a new TWRP for us with 3.2.1-0 and I haven't noticed any bugs while using it. This is from TWRP Builder, so it's unofficial.
The Original download can be found here: https://basketbuild.com/uploads/devs/androidlover5842/lineage_ghost/TWRP_lineage_ghost-08051822.img

[ISSUE] "this device is lineage_ghost"
Kevanness said:
I noticed that @androidlover5842 built a new TWRP for us with 3.2.1-0 and I haven't noticed any bugs while using it. This is from TWRP Builder, so it's unofficial.
The Original download can be found here: https://basketbuild.com/uploads/devs/androidlover5842/lineage_ghost/TWRP_lineage_ghost-08051822.img
Click to expand...
Click to collapse
Thanks, I installed successfully the unofficial TWRP 3.2.1-0 (TWRP_lineage_ghost-08051822.img) to my Moto X 2013 (XT1053).
But I notice my device model is now "lineage_ghost". This cause conflict with ROMs like "xpe_10.0.2_r66-20160929-ghost" or "aokp_ghost_mm_unofficial_2017-09-18_0933". Tomorrow (May16/2018) I will test the ROM "lineage-14.1-20170212-NIGHTLY-ghost" with this TWRP due right now I'm in a Chromebook.
Regards
-@JCdelValle

JCdelValle said:
Thanks, I installed successfully the unofficial TWRP 3.2.1-0 (TWRP_lineage_ghost-08051822.img) to my Moto X 2013 (XT1053).
But I notice my device model is now "lineage_ghost". This cause conflict with ROMs like "xpe_10.0.2_r66-20160929-ghost" or "aokp_ghost_mm_unofficial_2017-09-18_0933". Tomorrow (May16/2018) I will test the ROM "lineage-14.1-20170212-NIGHTLY-ghost" with this TWRP due right now I'm in a Chromebook.
Regards
-@JCdelValle
Click to expand...
Click to collapse
At the end, this TWRP changes the device name to "lineage_ghost" and then any ROM fails due the verification of device.
> I found you can add the device name into the file "updater-script" of the folder "\META-INF\com\google\android", but after test this I faced the problem with an "invalid zip file" where I found it's better to delete the first line of the same file, but the result was the same.
I already sent an email to @androidlover5842 explain this.
My solution was to install the TWRP 3.1.2.
Regards!

Mr. @androidlover5842 releases an update of this TWRP:
https://basketbuild.com/filedl/devs...ndroidlover5842/ghost/TWRP_ghost-18051856.img
Not tested by me yet, but I'll use it later. Or if someone else install it, please feed this thread with your experience.

JCdelValle said:
Mr. @androidlover5842 releases an update of this TWRP:
https://basketbuild.com/filedl/devs...ndroidlover5842/ghost/TWRP_ghost-18051856.img
Not tested by me yet, but I'll use it later. Or if someone else install it, please feed this thread with your experience.
Click to expand...
Click to collapse
That build appears to install and work just fine.

I can't tested yet due a physical problem with the micro usb port of my Moto X.

can u give me the link for twrp 3.1.2?
Thanks
JCdelValle said:
At the end, this TWRP changes the device name to "lineage_ghost" and then any ROM fails due the verification of device.
> I found you can add the device name into the file "updater-script" of the folder "\META-INF\com\google\android", but after test this I faced the problem with an "invalid zip file" where I found it's better to delete the first line of the same file, but the result was the same.
I already sent an email to @androidlover5842 explain this.
My solution was to install the TWRP 3.1.2.
Regards!
Click to expand...
Click to collapse

Related

Error executing updater binary in zip (TWRP)

I'm getting this error when trying to flash lollipop roms. I can flash Kitkat roms fine as I'm currently running xdabbeb VS982.5 1.0.0 (G3 rom), but it won't let me flash any lollipop rom. I installed twrp via the autorec program which installs 2.7.0.0 then I updated twrp within twrp with the flashable zip.
Please help
Thank you
Anyone?
Seriously no one knows? What is everyone else using that is flashing the latest 5.0.2 roms?
What am I getting this error?
Please help
Possible Fix
I've also had this problem. The only way I can seem to fix it is to also download the .md5 along with the rom itself. Just make sure its in the same folder as the rom. Everytime I have that problem with TWRP this seems to fix it. Let me know if it works for you!
Edit: Also I forgot to mention, if one isn't available to download I can help with that.
Thanks for the suggestion. I'll give it a try. If there is no. Md5 what do I do then?
All you need to do if it comes to that is download an md5 checker on your computer. Just curious, what rom are you trying to flash?
I tried resurrection remix and liquid lollipop roms. I had no issues with the initial 5.0 lollipop roms so I'm not sure what changed with 5.0.2.
So the md5 checker generates the .Md5 then you just put that on the SD card with the rom?
Resurrection remix should have an md5 on the download page right below the rom itself.
derekmt95 said:
All you need to do if it comes to that is download an md5 checker on your computer. Just curious, what rom are you trying to flash?
Click to expand...
Click to collapse
Can you point me to the program to use on my computer? Do I just load the .zip file in the program to generate the .md5sum file then put both the zip and the .md5sum file on the sdcard before flashing?
Thanks
derekmt95 said:
I've also had this problem. The only way I can seem to fix it is to also download the .md5 along with the rom itself. Just make sure its in the same folder as the rom. Everytime I have that problem with TWRP this seems to fix it. Let me know if it works for you!
Edit: Also I forgot to mention, if one isn't available to download I can help with that.
Click to expand...
Click to collapse
Nope, I downloaded the md5 file along with the zip and I'm still getting the same "error executing updater binary in zip".
Any other suggestion? How is no one else having this same issue? I'm using the latest version of TWRP 2.8.3.1 probably like most people. I don't understand.
xxNiradxx said:
Nope, I downloaded the md5 file along with the zip and I'm still getting the same "error executing updater binary in zip".
Any other suggestion? How is no one else having this same issue? I'm using the latest version of TWRP 2.8.3.1 probably like most people. I don't understand.
Click to expand...
Click to collapse
Try to reflash the TWRP.. or maybe is something wrong with the zip file
Use the TWRP compiled by blastagator
Nope, still getting same error with latest twrp.
Finally got it working. I downgraded TWRP to 2.7.0.0 and the lollipop roms are flashing fine now.
Thanks everyone for your help.
xxNiradxx said:
Finally got it working. I downgraded TWRP to 2.7.0.0 and the lollipop roms are flashing fine now.
Thanks everyone for your help.
Click to expand...
Click to collapse
How did you downgrade because I cannot seem to find a way to do it.
TheAnonymousButler said:
How did you downgrade because I cannot seem to find a way to do it.
Click to expand...
Click to collapse
just run AutoRec again and you are all set.
LG G2 cm-11 M12 : Error executing updater binary in zip (TWRP)
kashif87 said:
just run AutoRec again and you are all set.
Click to expand...
Click to collapse
Hi, I am having the same problem. Actually my LG G2 was stuck in boot loop with secure boot error. I used SRK tool to flash the partition files as well as TWRP recovery 2.8.6.1. I have wiped everything and there is no OS installed. I am stuck in TWRP recovery screen [cannot downgrade /upgrade]. I am using and OTG cable to flash the cm-11 custom ROM but it is giving me the same error. Can anyone help ?? It has been 10 days I am trying and my phone is dying please help...
Thanks in advance...
before flash 5.1.1 aosp lollipop rom u must to flash first lollipop bootstack
Hi,
I am assuming the reply was for me. Actually I am not installing lollipop. I am going for kitkat but nothing is working now. I have tried cm-10.2, cm-11 M12, cm-11 M7 but all are showing "error executing updater binary in zip". Please if someone can help me out....
Thanks is advance....
@[email protected] i think kk aosp room need jb bootleader
Hello everyone,
I am running a D802 on stock Lollipop and installed TWRP 2.8.6.0 via AutoRec. Now I booted into recovery, wiped System and Cache and got the Error message when installing CrDroid (Marshmallow 6.0.1). Now I tried installing TWRP 3.0.2.0, which succeeded and then downloaded the twrp 2.7.0.0 zip to try that as the ROM still wouldnt install. But it wont install the older TWRP. So I am asking for help to either
1) Install TWRP 2.7.0.0
or
2) Delete the getprop lines from updater-script (after I removed them I get an error 6 so i probably removed too much?)
Thank you in advance
(Guide for Error 7: http://forum.xda-developers.com/showthread.php?t=2522762)
EDIT: Someone said installing another Kernel might allow installation of the ROMs. Which Kernel could work for my phone?
EDIT 2: When flashing TWRP 2.7.0.0 it says "assert failed: run_program("/tmp/loki.sh")==0". So what exactly am I missing on my phone? Is Loki the MM Bootloader?
EDIT 3: Could it be that the build.prop was deleted when I wiped system? Would be weird if that was the cause, but I simply dont know..
Edit: Booted in Downloa Mode and flashed v30D KDZ with the 2014 LG Flashtool. Works with Stock ROM for now

[Q] error excecuting updater binary in zip with twrp

hi guys when I try to flash a rom appears the message "error excecuting updater binary in zip" someone know how to solve it?
Sorry for my bad english
Your English is fine. Check to make sure there are no spaces in the file name, and if there are, replace them with dashes or underscores. Then try running the zip again.
Strephon Alkhalikoi said:
Your English is fine. Check to make sure there are no spaces in the file name, and if there are, replace them with dashes or underscores. Then try running the zip again.
Click to expand...
Click to collapse
there is no space in the name :\ maybe can be a problem of the recovery's version ?
I mentioned it because the presence of spaces was the reason my copy of Optimized CM12 failed to install. What version of TWRP are you running?
2.8.5.0
Upgrade. 2.8.6.0 is available from the TWRP homepage (once the page comes back up), though I believe a customized copy is available for Alucard and Antares One's Optimized CM12 build in I9505 Original Android Development.
EDIT: 2,8.6.0 can be downloaded from here.
AntaresOne's TWRP will convert the system to F2FS automatically when flashing a rom. He said he was going to make it a choice in a future update. Don't know if he gotten around doing so.
GDReaper said:
AntaresOne's TWRP will convert the system to F2FS automatically when flashing a rom. He said he was going to make it a choice in a future update. Don't know if he gotten around doing so.
Click to expand...
Click to collapse
This problem started when I tried to flash cyano 12 based on 5.1.1 (by AntaresOne) before doing this everything was fine. Maybe the recovery couldn't convert system to F2FS, can be this?
Strephon Alkhalikoi said:
Upgrade. 2.8.6.0 is available from the TWRP homepage (once the page comes back up), though I believe a customized copy is available for Alucard and Antares One's Optimized CM12 build in I9505 Original Android Development.
EDIT: 2,8.6.0 can be downloaded from here.
Click to expand...
Click to collapse
Thank you, I will try it
eleonora97100 said:
Thank you, I will try it
Click to expand...
Click to collapse
It doesn't necessarily needs to be converted. It can run with the default ext4 too. Problem with converting is that it will wipe your internal storage. So that into account.
I had the binary updater issue occur on a flashable zip I made. The cause? I accidentally deleted the line that told TWRP to mount the system partition. Restoring the line solved the issue, so check the script. The developer may have accidentally missed a line.
thank you guys I upgraded the recovery and now it works fine thank you very much

Issues Flashing EAS kernel on OmniRom

Hi,
I downloaded and flashed successfully the OmniRom image on my phone this morning, but not the EAS Kernel (v2) provided by @darkobas few days ago. Everytime I try it (I download a couple of times, in case something wrong happen) I get the same error message on TWRP.
Could not find 'META-INFO/com/google/android/update-binary' in the zip file.
Error Installing zip file '/sdcard/ROMs/OmniRom/darkobas-zl1-easkernel-v2.zip'​
Do I have to use a more recent TWRP? the one I'm using is 3.0.2-0
Or is it I'm missing something?
I searched on XDA, but I didn't see anyone reporting this.. so I suppose it's a really noob issue.
Thanks for the help!!
try downloading again
Sent from my LEX720 using Tapatalk
darkobas said:
TRY THIS TWRP!
Click to expand...
Click to collapse
...
lluis.hs said:
Hi,
I downloaded and flashed successfully the OmniRom image on my phone this morning, but not the EAS Kernel (v2) provided by @darkobas few days ago. Everytime I try it (I download a couple of times, in case something wrong happen) I get the same error message on TWRP.
Could not find 'META-INFO/com/google/android/update-binary' in the zip file.
Error Installing zip file '/sdcard/ROMs/OmniRom/darkobas-zl1-easkernel-v2.zip'​
Do I have to use a more recent TWRP? the one I'm using is 3.0.2-0
Or is it I'm missing something?
I searched on XDA, but I didn't see anyone reporting this.. so I suppose it's a really noob issue.
Thanks for the help!!
Click to expand...
Click to collapse
same for me...
It worked like a charm now @darkobas! Thank you!
Working! Thanks @darkobas
if you have successfully flash the onim rom,change to "flash image" then flash the boot.img extracted from the eas kernel zip.

Lineage 15 - Vendor Image Mismatch

So this appeared today after updating my Lineage OS. I'm not that deep into custom Android stuff so i have no clue what to do regarding this, could anyone direct me please?
To be specific i'm getting this message:
A vendor image mismatch has been detected. Typically this means your vendor image is out of date. Please ensure your vendor image matches OPM2.171019.029.A1
Click to expand...
Click to collapse
I only have the OK option and after pressing it is seems the phone works normally yet I still want to resolve this.
@niirb Each months security update will come with a different vendor. So if your on the latest update of your ROM more then likely June's. You can always extract Google's firmware to get it. But usaully it gets posted somewhere in the ROMs thread. I use this site always gets updated . Flash the vendor in either fastboot or with twrp just select zip button to change to image so you can see the file in your downloads .
Exodusche said:
@niirb Each months security update will come with a different vendor. So if your on the latest update of your ROM more then likely June's. You can always extract Google's firmware to get it. But usaully it gets posted somewhere in the ROMs thread. I use this site always gets updated . Flash the vendor in either fastboot or with twrp just select zip button to change to image so you can see the file in your downloads .
Click to expand...
Click to collapse
Thank you! So this is common and I should do this once every month or did something screw up in my update and is this just the exception?
niirb said:
Thank you! So this is common and I should do this once every month or did something screw up in my update and is this just the exception?
Click to expand...
Click to collapse
You didn't break anything. This is completely normal since the LineageOS update doesn't update the vendor image.
Anyone have issue updating to June vendor img? I updated radio bootloader vendor via fastboot said it was installed but didn't tried TWRP same result says it installed but to no avail any suggestions thank you.
Glock45 said:
Anyone have issue updating to June vendor img? I updated radio bootloader vendor via fastboot said it was installed but didn't tried TWRP same result says it installed but to no avail any suggestions thank you.
Click to expand...
Click to collapse
What are you showing as wrong in the picture? Are you getting error on boot up?
Exodusche said:
What are you showing as wrong in the picture? Are you getting error on boot up?[/QUOTE Couldn't update to Build OPM6 was getting mismatch till last update but everything functioning properly
Click to expand...
Click to collapse
Glock45 said:
What are you showing as wrong in the picture? Are you getting error on boot up?[/QUOTE Couldn't update to Build OPM6 was getting mismatch till last update but everything functioning properly
Click to expand...
Click to collapse
Try this page has all the vendors. You can flash in TWRP just to get a match
Exodusche said:
Try this page has all the vendors. You can flash in TWRP just to get a match
Click to expand...
Click to collapse
Thanks I've noticed these are large so I have to extract the vendor img from the dwnld correct?
Glock45 said:
Thanks I've noticed these are large so I have to extract the vendor img from the dwnld correct?
Click to expand...
Click to collapse
No extraction they are large just download the desired vendor/s and flash.
Exodusche said:
No extraction they are large just download the desired vendor/s and flash.
Click to expand...
Click to collapse
Dwnld the opm6 flashed in TWRP still showing opm2 oh well everything is functioning so guess I'll have to leave it! Thanks for the link/help
Glock45 said:
Dwnld the opm6 flashed in TWRP still showing opm2 oh well everything is functioning so guess I'll have to leave it! Thanks for the link/help
Click to expand...
Click to collapse
Oh I get it now yeah the developer didn't change the title to represent the next month's update that's all. General rule of thumb after a week into the month updates should have the corresponding security update.
i am having the same issue, downloaded the vendor file and moved it to twrp. when i click twrp install i can not find the file, i moved the file a second time to twrp and it asked if i want to replace it, so it must be in there somewhere. i searched the files but did not find it. any idea where it is located? thanks
edit: i downloaded the vendor file directly on the phone. the file manager shows it in the phone dl file. when i open twrp/install/download it is empty?
i run sideload and get "zip file is corrupt!" this is in linux.
[email protected]:~/Desktop$ adb start-server
[email protected]:~/Desktop$ adb sideload vendor-angler-OPM6.171019.030.B1.img
Total xfer: 0.00x
dr1445 said:
i am having the same issue, downloaded the vendor file and moved it to twrp. when i click twrp install i can not find the file, i moved the file a second time to twrp and it asked if i want to replace it, so it must be in there somewhere. i searched the files but did not find it. any idea where it is located? thanks
edit: i downloaded the vendor file directly on the phone. the file manager shows it in the phone dl file. when i open twrp/install/download it is empty?
Click to expand...
Click to collapse
When you're downloading the file in the phone, it should be in /sdcard/download/ folder
But when you're navigating on TWRP, seems you're in /sdcard/twrp/install/download folder. Just go up from TWRP and see if you can see that download folder.

Trying to flash a custom rom.Noob. help plox

I was trying to flash Arrow Rom. Previously i had installed another rom which was oreo too. Can't remember its name. Steps that I followed:-
1. Wiped everything. Since i don't use this device i didn't take any backup. So i don't have any rom installed now:'(
2. Tried to flash the file. But it keeps showing error
Help plox
golu12c said:
I was trying to flash Arrow Rom. Previously i had installed another rom which was oreo too. Can't remember its name. Steps that I followed:-
1. Wiped everything. Since i don't use this device i didn't take any backup. So i don't have any rom installed now:'(
2. Tried to flash the file. But it keeps showing error
Help plox
Click to expand...
Click to collapse
You simply downloaded the wrong file, it's for Zuk Z2, not for moto g4 plus aka athene.
Please be aware what rom files for which devices you download.
strongst said:
You simply downloaded the wrong file, it's for Zuk Z2, not for moto g4 plus aka athene.
Please be aware what rom files for which devices you download.
Click to expand...
Click to collapse
Oh okay. Sorry;_;
Thank you. I will try to flash another rom.
strongst said:
You simply downloaded the wrong file, it's for Zuk Z2, not for moto g4 plus aka athene.
Please be aware what rom files for which devices you download.
Click to expand...
Click to collapse
Hi. Downloaded the Athene file this time. It started downloading normaly. But then a new error popped up. Update Process ended with signal 7.
Attaching photo again
golu12c said:
Hi. Downloaded the Athene file this time. It started downloading normaly. But then a new error popped up. Update Process ended with signal 7.
Attaching photo again
Click to expand...
Click to collapse
Error 7 leads to corrupted file. Please make sure you download it without interrupting or it will be broken.
strongst said:
Error 7 leads to corrupted file. Please make sure you download it without interrupting or it will be broken.
Click to expand...
Click to collapse
So i downloaded the rom again. Transfered it properly. Same error.(error 7)
So just to be sure. Downloaded 5 different Roms.
Same error. My friend suggested me to flash through Adb sideload. I think it flashes but not properly since my device got stucked on bootloop for around 40 minutes before i switched it off for 2 different ROMs. Ene of the day I am back to stage 1. My friend told me to instal TWRP again. But without any OS how can i do it. Please help;_;
golu12c said:
So i downloaded the rom again. Transfered it properly. Same error.
So just to be sure. Downloaded 5 different Roms.
Same error. My friend suggested me to flash through Adb sideload. I think it flashes but not properly since my device got stucked on bootloop for around 40 minutes before i switched it off for 2 different ROMs. Ene of the day I am back to stage 1. My friend told me to instal TWRP again. But without any OS how can i do it. Please help;_;
Click to expand...
Click to collapse
And your absolut sure these 5 rom files are OK and not broken? You download the correct device versions?
Which roms you have(file names)?
What twrp version(link /file name)?
You can flash twrp with twrp itself(install - > image) or with fastboot like the first time.
golu12c said:
So i downloaded the rom again. Transfered it properly. Same error.(error 7)
So just to be sure. Downloaded 5 different Roms.
Same error. My friend suggested me to flash through Adb sideload. I think it flashes but not properly since my device got stucked on bootloop for around 40 minutes before i switched it off for 2 different ROMs. Ene of the day I am back to stage 1. My friend told me to instal TWRP again. But without any OS how can i do it. Please help;_;
Click to expand...
Click to collapse
I hope you did not pause the download in between or it did not failed and you started from the failed point (It can be done in Firefox)
Check the md5 of the zip file.
Also try a different TWRP. What TWRP are you using right now??.......just tell what source you downloaded it from
Heeth21 said:
I hope you did not pause the download in between or it did not failed and you started from the failed point (It can be done in Firefox)
Check the md5 of the zip file.
Also try a different TWRP. What TWRP are you using right now??.......just tell what source you downloaded it from
Click to expand...
Click to collapse
I downloaded the TWRP from the official website version 3.2.1
Link : https://dl.twrp.me/athene/
I have a moto g4 plus 3gb/32 gb version.
golu12c said:
I downloaded the TWRP from the official website version 3.2.1
Link : https://dl.twrp.me/athene/
I have a moto g4 plus 3gb/32 gb version.
Click to expand...
Click to collapse
Wrong TWRP my friend (its a 32 bit TWRP and you need 64 bit TWRP)........strange I thought it was error 255 when we tried to install using wrong TWRP.
Download TWRP by Lyuu and backup EFS first and then flash the ROM.
Heeth21 said:
Wrong TWRP my friend (its a 32 bit TWRP and you need 64 bit TWRP)........strange I thought it was error 255 when we tried to install using wrong TWRP.
Download TWRP by Lyuu and backup EFS first and then flash the ROM.
Click to expand...
Click to collapse
Installed this twrp too. Still no good. Still same error;_;.
But when i tried installing stock rom a new error pooped up. Attaching image of that.
I thought it was successful but it got stuck on boot loop for around 30 mins so i switched off my phone :/
golu12c said:
Installed this twrp too. Still no good. Still same error;_;.
But when i tried installing stock rom a new error pooped up. Attaching image of that.
I thought it was successful but it got stuck on boot loop for around 30 mins so i switched off my phone :/
Click to expand...
Click to collapse
Try installing Stock ROM from fastboot then.
Heeth21 said:
Try installing Stock ROM from fastboot then.
Click to expand...
Click to collapse
Thank you. This worked. Finally i have a ROM ;_;. I will now try to flash custom rom. Thank you for your help
strongst said:
And your absolut sure these 5 rom files are OK and not broken? You download the correct device versions?
Which roms you have(file names)?
What twrp version(link /file name)?
You can flash twrp with twrp itself(install - > image) or with fastboot like the first time.
Click to expand...
Click to collapse
I think there was some problem with the TWRP. Not sure entirely. Yes i downloaded the correct versions of the ROMS. Downloaded 3 versions of one ROM just to be sure;_;
I am currently back to stock rom thanks to Heeth21.
I will try to flash now from the beginning.
Thank you for your help
golu12c said:
I think there was some problem with the TWRP. Not sure entirely. Yes i downloaded the correct versions of the ROMS. Downloaded 3 versions of one ROM just to be sure;_;
I am currently back to stock rom thanks to Heeth21.
I will try to flash now from the beginning.
Thank you for your help
Click to expand...
Click to collapse
I asked you about your twrp already https://forum.xda-developers.com/mo...sh-custom-rom-noob-help-t3883210/post78527551
Please make sure to read and answer the questions properly

Categories

Resources