Hi all,
My device is i9505 (international) with CM11 installed (installed via windows installer).
For some reason it tells me that my device is up to date but it is obviously not. I tried installing the latest nightly via recovery (tried TWRP and CWM) but both gave me an error saying there is some kind of signature verification failed.
Does anyone know how to solve this problem?
Thanks in advance,
Nelson
Maybe the app shows only stable version as viable updates? I don't think nightlys are classified as stable.
As for the failed verification, try turning off zip signature verification. This is done from within the recovery.
Related
Hello,
Anyone could help me with this problem:-
I have already rooted my Note 2 N7100 with Omni 4.4.2 Nightly but somehow, on software update, with an update available after checking it, I was unable to flash it successfully. There was an error. I have checked SuperSU as to install SuperSu backup script as I believe it would help me to do update on the current build but I could not do that as it requires installing SuperSu into/system (converting into a system app) first but when I have tried to install and later rebooted my device, it was still the same. On Custom Rom, I could not install supersu backup script and when trying to flash update (after checking it and update is available, it was again not successful.
Any advice?
Salam Husin said:
Hello,
Anyone could help me with this problem:-
I have already rooted my Note 2 N7100 with Omni 4.4.2 Nightly but somehow, on software update, with an update available after checking it, I was unable to flash it successfully. There was an error. I have checked SuperSU as to install SuperSu backup script as I believe it would help me to do update on the current build but I could not do that as it requires installing SuperSu into/system (converting into a system app) first but when I have tried to install and later rebooted my device, it was still the same. On Custom Rom, I could not install supersu backup script and when trying to flash update (after checking it and update is available, it was again not successful.
Any advice?
Click to expand...
Click to collapse
Flash SuperSU in recovery and then you should be able to install the backup script.
I was trying to upgrade from CM10.2 to CM11 (M2 Snapshot) and now I'm getting status 7 and can't install the CM11 image. I can't boot now either. I queued both this and the 4.4 google apps up (that is a mistake I guess?) and I'm guessing it went ahead and installed the incompatible google apps even though the CM11 failed.
So I'm thinking the status 7 error is because my TWRP image is outdated, because I have the correct CM11 for my device. Is there a way to update TWRP from within TWRP? I am not seeing the option. I do have the recovery.img on the device.Not sure what else it could be. Do I have to load ADB and use it to flash an updated recovery now?
Any help would be appreciated. Kind of desperate here since nothing is working at this point.
I got it sorted out... loaded the SDK, managed to update the TWRP image to something more current with fastboot and finally was able to install the CM11 zip without the status 7 error.
Hi,
I originally posted this over at android central where I was told it is not possible to root a Moto G4, so I am trying here hoping for a different answer = )
I am attempting to install Cyanogenmod on my handset using the below guide:
Install_CM_for_peregrine (looks like I can't post link but that is the name of the page on he Cyanogenmod site)
I have unlocked the handset, copied the Cyanogenmod zip file to my sdcard, booted in recovery mode and attempted to install the zip package. At this point I get an error "E:failed to verify whole-file signature". I have tried both the stable and nightly build with the same result. Also when I have attempted to install SuperSU using the same process have received the same error so I suspect it is not a corrupted file.
I believe this is being caused by the signature check and to get around this have been following the below guide to disable signature check:
tutorial-how-to-disable-signature-check.html (name of the tutorial as can't post links)
When it comes to the step "Then find a option Called "Patch To Android", I don't see this option, and from what I understand this may be due to not having my phone rooted.
I have installed Kingo ROOT to resolve this but it failed to root the handset (error 0x1C5C33 if that means anything to anybody), checking the list of phones which Kingo ROOT can root, Moto is not one of them. What are the other options?
Any advice greatly appreciated. Thanks in advance.
Get rid of kingo. Look up android doctor on YouTube for unlock, root, twrp instructions. CM has a lot of bugs and isn't ready for daily use on this device. Slim roms has released their rom, it's CM based. I've been using it for a few days, and it's running smooth. There's a thread about it with the link on here. The only problem I've had was a boot loop when I try and flash xposed and supersu. There's a built in super user access in the settings, so supersu isn't necessary.
hooks024 said:
Get rid of kingo. Look up android doctor on YouTube for unlock, root, twrp instructions. CM has a lot of bugs and isn't ready for daily use on this device. Slim roms has released their rom, it's CM based. I've been using it for a few days, and it's running smooth. There's a thread about it with the link on here. The only problem I've had was a boot loop when I try and flash xposed and supersu. There's a built in super user access in the settings, so supersu isn't necessary.
Click to expand...
Click to collapse
Phone rooted, thanks!
Now to install SlimRoms
Strange, after rooting gained the below options in Lucky Patcher:
Signature Verification Status always True
Disable .apk Signature Verification
Disable signature verification in the package manager
Patch applied for all three, but then when I restart in recovery mode and attempt to install the SlimRoms zip still getting error "E:failed to verify whole-file signature".
I didn't patch anything. Just root, installed twrp, and flashed slim rom and gapps
hooks024 said:
I didn't patch anything. Just root, installed twrp, and flashed slim rom and gapps
Click to expand...
Click to collapse
Ah I see, did not realise you install the rom via twrp. It's installed now, awesome, thanks.
Hello!
I have a S5 with CM13 and the CM recovery.
I have tried to wipe everything and install LineageOS 14.1.
I got the "failed to verify signature" error.
I cannot disable signature verification because that doesn't exist in CM recovery (or does it??).
I want to update my recovery to TWRP's and try to install LineageOS again.
Can I simply use their official app? Or would it be an issue since the current recovery is CM ?
Thanks !
Bump for an easy question!
Thanks!
Hey hey hey!
Still looking for that information in case anyone knows the answer.
Thank you!
For a few days now i have being trying to install a customer ROM on my Samsung J5, EVERY ROM i have downloaded has failed with errors stating that the ROM is for J5nlte NOT for j5nltexx even if the file name has been relating to j5nltexx.
I have tried to change/remove the assert line in the install package with no success.
has anybody got/or can recommend a ROM that WILL work with samsung J5 (j5nltexx) - I Currently have a phone that will not boot into a ROM, but will happily boot into TWRP 3.1.1-0
***Update***
The CM13 firmware installed and initially booted, but then went into a boot loop at "optimising apps", still unable to successfully install a custom ROM of any sort, tried Skies and ASUX both didn't boot, even with an Aroma aware TWRP install (confirmed by attempting to install CM13)
Since rebuilding with a "greek" factory ROM, my phone is now showing as sm-j5lte anymore advise will be well recieved
Thanks in Advance
PB
pdjbarber said:
For a few days now i have being trying to install a customer ROM on my Samsung J5, EVERY ROM i have downloaded has failed with errors stating that the ROM is for J5nlte NOT for j5nltexx even if the file name has been relating to j5nltexx.
I have tried to change/remove the assert line in the install package with no success.
has anybody got/or can recommend a ROM that WILL work with samsung J5 (j5nltexx) - I Currently have a phone that will not boot into a ROM, but will happily boot into TWRP 3.1.1-0
Thanks in Advance
PB
Click to expand...
Click to collapse
first install a aroma supported recovery then install ASUX or Skies ROM i should boot if it dosent let me me know with the error
I have managed to get a booting phone, using an old Samsung Factory ROM (5.1.1), re-rooted using CF-Auto-Root. Re-installed TWRP (this time with Aroma support) from @Zonic here To be able to install CyanogenMod 13.0 for Galaxy J5 Here do i need to Marshmallow (6.0.1) BEFORE i attempt a firmware upgrade?
Thanks