Database Info

[Q] CM11 Nightlies Installation Failure

When I try to install the CM11 nightly builds as found through this thread:
http://forum.xda-developers.com/showthread.php?t=2570965
the update process fails. Below a snip ffrom the TWRP log (I've attached the complete log).
minzip: Extracted file "/system/xbin/vim"
ApplyParsedPerms: removexattr of /system/addon.d/50-cm.sh to 0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/external_sdcard/ROM/cm-11-20140101-NIGHTLY-tf300t.zip'
Error flashing zip '/external_sdcard/ROM/cm-11-20140101-NIGHTLY-tf300t.zip'
Through creative Googling I found some references to the install failing with TWRP and succeeding with CWM. However, the CWM ROM Manager tells me there is no supported recovery version for the TF300, so I have no idea which version to pick.
I should mention I may have partially broken my partition table when making nvFlash available though. I made another post about that:
http://forum.xda-developers.com/showthread.php?t=2594142
to which I was hoping to get a reply by now.
I'm hoping someone could help me out, I'd really like to try KitKat on this tablet.
Thanks!

Wrong TWRP?!
Orionos said:
When I try to install the CM11 nightly builds as found through this thread:
http://forum.xda-developers.com/showthread.php?t=2570965
t[...]
I'm hoping someone could help me out, I'd really like to try KitKat on this tablet.
Thanks!
Click to expand...
Click to collapse
Hmm, regularly the issue with TWRP for the TF300T is that you need a very specific/modified version, more often than not for the TF300T not the one from the TWRP site.
I can only recommend using this script to update to CM11, as it does all the installation/downloading/flashing for you, inlcuding the correct TWRP and CM/Omni and GAPPS.
http://forum.xda-developers.com/showthread.php?t=2579922
Hope this helps

recovery
Recheck the original post and make sure you are using the correct recovery.

buche,
Your script helped. When using that particular recovery, not only can I install KitKat, but my backups started working as well. Of course, the patched TWRP generates an error when installing CM10. Go figure.
norskyforce,
The post stated:
"To install, you need a recent CWM or other recovery."
I figured I was fine with the TWRP from the TWRP site. Apparently not.
Maybe I'll try the poster's recovery image. I'm still looking for the correct CWM to use, to see if it has more options. I miss 4ext
Thanks for the help.
Unfortunately, CM11/Omni don't appear to support my WiFi's channel 13. Took me a while to figure out why I could see all the neighbors' networks, but not my own.
And I just figured out neither CM10 or 11 supports my ASUS Connect Dock, which I use for the wired ethernet and USB. Grrr...

[Completed] Rom error [ please help ]

Today I decided to upgrade my Android 4.0 on my Samsung Galaxy S III mini to Android 5.1 ( Lollipop ).
I decided to install Cyanogenmod 12 to get Android 5.1 ( Lollipop ).
So I put Cyanogenmod 12 on my external SD-Card.
Then I installed ClockworkMod Recovery [Version 6.0.2.7 ] on my phone.
After that I did a factory reset and then I started the installation.
After 3-5 minutes,there was an error :crying:.
It says: " ApplyParsedPerms: Isetfileicon of /system/lost+found to u: object_r:system_file:s0 failed:
Operation not supported on transport endpoint
set_metadata_recursive: some changes failed
E:Error in /external_sd/Download/cm12.1_golden.nova.20150901.zip
(Status 7) Installation aborted. "
Then I tried to reboot my phone,but everytime it returns to ClockworkMod Recovery.
I searched for a solution,but I didnt find it.I tried
to do a factory reset too.
It seems like all system files are deleted because of this ROM installation.
And now I cant start my phone.
What can I do?
Please help!
Thanks.

PlzHelp04 said:
Today I decided to upgrade my Android 4.0 on my Samsung Galaxy S III mini to Android 5.1 ( Lollipop ).
I decided to install Cyanogenmod 12 to get Android 5.1 ( Lollipop ).
So I put Cyanogenmod 12 on my external SD-Card.
Then I installed ClockworkMod Recovery [Version 6.0.2.7 ] on my phone.
After that I did a factory reset and then I started the installation.
After 3-5 minutes,there was an error :crying:.
It says: " ApplyParsedPerms: Isetfileicon of /system/lost+found to u: object_r:system_file:s0 failed:
Operation not supported on transport endpoint
set_metadata_recursive: some changes failed
E:Error in /external_sd/Download/cm12.1_golden.nova.20150901.zip
(Status 7) Installation aborted. "
Then I tried to reboot my phone,but everytime it returns to ClockworkMod Recovery.
I searched for a solution,but I didnt find it.I tried
to do a factory reset too.
It seems like all system files are deleted because of this ROM installation.
And now I cant start my phone.
What can I do?
Please help!
Thanks.
Click to expand...
Click to collapse
Hello and thank you for using XDA Assist.
Sorry to hear about your trouble but fortunately there is an XDA area dedicated to the Samsung Galaxy S II Miini at http://forum.xda-developers.com/galaxy-s3-mini which would be a good starting place. I suggest you post your question with all relevant details in the friendly Q&A forum there at http://forum.xda-developers.com/galaxy-s3-mini/help where the experts familiar with your device will be best able to guide you. You could also ask wherever you found the ROM that you're attempting to install.
Good luck!

TWRP Error executing updater binary in zip

Tried to flash Sailfish OS on my moto g 1st gen using TWRP but i keep getting this error. E:Error executing updater binary in zip '/sdcard/sailfishos-falcon-release-1.1.7.28-my4.zip'
Error flashing zip '/sdcard/sailfishos-falcon-release-1.1.7.28-my4.zip'

Prymston said:
Tried to flash Sailfish OS on my moto g 1st gen using TWRP but i keep getting this error. E:Error executing updater binary in zip '/sdcard/sailfishos-falcon-release-1.1.7.28-my4.zip'
Error flashing zip '/sdcard/sailfishos-falcon-release-1.1.7.28-my4.zip'
Click to expand...
Click to collapse
No other error messages before these? Try "adb pull /tmp/recovery.log" and post the file.

_that said:
No other error messages before these? Try "adb pull /tmp/recovery.log" and post the file.
Click to expand...
Click to collapse
Sorry for the noobie question but do i post the whole log here or do i upload the file? :silly:

Known issue:
When flashing, I get the following: "E:Error executing updater binary in zip"
This is a custom recovery bug. Try restarting recovery and flashing again. Alternatively you may need to format /data (userdata) in Custom Recovery. Note: This will delete anything on internal storage - photos, music, videos etc.​

Prymston said:
Sorry for the noobie question but do i post the whole log here or do i upload the file? :silly:
Click to expand...
Click to collapse
I don't know if Junior members are allowed to attach files to posts. If not, upload it to some paste site and post the link (you'll need to remove things like "http://" to be allowed to post it).
lost101 said:
Known issue:
When flashing, I get the following: "E:Error executing updater binary in zip"
This is a custom recovery bug.
Click to expand...
Click to collapse
Unlikely - if the recovery could not run update binaries at all, someone would have noticed. Why should restarting recovery change anything? What exactly is the bug?

