RE: "Update Signature Verification Failed"
I've searched and read the other topics.. One person responded to someone else's question that there are "hundreds of answers on this", yet only 2-3 topics with a related subject and posts. None that say they found the solution mention the topic that held the magic solution, and topics discuss other issues being the cause which don't match my scenario...
PROBLEM:
In Android System Recovery mode on KOT49H...... and attempting to recover an ".ab" backup made via command prompt on the computer with ADB from 2012 I used with a Sony Tablet S...
Using the command prompt, the restore completes after only a minute or so, and then the phone thinks the restore was successful... Tried cmd command prompt method both via Android and Recovery.
Size is 416 MB (436,330,412 Bytes) or 426 MB in Windows. Device has lots of free space - over 2GB.
I've tried Sideloading the restore in Recovery mode.
C:\Users\User\AppData\Local\Android\android-sdk\platform-tools>adb sideload Samsung.S4.v442.2015.05.01.Backup.ab
Finding update package...
Opening update package...
Verifying update package...
E:footer is wrong
E:signature verification failed
Finding update package...
Opening update package...
Verifying update package...
E:footer is wrong
E:signature verification failed
Installation aborted.
C:\Users\User\AppData\Local\Android\android-sdk\platform-tools>adb restore Samsung.S4.v442.2015.05.01.Backup.ab
Now unlock your device and confirm the restore operation.
< click button on device to continue >
< then nothing! >
Click to expand...
Click to collapse
The backup has resided on my PC since it was created via ADB. Is it a USB-related problem? I have attempted recovery via 2 x USB cables: 1 x Premium USB 2M cable plus 1 x Cheap 1M USB cable. hmmm...
??? Ideas? The '.ab' file backup is from 8 months ago on the SAME OS version and system. It is a stock ROM.
Help! Can anyone share their '.ab' backup from a Samsung Galaxy S4 GT-i9505??? e.g. I9505XXUGNH6? (OPS?)
Thank you!
Normally you can just flash the backup with a custom recovery like TWRP.
I don't have any experience in making and restoring backups with the method you used. You could try to see if you can flash it with TWRP.
Why don't you just flash a stock rom with Odin? Are there files in the backup you need? If so, then you can just extract the files you need on your pc.
e.g. http://forum.xda-developers.com/showthread.php?t=2011811
I'm on a Nexus 6p with resurrection remix (for android 6.0.1) trying to flash back to stock 6.0.1. I've been attempting to sideload angler-ota-mtc20l-095e81f7.zip on TWRP (After wiping Dalvik, system, data, and cache) but it keeps saying "Zip signature verification failed!" in my phone and "total xfer: 1.00x" on cmd. I had a backup which I attempted to restore after this failed several times but this left me in a bootloop. Any solution would be appreciated. If you need more information just ask.
Hskom said:
I'm on a Nexus 6p with resurrection remix (for android 6.0.1) trying to flash back to stock 6.0.1. I've been attempting to sideload angler-ota-mtc20l-095e81f7.zip on TWRP (After wiping Dalvik, system, data, and cache) but it keeps saying "Zip signature verification failed!" in my phone and "total xfer: 1.00x" on cmd. I had a backup which I attempted to restore after this failed several times but this left me in a bootloop. Any solution would be appreciated. If you need more information just ask.
Click to expand...
Click to collapse
You'll have to flash the full factory image, not an OTA. You won't be able to side load or flash from recovery. You can either use ADB to flash the full image with the included flash-all.bat, or a toolkit like NRT.
v12xke said:
You'll have to flash the full factory image, not an OTA. You won't be able to side load or flash from recovery. You can either use ADB to flash the full image with the included flash-all.bat, or a toolkit like NRT.
Click to expand...
Click to collapse
I exactly have the same issue but, if I understand correctly, because my device is locked I'm unable to flash the factory image. My phone got bricked during a system update. I had this issue once and I was able to recover it with OTA sideload. But this time it doesn't work: when I do the OTA sideload it gives me the signature verification error.
How could I overcome it?
D4rkFloors said:
I exactly have the same issue but, if I understand correctly, because my device is locked I'm unable to flash the factory image. My phone got bricked during a system update. I had this issue once and I was able to recover it with OTA sideload. But this time it doesn't work: when I do the OTA sideload it gives me the signature verification error.
How could I overcome it?
Click to expand...
Click to collapse
Hi... More infos would help troubleshooting the issue more efficiently.
What was the initial build before the device got bricked?
What was the build "system update" that bricked your phone? Did you update manually or through a pushed OTA? If manually, how did you flash it /bricked your phone?
Finally, which build did you try to Sideload?
5.1 said:
Hi... More infos would help troubleshooting the issue more efficiently.
What was the initial build before the device got bricked?
What was the build "system update" that bricked your phone? Did you update manually or through a pushed OTA? If manually, how did you flash it /bricked your phone?
Finally, which build did you try to Sideload?
Click to expand...
Click to collapse
Thanks for your help.
My current build before the phone got bricked is N4F26I .
I think the update that bricked my phone was N4F26O.
I applied the OTA from the recovery system by selecting "Apply update from ADB" and then doing an adb sideload.
More info:
– I have tried to sideload the OTA images for N4F26I, N4F26J, N4F26O but for all of them I get the error above (I downloaded the OTA image files from Google page)
– Re-downloaded the files, but no joy.
– Phone is not rooted. It had the stock image
- Device shows as LOCKED. If I understand correctly, when device is locked it's not possible to flash the factory image
- USB debugging is enabled
this is the error which happens when I reach 47% of the sideload:
E: failed to verify whole file signature
E: signature verification failed
E: error 21
Installation aborted.
D4rkFloors said:
Thanks for your help.
My current build before the phone got bricked is N4F26I .
I think the update that bricked my phone was N4F26O.
I applied the OTA from the recovery system by selecting "Apply update from ADB" and then doing an adb sideload.
More info:
– I have tried to sideload the OTA images for N4F26I, N4F26J, N4F26O but for all of them I get the error above (I downloaded the OTA image files from Google page)
– Re-downloaded the files, but no joy.
– Phone is not rooted. It had the stock image
- Device shows as LOCKED. If I understand correctly, when device is locked it's not possible to flash the factory image
- USB debugging is enabled
this is the error which happens when I reach 47% of the sideload:
E: failed to verify whole file signature
E: signature verification failed
E: error 21
Installation aborted.
Click to expand...
Click to collapse
Did anyone ever figure out this situation. I'm in exactly same situation. Can't sideload full ota image, quits in middle with signature verification. Bootloader is locked and device wont boot up to enable oem unlocking.
How to get past
adb sideload "Zip signature verification failed!"Disable signature verification
xinulhacker said:
Come superare
adb sideload "Verifica firma zip fallita!"Disabilita la verifica della firma
Click to expand...
Click to collapse
How?
Hi everyone,
My brother bought an Axon 7 (A2017) from China and because it came without Google package he installed them manually. However, he start having some malfunctioning issue while importing his contacts from his google account. So, I advise him to switch to EU or US firmware and from there our nightmare started!
First we switched to US firmware (A2017U) and for some unknown reason the phone stopped recognizing our SIM. Basically, the phone sees the SIM but we cannot make a call. The signal bar showing ZERO bars at all time.
Moved to EU firmware (A2017G) without a success.
Tried to go back to A2017 without a success.
What do you think has happened?
Currently, we are on A2017-B08 and we have no issue with it but how can we make to SIM to work again?
Regards,
Nawaf
I would install the latest Chinese build, therefore b013. Easy to do, look back in general questions thread. Use a contacts transfer app to transfer contacts. I've got mine fully up and running on Chinese axon 7 b013.
hajjinm said:
Hi everyone,
My brother bought an Axon 7 (A2017) from China and because it came without Google package he installed them manually. However, he start having some malfunctioning issue while importing his contacts from his google account. So, I advise him to switch to EU or US firmware and from there our nightmare started!
First we switched to US firmware (A2017U) and for some unknown reason the phone stopped recognizing our SIM. Basically, the phone sees the SIM but we cannot make a call. The signal bar showing ZERO bars at all time.
Moved to EU firmware (A2017G) without a success.
Tried to go back to A2017 without a success.
What do you think has happened?
Currently, we are on A2017-B08 and we have no issue with it but how can we make to SIM to work again?
Regards,
Nawaf
Click to expand...
Click to collapse
I think you guys installed full US firmware which overwrited CN bootloader and it leads to lost signal. CN device only works with CN bootloader so you have to install full CN firmware.
Download CN B13 full firmware from here
Unzip it to get update.zip file. If you install via "SD upgrade" put this file into root of SD card. You also can install via TWRP.
Let me know if you get this error message :assert failed getprop( ro.product.name) == "P996A03" during installation process.
To sync Google Contact into CN firmware following these steps:
Enable Google Play Service in Apps setting
Install Google Play Store/Gmail in ZTE Market
Run Google Play Store/Gmail it will asks you update Google Play Service
Install Google Contacts Sync from here. It must be 6.0.1 version.
After this you can add Google account and see Google account option in Contact settings.
Greetings all,
Thanks for your prompt responds. I am on the process of downloading the CH firmware (B13) and I will update you with my outputs.
Appreciate your support and kindness.
Regards,
Nawaf
Greetings All,
I just download the CN firmware and upload it into my SD card. When I tried to "Apply update from SD card" and after reaching 25% progress, I end up with the following error message:
Eackage is not for this device AB - g
Installation aborted.
I rebooted the device and did (1) Wipe data/factory reset and (2) Wipe cache partition and tried again, the screen went black after reaching 25% progress. I re-performed Wipe cache partition again and tried it one more, and I end up with above message!
Any suggestions?
When I go to recovery mode, the following data are presented:
Android Recovery
ZTE/P996A04/ailsa_ii
6.0.1/MMB29M/20161124.233247
user/release-keys
One more thing, when I unzip the update file to the check the updater-script, I found this product no. mentioned there: assert(getprop("ro.product.name") == "P996A03");. As you can see the device showing P996A04 and the update file showing P996A03? Do you think this is the reason for the error and how to overcome it?
Regards,
Nawaf
hajjinm said:
Greetings All,
I just download the CN firmware and upload it into my SD card. When I tried to "Apply update from SD card" and after reaching 25% progress, I end up with the following error message:
Eackage is not for this device AB - g
Installation aborted.
I rebooted the device and did (1) Wipe data/factory reset and (2) Wipe cache partition and tried again, the screen went black after reaching 25% progress. I re-performed Wipe cache partition again and tried it one more, and I end up with above message!
Any suggestions?
When I go to recovery mode, the following data are presented:
Android Recovery
ZTE/P996A04/ailsa_ii
6.0.1/MMB29M/20161124.233247
user/release-keys
One more thing, when I unzip the update file to the check the updater-script, I found this product no. mentioned there: assert(getprop("ro.product.name") == "P996A03");. As you can see the device showing P996A04 and the update file showing P996A03? Do you think this is the reason for the error and how to overcome it?
Regards,
Nawaf
Click to expand...
Click to collapse
Don't worry the following trick should fix this issue:
Unzip update.zip
Use Notepad to open \META-INF\com\google\android\update-script
Delete the first and second line:
getprop ( "ro.product.device") == "ailsa_ii" || abort ( "This package is for " ailsa_ii \ "devices; this is a " "+ getprop (" ro.product.device ") +" \ ".");
assert (getprop ( "ro.product.name") == "P996A03");
Save the update-script and zip everything to update.zip rom file. The reason to do this is to remove the safety checks.
Greetings all,
Thalias, thank you again for everything. Unfortuenately, after I did all what you recommend I end up with the following while installing:
E:footer is wrong
E:Signature verification failed
Installation aborted
Did I miss something here?
Regards,
Nawaf
getprop("ro.product.device") == "ailsa_ii" || abort("This package is for "ailsa_ii" devices; this is a "" + getprop("ro.product.device") + "".");
assert(getprop("ro.product.name") == "P996A03");
ui_print("Target: ZTE/P996A03/ailsa_ii:6.0.1/MMB29M/20161027.021856:user/release-keys");
show_progress(0.950000, 180);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat") ||
abort("Failed to update system image.");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/bootdevice/by-name/boot");
package_extract_file("ddr.img", "/dev/block/bootdevice/by-name/ddr");
package_extract_file("echarge.img", "/dev/block/bootdevice/by-name/echarge");
package_extract_file("lksecapp.mbn", "/dev/block/bootdevice/by-name/lksecapp");
package_extract_file("rpm.mbn", "/dev/block/bootdevice/by-name/rpm");
package_extract_file("tz.mbn", "/dev/block/bootdevice/by-name/tz");
package_extract_file("xbl.elf", "/dev/block/bootdevice/by-name/xblbak");
package_extract_file("mdtp.img", "/dev/block/bootdevice/by-name/mdtp");
package_extract_file("xbl.elf", "/dev/block/bootdevice/by-name/xbl");
package_extract_file("cmnlib64.mbn", "/dev/block/bootdevice/by-name/cmnlib64");
package_extract_file("adspso.bin", "/dev/block/bootdevice/by-name/dsp");
package_extract_file("recovery.img", "/dev/block/bootdevice/by-name/recovery");
package_extract_file("sec.dat", "/dev/block/bootdevice/by-name/sec");
package_extract_file("NON-HLOS.bin", "/dev/block/bootdevice/by-name/modem");
package_extract_file("pmic.elf", "/dev/block/bootdevice/by-name/pmic");
package_extract_file("devcfg.mbn", "/dev/block/bootdevice/by-name/devcfg");
package_extract_file("emmc_appsboot.mbn", "/dev/block/bootdevice/by-name/aboot");
package_extract_file("keymaster.mbn", "/dev/block/bootdevice/by-name/keymaster");
package_extract_file("splash.img", "/dev/block/bootdevice/by-name/splash");
package_extract_file("hyp.mbn", "/dev/block/bootdevice/by-name/hyp");
package_extract_file("BTFM.bin", "/dev/block/bootdevice/by-name/bluetooth");
package_extract_file("cmnlib.mbn", "/dev/block/bootdevice/by-name/cmnlib");
package_extract_dir("cache", "/cache");
set_progress(1.000000);
I remove the two bold lines from the script.
Thalias,
I am still getting the same error message regardless of all my attempts:
E:footer is wrong
E:Signature verification failed
Installation aborted
Regards,
Nawaf
hajjinm said:
Thalias,
I am still getting the same error message regardless of all my attempts:
E:footer is wrong
E:Signature verification failed
Installation aborted
Regards,
Nawaf
Click to expand...
Click to collapse
Are you flashing with TWRP or SD Upgrade?
Thalias,
I am using SD Upgrade.
Regards,
Nawaf
hajjinm said:
Thalias,
I am using SD Upgrade.
Regards,
Nawaf
Click to expand...
Click to collapse
You could try to use TWRP and let me know.
You could try to use TWRP and let me know.
Click to expand...
Click to collapse
Thalias,
The problem I cannot go into EDL mode to install TWRP into A2017G!? I made to many attempts but unfortunately no success.
After confirming that the PC seeing the device with "adb devices" and after sending the command "adb reboot edl", the screen of A2017G went dark BUT the "RED LIGHT" is OFF. Any command I sent I end up with error that the device cannot be seen.
Have you ever experienced this?
Regards,
Nawaf
hajjinm said:
Thalias,
The problem I cannot go into EDL mode to install TWRP into A2017G!? I made to many attempts but unfortunately no success.
After confirming that the PC seeing the device with "adb devices" and after sending the command "adb reboot edl", the screen of A2017G went dark BUT the "RED LIGHT" is OFF. Any command I sent I end up with error that the device cannot be seen.
Have you ever experienced this?
Regards,
Nawaf
Click to expand...
Click to collapse
even if it is dark it is in edl mode, i finished the steps and when i tried to go to recovery mode i failed it will give a black screen like the one with edl mode. and I suffered to bring the mi recovery back. i have the same problem dude "NO SIGNAL!"
You will turn your phone to brick if you keep messing around with locked bootloader.
1. Unlock bootloader
2. Flash twrp
3. Flash right bootstack for your country (A2017U for US, A2017G for world and A2017 for china) - (warning: "Your country" - not "Your phone's country)
Thalias said:
Are you flashing with TWRP or SD Upgrade?
Click to expand...
Click to collapse
I have just removed the two lines, pack into a zip and flash by TWRP but TWRP called "corrupt zip". When I go back the OS, I try to open the .zip file by ES explorer, it can be opened normally, not corrupt!
---------- Post added at 02:25 PM ---------- Previous post was at 02:11 PM ----------
I have solution for this:
1-Copy ORIGINAL .zip file (no removing 2 line like above)
2-Flash Stock recovery by fastboot (you can extract stock recovery: recovery.img from ORIGINAL.zip file)
3-Use updater app from Settings to choose and install the zip file => your OS will be updated
4-Flash back to TWRP
A blessed day to all who read and many thanks to those who will help.
I will not confuse you with a long back story. My goal is to update to lollipop but this is where I am at:
fastboot works but I have no OS (having wiped out system folder)
i can install TWRP-2870_Zenfone5.img or recovery_philz_t00f.img. The stock recovery image from UL-ASUS_T00F-WW-2.22.40.53-user.zip only results in a dead droidboot logo (with red exclamation mark)
installing from firmware.zip SD card doesnt work, I will recreate the error messages
E: Unknown File System: 'osip'
E: Unknown File System: 'osip'
E: Unknown File System: 'osip'
E: Unable to find partition size for '/misc'
E: Unable to find partition size for '/splashscreen'
Updating partition details . . .
. . . done
Full SELinux support is present.
E: Unable to set bootloader message.
MTP Enabled
Installing '/external_sd/UL_ASUS_T00F-WW-2.22.40.53-user.zip'. . .
Checking for MD5 file . . .
Skipping MD5 check: no MD5 file found
Error flashing zip '/external_sd/UL_ASUS_T00F-WW-2.22.40.53-user.zip'
Updating partition details . . .
. . . done
Click to expand...
Click to collapse
installing from adb sideload doesnt work. error: closed
I need your help, I have spent 2 days in Google, Asus.com Zentalk and this amazing forum. I need to install the stock ROM and upgrade to Lollipop.
Thanks in advance.
ASUS Zenfone 5 t00j a500cg WW
IFWI 59.A1
Droidboot 2.1
UPDATE
I finally got an OS by following this: link
Quote:
Originally Posted by dgadelha
Hello,
There can be a way to solve your problem
(this solution also can be useful for any other broken systems)
ZENFONE 5 (T00F, T00J) ONLY!
Required downloads:
Jelly Bean Firmware
Intel USB Drivers
ADB+Fastboot
Offline Update Image Script
Steps:
Install the Intel USB Drivers
Rename the Jelly Bean Firmware file, changing the extension from .raw to .zip
Create a directory for all the files (e.g.: C:\zenfone)
Extract the contents of the Jelly Bean Firmware and ADB+Fastboot on the directory you just created
Copy the file of Offline Update Image Script (sec_offline_update_image.cmd) to the same directory
Shutdown your phone and start in droidboot mode (Power + Vol. Up)
Plug the USB
Assert that your device is connected, check by running the command fastboot devices on a Command Prompt
Go to the directory you created before and run the file sec_offline_update_image.cmd as administrator
When your device reboot again into bootloader, check if there was no errors (the userdata erase error can be ignored with no problems). If there was any error, I recommend you to go back and check if you done all steps correctly. If not, just use the volume buttons to select the option 'Reboot' and activate it by pressing the Power key
After this is done, you can upgrade to KitKat or Lollipop via recovery, just download the update from Asus site and sideload it via ADB.
Thanks!
Click to expand...
Click to collapse
adb sideload works
SD card to internal memory copying of stock firmware UL-ASUS_T00F-WW-2.22.40.53-user.zip works when I restart the phone, it detects the system update
but now I get the following error
E:end of footer from data/media/0/UL-ASUS_T00F-WW-2.22.40.53-user.zip failed not 0xFFFF (file exists)
E:signature verification failed
E:Install of data/media/0/UL-ASUS_T00F-WW-2.22.40.53-user.zip failed with status 2
Installation aborted.
E:Installation failed with status 2
E:Can't open tmp/update-script.log
E:Can't load volume/misc!
Click to expand...
Click to collapse
Any ideas how I can get past this?
UPDATE #2 [SOLVED]
I initially thought of going ladder steps up but then out of curiosity searched for ASUS Zenfone 5 Marshmallow and came across this.
Here is what I did:
1. Unlocked bootloader (cause it was initially locked)
fastboot flash fastboot fastboot_unlocker.img
fastboot reboot-bootloader
fastboot flash dnx dnx_fwr_ctp_a500cg.bin
fastboot flash ifwi ifwi_ctp_a500cg_unlock.bin
fastboot reboot-bootloader
Click to expand...
Click to collapse
2. Downloaded and flashed boot image. I used cm13-zenfone5-kernel.img
fastboot flash boot cm13-zenfone5-kernel.img
Click to expand...
Click to collapse
3. Downloaded and flashed recovery image. I used TWRP.img
fastboot flash recovery TWRP.img
Click to expand...
Click to collapse
4. Downloaded and flashed system image. I used cm13-zenfone5-system.img
fastboot flash system cm13-zenfone5-system.img
Click to expand...
Click to collapse
5. Erased unneeded files
fastboot erase data
fastboot erase userdata
fastboot erase cache
Click to expand...
Click to collapse
6. I installed open_gapps-x86-6.0-pico-20200207.zip (Open Google Apps Pico version)
7. I did some memory cleaning factory reset then dalvik cache and cache wipe
8. My TWRP froze on reboot system so I unplugged/replugged the USB cable then I did an adb reboot which is the same thing as Power+Volume Up button.
Click to expand...
Click to collapse
And voila! A running marshmallow OS on Asus Zenfone 5 t00j a500cg.
Overall, I spent 2 days trying to do this but it was well worth it. My son is very happy he can now play his MOBA faster than the original bloated KitKat OS. Same hardware, better software. Overall, I enjoyed the learning experience and the joy of being appreciated by my son.
Hello everybody!
To defeat planned obsolescence of my Zenfone 3 (ZE520KL) I've decided to root it and install an alternative ROM.
With much difficulty at the end I achive root it but I've a problem flashing roms.
- Unloked OK
- To flash and fix TWRP I used Magistik (without it TWRP starded only when phone was connected to pc)
Now Root Checker says my phone is rooter, Magistik is correctly installed and TWRP seems ok. So I felt in 90% of my challenge!
But…
When I try to flash a ROM in TWRP lots of red line appear…
Data successfully decrypted, new block device: '/dev/block/dm-0'
Updating partition details…
...done
Unable to mount storage
Successfully decrypted with default password.
Updating partition details
…..done
Unable to mount storage
Failed to mount '/data? (Invalid Argumetn)
Full SELinux support is present.
Unable to mount /data/media/twrp/.twrps
MTP Enabled
Installing zip file '/external_sd/PixelExperience_zenfone3_-9.0-20190823-1844-UNOFFICIAL.zip'
Checking for MD5 file…
Skipping MD5 check: no MD5 file found
Warnink: No file_context
E3004: This package is for device: Z017, ASUS_Z017_1D, ASUS_Z012D, ASUS_Z012DC, ASUZ_Z012S; this device is .
E:unknown command [log]
Update process ended with ERROR: 7
Error installing zip file '/external_sd/PixelExperience_zenfone3_-9.0-20190823-1844-UNOFFICIAL.zip'
Updating partition details…
...done
Unable to mount storage
Click to expand...
Click to collapse
The same thing happens with Lineage OS
In addition if I try to save the log I can't find it in the storage of the phone (really I don't know where it should be).
Maybe the Recovery [treble] proposed by Giovix92 can solve my problem?
Any other suggestion?
Thanks a lot to everybody!
twin-s said:
Hello everybody!
To defeat planned obsolescence of my Zenfone 3 (ZE520KL) I've decided to root it and install an alternative ROM.
With much difficulty at the end I achive root it but I've a problem flashing roms.
- Unloked OK
- To flash and fix TWRP I used Magistik (without it TWRP starded only when phone was connected to pc)
Now Root Checker says my phone is rooter, Magistik is correctly installed and TWRP seems ok. So I felt in 90% of my challenge!
But…
When I try to flash a ROM in TWRP lots of red line appear…
The same thing happens with Lineage OS
In addition if I try to save the log I can't find it in the storage of the phone (really I don't know where it should be).
Maybe the Recovery [treble] proposed by Giovix92 can solve my problem?
Any other suggestion?
Thanks a lot to everybody!
Click to expand...
Click to collapse
Might be due to encrypted partition.
Try
Code:
fastboot format userdata
in fastboot mode.
This will, as you might expect, wipe all your data. So be sure to backup first.
Also, the flashing error
Code:
E3004: This package is for device: Z017, ASUS_Z017_1D, ASUS_Z012D, ASUS_Z012DC, ASUZ_Z012S; this device is .
E:unknown command [log]
Update process ended with ERROR: 7
is from incompatible TWRP and ROM version. Are you using the latest TWRP?
As a last resort for the flashing error, try this https://forum.xda-developers.com/showthread.php?t=2522762
vaanish said:
Might be due to encrypted partition.
Try
Code:
fastboot format userdata
in fastboot mode.
This will, as you might expect, wipe all your data. So be sure to backup first.
Also, the flashing error
Code:
E3004: This package is for device: Z017, ASUS_Z017_1D, ASUS_Z012D, ASUS_Z012DC, ASUZ_Z012S; this device is .
E:unknown command [log]
Update process ended with ERROR: 7
is from incompatible TWRP and ROM version. Are you using the latest TWRP?
As a last resort for the flashing error, try this https://forum.xda-developers.com/showthread.php?t=2522762
Click to expand...
Click to collapse
Thank you vaanish!
I solved flashing an older versione of TWRP. The 3.3.1.
Now all is right!