Hi I downloaded this android peeing on Apple logo bootscreen, it installed well so I got too excited and wanted to put tux hammering the Windows logo before android pee on the Apple, I made all 70 png's but did not touch anything either than creating the images. I then zipped them according to the original names but when I flash it I get ..... E: wrong digest, system/media/bootanimation.zip
I have tried several times but no luck, yet the original one would easy install. Help guys
Sent from my HTC Hero VillainRom 12, flykernel11 using XDA App
any idea someone
You probably need to sign the update zip, possibly change the install/flash location. Upload what you have in a zip and I'll make one for ya
Edit: and explain what I did
kyouko said:
You probably need to sign the update zip, possibly change the install/flash location. Upload what you have in a zip and I'll make one for ya
Edit: and explain what I did
Click to expand...
Click to collapse
Too bad everyone doesn't do that.
I have decided to change the part1 folder images with custom ones, I will upload the whole zip later so when you help me I won't have to re edit it again, thanx for your replies
Apologies as this is long overdue. Finally had some free time this weekend
Attached are both the working bootscreen AND the original for those who want to see what was changed between the two.
Edit: added the non-signed bootscreen.zip for reference as well. Never know who may want to look at it.
Setup
Extracted the zip (original_doesntflash.zip) into its own directory
Created the META-INF folder
Deleted the CERT.RSA, CERT.SF, and MANIFEST.MF files
Created the "com" folder inside META-INF
Inside the "com" folder I created another folder named "google"
Inside "google" create a folder named "android" <- forgot about this step
Inside there I placed the "update-script" (if you want to know how to make one of these by hand refer to my post HERE)
Added both folders (META-INF and system) to a zip - in this case named it "bootscreen.zip"
Signing The Zip
I'm running linux currently so I do it slightly different, but I'm assuming the majority of you guys and gals are windows users. If that's the case follow these directions:
Go HERE and download AvaboxV2
Extract the AvaboxV2.zip where you want it. Personally I'd made a separate AvaboxV2 folder in my AndroidSDK dir. But the desktop still will work
Copy the newly created zip (bootscreen.zip) into the "Auto-Sign" folder found in AvaboxV2
As per the README.txt:
Start a cmd prompt AS ADMINISTRATOR (not really needed if running Win7)
cd <to the directory of the Auto-Sign folder> [Example: cd C:\AndroidSDK\AvaboxV2\Auto-sign]
java -jar signapk.jar testkey.x509.pem testkey.pk8 bootscreen.zip bootscreen_signed.zip <- same command as used in linux, at least for me
Press enter...wait...wait...done
Congratulations you now have a working/flashable bootscreen zip
thanks mate I will download it today, thanks for the tutorial man its highly appreciative, thanks a lot
kyouko said:
Apologies as this is long overdue. Finally had some free time this weekend
Attached are both the working bootscreen AND the original for those who want to see what was changed between the two.
Edit: added the non-signed bootscreen.zip for reference as well. Never know who may want to look at it.
Setup
Extracted the zip (original_doesntflash.zip) into its own directory
Created the META-INF folder
Deleted the CERT.RSA, CERT.SF, and MANIFEST.MF files
Created the "com" folder inside META-INF
Inside the "com" folder I created another folder named "google"
Inside there I placed the "update-script" (if you want to know how to make one of these by hand refer to my post HERE)
Added both folders (META-INF and system) to a zip - in this case named it "bootscreen.zip"
Signing The Zip
I'm running linux currently so I do it slightly different, but I'm assuming the majority of you guys and gals are windows users. If that's the case follow these directions:
Go HERE and download AvaboxV2
Extract the AvaboxV2.zip where you want it. Personally I'd made a separate AvaboxV2 folder in my AndroidSDK dir. But the desktop still will work
Copy the newly created zip (bootscreen.zip) into the "Auto-Sign" folder found in AvaboxV2
As per the README.txt:
Start a cmd prompt AS ADMINISTRATOR (not really needed if running Win7)
cd <to the directory of the Auto-Sign folder> [Example: cd C:\AndroidSDK\AvaboxV2\Auto-sign]
java -jar signapk.jar testkey.x509.pem testkey.pk8 bootscreen.zip bootscreen_signed.zip <- same command as used in linux, at least for me
Press enter...wait...wait...done
Congratulations you now have a working/flashable bootscreen zip
Click to expand...
Click to collapse
I got an error when flashing the signed zip I got no update file found
elliotn said:
I got an error when flashing the signed zip I got no update file found
Click to expand...
Click to collapse
LOL uhh, I'll take a look at it and test it out... and edit my previous post with w/e I did wrong
Forgot to add the ''android'' folder in the zip. Fixed and should work now
***I added some minor reliability improvements, by including more error checking, seems to run pretty smooth***
I've been playing around with making a deodexer script and having some issues, did a google search and came across these two posts.
http://forum.xda-developers.com/showthread.php?t=598026
http://forum.xda-developers.com/showpost.php?p=5775540&postcount=57
So I merged what I had with theirs and modified it to work on the Captivate ROM's.
I thought it would be a useful tool to have and thought I would share with anyone interested in deodexing their own stock ROM.
Why would you want to deodex your own ROM when you could download somebody elses? Something to do I guess.
It deodexes the app and framework folders in three passes, the first pass does the files that don't require a specific boot class path, the second pass deodexes the files that do require a boot class path and the third does a check for any files the for-do loop may have skipped.
It takes approximately 10 to 30 minutes to complete, depending on your computer, but considering that it took me almost a day to deodexed a ROM manually, , thats not so bad.
It can pull a stock ROM from your phone and deodex it, using adb or you can extract a factoryfs.rfs file and place app and framework folder into the app and framework folders for the script.
It also has a batch zipalign tool for when its done deodexing.
You have the option to select boot class paths for Captivate i897 (gingerbread or froyo), or you can input a custom boot class path string.
Extract the Deodexer_i897.zip to a folder that does not have spaces in the name.
Pull the system from your phone or add your app and framework folders to the extracted folder for the deodexer.
Then just doubleclick on deoall.bat and your off and running.
I included a Readme file with instructions.
You have to have the Java sdk and samsung usb drivers installed on your computer for it to work.
The script is a windows batch file and was modified on Windows 7. I assume it will work on XP as well, but haven't tested it.
I've tested it on:
i897 - KB1, KF1, KH3, KI1, KI2, KJ1, KJ2, KJ3, KK1 and KK2
Rogers - KH2
i9000 - JVO, JVR and JVS stock ROMs.
I've flashed and tested KF1, KH3, KI2, KJ1, KJ2 and KJ3 on my phone with no problems.
(Remember, stock KH3 - KJ3 do not have any ringtones so you will have to copy them to the media/audio folder from another ROM)
Note: Remember to check the app and framework folders for files that got skipped. If there is, try running the deodexer again just to make sure it just wasn't a glitch.
Thanks and credits goes out to Daneshm90 and crzyruski for the deodexer scripts and JesusFreke for giving us baksmali-smali and not to forget, Igor Pavlov for 7zip.
UPDATE- I'm adding a basic clockworkmod flashable script template that you can pop your system into. It includes redbend_ua, wipe, busybox, su and superuser.apk for root. You will have to add a kernel (zImage) and the appropriate modem (modem.bin) to the updates folder.
You will have to flash an update.zip (Froyo) http://forum.xda-developers.com/showthread.php?t=734163
or flash a kernel tar using odin, that has clockwork mod baked in (Gingerbread), and will need to add a cwm modded kernel to the update folder in the template if you want to keep clockwork mod recovery (Gingerbread). The template will not work with special kernels that have scripting included such as init.d, you will have to flash special MOD kernels that contain scripts, afterwards.
*****CAUTION:This is a full wipe template so be careful and know what you are doing.*****
***Fixed the Core_ROM.zip so it will install the modem and kernel, plus added the wipe script.***
It is beyond the scope of my talents and time to completely teach someone how to do all of this, but google is your friend when it comes to learning this stuff. There are allot of resources out there to help you accomplish your task. I'm just merely supplying some basic tools for you.
TOOLS
Notepad++ works great at editing the updater-script in the META-INF folder.
And the smali and xmls in the apks and jars.
http://notepad-plus-plus.org/
And Apkmanager is great to decompile and compile apk and jar files - Thanks raziel23x
http://forum.xda-developers.com/showthread.php?t=1227179
Just add .apk to the end of the .jar, do your modding, change it back to jar when you're done, works great.
Plus raziel23x has a new apk multi tool that is still in beta but is worth watching http://apkmultitool.com/
Also for those that want a free alternative to Photoshop to modify your graphics, there is a great program called Paint.Net http://paintnet.org/
If you are serious about MODDING here is another valuable tool, Beyond Compare available here $$ http://www.scootersoftware.com/
And this is a valuable reference for those interested in Modding
http://forum.xda-developers.com/showthread.php?t=822311
KERNELS
For KF1 I found this link for the cog5-beta2-kernel.tar, thanks to designgears. http://ftp.captivate.org.ua/samsung/captivate/2.3.x/2.3.3/ROM/cognition_5/
And of course, for KH3 and KI1-KI2 use Boogs kernel available here http://forum.xda-developers.com/showthread.php?t=1242533
For KJ1, KJ2 and KJ3 use Boogs kernel here http://forum.xda-developers.com/showthread.php?t=1294849
***The script has been updated to include the boot class path as an option, instead of having to copy and paste the whole thing, so the Bootclass_path.txt file is no longer needed... Thanks to ralphreyes ***
**NOTICE: due to the nature of DOS (Windows) environmental variables, the deodexer needs to be extracted to the root folder, or any folder it resides in, can't have a space in its name. e.g. Android SDK as opposed to Android_SDK***
As always, I am not responsible if it messes up your phone.
I hope someone finds this useful.
***NOW ITS FINAL***
This is awesome !! Thanks for sharing.
I will have to check this out when I get time this weekend...or sooner.
What about an odexer?
I would like to odex the ROM on my phone after I get my desired modifications in. Any chance on an odexer script?
Thanks I've been looking for an easy way to deodex my own stock rom. I will put it to good use.
Sent from my SAMSUNG-SGH-I897 using XDA App
gibson3659 said:
I would like to odex the ROM on my phone after I get my desired modifications in. Any chance on an odexer script?
Click to expand...
Click to collapse
Odexing is a little tricky, I haven't found a compiler to do that, something exclusive to google and phone manufacturing developers. Though the performance of an odexed ROM is so slight over a deodexed one, it probably wouldn't be worth it.
Nice job on the "Read me".
Will be trying my hand at this asap...
thanks again
4-2ndtwin said:
Nice job on the "Read me".
Will be trying my hand at this asap...
thanks again
Click to expand...
Click to collapse
Thanks, let me know how it goes. I did three more ROMs after I fixed it and flashed two of them and had no problems. When I get home tonight, was going to add an option to root plus will upload some templates for cwm recovery.
Sent from my SAMSUNG-SGH-I897 using XDA App
crt60 said:
**NOTICE** I added another deodexer for high performance computers with quad-core or high end dual core processors, even though the original deodexer works fine, because the script would run so fast, it can produce errors, or skip files because of possible memory segment overlap, causing null pointer exceptions, so I added a 3 second pause between each operation to solve this issue. It only adds a minute or two to the deodexing time, but should add reliability and integrity to the deodexed ROM -> Deodexer_i897x.zip
I've been playing around with making a deodexer script and having some issues, did a google search and came across these two posts.
http://forum.xda-developers.com/showthread.php?t=598026
http://forum.xda-developers.com/showpost.php?p=5775540&postcount=57
So I merged what I had with theirs and modified it to work on the Captivate ROM's.
I thought it would be a useful tool to have and thought I would share with anyone interested in deodexing their own stock ROM.
Why would you want to deodex your own ROM when you could download somebody elses? Something to do I guess.
It deodexes the app and framework folders in three passes, the first pass does the files that don't require a specific boot class path, the second pass deodexes the files that do require a boot class path and the third does a check for any files the for-do loop may have skipped.
It takes approximately 10 to 30 minutes to complete, depending on your computer, but considering that it took me almost a day to deodexed a ROM manually, , thats not so bad.
It can pull a stock ROM from your phone and deodex it, using adb or you can extract a factoryfs.rfs file and place app and framework folder into the app and framework folders for the script.
It also has a batch zipalign tool for when its done deodexing.
You have to manually add the boot class paths at the beginning when prompted, but I included a text file that you can just copy and paste the appropriate boot class paths into the script. I did that in case of future or other ROMs, so the boot class paths could be modified.
Just doubleclick on deoall.bat and your off and running.
I included a Readme file with instructions.
You have to have the Java sdk and samsung usb drivers installed on your computer for it to work.
The script is a windows batch file and was modified on Windows 7. I assume it will work on XP as well, but haven't tested it.
I've tested it on KB1, KF1, KH3, KI1-KI2, KJ1, KJ2, KJ3 and Rogers KH2 stock ROMs.
I've flashed and tested KF1, KH3, KI2, KJ1, KJ2 and KJ3 on my phone with no problems.
(Remember, stock KH3 - KJ3 do not have any ringtones so you will have to copy them to the media/audio folder from another ROM)
Note: Remember to check the app and framework folders for files that got skipped. If there is, try running the deodexer again just to make sure it just wasn't a glitch.
Thanks and credits goes out to Daneshm90 and crzyruski for the deodexer scripts and JesusFreke for giving us baksmali-smali and not to forget, Igor Pavlov for 7zip.
UPDATE- I'm adding a basic clockworkmod flashable script template that you can pop your system into. It includes redbend_ua, busybox, su and superuser.apk for root. You will have to add a kernel (zImage) and the appropriate modem (modem.bin) to the updates folder.
You will have to flash an update.zip (Froyo) http://forum.xda-developers.com/showthread.php?t=734163
or flash a kernel tar using odin, that has clockwork mod baked in (Gingerbread), and will need to add a cwm modded kernel to the update folder in the template if you want to keep clockwork mod recovery (Gingerbread). The template will not work with special kernels that have scripting included such as init.d, you will have to flash special MOD kernels that contain scripts, afterwards.
*****CAUTION:This is a full wipe template so be careful and know what you are doing.*****
It is beyond the scope of my talents and time to completely teach someone how to do all of this, but google is your friend when it comes to learning this stuff. There are allot of resources out there to help you accomplish your task. I'm just merely supplying some basic tools for you.
TOOLS
Notepad++ works great at editing the updater-script in the META-INF folder.
And the smali and xmls in the apks and jars.
http://notepad-plus-plus.org/
And Apkmanager is great to decompile and compile apk and jar files - Thanks raziel23x
http://forum.xda-developers.com/showthread.php?t=1227179
Just add .apk to the end of the .jar, do your modding, change it back to jar when you're done, works great.
Also for those that want a free alternative to Photoshop to modify your graphics, there is a great program called Paint.Net http://paintnet.org/
KERNELS
For KF1 I found this link for the cog5-beta2-kernel.tar, thanks to designgears. http://ftp.captivate.org.ua/samsung/captivate/2.3.x/2.3.3/ROM/cognition_5/
And of course, for KH3 and KI1-KI2 use Boogs kernel available here http://forum.xda-developers.com/showthread.php?t=1242533
For KJ1 and KJ2, use Boogs kernel here http://forum.xda-developers.com/showthread.php?t=1294849
As always, I am not responsible if it messes up your phone.
I hope someone finds this useful.
***Fixed Root***
Click to expand...
Click to collapse
thanks for your work ,so i can build my own rom by myself with less work
crt60,
Didn't get a chance to try this out last weekend. I hope to get to it this Sat. I'll give u some feed back afterwards.
Appreciate the work u are doing and sharing.
Sent from i897uckj3
How can I extract a one-click .exe stock ROM?
Thansk.
chappatti said:
How can I extract a one-click .exe stock ROM?
Thansk.
Click to expand...
Click to collapse
You can't that I know of, it is a microsoft mfc program and I haven't found a decompiler for it. You will have to find the original odin tar file
Sent from my SAMSUNG-SGH-I897 using XDA App
crt60 said:
You can't that I know of, it is a microsoft mfc program and I haven't found a decompiler for it.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Thanks for your quick reply !!
One thing is not clear in your reademe? Do I need to run the deodexer from the stock ROM folder, or do ineed to edit my win $path.?
chappatti said:
Thanks for your quick reply !!
One thing is not clear in your reademe? Do I need to run the deodexer from the stock ROM folder, or do ineed to edit my win $path.?
Click to expand...
Click to collapse
Copy the app and framework folders in system into the deodexer folder and merge with the app and framework folders already there.
Sent from my SAMSUNG-SGH-I897 using XDA App
crt60 said:
Copy the app and framework folders in system into the deodexer folder and merge with the app and framework folders already there.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I have checked the updater-script and found it doesn't extract the 'updates' folder ，so the zImage and modem.bin can't be installed
q659503934 said:
I have checked the updater-script and found it doesn't extract the 'updates' folder ，so the zImage and modem.bin can't be installed
Click to expand...
Click to collapse
I will check it out when i get time
Sent from my SAMSUNG-SGH-I897 using XDA App
crt60 said:
I will check it out when i get time
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I just add the script
ui_print("");
ui_print("extract files...");
package_extract_dir("updates", "/tmp");
set_perm(0, 0, 0777, "/tmp/redbend_ua");
i think you could build a ROM template ,it's more useful.
Yep, you're right. I must have accidentally deleted that, when I removed the wipe program, trying to simplify the script. It has been fixed, plus I went ahead and added the wipe script back in. Thanks for your input...
Sent from my SAMSUNG-SGH-I897 using XDA App
I thought I would make it a little easier on your script by adding a couple extra lines to the 'deoall.bat' file so the bootclass path is included within. When it prompts you to enter the bootclass path, you can enter 1 for GingerBread, 2 for Froyo, or you can just enter your custom one.
Replace the line that starts with
Code:
set /P INPUT=Enter BootClassPath (ex 1.jar:2.jar:3.jar): %=%
with the following:
Code:
echo Enter BootClassPath: 1=GingerBread, 2=Froyo,
set /P INPUT=or custom (ex file1.jar:file2.jar:file3.jar): %=%
IF %INPUT%==1 (set INPUT=core.jar:bouncycastle.jar:core-junit.jar:twframework.jar:services.jar:framework.jar:seccamera.jar:javax.obex.jar:com.google.android.maps.jar)
IF %INPUT%==2 (set INPUT=core.jar:twframework.jar:android.policy.jar:services.jar:framework.jar:seccamera.jar:javax.obex.jar:com.google.android.maps.jar)
Thank you for your excellent work crt60!!
ralphreyes said:
I thought I would make it a little easier on your script by adding a couple extra lines to the 'deoall.bat' file so the bootclass path is included within. When it prompts you to enter the bootclass path, you can enter 1 for GingerBread, 2 for Froyo, or you can just enter your custom one.
Replace the line that starts with
Code:
set /P INPUT=Enter BootClassPath (ex 1.jar:2.jar:3.jar): %=%
with the following:
Code:
echo Enter BootClassPath: 1=GingerBread, 2=Froyo,
set /P INPUT=or custom (ex file1.jar:file2.jar:file3.jar): %=%
IF %INPUT%==1 (set INPUT=core.jar:bouncycastle.jar:core-junit.jar:twframework.jar:services.jar:framework.jar:seccamera.jar:javax.obex.jar:com.google.android.maps.jar)
IF %INPUT%==2 (set INPUT=core.jar:twframework.jar:android.policy.jar:services.jar:framework.jar:seccamera.jar:javax.obex.jar:com.google.android.maps.jar)
Thank you for your excellent work crt60!!
Click to expand...
Click to collapse
Nice, I did make a script like that but thought it would be too confusing for those that use this for non-captivate ROMs. I'll update the link with the new code.
Thanks
could add option 3 , custom boot class list (as it is now) for other devices! or have them save it to a txt file in a list one per line and have the bat read the custom txt list
Hi. I've always thought about this. Some people say something like this
Copy the file aroma-config and updater-script from META-INF\com\google\android\ from 3.1.1 rom.zip to 3.1.2 zip to the same path. He will say v3.1.1 during installation, but he will install 3.1.2 and you can select CLK again.
Click to expand...
Click to collapse
And what does it mean? When I edit zip file, it doesn't work. Is there a program for this?
kubekpop said:
Hi. I've always thought about this. Some people say something like this
And what does it mean? When I edit zip file, it doesn't work. Is there a program for this?
Click to expand...
Click to collapse
Looks like the update (the zip) mentioned in the quote disables a feature on the HD2 that was present before that update. See here - shouldn't you have included that link
hxxp://forum.xda-developers.com/showthread.php?t=1166948&page=1286
To prevent disabling the feature, the quote-poster advises to run the update with the updater script (the script that does the actual updating) replaced by an old version. To do that, download both update versions and replace the mentioned files mentioned in the post in the newest version. Rezip and apply the update.
Not sure if this is a wise thing to do if you don't know more about updating, restoring etc... At least backup your data.
No, it's just when I zip it after update, cwm doesn't want to install this and sees as damaged rom.
But 7-zip can change files in archive no need to unzip all. So it works
... to "flash" or otherwise install theme type mods such as changing a notification icon, without recovery? I had experimented with framework type flashable zip files to do with on my GS3 and always flashed from recovery. I am trying to (at least for now) keep from tripping my KNOX.
Also is there a wifi hotspot app or mod that also does not require recovery?
With a towel root, I can probably do everything I want, and keep my KNOX at 0, if I can do these two things.
Bob
ParrSt said:
Is it possible? ... to "flash" or otherwise install theme type mods such as changing a notification icon, without recovery?
Click to expand...
Click to collapse
Sure. It's just more work. Having root gives you the necessary permissions to change system files and do anything that a (recovery) flashable zip file would.
But pragmatically, it wouldn't be reasonable to expect everyone going around writing custom install scripts for your theme mods when the common practice is to package them as a flashable zip.
The solution? It would be eminently useful to learn how to make manual changes yourself. Theme mods typically modify a system file e.g. TouchWizHome.apk or SystemUI.apk. You can make simple edits or replace packages with a root aware file browser e.g. FX. And more advanced edits with a decompiler like apktool.
.
fffft said:
Sure. It's just more work. Having root gives you the necessary permissions to change system files and do anything that a (recovery) flashable zip file would.
But pragmatically, it wouldn't be reasonable to expect everyone going around writing custom install scripts for your theme mods when the common practice is to package them as a flashable zip.
The solution? It would be eminently useful to learn how to make manual changes yourself. Theme mods typically modify a system file e.g. TouchWizHome.apk or SystemUI.apk. You can make simple edits or replace packages with a root aware file browser e.g. FX. And more advanced edits with a decompiler like apktool.
.
Click to expand...
Click to collapse
Oh I don't expect others to make my scripts. I was making the zip packages myself.
If I understand you correctly, I can use something like FX to replace the an icon in one of the .apks? Those are zip type files but FX can do that?
As I already said, yes you can. Icons are (usually) especially easy. It's literally just replacing an icon with a file browser, usually in the xxhdpi360 drawable folder of the apk.
Something like
Copy the apk to another directory or your PC
Temporarily rename the .apk to a .zip file
Use FX Root to browse the compressed file and locate the icon you want to change.
Delete the icon from the zip.
Drag and drop the new icon to replace it.
Rename the .zip back to .apk
Browse to the folder where you copied the apk from
Rename the original .apk to .bak in case you need it later
Move your modified apk to the directory
Confirm that the permissions are still 0644 (long press to check.. but I've never seen FX mess them up to start with).
Reboot
That may look like a lot of steps but they are all trivial and you can do the entire thing in about 60 seconds.
Features e.g. suppressing nags or some colour changes may require decompiliing an apk.
.