Database Info

Error installing new Xposed on 3.1

So I saw that an official version of Xposed was posted for 5.1. I tried flashing the zip like in the instructions but I keep getting
Code:
error executing updater binary in zip xposed-v72-sdk22-arm.zip
and bootloops. This is the replacement tablet I got from Nvidia for the recall and I unlocked the bootloader an have TWRP installed. I tried running the uninstall zip, even though it didnt have xposed installed before, but that didn't work. I'm tempted to just factory reset and try again but I'd like to get it working with my current settings before resorting to that if possible. I also had this issue with romracer's port of xposed. What else could I do to get it to work?

Error with bliss pop and cm 12
I know this is an older thread but I have recently tried to root and install a custom rom and I get the same error. I have the most current version of TWRP flashed and I have looked up others who have installed both CM 12 and bliss pop, to follow their steps. For example formating the casch and system before install, and every time I get the same error. What am I doing wrong? Any help would be greatly appreciated.

some more Information? any errortext?

Sorry I didn't explain that, it's the same error as the first post. "Error executing updater binary in zip" then it will list the path of the zip with the rom I'm trying to install.

Unable to install MIUI rom using TWRP on Xiomi Redmi 1s

I have been using the Armani rom for my redmi 1s for quite some time.Recently, I started facing a problem of process lagging which isn't getting fixed on installing all the updates so i decided to install MIUI again.
I went to downloads and downloaded the global MIUI rom 'V7.5.1.0.KHCMIDE'(MIUI7) and placed it on my USB Drive, connected it and flashed it using TWRP recovery. It shows me an error "error executing updater binary in zip" . I had faced the same problem when flashing an older version of a MIUI rom. I also tried checking the verify zip before flashing in twrp menu but still no success. I want to get back to MIUI. Kindly help me in overcoming this problem.
Thanks

sar1097 said:
I have been using the Armani rom for my redmi 1s for quite some time.Recently, I started facing a problem of process lagging which isn't getting fixed on installing all the updates so i decided to install MIUI again.
I went to downloads and downloaded the global MIUI rom 'V7.5.1.0.KHCMIDE'(MIUI7) and placed it on my USB Drive, connected it and flashed it using TWRP recovery. It shows me an error "error executing updater binary in zip" . I had faced the same problem when flashing an older version of a MIUI rom. I also tried checking the verify zip before flashing in twrp menu but still no success. I want to get back to MIUI. Kindly help me in overcoming this problem.
Thanks
Click to expand...
Click to collapse
I don't think You can't flash stock ROM via twrp .twrp allow installing of custom things(custom ROM,kernel etc...) . if you want to get back to miui try something along the line of fastboot .

Problems with flashing ROM with TWRP

