Hey guys i'm pretty new to this. I rooted my phone yesterday and i stuck on today Open Desire-4.0.15. I want to try another rom but when i try to apply the update.zip i get the message E:signature verification failed Installation aborted.
I hope you guys can help me and let me know if you need any more information
tribute said:
Hey guys i'm pretty new to this. I rooted my phone yesterday and i stuck on today Open Desire-4.0.15. I want to try another rom but when i try to apply the update.zip i get the message E:signature verification failed Installation aborted.
I hope you guys can help me and let me know if you need any more information
Click to expand...
Click to collapse
thats because the rom you are trying to flash has no signature, all you have to do is use a recovery that lets you flash unsigned .zip's, the latest version of clockworkmod recovery that comes with the unrevoked flash tool lets you do this
I did what you said and it worked from what i can tell and it loaded on AuraxTSense. The problem is at start up now it just says loading, this may take a few minutes to complete and just hangs there. I can't do anything with it and i can't change the rom from the recovery menu so now i'm even more stumped.
tribute said:
I did what you said and it worked from what i can tell and it loaded on AuraxTSense. The problem is at start up now it just says loading, this may take a few minutes to complete and just hangs there. I can't do anything with it and i can't change the rom from the recovery menu so now i'm even more stumped.
Click to expand...
Click to collapse
at witch part is it saying please wait? has the rom booted? did you do a full wipe before flashing? try doing a full wipe from the partitions menu in recovery and re flashing the rom
rebooted it and this time it just loaded up properly. Strange but hey.
Thanks for you help on my previous problem. It's basically the same issue but i've also tried deleting the partitions in the recovery menu. I've tried changing the rom from clockworkmod, nothing is working. It just puts AuraxTSense back to default.
Hello all,
I've got an unbranded international (taiwan) HOX.
Today I was notified that I got an update availabe for my device - finally JB!
So I let it download and install, but when it turns off to install (in CWM) it automatically I've got an error that says
PHP:
"E: unknown volume for path [file path]"
"E: Can't mount [file path]"
"Installation aborted."
So I tried to install the file from the zip manually (in CWM) but I got these errors:
PHP:
"E: failed to verify whole-file signature"
"E: signature verification failed"
"Installation aborted."
Also tried to put it in another folder and install manually, but no luck, and even re-download it. (Delete, let it download the update again and install).
Another friend who's got the same phone as mine (we bought it at the same store) did get to install the update successfully.
Any thoughts? I'll go ahead and say that my phone has CWM and is rooted. my friend's phone is clean in that matter, no modifications.
noodlez04 said:
Hello all,
I've got an unbranded international (taiwan) HOX.
Today I was notified that I got an update availabe for my device - finally JB!
So I let it download and install, but when it turns off to install (in CWM) it automatically I've got an error that says
PHP:
"E: unknown volume for path [file path]"
"E: Can't mount [file path]"
"Installation aborted."
So I tried to install the file from the zip manually (in CWM) but I got these errors:
PHP:
"E: failed to verify whole-file signature"
"E: signature verification failed"
"Installation aborted."
Also tried to put it in another folder and install manually, but no luck, and even re-download it. (Delete, let it download the update again and install).
Another friend who's got the same phone as mine (we bought it at the same store) did get to install the update successfully.
Any thoughts? I'll go ahead and say that my phone has CWM and is rooted. my friend's phone is clean in that matter, no modifications.
Click to expand...
Click to collapse
You need to go back to stock in everything to get that update ... It needs stock recovery and locked bootloader ...
chaun1308 said:
You need to go back to stock in everything to get that update ... It needs stock recovery and locked bootloader ...
Click to expand...
Click to collapse
Could you please refer me to a guide that will help me do that?
and from my understanding, If I'll go back to stock, and update, I'll have to unlock the bootloader again. Last time I did that I had to delete everything on my phone (I guess this will happen when I revert the root and bootloader unlocking too), so got any good way to backup all the app data and everything I need?
Thanks.
noodlez04 said:
Could you please refer me to a guide that will help me do that?
and from my understanding, If I'll go back to stock, and update, I'll have to unlock the bootloader again. Last time I did that I had to delete everything on my phone (I guess this will happen when I revert the root and bootloader unlocking too), so got any good way to backup all the app data and everything I need?
Thanks.
Click to expand...
Click to collapse
Correction . You will have to relock the bootloader again . And since you've rootedd your phone , use Titanium Backup or MyBackup .
This video will guide you to complete stock .
Relocking bootloader is not necessary for OTA updates, but you need stock recovery.
You have to find a stock recovery and then flash it via Fastboot.
Tutorials over here: http://forum.xda-developers.com/showthread.php?t=1832891
Agree with webpatrick
you only need stock recovery to install OTA updates, just find your original rom(or extract from ruu) and flash it in bootloader fastboot flash recovery path_to_recovery_signed.img
not sure if it requires locking the bootloader or not, after that you can reinstall CWM the way you did before and make a backup.
There are 2 options
1:
Flash the non-rooted stock rom with stock boot.img and stock recovery. Bootloader can stay UNLOCKED.
2:
Flash the right RUU, only LOCKING the bootloader is needed. The ruu will flash the stock recovery and boot.img.
Just to be clear
Verstuurd van mijn HTC One X
Need some clearing up here:
1. Can my phone stay rooted? if not - how do I remove SuperSU? tried to remove it from ES by removing the SU file and the app from system/app but that didn't work. - EDIT: Managed to remove root from my device using HTC Quick Root, though it says I need to install secure boot.img to entirely remove root.
2. I tried to flash a recovery file I found in a guide, but the recovery doesn't really work...when I try to access the recovery I got the error screen (the one with the red triangle and exclamation mark), so can someone refer me to a working recovery? attached my software information.
3. Do I need to relock my bootloader or not?
Thanks alot guys, I'm pretty much of a newbie in this whole business
Okay let me lay it down for you.. Pretty simple.. This process doesn't need you to relock the bootloader. (Even if you had to using the other process you would be adding a couple of minutes more in unlocking bootloader)
method1:
1- First things first get your RUU depending upon the version you are at. I haven't had a look at your picture. but just make sure that your region is correct and that the version you possess is either the same version or higher.
2- You need to flash the recovery as that is what will update the recovery and the ROM. so as mentioned above you can just go into fastboot and then flash recovery using the RUU.
method 2:
just relock te bootloader by going into fastboot and typing "fastboot oem lock".
Once that is done you can just run RUU and it will update everything for you. Once complete just unlock bootloader and then flash CWM.. thats it
zainalabididn.syed said:
Okay let me lay it down for you.. Pretty simple.. This process doesn't need you to relock the bootloader. (Even if you had to using the other process you would be adding a couple of minutes more in unlocking bootloader)
method1:
1- First things first get your RUU depending upon the version you are at. I haven't had a look at your picture. but just make sure that your region is correct and that the version you possess is either the same version or higher.
2- You need to flash the recovery as that is what will update the recovery and the ROM. so as mentioned above you can just go into fastboot and then flash recovery using the RUU.
method 2:
just relock te bootloader by going into fastboot and typing "fastboot oem lock".
Once that is done you can just run RUU and it will update everything for you. Once complete just unlock bootloader and then flash CWM.. thats it
Click to expand...
Click to collapse
now I've got a few problems with that:
first of all, my version is 2.18 and there is no RUU for that version for my HTC (which is TWM-TW) yet. and I don't wanna go back to stock ROM, it is the one I have. I just want to set my phone straight so it can get the OTA JB update.
The problem I think I've got now is that my recovery is malfunctioning. I think I don't have the right recovery, since when I try to go into recovery mode I get the red triangle and exclamation mark.
When I tried to install the update, it downloaded it, went into recovery, started doing the process (the green bar was progressing) and then out of the blue - error screen (red triangle and exclamation mark)...
Any ideas?
I always have this problem when i try to update even if i go back to the stock recovery.The problem is that you installed something that modified you'r system (in my case i've installed using CWM the Google Now and some other stuff on it) and now the phone can't update because something is "messed up" in the system.You now have to restore and old backup in CWM,preferably one that doesn't have any mods in it.The recovery is good,otherwise it wouldn't work at all.
jeyml said:
I always have this problem when i try to update even if i go back to the stock recovery.The problem is that you installed something that modified you'r system (in my case i've installed using CWM the Google Now and some other stuff on it) and now the phone can't update because something is "messed up" in the system.You now have to restore and old backup in CWM,preferably one that doesn't have any mods in it.The recovery is good,otherwise it wouldn't work at all.
Click to expand...
Click to collapse
Well, I rooted my phone and installed CWM. so I did the unroot (as far as I know) and got the stock recovery, so what else could it be? :S
No,you didn't understand,this is not about the stock recovery.This is about the fact that you probably installed something (using CWM) that rewrited some files in the /system or other folders that this update depend on.Because those folders are modified the update doesn't recognize those apps and can't continue.That is what i am saying.Install the CWM again,search for any nandroid backups that you have on it and install the oldest one.I usualy make a nandroid backup everytime i update my phone because until the next update i keep installing stuff that messes up my ROM and in cases like yours i just apply the backup i've taken and voila,the update works.Also there is one app that messes up you'r system,it is called BusyBox,and if you install that app and want to make an update,the update will fail (red triangle) because of that app.
If you don't have any nandroid backups the only solution is to install the RUU.
jeyml said:
No,you didn't understand,this is not about the stock recovery.This is about the fact that you probably installed something (using CWM) that rewrited some files in the /system or other folders that this update depend on.Because those folders are modified the update doesn't recognize those apps and can't continue.That is what i am saying.Install the CWM again,search for any nandroid backups that you have on it and install the oldest one.I usualy make a nandroid backup everytime i update my phone because until the next update i keep installing stuff that messes up my ROM and in cases like yours i just apply the backup i've taken and voila,the update works.Also there is one app that messes up you'r system,it is called BusyBox,and if you install that app and want to make an update,the update will fail (red triangle) because of that app.
If you don't have any nandroid backups the only solution is to install the RUU.
Click to expand...
Click to collapse
Thanks for making it all clear I'll check if I've got a backup from when I formatted my phone (does root affect this process?)
And from what I understand, I can only install RUU that is the same as my phone's version or higher. right now I got 2.18, the TWM-TW version of the phone. know by any chance if there is an RUU for it?
The root should not affect the backup/restore proces as far as i know.Yes,the RUU must be the same as phone version or higher.Honestly i don't know any RUU for that,try searching for the new JB RUU.
EDIT:
Check you'r CID and download one of the stock nandroid backups here:
http://forum.xda-developers.com/showthread.php?t=1975140
Thanks for the nandroid, It will be my last resort if restoring a clean image won't help
and about the root - I meant if it's supposed to interfere with the update.
Thanks.
So let me get this straight. You don't have the RUU for your version at all?? and what recovery is installed right now???
No problem,if there are any other problems just ask.
@zainalabididn - I made a recovery image when i first rooted the phone (not when I first got it), but it still won't let me update over it - maybe because of the root. the recovery I'm using right now is CWM 5.8.4
@jeyml - I tried to install the nandroid in the link you gave me, but it wouldn't let me flash the hboot on my device, so after flashing the boot and nandroid it just went into loops of trying to start up, getting stuck and rebooting. got any idea why that happens? (notice: I don't have S-off, if that's what causing the problem)
when i try to install the non stock roms i get an abort message on cwm for some reason? any help?
What is your fail message? Could be your recovery version or could be your bootloader. We need more details of the problem and what you've done to troubleshoot it.
xBeerdroiDx said:
What is your fail message? Could be your recovery version or could be your bootloader. We need more details of the problem and what you've done to troubleshoot it.
Click to expand...
Click to collapse
well im on twrp 2.5 and when i try to flash it says assert failed: getprop('ro.prudect.device") == "e: Error executing updater binary in zip ' /sdcard Error flashing zip '/sdcard/download/aokp_d2att_ upadtion partition details. .. i guess it would have to be my bootloader then. ive done what task said and updated it through odin but still get this message
I downloaded the OTA update for my flo (nexus 7 wifi 2013). Checked the md5 checksum and it passes. tried to install it via asb sideload. Unlocked bootloader, stock recovery, stock system image and it says "whole-file verification", "signature verification failed", "installation aborted.
Im at at my wits end why? Everything is ****ing stock and I have re-imaged everything to ****ign stock to be sure and haven't been able to solve this for the last hour.
Any help or insight would be appreciated.
Update: Yes, I've searched this forums and others and most people come up with "its probably a corrupt download". And it is not. Also, tried iinstalled it with TWRP 2.6.3.1 , it still aborts, albeit with a different error (cant recall).
NoobieExtraordinare said:
I downloaded the OTA update for my flo (nexus 7 wifi 2013). Checked the md5 checksum and it passes. tried to install it via asb sideload. Unlocked bootloader, stock recovery, stock system image and it says "whole-file verification", "signature verification failed", "installation aborted.
Im at at my wits end why? Everything is ****ing stock and I have re-imaged everything to ****ign stock to be sure and haven't been able to solve this for the last hour.
Any help or insight would be appreciated.
Update: Yes, I've searched this forums and others and most people come up with "its probably a corrupt download". And it is not. Also, tried iinstalled it with TWRP 2.6.3.1 , it still aborts, albeit with a different error (cant recall).
Click to expand...
Click to collapse
You mentioned that it's not corrupt, but have you verified that the file isn't corrupt via something like an MD5 hash? There are numerous programs you can grab from google to do this.
The MD5 for the copy I downloaded from google: ce344ae6d5d2f74f80c9009947c9cbe9
That really should be the only reason you get that error in my experience...if you could find out what the TWRP log says that would help as well.
WHy not just go the rooted route and install this Stock Rooted 4.4.1 - KOT49E - Official Google OTA! http://forum.xda-developers.com/showthread.php?t=2558756
Ummm....yes....
OJ in Compton said:
You mentioned that it's not corrupt, but have you verified that the file isn't corrupt via something like an MD5 hash? There are numerous programs you can grab from google to do this.
The MD5 for the copy I downloaded from google: ce344ae6d5d2f74f80c9009947c9cbe9
That really should be the only reason you get that error in my experience...if you could find out what the TWRP log says that would help as well.
Click to expand...
Click to collapse
I mentioned that in my original post. Twice. I appreciate the response, but no that isn't the issue.
Because...
naturecannon said:
WHy not just go the rooted route and install this Stock Rooted 4.4.1 - KOT49E - Official Google OTA! http://forum.xda-developers.com/showthread.php?t=2558756
Click to expand...
Click to collapse
I want this stock without root. I guess, it is an option, but then I'd have to unroot it?
NoobieExtraordinare said:
I mentioned that in my original post. Twice. I appreciate the response, but no that isn't the issue.
Click to expand...
Click to collapse
I'm an idiot. Not sure how I managed to miss your first sentence, sorry about that.
Does it not say where the verification failed? It checks each system file that needs to be patched one by one and when it gets to one that's been modified it aborts the update, whenever this happens for me it says exactly which file it failed on
Nope
AlderCass said:
Does it not say where the verification failed? It checks each system file that needs to be patched one by one and when it gets to one that's been modified it aborts the update, whenever this happens for me it says exactly which file it failed on
Click to expand...
Click to collapse
Says "whole-file verification failed", "signature verification failed" and "installation aborted", like i mentioned in my post.
today all of my apps started crashing and i couldn't do anything but try to get into recovery and flash the dn4v2 rom. but couldn't due to the flashing getting stuck at updating partition details and then error 7 appearing and the flashing failed.
please help me out guys.
Aditya#714 said:
today all of my apps started crashing and i couldn't do anything but try to get into recovery and flash the dn4v2 rom. but couldn't due to the flashing getting stuck at updating partition details and then error 7 appearing and the flashing failed.
please help me out guys.
Click to expand...
Click to collapse
Try using a TWRP recovery, and flash with it.
If still the same, try going back to stock, and then start over.
no success
i was on twrp itself and then switched to cwm and i don't even have my stock backed up so i guess there's nothing that can be done here. but if there is a way then do help.
and i also needed the zip file to get back to twrp.
please help.
Aditya#714 said:
i was on twrp itself and then switched to cwm and i don't even have my stock backed up so i guess there's nothing that can be done here. but if there is a way then do help.
and i also needed the zip file to get back to twrp.
please help.
Click to expand...
Click to collapse
You don't need stock backup to get to stock!
You can boot into download mode, and flash the stock ROM with Odin using PC, that's it.
What is your phone Model number?
So i can give you TWRP link.
yeah. please gimme the link to a twrp zip file and yes i downloaded a stock rom for my samsung note 2 gt n7100 and i even got odin but when i'm trying to put the md5 file in the AP section it stops for some time and then an error message pops up.
the screenshot is attached of the error message that popped up
Aditya#714 said:
the screenshot is attached of the error message that popped up
Click to expand...
Click to collapse
The error is because the stock ROM md5 file is corrupt.
If you want TWRP to flash with odin, then here you are.
https://dl.twrp.me/t03g/twrp-3.0.2-0-t03g.img.tar.html
If you want Stock ROM, then here you go:
https://androidfilehost.com/?fid=24499762636004468