So, I was trying to Install CM13 on OnePlus One without Root or unlocking the bootloader(using Stock CM Recovery).
When I tried to update it shows the following on the cyanogen recovery screen
"Install failed.
Finding update...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted."
Current operating system.
12.1.1-YOG7DAS2K1
Trying to install:
Download: cm-13.0-20160310-NIGHTLY-bacon.zip (328.14 MB)
sha1: f08287b6884e6e465ec46eaaa1291488678dd2e9
From: https://download.cyanogenmod.org/?device=bacon
Solution? Please advise. Thanks
sowad9 said:
So, I was trying to Install CM13 on OnePlus One without Root or unlocking the bootloader(using Stock CM Recovery).
When I tried to update it shows the following on the cyanogen recovery screen
"Install failed.
Finding update...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted."
Current operating system.
12.1.1-YOG7DAS2K1
Trying to install:
Download: cm-13.0-20160310-NIGHTLY-bacon.zip (328.14 MB)
sha1: f08287b6884e6e465ec46eaaa1291488678dd2e9
From: https://download.cyanogenmod.org/?device=bacon
Solution? Please advise. Thanks
Click to expand...
Click to collapse
Seriously what made you think you can flash custom software without unlocking your bootloader? Either stick to stock OS or if you wanna enjoy CM13 you have to unlock and install a custom recovery
Sent from my A0001 using Tapatalk
Renosh said:
Seriously what made you think you can flash custom software without unlocking your bootloader? Either stick to stock OS or if you wanna enjoy CM13 you have to unlock and install a custom recovery
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
You sound like a bit of a ****
He is right though.
The way op describes it, it sounds as if he actually knows that the bootloader
should be unlocked. But at the same time he is amazed that it does not work.
Then this "solution?"... Seriously?
There are guides on xda for unlocking and flashing for a reason.
Pretty dumb and useless thread if you ask me.
Related
Okay here's my problem. My phone has been asking to update for a while so I restored to a recovery with the stock kernal and unrooted it. I go to install the update and I am getting an error. I click instal, my phone turns off like its suppose to, recovery mode then appears says there's been an error update failed.
Anyone know what I did/what I can do to fix this?
edit: heres exactly that it says:
ClockwordMod Recovery v3.0.0.5
Finding update package...
E:unknown volume for path [SDCARD:download/OTA_Vision_BellMobility_WWE_1_84_666_2-1_34_666_5_release_172473wagbpno61mgwg4k0.zip]
E:Can't mount SDCARD:download/OTA_Vision_BellMobility_WWE_1_84_666_2-1_34_666_5_release_172473wagbpno61mgwg4k0.zip
Also When I try to install zip from sdcard is says:
Installing: /sdcard/download/OTA_Vision_BellMobility_WWE_1_84_d666_2-1_34_666_5_release_172473wagbpno61mgwg4k0.zip]
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
Hey I have this same problem! Where can I get a copy of the OTA update or something else? I also tried updating to cyanogenmod 7 and can't get it to work either
i had this problem with my sgs2 for there update, i unrooted went back to the stock like the phone was brand new , did you do the same?
No, I am not sure I want to go back to unrooted, the bacckup options just aren't as good. I guess I want the best of both worlds, to have htcsense and to be able to back it up completely. (It's really my dad's phone, I'm not so tied to htc sense)
First time trying to install a ROM other than the default on my AT&T Nexus S. Unlocked the boot loader. Installed Clockwork. Downloaded the NexusBeam4.01 and named the file update.zip. Copied it to the SD card, rebooted, told it to update from the zip file. I get the following:
-- Install /sdcard --
Finding update package....
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
e:signature verification failed
Installation aborted.
Being new, I was hoping someone could tell me where I went wrong. Nexus S, AT&T.
Thank you.
Mike.
Got it figured out. I had unlocked the bootloader, but not rooted. All better now. Sorry for the newbie intrusion.
Mike.
I keep getting an OTA notification, but when I try to install it, the update always fails. My Android version is currently 4.0.4. My phone is rooted and have the custom recovery installed. When I try to install the update, the phone reboots into recovery and always fails with the following details:
CWM-based recovery v5.5.0.4
E: Invalid command argument
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted.
What is this update? Should I just keep trying? Do I need to do something to make it work? Or should I just install the new leaked JB ROM?
MrGibbage said:
I keep getting an OTA notification, but when I try to install it, the update always fails. My Android version is currently 4.0.4. My phone is rooted and have the custom recovery installed. When I try to install the update, the phone reboots into recovery and always
Click to expand...
Click to collapse
I believe you can't be on a custom recovery and successfully install an OTA update on its own.
- ooofest
MrGibbage said:
I keep getting an OTA notification, but when I try to install it, the update always fails. My Android version is currently 4.0.4. My phone is rooted and have the custom recovery installed. When I try to install the update, the phone reboots into recovery and always fails with the following details:
CWM-based recovery v5.5.0.4
E: Invalid command argument
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted.
What is this update? Should I just keep trying? Do I need to do something to make it work? Or should I just install the new leaked JB ROM?
Click to expand...
Click to collapse
Any OTA update, you need to go back to pure stock rom, meaning no root, no custom rom, no cwm. Sooner or later you need to move on to Jelly Bean, so yeah, prepare yourself, do a full backup of your apps (not system apps), go back to stock then take the OTA. Second option, disabled the OTA notification for now and wait for JB custom rom build for official Jelly Been.
That all makes sense. Thanks, guys!
Please make a working guide/tutorial to install the Official Cyanogenmod 12 on Moto G XT1033 which has been converted to GPe 5.0.1.And pls provide a fix to make the sims work, even one working sim is good if not the both of them.
Thanks...
1. Take a backup of your Current rom first
2.download any cm12 rom and place it in the root of the SD card
3. Boot in to twrp recovery and do factory reset
4. Flash CM12 rom
5. Flash donkey kernel..
6.reboot and check..
7. If not working, restore your backup
But this doesn't work for the Official Cyanogenmod Nightly.
modifan14 said:
But this doesn't work for the Official Cyanogenmod Nightly.
Click to expand...
Click to collapse
How long did you wait on the first boot? It can take like...10 minutes.
modifan14 said:
Please make a working guide/tutorial to install the Official Cyanogenmod 12 on Moto G XT1033 which has been converted to GPe 5.0.1.And pls provide a fix to make the sims work, even one working sim is good if not the both of them.
Thanks...
Click to expand...
Click to collapse
I have the same problem. I have gpe 5.0.1 bootloader and all recovery can't flash cm12 nightly : flash error with twrp 2.8.3, Phil'z and CWM.
Quentinga said:
I have the same problem. I have gpe 5.0.1 bootloader and all recovery can't flash cm12 nightly : flash error with twrp 2.8.3, Phil'z and CWM.
Click to expand...
Click to collapse
Are you getting the error about mounting /system? I tried the 2.8.1.0 version of TWRP and was able to mount the /system partition successfully. I haven't had the time to flash a rom but you can try if this version works for you.
andogeek10 said:
Are you getting the error about mounting /system? I tried the 2.8.1.0 version of TWRP and was able to mount the /system partition successfully. I haven't had the time to flash a rom but you can try if this version works for you.
Click to expand...
Click to collapse
No: my log
flash history
-- Installing: /sdcard/0/cm-12-20150107-NIGHTLY-falcon.zip
Finding update package...
Opening update...
Installing update...
E: Error in /data/media/0/cm-12-20150107-NIGHTLY-falcon.zip
(Status 1)
Installation aborted.
Click to expand...
Click to collapse
cwm log
-- Installing: /sdcard/0/cm-12-20150107-NIGHTLY-falcon.zip
Finding update package...
I : Update location : /data/media/0/cm-12-20150107-NIGHTLY-falcon.zip
Opening update...
Installing update...
about to run program [/tmp/backuptool.sh] with 2 args
Not backing up files from incompatible version: 12
run_program: child exited with status 127
about to run program [/tmp/otasigcheck.sh] with 1 args
erasing 249856 blocks
blkdiscard failed: Invalid argument
writing 111672 blocks of new data
lseek64 failed: Invalid argument
E : Error in /data/media/0/cm-12-20150107-NIGHTLY-falcon.zip
(Status 1)
Installation aborted.
I : using /data/media for /sdcard/0/clockworkmod/ .last_install_path.
I : Cannot load volume /misc.
Return to menu with any key.
Click to expand...
Click to collapse
That's because of the updated partition table. I also had the same error on GPE 4.4.4. Try flashing vanir, it worked for me.
Hi Guys,
Please help My phone is continuously downloading OTA update and cannot update the OTA. Finished my mobile DATA because of multiple download of 565 mb file. Tried updating manually from recovery but gives the following error.
uwhen i flash OTA incremental update zips
YOG4PAS47N from YNG1TBS2P2: cm-lettuce-79f9ccdc85-to-bafcc5769e-signed.zip
Install failed
Finding update package...
opening update package...
verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted.
pls help.
There is no way to relock bootloader
Sent from my SpiceMi-511 using XDA-Developers mobile app
disable signature verification in TWPRP settings.
and then try to flash again ROM
i hope it will help you
I want to unlock my bootloader which is locked by componey pls help