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
Could someone point me in the right direction for downloading the latest Android OS update? I'm currently running FRF83 on my rooted N1. When I select the "Restart and Install" option, it boots and says there is no signature and aborts.
Hm. I just downloaded a file named update-nexusone-FRF91-root-signed.zip, renamed it to update.zip and flashed it, but my phone still says it's running FRF83. I wish I knew what I was doing…
Command line interfaces aren't my forte, but here's what the Android system recovery program says after trying to install the update:
Build : RA-nexus-v.1.5.3
Finding update package…
Opening update package…
Verifying update package…
E:No signature (117 files)
E:Verification failed
Instalation aborted.
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.
Just downloaded the latest update and this is what's happening all the time.
I get phone with red square and question mark, I'm using vol-up and power and:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Copying fotaboot to /data/system for customise reload...
Verifying current system...
assert failed: apply_patch_check("/system/app/AppSharing.apk", "f8714e2420be7831ed33d23ef4902e57b7aa569a", "19405a34a62d20460ee421ba25f98d773468ad09")
E:Error in /sdcard/Download/OTA_PYRAMID_ICS_HTC_Europe_3.33.401.6-3.32.401.5_R_release_266230n9ouzm6y7ls02drn.zip
(Statuc 7)
Installation aborted.
How can fix this and install the update??? Thx
suchoza.neon said:
Just downloaded the latest update and this is what's happening all the time.
I get phone with red square and question mark, I'm using vol-up and power and:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Copying fotaboot to /data/system for customise reload...
Verifying current system...
assert failed: apply_patch_check("/system/app/AppSharing.apk", "f8714e2420be7831ed33d23ef4902e57b7aa569a", "19405a34a62d20460ee421ba25f98d773468ad09")
E:Error in /sdcard/Download/OTA_PYRAMID_ICS_HTC_Europe_3.33.401.6-3.32.401.5_R_release_266230n9ouzm6y7ls02drn.zip
(Statuc 7)
Installation aborted.
How can fix this and install the update??? Thx
Click to expand...
Click to collapse
That error mean you dont have the correct system version (3.32.401.5_R) installed. More likely you have 3.32.401.5 (without the _R) so you either need to download the 3.32.401.5_R RUU from Football's Shipped ROM collection thread or you need to download the 3.33.401.6 RUU from the same thread
I am having problems installing the update.zip file to my Moto Droid. When I am in recovery mode and select "apply sdcard:update.zip" the following comes up on the screen
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:EOCD marker ooccurs after start of ECOD
E:signature verification failed
Installation aborted.
I have tried deleting and re-copying the update.zip file and tried applying it again with no luck. Every time it comes up with the same message.
This is my first time rooting a device so I lack knowledge about these things.