Error message during failed install of CM zip: assert failed: get prop ("ro.product.device") == "ovation" || get prop ("ro.build.product") = ="ovation"
Solved: See below.
When I first got my HD+, I did an SD "install" of CM 11. Then I installed CM 11 to the emmc, via CWM, per all the instructions on the xda website.
Once CM 11 was installed, I changed to TWRP 2.6.3.0. (I like being able to name the backups.)
Then I did a wipe and dropped down to CM 10.2.1. (More stable.) I did the install from TWRP.
Then I installed the fuzz kernel from TWRP.
Last, I updated to TWRP 2.6.3.0a when I couldn't get Succulent's CM 11 to install.
Okay, so tonight I wanted to do a clean install of CM 10.2.1, without gapps this time.
So I booted to recovery, did a wipe, and tried installing CM 10.2.1.(The build came direct from Cyanogen mod's website for the Ovation.)
I get an error similar to what I got when I tried to install Succulent's CM 11. Here's the error message:
assert failed: get prop ("ro.product.device") == "ovation" || get prop ("ro.build.product") = ="ovation"
I dropped back to CWM and tried installing the ROM from three different versions: CWM 6.0.4.5, 6.0.4.5b, and CWM 6.0.4.6.
I tried installing CM 10.2.1 from the internal and the external SD card.
No joy. Fortunately, a Nandroid backup beforehand and I've restored to where I was.
Any ideas what's wrong? It shouldn't be this hard. It doesn't seem that a ROM install should be Recovery Dependent . But maybe it is?
==========
Solved. leapinlar, in the thread where I originally posted this question, said to use an older version of CWM to install. Apparently some incompatibility between versions of CWM (and TWRP) and the ROM zip.
Another solution was alluded to by King200 in another forum, but it sounded arcane and hard to do. It wasn't.
Here are Windows instructions:
++++++++++
Note: This method removes the "sanity check" built into the recovery image which checks to make sure the ROM you're installing is compatible with your tablet. Obviously, flashing the wrong ROM can/will brick your tablet.
So be warned.
Since I only have one tablet that I flash CM 10.2.1 on, no problem for me. If you have more than one tablet, perhaps you should delete your hacked zip after you install, to be safe.
Okay?
But for educational purposes, here's what I did to work around the problem.
++++++++++
You do this with 7-Zip. (So install 7-Zip if you don't have it already.)
Right click on the ROM that you're trying to install.
A 7-Zip context menu opens.
Select "Open Archive."
Drill your way down to
/META-INF/com/google/android/updater-script
Right click on the updater-script and select "Edit."
Open updater-script with Notepad.
Delete the first line of code, all the way up to the first semicolon. And delete the first semi-colon as well.
Save the edited file in Notepad. You'll get a 7-zip message asking if you want to incorporate your changes back into the archive. "Yes."
Now the ROM will install with later versions of CWM or TWRP.
Note: I had to do with this with the "fuzz" kernel too.
P.S. I don't know how to read code, so I don't understand exactly what the problem here is. I peeked at the scripts. I have an "ovation" tablet. Both the ROM and the Recovery image mention "ovation" in their updater scripts. Seems like they ought to talk to each other.
Please don't do this procedure. It is dangerous. It could brick your device. And the issue is not whether you have more than one tablet, it is if you accidentally download a hummingbird (HD) zip when you have an ovation (HD+) and try to flash it to an HD+. If you remove that assert statement the HD zip will merrily install to an HD+. And you will have a real mess.
A real case happened where a Nook Color user tried to flash a Nook Tablet ROM to his Color. The assert statement which was designed to prevent that did its job and prevented it. However, another user recommended he remove the assert statement, which he did, and thus flashed the Tablet ROM to his Color. His Color ended up bricked.
NEVER REMOVE AN ASSERT STATEMENT!
There are two more safe procedures.
One, use an older version of CWM to flash the older zips.
Two, do as the procedure says by opening the archive, but don't edit the updater-script file to remove the assert line. Look in a newer zip like CM11 and extract the file 'update-binary' and copy it to the old zip replacing the old update-binary file there. Then the old zip is flashable with the newer CWM/TWRP recoveries.
Sent from my BN NookHD+ using XDA Premium HD app
Hello,
Im pretty new to this kind of stuff. So forgive me. I've Nexus 4 device, and got tired of mobile radio active bug.
Android verions 5.1.1
Looked everywhere for the fix and cried on gogole bug report page.
Now i found information about this xposed module, and mobile radio active fix on this forum.
Ive rooted my device. (confirmed with root checker app)
I had custom recovery: clockworkmod recovery v6.0.4.7 (later switched to openrecovery-twrp-2.8.5.2-mako to test and stayed on it )
From this page http://forum.xda-developers.com/showthread.php?t=3034811
i have installed XposedInstaller_3.0_alpha4.apk
App requires (red text) to flash the package, so i am putting this .zip (xposed-v75-sdk22-x86.zip) on my device and trying to flash it through recovery.
chosing it, process starts, and ill write you everything it says
(that is clockworkmod recovery log)
-- Installing /sdcard/0/xposed-v75-sdk22-x86.zip
Finding update package...
Opening update package...
Installing update...
E:Error in /data/media/0/xposed-v75-sdk22-x86.zip
(Status 255)
Installation aborted
tried many times, redownloading the file, renaming it to a.zip
same message every time.
I have also switched to
openrecovery-twrp-2.8.5.2-mako
Tried to flash it using this.
Also error:
updating partition details...
.. done
Full SELinux support is present
MTP Enabled
Installing '/sdcard/xposed-v75-sdk22-x86.zip'...
Checking for MD5 file...
Skipping MD5 check: No MD5 file found
E: Error executing updater binary in zip " /sdcard/xposed-v75-sdk22-x86.zip'
Error flashing zip ' /sdcard/xposed-v75-sdk22-x86.zip'
Updating partition details...
... done
Comment below box "FAILED" (red color)
clicked wipe cache/dalvik
reflashed and getting same error
Am i doing something wrong? Ive no idea what to do, whats the problem. Or maybe some of you had same issue and figured out how to deal with it?
Any answer appreciated.
Thank you.
~~~~~~~~~~~~~~
Out of topic question:
Does Cyanogenmod have this mobile radio active fixed? I'd just switch to it if theres no way installing xposed on my nexus 4 with stock adroid)
The Nexus 4 has an ARM processor, and you're trying to flash the zip for an x86 processor. The flash is failing in order to stop you from putting the wrong software on there.
Try again with the xposed-v75-sdk22-arm.zip file. This was explained repeatedly in the first two posts of the official discussion thread.
I can see now where i've done it wrong after re-reading that post knowing what you just told me.
Must've been some weird article about nexus 4 and its processor that led me to think my processor is 32bit and i thought its ok to use x86 file even tho it says ARM everywhere. And trusted it more over the chart in the main discussion topic.
Everything comes down to my lack of knowledge.
Thank you for your patience and help.
flashed ARM file and it worked perfectly
Topic to be closed.
Thanks again!
I checked my logs after a bunch of things failed and my SKU is coming up blank!
"
script aborted: Please use the right SKU for updating...
Device image SKU:
OTA image SKU: WW
Please use the right SKU for updating...
"
How can I make it WW again... this is causing me an impressive amount of problems.
Is this happening when you try to install stock from a custom ROM?
FruitlessPotato said:
Is this happening when you try to install stock from a custom ROM?
Click to expand...
Click to collapse
Happened then as well. However currently it is happening with the stock ROM that I restored after getting rid of the custom ROM
Let me also give a background. I was on CM13, went to go update got an error saying I needed to update my firmware in order to install. So I tried a crap ton to get stock roms to install, didnt work (SKU was blank). So I restored my original/stock rom which would not restore the data.
I am having the same issue. I have tried and fail many times to install UL-Z00T-WW-21.40.1220.1615-user.
Always with Error 7
Right now I am stuck in fastboot with no access to recover other than fastboot boot twrp.img
However when I try to reinstall lollipop It fails with another error
FruitlessPotato said:
I am having the same issue. I have tried and fail many times to install UL-Z00T-WW-21.40.1220.1615-user.
Always with Error 7
Right now I am stuck in fastboot with no access to recover other than fastboot boot twrp.img
However when I try to reinstall lollipop It fails with another error
Click to expand...
Click to collapse
Okay so a guy on Reddit told me that errors dont mean anything, you need to look at the logs and see what caused them which is done by the recovery log.
And if you have TWRP recovery on there try to flash CM12 for the zenfone. CM13 flashes for me but randomly/constantly reboots
Installing zip file '/sdcard1/UL-Z00T-WW-21.40.0.1692-user.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
script aborted: Can't install this M package (三 6月 15 00:54:43 CST 2016) L less than 20160426 build (Tue Apr 5 07:29:00 EDT 2016).
Can't install this M package (三 6月 15 00:54:43 CST 2016) L less than 20160426 build (Tue Apr 5 07:29:00 EDT 2016).
Updater process ended with ERROR: 7
I:Legacy property environment disabled.
Error installing zip file '/sdcard1/UL-Z00T-WW-21.40.0.1692-user.zip'
Updating partition details...
FruitlessPotato said:
Installing zip file '/sdcard1/UL-Z00T-WW-21.40.0.1692-user.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
script aborted: Can't install this M package (三 6月 15 00:54:43 CST 2016) L less than 20160426 build (Tue Apr 5 07:29:00 EDT 2016).
Can't install this M package (三 6月 15 00:54:43 CST 2016) L less than 20160426 build (Tue Apr 5 07:29:00 EDT 2016).
Updater process ended with ERROR: 7
I:Legacy property environment disabled.
Error installing zip file '/sdcard1/UL-Z00T-WW-21.40.0.1692-user.zip'
Updating partition details...
Click to expand...
Click to collapse
script aborted: Can't install this M package (三 6月 15 00:54:43 CST 2016) L less than 20160426 build (Tue Apr 5 07:29:00 EDT 2016).
**** that looks like you are doing CM13 and it is telling you your firmware is out of date.
So it wants you to flash the latest stock firmware.... but you and I are in the boat were our phones wont let us do that. Dude I do not know
me either, tried updating the updater-script and all but to no avail
Is your phone on Android 5.0.2?
I was trying to find ROMs that fit that version. There are definitely other custom roms then just CM
Fruitless! Download the CM13 nightly from june 14th!
Dont do the most recent.
Edit: I know this sounds sketchy and or stupid but I have a cm13 rom from june 14th that I downloaded then, it works. The CM13 from then that I downloaded today did not. I can see about uploading the one that did work if the one you download doesnt work.
after reformatting my device and flashing stock rom through twrp, i went and download the zip file with magisk manager latest version and then i fully unroot my device with full unroot of supersu. after i rebooted to twrp, i installed magisk v14 zip and this is what it tells me after i flashed it.
Installing '/sdcard/Magisk-v14.0.zip...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
************************
* Magisk v14.0 Installer
************************
- Mounting /system, /vendor, /cache, /data
- Device platform: arm
- Constructing environment
! Unable to detect boot image
- Unmounting partitions
E: Error executing updater binary in zip ' /sdcard/Magisk-v14.0.zip'
Error flashing zip ' /sdcard/Magisk-v14.0.zip'
Updating partition details...
...done
i have few questions.
1. unable to detect boot image. what do you mean by that? where can i get this boot image?
2. what's that updater binary in the zip file?
what can i do to be able to use magisk? thank you in advance
my device is oppo neo 7 android 5.1
The boot image is a part of your device's software. It's what Magisk modifies to do it's thing. If the installer can't recognise it, there's not much you can do... Except providing logs, that is.
The update binary is a part of the installer. It's the script that modifies the boot image to install Magisk on your device.
When you have these kind of errors, save the recovery log after flashing the zip (Advanced -> Copy Log) and post that (attach it or use Pastebin or similar, don't copy it directly to the post). It's so much easier to troubleshoot with proper logs.
First thing you can try is to use the latest beta and see if that works.
Didgeridoohan said:
The boot image is a part of your device's software. It's what Magisk modifies to do it's thing. If the installer can't recognise it, there's not much you can do... Except providing logs, that is.
The update binary is a part of the installer. It's the script that modifies the boot image to install Magisk on your device.
When you have these kind of errors, save the recovery log after flashing the zip (Advanced -> Copy Log) and post that (attach it or use Pastebin or similar, don't copy it directly to the post). It's so much easier to troubleshoot with proper logs.
First thing you can try is to use the latest beta and see if that works.
Click to expand...
Click to collapse
i got the log, how do i upload it here? im only using android browser.
so itried to install magisk v14 and it didnt detect bootimg but v14.5 did detect but still failed to install.
rajoholic said:
i got the log, how do i upload it here? im only using android browser.
so itried to install magisk v14 and it didnt detect bootimg but v14.5 did detect but still failed to install.
Click to expand...
Click to collapse
I guess you can't attach a file, being so new... You can upload it somewhere and provide the link or use Pastebin and provide the link/id for it.
Didgeridoohan said:
I guess you can't attach a file, being so new... You can upload it somewhere and provide the link or use Pastebin and provide the link/id for it.
Click to expand...
Click to collapse
https://dropmb.com/download/aca1616df3f0d913cb70d1f88176d9d4.html
here it is. thanks for the help
I m also facing same problem
rajoholic said:
after reformatting my device and flashing stock rom through twrp, i went and download the zip file with magisk manager latest version and then i fully unroot my device with full unroot of supersu. after i rebooted to twrp, i installed magisk v14 zip and this is what it tells me after i flashed it.
Installing '/sdcard/Magisk-v14.0.zip...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
************************
* Magisk v14.0 Installer
************************
- Mounting /system, /vendor, /cache, /data
- Device platform: arm
- Constructing environment
! Unable to detect boot image
- Unmounting partitions
E: Error executing updater binary in zip ' /sdcard/Magisk-v14.0.zip'
Error flashing zip ' /sdcard/Magisk-v14.0.zip'
Updating partition details...
...done
i have few questions.
1. unable to detect boot image. what do you mean by that? where can i get this boot image?
2. what's that updater binary in the zip file?
what can i do to be able to use magisk? thank you in advance
my device is Micromax canvas nitro a310 current android version is cyanogen mode 13
Click to expand...
Click to collapse
rajoholic said:
https://dropmb.com/download/aca1616df3f0d913cb70d1f88176d9d4.html
here it is. thanks for the help
Click to expand...
Click to collapse
That was a bit of a shady file sharing site. Anyway...
Your installed TWRP is pretty old. That might have something to do about it. Update TWRP, or you could try letting the Magisk Manager patch the boot image and then flash the patched image with TWRP. Installation instructions in the release thread.
Didgeridoohan said:
That was a bit of a shady file sharing site. Anyway...
Your installed TWRP is pretty old. That might have something to do about it. Update TWRP, or you could try letting the Magisk Manager patch the boot image and then flash the patched image with TWRP. Installation instructions in the release thread.
Click to expand...
Click to collapse
sorry bout that. i just search the google free and temporary storage online. haha! thank you for the help. I'll try what u just said
Didgeridoohan said:
That was a bit of a shady file sharing site. Anyway...
Your installed TWRP is pretty old. That might have something to do about it. Update TWRP, or you could try letting the Magisk Manager patch the boot image and then flash the patched image with TWRP. Installation instructions in the release thread.
Click to expand...
Click to collapse
how do i flash the patched boot.img with twrp? i cant find it in my sd card. it's not showing up. i already got the patched boot img
rajoholic said:
how do i flash the patched boot.img with twrp? i cant find it in my sd card. it's not showing up. i already got the patched boot img
Click to expand...
Click to collapse
Hm.... It might be that your TWRP is to old, but it should be the same procedure as when flashing a zip file except you switch to image flashing by pressing the "Image" button after going to the "Install" screen.
If that doesn't work, use fastboot (or whatever is available for your device).
Code:
fastboot flash boot patched_boot.img
Didgeridoohan said:
Hm.... It might be that your TWRP is to old, but it should be the same procedure as when flashing a zip file except you switch to image flashing by pressing the "Image" button after going to the "Install" screen.
If that doesn't work, use fastboot (or whatever is available for your device).
Code:
fastboot flash boot patched_boot.img
Click to expand...
Click to collapse
So I did what u told me and flashed the boot.img succesfully. Now after flashing that, I flashed v14 and still error in executing update binary. Same with 14.5. But this time after I saw that, I rebooted my device and found magisk manager on my phone. It says v14 installed. Is it installed already?
rajoholic said:
So I did what u told me and flashed the boot.img succesfully. Now after flashing that, I flashed v14 and still error in executing update binary. Same with 14.5. But this time after I saw that, I rebooted my device and found magisk manager on my phone. It says v14 installed. Is it installed already?
Click to expand...
Click to collapse
Yes, if you flash the patched boot image you don't have to do anything else. The Magisk Manager has already taken care of everything.
If you want v14.5 beta, you should now be able to change the update channel (in Manager settings) to beta and update. Just as a FYI, you could have done this already when patching the boot image.
Sounds like it's working now, or? Can you install modules?
Didgeridoohan said:
Yes, if you flash the patched boot image you don't have to do anything else. The Magisk Manager has already taken care of everything.
If you want v14.5 beta, you should now be able to change the update channel (in Manager settings) to beta and update. Just as a FYI, you could have done this already when patching the boot image.
Sounds like it's working now, or? Can you install modules?
Click to expand...
Click to collapse
I installed an app and gave it root permission. It looks like it's working. However the module part, I'm still unsure. When I try to add modules, the screen took me in storage. Looks like it requires me to import something? Where can I download modules?
rajoholic said:
I installed an app and gave it root permission. It looks like it's working. However the module part, I'm still unsure. When I try to add modules, the screen took me in storage. Looks like it requires me to import something? Where can I download modules?
Click to expand...
Click to collapse
First of all, don't even mention that piece of piracy software on xda. It's used to steal from developers and is not allowed here.
In the "Modules" part you can manually install modules that you've previously downloaded. If you want to install directly from the Magisk repo, you (unsurprisingly ) go to the "Downloads" section of the Manager. If you can't see "Downloads", make sure the Manager has internet access.
Didgeridoohan said:
First of all, don't even mention that piece of piracy software on xda. It's used to steal from developers and is not allowed here.
In the "Modules" part you can manually install modules that you've previously downloaded. If you want to install directly from the Magisk repo, you (unsurprisingly ) go to the "Downloads" section of the Manager. If you can't see "Downloads", make sure the Manager has internet access.
Click to expand...
Click to collapse
Sorry I didn't know. What I had in mind is that I'll give u all the details without leaving none so u know what I do and be able to help fast. Anyway, again I'm sorry. I didn't mean it.
I tried to dl greenify4magisk and I successfully download and install it. Rebooting the device now
rajoholic said:
Sorry I didn't know. What I had in mind is that I'll give u all the details without leaving none so u know what I do and be able to help fast. Anyway, again I'm sorry. I didn't mean it.
I tried to dl greenify4magisk and I successfully download and install it. Rebooting the device now
Click to expand...
Click to collapse
Sir, did you manage to install? when i tried to install log is failed.
Hallo, I hope someone in this forum can help me with a problem with my SM-T819 TWRP.
I tried to install a CustomRom without making a back-up copy and apparently I removed all details on the tablet.
The installation of TWRP was succesful, however all my recent trials to install a CustomRom failed with the following comments:
Updating partition details….
…done
Full SELinux support is present
MTP enabled
Installing zip file `/sdcard1/lineage-16.0-20181203_161503-Unofficial-gts210velte.zip`
Checking for digest file...
Updater process ended with ERROR: 7
Error installing zip file `/sdcard1/lineage-16.0-20181203_161503-Unofficial-gts210velte.zip`
Updating partition details…
…done
installing zip file `/ sdcard1/lineage-16.0-20181203_161503-Unofficial-gts210velte.zip`
Checking for digest file...
Warning: No file_contexts
Comparing TZ version TZ.BF.3.0.3-00054 to TZ.BF.3.0.3-00077
Comparing TZ version TZ.BF.3.0.3-00064 to TZ.BF.3.0.3-00077
Comparing TZ version TZ.BF.3.0.3-00067 to TZ.BF.3.0.3-00077
Comparing TZ version TZ.BF.3.0.3-00071 to TZ.BF.3.0.3-00077
assert failed: samsung.verify_trustzone ("TZ.BF.3.0.3-00054", "TZ.BF.3.0.3-00044",
"TZ.BF.3.0.3-00067", "TZ.BF.3.0.3-00071") == "1"
Updater process ended with ERROR: 7
Error installing zip file `/sdcard1/lineage-16.0-20181203_161503-Unofficial-gts210velte.zip`
Updating partition details…
… done
I have done this trial with various TWRP and Lineage varieties but in vain and always with the identical error.
The only thing I could do was via TWRP the installation of “SMT819_Deodex_Debloated Custom Rom” (based on Stock-Samsung-Firmware.
I have also tried via Odin (several versions) to apply the original firmware. The installation proceeds without error, the tablet starts,
the progress is shown on the blue screen and every time it is cancelled after 25 % and 32%. Then the tab shuts down and starts again and remains in a continous loop with the splash screen.
Well, what is the reason to install a ... REALLY REALLY OLD version like this?
Try this https://lineageos.wickenberg.nu/gts210velte/ or that https://drive.google.com/drive/folders/1VsHc9-k4LA3-n19dp6Gkvqwf0GZLTRcA depending on what you want to have, LOS 16 or 17.1