HELP : Error executing updater binary in zip : TWRP (SM-A500G) - Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot

Well, let me tell you, I DID see the other threads before posting this one about the topic, but believe me, none of the topics met my condition, and none solved my problem. :crying:
I have a Galaxy A5 (SM-A500G), and tried to flash CM12.1 unofficial TEMASEK version by @mygalaxya . I followed EVERY single step correctly, but when I tried to flash the ROM using TWRP, it said "Error executing updater binary in script."
I tried to rename 'a5lte' to 'a5ltedd' in updater-script in zip/META-INF/com/google/android
But, it didn't work.
Also, my stock firmware had stopped working a few days ago. The phone automatically switched off after running out of charge although I kept the charger connected throughout the night (if you understand what I'm saying ) And then, when I switched on the phone, it booted into TWRP. I chose Reboot and then System, but it just won't boot normally... It kept on rebooting into recovery mode..!! So, I finally gave up, and tried to flash CM12.1 into the phone. And, the above error came up.
What do I do? HELP...
Here's the link to the post by @mygalaxya ..
http://forum.xda-developers.com/sam...ev-help-to-create-cm12-rom-galaxy-a5-t3153129

Related

OnePLus two with NO OS and Oneplus recovery

Hey, yesterday i tried to clean flash RR ROm (already was using it) and when i flashed the rom zip file, it showed patching system image uncondtionally , and flashing file 1 of 1 for like 30 min then i turned off my device. And from then, i have been stuck with oneplus logo, sometime twrp sometime oneplus recovery https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Tried this method bcz i thought my device was bricked but the last step failed. No i again got back to twrp through fastboot method
https://forums.oneplus.net/threads/...-custom-recovery-root-efs-backup-more.345478/
And one more thing, when i am copyingthe rom files from pc to device, the progress bar goes well upto like 50% and then suddenly closes. But copied file size is same as of original. Is this the main problem?
file not getting copied properly?
Now i am in twrp and cant even start the flash proces as it now says E: error executing updater binary in zip ' ROM Name' error flashing zip.
What should i do now? Just want to turn on my phone, no matter if its RR ROM or OOS rom . Please help.
Also again went to oneplus recovery using that unbrick method and then tried to install OOS 2.2.1 using adb sideload method, but it stops at 47% everytime. What could be the reason? Should i go to service center tomorrow because from wednesday i will be having my exams and i want my phone up and running by tomorrow evening. Please help me . It's an emergency. Also asked for help at xda RR ROm forum but no such help yet .
And is my motherboard damaged ? No, right?

Motorola G2 XT1068 problem after flashing omni

Hello, i decided to open new thread because I nowhere find solution. My problem is that after flashing my moto g2 with omni 6.0.1 it get stuck on warning message (about unlocked bootloader). Now I can only get into bootloader menu, connect phone to PC (it's showing dewice as motorola dadb interface),I can only flash twrp using fastboot (fastboot boot twrp.img) and that's it. I can not flash anything permanently to the phone: any custom recovery, any rom,can't fix it with logofix.It just look like phone doesn't accept any flash. I tried also to change boot and other img but with no succes, always after any operation when I reboot phone it's get to warning message.
My phone is motorola 2G xt1068, 8gb, bootloader ver 48.87. Once I tried to flash it with retail rom from sd card via twrp 3.8.0.1 it shows that previous system was omni-titan 6.0.1 and retaildsdsall can not be flash,always shows error 7.
I wonder if I can flash it with upper version of omni: 7.0.1 to fix the problem with booting the phone.
If You could give me any advise how to solve the problem, I would be very appreciate.
Waitng for your reply Guys.
After a lot of tryes I found that anythig I do on the phone after restart it's getting to the same state, even if I manually deleted folder "Firmware", after reboot it's going back. When I prepared Moto for installing new rom using Philz recovery, all the data stay on it's place ( I mean private data like thumbnails in DCIM folder etc), nothing dissapeared. It's look like it have some copy of the system in internal storage and always after rebooting it's recovering it back, even if the system is flashed by new rom.
Have U any idea what's wrong with this phone?
Additinally I found that a lot of internal memory is busy: over 4500MB and free is only 780MB. Even after wiping everything, also formatting system.Should it be like this?
Edit: 2018-02-15
Ok, if noone could help me let's treat it as a blog.
Digging in google I found spanish site with a lot of custom roms for motorola. Now I'm trying one by one till I found the right one.
It's a pitty that Father's of the omni rom leaving me lonely in that situation, I think that they are the best of source of informations about that rom.
2018.02.19
I tried to install OmniRom 6.0.1 Homemade but on the beginning I had the infothat installation failed with error 7. So I found the solution to change the information in meta-info folder.I did it but when instalation started after "symlinkig" it stopped with error: some symlinks failed, error 7. And again I stucked.I feellike I'm very close of the solution but I need help. I'm using twrp 3.2.1.0 running via fastboot (boot twrp.img).

[Bootloop] N9005 not booting after frame (display) replacement

Hi,
as the title says, my phone is not booting anymore, after I transplanted the motherboard from a frame with a broken screen into a new frame (from china).
Abbreviations used:
RR => Resurrection Remix 5.8.5
CWM => ClockWorkMod Recovery 6.0.4.6-kitkat
TWRP => TeamWinRecoveryProject 3.2.1-1
I was using RR from the Rock Stable Setup on it before and it worked beautifully.
What happened:
I performed the mainboard-transplantation according to the iFixit guide
I held the power button to boot the phone:
It vibrated
It showed this screen for a couple of seconds
It vibrated
Back to step 1
And that until I removed power.
Then I tried to boot into recovery mode by holding the key combination on boot:
Same as above, but with this bootscreen
Then I tried to boot into download mode by holding the key combination on boot:
The warning to confirm download mode poped up and I got to see this screen.
I connected it to my PC and opened odin 3.09 and it recognized the device.
I tried to get adb and fastboot to see the device, but nothing worked. (In the old frame and before I broke the screen, it would be recognized at this stage)
I flashed TWRP with odin, odin showed the green "PASS!", but booting to recovery still failed.
I proceeded to flash a stock ROM, which had worked when I had issues with RR.
It worked, I went through the Android 5 setup process, enabled debug and connected adb.
adb saw the phone.
I rebooted to recovery and stock recovery booted correctly.
Sideloading anything with adb failed due to signature verification.
I then went back to download mode and flashed CWM successfully.
It now boots into recovery, but whenever I try to flash anything with CWM, it fails showing this screen
Or something similar (the photo comes from flashing RR 5.8.5)
I have both linux and windows properly setup and used both with adb, fastboot and odin (only windows)/heimdal (only linux).
I checked drivers and usb cables.
I opened the phone back up and checked all connections.
But I can't get any version of RR, CyanogenMod or LineageOS on there.
I've searched the internet, but people that have these kinds of problems after replacing parts of their phones, seem to only have driver issues or skipped steps in the manuals of custom ROM installations.
If you have any idea on what I could try or what I'm doing wrong or not doing, please leave an answer.
I'll keep this post updated below here:
(no updates, yet)
Thanks so much in advance
Simon
Your picture shows stock recovery not CWM .
Try flashing TWRP recovery through Odin .
I did flash TWRP and afterwards there was no recovery anymore.
When I flash CWM, I get the recovery shown in the photo.
The stock recovery has a black background and no touch controls for me.
What you saw must have been CWM.
Update: I can flash twrp-2.8.7.0-hlte-4.4.img.tar and it works. It's the only image that works, but I still can't boot into or flash any custom OS.
The only working OS I have at the moment is a stock android 5.0, which is not all that useful...
If anyone has an idea, why I can't or how I can find out what is causing it, please say so.
I can flash twrp-2.8.7.0-hlte-4.4.img.tar and it works. It's the only image that works, but I still can't boot into or flash any custom OS. )
What do you mean by ANY ??
Well, exactly that.
Regardless of what zip I flash, I end up with a bootloop.
If I flash a recovery zip, the recovery bootloops, but the OS still boots.
If I flash a custom ROM, I can still boot into recovery fine, but booting normally results in a bootloop.
The only way to get software onto my phone has been via odin and only an old CWM, Philz Touch, TWRP (Version 2.8.7.0 and below) and STOCK Android (Versions 4.3, 4.4.2, 5).
Anything else I have tried so far did not result in an error, but I couldn't boot into it either.
If you have ideas for software I can try flashing, please tell. I really have no idea how to get the damn thing to work again...
What happens when you flash correct stock rom via Odin ??
I mean that I can boot into it after flashing it via Odin.
But its terribly slow and bloated compared to ROMs like ResurectionRemix, so I don't want to use it.
AnyTimeTraveler said:
I mean that I can boot into it after flashing it via Odin.
But its terribly slow and bloated compared to ROMs like ResurectionRemix, so I don't want to use it.
Click to expand...
Click to collapse
In that case phone is OK .
Usual is that user is failing to follow instructions .
Not sure what you mean by fastboot on a N9005 .sounds like not a N9005 .
Personally with TWRP 2.8.70 i would be flashing something like .
https://forum.xda-developers.com/galaxy-note-3/development/rom-magma-nx-rom-t3508672
as its correct TWRP .
I am able to follow instructions.
Thank you very much.
I followed exactly the same procedure that has worked many times when switching between custom ROMs.
Also, the phone has a perfectly working version of Ressurection Remix installed at the time my frame broke and it did get stuck in the same bootloop after replacing the frame, even thogh the software was exactly the same.
I am looking for help analyzing the boot process and some way of capturing the kernel log when booting to determine where the error occures that traps the phone in a bootloop.
AnyTimeTraveler said:
I am able to follow instructions.
Thank you very much.
I followed exactly the same procedure that has worked many times when switching between custom ROMs.
Also, the phone has a perfectly working version of Ressurection Remix installed at the time my frame broke and it did get stuck in the same bootloop after replacing the frame, even thogh the software was exactly the same.
I am looking for help analyzing the boot process and some way of capturing the kernel log when booting to determine where the error occures that traps the phone in a bootloop.
Click to expand...
Click to collapse
Dear Mate..
Have you solved your problem? I have same problem after transplating N900 frame.
Sorry, I gave up, since I dearly needed a working phone and bought a OnePlus 3 cheaply from ebay second hand. It's been working like a charm and I threw the note into my museum after I softbricked it for the n-th time and couldn't get it out of a bootloop that didn't leave me time to go into Fastboot.
Sorry friend, but I can't help with this.
after reading a lot of similar threads, seems like the hardware is the cause of us not able to update to higher versions of twrp(& custom roms)

Bootloop after uninstalling Xposed + Firmware upgrade encountered issue

Hello,
I'm really desperate right now and would highly appreciate your help.
The background is the following:
several months ago I've flashed Cyanogenmod 13 on my Note 3 (N9005) using TWRP (via Odin). The system has been working perfectly. In addition, I was using Xposed (Version 89) without any problems. However I decided to uninstall Xposed today using its uninstaller, but I only got a error message ( I don't remember its content, it was saying something like ' can't rename... /lib'.
Well, I then tried uninstalling via recovery which resulted in a bootloop.
I watched some YT-videos explaining how to bypass Xposed in TWRP, so I went to download mode and tried installing the TWRP with stock_kernel_twrp_1120-signed-for_Odin (the file I used the first time). This step failed. After restarting my phone it's saying: 'Firmware upgrade encountered issue. Please select recovery mode in Kies & try again'.
I don't know what to do now. I simply want to install a working TWRP to save all my files and recover from the bootloop. What matters the most to me is to recover all data on the phone (videos, pictures, files etc. which unfortunately I haven't backed up).
I'm able to access download mode (home/power/volume down) but I don't know what to do to get a recovery/TWRP.
I'm not doing anything right to avoid further harm and wait for your advice. I'd be most grateful if you could help me.
Thanks in advance!
Exupery
exupery09 said:
Hello,
I'm really desperate right now and would highly appreciate your help.
The background is the following:
several months ago I've flashed Cyanogenmod 13 on my Note 3 (N9005) using TWRP (via Odin). The system has been working perfectly. In addition, I was using Xposed (Version 89) without any problems. However I decided to uninstall Xposed today using its uninstaller, but I only got a error message ( I don't remember its content, it was saying something like ' can't rename... /lib'.
Well, I then tried uninstalling via recovery which resulted in a bootloop.
I watched some YT-videos explaining how to bypass Xposed in TWRP, so I went to download mode and tried installing the TWRP with stock_kernel_twrp_1120-signed-for_Odin (the file I used the first time). This step failed. After restarting my phone it's saying: 'Firmware upgrade encountered issue. Please select recovery mode in Kies & try again'.
I don't know what to do now. I simply want to install a working TWRP to save all my files and recover from the bootloop. What matters the most to me is to recover all data on the phone (videos, pictures, files etc. which unfortunately I haven't backed up).
I'm able to access download mode (home/power/volume down) but I don't know what to do to get a recovery/TWRP.
I'm not doing anything right to avoid further harm and wait for your advice. I'd be most grateful if you could help me.
Thanks in advance!
Exupery
Click to expand...
Click to collapse
Flash TWRP 2.8.7.0 via ODIN.
if this works, then backup everything from recovery immediately.
here is the link (if you need).
https://forum.xda-developers.com/ga...ecovery-twrp-materialized-dark-light-t3153589
Now Flash a new kernel. look over here at xda for your need.
then reboot and check. pls have patience if it took long while first boot.
and pls tell if it works.
dark_phoenix said:
Flash TWRP 2.8.7.0 via ODIN.
if this works, then backup everything from recovery immediately.
here is the link (if you need).
https://forum.xda-developers.com/ga...ecovery-twrp-materialized-dark-light-t3153589
Now Flash a new kernel. look over here at xda for your need.
then reboot and check. pls have patience if it took long while first boot.
and pls tell if it works.
Click to expand...
Click to collapse
Thank you very much for your help.
I've just flashed twrp-2.8.7.0-hlte-4.4.img.tar successfully, but when trying to access recovery (volume up/home/power) it's stuck in the Samsung logo saying:
'RECOVERY BOOTING....
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery"
What to do now?
I've found different kernels:
https://forum.xda-developers.com/ga...nt/kernel-idlekernel-leankernel-fork-t3241582
and
https://forum.xda-developers.com/galaxy-note-3/development/temasek-kernel-t3395437
Which should I choose for N9005/Cyanogenmod 13? I have no idea due to lacking knowledge.
[Hlte][Purify][25.02.17][CM13.0]. sounds appropriate to me? Could you please give me an advice? Thank you!
Ok, flashing both twrp-2.8.7.0-ha3g.tar and then twrp-2.8.7.0-hlte-4.4.img.tar resulted in the herein before mentioned problem (stuck on Samsung logo).
I now flashed successfully n9005-cwm-recovery-6.0.4.4 and it's backed up everything.
I then tried uninstalling xposed via recovery with the uninstaller.zip on sdcard, but got this error message:
mv: can't rename '/system/lib/libart.so.o
rig': No such file or directory
E: Error in /data/media/0/Android/data/de.robv.android.xposed.installer/cache/downloads/framework/xposed-uninstaller-20180117-arm.zip
Any ideas how to fix it? Or do you recommend wiping everything and flashing a new ROM (e.g. MagMa NX ROM)?
exupery09 said:
Ok, flashing both twrp-2.8.7.0-ha3g.tar and then twrp-2.8.7.0-hlte-4.4.img.tar resulted in the herein before mentioned problem (stuck on Samsung logo).
I now flashed successfully n9005-cwm-recovery-6.0.4.4 and it's backed up everything.
I then tried uninstalling xposed via recovery with the uninstaller.zip on sdcard, but got this error message:
mv: can't rename '/system/lib/libart.so.o
rig': No such file or directory
E: Error in /data/media/0/Android/data/de.robv.android.xposed.installer/cache/downloads/framework/xposed-uninstaller-20180117-arm.zip
Any ideas how to fix it? Or do you recommend wiping everything and flashing a new ROM (e.g. MagMa NX ROM)?
Click to expand...
Click to collapse
ok.
you backed up your necessary data ?
if YES then go ahead and wipe everything and flash a new rom, which ever you want.
you know what. i am a huge fan of this dev.
here is this his work. awesome rom. give it a go.
https://forum.xda-developers.com/galaxy-note-3/development/rom-aspireteam-c9-pro-v2-0-t3610152
or this one if you don't want touchwiz .
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
---------- Post added at 10:43 AM ---------- Previous post was at 10:27 AM ----------
exupery09 said:
Thank you very much for your help.
I've just flashed twrp-2.8.7.0-hlte-4.4.img.tar successfully, but when trying to access recovery (volume up/home/power) it's stuck in the Samsung logo saying:
'RECOVERY BOOTING....
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery"
What to do now?
I've found different kernels:
https://forum.xda-developers.com/ga...nt/kernel-idlekernel-leankernel-fork-t3241582
and
https://forum.xda-developers.com/galaxy-note-3/development/temasek-kernel-t3395437
Which should I choose for N9005/Cyanogenmod 13? I have no idea due to lacking knowledge.
[Hlte][Purify][25.02.17][CM13.0]. sounds appropriate to me? Could you please give me an advice? Thank you!
Click to expand...
Click to collapse
FOR THIS ONE ....
i think you need to pull battery out just after successfully flashing TWRP 2.8.7.0
when ODIN flashes recovery and says passed. pull out battery immediately. don't let the phone boot/start. wait 10-20 seconds. re-insert battery and try now booting in TWRP.

