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 flashed .26 to.30 fine now when I put the TF700T US_10.4.4.16-20120927 OTA.zip file in SD card then go to recovery I get this.
Finding update package...
Opening bundle update package...
E: can't open /SD card/ASUS bundle.zip
( no such file in directory)
Installing update...
Finding update package...
Opening update package...
E: failed to open /sdcard/ep201_768_sdupdate.zip ( no such file or directory)
E: signiture verification failed
SD installation aborted
I also changed the file name like I read
Know I'm doing something wrong just don't know what
Thnx.
Dr. Greenthumb said:
I flashed .26 to.30 fine now when I put the TF700T US_10.4.4.16-20120927 OTA.zip file in SD card then go to recovery I get this.
Finding update package...
Opening bundle update package...
E: can't open /SD card/ASUS bundle.zip
( no such file in directory)
Installing update...
Finding update package...
Opening update package...
E: failed to open /sdcard/ep201_768_sdupdate.zip ( no such file or directory)
E: signiture verification failed
SD installation aborted
I also changed the file name like I read
Know I'm doing something wrong just don't know what
Thnx.
Click to expand...
Click to collapse
You still have the stock recovery installed. You have to flash that zip with a custom recovery. Install TWRP or CWM and give it another go.
got twrp
urrlyx said:
You still have the stock recovery installed. You have to flash that zip with a custom recovery. Install TWRP or CWM and give it another go.
Click to expand...
Click to collapse
I got twrp installed it just won't go into boot recovery so do you know the manual button combo for twrp?
Can't seem to get into twrp reboot just goes to stock recovery even on manual
Just a thought... when you flash a stock image you will lose root. Even though the Goomanager looks like it is installing the twrp it wont work without root. Check your root status through Titanium or rootkeeper etc. Sometimes the debug method seems to tell you that you have root when none of the programs are getting root access.
Hello
Several days ago, there is notif that new firmware available to downloaded, so i downloaded via setting>about device>check for update or whatever it is,(its on indonesian language so i dont know the exactly meaning in english )
The download finish, then i click install on complete download notif. And my device go to cwm recovery
The problem start here, it says signature verification failed, i reboot and install newest cwm recovery v6.x.x.x, start to redownload the firmware just like before and copy the update.zip from root/cache/fota (the firmware is big enough for my poor internet network, about 400mb, so if my next install error again, i can simply reinstall update.zip without download again ang again)
On cwm recovery, i install the update.zip within disabled signature verification, but new problem appear
Below is the log of my error
Finding update package...
Opening update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check ("/system/lib/libGLESv1_CM.so". "ed4c783blablabla
E:error in sdcard/update.zip
Installation aborted
Any issue how to fix that ??
Sorry if my english bad and im newbie on android:silly: so i dont know deeply about android system
PS. My galaxy tab p3100 in on rooted status
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
I have a Galaxy S4 (SGH-M919V) which is the Canadian Variant (Wind/Mobilicity). I used Cyanogenmod Installer and it identified my phone as jfltecan (Canadian Variants) which is good, it got my phone rooted and CM on it but it was KitKat and CM didn't support Lollipop on jfltecan.
Therefore, I manually flashed a jfltetmo (T-Mobile) nightly-may-1st which is similar to SGH-M919V by opening up the script update file and getting rid of the "assert" code that checks if you have the correct phone and correct file. I have SGH-M919V phone and jfltetmo file. was successful and got 5.1.1 Lollipop and my sim working. Few days later, now there's multiple nightlies and I try to use the built in updater to get the most recent nightly. I download it and tap to install it, it takes me to CWM recovery, and displays the following. (Problem #1)
Finding update package...
E: unknown volume for path [@/cache/recovery/block.map]
E: Can't mount @/cache/recovery/block.map
Installation aborted.
Rebooting...
That didn't work but I had that installation zip file downloaded therefore I went to recovery and manually installed it, is displayed the following. (Problem #2)
Finding update package...
Opening update package...
Installing update...
This package is for device: jfletmo, jflte; this device is jfltecan.
(Status 7)
Installation aborted.
The status 7 can be fix by opening up the script update file and removing "assert" code but I don't want to do that for every nightly I will install. Can anyone help me to a solution to problem 1 and 2 or at least one of them. I would really absolutely appreciate it. Thank You.
Hi, thank you for using XDA Assist. I suppose you could edit your build.prop on your device to show the product and device that's listed in the assert line of the rom's updater.script. But be careful as flashing stuff not for your specific device can brick it.
Thread closed.