lost101 said:
Known issue:
When flashing, I get the following: "E:Error executing updater binary in zip"
This is a custom recovery bug. Try restarting recovery and flashing again. Alternatively you may need to format /data (userdata) in Custom Recovery. Note: This will delete anything on internal storage - photos, music, videos etc.​
Click to expand...
Click to collapse
I tried that didn't work

Prymston said:
I tried that didn't work
Click to expand...
Click to collapse
Make sure to use the following option: TWRP > Wipe > Format Data > Yes

can't post log? probably to much text?

where can i post the log? I can't post it here.

i posted the recovery.log on google drive

Prymston said:
i posted the recovery.log on google drive
Click to expand...
Click to collapse
The script expects the device name to be "falcon":
Code:
script aborted: assert failed: getprop("ro.product.device") == "falcon" || getprop("ro.build.product") == "falcon" || getprop("ro.cm.device") == "falcon"
But your TWRP version calls it "xt1032":
Code:
ro.product.name=XT1032
ro.build.product=xt1032
ro.cm.device=xt1032
Workaround: replace "falcon" with "xt1032" in updater-script inside the zip file.

New Log.

Prymston said:
New Log.
Click to expand...
Click to collapse
Looks fine. The mount error is probably because /data is already mounted, which it must be to read the zip from the emulated sdcard.

