I grabbed a ROM from here and deleted some unwanted apps, and added a couple that I wanted so I wouldnt have to do it after I flashed and zipped it back up. When going to flash it to my phone I get a "E: No signature (830 files)... E: Verification failed. Installation aborted."
Im very new to all this so please dont flame me. Is it simple enough to sign & verify it so I can flash it, or will I have to flash the original and uninstall the unwanted apps via adb?
Thanks in advance.
The Jero said:
I grabbed a ROM from here and deleted some unwanted apps, and added a couple that I wanted so I wouldnt have to do it after I flashed and zipped it back up. When going to flash it to my phone I get a "E: No signature (830 files)... E: Verification failed. Installation aborted."
Im very new to all this so please dont flame me. Is it simple enough to sign & verify it so I can flash it, or will I have to flash the original and uninstall the unwanted apps via adb?
Thanks in advance.
Click to expand...
Click to collapse
You can sign it and then flash. Try this
http://androidforums.com/developer-101/8665-how-signing-roms.html
Jus10o said:
You can sign it and then flash. Try this
http://androidforums.com/developer-101/8665-how-signing-roms.html
Click to expand...
Click to collapse
Thanks man! I got it all resigned and went to flash but now it got all the way to "Installing update..." then I recieved a "E:Can't find update script Installation aborted."
I guess I'm going to have to do a lot of forum searching and reading to get this running!
Jus10o said:
You can sign it and then flash. Try this
http://androidforums.com/developer-101/8665-how-signing-roms.html
Click to expand...
Click to collapse
Just to add a little more info if your using someone elses updatezip make sure you delete the apks sha1 or anything else you aren't using out of the manifest. also avabox works great. all in one tool for signing apps unyaffs and so fourth
The Jero said:
Thanks man! I got it all resigned and went to flash but now it got all the way to "Installing update..." then I recieved a "E:Can't find update script Installation aborted."
I guess I'm going to have to do a lot of forum searching and reading to get this running!
Click to expand...
Click to collapse
You need to zip the contents of the rom folder, and not the folder itself. Go into the ROM folder, select all the files (system, boot.img, meta-inf, etc) and zip it that way. Then, sign THAT zip, and you're good to go.
HeroMeng said:
You need to zip the contents of the rom folder, and not the folder itself. Go into the ROM folder, select all the files (system, boot.img, meta-inf, etc) and zip it that way. Then, sign THAT zip, and you're good to go.
Click to expand...
Click to collapse
I'm editing the update-script with Word Pad, then re-saving it. Is this the wrong way to do it?
I'm getting an error (Status 6) when I run my .zip update, every time.
http://forum.xda-developers.com/showthread.php?t=763406
i just put this up bro check it out
Thank you now I learned how to sign roms I just modded...
Problems signing with stock recovery
I am trying to reuse an old LG L45C and I need to flash the stock rom however I get "E: failed to verify whole-file signature" Could anybody sign this for me?
https://www.dropbox.com/s/04o8d0har828chm/Stock_L45C_Rom.zip?dl=0
I am on the stock recovery <3e>
I'm trying to make a file package that will install a file manager and terminal emulator. The device only reads a file package that has am zip md5 and zip sig. Can anyone help me set up something like this
Related
Since we have rooted it now SPL seems to be useless.
----
Well, this is the original SPL image on Tattoo, nothing related to update.zip.
----
I was trying to reverse it, and just found why it refuses to erase, but I could not find why it refuses to download data from the host.
----
By now, to flash SPL or the first splash, you need a custom kernel with additional partition information and then use flash_image is OK.
tewilove said:
Since we have rooted it now SPL seems to be useless.
Click to expand...
Click to collapse
useless !! nope defo not, thanks for the input..
are you new here or regular user with new I.D. ??
..
definitely tewilove ; i loved this since long time.... is it correct that i rename it as update.zip & boot into recovery, then apply update.zip ???
one more question : will it change my baseband version from G to H ?, which is non 3G to 3G firmware...
i am dying here someone would come up with this innovative upload. thanks tewilove for this wonderful upload....
@tewilove, ur zip file is not signed.... when i tried updating it in recovery mode, it says verification failed, no signature....
what to do buddy ?
manuvaidya said:
@tewilove, ur zip file is not signed.... when i tried updating it in recovery mode, it says verification failed, no signature....
what to do buddy ?
Click to expand...
Click to collapse
sign it urself using testsign.jar
svprm said:
sign it urself using testsign.jar
Click to expand...
Click to collapse
how do i do it ??? little brief explanation would have been much better rather than telling me do it myself right ???
I have a dead Tattoo.. stucked in tattoo logo at the boot... it's possible to use this spl for heal?
Lox_Dev said:
Original post:
Now you are going to sign the zip file. Download attached testsign.zip and copy it in your <SDK>/tools folder. Extract it here. It should create a sign subfolder with a testsign.jar file in it.
Then, from <workdir> folder, do:
java -classpath <SDK>/tools/sign/testsign.jar" testsign file.zip file-signed.zip
Ok, now your zip file is ready to be deployed using cyanogen recovery image.
Click to expand...
Click to collapse
Test Jar:http://forum.xda-developers.com/attachment.php?attachmentid=220533&d=1251207154
after i signed the file and try to flash i get the following message:
E:Can't find update script
Any ideas?
svprm said:
Test Jar:http://forum.xda-developers.com/attachment.php?attachmentid=220533&d=1251207154
Click to expand...
Click to collapse
i am sorry. i couldnt succeed in signing it with testsign.jar file u uploaded....
could u please do it for me... just a favour. i think i am missing out some important step whicch i couldnt figure it out.... please test sign it & upload it here.....
moved to here
Hi!
I have tried to create my own update for Milestone, unfortunately I can't get it to work. I copied the test updates from OpenRecovery and edited the update-script but it did not work.
I copied over test-update-or.zip and unpacked it, then I threw my stuff into the system and modified the bash script in META-INF. The whole thing look like this:
And when I try to apply this, I get:
Code:
(...) Using default updater...
E:Error in /sdcard/OpenRecovery/updates/moj-update.zip
(Status 4)
Installation aborted
What am I doing wrong?
Quintasan said:
Hi!
I have tried to create my own update for Milestone, unfortunately I can't get it to work. I copied the test updates from OpenRecovery and edited the update-script but it did not work.
I copied over test-update-or.zip and unpacked it, then I threw my stuff into the system and modified the bash script in META-INF. The whole thing look like this:
And when I try to apply this, I get:
Code:
(...) Using default updater...
E:Error in /sdcard/OpenRecovery/updates/moj-update.zip
(Status 4)
Installation aborted
What am I doing wrong?
Click to expand...
Click to collapse
You should apply it as a nandroid restore through the nandroid menu!? Anyone?
vladstercr said:
You should apply it as a nandroid restore through the nandroid menu!? Anyone?
Click to expand...
Click to collapse
Sir, do you realise that I'm trying to create an UPDATE package, not a NANDROID BACKUP?
Quintasan said:
Sir, do you realise that I'm trying to create an UPDATE package, not a NANDROID BACKUP?
Click to expand...
Click to collapse
Yes... But thats the same error I got when I tried to restore a nandroid backup through "apply update"
Thats why I said that...
Quintasan said:
Hi!
I have tried to create my own update for Milestone, unfortunately I can't get it to work. I copied the test updates from OpenRecovery and edited the update-script but it did not work.
I copied over test-update-or.zip and unpacked it, then I threw my stuff into the system and modified the bash script in META-INF. The whole thing look like this:
And when I try to apply this, I get:
Code:
(...) Using default updater...
E:Error in /sdcard/OpenRecovery/updates/moj-update.zip
(Status 4)
Installation aborted
What am I doing wrong?
Click to expand...
Click to collapse
attach your update.zip file so we can have alook will make it easier for helping
Here you go, thanks in advance
bumping form the depths of hell and because I'm too lazy to keep note of what changes I do each reflash
ok well first of all your directory structure doesnt seem good , meta-inf and other folders needs to be in the root of the zip file .
I suggest you grab latest CM6 by kabaldan and copy what hes doing and replace files .
good luck
Hi!
Can someone help me by uploading the .apk of Amazon Mp3 from FRG83G?
I deleted the app a while ago and Gingerbread update won't proceed unless it is present
Thanks!
Are you rooted? If so it's not going to work. U uploaded it and it went missing? Confused.
Sent from my Nexus One using XDA App
If you install the apk, would it still not go into the /data partition?
I think Geo mentioned that install the Amazon MP3 from the market won't work because the install would go into the /data partition and not in the /system partition as originally shipped with the ROM.
I had removed the Amazon app too. Could someone please upload the com.amazon.mp3.apk
from frg83d?
I wouls then be able to restore it with root explorer.
I just copyied an .apk from FRF91 but it didn't work either. I've got an error again:
assert_failed: apply_patch_check("/system/app/com.amazon.mp3.apk", ""ff8ad0f610cfdd4a632567bd823d3a659421aa44", "c2a88c45aa6e99c0a0062620c5d2618ea620ef53")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
rcknr said:
I just copyied an .apk from FRF91 but it didn't work either. I've got an error again:
assert_failed: apply_patch_check("/system/app/com.amazon.mp3.apk", ""ff8ad0f610cfdd4a632567bd823d3a659421aa44", "c2a88c45aa6e99c0a0062620c5d2618ea620ef53")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
With this file it works fine - http://www.freewarelovers.com/android/download/temp/1288197512_Amazon_MP3_1.8.29.apk
[Q] Gingerbread 2.3.3 update problem on Nexus One! - Need AmazonMP3
Trying to update my Nexus with 2.3.3 update, but I deleted the Amazon MP3 apk ages ago, and the 2.3.3 update fails trying to patch it.
Can someone PLEASE email me the apk (and path) from a Froyo FRG83G Nexus One, so that I can put it back? An APK from any build might help! [email protected].
Thank you so much in advance
Steve...
Download a .ZIP format stock firmware from here;
http://android.modaco.com/content/g...es-zip-online-kitchen-optional-root-insecure/
Extract the files you need from there.
rcknr said:
With this file it works fine -
Click to expand...
Click to collapse
Just installing that file didnt help Still getting the same error. Can anyone help? Is it a location issue? How to get it back into its original location?
Get this file:
http://android.clients.google.com/packages/passion/signed-passion-ota-43546.cc653ee4.zip
Extract com.amazon.mp3.apk
copy it into /system/app/
you're done.
Code:
- type 'adb remount'
- type 'adb push com.amazon.mp3.apk /system/app/com.amazon.mp3.apk'
(you need to be root to write to /sys/apps)
It Works!
rcknr said:
With this file it works fine - http://www.freewarelovers.com/android/download/temp/1288197512_Amazon_MP3_1.8.29.apk
Click to expand...
Click to collapse
THANK YOU If anyone else is doing this. You need to download the file (http://www.freewarelovers.com/android/download/temp/1288197512_Amazon_MP3_1.8.29.apk) and then rename it to com.amazon.mp3.apk.
Once renamed, use adb to push it to /system/app.
It works, I've updated to Gingerbread, and I'm VERY VERY happy
Thanks, Steve
progam to create update.zip.
x8 naa
download link pleasea
notepad.exe to write up the updater-script
Any program that can create ZIPs
EDIT: And it might also help to read the articles on the XDA portal page from time to time.
progam already have. but when I try to install the update, looks like this "installation aborted"
lucaslc7 said:
progam already have. but when I try to install the update, looks like this "installation aborted"
Click to expand...
Click to collapse
Then you have a syntax error in your updater-script, easy as that.
never mind it. Thanks for trying to help
Look for update zip creator.. I cant find the link. There is a wizard which helps you create a update.zip
Hi All,
I'm relatively new to Android (had the Nexus 7 for about a year). My questions is this:
I have 4.2.2 currently loaded. When I orinally got the nexus 7, I used a toolkit to unlock the bootloader and root the device, so I could install SixAxis and a few other apps that required root.
What is the easiest way for me to now update to 4.3? Will the OTA update that is bound to show up on the device shortly work?
BTW This is the WiFi only Nexus 7, 16 GB and my main PC at home is a Mac.
Thanks.
Foxman2k said:
Hi All,
I'm relatively new to Android (had the Nexus 7 for about a year). My questions is this:
I have 4.2.2 currently loaded. When I orinally got the nexus 7, I used a toolkit to unlock the bootloader and root the device, so I could install SixAxis and a few other apps that required root.
What is the easiest way for me to now update to 4.3? Will the OTA update that is bound to show up on the device shortly work?
BTW This is the WiFi only Nexus 7, 16 GB and my main PC at home is a Mac.
Thanks.
Click to expand...
Click to collapse
Get it locked and unrooted to get OTA possiblt easiest way.
Otherwise flash the factory images:thumbup:
Sent using Nexus 7
basuraunak said:
Get it locked and unrooted to get OTA possiblt easiest way.
Otherwise flash the factory images:thumbup:
Sent using Nexus 7
Click to expand...
Click to collapse
Do you have a link of a guide that I could follow on how to flash the factory image?
Can I download the zip and then use the clockwork recovery i have installed to load the zip?
I don't think that having the bootloader locked or unlocked will really affect the OTA..
Am I right or am I right?
Foxman2k said:
Do you have a link of a guide that I could follow on how to flash the factory image?
Can I download the zip and then use the clockwork recovery i have installed to load the zip?
Click to expand...
Click to collapse
Just use wug's toolkit. Its over in the android development in the n7 section...
---------- Post added at 10:04 AM ---------- Previous post was at 10:00 AM ----------
drake90001 said:
I don't think that having the bootloader locked or unlocked will really affect the OTA..
Am I right or am I right?
Click to expand...
Click to collapse
I dont think having it unlocked will effect the ota (it hasnt in the past for me), but it sounded like he wanted to flash the factory image. I actually have a nandroid of it on my unlocked n7. Gonna flash the official and see if I can get the ota later...
I've taken OTAs no problem on an unlocked, rooted device with TWRP recovery. So you're fine.
Sent from my Nexus 7 using Tapatalk 4 Beta
Here you go for flashable zip :
http://forum.xda-developers.com/showthread.php?t=2376522
Sent from my Nexus 7 using xda premium
So I downloaded what I believe to be the right file, ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi-JWR66V-from-JDQ39.ab67ca07 (1).zip.
I then reboot my nexus 7 into clockworkmod revovery and select install zip, choose zip from sdcard, browse to the aboev file but then get an error:
It ends in (Status 7) Installation aborted.
What am I missing?
Also, just tried via adb sideload and that didn't work either.
Foxman2k said:
So I downloaded what I believe to be the right file, ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi-JWR66V-from-JDQ39.ab67ca07 (1).zip.
I then reboot my nexus 7 into clockworkmod revovery and select install zip, choose zip from sdcard, browse to the aboev file but then get an error:
It ends in (Status 7) Installation aborted.
What am I missing?
Click to expand...
Click to collapse
Did you install the aosp browser and rename the default browser apk and odex files or modify the buildprop file? Those must be as original to take the update. Also, you should have gotten a message about what failed when you get the Status 7 error. What else did it say?
Groid said:
Did you install the aosp browser and rename the default browser apk and odex files or modify the buildprop file? Those must be as original to take the update. Also, you should have gotten a message about what failed when you get the Status 7 error. What else did it say?
Click to expand...
Click to collapse
No to all of the above. I don't know what odex files or buildprop file would refer to, so I defintely haven't modified them.
It says:
Warning: No file_contextsVerifying current system...
assert failed: apply_patch_check("/system/bin/debuggerd", "a whole bunch of letters and numbers", "a whole bunch of letters and numbers")
E:Error in /sdcard/0/update rom/ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi - JWR66V - from - JDFQ39.ab67ca07 (1).zip
(Status 7)
Installation aborted.
Groid said:
Did you install the aosp browser and rename the default browser apk and odex files or modify the buildprop file? Those must be as original to take the update. Also, you should have gotten a message about what failed when you get the Status 7 error. What else did it say?
Click to expand...
Click to collapse
Foxman2k said:
No to all of the above. I don't know what odex files or buildprop file would refer to, so I defintely haven't modified them.
It says:
Warning: No file_contextsVerifying current system...
assert failed: apply_patch_check("/system/bin/debuggerd", "a whole bunch of letters and numbers", "a whole bunch of letters and numbers")
E:Error in /sdcard/0/update rom/ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi - JWR66V - from - JDFQ39.ab67ca07 (1).zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Does it make a difference that my current build number in "about tablet" shows as JDQ39 and not JDFQ39 as above?
The problem file is 'debuggerd' in the /system/bin folder as it says in the error message. I had the same issue previously on the last N7 update. I had to get the original file from someone since the file had been replaced by another app (possibly Stickmount) or it can be extracted from the previous update to 4.2.2. I don't know about the JDFQ39 compared to the download file showing JDQ39, but that is the same file I downloaded. The (1).zip means you had previously downloaded the file and this is an additional d/l. That shouldn't be a problem, but you can delete the (1) if you want.
I'll try flashing through CWM and let you know if mine worked. If so, I can send you the right 'debuggerd' file.
Groid said:
The problem file is 'debuggerd' in the /system/bin folder as it says in the error message. I had the same issue previously on the last N7 update. I had to get the original file from someone since the file had been replaced by another app (possibly Stickmount) or it can be extracted from the previous update to 4.2.2. I don't know about the JDFQ39 compared to the download file showing JDQ39, but that is the same file I downloaded. The (1).zip means you had previously downloaded the file and this is an additional d/l. That shouldn't be a problem, but you can delete the (1) if you want.
I'll try flashing through CWM and let you know if mine worked. If so, I can send you the right 'debuggerd' file.
Click to expand...
Click to collapse
Ok great. I do have stickmount installed...
Well, I got the debuggerd error also. I'll try the backup debuggered file I used in the last update. Otherwise, I'll have to find the debuggerd file from 4.2.2. Any help out there?
Groid said:
Well, I got the debuggerd error also. I'll try the backup debuggered file I used in the last update. Otherwise, I'll have to find the debuggerd file from 4.2.2. Any help out there?
Click to expand...
Click to collapse
Glad I'm not alone lol
Still no joy. I think someone will have to get the right debuggerd file and get it to one us on a pm or email. Also, I noticed on my update try that the file was listed as JDQ39. ... and not the JDFQ39. ... that you saw.
Groid said:
Still no joy. I think someone will have to get the right debuggerd file and get it to one us on a pm or email. Also, I noticed on my update try that the file was listed as JDQ39. ... and not the JDFQ39. ... that you saw.
Click to expand...
Click to collapse
once we get the file, how do I replace the file with the debuggerd that is currently on the nexus?
What I will do is to copy the debuggerd file to the N7 internal storage root folder from my pc. Then I will rename /system/bin/debuggerd to debuggerd.bak (or whatever extension you want to add). Then I will copy the correct debuggerd file from sdcard to /system/bin and try the update again. I started a new thread asking for someone with an unaltered 4.2.2 debuggerd file to send it to me. If I get it I'll pass it along to you.
Groid said:
What I will do is to copy the debuggerd file to the N7 internal storage root folder from my pc. Then I will rename /system/bin/debuggerd to debuggerd.bak (or whatever extension you want to add). Then I will copy the correct debuggerd file from sdcard to /system/bin and try the update again. I started a new thread asking for someone with an unaltered 4.2.2 debuggerd file to send it to me. If I get it I'll pass it along to you.
Click to expand...
Click to collapse
Are you using a tool like ES File Manager to do the moving and renaming of files etc?