Hey guys,
So for a couple of hours I've tried quite a few of guides, but I can't fix my problem.
I'm trying to flash the stock ROM from Oneplus, but I get an error that says the following (just typing everything so I don't miss anything for you guys)
Installing '/sdcard/Oneplus_Bacon_OxygenOS-201601190107.zip'
Checking for MD5 file
Skipping MD5 check: no MD5 file found
This package is for "Oneplus" devices, this is a "bacon"
E:Error executing updater binary in zip '/sdcard/Oneplus_Bacon_OxygenOS-201601190107.zip'
Error flashing zip '/sdcard/Oneplus_Bacon_OxygenOS-201601190107.zip'
Updating partition details..."
I currently have no OS on. When I go to the Reboot button and press any of the buttons there, it firstly comes up saying that I have no OS installed. When clicking OK to that, it comes up with a message that my system is not rooted. I have an option to "Do Not Install" and the "Swipe to Install". The same thing happens no matter what I press (the phone just restarts instantly"
I'm running TWRP v2.7.0.0
Any help is greatly appreciated

Using TWRP to install stock rom's
In most cases TWRP cannot install "Stock" roms, mostly due to an issue with "updater scripts." If you want to use the Stock rom than you'll have to go back to the Stock recovery.
Side note: I wanted to use OxygenOS on mine; however, I wanted to keep it rooted so I found a "TWRP safe" version of OxygenOS online. Be cautious if you attempt that because you'll more than likely lose functionality of your Sim/Radio (will have to flash a baseband in the recovery) if you decide to flash another custom Rom over OxygenOS.

Use oneplus one flashtool or bacon toolkit to flast stock rom. Find in tools sections for flashtools

Error 7 on TWRP while Installing Lineage OS on Redmi Note 3 Kenzo

I have downloaded the latest official LineageOS build ( lineage-14.1-20170705-nightly-kenzo-signed.zip) for the Redmi Note 3 Kenzo. Then I tried to install this ROM from TWRP (3.0.2-2) on my Redmi Note 3 kenzo, and I got the following error message:
Code:
assert failed : xiaomi.verify_modem("MSM8976.LA.1.0.c3-30041-STD.PROD-1.77504.1.83742.1") == "1"
update process ended with error 7
I did some research on this and found out that a lot of others faced the same and one of the solutions for this is to install latest Dev Build of MIUI, which I did (MIUI 7.7.6 Global Beta) before flashing Lineage, but still failed.
From some other source, I got another solution stating that I should try by removing the assert check from the update-script in LineageOS package (zip) , but I am not sure if it will be harmless or not.
What should I do to successfully flash my device with the latest Lineage (or RessurectionRemix). I am stuck for last 2-3 days. It would be great if I am provided with some thorough procedures as I am kind of new to this whole "flashing custom rom" things.

HostileSage said:
I have downloaded the latest official LineageOS build ( lineage-14.1-20170705-nightly-kenzo-signed.zip) for the Redmi Note 3 Kenzo. Then I tried to install this ROM from TWRP (3.0.2-2) on my Redmi Note 3 kenzo, and I got the following error message:
I did some research on this and found out that a lot of others faced the same and one of the solutions for this is to install latest Dev Build of MIUI, which I did (MIUI 7.7.6 Global Beta) before flashing Lineage, but still failed.
From some other source, I got another solution stating that I should try by removing the assert check from the update-script in LineageOS package (zip) , but I am not sure if it will be harmless or not.
What should I do to successfully flash my device with the latest Lineage (or RessurectionRemix). I am stuck for last 2-3 days. It would be great if I am provided with some thorough procedures as I am kind of new to this whole "flashing custom rom" things.
Click to expand...
Click to collapse
Been facing the same issue, read somewhere that flashing latest firmware will resolve that error 7 , and I flashed but nothing happened..
Looking for a way like you..

suniluv said:
Been facing the same issue, read somewhere that flashing latest firmware will resolve that error 7 , and I flashed but nothing happened..
Looking for a way like you..
Click to expand...
Click to collapse
I have removed the assert check from the script and it worked. I am using the ROM for last 2 months and it's working smmothly.

Keep getting error 7 on ROMs installation

I just got my z5 from the service centre.
I use this guide to root my phone as soon as I got it.
https://forum.xda-developers.com/xperia-z5/general/ftf-e66xx-patched-kernels-google-drive-t3630282
Then proceeded to install Resurrection remix and LineageOS.
First one gave me error 7 and the latter too.
I tried to delete the assert line in updater-script but the same problem persist.

You have to flash twrp 3.1.1 and everything will work without problem, so you are doing something wrong.

TWRP flash is already inside the guide. How would I say I get error 7 without installing TWRP?

That's kinda weird since I specifically deleted the line that checks for the device string for RR (only the AOSP / lineageOS based TWRP versions would match, so that check is kinda stupid),
in that case users need to know for sure that they have that specific device (e.g. NOT flashing Z5 compact to Z5) but the hassle is removed.
I believe I'm using the attached TWRP (it's 3.1.0 anyway),
and with that I could flash RR without problems

i will flash that TWRP again and try re-installing the ROM again

Still the same errorRIP