When I tried to flash Lineage OS on my device using TWRP I was met with the error mentioned in the title: Zip file is corrupt, and the installation aborted, leaving me without an installed OS. Now I managed to install back MIUI 9, but I don't like it and would still rather have Lineage. How do I check if the zip file is corrupt, preferably before installing?
asmd30 said:
When I tried to flash Lineage OS on my device using TWRP I was met with the error mentioned in the title: Zip file is corrupt, and the installation aborted, leaving me without an installed OS. Now I managed to install back MIUI 9, but I don't like it and would still rather have Lineage. How do I check if the zip file is corrupt, preferably before installing?
Click to expand...
Click to collapse
A simple CLI command in your Linux desktop will do it.
Code:
$ unzip -t insert-rom-name.zip
If it says "No errors detected in...", you're ready to go.
You can also use your favorite file archiver and use 'Test integrity' option.
Sent from my Redmi 3 using XDA Labs
Related
I tried to flash tesla rom but was unable to do so using Cwm recovery and now I am not able to flash any rom on my phone.
Whenever I try to flash it says
Symmlinks:some link failed
E:/error in /sd card
Status 7
Installation aborted..what to do
I am using a310
zain.shamsi261 said:
I tried to flash tesla rom but was unable to do so using Cwm recovery and now I am not able to flash any rom on my phone.
Whenever I try to flash it says
Symmlinks:some link failed
E:/error in /sd card
Status 7
Installation aborted..what to do
Click to expand...
Click to collapse
Short way: Try TWRP.
Longer way: uzip the rom, open META-INF/com/google/android directory. You will find a file "updater-script" . Rename that to "updater-script.txt"
With any of your favorite text editor delete line starting with “assert” to next semicolon. Most probably you'll find it at the top.
Save file. Rename back to updater-script. Replace from original. Rezip. And flash.
If none of this work may be you have tried experimenting with partitions.
In that case you need to repartition.
Hi all. I keep getting this error after rooting, installing SuperSu and TWRP. When I try to flash a ROM (any ROM), I get stuck. I've tried the latest Resurrection and CM ROMS. Will someone please help me past this last hurdle? Thank you!
I can't upload or link the screenshot but here's the info:
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
Which I have done several times.
Backup ==> select all ==> Swipe to Backup
Wipe ==> Advenced Wipe ==> /System + /Data + /Cache Confirm "Swipe to Wipe" . Try installing again ROM
maxprzemo said:
Backup ==> select all ==> Swipe to Backup
Wipe ==> Advenced Wipe ==> /System + /Data + /Cache Confirm "Swipe to Wipe" . Try installing again ROM
Click to expand...
Click to collapse
That did the trick! I put Resurrection OS on there and all is well except for finding a stable GAPPS build.
Not working for me, my device is KII-L21 on stock rom and I'm trying to install official CM13, my device is rooted and have twrp
If your device is wiped It isnt rooted.. Wipe it dont forget Cache partitions try again.
maxprzemo said:
Backup ==> select all ==> Swipe to Backup
Wipe ==> Advenced Wipe ==> /System + /Data + /Cache Confirm "Swipe to Wipe" . Try installing again ROM
Click to expand...
Click to collapse
Bro, me sirvió. Muchas gracias
It really works, thanks dude
I think it all boils down to doing a format /system.
Next time I will try that!
Edit: I was wrong, the format /data is needed.
If I don't to the reset I am one of those that always gets error 7.
unmount ->system, data, cache :good:
As I already posted at https://forum.xda-developers.com/showpost.php?p=70851854&postcount=534,
I am able to avoid the Error 7 (inconsistend data) by switching to gapps mini before installing the update.
Since the experiental build, I do the following within one TWRP session: install latest gapps mini, install the upgrade to latest lineage-nightly and reinstall latest gapps stock.
So far it works for me.
Do a clean install wiping system, data, cache and dalvik cache before flashing a new ROM is adviced, it will avoid most of problems. For the GApps, I recommend OpenGapps Pico version to install the minimal needed, then you can install the other Google apps you need from the Play Store.
Guys I need some help here. I'm running into the same TWRP error 7 situation. The phone is unlocked, and I've installed kiwi_twrp_3-21_recovery. The model of the device is Honor X5 (KIW-CL00)
I've tried flashing both ResurrectionRemix-M-v5.7.4-20161220-kiwi & lineage-14.1-20170419-nightly-kiwi-signed ROM, whether it's flashing from the phone's storage or from the SD card, both ROM are giving me the same error code.
I tried formatting the system, advance wipe function (Dalvik & Cache & Data & System), now I don't even have the default factory ROM on my phone, but I'm still getting the error 7 code.
Please help. Thanks in advance.
U need to edit updater script to remove assert for device check
Error7 and then "could not find meta inf..."
Huawei KIWI Honor 5x
KIW-L21 EMUI 3.1
I installed
TWRP3.0.2-0 lineage-14.1-20170607-nightly-kiwi-signed.zip ->Error 7
then
cm-13.0-20160904-NIGHTLY-kiwi.zip and cyanogen recovery the same -> Error 7
Error 7 and if I try to delete assert, the next message is "could not find meta inf/com/google/android/update-binary"
My last problem
If I unzip and zip without change anything the Install message is "could not find..." I try it whit Linux 16.4 Win10 Win7 and 7Zip. all the same.
I can not change the updater-script without unpacking the File
Can anybody Help
robert_web said:
Huawei KIWI Honor 5x
KIW-L21 EMUI 3.1
I installed
TWRP3.0.2-0 lineage-14.1-20170607-nightly-kiwi-signed.zip ->Error 7
then
cm-13.0-20160904-NIGHTLY-kiwi.zip and cyanogen recovery the same -> Error 7
Error 7 and if I try to delete assert, the next message is "could not find meta inf/com/google/android/update-binary"
My last problem
If I unzip and zip without change anything the Install message is "could not find..." I try it whit Linux 16.4 Win10 Win7 and 7Zip. all the same.
I can not change the updater-script without unpacking the File
Can anybody Help
Click to expand...
Click to collapse
Did you try this?
Backup ==> select all ==> Swipe to Backup
Wipe ==> Advenced Wipe ==> /System + /Data + /Cache Confirm "Swipe to Wipe" . Try installing again ROM
robert_web said:
Huawei KIWI Honor 5x
KIW-L21 EMUI 3.1
I installed
TWRP3.0.2-0 lineage-14.1-20170607-nightly-kiwi-signed.zip ->Error 7
then
cm-13.0-20160904-NIGHTLY-kiwi.zip and cyanogen recovery the same -> Error 7
Error 7 and if I try to delete assert, the next message is "could not find meta inf/com/google/android/update-binary"
My last problem
If I unzip and zip without change anything the Install message is "could not find..." I try it whit Linux 16.4 Win10 Win7 and 7Zip. all the same.
I can not change the updater-script without unpacking the File
Can anybody Help
Click to expand...
Click to collapse
Pleasw upgrade to TWRP 3.1.1
Sent from my Honor 8 using XDA Labs
robert_web said:
Huawei KIWI Honor 5x
KIW-L21 EMUI 3.1
I installed
TWRP3.0.2-0 lineage-14.1-20170607-nightly-kiwi-signed.zip ->Error 7
then
cm-13.0-20160904-NIGHTLY-kiwi.zip and cyanogen recovery the same -> Error 7
Error 7 and if I try to delete assert, the next message is "could not find meta inf/com/google/android/update-binary"
My last problem
If I unzip and zip without change anything the Install message is "could not find..." I try it whit Linux 16.4 Win10 Win7 and 7Zip. all the same.
I can not change the updater-script without unpacking the File
Can anybody Help
Click to expand...
Click to collapse
U need to edit and repack everything . And do remember that if u mess a single letter it will give an error
Thanks
Sure I wipe advanced by every attempt.
Twrp 3.1.1 the same problem.
But you have right, the Solution for me is not to unzip and zip the file for delete the "assert". Only the way to edit without unpack the File in the Ubuntu "ARCHIVMANAGER" works.
Now it is installed but now I am in a bootloop But this is an other Problem. One step after another.
robert_web said:
Thanks
Sure I wipe advanced by every attempt.
Twrp 3.1.1 the same problem.
But you have right, the Solution for me is not to unzip and zip the file for delete the "assert". Only the way to edit without unpack the File in the Ubuntu "ARCHIVMANAGER" works.
Now it is installed but now I am in a bootloop But this is an other Problem. One step after another.
Click to expand...
Click to collapse
try again by making a clean flash
robert_web said:
Thanks
Sure I wipe advanced by every attempt.
Twrp 3.1.1 the same problem.
But you have right, the Solution for me is not to unzip and zip the file for delete the "assert". Only the way to edit without unpack the File in the Ubuntu "ARCHIVMANAGER" works.
Now it is installed but now I am in a bootloop But this is an other Problem. One step after another.
Click to expand...
Click to collapse
So , plz upload the updater-script here . I will edit and forward u . Later repack everything as is, lets see if that works . If not , i will build a rom for u especially
Thanks its work fine now. It was my fault, I updated from Lollipop not from Nougat. So I used Huawei Firmbootextraktor extract system.img cust.img recovery.img and boot.img and on my SD I copy ../dload/update.app version B140 Android 5.1.1. Then the Handy started I updated EMUI 4.0 and Android 6.1. Now works my Handy with all zip files where I delete the asserts.
Maybe was the problem, in the assert is wrote "kiwi" and my Handy is a "KIW-L21"
1. My Redmi 5 Plus/Redmi Note 5 India is rooted, using TWRP and Magisk
2. I would like to know if there is a way that recent updates under downloaded_ROM can be flashed using a third party application such as Flashify?
3. I have come to this decision because when I tried to reboot device for installing recently updates, my device enters the TWRP recovery only find nothing in there, which is annoying. Root cause for this mess is that Xiaomi's fastboot rom downloads page is download, which would usually be my go to method after all. Using Mi Flash Tool, and then a few command types re-root the recently updated mobile phone.
Please guide me!
If I understood well if twrp it´s not recognicing (not really, only it can´t access) your data partition you need to format data at first time after to unlock and install a custom recovery in order that twrp can access to your storage directory.
Flashify just is capable to install boot and recovery images. Maybe you meant FlashFire, then to install it tap on + button and a menu will display with some options like Flash ZIP or OTA.
SubwayChamp said:
If I understood well if twrp it´s not recognicing (not really, only it can´t access) your data partition you need to format data at first time after to unlock and install a custom recovery in order that twrp can access to your storage directory.
Flashify just is capable to install boot and recovery images. Maybe you meant FlashFire, then to install it tap on + button and a menu will display with some options like Flash ZIP or OTA.
Click to expand...
Click to collapse
you're right, brother. I meant FlashFire, when I typed Flashfire. My bad.
I have the OTA downloaded from the official website, since the file I had in the downloaded ROM folder always returned an error as corrupt file when tried to open using Winrar. So I had to go the official site and get the same downloaded to see the contents inside.
But now, having copied the file to the downloaded ROM folder on my phone, I do not see any option as how I can choose the file to get installed. I mean there is no file explorer option given to me, rather Google Drive option. Perhaps I have to have the file uploaded once again on to my Google Drive on my device?
sengottuvel said:
you're right, brother. I meant FlashFire, when I typed Flashfire. My bad.
I have the OTA downloaded from the official website, since the file I had in the downloaded ROM folder always returned an error as corrupt file when tried to open using Winrar. So I had to go the official site and get the same downloaded to see the contents inside.
But now, having copied the file to the downloaded ROM folder on my phone, I do not see any option as how I can choose the file to get installed. I mean there is no file explorer option given to me, rather Google Drive option. Perhaps I have to have the file uploaded once again on to my Google Drive on my device?
Click to expand...
Click to collapse
Download again the file from the same site, maybe downloaded to your Google Drive is corrupted and check that the extension didn´t change from .zip to .rar or FlashFire won´t recognice it. Winrar have to be capable to open it otherway the file is corrupted.
When you are sure that is the correct file If you had a stock recovery then you can install it through update option in settings/about device/updates from miui menu
I'm trying to root my M5 (SHT-W09, C567). I have unlocked the bootloader and installed Magisk but am having problems extracting and patching the ramdisk.img file. I would appreciate anyone who could double check my steps or see if they spot my error.
Here is what I have done.
1) Using HFF, downloaded, the Update.zip file (full image), size is approximately 4 GB.
2) Copied image over to Windows laptop
3) Downloaded Huwei Image Extractor
4) Set image extractor to unknown profile
5)Under settings, unchecked verify header and file checksum
6) The extractor extracted 33 files
Here is where I need assistance, how do I proceed? Do i need to .zip the ramdisk file and then copy it over to the tablet? I've attached an image of the files that were extracted. Any assistance would be appreciated.
Thanks,
Rick
@C5Longhorn you can now select the RAMDISK.img entry from that bundle and extract it to your PC. Then you copy that file by e.g
adb put RAMDISK.img /sdcard/
onto your device. Then you need to open Magisk-Manager (which you should have already installed on your device) and seldct the RAMDISK.img from /sdcard/ and a patched_boot.img will be created. This is the file which you later on need to flash back onto your device as ramdisk.img
AndDiSa said:
@C5Longhorn you can now select the RAMDISK.img entry from that bundle and extract it to your PC. Then you copy that file by e.g
adb put RAMDISK.img /sdcard/
onto your device. Then you need to open Magisk-Manager (which you should have already installed on your device) and seldct the RAMDISK.img from /sdcard/ and a patched_boot.img will be created. This is the file which you later on need to flash back onto your device as ramdisk.img
Click to expand...
Click to collapse
Ok, i copied the file to my computer desktop, and then attached device to computer and I copied into my SD card download folder but kept getting an error when I would run Magisk that it failed.
Do I need to use adb to push the file or does it not matter how it's copied. Maybe I'm placing in the wrong folder or need to zip file.
I'll try again and screenshot the messages. I really appreciate your help.
Sent from my Pixel 2 using Tapatalk
@C5Longhorn how you copy the file to your device doesn't matter. Do you have Magisk-Manager installed? Did you select the patch option and did you choose patch boot file and did you select the RAMDISK.img as the file to be patched? What is the error message Magisk-Manager is giving you? Did you use MagiskManager-5.7.0.apk?
Yes, to all. I'll capture and post the error I'm receiving when I can get back to the tablet. Thanks again.
Sent from my Pixel 2 using Tapatalk
I finally got it. I zipped the ramdisk file, moved it to Dropbox and then downloaded it locally to the tablet. I then went through the Magisk Manager process and it created the patched file.
I'm rooted now but notice I can't open Magisk without the app closing very quickly afterwards.
Is this normal? Also, I noticed "preserve AVB 2.0/dm-verity is not checked. Should it be?
Sent from my SHT-W09 using Tapatalk
I wiped the Magisk app data and now the app will open.
Sent from my SHT-W09 using Tapatalk
If run MagiskManager - run 1..2 second - self-close : it's a bug.
The new Version is 5.8.0 and i hope it's debuged.
The Bug is a optical Problem, root work.
Can version 5.8 be installed without losing root or do you have to repush the patched file again?
Sent from my Pixel 2 using Tapatalk
I installed 5.8 Magisk Manager and did not have to reload ramdisk image file.
Sent from my SHT-W09 using Tapatalk
2 Way for install Magisk
Way 1 : the device is new and TWRP is not available
download your build, extract "ramdisk.img" and copy on device (example: to "download")
download MagiskManager.App (actual 5.8.0), install, run and let MM modify the boot.img (in OREO is inside ramdisk.img)
fastboot flash ramdisk patched_boot.img
Way 2 : install "twrp_p10_0.1.img"
fastboot flash recovery_ramdisk twrp_p10_0.1.img
boot to recovery (TWRP) and TWRP-Install Magisk-v16.0.zip (actual)
this 2 way work on my device CMR-AL09 8.0.0.161(C432)
i use way 1 if device new on market and twrp not available
if twrp available i use way 2
the core-question is : the build from your device
extract from your-build full-update "ramdisk.img"
All Huawei/Honor with OREO have the same OS, but the build is different
HI,
I would like to update my mediapad to the latest update available.
However, you can't update through the official updater when you're root.
Can i flash back the original ramdisk.img and do the official update, then root it back with the new ramdisk.img patched ?
Tanogeek said:
HI,
I would like to update my mediapad to the latest update available.
However, you can't update through the official updater when you're root.
Can i flash back the original ramdisk.img and do the official update, then root it back with the new ramdisk.img patched ?
Click to expand...
Click to collapse
Normally when there are changes on the ramdisk.img a full update image will be installed by the OTA update process. Your proposed way will be probably sufficient to get only the delta update.
I have a Samsung Tab 2 with TWRP 3.3 installed. I wanted to try out some old jellybean roms but they didnt support my device codename so i edited updater-script to fix the issue. I did the same thing a year ago using winrar to make it into a zip again and the edited rom flashed with no problems but now trying the same thing with winrar or 7-zip doesnt work and gives me the "Invalid Zip File Format" error. Any way to fix this?
You try to flash the ZIP-file via ADB Sideload option from TWRP's Advanced option?
If you are facing this TWRP invalid zip file format issue, then by unpacking and re-zipping these zip files could simply fix your issue instantly.
jwoegerbauer said:
You try to flash the ZIP-file via ADB Sideload option from TWRP's Advanced option?
If you are facing this TWRP invalid zip file format issue, then by unpacking and re-zipping these zip files could simply fix your issue instantly.
Click to expand...
Click to collapse
No i copy them to my sd card and flash them from there
jwoegerbauer said:
You try to flash the ZIP-file via ADB Sideload option from TWRP's Advanced option?
If you are facing this TWRP invalid zip file format issue, then by unpacking and re-zipping these zip files could simply fix your issue instantly.
Click to expand...
Click to collapse
still doesnt work. then can i change my device codename so i dont have to edit updater-script?
Having the same problem here... fairly reputable zips Magisk and Flashify. Tried sideload and repakaging, no joy
I have the same problem in my Samsung J5 (2016).Model J510F.
I have the same problem "invalid zip file format" with Xperia Z2 and Resurrection Remix 10.
I found some possible help here. They recommend to unpack and repack the zip or install with ADB Sideload, too. Instructions for using ADB Sideload are also included.