SAMSUNG GALAXY NOTE 4 (dm-verity verification failed)

I’ve tried looking for solutions online, but to no avail I can’t seem to fix by myself I have recently installed LineageOS 16 , been using it for months until recently it started to slow down, and die down what i mean is the booting process takes time and after booting there is some random crashes and it reboots , I was able to solve the problem using TWRP by wiping out the cache and resetting back to factory settings, but it was taking so long to boot after and then I decided to flash it once again, started from scratch and it worked for some time until it crashed once again leaving me to unfixable bootloop, it stays on LineageOS logo, then screen dims and then just bootloops, so i decided to flash the STOCK ROM using odin which apparently worked It booted and the process was painful because every boot im doing it got slower and slower until it would be stuck at Samsung Logo and then reboots once again, so I reflashed it once again and when it booted, I was bombarded by system apps not reponsing properly, icon like ‘System UI has stopped’ and then most of the In-built app would do the same and it crashed this time, this time when it booted it is stuck to samsung logo, so i tried wiping the cache and formatting data on stock recovery and it is still stuck on boot-loop, if lucky it goes to samsung logo and just literally in that state forever, i left it for hours and it is still the same. and then when i tried booting to stock rom there was a message below that says (dm-verity verification failed), I googled it and it is a cause for tampering system files and I just couldn’t get to work it out and find a proper solution. I hope you all can help me out. Every-time i try to flash the stock rom the message is , (Installing system updates, error, goes to recovery then it has the problem below) If anyone has encountered the same problem, or has a solution I would appreciate it. Thank you.
Samsung Galaxy Note 4 (SM-N910C) treltex
A dm-verity (device mapper verification) is most likely related to a DRK (device root key) fail as well. Contrary to popular belief, flashing the Samsung official factory firmware does not fix all. As I'm sure you have already come to realize nite even flashing a previous nandroid backup resolves the issues.
There are many YouTube vids of fixing dm-verity but the comments are mixed. Some recommend using 4files with and additional file in the pit (partition information table) but that is also very risky and you could wind worse off than you already are.
Your best bet is to flash a "no opt encryt .zip" and follow the introductions. If this is successful you will need to flash the .zip with every no rom or you'll get dm-verity error. The .zip is not a permanent fix but more like a patch, so to speak. The link below is for general info and I can't vouch for the downloads provided from the site. Its best to download your .zips from XDA.
https://www.androidinfotech.com/no-verity-opt-encrypt-versions/
https://www.google.com/search?ie=UT...e=android-browser&q=xda+no-verity-opt-encrypt
There is also a force encrip .zip you could look into. Good luck
Thank you. I hope this fixes my problem.. But where do I flash it through odin or TWRP??
I tried flashing the zip i got error 1
Mr. JAVI said:
A dm-verity (device mapper verification) is most likely related to a DRK (device root key) fail as well. Contrary to popular belief, flashing the Samsung official factory firmware does not fix all. As I'm sure you have already come to realize nite even flashing a previous nandroid backup resolves the issues.
There are many YouTube vids of fixing dm-verity but the comments are mixed. Some recommend using 4files with and additional file in the pit (partition information table) but that is also very risky and you could wind worse off than you already are.
Your best bet is to flash a "no opt encryt .zip" and follow the introductions. If this is successful you will need to flash the .zip with every no rom or you'll get dm-verity error. The .zip is not a permanent fix but more like a patch, so to speak. The link below is for general info and I can't vouch for the downloads provided from the site. Its best to download your .zips from XDA.
https://www.androidinfotech.com/no-verity-opt-encrypt-versions/
https://www.google.com/search?ie=UT...e=android-browser&q=xda+no-verity-opt-encrypt
There is also a force encrip .zip you could look into. Good luck
Click to expand...
Click to collapse
I tried flashing the zip file in TWRP after installing the stock rom, and I got a Error 1 code
kenesuuu said:
I tried flashing the zip file in TWRP after installing the stock rom, and I got a Error 1 code
Click to expand...
Click to collapse
Try this, read threw the entire tread, follow the instructions. I'd alsoblike to add dm-verity and drk are some of the most difficult to solve, at least in my experience. Furthermore, I would highly recommend making a nandroid backup of all your partitions, especially EFS, boot. I'll see if I can find the no opt encrypt .zip in the meantime. I believe it was 6.0 or 6.1 .
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Error 1
https://forum.xda-developers.com/galaxy-s7/help/error-installing-verity-opt-encrypt-zip-t3436385
scroll down to
JUST WANT TO DISABLE VERITY/ENCRYPTION
https://www.google.com/amp/s/forum....azyflasher-tool-flashing-custom-t3549210/amp/
read threw the rest of the thread.
I don't believe you'll have any success on pure stock firmware. Chances are you'll need to flash a custom kernel for your specific device and/or root package. Unfortunately, theres no one size fits all when it comes to dm-verity or drk.

Categories

Resources