Hi,
as i already told in another thread, i just successfully rooted my magic. But now i tried to patch the security update "CRB43" using this link http://android.clients.google.com/up...F.29b87a90.zip
But after i renamed it to update.zip and started the update i get the error:
...
Verifying update package
E:No signature (136 files)
E:Verification failed
Installation aborted.
Isn't this working after the Haykuro procedure?
Thanks and cheers,
Dirk
have you installed the latest Haykuro SPL??
If not just install it and it should sort the problem.
Same problem with the latest Haykuro SPL (the patch check the number version... 1.33.2004 != 1.33.2005 hyk) and check the touched file signature.
we need, to solve a problem, a clean image of system and unroot the magic
have you tried re rooting and then apply the last SPL?
this is because the recovery.img you are using is for test-keys. not naturally signed updates.
i wasn't aware you guys had an update! i will release a build for this ASAP
haykuro Can you provide us a untouch SPL (004)
thanks
guys, am i sort of a stupid?!? my update wont apply too... i've got the italian vodafone magic rooted... but i miss the simplicity and the safety of a standard non rooted device... i really want it back...
is there a guide to easily revert the procedure and get the software like when i had may magic unboxed?!?
thank you all for the efford, it's just that all this doesn't suit for me =)
we don't have original recovery.img, but can we mod the security update signature, a it work with test-keys recovery ??
hi!
in the security update zip, dir /system ( http://android.clients.google.com/updates/signed-vfpioneer-CRB43-from-CRB17-KF.29b87a90.zip ) there is the orig "recovery.img"
move to dir tools/ of sdk, open terminal with magic in fastboot mode, "fastboot flash recovery recovery.img" and now open recovery mode (home+power, 2times).
link is not working
guinnes.s said:
link is not working
Click to expand...
Click to collapse
try:
http://www.megaupload.com/?d=OIW5FR8S
@nk02
which spl are you using? What happend after you used the recovery.img, are you still able to havbe root access or what does it affect? Sorry but i'm a little bit confused.
Thanks.
diRm said:
@nk02
which spl are you using? What happend after you used the recovery.img, are you still able to havbe root access or what does it affect? Sorry but i'm a little bit confused.
Thanks.
Click to expand...
Click to collapse
simply with orig recovery.img you can't flash rom with testkey (rom cooked..)! but root access remain on your rom.
however, after the update crb43 you can reflash haykuro's recovery.img!
ps: i'm using haykuro's spl, but my magic doesn't notify me system update, therefore i can't try update...
pps: sorry for my english
i think haykuro as removed the OTA update function from his releases for obvious reasons.
I tried this and on the surface it looks like the recovery has flashed the original fine as I now get the original recovery utility.
When it launches I get - E:Can't open /cache/recovery/command
When I try to apply the new security update from /sdcard/update.zip I get:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
E:Failure at line 4:
assert getprop("ro.bootloader")
== "1.33.2004" || getprop("ro.bo
otloader") == "1.33.0004
Installation aborted
Have I missed something and can someone help me out?
I retried and flashed with the recovery.img within the security update and now I get:
E:Can't open /cache/recovery/command
When I try to apply the new security update from /sdcard/update.zip I get:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:No signature (136 files)
E:Verification failed
Installation aborted
Any ideas?
Any news about this particular problem?
Has anyone successfully updated their Sapphire with the update CRB43 on a Rooted phone? If so - please can you explain your method.
This thread seems to have stopped
Solution: Update Rooted CRB17 to Original CRB43
To update rooted Magic you need:
1) Original system.img from previous backup with nandroid
Flash in hboot mode with fastboot
2) Original SPL 1.33.2004 or my SPL mod http://uploadbox.com/files/88b081fe77
rename in update.zip and flash with haykuro mod recovery
3) Original recovery.img (i create a fastboot version) http://uploadbox.com/files/3baefad7c7
flash in Hboot mode with fastboot.
Bye..
Crios,
thanks again, how did you flash it?
fastboot flash? Or did you use
fastboot boot?
Could you write the whole fastboot command down?
Thanks for your continued assistance
Dirk
I am trying to install an update.zip on to my Droid 1, which is rooted, but I am getting the following output:
Code:
-- Install from sdcard...
Finding update package...
Verifying update package...
E:signature verification failed
Installation abored.
What is this verification process? Do I need to do this using a custom recovery mode of some sort? I think I am still using the android system recovery system.
I am not pro but I think its not possible to install on original recovery as its not signed by android.
You need to install custom recovery available and disable signature verification.
when I try to install the 4.4.4 update it aborts with the message below.
Code:
Verifying current system...
"system/build.prop" has unexpected contents.
Installation aborted.
I don’t recall editing the build.prop file and I don’t have a backup. I’ve tried flashing the update in both CWM and the stock recovery but it fails either way.
Any ideas about what I can do? :crying: :crying: :crying:
nebrass said:
when I try to install the 4.4.4 update it aborts with the message below.
Code:
Verifying current system...
"system/build.prop" has unexpected contents.
Installation aborted.
I don’t recall editing the build.prop file and I don’t have a backup. I’ve tried flashing the update in both CWM and the stock recovery but it fails either way.
Any ideas about what I can do? :crying: :crying: :crying:
Click to expand...
Click to collapse
The build.prop is edited, flash a complete stock rom or a stock build.prop and try again
Hi there, if anyone could help me get through this installation, it'd be greatly appreciated.
I'm a newbie at flashing, but not a newbie with computers.
I'm trying to flash CM 11S v1.5 but have run into numerous issues. I'm running CWM, have updated bootloader (HHZ11K), and my drivers are on point.
Right now, I'm trying to have it install from the zip in the root directory, and it won't install:
"E:Can't open ... (bad)
Installation aborted."
If I toggle signature verification, it says:
"Finding update package ...
Opening update package...
Verifying update package...
E:footer is wrong
E:signature verification failed"
What am I doing wrong?
Bad means corrupt. Re-download
Sent from my Nexus 5 using Tapatalk
Hi,
I've downloaded the lastest nightly version for Nexus 5 for installing CyanogenMod into it. The problem is that when I loaded the zip into my phone using adb and the command "adb sideload <file>", it couldn't verify the file and gave me this message:
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted.
Click to expand...
Click to collapse
I've been searching for a solution but I couldn't find anything.
What am I doing wrong?
Thanks!
Well, it was simply my fault to not being properly informated...
The thing was that I didn't have my recovery image updated, so it couldn't install me a newer version because it didn't support it.
What I did was simply install a proper CWM recovery and thus, I was able to install my newly CM.
Hi Please can you send me the link to link to install cwm recovery. I have same issue stuck in e: signature verification failed