Hello!
Could some good soul create an update.zip file for me with the following content?
I don't have the time and resources for that so any help would be great!
Thanks!
This should work.
Swiftwork said:
This should work.
Click to expand...
Click to collapse
Thanks but there is an error: E:Can't find update script | Installation aborted
Swiftwork aint you the good samaritan?... a credit to the community.
Arkymedes,... Please post in GENERAL or Q&A next time.
Oops, my bad. You can move the thread if you wish.
I just got too used to see this part of the forums only
about the script, I noticed that the update-script has an TXT extension in the zip file. Is that correct?
Was just about to reply. I believe that is wrong. I will check.
Re-uploaded check again
Thanks again! but...
"E:Syntax error in update script"
Here u go have fun
Can I have the update-script please? I'm on a diving vessel with an ultra snail speed of Internet. I need to know what's in the update-script only
xtcislove said:
Here u go have fun
Click to expand...
Click to collapse
Thanks a lot
Geochelone said:
Can I have the update-script please? I'm on a diving vessel with an ultra snail speed of Internet. I need to know what's in the update-script only
Click to expand...
Click to collapse
Have fun:
Code:
show_progress 0.1 0
copy_dir PACKAGE:data DATA:
show_progress 0.1 10
Nice.
Thanks mate.
Related
I installed the MoDaCo Custom Rom r3.1 and it's perfect except for 1 tiny little thing: the default HTC contacts app has been renamed from 'People' to 'HTC People' (actually, from 'Contacten' to 'HTC Contacten' in my localized version of MCR).
I decided to unpack the HtcContacts.apk using apktool and replace all occurrences of 'HTC People' with just 'People'. Then, I repacked everything into an .apk and signed it with a key. Then, I pushed the new HtcContacts.apk to /system/app/ while in recovery mode. However, the new contacts app does not show up after booting ... might this be caused by using a random key for signing? If so, how should I sign this apk to make it work?
The whole thing should have been signed with test keys when it was de-odexed. The only other thing is that it could have been re-packed wrong, or you need to update the packages.xml.
I'm quite new to this odex stuff, so I don't know much about it. I'm usually 'just' a developer.
What's the deal with this 'test keys' stuff? Do you mean that I should find a specific key to sign the apk with?
No, I mean don't sign it again after you edit it.
-------------------------------------
Alias::NeO on HTC Desire
Well, that's what I tried first. To be more concise:
1. I flashed MCR r3.1 to my device and kept it in recovery
2. I took the HtcContacts.apk from the update zip that I used in step 1
3. I used apktool to unpack it, since all resources were in binary format in the apk itself
4. I edited the appropriate resources
5. I repacked everything into a fresh HtcContacts.zip
6. I pushed the new HtcContacts.zip to /system/app/
7. After the very first boot of MCR r3.1, the Contacts app was invisible in the app drawer
Since that obviously didn't work, I decided to sign the apk before pushing it to /system/app/ but that yielded the exact same result.
Do I need to sign the APK with the same key that is used for the other apks in /system/app?
alias_neo said:
No, I mean don't sign it again after you edit it.
Click to expand...
Click to collapse
You must resign files after any change made to them. If we wouldn't have to do it, then whole signing idea would have no sense.
franklinvv said:
What's the deal with this 'test keys' stuff? Do you mean that I should find a specific key to sign the apk with?
Click to expand...
Click to collapse
franklinvv said:
Do I need to sign the APK with the same key that is used for the other apks in /system/app?
Click to expand...
Click to collapse
Yes, and they were probably signed using testsigner tool. Did you used testsigner last time? If not, then try it.
Also looking into logcat would be helpful - to be sure, that problem is related to signing.
I'm not sure where to find the testsigner that you mention ... but I used some testsign.jar that I found somewhere. Using that jar, I get this:
I/PackageManager( 151): /system/app/HtcContacts.apk changed; collecting certs
E/PackageManager( 151): Package com.android.htccontacts has no signatures that match those in shared user android.uid.shared; ignoring!
Click to expand...
Click to collapse
Also, I read (almost) everywhere that that testsign stuff is used for signing update zips. Can I still use it for signing APKs?
franklinvv said:
Also, I read (almost) everywhere that that testsign stuff is used for signing update zips. Can I still use it for signing APKs?
Click to expand...
Click to collapse
I don't know. But some time ago I wanted to replace my framework-res.apk file and I had to create update.zip file and sign it using testsign tool. So I think you are right.
Brut.all said:
I don't know. But some time ago I wanted to replace my framework-res.apk file and I had to create update.zip file and sign it using testsign tool. So I think you are right.
Click to expand...
Click to collapse
Right about what? That I should put it in an update.zip? And if so, do I still need to sign the APK that I will put in the update.zip or is that unnecessary?
Are you flashing or pushing the file?
franklinvv said:
Right about what? That I should put it in an update.zip? And if so, do I still need to sign the APK that I will put in the update.zip or is that unnecessary?
Click to expand...
Click to collapse
I think you have to create update.zip with unsigned file, then sign update.zip file using testsign and install it from recovery.
eViL D: said:
Are you flashing or pushing the file?
Click to expand...
Click to collapse
I'm pushing it ... I will try flashing it now. (Never knew that there really was a difference between those 2 methods.)
Brut.all said:
I think you have to create update.zip with unsigned file, then sign update.zip file using testsign and install it from recovery.
Click to expand...
Click to collapse
I'm trying that right now.
Argh ... whatever I do, my update-script keeps yielding syntax errors!
This is all that I have in the update-script:
show_progress 0.1 0
copy_dir PACKAGE:system SYSTEM:
set_perm_recursive 0 0 0755 0644 SYSTEM:app
show_progress 0.1 10
Click to expand...
Click to collapse
I put the HtcContacts.apk in a /system/app subdir.
When I try to flash the zip, it fails with 'E:Syntax error in update script', and /tmp/recovery.log tells me:
Install from sdcard...
Finding update package...
I:Update location: SDCARD:update-signed.zip
Opening update package...
I:Update file path: /sdcard/update-signed.zip
Verifying update package...
I:Verified META-INF/CERT.RSA
I:Verified META-INF/MANIFEST.MF
I:Verified META-INF/com/google/android/update-script
I:Verified system/app/HtcContacts.apk
Installing update...
line 1: syntax error at '0.1'
E:Syntax error in update script
Installation aborted.
I:Set boot command ""
Click to expand...
Click to collapse
I have NO idea what I'm doing wrong.
Try: "show_progress 0.100000 0". But I don't know much about update.zip creating.
If I try that, it tells me:
line 1: syntax error at 'show_progress'
Click to expand...
Click to collapse
Edit: I'm all out of ideas ... I think I'll have to give up.
Edit2: After playing around with the update-script and trying stuff with the show_progress lines, I finally removed the lines and that worked after the 2nd try.
Unfortunately, my own HtcContacts.apk STILL doesn't work ...
I/PackageManager( 328): /system/app/HtcContacts.apk changed; collecting certs
E/PackageParser( 328): Package com.android.htccontacts has no certificates at entry AndroidManifest.xml; ignoring!
I/PackageManager( 328): Failed verifying certificates for package:com.android.htccontacts
Click to expand...
Click to collapse
So the APK does need to be signed before putting it in the update.zip?
you don't need:
set_perm_recursive 0 0 0755 0644 SYSTEM:app
Thanks, I changed the update-script accordingly.
However, I ended up with this:
I/PackageManager( 190): /system/app/HtcContacts.apk changed; collecting certs
E/PackageManager( 190): Package com.android.htccontacts signatures do not match the previously installed version; ignoring!
Click to expand...
Click to collapse
And after the second boot, I get this:
I/PackageManager( 151): /system/app/HtcContacts.apk changed; collecting certs
E/PackageManager( 151): Package com.android.htccontacts has no signatures that match those in shared user android.uid.shared; ignoring!
Click to expand...
Click to collapse
So, I'm stuck now ... I have the feeling that Paul signed everything in the MoDaCo ROM with an unknown key?
Hi all,
I'm trying to make an update.zip for users to install my app easily in recovery mode. It sounds trivial, and should basically just copy the apk into /data/app/.
Before I sign it, the zip contains (as shown by "unzip -t"):
Code:
data/app/com.keramidas.TitaniumBackup.apk
META-INF/com/google/android/update-script/update-script
The update-script is as follows:
Code:
show_progress 0.1 0
copy_dir PACKAGE:data DATA:
show_progress 0.1 10
Then I signed the update.zip with:
jarsigner -verbose -keystore my_keystore update.zip my_key
When I launch:
jarsigner -verify update.zip
I get "jar verified".
But in Clockwork recovery, my update.zip does not work - and signature verification is disabled, afaik.
EDIT: I have uploaded the update.zip there:
http://matrixrewriter.com/android/files/update.zip
Any ideas ?
Thanx in advance for any help
joel.bourquard said:
Hi all,
I'm trying to make an update.zip for users to install my app easily in recovery mode. It sounds trivial, and should basically just copy the apk into /data/app/.
Before I sign it, the zip contains (as shown by "unzip -t"):
Code:
data/app/com.keramidas.TitaniumBackup.apk
META-INF/com/google/android/update-script/update-script
The update-script is as follows:
Code:
show_progress 0.1 0
copy_dir PACKAGE:data DATA:
show_progress 0.1 10
Then I signed the update.zip with:
jarsigner -verbose -keystore my_keystore update.zip my_key
When I launch:
jarsigner -verify update.zip
I get "jar verified".
But in Clockwork recovery, my update.zip does not work - and signature verification is disabled, afaik.
EDIT: I have uploaded the update.zip there:
http://matrixrewriter.com/android/files/update.zip
Any ideas ?
Thanx in advance for any help
Click to expand...
Click to collapse
Hey Joel
Just curious has this been sorted yet? I would love a .zip so I can flash it after a new ROM when I don't have data.
FHL09 said:
Hey Joel
Just curious has this been sorted yet? I would love a .zip so I can flash it after a new ROM when I don't have data.
Click to expand...
Click to collapse
Hi dear Androlute overlord
Unfortunately no, I haven't got any hint on how to fix the zip file. Looking forward to having a working file!
I tweeted about it today, so I'm hoping someone will help...
Thanks
It's okay, the zip file works now. The update-script was misplaced
Hi Joel,
DO we have to sign the zip file created or would it be possible for your app to sign the file?
Thanks NSCXP2005
nscxp2005 said:
Hi Joel,
DO we have to sign the zip file created or would it be possible for your app to sign the file?
Thanks NSCXP2005
Click to expand...
Click to collapse
Hi,
The generated zip files are not signed - sorry.
I would love to incorporate the necessary signing code into my app, but unfortunately the signapk tool seems to require several Sun-only crypto classes, which don't exist on Android. If you know of a java implementation that can sign a zip file without using these Sun-only imports, please let me know and (as long as it's in the public domain) I'd be glad to include it in my app.
Thanks!
ok, Thanks.
Could you tell me how to sign the Update.zip that has been created by your app?
nscxp2005 said:
ok, Thanks.
Could you tell me how to sign the Update.zip that has been created by your app?
Click to expand...
Click to collapse
I have never really done it (or succeeded to do it), to be honest.
You need to use the "signapk" tool. I tried with Sun's standard "jarsigner" tool that comes with the JDK, but it wasn't considered as properly signed by the recovery image I have (Clockwork).
If you have more success than me, please let me know...
ok, thanks Joe, I hope you manage to find a way to sign the update.zip in the future.
Keep up the great work!!
EDIT Joel, I finally managed to flash your app in Recovery!!
Go here and look at the Update Maker made by DMzda
Update Maker
I hope you manage to implement this in to your update generator
I hope this helps
All the best
NSCXP2005
im tring to write my own update script. I have read the few pages that i was able to find on the www but none have answered my questions that i have or maybe not understanding what im reading. so here is what i have:
show_progress 0.1 0
delete_recursive SYSTEM:framework/
delete_recursive SYSTEM:app/
copy_dir PACKAGE:system SYSTEM:
delete_recursive DATA:dalvik-cache/
show_progress 0.1 10
or http://www.4shared.com/file/5Yms6qAg/update-script.html
this was writen w/notepadd++ file saved as all types *.*
when i flash my update zip i get:
Finding update package...
Opening update package....
Installing update...
E:Syntax error in update script
Installation aborted.
if someone can shed a little light if would be a great help.
hope posted in right section. thank you for the help anyone can provide.
EDIT: I used the samsung kitchen to convert the script to an updater-script. That seemed to fix whatever issue there was
Neverfmind. Got it figured out. Thanks for the help that I would have gotten.
U should post what ur findings were, in case someone in the future has the same issue.
Sent from my SPH-D700 using Tapatalk
Read edit in first post for how I fixed the issue.
Thanks decalex your right if I would have found this post I would be wondedring how it was fixed too. Thanks
Sent from my SPH-D700 using XDA Premium App
Sup I know there is a hack for ext4 on the nexus s but haven't seen anything for the NS4G. Is it the same hack or what? If so it seems a little complicated to get going with the tutorial given. Does anybody have a better tutorial or if there is a different hack for the 4g can you direct me to it please? Much appreciated.
Sent from my Nexus S 4G using xda premium
Joshhayes801 said:
Sup I know there is a hack for ext4 on the nexus s but haven't seen anything for the NS4G. Is it the same hack or what? If so it seems a little complicated to get going with the tutorial given. Does anybody have a better tutorial or if there is a different hack for the 4g can you direct me to it please? Much appreciated.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
not sure what "ext4 hack" youre talking about, but there is an ext4 mount script. itll give you a little speed/performance kick overall. but its not really a hack, its a fix. type this in a terminal emulator app..
su(press enter)
mount -o remount,noauto_da_alloc /data /data(press enter)
youll have to type it in after each reboot. or you can use an app to run it after each boot. most custom kernels already include it or some version of it, stock doesnt include it.
Use dsixda's rom kitchen to unpack boot.img: http://forum.xda-developers.com/showthread.php?t=633246
Then do this: http://forum.xda-developers.com/private.php?do=showpm&pmid=4452832 and repack.
snandlal said:
Use dsixda's rom kitchen to unpack boot.img: http://forum.xda-developers.com/showthread.php?t=633246
Then do this: http://forum.xda-developers.com/private.php?do=showpm&pmid=4452832 and repack.
Click to expand...
Click to collapse
That second link seems to not work, it says this "Invalid Private Message specified. If you followed a valid link, please notify the administrator"
Joshhayes801 said:
That second link seems to not work, it says this "Invalid Private Message specified. If you followed a valid link, please notify the administrator"
Click to expand...
Click to collapse
fter unpacking the boot.img go to BOOT_EXTRACTED/ramdisk and open the file init.herring.rc and add the following in green to the following to lines and save:
Code:
mount ext4 /dev/block/platform/s3c-sdhci.0/by-name/system /system wait ro noauto_da_alloc
mount ext4 /dev/block/platform/s3c-sdhci.0/by-name/userdata /data wait noatime nosuid nodev noauto_da_alloc
Sorry bout that
Sweet. Thanks. I'll be doing this later after I run errands.
Sent from my Nexus S 4G using xda premium
snandlal said:
fter unpacking the boot.img go to BOOT_EXTRACTED/ramdisk and open the file init.herring.rc and add the following in green to the following to lines and save:
Code:
mount ext4 /dev/block/platform/s3c-sdhci.0/by-name/system /system wait ro noauto_da_alloc
mount ext4 /dev/block/platform/s3c-sdhci.0/by-name/userdata /data wait noatime nosuid nodev noauto_da_alloc
Click to expand...
Click to collapse
I think I've done everything right and getting ready to flash soon. How will I know if it worked?
So I did everything you said, repacked (no errors, everything worked fine) now when trying to flash it gives me this "error in/tmp/sideload/package.zip (status 6)" Do you have any clue why this would happen?
EDIT: NVM I fixed it.
I don't understand why people want to make it harder on themselves. just run the script, it does the same thing.
simms22 said:
I don't understand why people want to make it harder on themselves. just run the script, it does the same thing.
Click to expand...
Click to collapse
It's not really hard...it's actually kind of easy with that particular kitchen. Plus I am willing to do it all because I like learning.
Joshhayes801 said:
It's not really hard...it's actually kind of easy with that particular kitchen. Plus I am willing to do it all because I like learning.
Click to expand...
Click to collapse
good answer
Hmm
Tried to flash the repacked rom and got stuck in a bootloop. Really can't find anything on why this happened or how to fix. Restoring nandroid as we speak.
simms22 said:
good answer
Click to expand...
Click to collapse
Lol. yeah well we all gotta start somewhere. I practically live on xda as it is, so I may as well learn as much as I can and hopefully become a contributor in some way. It started as just wanting to dink sound with my own device but now that I know that I CAN do it. I want to go further with it.
Sent from my Nexus S 4G using xda premium
ROM Porter
About the tool:
This tool is based on rishab.raj37's great guide. And makes porting ROMs in few simple clicks. This is made only for linux.
Click to expand...
Click to collapse
How to use it:
1. Download the port.sh from here.
2. Place the ROM zips and script in the home directory (~/) (home/username).
3. Now open the terminal and type the following:
Code:
./port.sh
In some cases this might not work so try this:
Code:
bash ~/port.sh
4. Now follow the on-screen instructions and done. :good:
5. You can find your ported ROM in ~/PORT/ directory.
6. Enjoy and press THANKS.
Click to expand...
Click to collapse
Note:
If you get stuck on bootloop, try this tool, here.
Click to expand...
Click to collapse
Credits:
rishab.raj37- For such a great guide
ME
Click to expand...
Click to collapse
Reserved for FAQs
THANKS for the Awesome Tool
Witch program to use for build.prop file to be open?
djkidy123 said:
Witch program to use for build.prop file to be open?
Click to expand...
Click to collapse
Notepad++?
Regards
N
In ubuntu??
OK they are open in GEDIT, but i'm getting only blank pages with red line can't open...
Seeing the code, yes it does open in gedit. Sorry.
Regards
N
djkidy123 said:
In ubuntu??
OK they are open in GEDIT, but i'm getting only blank pages with red line can't open...
Click to expand...
Click to collapse
Use SciTE .
www.scintilla.org/SciTE.html
karandpr said:
Use SciTE .
www.scintilla.org/SciTE.html
Click to expand...
Click to collapse
Thanx, but how to setup script to auto open in this reader?!
djkidy123 said:
Thanx, but how to setup script to auto open in this reader?!
Click to expand...
Click to collapse
Open port.sh find and replace gedit with path-to-scite( if its default path, just scite)
Regards
N
So this does not work with gedit at all?
The script keeps trying to extract the rom files into the same exact folder, causing conflicts. Also, when it tries to open the build.prop files it thinks they are in folders named after the ROM zips that are never created. Has anyone gotten this to work yet?
Download link inactive
Abhinav1997 said:
ROM Porter
About the tool:
How to use it:
Note:
Credits:
Click to expand...
Click to collapse
Thank you very much for this helpful tool. But th download link does'nt work for me. Could you help me please by giving another link or sending the file in mp.
Thanks again for your help
Is impossible to download from dev host!!!!