_that said:
Looks fine. The mount error is probably because /data is already mounted, which it must be to read the zip from the emulated sdcard.
Click to expand...
Click to collapse
but i get a black screen when booting sailfish os, somethings not right.

Prymston said:
but i get a black screen when booting sailfish os, somethings not right.
Click to expand...
Click to collapse
Did you get it to flash properly now?
If yes, you should try another CM12.1 nightly. I posted a working one in the Sailfish thread

k-kuchen said:
Did you get it to flash properly now?
If yes, you should try another CM12.1 nightly. I posted a working one in the Sailfish thread
Click to expand...
Click to collapse
It worked! Thank you

[Q] How to solve "Error executing updater binary zip"?

Hi
I am not sure if anyone is still reading this forum, but I recently found my old Desire S and wanted to flash a ROM to it to revive it.
But I stumbled upon several problems.
The phone has currently twrp v2.8.7.1 installed, but simply installing a rom zip file with it always delivers the same error:
E:Error exectuting updater binary in zip '/sdcard/CM-11S-UNOFFICIAL-BR1-saga.zip
Error flashing zip 'sdcard/...'
I tried several roms I found in this forum, but most of the download links seem to be offline by now. I do not really care which rom is installed. The only goal was to find one which is working and the phone can be used with it.
It is not possible to mount->sd-ext in twrp even though an sd card is installed.
Mount->data is only possible when the sd-card is inserted. If it is removed mounting data is not possible.
Yesterday I had some trouble with wiping most of the available partitions in twrp, but today it seems to work properly, except wipe->advanced->internal storage which results in the error: "Invalid partition selection"
It is probably also worth mentioning that wipe->Format Data->yes was performed, and therefore barely any data is currently on the phone.
ADB and Fastboot commands can be executed from the pc and are being processed.
That's pretty much every information I think would be beneficial to find a solution to the flashing problem.
I also found the thread "[Q] How can I install Mokee rom?" in this forum, where the same problem ("exectuting updater binary in zip ...") seems to be solved by installing a newer version of twrp. But since I think, that the installed one on my phone is the newest, I only think that I could try downgrading the recovery. Not sure if this would help, and where to find an older recovery.
Thanks in advance for any possible solutions to approach the given problem.
Edit:
I installed recovery-clockwork-touch-5.8.1.5-saga to try a different recovery. Then I pushed the rom via adb. The installation failed with:
"set_metadata_recursive: some changes failed
E: Error in /sdcard/rom.zip
(Status 7)
Installation aborted."
Edit2: SOLVED
If someone else should have similar problems:
The error message from cwm seems to indicate that the used rom is not flashable with this version of cwm.
I was able to install the ics rom aokp_saga_milestone-6-120708-2354 with cwm version recovery-clockwork-touch-5.8.1.5-saga (both can be found in the download section https://forum.xda-developers.com/showthread.php?t=1146601

Try 4ext recovery v1.0.0.6 RC3 build8.

no-verity-opt-encrypt-6.1 - Updater process ended with ERROR: 1

I'm currently trying to root my Samsung S8+ (G955FD). I've followed the TWRP guide, step by step, but I've run into a roadblock trying to flash no-verity-opt-encrypt-6.1.
I've repeated the steps from the TWRP multiple times, but every time i attempt to flash no-verify it prints:
...
Unpacking the installer...
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/no-verity-opt-encrypt-6.1.zip'
Updating partition details...
...done
Click to expand...
Click to collapse
If i attempt to install the no verity with the 'Zip signature verification' ticked, It prints the same but instead of "Updater process ended with ERROR: 1" it prints "Zip signature verification failed!".
I've tried multiple different mirrors, and verified the hash, so I'm not exactly sure what Zip signature is.
I accidentally attempted to boot into system after installing TWRP for the first time and got stuck on the boot-loop, and i assume it's still that way, in a boot-loop. I did a complete factory reset prior to attempting this. I'm 99% sure I enabled USB de-bugging in dev settings. I've tried wiping the preload partition to get rid of the "Failed to mount /preload message". I have no backup of anything. I hope I'm not leaving out any info..
P.S - I do recall getting some pretty big errors while attempting to format data partition. Here is a imgur link of what it printed.. , but after repeating the steps from TWRP, these errors are nowhere to be found.
P.P.S - At least let me know if i need to buy a new phone

I should have thought to include this, but here is the recovery.log https://pastebin.com/vRNUgNdU
Edit: Sorry for adding a new reply, i didn't realise i could edit

Lexiannn said:
I'm currently trying to root my Samsung S8+ (G955FD). I've followed the TWRP guide, step by step, but I've run into a roadblock trying to flash no-verity-opt-encrypt-6.1.
I've repeated the steps from the TWRP multiple times, but every time i attempt to flash no-verify it prints:
If i attempt to install the no verity with the 'Zip signature verification' ticked, It prints the same but instead of "Updater process ended with ERROR: 1" it prints "Zip signature verification failed!".
I've tried multiple different mirrors, and verified the hash, so I'm not exactly sure what Zip signature is.
I accidentally attempted to boot into system after installing TWRP for the first time and got stuck on the boot-loop, and i assume it's still that way, in a boot-loop. I did a complete factory reset prior to attempting this. I'm 99% sure I enabled USB de-bugging in dev settings. I've tried wiping the preload partition to get rid of the "Failed to mount /preload message". I have no backup of anything. I hope I'm not leaving out any info..
P.S - I do recall getting some pretty big errors while attempting to format data partition. Here is a imgur link of what it printed.. , but after repeating the steps from TWRP, these errors are nowhere to be found.
P.P.S - At least let me know if i need to buy a new phone
Click to expand...
Click to collapse
P.P.S - At the worst case your would only need to flash stock firmware.
You will always get the error message when your first format your data through TWRP.
It seems that the no- verity-opt-encrypt zip is causing the same issues as yours mainly on android 9 ( pie ) with other people to.
Your can repeat your TWRP proceedure but instead of using the no- verity-opt-encrypt zip use the one from this guide
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com
You will probably have to add ' quota ' to the file name.

spawnlives said:
You will probably have to add ' quota ' to the file name.
Click to expand...
Click to collapse
Sorry, but I don't fully understand what you mean by this. I literally just add the word 'quota' to the name of the .zip file? Just quota? Does it need to be in a specific order, letter case or with or without quotations?
I can't seem to find a solid answer on the thread.

Lexiannn said:
Sorry, but I don't fully understand what you mean by this. I literally just add the word 'quota' to the name of the .zip file? Just quota? Does it need to be in a specific order, letter case or with or without quotations?
I can't seem to find a solid answer on the thread.
Click to expand...
Click to collapse
I normally add after forceenrypt before the date.
Downloaded zip file
Disable_Dm-Verity_ForceEncrypt_11.02.2020
Change to
Disable_Dm-Verity_ForceEncrypt_quota_11.02.2020

Lexiannn said:
I'm currently trying to root my Samsung S8+ (G955FD). I've followed the TWRP guide, step by step, but I've run into a roadblock trying to flash no-verity-opt-encrypt-6.1.
I've repeated the steps from the TWRP multiple times, but every time i attempt to flash no-verify it prints:
If i attempt to install the no verity with the 'Zip signature verification' ticked, It prints the same but instead of "Updater process ended with ERROR: 1" it prints "Zip signature verification failed!".
I've tried multiple different mirrors, and verified the hash, so I'm not exactly sure what Zip signature is.
I accidentally attempted to boot into system after installing TWRP for the first time and got stuck on the boot-loop, and i assume it's still that way, in a boot-loop. I did a complete factory reset prior to attempting this. I'm 99% sure I enabled USB de-bugging in dev settings. I've tried wiping the preload partition to get rid of the "Failed to mount /preload message". I have no backup of anything. I hope I'm not leaving out any info..
P.S - I do recall getting some pretty big errors while attempting to format data partition. Here is a imgur link of what it printed.. , but after repeating the steps from TWRP, these errors are nowhere to be found.
P.P.S - At least let me know if i need to buy a new phone
Click to expand...
Click to collapse
i have solution brother
the problem is Twrp Use old Twrp

Abdilaahi said:
i have solution brother
the problem is Twrp Use old Twrp
Click to expand...
Click to collapse
Which version did you use?

I encountered the same issue with my old but beloved Redmi 3S. Used TWRP 3.2.3-4 (or older), that did the trick.