So I am trying to root my phone (ASUS Zenfone 6) but it says "E: failed to verify whole-file signature". Now I head I need to install custom recoveries like CWM but I cannot technically install CWM since my phone is not yet rooted and I am blocked from rooting my phone because of this error. Any help? I need one ASAP
no help?
Have you tried RootZenfone?
If that doesn't work, there is a temporary ClockWorkMod session for Intel Atom devices. You can flash SuperSU through that.
jerbear294 said:
Have you tried RootZenfone?
If that doesn't work, there is a temporary ClockWorkMod session for Intel Atom devices. You can flash SuperSU through that.
Click to expand...
Click to collapse
It doesnt work for the newest firmware sadly. Mind giving instructions how to?
Rhandythebeast said:
So I am trying to root my phone (ASUS Zenfone 6) but it says "E: failed to verify whole-file signature". Now I head I need to install custom recoveries like CWM but I cannot technically install CWM since my phone is not yet rooted and I am blocked from rooting my phone because of this error. Any help? I need one ASAP
Click to expand...
Click to collapse
there is a new magisk method which works perfectly with rr 5.8.5.
https://forum.xda-developers.com/ze...-t00j-t00f-t4122347/post83497537#post83497537
if i helped drop a thanks
Related
Hey guys,
So I attempted to root my nexus s and ran into some troubles.
I started the process on my mac.....(keep in mind I also have a PC, so that is still an option to work with) I got the bootloader unlocked.....I have ClockwordMod Recovery v3.0.0.0 working.......but as soon as I try to restart the device it just wont go past the google splash screen with the padlock.
I've tried to install superuser .zip files.....nandroid backup .zips....with no success. I always get hung up on the splash screen!
I feel terrible I don't know where I went wrong
dannykavs said:
Hey guys,
So I attempted to root my nexus s and ran into some troubles.
I started the process on my mac.....(keep in mind I also have a PC, so that is still an option to work with) I got the bootloader unlocked.....I have ClockwordMod Recovery v3.0.0.0 working.......but as soon as I try to restart the device it just wont go past the google splash screen with the padlock.
I've tried to install superuser .zip files.....nandroid backup .zips....with no success. I always get hung up on the splash screen!
I feel terrible I don't know where I went wrong
Click to expand...
Click to collapse
Did you follow the terrible guide at http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/ where you flash the insecure boot image that is way out of date and only for the i9020t?
Are you trying to restore a stock rom or a custom rom? Either way, grab the full package OTA of a stock rom for your device (around 90mb) or your custom rom of choice and flash that from CWM. That will write a new boot.img as well as /system, etc.
krohnjw said:
Did you follow the terrible guide at http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/ where you flash the insecure boot image that is way out of date and only for the i9020t?
Are you trying to restore a stock rom or a custom rom? Either way, grab the full package OTA of a stock rom for your device (around 90mb) or your custom rom of choice and flash that from CWM. That will write a new boot.img as well as /system, etc.
Click to expand...
Click to collapse
I didn't follow that guide thankfully but I still think I followed an outdated procedure.
So when i try to install a rom Clockwork always aborts the installation.
here is the error I get:
assert failed: getprop("ro.product.device")=="crespo" || getprop("ro.build.product") =="crespo" || getprop ("ro.product.board") == "crespo" E: Error in /sdcard/update-cm-7.1.0.1-NS-signed.zip
(status) 7
Installation aborted
dannykavs said:
I didn't follow that guide thankfully but I still think I followed an outdated procedure.
So when i try to install a rom Clockwork always aborts the installation.
here is the error I get:
assert failed: getprop("ro.product.device")=="crespo" || getprop("ro.build.product") =="crespo" || getprop ("ro.product.board") == "crespo" E: Error in /sdcard/update-cm-7.1.0.1-NS-signed.zip
(status) 7
Installation aborted
Click to expand...
Click to collapse
Do you have a GSM Nexus S (i9020t, i9020a, i90230) or the CDMA Nexus S 4G? If it's the latter you are trying to flash a ROM that's not for your device. Get a rom for the NS4G from that development forum (device = crespo4g).
have you tried flashing a rom?
krohnjw said:
Do you have a GSM Nexus S (i9020t, i9020a, i90230) or the CDMA Nexus S 4G? If it's the latter you are trying to flash a ROM that's not for your device. Get a rom for the NS4G from that development forum (device = crespo4g).
Click to expand...
Click to collapse
It is the GSM Nexus S i9020A. Don't believe that to be an issue.
I've threw so many different zip files on my sd card when I mount it via usb and I always seem to get that same error message. Pretty frustrating....I always read about people not being able to flash recovery but I'm there.....I just can't seem to find anyone who has my same issue...
Any other information I can provide that would be useful?
Try a more recent version of cwm.
albundy2010 said:
Try a more recent version of cwm.
Click to expand...
Click to collapse
I've actually got version 3.1 going right now with no luck
What is the latest version ?
Update CWM to higher than 4.0.0.0. You could flash the zip below in recovery and if that doesn't work then find the new version with fastboot.
http://forum.xda-developers.com/showthread.php?t=1248760
EDIT: Just flash one of these with fastboot: http://forum.xda-developers.com/showthread.php?t=988686&highlight=clockwork+recovery
The first and second ones will work for you.
irishrally said:
Update CWM to higher than 4.0.0.0. You could flash the zip below in recovery and if that doesn't work then find the new version with fastboot.
http://forum.xda-developers.com/showthread.php?t=1248760
EDIT: Just flash one of these with fastboot: http://forum.xda-developers.com/showthread.php?t=988686&highlight=clockwork+recovery
The first and second ones will work for you.
Click to expand...
Click to collapse
Thanks for the suggestion. I will give this a go first thing in the morning and report back.
Bedtime zzzzzzzZzzZzz
irishrally said:
Update CWM to higher than 4.0.0.0. You could flash the zip below in recovery and if that doesn't work then find the new version with fastboot.
http://forum.xda-developers.com/showthread.php?t=1248760
EDIT: Just flash one of these with fastboot: http://forum.xda-developers.com/showthread.php?t=988686&highlight=clockwork+recovery
The first and second ones will work for you.
Click to expand...
Click to collapse
Yup so I went ahead and flashed the recovery from the second link you gave me and on my first try i was able to install the CyanogenMod 7.1 zip file. Made my day!
Thanks everyone!
http://forum.xda-developers.com/showthread.php?t=1250583
for reference, I just rooted my new (to me) nexus s the other day with this. It couldn't be any easier really.
Running 4.1.1 at the moment and rooted / unlocked using a toolkit.
Trying to update to 4.2.2 ota but when the nexus reboots I get that error.
What do I do?
Foxman2k said:
Running 4.1.1 at the moment and rooted / unlocked using a toolkit.
Trying to update to 4.2.2 ota but when the nexus reboots I get that error.
What do I do?
Click to expand...
Click to collapse
See thread:
http://forum.xda-developers.com/showthread.php?t=1764794
seems to be due to custom kernel
flyi said:
I think I have the same problem, mine says "Verifying current system..." then says "assert failed: apply_patch_check ..."
I'm currently running 4.1.1 stock rom rooted and custom kernel.
Also, I think you mean 'trying to update to 4.1.2 ota'.
Click to expand...
Click to collapse
Flash the stock kernel. You can do it a number of ways. You can find a cwm zip file with it, use the toolkit to do it, or get the IMG yourself and flash it via fast boot. I had this error earlier.
Install a custom recovery and use it to run the update. If you already have a custom recovery, then that's why you can't run the ota via google possibly.
flyi said:
See thread:
http://forum.xda-developers.com/showthread.php?t=1764794
seems to be due to custom kernel
Click to expand...
Click to collapse
But I don't have a custom kernel. Just rooted and unlocked.
mustbepbs said:
Flash the stock kernel. You can do it a number of ways. You can find a cwm zip file with it, use the toolkit to do it, or get the IMG yourself and flash it via fast boot. I had this error earlier.
Click to expand...
Click to collapse
Any guides on this? Pretty new to android.
Anyone have any thoughts on what I should do?
Did you touch any of your system apps?
Seems more likely your update didn't download fully and it failed and md5 checksum. Just try again next time.
I don't think I touched any of the system apps. I did download Adblock and six axis tool. Anything else to look for?
I've downloaded the update probably 4 different times now and same thing each time.
Anything else I can try?
Foxman2k said:
Anything else I can try?
Click to expand...
Click to collapse
Any other options besides resetting? has no one else who only rooted and unlocked run into this problem???
I didn't change any system apps, and for rooting purposes the only apps I downloaded where Titanium Backup, Sixaxis and Stickmount. Should I remove those?
and OT Rootkeeper. Do I remove root first?
flyi said:
See thread:
http://forum.xda-developers.com/showthread.php?t=1764794
seems to be due to custom kernel
Click to expand...
Click to collapse
I was getting exactly the same as you Foxman2k, about the unverified whole-file signature when trying the OTA way. I've just followed the advice of the above linked thread and it worked fine. I had to install Quick Boot (Reboot) to get in to Recovery, then update from SD Card, then ensure signature verification is disabled, then select the downloaded .zip file. I did have RootKeeper active, but I don't really understand what that does so not sure if it made any difference.
HTH
I finally managed to get mine to go through, am rooted but running stock and was getting the error with build.prop.
Then it hit me, I am in tablet mode with my screen at 160, so I set it back to 213 and boom it went through.
HTH
I am looking help from someone who knows TWRP. My phone accidentally did an update and now it just boots into TWRP v2.6.3.2. I am new to this stuff but through learnings I have pushed the stock firmware found on this site (I am in Canada and with Telus) using adb push through command prompt. However when i go to install, it fails. I have also tried Rogers and Bell. Nothing works. I don't understand what is wrong?
What I see is:
E: storage partition '//TWRP/BACKUPS/018bf7ce0f4c6fa0' not found
Installing '/sdcard/TelusD803T10B_00.zip
Checking for MD5 file ...
Skipping MD5 check: no MD5 file found.
Verifying zip signature ...
E:Zip signature verification failed: 1
Error flashing zip '/sdcard/TelusD803T10B_00.zip
Can anyone please tell me what is going on here and what is wrong? I would really appreciate it. The phone is new and useless to me right now as is .... thank you
Did you did an OTA update while on custom ROM? have you tried other recovery? I had trouble flashing with TWRP too. Im using Philz Touch atm and it works great for me.
super114 said:
Did you did an OTA update while on custom ROM? have you tried other recovery? I had trouble flashing with TWRP too. Im using Philz Touch atm and it works great for me.
Click to expand...
Click to collapse
All I did was accept an update when prompted but didn't pay attention and when the phone rebooted it went into twrp. I had no idea what twrp was. through learning about it i got the stock roms off this website and pushed it on to the phone and tried to install but it just fails for some reason. i don't know what more i can do.
Follow the"back to stock threads" you cant accept ota's when rooted
Sent from my LG-D800 using Tapatalk
I would follow the above comment and follow the step by step guide how to get back to stock when you accidentally got OTA when rooted. Just follow the steps carefully and you'll be fine.Good luck
Have you tried this?
Just untick Zip File Signature when prompting to flash zip.That might work
Hi Everyone
I'm hoping to get some help here, I have flashed my SM-910F (Galaxy Note 4) with TWRP Recovery.
When I try to install SURoot, i get an error stating signature verification failed.
How do I disable signature verification in TWRP Recovery. I have looked everywhere in the menus and its just not visible, I have tried different TWRP recovery versions in the hope that I can get to the setting to disable it but so far no luck.
Can someone help please
Thank you in advance!
Jay_010 said:
Hi Everyone
I'm hoping to get some help here, I have flashed my SM-910F (Galaxy Note 4) with TWRP Recovery.
When I try to install SURoot, i get an error stating signature verification failed.
How do I disable signature verification in TWRP Recovery. I have looked everywhere in the menus and its just not visible, I have tried different TWRP recovery versions in the hope that I can get to the setting to disable it but so far no luck.
Can someone help please
Thank you in advance!
Click to expand...
Click to collapse
Update in case anyone has the same problem:
1. Flash twrp using Odin but do not let it auto reboot.
2. Then power off and immediately go back into recovery.
3. Finally flash SU and reboot back into system.
You're done.
Hope this helps someone.
Jay_010 said:
Hi Everyone
I'm hoping to get some help here, I have flashed my SM-910F (Galaxy Note 4) with TWRP Recovery.
When I try to install SURoot, i get an error stating signature verification failed.
How do I disable signature verification in TWRP Recovery. I have looked everywhere in the menus and its just not visible, I have tried different TWRP recovery versions in the hope that I can get to the setting to disable it but so far no luck.
Can someone help please
Thank you in advance!
Click to expand...
Click to collapse
I think your supersu.zip file is corrupted
Download again and flash it should work
every flashing using adb or flashtools has failed
adb sideload fails with E:cant mount/cache
flashtool (oem partition)
and i think i messup with the oem partiton. i flash with the kitkat v.54
i am in lolipop non root
i can go to droidmode and recovery but wipe and factory reset always fails with E:cant mount........
i have tried every bit of available solutions . plz help
please tell me with something effective
fastboot flash recovery recovery.img
........................................
.....................................
.................................... don't work during sideload it fails
is the zenfone 5 section dead here on xda? there are too many queries left unanswered, this is still such a good phone though
adb sideload ?
u'll never success !
u just need to unlock bootloader
go study this thread http://forum.xda-developers.com/zenfone-5/general/recovery-twrp-2-8-6-0-asus-zenfone-5-t3136263
and give it a try u can read thru from
page to page !
I'm a noob on this zenfone 5
after 4th day success unlock bootloader
and flash any rom o like !
but there will still have problem
with TWRP for flashing ROMs
zenfone 5 TWRP not universer !
u need to tackle by ur self !
done everything but failed to mount is the ans
failed to mount is the final result
gradd said:
is the zenfone 5 section dead here on xda? there are too many queries left unanswered, this is still such a good phone though
Click to expand...
Click to collapse
i don't know what else i can do sideload cant be done
E:failed to mount(invalid argument)
if you can help me please
akatsuki oinam said:
i don't know what else i can do sideload cant be done
E:failed to mount(invalid argument)
if you can help me please
Click to expand...
Click to collapse
it seems you lost root. are you using custom recovery? if not, you may try debricking thread, as a last resort. if its stock recovery. it looks lije its borked
http://forum.xda-developers.com/zenfone-5/help/debrick-asus-zenfoen-5-fastboot-t3377455
gradd said:
it seems you lost root. are you using custom recovery? if not, you may try debricking thread, as a last resort. if its stock recovery. it looks lije its borked
http://forum.xda-developers.com/zenfone-5/help/debrick-asus-zenfoen-5-fastboot-t3377455
Click to expand...
Click to collapse
i try the method but sadly it gives the same command
akatsuki oinam said:
i try the method but sadly it gives the same command
Click to expand...
Click to collapse
consider yourself lucky coz you can get past droidboot, if you can sideload, there's an alternate method to flash stock .raw firmware thru xfstk. im still stuck at intel logo, no progress just yet since December 8 and no droidboot
gradd said:
consider yourself lucky coz you can get past droidboot, if you can sideload, there's an alternate method to flash stock .raw firmware thru xfstk. im still stuck at intel logo, no progress just yet since December 8 and no droidboot
Click to expand...
Click to collapse
xfstk.im how? can i check
akatsuki oinam said:
xfstk.im how? can i check
Click to expand...
Click to collapse
sure! i found it outside xda, its for both variants of zen5.
https://www.google.com/amp/s/andrewbenedictus.wordpress.com/2016/02/15/how-to-unbrick-asus-zenfone-5-stuck-on-intel-logo/amp/?client=ms-android-pantech
gradd said:
sure! i found it outside xda, its for both variants of zen5.
https://www.google.com/amp/s/andrewbenedictus.wordpress.com/2016/02/15/how-to-unbrick-asus-zenfone-5-stuck-on-intel-logo/amp/?client=ms-android-pantech
Click to expand...
Click to collapse
after using the flashtool
flash image failure(FAILURE(remote:unknown OEM command))
what can be done more:crying::crying::crying:
Hello! I'm new to you at xda
I am having this same problem on my asus zenfone 5 (a501cg), when I clear the partiques cache / data or facrore reset, it shows the following. "E: cant mount / cache / recovery / last_update-log".
I would like and help, but I have not found a solution yet:confuso:
-benzóico.