I've looked through the update.zip and it seems only a few changes are needed to -keep- root.
* Flash the recovery image from http://forum.xda-developers.com/showthread.php?t=443041
* Unzip the FULL rc30
* Replace the system/recovery.img with the one from the above url.
* Copy system/bin/sh to system/bin/rootshell, and make the following changes to META-INF/com/google/android/update-script (or download a modified copy from a trusted source)
Add this to the end of the first line, which should start with: assert getprop("ro.build.finger.......
|| getprop("ro.build.fingerprint") == "generic/htc_dream/dream/trout:1.0/TC3/eng.jesusfreke.20081105.164210:eng/test-keys"
After
set_perm_recursive 0 2000 0755 0755 SYSTEM:bin
add
set_perm 0 2000 04755 SYSTEM:bin/rootshell
BACKUP anything from /system as it will be formatted. Do -not- use the 4 meg rc30 patch, as it bricks systems.
Resign with the utility provided in the above link, copy to sdcard, enter recovery, and pray. If it works, you can run the following from the terminal app (not pterminal)
/system/bin/rootshell
I've sucessfully done this on my machine.
That looks right, but just in case, I would also try to add a couple back doors, and close a few of Google's:
Add a test cert to the list of accepted OTA certs.
Remove Google's OTA cert.
Include a setuid shell somewhere in the patch.
has ne1 tryed this? does it work...
im not sure wat changes to make to the script...its kind of confusing..can sum1 post an changed script?
Koush said:
That looks right, but just in case, I would also try to add a couple back doors, and close a few of Google's:
Add a test cert to the list of accepted OTA certs.
Remove Google's OTA cert.
Include a setuid shell somewhere in the patch.
Click to expand...
Click to collapse
The setuid shell is added by means of chmodding /system/bin/sh. I'm not clear on the syntax for the 'concat' function that's apparently in the updater, so for safety's sake I won't try to make a copy. Regarding the other stuff....
Warning - Several people have bricked phones because a file that the updater intends to patch is either modified or missing. This includes otacerts.zip, so it would be a good idea to look through META-INF/com/google/android/update-script and make sure that none of the files listed have been tampered with.
Fnorder said:
The setuid shell is added by means of chmodding /system/bin/sh. I'm not clear on the syntax for the 'concat' function that's apparently in the updater, so for safety's sake I won't try to make a copy. Regarding the other stuff....
Warning - Several people have bricked phones because a file that the updater intends to patch is either modified or missing. This includes otacerts.zip, so it would be a good idea to look through META-INF/com/google/android/update-script and make sure that none of the files listed have been tampered with.
Click to expand...
Click to collapse
You are right, otacerts.zip is one of the files they are patching. So we'd need to remove that applypatch line and leave our own copy on the file system. Or just leave it as is...
Koush said:
You are right, otacerts.zip is one of the files they are patching. So we'd need to remove that applypatch line and leave our own copy on the file system. Or just leave it as is...
Click to expand...
Click to collapse
Or rename otacerts back to what it was, yeah.
So, if we want the modified rc30 update, we absolutely have to have the modded recovery and boot imgs at the link you provided? Can we not have the option to simply resign the modified update and install it?
stephen.n.nikki said:
So, if we want the modified rc30 update, we absolutely have to have the modded recovery and boot imgs at the link you provided? Can we not have the option to simply resign the modified update and install it?
Click to expand...
Click to collapse
Just the modified recovery.img, and yes it's required to install any modified update - since you don't have google's private key, you can't put google's signature on the update, and google's recovery only allows updates signed with that.
So has anyone had success with, or even tried, your fix?
stephen.n.nikki said:
So has anyone had success with, or even tried, your fix?
Click to expand...
Click to collapse
I'll know in a few minutes!
Related
I dont know how to create update script till now i used to edit some ones update script so i need a tutorial on making update script...
Update script? if you are asking for what I think you are you need to learn bash scripting. If not, you should clarify what you want when asking a question.
I think perhaps he means themes? If so, use the search key
Darkrift said:
Update script? if you are asking for what I think you are you need to learn bash scripting. If not, you should clarify what you want when asking a question.
Click to expand...
Click to collapse
If you're thinking what I'm thinking that you are thinking about what he is thinking..
the update-script file in an update.zip isn't a bash script . It sorta looks like one, but it actually contains commands that are interpreted by the recovery program.
sangeet.003 said:
I dont know how to create update script till now i used to edit some ones update script so i need a tutorial on making update script...
Click to expand...
Click to collapse
Assuming you mean update-script in an update.zip update, you will need to either look at existing update-script files for an example of the syntax, or look at the source of the recovery program in the android source
Thanks JesusFreke U got my point...
Bump
I too would like info on this. I'm wondering if its at all possible to alter the update script to install 3rd party apps into /data/app and /data/app-private. I've tried placing 3rd party apps into one of the Dude's roms(i think, can.'t remember exactly which rom it was), but I didn't install my 3rd party app. Yes, I did resign the update.
So if someone could help me with this, i would be really grateful. I'd like to make one script to load just /data and another to be included with my usual update.zip's.
I really enjoy the fact that my phone is so customizable, but those 3rd party apps make my custom themes sooooo ugly. i don't mind taking the time to pull apps and theme them, but reinstalling them is a pain. I know there is a windows utility for reinstalling apps, but I'd rather just flash /data.... is this even possible?
Anywho, if any of you "smart" guys around here could help me with this, I would be such a happy droid.
jonnybueno said:
I too would like info on this. I'm wondering if its at all possible to alter the update script to install 3rd party apps into /data/app and /data/app-private. I've tried placing 3rd party apps into one of the Dude's roms(i think, can.'t remember exactly which rom it was), but I didn't install my 3rd party app. Yes, I did resign the update.
So if someone could help me with this, i would be really grateful. I'd like to make one script to load just /data and another to be included with my usual update.zip's.
I really enjoy the fact that my phone is so customizable, but those 3rd party apps make my custom themes sooooo ugly. i don't mind taking the time to pull apps and theme them, but reinstalling them is a pain. I know there is a windows utility for reinstalling apps, but I'd rather just flash /data.... is this even possible?
Anywho, if any of you "smart" guys around here could help me with this, I would be such a happy droid.
Click to expand...
Click to collapse
update-script can put things into data, yes. Just create a data folder in your zip file and include the relevant lines in the script:
copy_dir PACKAGE:system SYSTEM:
copy_dir PACKAGE:data DATA:
Thank you! you sir, are a kind person. I will try this tonight and report my findings afterward!
bringing this thread back from the dead. I need help, if somebody could point to how to use set_permission and why all the symlinking toolbox and busybox (i understand busybox is not part of the regular android package) to other tools already in bin. Also, maybe pointers of what the tools in bin do and if i could remove them after including busybox since they're already in busybox anyway
how about removing a file?
would it be 'remove system:app:mms.apk'
would that work?
gwydionwaters said:
how about removing a file?
would it be 'remove system:app:mms.apk'
would that work?
Click to expand...
Click to collapse
Nope but I think
"delete SYSTEM:app/Mms.apk"
update-script
gwydionwaters said:
how about removing a file?
would it be 'remove system:app:mms.apk'
would that work?
Click to expand...
Click to collapse
what he said:
delete SYSTEM:app/Mms.apk
delete SYSTEM:app/Mms.odex
if you're really interested just grab any ROM available on xda and started learning the commands .. it's really rather simplistic
right on, thanks guys. i'll download some other roms as well and have a look through.
Maybe someone can halp me with correct command for sript. I need to copy one file (for example photo.ipg) into ext (root) partition whilst flshing update.zip. Files is in update.zip/photo.jpg. I have try put it into system/sd, but after flash files wont copy.
im trying remove certain apps from /data/app then install other apps on the /system/app
but im having trouble in removing apps from /data/app
mount("MTD", "data", "/data");
delete("/data/app/someapp.apk"); ?? not sure about deleting apps, i think this is wrong.
unmount("/data");
Is that the even the correct way to mount it? because that works with the /system
Any help would be greatly appreciated.
Ubuntu only
Wrong section btw, just have to say it. I am on Ubuntu 10.04 LTS and I just use terminal:
Code:
gedit update-script
Once you do that your newly created file will pop up, the put what ever you want in it and save it. The file will be in your home folder. this is what mine looks like:
Code:
show_progress 0.1 0
copy_dir PACKAGE:system SYSTEM:
show_progress 0.1 10
Then create these folders, each one inside of the other:
Code:
META-INF
root of update zip >
Code:
com
>
Code:
google
>
Code:
android
Then place your update-script in the android folder, and also create the system or data folder in root of update.zip
If it's not compressed into a zip file already than you will need to select all the folders, right click and select compress, then compress as zip. After compressing into zip you will need to sign it. I'm not going to get into signing and all that because there is tons of info on xda for signing roms
in other thread and if someone still looking:
update-script syntax - A guide for ROM devs, modders, and themers
Code:
http://forum.xda-developers.com/showthread.php?t=641223
Thanks to TylTru for the gift
hey!, I have a problem when I try to flash the update.zip (AOSP compiled for HTC Desire), I get the following error:
E: Can't chown/mod /system/keyspa.sh
(No such file or directory)
E:Failure at line 14:
set_perm 0 0 06755 SYSTEM:keyspa.sh
Installation aborted
anybody knows the reason?
Thanks in advance..
jm0077 said:
hey!, I have a problem when I try to flash the update.zip (AOSP compiled for HTC Desire), I get the following error:
E: Can't chown/mod /system/keyspa.sh
(No such file or directory)
E:Failure at line 14:
set_perm 0 0 06755 SYSTEM:keyspa.sh
Installation aborted
anybody knows the reason?
Thanks in advance..
Click to expand...
Click to collapse
does /system/keyspa.sh exist?
I'd been trying to figure out how to set up a few simple things in my rooted, post-MR, but otherwise stock CDMA Hero. Namely, ADB Remount permissions (/default.prop file), set up Superuser to properly manage permissions for apps that require root, and install Busybox. Ideally, I wanted to set these up manually. Turns out it's not as simple as one might hope. ADB Remount, for example, requires that you modify and repackage the boot.img/recovery.img.
So, what I've got here is a minimal update.zip file you can apply to your phone via the recovery console. Nothing crazy, it's just MoDaCo's ROM 1.1, but with everything taken out except for the aforementioned items. Once you patch your phone, just these items will be configured and your phone will still look, run, etc. the same as before. Also, a2sd will be copied to your /system/bin directory, but it's something that had to stay in the file for some reason, otherwise the phone wouldn't boot. Probably a setting Paul built into the boot.img.
In any case, here it is. It's working well for me. Hope it helps some of you out too.
****
Thanks goes to Paul of course (MoDaCo) camalot (Droid Explorer) and dagnasty for telling me about the auto-sign plugin that's available in Droid Explorer.
Instructions for manually installing Busybox over here:
http://forum.xda-developers.com/showthread.php?t=591303
****
I responded on ppcgeeks:
mercado79 said:
IAlso, a2sd will be copied to your /system/bin directory, but it's something that had to stay in the file for some reason, otherwise the phone wouldn't boot. Probably a setting Paul built into the boot.img.
Click to expand...
Click to collapse
Yup. It's a script that was added to the boot.img-ramdisk that copies all of your apps to your sd when apps2sd's requirements are met.
So if the sdcard is not partitioned correctly then ap2sd will not run, yes?
Smacky55 said:
So if the sdcard is not partitioned correctly then ap2sd will not run, yes?
Click to expand...
Click to collapse
"Correctly" is relative. If there is no EXT partition on the sdcard, then the ROM won't try to move your applications to it. But the script runs regardless.
Sorry, meant if sdcard isn't partitioned at all. Thanks for the answer.
flipzmode told me in another thread that even though this script is included, that doesn't mean that the update.zip i posted will enable apps2sd for anyone. there's more required in order to get it to work (i stripped most everything out).
A few simple questions. re -stock 1.56... rom
1) in the zip system folder, its refers to /xbin ; does that require that /system/xbin be pre-existent, or will it create it ?
2) busybox is in /system/bin on mine. Do I need to remove it?
a) if so then due to the "busybox --install -s /system/bin"
command , how do i remove the current symbolic busybox entry points?
b)have $PATH changes been applied to overwrite the current export
3) empty init.sh file?
4) google meta references?
I think I may understand the need to get bootstrap-"root" permissions established, is there another way as well?
Thanks for dealing with these noobie questions.
Thanks for this. worked out great.
willy900wonka said:
A few simple questions. re -stock 1.56... rom
1) in the zip system folder, its refers to /xbin ; does that require that /system/xbin be pre-existent, or will it create it ?
2) busybox is in /system/bin on mine. Do I need to remove it?
a) if so then due to the "busybox --install -s /system/bin"
command , how do i remove the current symbolic busybox entry points?
b)have $PATH changes been applied to overwrite the current export
3) empty init.sh file?
4) google meta references?
I think I may understand the need to get bootstrap-"root" permissions established, is there another way as well?
Thanks for dealing with these noobie questions.
Click to expand...
Click to collapse
sorry willy man. not sure what i can tell you. i'm pretty close to being a newbie myself. i never fully understood what the script was doing. i simply took the original modaco update and compared it to another script paul had posted on his forums last fall.
if you unzip the file, you should be able to see everything that's going on. the file structure is super simple, so modify it to suit your needs and give it a try. worst case, you'll need to revert to a nandroid backup. oh, and don't forget you'll need to sign the file and zip it back up in order to flash it onto the phone.
come to think of it, i guess maybe i should update the script using the latest modaco rom, though i'm not sure how helpful it'd be for everyone. to be honest, i've since bitten the bullet and moved on to flipz's rom and the gumbo kernel. runs beautifully!
Ok, so I formated the card, put the .zip file on the sdcard and tried to press home+power to enter the recovery council. When I hold home and press power I am taking to a screen that has an exclamation point and an image of the phone.
Can anyone help?
partylatino420 said:
Ok, so I formated the card, put the .zip file on the sdcard and tried to press home+power to enter the recovery council. When I hold home and press power I am taking to a screen that has an exclamation point and an image of the phone.
Can anyone help?
Click to expand...
Click to collapse
Boot the phone by holding home only. And...I'm assuming you have the recovery console installed and are rooted.
I think the problem is that a recovery boot image was not previously installed. A green screen with a set of options should've appeared.
http://forum.xda-developers.com/showthread.php?t=596879
I prefer 1.2.3
mercado79 said:
Boot the phone by holding home only. And...I'm assuming you have the recovery console installed and are rooted.
Click to expand...
Click to collapse
I did root the phone but I am not familiar with the recovery council. I tried to search for this but was unsuccessful.
I just got my Hero last week so I am still new to all of this. Can you point me in the right direction?
partylatino420 said:
I did root the phone but I am not familiar with the recovery council. I tried to search for this but was unsuccessful.
I just got my Hero last week so I am still new to all of this. Can you point me in the right direction?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=596879 explanation
code from : http://forum.xda-developers.com/showthread.php?t=583291
13:
Code:
adb push recovery-RA-heroc-v1.5.2.img /sdcard
Pushing is equivalent of copy the file to the root of your sdcard. By the time you finished reading this it should be done. You'll know its done because the ouput will say something like transferred X bytes in X secs.
14:
Code:
adb shell reboot
This will cause the phone to restart automatically. Wait till it is fully booted to continue.
http://tinyurl.com/yc96j2z
partylatino420 said:
I did root the phone but I am not familiar with the recovery council. I tried to search for this but was unsuccessful.
I just got my Hero last week so I am still new to all of this. Can you point me in the right direction?
Click to expand...
Click to collapse
Your google search didn't turn anything up on "recovery council" because the operative use would have actually been "recovery console"..
that did it!! Thanks guys!!!
um, what???
mercado79 said:
So, what I've got here is a minimal update.zip file you can apply to your phone via the recovery console.
Click to expand...
Click to collapse
Apply via the recovery console? Sorry, still very new to this. Thanks!
Recovery Console
Go to the recovery console by holding down home when you power your Android. In that menu, you should see something that says 'flash update from SD card'... or something like that... then you choose the .zip that he has so kindly provided us.
Oh, and you have to put the .zip file that he provided on the SD card if that isn't already obvious :/
I also renamed it update.zip once I copied it to my SD card. Hope this clears it up a little. I just rooted my Hero yesterday.. so I am on the same NOOB level.
Do I need to wipe before flashing this / will this wipe my phone if I flash it?
fallonjp said:
Do I need to wipe before flashing this / will this wipe my phone if I flash it?
Click to expand...
Click to collapse
You shouldn't need to wipe your phone; however I really don't think it's a good idea to use this. I put this together last year when we were still running Android 1.5 so it's WAY out of date. Just go with Nfinite's ROMs. He keeps them almost completely stock (depending on which you choose) and they can serve as great back-up / go-to ROMs.
I'm sorry to say I have no idea but I'm now determined to learn how and I think I'll start with a linux partition.
Anyone care to join me?
I think the Avabox that avaluanchemods posted up included the files to pull out the files from the .img, after that wouldn't it be just like modifying another ROM (with a lot more to mod, of course, to gain root, etc.)?
danaff37 said:
I think the Avabox that avaluanchemods posted up included the files to pull out the files from the .img, after that wouldn't it be just like modifying another ROM (with a lot more to mod, of course, to gain root, etc.)?
Click to expand...
Click to collapse
nope, this ruu is different
doesn't work like that.
well, once you have the images you can use yaffs, for the system image, but getting the images from the ruu...
regaw_leinad said:
nope, this ruu is different
doesn't work like that.
well, once you have the images you can use yaffs, for the system image, but getting the images from the ruu...
Click to expand...
Click to collapse
Hahaha yeah, getting the images from the ruu is a blast!
u guys want the new sprint ruu turned into a flashable update.zip? isn't that what damages 2.06 basically is? if not i'll do it for you.
I think it's really more that they wanna learn how. Anyone down to throw out some pointers?? I'd be interested to learn too
I was actually just looking into pulling the files from the ruu myself.
extract the exe file. unyaffs the system.img. make an update-script in META-INF/com/google/android/. zip the boot.img META-INF/ folder, and system/ folder and sign it. nothing more to it. lol
zenulator said:
u guys want the new sprint ruu turned into a flashable update.zip? isn't that what damages 2.06 basically is? if not i'll do it for you.
Click to expand...
Click to collapse
well, well howdy stranger! zen you were a great dev on the vogue/android...we need you here my man!
fixxxer2008 said:
well, well howdy stranger! zen you were a great dev on the vogue/android...we need you here my man!
Click to expand...
Click to collapse
this communtiy is a little crazy for my taste. but darchstar answered the question.
http://code.google.com/p/zen-droid/downloads/list
this is a link to the files i use. you must have linux installed to use them as well as pearl which should be installed on most distros. you'll prob have to chmod them executable if you download them.
any questions post them and i'll try to help. i'm glad to see people trying to learn.
regaw_leinad said:
nope, this ruu is different
doesn't work like that.
well, once you have the images you can use yaffs, for the system image, but getting the images from the ruu...
Click to expand...
Click to collapse
thats all you need for a rom. is the /system. just place that in a folder along with the boot.img. andddd archive and sign. you have a rom now.
and if you want to know a secret. lol
if you are in windows, all .exe's are archived as zips. change .exe to .rar/zip and then you can unzip and have everything. very simple.
o and you need an update script which you can create, or take someones from a rom and edit it to fit the RUU. and as always give credit where needed
Avalaunchmods said:
thats all you need for a rom. is the /system. just place that in a folder along with the boot.img. andddd archive and sign. you have a rom now.
and if you want to know a secret. lol
if you are in windows, all .exe's are archived as zips. change .exe to .rar/zip and then you can unzip and have everything. very simple.
o and you need an update script which you can create, or take someones from a rom and edit it to fit the RUU. and as always give credit where needed
Click to expand...
Click to collapse
interesting. so in theory this could be done as easily on windows, no linux partitions?
mountaindont said:
interesting. so in theory this could be done as easily on windows, no linux partitions?
Click to expand...
Click to collapse
i hate linux. lol so yes
Not all exe's work like that. Like this one for example....
not even 7zip can get into it.
danaff37 said:
Not all exe's work like that. Like this one for example....
not even 7zip can get into it.
Click to expand...
Click to collapse
uniextract, google it. you are correct some are a certain type that cant be extracted but 99% of RUU's can.
Ok here is a basic run through for extracting the RUU and making an update.zip
1. Run the RUU in windows or through wine. You don't have to run it completely with your phone plugged in. The install shield will extract the files to a tmp folder. Search through your tmp folders until you find it. Inside should be a rom.zip. Unzip it. Inside it should be system.img data.img boot.img etc...
2.
a: Switch to linux. Use unyaffs to extract the system.img. I usually make a directory called system in the same directory as the system image and cd to it. then issue.
unyaffs ../system.img
this will extract it into the system directory that your in. make your changes. add apps/busybox/su etc..
b: You can also use unyaffs for windows from here: http://code.google.com/p/unyaffs/downloads/list it should do the same thing but I've never used it.
3. If you want apps pre-installed to /data then make a data directory with a apps directory in it and put your extra apps there like wireless tether etc... so now you have a directory with
/system
/data
boot.img
4. Use an update script from another rom as a base and modify it to symlink busybox, set the correct permissions, copy data write boot.img, clear cache etc... read through some other update scripts to get the idea of whats going on it's simple text based stuff. The update script is inside the directory
META-INF/com/google/android.
Once done move the META-INF directory to your working directory. so you should now have
/system
/data
/META-INF
boot.img
Zip up the above directorys/files into something like myrom.zip
5. Sign the zip. You'll need java and a testsign.jar and the android sdk. I've never done it without the sdk. Create a directory called sign inside the tools directory of the android sdk. Move testsign.jar and your myrom.zip to the sign directory. Execute the following command while in the sign directory
java -classpath testsign.jar testsign myrom.zip myrom-signed.zip
6. Copy myrom-signed.zip to the root of your sdcard. reboot recovery. nandroid backup. wipe/factory reset. flash update zip.
Good luck.
zenulator said:
Ok here goes a basic run through for extracting the ruu and making an update.zip
1. Run the ruu in windows or through wine. It will be extracted to a tmp folder. Search through the tmp folders until you find it. Inside should be a rom.zip. Unzip it. Inside it should be system.img data.img boot.img etc...
2. Switch to linux. Use unyaffs to extract the system.img. I usually make a directory called system in the same directory as the system image and cd to it. then issue.
unyaffs ../system.img
this will extract it into the system directory that your in. make your changes. add apps/busybox/su etc..
3. if you want apps pre-installed to /data then make a data directory with a apps directory in it and put your extra apps there like wireless tether etc... so now you have a directory with
/system
/data
boot.img
4. use a update script from another rom as a base and modify it to symlink busybox, set the correct permissions, copy data write boot.img, clear cache etc... read through some other update scripts to get the idea of whats going on it's simple text based stuff. the update script is inside the directory META-INF/com/google/android. once done move it to your working directory. so you should now have
/system
/data
/META-INF
boot.img
Zip up the above directorys/files into something like myrom.zip
5 sign the zip. you need java and a testsign.jar and the android sdk. i've never done it without the sdk. create a directory called sign inside the tools directory of the android sdk. move testsign.jar and your myrom.zip to the sign directory. execute the following command while in the sign directory
java -classpath testsign.jar testsign myrom.zip myrom-signed.zip
6. copy myrom-signed.zip to the root of your sdcard. reboot recovery. nandroid backup. wipe/factory reset. flash update zip.
Good luck.
Click to expand...
Click to collapse
uhh...i think ill leave that one too the pros
zenulator said:
Ok here goes a basic run through for extracting the ruu and making an update.zip
Click to expand...
Click to collapse
Interesting. Sounds easy enough, I'll definitely have a go. Thanks for the tutorial.
pseudoremora said:
Interesting. Sounds easy enough, I'll definitely have a go. Thanks for the tutorial.
Click to expand...
Click to collapse
+5, HOLY CRAP guys, I havent checked the forum in a few hours.
Thank you all so much for the insight.
I'll be back in a week!!
nebenezer said:
+5, HOLY CRAP guys, I havent checked the forum in a few hours.
Thank you all so much for the insight.
I'll be back in a week!!
Click to expand...
Click to collapse
There's an easy fix for your problem... Install the XDA Android App. Seriously, my soul belongs to Android now... and XDA has become my home, I HAVE to know what's going on at all times... it's like a drug, lol.
I hate having to remove apps everytime I flash a new ROM. So here is what I've done and I'm sure others too.
1) Open notepad in Windows.
2) Add these lines in it:
adb remount
adb shell rm system/app/*Stock*
adb shell rm system/app/IM.apk
adb shell rm system/app/*Facebook*
adb shell rm system/app/Flickr.apk
adb shell rm system/app/Mail.apk
adb shell rm system/app/htcmailwidgets.apk
adb shell rm system/app/Sprint_Navigation.apk
adb shell rm system/app/Sprint_NFL.apk
adb shell rm system/app/Sprint_Nscar.apk
adb shell rm system/app/HTCNew.apk
3) Save it as RemoveAPK.bat on desktop.
4) Double click this file to run it. (This will only work if SDK tools directory is in system path)
If SDK tools is not in your system path, you can place this script in the SDK tools folder and double click in there.
so now anytime a new ROM comes out, connect your phone, and double click. They'll be removed in literally a blink of an eye.
I'd attach this to the thread, but *.bat files are not allowed as attachments.
another suggestion that's awesome too (thanks to daryelv):
daryelv said:
Why not just create your own update.zip to do all the actions after flashing the ROM zip? Here's an example of mine...
Code:
show_progress 0.1 0
delete_recursive DATA:dalvik-cache/
delete_recursive DATA:boot-cache/
delete SYSTEM:app/com.android.launcher2.apk
delete SYSTEM:app/LiveWallpapers.apk
delete SYSTEM:app/LiveWallpapersPicker.apk
delete SYSTEM:app/VisualizationWallpapers.apk
delete SYSTEM:app/HtcLockScreen.apk
delete SYSTEM:app/HtcLockScreen.odex
delete SYSTEM:app/DeskClock.apk
delete SYSTEM:app/DeskClock.odex
delete SYSTEM:app/com.htc.StockWidget.apk
delete SYSTEM:app/Stock.apk
delete SYSTEM:app/Sprint_Navigation.apk
delete SYSTEM:app/HtcFootprintsWidget.apk
delete SYSTEM:app/HtcFootprints.apk
delete SYSTEM:app/LatinIME.apk
delete SYSTEM:app/GSD.apk
delete SYSTEM:app/FieldTest.apk
delete SYSTEM:app/amazonmp3.apk
delete SYSTEM:customize/resource/BigBen.jpg
delete SYSTEM:customize/resource/Colosseum.jpg
delete SYSTEM:customize/resource/EiffelTower.jpg
delete SYSTEM:customize/resource/StatueOfLiberty.jpg
delete SYSTEM:customize/resource/htc_wallpaper_01_lockscreen.jpg
delete SYSTEM:customize/resource/htc_wallpaper_02_lockscreen.jpg
delete SYSTEM:customize/resource/htc_wallpaper_03_lockscreen.jpg
delete SYSTEM:customize/resource/htc_wallpaper_04_lockscreen.jpg
delete SYSTEM:customize/resource/htc_wallpaper_05_lockscreen.jpg
delete SYSTEM:customize/resource/htc_wallpaper_06_lockscreen.jpg
delete_recursive SYSTEM:media/audio/
delete_recursive SYSTEM:media/bootscreen/
delete SYSTEM:media/bootanimation.zip
copy_dir PACKAGE:system SYSTEM:
show_progress 0.2 10
Just find an existing update package (any of them) and modify the update script to your liking and also put files in /system/ that you want in your ROM. (You could also put files into /data/app/ to load your programs, but I use A2SD which needs to be mounted first).
This also inserts my favorite Boot animation and favorite HTC keyboard into the ROM. My media files I keep in the /sdcard/ directory, so I just delete them from the ROM as well.
The benefits of doing this is that I can leave this on the root of my sdcard and just flash this ZIP after flashing a ROM.
-Daryel
Click to expand...
Click to collapse
Good idea! I never thought of using a bat...I just had a text file I copy and past the commands I use alot...this will save me some time!
great idea. me personally I use the autosign.bat and just unzip the rom remove all the stuff I dont want, add all my tweeks and customizations in and then resign it before I flash it but that becuase I have stuff I add in so thats the easiest way for me to do it. plus then all my stuff is there right at boot.
wtphoto said:
great idea. me personally I use the autosign.bat and just unzip the rom remove all the stuff I dont want, add all my tweeks and customizations in and then resign it before I flash it but that becuase I have stuff I add in so thats the easiest way for me to do it. plus then all my stuff is there right at boot.
Click to expand...
Click to collapse
Yeah. but then you have to unzip. That's too many clicks for me lol. I like the signing part though. You know what you can do. You can probably modify a script to do all that for you.
for instance not worry about modifying a zip, but after it's installed, just run a script that would remove apks, add your themes and apks that you'd want. So you dont have to unzip and re-sign. Unless you end up re-releasing your ROMs to others.
Bat and Cmd files are AMAZING things. Everyone touts VBScript like its a god send, but good ole Bat never fails me.
wtphoto said:
great idea. me personally I use the autosign.bat and just unzip the rom remove all the stuff I dont want, add all my tweeks and customizations in and then resign it before I flash it but that becuase I have stuff I add in so thats the easiest way for me to do it. plus then all my stuff is there right at boot.
Click to expand...
Click to collapse
jackal424 said:
Yeah. but then you have to unzip. That's too many clicks for me lol. I like the signing part though. You know what you can do. You can probably modify a script to do all that for you.
for instance not worry about modifying a zip, but after it's installed, just run a script that would remove apks, add your themes and apks that you'd want. So you dont have to unzip and re-sign. Unless you end up re-releasing your ROMs to others.
Click to expand...
Click to collapse
you could write a batch with a menu system to give various options.
I used to write those all the time until I switched to VB and added graphics.
What does the "HTCNew.apk" contain?
jackal424 said:
Yeah. but then you have to unzip. That's too many clicks for me lol. I like the signing part though. You know what you can do. You can probably modify a script to do all that for you.
for instance not worry about modifying a zip, but after it's installed, just run a script that would remove apks, add your themes and apks that you'd want. So you dont have to unzip and re-sign. Unless you end up re-releasing your ROMs to others.
Click to expand...
Click to collapse
I dont plan on releasing any roms anytime soon since everything I do is theme stuff but by doing that way makes it a lot easier if I fubar something bad with a new mod becuase then I just reflash with the base that I know is good. that and I do it so much it only takes me a bout 1.5 minutes to unzip remove the stuff I dont and drag everything in then resign.
wtphoto said:
I dont plan on releasing any roms anytime soon since everything I do is theme stuff but by doing that way makes it a lot easier if I fubar something bad with a new mod becuase then I just reflash with the base that I know is good. that and I do it so much it only takes me a bout 1.5 minutes to unzip remove the stuff I dont and drag everything in then resign.
Click to expand...
Click to collapse
makes sense...
Hmm. I'm with wtphoto on this one, but I can certainly think of other applications for this. I've never messed with this kinda stuff before. Quick couple of questions:
1. If sdk is in my system path, does that mean I wouldn't need to move stuff to the tools folder to resign it, push it etc?
If so:
2. How do I do this black magic?
I know, I know my inner n00b is showing again
tejasrichard said:
Hmm. I'm with wtphoto on this one, but I can certainly think of other applications for this. I've never messed with this kinda stuff before. Quick couple of questions:
1. If sdk is in my system path, does that mean I wouldn't need to move stuff to the tools folder to resign it, push it etc?
If so:
2. How do I do this black magic?
I know, I know my inner n00b is showing again
Click to expand...
Click to collapse
if sdk tools directory is in your system path, that means any app in that directory can be called from anywhere in your computer, including push.
The directions are in the first post for auto remove script if you need.
Or you can purchase Root Manager for a dollar and remove the apps that way..
@jackal424:
Good to know! Now I just need to figure out how to put sdk in the system path. I'll Google it later.
Why not just create your own update.zip to do all the actions after flashing the ROM zip? Here's an example of mine...
Code:
show_progress 0.1 0
delete_recursive DATA:dalvik-cache/
delete_recursive DATA:boot-cache/
delete SYSTEM:app/com.android.launcher2.apk
delete SYSTEM:app/LiveWallpapers.apk
delete SYSTEM:app/LiveWallpapersPicker.apk
delete SYSTEM:app/VisualizationWallpapers.apk
delete SYSTEM:app/HtcLockScreen.apk
delete SYSTEM:app/HtcLockScreen.odex
delete SYSTEM:app/DeskClock.apk
delete SYSTEM:app/DeskClock.odex
delete SYSTEM:app/com.htc.StockWidget.apk
delete SYSTEM:app/Stock.apk
delete SYSTEM:app/Sprint_Navigation.apk
delete SYSTEM:app/HtcFootprintsWidget.apk
delete SYSTEM:app/HtcFootprints.apk
delete SYSTEM:app/LatinIME.apk
delete SYSTEM:app/GSD.apk
delete SYSTEM:app/FieldTest.apk
delete SYSTEM:app/amazonmp3.apk
delete SYSTEM:customize/resource/BigBen.jpg
delete SYSTEM:customize/resource/Colosseum.jpg
delete SYSTEM:customize/resource/EiffelTower.jpg
delete SYSTEM:customize/resource/StatueOfLiberty.jpg
delete SYSTEM:customize/resource/htc_wallpaper_01_lockscreen.jpg
delete SYSTEM:customize/resource/htc_wallpaper_02_lockscreen.jpg
delete SYSTEM:customize/resource/htc_wallpaper_03_lockscreen.jpg
delete SYSTEM:customize/resource/htc_wallpaper_04_lockscreen.jpg
delete SYSTEM:customize/resource/htc_wallpaper_05_lockscreen.jpg
delete SYSTEM:customize/resource/htc_wallpaper_06_lockscreen.jpg
delete_recursive SYSTEM:media/audio/
delete_recursive SYSTEM:media/bootscreen/
delete SYSTEM:media/bootanimation.zip
copy_dir PACKAGE:system SYSTEM:
show_progress 0.2 10
Just find an existing update package (any of them) and modify the update script to your liking and also put files in /system/ that you want in your ROM. (You could also put files into /data/app/ to load your programs, but I use A2SD which needs to be mounted first).
This also inserts my favorite Boot animation and favorite HTC keyboard into the ROM. My media files I keep in the /sdcard/ directory, so I just delete them from the ROM as well.
The benefits of doing this is that I can leave this on the root of my sdcard and just flash this ZIP after flashing a ROM.
-Daryel
daryelv said:
Why not just create your own update.zip to do all the actions after flashing the ROM zip?
Click to expand...
Click to collapse
Both methods are great (Update.zip is method I use). Not to mention, with this method, you don't have to be on a computer to do it. Just write the update file once, always leave it on your SD Card and run whenever you want... that's convenient to me.
Plus both files can be distributed to someone whose not tech savvy to wipe what they don't want... thank god!
4SidedDie said:
Or you can purchase Root Manager for a dollar and remove the apps that way..
Click to expand...
Click to collapse
Not saying Root Manager isn't a good purchase, but a .bat file will remove all the apps I want gone faster than any other method I've found. Just double-click and they're all gone!
4SidedDie said:
Or you can purchase Root Manager for a dollar and remove the apps that way..
Click to expand...
Click to collapse
Well... personally, there's no need to pay for something if you're capable of doing it yourself (Not saying you aren't) -- especially when this method is more streamlined and a lot more efficient.
daryelv said:
Why not just create your own update.zip to do all the actions after flashing the ROM zip? Here's an example of mine...
Code:
show_progress 0.1 0
delete_recursive DATA:dalvik-cache/
delete_recursive DATA:boot-cache/
delete SYSTEM:app/com.android.launcher2.apk
delete SYSTEM:app/LiveWallpapers.apk
delete SYSTEM:app/LiveWallpapersPicker.apk
delete SYSTEM:app/VisualizationWallpapers.apk
delete SYSTEM:app/HtcLockScreen.apk
delete SYSTEM:app/HtcLockScreen.odex
delete SYSTEM:app/DeskClock.apk
delete SYSTEM:app/DeskClock.odex
delete SYSTEM:app/com.htc.StockWidget.apk
delete SYSTEM:app/Stock.apk
delete SYSTEM:app/Sprint_Navigation.apk
delete SYSTEM:app/HtcFootprintsWidget.apk
delete SYSTEM:app/HtcFootprints.apk
delete SYSTEM:app/LatinIME.apk
delete SYSTEM:app/GSD.apk
delete SYSTEM:app/FieldTest.apk
delete SYSTEM:app/amazonmp3.apk
delete SYSTEM:customize/resource/BigBen.jpg
delete SYSTEM:customize/resource/Colosseum.jpg
delete SYSTEM:customize/resource/EiffelTower.jpg
delete SYSTEM:customize/resource/StatueOfLiberty.jpg
delete SYSTEM:customize/resource/htc_wallpaper_01_lockscreen.jpg
delete SYSTEM:customize/resource/htc_wallpaper_02_lockscreen.jpg
delete SYSTEM:customize/resource/htc_wallpaper_03_lockscreen.jpg
delete SYSTEM:customize/resource/htc_wallpaper_04_lockscreen.jpg
delete SYSTEM:customize/resource/htc_wallpaper_05_lockscreen.jpg
delete SYSTEM:customize/resource/htc_wallpaper_06_lockscreen.jpg
delete_recursive SYSTEM:media/audio/
delete_recursive SYSTEM:media/bootscreen/
delete SYSTEM:media/bootanimation.zip
copy_dir PACKAGE:system SYSTEM:
show_progress 0.2 10
Just find an existing update package (any of them) and modify the update script to your liking and also put files in /system/ that you want in your ROM. (You could also put files into /data/app/ to load your programs, but I use A2SD which needs to be mounted first).
This also inserts my favorite Boot animation and favorite HTC keyboard into the ROM. My media files I keep in the /sdcard/ directory, so I just delete them from the ROM as well.
The benefits of doing this is that I can leave this on the root of my sdcard and just flash this ZIP after flashing a ROM.
-Daryel
Click to expand...
Click to collapse
uhhh....that's nice...i'm going to give this a shot....it is more convinient then double clicking....it stays on the phone too.... no need to connect phone to comp..
jackal424 said:
uhhh....that's nice...i'm going to give this a shot....it is more convinient then double clicking....it stays on the phone too.... no need to connect phone to comp..
Click to expand...
Click to collapse
Agreed. That is nice.
Nice thread....
Nice thread....
//forum.xda-developers.com/showthread.php?t=581635
I would like to copy additional files into the /data/app/ folder with an update.zip file. My script will successfully add to /system/app/ folder but not /data/app/. I've seen code to delete and then add a whole new /data/app/ folder but I would like to keep whatever is in there already, just add and remove specific files in it. This is what I've been using but it fails. Can this be done?
Code:
show_progress 0.200000 0
delete DATA:app/com.facebook.katana.apk
copy_dir PACKAGE:data DATA:
set_perm 1000 1000 0771 DATA:app
diordnahero said:
I would like to copy additional files into the /data/app/ folder with an update.zip file. My script will successfully add to /system/app/ folder but not /data/app/. I've seen code to delete and then add a whole new /data/app/ folder but I would like to keep whatever is in there already, just add and remove specific files in it. This is what I've been using but it fails. Can this be done?
Code:
show_progress 0.200000 0
delete DATA:app/com.facebook.katana.apk
copy_dir PACKAGE:data DATA:
set_perm 1000 1000 0771 DATA:app
Click to expand...
Click to collapse
While not necessarily my forte, do you happen to be running apps2sd? My guess is that the partition on the SD card hasn't mounted yet, and thus, the file(s) can't be accessed to delete.
yes I am.
Though my update script works to write and delete to /system/.. folders just fine. The update-script files I have looked at delete the whole folder first and then create/copy the new one, then correct permissions. I can't find anything specific to delete/adding individual files though.
diordnahero said:
yes I am.
Though my update script works to write and delete to /system/.. folders just fine. The update-script files I have looked at delete the whole folder first and then create/copy the new one, then correct permissions. I can't find anything specific to delete/adding individual files though.
Click to expand...
Click to collapse
The system folder is not part of apps2sd, so that would make sense.
I'm still thinking this is your issue. I'm wondering if there is a way to mount via an update script?
JsChiSurf said:
The system folder is not part of apps2sd, so that would make sense.
I'm still thinking this is your issue. I'm wondering if there is a way to mount via an update script?
Click to expand...
Click to collapse
I dont think mounting via an update script is possible but you could write a script to do it kinda like Cyanogen's backup script that mounts the sdcard when in recovery to do a backup of google ****s.
zippy-man said:
I dont think mounting via an update script is possible but you could write a script to do it kinda like Cyanogen's backup script that mounts the sdcard when in recovery to do a backup of google ****s.
Click to expand...
Click to collapse
I saw this syntax referenced in another thread, that you can use in an update script:
run_program PACKAGE:script.sh
I'm assuming this is what Cyanogen is doing?
That's pretty cool. So, moral of the story, you can create a little shell script that runs during the update process that will mount the necessary partition, and move / add / delete files as necessary.
Actually makes it nicer, as you can write your entire update as a shell script rather than using the standard update script lingo, which may be less familiar...
JsChiSurf said:
I saw this syntax referenced in another thread, that you can use in an update script:
run_program PACKAGE:script.sh
I'm assuming this is what Cyanogen is doing?
That's pretty cool. So, moral of the story, you can create a little shell script that runs during the update process that will mount the necessary partition, and move / add / delete files as necessary.
Actually makes it nicer, as you can write your entire update as a shell script rather than using the standard update script lingo, which may be less familiar...
Click to expand...
Click to collapse
yup, I've done that before. Very handy. that'll get the job done
I dont think mounting via an update script is possible but you could write a script to do it kinda like Cyanogen's backup script that mounts the sdcar
Click to expand...
Click to collapse
I saw this syntax referenced in another thread, that you can use in an update script:
run_program PACKAGE:script.sh
I'm assuming this is what Cyanogen is doing?
That's pretty cool. So, moral of the story, you can create a little shell script that runs during the update process that will mount the necessary partition, and move / add / delete files as necessary.
Actually makes it nicer, as you can write your entire update as a shell script rather than using the standard update script lingo, which may be less familiar...
Click to expand...
Click to collapse
Yep. You just create whatever script you want and add that to the update script and it will run it. I have used it for many things but have not used a script to mount the sd card.
If you get a hold of the script that cm wrote you could pull out the party that mounts the sd card and use that to write to data if it its located on the sd card.
-------------------------------------
Sent from my HTC Hero
Awsome! Great stuff.
I found this but have not tried it yet as there hasn't been need to update anything lately.