search

ianmacd / multidisabler-samsung

Disables FBE, proca, Vaultkeeper and auto-reflash of stock recovery on Samsung Pie devices, including S10, N10, A10 - A50 and Tab A 10.1.
98 stars 49 forks source link

invaild zip file format #5

Closed moom825 closed 4 years ago

moom825 commented 4 years ago

when i go to install it it says invalid file format. im using a samsung a50 please help

ianmacd commented 4 years ago

Are you using zip file signature verification in TWRP? If so, turn it off.

evren320 commented 4 years ago

i have found the download links for multidisabler has zip file has folder META-INF not on the root folder, i have rezipped META-INF and installing that newly created zip worked without errors

ianmacd commented 4 years ago

I'm puzzled.

[ianmacd@fika /tmp]$ unzip -l =(wget -qO - 'https://forum.xda-developers.com/attachment.php?attachmentid=4991703&d=1586612172')   
Archive:  /tmp/zshk29RxF
  Length      Date    Time    Name
---------  ---------- -----   ----
        0  01-15-2019 11:35   META-INF/
        0  05-30-2018 21:01   META-INF/com/
        0  12-03-2019 12:38   META-INF/com/google/
        0  04-11-2020 11:43   META-INF/com/google/android/
     7458  04-11-2020 11:43   META-INF/com/google/android/update-binary
       28  01-21-2020 14:37   nl
---------                     -------
     7486                     6 files
bilogic commented 4 years ago

@evren320 is correct, when clicking into the ZIP, I see this

image

bilogic commented 4 years ago

@ianmacd I was using downloads from your github releases here https://github.com/ianmacd/multidisabler-samsung/releases

ianmacd commented 4 years ago

@ianmacd I was using downloads from your github releases here https://github.com/ianmacd/multidisabler-samsung/releases

I didn't know that GitHub was creating a release for each source tag, but in any case, these are not flashable files, because of the extra directory that GitHub creates inside the zip.

ianmacd commented 4 years ago

@evren320 is correct, when clicking into the ZIP, I see this

image

It seems that XDA has an issue and has cached the 2.2 release on some of its servers.

If I refresh the XDA page, the file attached to the first posting in the thread switches between 2.5 (the latest version at the time of writing) and 2.2.

bilogic commented 4 years ago

I didn't know that GitHub was creating a release for each source tag, but in any case, these are not flashable files, because of the extra directory that GitHub creates inside the zip.

I see, perhaps it can help if that was indicated. I suspect there are folks who trust the GitHub source more than XDA. :)

moom825 commented 4 years ago

I have fixed my problem but thx