okay, im new to this and i just spent the last three hours taking all the app icons from the aero theme and applying them to the gloss suite theme,
just for myself,
not uploading this,
but now that im done i dont know how to properly sign this stupid thing to get it to apply to my phone! helllppp!
i need detailed instructions because at the moment i feel like i have tried every single how to on signing and theming and im stumped and annoyed
ps sorry for posting this here but it doesnt seem that anyone who posts in the other thread gets any answers...
Use Stericson's auto signing tool, run the autosign.bat file, choose 4) which is for manual signing, after choosing xp/vista option. Then type the full path to your theme .zip file and let it sign. If there arent any errors shown, then its ready to be uploaded.
i made a very very very huge mistake when re zipping all of the apks...
heres to another hour of work..
Make sure you do the first two options in Autosign.bat. This happened to me, or you'll get an error everytime and it won't verify. It add directories or some **** to java. Make sure you've sone that!
yeah thats all good, i just cant believe i didnt notice that i somehow double zipped everything.
thats rediculous im slapping myself across the face right now
okay now im really really stuck,
i believe that i have done everything and it should be perfect but when i try to install the theme i get this
installing from sdcard...
finding update package...
openining update package...
E:Wrong digest:
system/app/Vending.apk
E:Verification Failed
Installation aborted.
Help me pleeaassseee im so frustrated
It is probably not signing correctly. That is one of the "tells".
I ran the Stericson Autosign tool according to the thread and it worked perfectly going through all four steps.
it def wasnt the signing,
i started over from scratch being much more careful and now it works!
thanks for the help guys,
oh and btw
GLOSS SUITE + AERO ICONS FTW
I'm running the latest Zero Hero rom and I managed to push a different resources once then I used my noob themere skills to give it the blur animations which failed and I had changed the build.prop with the maxisma 1 as it has native led support before pushing the resources.
So I reflashed and everything went back out of the boot loop that I had created with my botched framework-res editing but now I can't push anything becuz the phone keeps saying the file system is read only.
Any thoughts on how to fix my noob mistakes and actually get the blur animations to work without somehow making my file systems go haywire.
adb remount......
the bootloop could be caused by the incompatible build.prop file, your not just supposed to switch them between roms.....
B-man007 said:
adb remount......
the bootloop could be caused by the incompatible build.prop file, your not just supposed to switch them between roms.....
Click to expand...
Click to collapse
No actually it isnt its becuz my noob themer skills and me messing with the framework to get blur transitions the build.prop is running smoothly on this build and thx for the adb remount tip
Hello everyone.
I have been searching for hours and found nothing relating to my specific issue. Basically it is this, I have recently finished a theme and am ready to release it. Before doing so I wanted to test its functionality. Now pushing the apk's through android commander works perfectly, installing my themed apk's via update.zip through recovery has become a headache. After the "update" has finished and I boot the phone i run into an interesting scenario. Once I slide to unlock I get an error that com.phone.apk is fc'ing then boot loop. Same error until I pull the battery. I have no idea wtf is going on and I came here to you fine folks searching some assistance. Btwi haven't touched the phone apk. Here is what I themed:
ADW
Browser
Google quick search box
MMS
Settings
Framework
All the above are directed to system in the update script.
I also included two widgets that I made and directed those to data.
Script looks like this:
copy_dir PACKAGE:system SYSTEM:
copy_dir PACKAGE:data DATA:
Now this is my first time doing this and from everything I have read this will do what I want, and for the most part it seems as if it has copied the right files but somehow in the process fubared other things.
Any ideas, help and solutions are greatly welcome.
Syn
When installing new themes or add ons through metamorph when it gets to installing the framework.apk files i end up waiting for about 30 minutes and then the app goes into not responding. How long does it usually take to install the framework.apk files? Is there anything I can do to make these files work without causing metamorph to not respond after a certain amount of time? Any help would be great with this problem I am having.
It shouldn't take more than a couple of minutes. Make sure the morph is made for the ROM you are using it on as the framework is sometimes different. (namely if it has .xml edits and .jar file edits)
I have in the past had metamorph freeze prior to rebooting, or just randomly reboot during install. But it was normally an issue with my morph itself.
I am running CM6.1 and I am new to all of this so is there a way to find out if it will work on my ROM without having to search for all of the files again through various websites?
this script is based on the work to Danesham90 and others see link
http://forum.xda-developers.com/showthread.php?t=598026
===============================================================================
Tested on the Samsung Vibrant, Script may need modification for other phones
===============================================================================
===============================================================================
Directions:
===============================================================================
the easy way:
1. turn on USB debugging
2. plug phone in to computer
3. run the script and follow the screen pormpts
the script will download everything needed to make a
signed deodexed clockwork flashable update.zip while also
adding root and the modified 3e recovery in the proccess.
===============================================================================
the hard way:
http://forum.xda-developers.com/showpost.php?p=10986893&postcount=28
================================================== =============================
Code:
/* This program is free software. It comes without any warranty, to
* the extent permitted by applicable law. You can redistribute it
* and/or modify it under the terms of the Do What The **** You Want
* To Public License, Version 2, as published by Sam Hocevar. See
* http://sam.zoy.org/wtfpl/COPYING for more details. */
UPDATED 02/03/2010
bug fix to signupdate.jar
clockwork script tweeks
UPDATED 02/02/2011
added upload to ROM to SDCard
added reboot recovery
added test sign all apk's in ROM - see README for details
added pull "/data/app/" and install "/data/app"
UPDATED 02/01/2011
added adb on by default toggle
added data wipe toggle
updated smali/baksmali to 1.2.6
UPDATED 01/31/2011
updated adb
fix similar filename deletion when using delete.txt
added barebones_delete.txt deletes everything that
does not cause phone to crash
UPDATED 01/29/2011
add "symlink dumpstate SYSTEM:bin/dumpmesg" to update-script.
add "symlink debuggerd SYSTEM:bin/csview" to update-script.
completed secondary method to make ROM from extracted Odin files.
see this post for instructions
http://forum.xda-developers.com/showpost.php?p=10986893&postcount=28
UPDATED 01/28/2011
added auto delete apk's (bloat removal), edit bin/example_delete.txt and rename to delete.txt
added auto add apk's (pre-install or update apk's) add apk's to bin/apks directory
UPDATED 01/23/2011
fix path error when space in user name
UPDATED 01/22/2011
updated TempRoot.exe to not trigger anti-virus
updated Superuser.apk
This is fantastic! Thank you for always making things a little less troublesome.
Oooops, last minute change broke something, fixed and re-uploaded.
untermensch said:
Oooops, last minute change broke something, fixed and re-uploaded.
Click to expand...
Click to collapse
Thanks for the heads up. I was just testing this on KA5 for funsies. It looked like it went ok but there was a prob with temp root at the beginning and it looked like a few java errors at the end. I'll re-download and give it another go.
Edit: Ah, looks like it's working now. Temp root worked and it downloaded the modem and kernel.
Edit2: So it looked as though everything worked fine, but when I went to install it I got
E:Can't symlink /system/bin/cat
E:Failure at line15:
symlink toolbox SYSTEM:bin/cat
Installation aborted.
Whitehawkx said:
Thanks for the heads up. I was just testing this on KA5 for funsies. It looked like it went ok but there was a prob with temp root at the beginning and it looked like a few java errors at the end. I'll re-download and give it another go.
Edit: Ah, looks like it's working now. Temp root worked and it downloaded the modem and kernel.
Click to expand...
Click to collapse
I just tested on my laptop and got a java out of memory error
while signing the rom so I increased the heap size which seems
to have fixed it.
untermensch said:
I just tested on my laptop and got a java out of memory error
while signing the rom so I increased the heap size which seems
to have fixed it.
Click to expand...
Click to collapse
Yea I got the same thing as well. Thanks again, will give it another go.
Update: The process was more in-depth when deodexing. Signing went through np and when I flashed through clockwork it worked (goodbye splash screen!). There must be some issue with KA5 though. It got through to the Galaxy S screen and then started vibrating and then blackscreen. T_T
Thank god for this.. (Deodexer)
Thanks untermensch, your the best
Really really appreciate this. Thanks a bunch!
Most useful tool EVAR!
I T W O R K E D~!
My final attempt last night did not shoot out the "signed_ROM.zip" at the end. I ran it again this morning on KA5 and when it finished I had the signed_ROM.zip in the folder. Put that on my internal, flashed through clockwork and viola! Doedexed KA5 with root and modded 3e recovery. I can't thank you enough Untermensch for putting this together for everyone.
"Give a man fish feed him for a day. Provide him with tools to fish and feed him for a lifetime." (Yea I tweaked it but you get the idea!)
I noticed one thing. During the deodexing process I got [null] on one file in the core.odex. After it had all finished up I looked in the framework folder and core.odex was still there. So am I correct in assuming that it did not doedex properly? Other than that everything else looks golden.
Oh this is sick. i was looking for this all day the otherday when i was trying to deodex ka5! you rock and rule. i cant wait to explore the possiblities!
Whitehawkx said:
I noticed one thing. During the deodexing process I got [null] on one file in the core.odex. After it had all finished up I looked in the framework folder and core.odex was still there. So am I correct in assuming that it did not doedex properly? Other than that everything else looks golden.
Click to expand...
Click to collapse
I deleted the core.odex file and rebooted just to see what would happen and it soft bricked and is stuck at the Vibrant screen. So it seems the only issue lies in deodexing the core.jar at this point.
can i use this to port a rom? forgive me if that is a noob question. just wanted to know if i had the right idea...
Whitehawkx said:
I noticed one thing. During the deodexing process I got [null] on one file in the core.odex. After it had all finished up I looked in the framework folder and core.odex was still there. So am I correct in assuming that it did not doedex properly? Other than that everything else looks golden.
Click to expand...
Click to collapse
yep that was an baksmali error, likely you could run the script again and it
would baksmali OK.
this script is a real system stress test, any way I increased the java maxmem
setting for framework files to 1024m added error logging and the script will
now stop if there is an error. hopefully to prevent a broken ROM from being
released.
Whitehawkx said:
I deleted the core.odex file and rebooted just to see what would happen and it soft bricked and is stuck at the Vibrant screen. So it seems the only issue lies in deodexing the core.jar at this point.
Click to expand...
Click to collapse
can you reproduce this error? I have seen it once but cant reproduce it
untermensch said:
yep that was an baksmali error, likely you could run the script again and it
would baksmali OK.
this script is a real system stress test, any way I increased the java maxmem
setting for framework files to 1024m added error logging and the script will
now stop if there is an error. hopefully to prevent a broken ROM from being
released.
Click to expand...
Click to collapse
untermensch said:
can you reproduce this error? I have seen it once but cant reproduce it
Click to expand...
Click to collapse
Pretty sure the core.odex [null] error I got happened every time I ran the program. I ran it once after the 1:25am update and it happened. That is also the time it did not produce the signed_ROM.zip. I ran it again this morning after I saw the OP had been updated and it did produce the signed_ROM.zip but I still got the [null] error on core.odex. I'm going to Odin KA5 and do it again right now. I will let you know how it works out.
On a side note. I flashed the one I recieved this morning with everything being deodexed except the core.jar and it ran great until I deleted the odex file. Anywho, will test now. Also, not sure if this matters but I am running 32-bit Windows 7.
Update1: Initial news is good. Core.jar was deodexed properly with no errors. Will let you know how the entire process fairs once its completed.
Worked perfectly. I got no errors and everything deodexed properly. Flashed it on my phone and it's running just fine. You are awesome.
Thanks for retesting, glad it worked, there are thousands of files being generated
an lots of java processes being spawned so there are bound to be an occasional
error. I have added an automatic retry when there is an error to the next version
should be posted some time tomorrow.
I'm about 3/4 the way through testing this out - it seems to be working just fine with the exception that every command is appended with "ATTRIB" is not recognized as...
Hopefully it will work anyway.
One thing I noticed that might speed the script up in the beginning would be a root check, I have already rooted this rom but it still needed to run rageagainstthecage.
I've been looking for something like this forever now, thanks so much! Can't wait to play with it.
Sent from my SGH-T959 using Tapatalk