Related
Hey guys, so this script de-odexe's a rom's apks and jar's.
Many thanks to ofcourse JesusFreke who created this method and the way to do it. Also to coolbho for his apkopt script from which i learnt certain techniques of batch programming. This is crzyruski script updated with jesus freke's latest smali/baksmali update ver 1.2.3
It incorporates detecting the bootclasspath of the odex instead of the user specifying it. For non standard odex however a specific bootclass path must be defined. For example:
According to Jr33 for rosie deodexing u have to add class paths com.htc.framework.jar. Thank him for the new Sense bootclasspaths
For those who dont know, this essentially uses jf's method of baksmali'ing the odex file into smali files, and then recreating the classes.dex file and packaging it into the apk hence disregarding the need for the odex.
*New Menu added
*Ability to specify custom bootclasspath (eg for sense ui)
*Added a java check at the beginning
*Added 1.2.3 smali/baksmali with froyo support(thank jf ofcourse )
*Modified it so if an error is encountered during deodexing, it leaves that file behind so once done you know what files encountered errors
*Added Ignore Mode
*Removed zipalign
*If apk doesnt have corresponding odex, it moves it to deodexed_APK instead of user manually moving it
*Added compression level option
*You can monitor the status of ignore mode / compression level right above the main menu
DISCLAIMER:
Its a batch file so it'll only work on windows.
Convince farmatito to bring this to linux
Thanks
So I checked this out and all ...
It's only apk's, right?
I only glanced but I didn't see anything in there for framework, etc.
If I'm right, then perhaps .. you should just say it de-odex's a ROM's apk's instead of the entire ROM.
~enom~
enomther said:
So I checked this out and all ...
It's only apk's, right?
I only glanced but I didn't see anything in there for framework, etc.
If I'm right, then perhaps .. you should just say it de-odex's a ROM's apk's instead of the entire ROM.
~enom~
Click to expand...
Click to collapse
Oh, yea so it takes the apk and odex and creates the classes.dex and repackages into the apk so u only need the apk. Ok, ill change the post a bit also yes, it doesnt do frameworks cuz i dont think they have odex's and the jar's do but i dunno of a method to do tht
Daneshm90 said:
Oh, yea so it takes the apk and odex and creates the classes.dex and repackages into the apk so u only need the apk. Ok, ill change the post a bit also yes, it doesnt do frameworks cuz i dont think they have odex's and the jar's do but i dunno of a method to do tht
Click to expand...
Click to collapse
Yea ... the jar's have dex's too and can be odex-d and can also be un-odex-d. I personally have never been able to successfully de-odex a fully odex'd framework (but I haven't tried hard enough either ). The main difference is once they are de-odex'd ... you insert the classes.dex into the jar and no re-signing required (as they aren't signed).
Either way, nice script mate. Good Job!
~enom~
enomther said:
Yea ... the jar's have dex's too and can be odex-d and can also be un-odex-d. I personally have never been able to successfully de-odex a fully odex'd framework (but I haven't tried hard enough either ). The main difference is once they are de-odex'd ... you insert the classes.dex into the jar and no re-signing required (as they aren't signed).
Either way, nice script mate. Good Job!
~enom~
Click to expand...
Click to collapse
Ah sweet, something i shall incorporate in the script later on. thanx
so will this script allow you to take an app from say a cliq dump and allow it to run on any android device?
Will this allow you to grab the MyFaves from a TMO rom and de-odex it and install?
Joe333x said:
so will this script allow you to take an app from say a cliq dump and allow it to run on any android device?
Click to expand...
Click to collapse
Emm...no im 99.99% sure it doesnt help tht way. I know that odex's cause customization problems in roms....there are other factors im sure
mrandroid said:
Will this allow you to grab the MyFaves from a TMO rom and de-odex it and install?
Click to expand...
Click to collapse
MyFaves == No Go ... it requires some other form of trickery ... I'm not sure what exactly ... as I did de-odex it and it would not work properly on test-key ROM's like CM, etc.
... So it requires more than a simple de-odex.
~enom~
does your phone need to be connected? I noticed some ADB commands in the script
Daneshm90 said:
Hey guys, so this script de-odexe's a rom's apks.
Many thanks to ofcourse JesusFreke who created this method and the way to do it. Also to coolbho for his apkopt script from which i learnt certain techniques of batch programming
For those who dont know, this essentially uses jf's method of baksmali'ing the odex file into smali files, and then recreating the classes.dex file and packaging it into the apk hence disregarding the need for the odex.
Oh also make sure to place only apk's that have their corresponding odex's. Dont place only apk's !!!!!
Instructions:[WINDOWS ONLY & Phone Must stay connected with adb WORKING]
1. Download http://www.mediafire.com/?mwownkhzm4m
2. Extract to a folder
3. Place all your rom's apk's which have odex's attached to them into that folder
4. Run deoall
5. Copy all the apk's from the deodexed folder into ur corresponding rom app folder
Thanks
Upcoming:
Seperate Framework & apps folder
De-odex framework apk's and jar's (thanx for the tip enomther )
Click to expand...
Click to collapse
So the apk after that has the DEX built in or is dexopt still needed?
wesgarner said:
So the apk after that has the DEX built in or is dexopt still needed?
Click to expand...
Click to collapse
>.<.......................
kingklick said:
>.<.......................
Click to expand...
Click to collapse
Hey I am just double checking
If you're having problems de-odexing the framework is because there's a particular order to it.
If you look at your bootclasspath you'll see the framework files necessary to boot the android system, the rest (whatever's not in there) can be dexopted in any order.
If you're trying to de-odex the framework, you're going to have to backtrace yourself.
Personally, I do:
for i in /system/app/*.apk
unodex
for j in /system/framework/nonCoreJar1.jar /system/framework/nonCoreJar2.jar /system/framework/...nonCoreJarN.jar
unodex
for k in /system/framework/bootClassPathJarN.jar /system/framework/bootClassPathJarN-1.jar /system/framework/...bootClassPathJarN-y.jar
unodex
it requires a couple of reboots along the way to deal with any created dalvik-cache so that it doesn't interfere with the next needed classes.dex
the only turn-off was that it requires a running system to do it (it's not that big of a problem, but porting and then flashing starts getting old after a while).
Has that changed?
Does OP mean you can take the apks, toss them into a folder, and then do it from the computer without the phone?
---edit---
shoot me for not reading.
Daneshm90 said:
Instructions:[WINDOWS ONLY & Phone Must stay connected with adb WORKING]
Click to expand...
Click to collapse
jubeh said:
If you're having problems de-odexing the framework is because there's a particular order to it.
If you look at your bootclasspath you'll see the framework files necessary to boot the android system, the rest (whatever's not in there) can be dexopted in any order.
If you're trying to de-odex the framework, you're going to have to backtrace yourself.
Personally, I do:
for i in /system/app/*.apk
unodex
for j in /system/framework/nonCoreJar1.jar /system/framework/nonCoreJar2.jar /system/framework/...nonCoreJarN.jar
unodex
for k in /system/framework/bootClassPathJarN.jar /system/framework/bootClassPathJarN-1.jar /system/framework/...bootClassPathJarN-y.jar
unodex
it requires a couple of reboots along the way to deal with any created dalvik-cache so that it doesn't interfere with the next needed classes.dex
the only turn-off was that it requires a running system to do it (it's not that big of a problem, but porting and then flashing starts getting old after a while).
Has that changed?
Does OP mean you can take the apks, toss them into a folder, and then do it from the computer without the phone?
Click to expand...
Click to collapse
Yea I would figure as much ... simply b/c one must follow the BOOTCLASSPATH order when odex'ing ...
So Jubeh .. you're saying you've personally de-odex'd an fully odex'd framework b4?
Just looking for confirmation from someone who has personally ... since I'm too lazy to go through that hectik crappy process
~enom~
enomther said:
Yea I would figure as much ... simply b/c one must follow the BOOTCLASSPATH order when odex'ing ...
So Jubeh .. you're saying you've personally de-odex'd an fully odex'd framework b4?
Just looking for confirmation from someone who has personally ... since I'm too lazy to go through that hectik crappy process
~enom~
Click to expand...
Click to collapse
I did it with the tattoo build, but upon boot I would get all sorts of fc's, but I think that was due more to a bad, hasty port than the deodexing. It was also a long time ago when the tool first came out, dont know if there's been newer revisions, so I'll try it again on that funky tattoo rom.
K guys one problem i found after doing multiple apk's is that i need to give the listening dex command a bit delay so its ready for baksmali. I was doing it right after which it misses for some conversions. I'll upload with delay between the two commands. Hmm framework i gotta give a shot :/ Sounds interesting ...
Solid script! Should make deodexing A LOT easier
Ok so i uploaded with delay between, seems to work fine, tested a LOT of times
thanks for this! can't wait for frameworks to be de-odexed.
jubeh: Thanks for the info. I had no idea and have informed JF previously here: http://jf.andblogs.net/2009/11/08/smalibaksmali-v1-0/ (see comments)
VillainTheme System 0.3.5 for the TF101
http://www.villainrom.co.uk/forum/showthread.php/4971-About-VillainTheme-System
pulser_g2 said:
OK, so I think it's time to explain what this is about. It's born from the idea that came about on IRC, for a way to make a theme once for a ROM, rather than have to adjust it for each incremental update for a given ROM or ROMs.
As a user, you don't need to know much - just flash this zip like a regular zip, and you'll get your theme running. But you should be able to apply themes to any device, ROM, and version of the ROM, without it causing adverse effects. That means less time spent by themers making the original theme, and less time spent modifying it constantly for new versions of ROMs.
As a themer? Well, here is the information:
Inside the zip, in the vrtheme folder, you can create a folder called "system" and "data". The former is required, the latter is not required unless you wanted to theme a data app (strongly not recommended, unless you know the app will be there on every phone)
Inside the system or data folder, create a subfolder "app", and in these, make subfolders named EXACTLY after the APK name. For example, to theme the Browser, you need a folder called "Browser.apk". It must be correctly capitalised.
Within there, place the files you require for your theme, in the relevant locations. So most PNGs will be in res/drawable-hdpi/. You can put in xml files too (those which are not in resources.arsc), if you compile them via apktool, and extract them with a zip tool.
In the vrtheme folder, as well as system and data folder, one called "raw" can exist. Within here, you can place files to be copied verbatim to the ROM (for example, modified JAR files). Note that using this may make the theme device dependent (read WILL make it device dependent)
And that's about it.
Features
Will modify APKs in a ROM, without changing signatures, and can be used on any ROM where the filenames of themed files is the same.
Should not need updated between versions of a ROM
Zipaligns all APKs before installation
Stores a backup of all files being modified in /cache/vrtheme-backup/
Requires no coding abilities or editing of files - just drag and drop
Can copy "raw" files, though at risk of not working on other devices (well, let's face it, it won't work on likely a slightly different ROM, so this feature is not recommended or encouraged)
Credits
Doctorcete for the original idea in a discussion on IRC
Stericson for the original idea of metamorph. While totally different, it's a shared goal to separate themes from ROMs
Matt from the Metamorph team, for the zip binary compiled for Android
Seshy, for testing
EULA
Click to expand...
Click to collapse
Nothing evil or complicated - just a few little things. You should not charge for access to this code. That includes a zip containing this, or a derivative of it. So please don't sell themes using it. That's not particularly cool. If you want to use it commercially for some reason, get in touch with us.
If you spot a bug or error, and find a fix, please reply in this thread and let us know, or post the changes you made. If you're going to distribute the changed version, it is expected that you share the change made by contacting us, or posting it here.
Finally, don't be a douche - don't rip this off or call it your own, and leave all headers and comments identifying the origin of the code in place. Don't rename this to match your ROM or "team" name - it's not cool, and it's not yours to go and adjust. I chose to make this a readable "plain" script, but can easily obfuscate and encrypt it if you want to be a douche.
Copyright VillainROM (2011). All rights reserved
Click to expand...
Click to collapse
Now this project was created around the SGS2, and as such it did not work on the TF101 at first, however me and Pulser have spent the day looking for solutions and finally got it working for the TF101.
IMPORTANT: DO NOT USE THE SGS2 TEMPLATE FROM THE VILLAINROM WEBSITE.
Download:
0.3.6 experimental
Clean template without theme included: http://www.mediafire.com/?5bs9srz88i4wdq4
Asus Eee Pad TF101 VRTheme template: http://www.mediafire.com/?5gyr1g0xgd05t70
Note: for now the template is my windows phone 7 theme since it shows you where everything goes really well
If you find any issues or bugs PM me with as much info as you can and if possible a recovery log (found in /cache/recovery/) so I can try and find a solution to your problem.
Changelog
0.3.5
Fixed ASCII art in updater script.
Minor clean up of installtheme.sh
Added preview.png to template.
0.3.3
Modified installtheme.sh as it was giving possible problems.
0.3.2
Fixed a problem with raw folder copying. Put contents of /raw in /system now on the root of the .zip
Fixed some status 0 errors.
Currently known bugs:
You may have issues trying to flash framework files and app files in the same .zip (code 0 error).
Temporary solution: Flash the framework folder and the app folder in seperate .zip files.
hello,
is that you can see screen pls ?
And this theme is compatible with any rom ?
wallah said:
hello,
is that you can see screen pls ?
And this theme is compatible with any rom ?
Click to expand...
Click to collapse
If you had taken 3 seconds to read the post you would know it's not a theme.
This is for themers only.
yes I have read and I have not really understood ...
sorry I disturb
For any themers who want a better example of how it works, I just updated my own theme to use this method:
http://forum.xda-developers.com/showthread.php?t=1120525
Hey seshmaru,
This is definitely a great method! As soon as I get a chance, I will experiment with adapting PCB Blue to use the VillainROM theming method (with leaving all credit intact of course )
If someone wants to uninstall any themes applied this way, what would be the best method though? Just reflash their ROM?...(is what I'm thinking).
Thanks for working on this with the Villain Team, and if there's anything I can do (help/test/etc.), please don't hesitate to PM me.
Thanks again, and cheers for now!
scar45 said:
Hey seshmaru,
This is definitely a great method! As soon as I get a chance, I will experiment with adapting PCB Blue to use the VillainROM theming method (with leaving all credit intact of course )
If someone wants to uninstall any themes applied this way, what would be the best method though? Just reflash their ROM?...(is what I'm thinking).
Thanks for working on this with the Villain Team, and if there's anything I can do (help/test/etc.), please don't hesitate to PM me.
Thanks again, and cheers for now!
Click to expand...
Click to collapse
Well seeing as the current .zip makes a backup of the original files, in the future there will probably be a script made to restore the back up.
Till then the easiest way is to just reflash your ROM without a wipe or to reflash whatever theme you had before.
If you want to help with testing (constantly fixing things since pulser is away so it's my task to keep the SGS2 template and TF101 template as identical as possible) or have any questions you can pop by the VillainROM IRC since I'm generally in there.
Hmm... I can't quite figure out why, but it is not working right for me.. My framework-res.apk file is exactly the same after flashing....
I managed to do some debugging, and i found out that the file file is actually created, but it doesn't copy it over for some reason...
within the VRTheme folder (which i prevented from being deleted so i could check out the contents) the framework-res.apk file is in apply/system/framework/framework-res.apk...
So i tried editing the install script, all the way down at the bottom, and i changed the code from from cd /cache/vrtheme/apply/system/framework/aligned/ to cd /cache/vrtheme/apply/system/framework/ and it worked!
All i can guess is that the file isn't getting aligned for some reason, so that folder/file is never created, but the script is still calling for it...
Can you please let me know if my fix is acceptable, or if there is something off with it that can be fixed and would allow it to be aligned therefore creating the folder and the file?
-trailblazer101
I just want to confirm this. I made some xml edits for the framework, finsky, and gmail were I change the color of the text. Those are in the values folder in the colors.xml file. After you compile the apk you cannot see that folder so I am guessing that you cannot use this to flash that xml correct?
went toflash the theme i get error 0
MetAloid said:
went toflash the theme i get error 0
Click to expand...
Click to collapse
just try the new version now i get error 6
MetAloid said:
just try the new version now i get error 6
Click to expand...
Click to collapse
I got error 6 as well.
Error 6
I'm gettting same error ^ as cescribed by others.
I have been wanting to get into the Honeycomb theme arena and this looks like a good place to start, thanks for your work and I hope I can figure it out. Would it be ok to drop by IRC if I have any questions?
Hi all, just looking for confirmation that the VillainTheme flasher is able to apply .XML files (specifically in framework-res/drawable)?
Thanks in advance!
It should be able to, although it's had some issues at times.
Anyone getting status 6, try this new updated template: http://www.mediafire.com/?5bs9srz88i4wdq4
seshmaru said:
Anyone getting status 6, try this new updated template: http://www.mediafire.com/?5bs9srz88i4wdq4
Click to expand...
Click to collapse
That 0.3.6 template works for me
Regards, folgui.
I'm having a problem with Recovery giving "E:Error in... / Error 0" with my theme for the TF101 below.
Can someone please test it and report their findings? Note that you should do a Nandroid backup first!
Thanks in advance...
** EDIT ** - Found the problem and fixed it...sorry for the post!
1st post: updates by others
2nd post: updates by me
I present you my package of recent updates for DSIXDA kitchen v0.202
This package is for Windows, Linux and Mac.
To use the updates, replace kitchen files with files from package.
Dk202u23092012; this package includes:
* added support for endeavoru credits to theintelligent
* updated wireless tether to v3.2-beta2 credits to harald
* updated busybox to v1.20.2 credits to Denys Vlasenko
* updated Superuser to v3.2-RC3 credits to ChainsDD
* updated zipalign to vR20.0.3 credits to Google
* updated apps2sd to v2.7.5.3 Beta 04 credits to tkirton
* updated unyaffs to v0.9.4 credits to ehlers
Click to expand...
Click to collapse
I take NO credits for these tools, only for sharing my package with the community, happy cooking!
Here you'll find experimental mods made by me. Please test it and give me some feedback.
NEW em2Dk202u24092012; this package includes:
* NEW added option to root your rom with chainfire's SuperSU v0.96 NEW
* removed option "old" incl. Superuser.apk and su binary
Click to expand...
Click to collapse
To use this update, replace su_files folder and do_root file from your kitchen with su_files folder and do_root file from package.
Plz test and report me back, enjoy!
emDk202u24092012+; this package includes:
* added support for primo aka HTC One V
* added support for ville aka HTC One S
Click to expand...
Click to collapse
To use the updates, add files from package in kitchen folder.
Remember these updates are experimental! I don't own these devices so can't test them myself!
I hope this helps you !:angel:
updated post 2, enjoy!
I can use this to build for the Samsung galaxy tab 2 7.0
Sent from my SGH-T679 using Xparent Blue Tapatalk 2
hatememarkz said:
I can use this to build for the Samsung galaxy tab 2 7.0
Sent from my SGH-T679 using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
Samsung Galaxy Tab 2.7.0 not supported yet...
updated 2nd post, added a great new experimental option! plz test it and give me feedback.
i dont know what im doing wrong here.. im getting this error
E: Error in /sdcard/Arquivo/roms/MIUI_X/MIUI_X_2.9.21_RC1.zip
(Status 6)
Installation aborted.
ill descrive my steps
1. Copyed endeavoru (without .txt extension) to tools/edify_defs/
2. Extracted ROM and converted updater-script to update-script like kitchen recomends
3. Made my changes
4. Builded ROM in interactive mode (1) in kitchen
5. Kitchen converted automaticaly to updater-script
6. Selected option "Proceed: updater-script and update-binary will be moved to the ZIP file.."
7. sign, copy to phone, etc
and when i go to flash it, i got that error ...
im using your kitchen...
this in HTC ONE X (enderavou)
any clue about this ?
3. Made my changes
Click to expand...
Click to collapse
What changes? tell me in detail plz
im using your kitchen...
Click to expand...
Click to collapse
not mine, kitchen owner is DSIXDA
l3inky said:
What changes? tell me in detail plz
not mine, kitchen owner is DSIXDA
Click to expand...
Click to collapse
nothing special ... deleted some apks in system/app (bloatware) and added some (gaaps) and edited build.prop with notepad++ just to change timezone
sorry .. your kitchen mod
im going now to build and untouched rom .. just to see if the problem is from my changes .. but i didnt changed anything special .. so i supose thats not the problem .. but just in case.. im going to test it ..
im going to extract the rom "miuiportugal_OneX_2.9.21_Signed.zip" and build it with kitchen defaults
convert updater like it recomends on extract..
and convert again to updater in building like it recommends
just to see if the problem is in the kitchen or my changes
---------- Post added at 07:48 PM ---------- Previous post was at 07:24 PM ----------
same problem .. same error ...
didnt change anything this time ...
just extracted rom and build it again with kitchen defaults
dont understand .. kitchen recognizes the device when converting scripts ...
maybe because the source rom its MIUI ? i tryed miui eng / pt / ch / rd .. and same problem ..
maybe java path invalid (\Java\jre7\bin) dont know if kitchen uses java ..
maybe cygwin version ?
lol .. what a strange thing ... do i need to change more files in kitchen ? i just downloaded the last kitchen release and applyed your mod ...
btw i founded this on changelog
Version 0.190 (March 26, 2012):
Change end-of-line characters in update(r)-script to proper format when building ROM. This gets done in case a noob modified the file with non-Unix compliant editor. Prevents 'Status 6' error when flashing ROM in custom recovery.
but it doesnt make sense because im not doing edits and i dont have < 0.190 kitchen
ruizit0 said:
nothing special ... deleted some apks in system/app (bloatware) and added some (gaaps) and edited build.prop with notepad++ just to change timezone
Click to expand...
Click to collapse
You don't need the kitchen for these changes mate!
+ I don't know what goes wrong with you, aosp and kitchen not a good match i guess
Mayb you can contact dsixda for your problem but again, if these are the only changes you wanna make you don't need the kitchen!
l3inky said:
You don't need the kitchen for these changes mate!
+ I don't know what goes wrong with you, aosp and kitchen not a good match i guess
Mayb you can contact dsixda for your problem but again, if these are the only changes you wanna make you don't need the kitchen!
Click to expand...
Click to collapse
yeah i know .... but i dont plan to make only that changes
it was only to test the kitchen ... i cant contact dsixda he stopped development of the kitchen :\
dont know what to do .. do you have an HOX ? i need to find someone with an hox to zip me the kitchen folder and send me just to see if it works ... or if its from my computer setup ...
i installed everything with a tutorial i saw here on forum .. maybe it wasnt the best tutorial to setting up the kitchen .. dont know :| damn
just in case someone can give me a clue...
here's some info and logs .. i think kitchen is converting wrong the updater-script... but why .. i dont know.. differente HOX versions ?
the part of flashing
Code:
-- Installing: /sdcard/Arquivo/roms/MIUI_X/endeavoru_signed_092512_200944.zip
Finding update package...
I:Update location: /sdcard/Arquivo/roms/MIUI_X/endeavoru_signed_092512_200944.zip
Opening update package...
Installing update...
line 4 col 20: syntax error, unexpected STRING, expecting $end
1 parse errors
E:Error in /sdcard/Arquivo/roms/MIUI_X/endeavoru_signed_092512_200944.zip
(Status 6)
Installation aborted.
and here's the full log
https://www.dropbox.com/s/f5b97a4tt2rlbqu/recovery.log
and here's the updater-script created by the kitchen
https://www.dropbox.com/s/7h8wl5a5vizen08/updater-script
For now use this workaround: when rom is builded replace meta inf folder with original, when im home i,ll take a look at it.
Sent from my HTC One X using xda app-developers app
l3inky said:
For now use this workaround: when rom is builded replace meta inf folder with original, when im home i,ll take a look at it.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
thanks l3inky!
detailed problem in here if you can check logs and specs etc
i didnt mentioned your mod in there to not cause more confusion .. but using your mod or not, the problem is the same, so the problem is not from your mod
http://forum.xda-developers.com/showthread.php?t=1906605
thanks again
Can u plz send me this: original updater-script, converted update-script and final updater-script.
Problem solved thanks to "backfromthestorm" hint!!
The problem is the Kitchen update to updater conversion.
The kitchen doesnt make correctly the conversion.
So the solution is:
not give any script to kitchen for conversion, remove META-INF folder from original zip and let kitchen create a fresh updater..
It doesn't fix the converting problem does it, also very interesting you prefer removing meta inf en make a new one then just changing 2 lines in updater script, 2 workarounds in my opinion, anyway can u send me those 3 files i asked for cause i wanna fix this problem.
Sent from my HTC One X using xda app-developers app
l3inky said:
It doesn't fix the converting problem does it, also very interesting you prefer removing meta inf en make a new one then just changing 2 lines in updater script, 2 workarounds in my opinion, anyway can u send me those 3 files i asked for cause i wanna fix this problem.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
you are right .. but i prefer to create a new one because its less work, i have to remove the ui_print and other symlinks, so for me its easyer create a new one.
but the perfect is if the kitchen can make correctly the conversion ...
here it is what you asked
https://www.dropbox.com/s/7fd3kboz0htiur7/updaters.zip
it will be great if you can fix that.. if you need something from me just ask!
thanks
made another test .. but this time with other rom...
the kitchen converts the updater bad again but with other errors ..
this time it add spaces to lines
here is the files from the another test ...
https://www.dropbox.com/s/vim2rpgrgmij3j9/updaters_2.zip
the kitchen is all messed up when converting updater .. i think the best is to stick to the original updater dont make conversion and make manual changes on the end ..
and hope DSIXDA gets back to kitchen development, or maybe someone makes another kitchen and give support to it :\
EDIT: found some bugs when removing META-INF folder from original zip and let kitchen create updater by his own .. for example in MIUI rom some functions stop working ... like theme applying etc... i think kitchen jumps something maybe permissions .. when creating updater
for now, and for me, the best option is to let META-INF in original zip, and when extrating rom when kitchen asks to convert updater to update, dont convert, and after edit original updater mannualy and make the changes
ruizit0 said:
made another test .. but this time with other rom...
the kitchen converts the updater bad again but with other errors ..
this time it add spaces to lines
here is the files from the another test ...
https://www.dropbox.com/s/vim2rpgrgmij3j9/updaters_2.zip
the kitchen is all messed up when converting updater .. i think the best is to stick to the original updater dont make conversion and make manual changes on the end ..
and hope DSIXDA gets back to kitchen development, or maybe someone makes another kitchen and give support to it :\
EDIT: found some bugs when removing META-INF folder from original zip and let kitchen create updater by his own .. for example in MIUI rom some functions stop working ... like theme applying etc... i think kitchen jumps something maybe permissions .. when creating updater
for now, and for me, the best option is to let META-INF in original zip, and when extrating rom when kitchen asks to convert updater to update, dont convert, and after edit original updater mannualy and make the changes
Click to expand...
Click to collapse
You probably have a problem with mount points & update binary. Make sure your device is supported by kitchen else manually create edify_defs for your device or Replace update binary in kitchen cooked meta inf folder with the one from original rom and edit kitchen updater script - change the lines with mount(...........) in new updater script to look exactly like the one in original rom's updater script. You can search xda forum for more info on edify language used in updater scripts. Most of changes you need make in updater sript will be within first 5lines. You can pm me if problem but also post response here
Sent from my GT-B5512 using Tapatalk 2
Hello all!
I am looking to automate a couple things I do when I flash a new build of Cyanogen mod. Namely my couple edits of the build.prop.
Yes I do understand that some will disagree with me editing the build.prop, and some may say it's dangerous. I'm not here to discuss those matters.
What I do want to discuss is that I want to create a flashable zip that contains an updater script that will essentially add my changes for me before I even start Cyanogen mod and save me time and effort. I am very unfamiliar with such things and was hoping someone could give me a hand and point me in the right direction. That way I can do my own thing and ask less questions in the future.
P.S. Do note I do prefer to be taught than just handed a script with everything I want in it.
Zadeis said:
Hello all!
I am looking to automate a couple things I do when I flash a new build of Cyanogen mod. Namely my couple edits of the build.prop.
Yes I do understand that some will disagree with me editing the build.prop, and some may say it's dangerous. I'm not here to discuss those matters.
What I do want to discuss is that I want to create a flashable zip that contains an updater script that will essentially add my changes for me before I even start Cyanogen mod and save me time and effort. I am very unfamiliar with such things and was hoping someone could give me a hand and point me in the right direction. That way I can do my own thing and ask less questions in the future.
P.S. Do note I do prefer to be taught than just handed a script with everything I want in it.
Click to expand...
Click to collapse
Same here my friend same here.
But what i do to my ROMs when i have edits i wanna make is i extract the build.prop from the zip and edit what i want using Notepad++ then drag the build.prop back to the 7zip window to add it back to the zip and i flash. Simple as that
Now, if you really wanna get fancy, you could create an sh script that will read the build.prop AFTER flashing the ROM. It will read the build.prop, then change the things you want for you.. I dont really recommend this method as its not very simple and quite frankly im too lazy to create the sh script for myself. But i do believe it is possible.
elesbb said:
Same here my friend same here.
But what i do to my ROMs when i have edits i wanna make is i extract the build.prop from the zip and edit what i want using Notepad++ then drag the build.prop back to the 7zip window to add it back to the zip and i flash. Simple as that
Now, if you really wanna get fancy, you could create an sh script that will read the build.prop AFTER flashing the ROM. It will read the build.prop, then change the things you want for you.. I dont really recommend this method as its not very simple and quite frankly im too lazy to create the sh script for myself. But i do believe it is possible.
Click to expand...
Click to collapse
Interesting... I have tried the modify then drop the build.prop back into the zip, using 7-zip even, and it refuses to do so. hence me trying to do it in the manner of an updater script.
Zadeis said:
Interesting... I have tried the modify then drop the build.prop back into the zip, using 7-zip even, and it refuses to do so. hence me trying to do it in the manner of an updater script.
Click to expand...
Click to collapse
You could always make a second zip containing your modded build.prop. I remember having to do this with one of my edits on my S2 cause the ROM wouldnt set itself up with the changed Build.prop.
elesbb said:
You could always make a second zip containing your modded build.prop. I remember having to do this with one of my edits on my S2 cause the ROM wouldnt set itself up with the changed Build.prop.
Click to expand...
Click to collapse
Hmm maybe. I'll try using winrar to see if it makes any difference using the same drag and drop new build.prop method just to satisfy my curiosity.
Could it be an MD5 issue since you are "modifying" the zip?
Still Charged Up
Reilly1812 said:
Could it be an MD5 issue since you are "modifying" the zip?
Still Charged Up
Click to expand...
Click to collapse
Actually winrar worked. 7-zip can delete files from a CM archive but not add for some reason when winrar can do both. Not sure why but I still prefer 7-zip myself for everything else.
Though while this method does work I still wouldn't mind knowing how to add my changes via build.prop to streamline the entire process of updating CM.
Zadeis said:
Actually winrar worked. 7-zip can delete files from a CM archive but not add for some reason when winrar can do both. Not sure why but I still prefer 7-zip myself for everything else.
Though while this method does work I still wouldn't mind knowing how to add my changes via build.prop to streamline the entire process of updating CM.
Click to expand...
Click to collapse
7zip works for me without any issues..
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
I am in the mid of Making my own ROM and it's almost done. I want to change the icon of the toggle switch button just below the status bar. I also like to change the pop up message when I press shutdown and reboot. How can I do that ? Pls reply fast. I know decompile using APK but I don't know which file to decompile and where can I find the file to edit . Can anyone please tell me and don't ignore my post ?
leezhijiang said:
I am in the mid of Making my own ROM and it's almost done. I want to change the icon of the toggle switch button just below the status bar. I also like to change the pop up message when I press shutdown and reboot. How can I do that ? Pls reply fast. I know decompile using APK but I don't know which file to decompile and where can I find the file to edit . Can anyone please tell me and don't ignore my post ?
Click to expand...
Click to collapse
If you are making your own rom (and not being a winzip wizard) them you should know that it is controled by the framework files.
zelendel said:
If you are making your own rom (and not being a winzip wizard) them you should know that it is controled by the framework files.
Click to expand...
Click to collapse
What do you mean ? I am a newbie actually. I made my rom based on a custom rom and follow the guide on this forum.
See the attachment.
How can I change the MindCr ROM to my own text ? I really don't know where to find it. What I know is how to edit those png files
leezhijiang said:
What do you mean ? I am a newbie actually. I made my rom based on a custom rom and follow the guide on this forum.
See the attachment.
How can I change the MindCr ROM to my own text ? I really don't know where to find it. What I know is how to edit those png files
Click to expand...
Click to collapse
You will have to decompile the jar files and edit the java code. As I stated in your other thread take some time and learn to make a rom properly. Mainly when you will be required to follow all the same rules that the devs are. New to this or not. Take some time and learn linux and then learn to build a rom the proper way.
I already have the basic knowledge. How am going to learn if I don't know. Asking is a way of learning too! I already good in decompiling and compiling and script editing. The problem is don't know which xml file should I edit. I can do basic programming. I did found out the directory of those icons but I don't know how to change the title text of the pop up menu that appear after I press the "restart" and "shutdown" button.
I almost finish my ROM already just left theming and that part only. For your information, I actually modified quite a number of apk files successfully based on Nero Young tutorial.
leezhijiang said:
I already have the basic knowledge. How am going to learn if I don't know. Asking is a way of learning too! I already good in decompiling and compiling and script editing. The problem is don't know which xml file should I edit. I can do basic programming. I did found out the directory of those icons but I don't know how to change the title text of the pop up menu that appear after I press the "restart" and "shutdown" button.
I almost finish my ROM already just left theming and that part only. For your information, I actually modified quite a number of apk files successfully based on Nero Young tutorial.
Click to expand...
Click to collapse
You learn by spending a few days searching. Trust me your not the first to ask this question. There are tons of TUT all over the site to help you learn how to make a rom. What you are missing to understand is that you have not really given any info like what style rom, for what device? These things matter as depending on device and rom then it is in different places. So I could tell you were it is in my rom (which i did) but it may not be there in your rom.