Database Users

{TOOL}MetaMorph Builder v3-Linux Only[8-5]

This could be considered part of the development forum or the apps and theme forum depending on how you look at it. if you have an issue, just click the report button and request that it be moved. no need to flame and troll and post that you reported it, just do it and move on.
Lots of people have asked me how to put together a theme control file, and its actually VERY easy but this tool makes it even easier.
this is an example of a theme control file created by this tool
Test-Theme.xml
Code:
<themename>Test-theme</themename>
<author>tater-salad</author>
<phone>Android Phone Codename Hulk</phone>
<rom>CM 8</rom>
<item>Phone.apk</item>
<path>/system/app<path>
<item>framework-res.apk</item>
<path>/system/framework</path>
<description>Requires reboot</description>
<item>FM-Reciever.apk</item>
<path>/data/app<path>
<item>My-custom-app.apk</item>
<path>/data/app<path>
run the mm-builder script and follow the on screen directions. you will of course need to put the correct replacement files in their respective directories, but this script will make all the right folders and set up your theme.xml for you. Bash scrip means linux only. This is also a super easy script, so i may get a batch version soon.
You can extract this file to any directory
All thanks to Stericson. W/O him we wouldnt have a metamorph app to begin with
######################################################################################################
v2
includes these additions
Code:
mkdir $app
mkdir $app/res
mkdir $app/res/drawable
mkdir $app/res/drawable-mdpi
mkdir $app/res/drawable-land-mdpi
mkdir $app/res/drawable-port-mdpi
these are the commonly used directories when it comes to theming. now all the sub-folders should be set up right.

I think this tool will be very helpful for newer themers and the like, looking forward to a windows adaptation.
also, what does it matter if ban_dover was andrizoid, seems to me hes not doing any harm here now, just trying to help people out, so give a guy a chance to rectify himself before you all start the flamethrowers

snyluc13 said:
I think this tool will be very helpful for newer themers and the like, looking forward to a windows adaptation.
also, what does it matter if ban_dover was andrizoid, seems to me hes not doing any harm here now, just trying to help people out, so give a guy a chance to rectify himself before you all start the flamethrowers
Click to expand...
Click to collapse
windows version is certainly viable, but batch is SO alien coming from bash. there isnt even an ls command
im going to have to play around and get a feel for batch before i get to work on it.

v3 is up. ive put together working metamorph themes using v3, so its been pretty well tested.

How about some constructive use of this thread?
ban_dover,
I've got a question. I read through Stericson's announcement post on XDA, and also the project page, and he mentions limitations due to signing checks of market apps.
Does it actually re-sign the .apk with the test key that all the devs use, or does it merely re-zip the .apk so that the manifest and keys are broken (won't pass a jarsigner -verify test)?
If it is the 2nd alternative, I guess that would means that Android does not check "non-market app" installs for valid signatures? Or that it doesn't check system apps but does check market apps?
The reason this piques my interest is that I noticed one of the devs recently released a ROM which had all its apps de-odexed and re-signed with the test key. (Can't remember which ROM, perhaps an xtr* ROM?)
Anyone else that knows how this goes is welcome to answer as well.
bftb0

Im going to lock this thread if the flame war doesn't stop
Play nice
Edit: Thread re-opened, ban_dover and I discussed and hopefully we will not have any more issues.
Thanks
Captainkrtek

bftb0 said:
How about some constructive use of this thread?
ban_dover,
I've got a question. I read through Stericson's announcement post on XDA, and also the project page, and he mentions limitations due to signing checks of market apps.
Does it actually re-sign the .apk with the test key that all the devs use, or does it merely re-zip the .apk so that the manifest and keys are broken (won't pass a jarsigner -verify test)?
If it is the 2nd alternative, I guess that would means that Android does not check "non-market app" installs for valid signatures? Or that it doesn't check system apps but does check market apps?
The reason this piques my interest is that I noticed one of the devs recently released a ROM which had all its apps de-odexed and re-signed with the test key. (Can't remember which ROM, perhaps an xtr* ROM?)
Anyone else that knows how this goes is welcome to answer as well.
bftb0
Click to expand...
Click to collapse
to be honest im not sure. but i can say that the rom your talking about isnt going to have any issues with anything because of the re-signing.

so the those who have downloaded it, what do you think?
ive tested it by putting together a few simple MMs, and it worked fne for me. have any of you ran into any issues?

[Q] Need help reinstalling stock Twitter app

Okay, I rooted my N1 with Universal Androot and removed the stock Froyo Twitter app without backing it up. (Shame on me.) Now, I can't update to 2.2.1 because of it (a status 7 error complaining about not finding /system/app/Twitter.apk)
I have, at the advice of some other forum posts I've read, installed Twitter from Android Market and backed it up to the sd. Renamed it Twitter.apk and used the Terminal Emulator to copy it to /system/app. That worked and the file is there, but the update still will not apply. Do I also need a .odex file? Is there any way to update at this point?
Any help would be super appreciated. THANKS!

if this is the new twitter app would you be kindly enough to share it..lol
Sent from my Nexus One

grab it from an older update like from frf91 update.. then do adb push /system/app
if you cant do that...
put the twitter app in sdcard then go to terminal and do
cp /sdcard/twitter /system/app
reboot then apply it.. i had trouble with amazon and i did it that way and it worked well

ilostchild said:
put the twitter app in sdcard then go to terminal and do
cp /sdcard/twitter /system/app
reboot then apply it.. i had trouble with amazon and i did it that way and it worked well
Click to expand...
Click to collapse
That's exactly what I did. It didn't work.
I'd love to pull the app from a FRF91 build but I have no idea how that's done.

Flash a GAPPS update (try the on listed with CM6)
Sent from my Nexus One using XDA App

danger-rat said:
Flash a GAPPS update (try the on listed with CM6)
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
It looks as though I can't flash the GAPPS without unlocking the bootloader and installing a new recovery, correct? I'm really not that motivated if that's the case. I appreciate the information.

OK, just download the GAPPS, then use something like estrongs file manager to unzip to a folder of choice (with estrongs, longpress and select extract).
The Twitter apk will be in the extract folder/system/app. Just click the apk to install...
Sent from my Nexus One using XDA App

BTW, if you have root, you may as well install a custom recovery (without touching the bootloader).
Easy way with ROM Manager (has Clockworkmod and Amon-Ra), or use adb if you wanna learn something...
Sent from my Nexus One using XDA App

Thanks for the tips. I'll check it out tomorrow when I can make a data transfer. I am doubtful that installing from the zip will solve much since I already loaded the app and its already in the system folder.
could someone verify whether or not the Twitter app has a corresponding odex file that I might need?

I ran into the same problem when I removed Amazon Mp3, but I was impatient so I ended up reflashing the stock rom and then updating.

There is a thread that has all n1 updates look for it and download froyo fr91 update then unzip it go to system app and look for twitter apk then put in sdcard and do commands again .. I tried to do with market twitter and it failed so I did it the way I'm explained andnworkd

[SOLVED]
ilostchild said:
There is a thread that has all n1 updates look for it and download froyo fr91 update then unzip it go to system app and look for twitter apk then put in sdcard and do commands again .. I tried to do with market twitter and it failed so I did it the way I'm explained andnworkd
Click to expand...
Click to collapse
You sir, have saved my life. I swear I used that same exact Twitter.apk but I must not have. I used 3 different apks all with the same result but the one in the zip I found somewhere in this forum worked perfectly. I appreciate all the help and feel like such a 'tard for not trying something so seemingly simple earlier.

68pontiac said:
You sir, have saved my life. I swear I used that same exact Twitter.apk but I must not have. I used 3 different apks all with the same result but the one in the zip I found somewhere in this forum worked perfectly. I appreciate all the help and feel like such a 'tard for not trying something so seemingly simple earlier.
Click to expand...
Click to collapse
No problem man.. glad you got it working.. now reroot the phone and back up all the apps from then phone.. doin adb pull /system/app

[STICKY][Patch][Rom]Malware Exploit for all pre-Gingerbread devices

Who is affected? All devices pre-gingerbread
Who should act? Users and developers using pre-gingerbread roms
How do I fix? Flash attached .zip at the bottom of this post
What if I think I was infected? Completely wipe your device, format sdard, go back to stock and re-apply rom, then flash the attached .zip (before installing any apps)
Why should I care? read below...
http://www.androidpolice.com/2011/0...your-phone-steal-your-data-and-open-backdoor/
Flash this with ClockWorkMod.... this is for any Pre Gingerbread ROM.... ie TNT anything, VEGAn 5.1.1 and below, Zpad anything, GAdam anything.
This is not necessary for any ROMS based off Gingerbread AOSP or CM7. Including VEGAn-TAB Experimentals.
Be Safe.
Even More Details here: http://www.androidpolice.com/2011/0...-android-nightmare-and-weve-got-more-details/

I checked out the zip and it just adds a blank text file (0 bytes) called profile to the /system/bin folder. So I am not sure what the fix is?
**EDIT** Nevermind it is a dummy file meant to prevent the virus. Thanks to the OP for providing this.

http://www.androidpolice.com/2011/0...your-phone-steal-your-data-and-open-backdoor/
Nasty stuff. I would say this patch is high priority and I'm already going through my own ROMs to add it in.

http://forum.xda-developers.com/showthread.php?t=977154
Link above has info on creating the file manually.
Jim

fyi -
http://www.pcworld.com/article/221213/keep_malware_off_your_android_phone_5_quick_tips.html
Lookout mobile security . In case you cannot find it via the market.
http://www.getjar.com/Lookout-Mobile-Security-with-Antivirus
Edit. I just installed the lookout app to scan my tab, everything was fine and then, i un-installed it since it was running on the background and taking 10% of the cpu..
Anyways, a nice app that can be used to do a quick scan..

I don't have a stock gtab but I'll ask anyways... how can our stock rom users be protected? Is there an alternate method?
Edit just saw the manual process. Im guess that's the way to go.

xmr405o said:
I don't have a stock gtab but I'll ask anyways... how can our stock rom users be protected? Is there an alternate method?
Edit just saw the manual process. Im guess that's the way to go.
Click to expand...
Click to collapse
I'd curious to see what all the vendors are going to do about this. Granted, they could just say that the Market is not there, but regardless the security hole is still there and needs to be plugged up.

Hi,
I hope that this isn't too offtopic, but I was trying to create /system/bin/profile using a term and su, and when i went into root explorer to make /system/bin R/W, root explorer showed the dir as R/W already, and as mounted on /dev/loop9.
Is that normal?
I haven't installed dataloop, at least intentionally, so it seems strange that /system/bin would be mounted there, plus it being R/W by default?
FYI, I use z4root to get temp root. Could that be why /system/bin is R/W?
Then again, that wouldn't explain the /dev/loop9 mount ...
Jim

jimcpl said:
Hi,
I hope that this isn't too offtopic, but I was trying to create /system/bin/profile using a term and su, and when i went into root explorer to make /system/bin R/W, root explorer showed the dir as R/W already, and as mounted on /dev/loop9.
Is that normal?
I haven't installed dataloop, at least intentionally, so it seems strange that /system/bin would be mounted there, plus it being R/W by default?
FYI, I use z4root to get temp root. Could that be why /system/bin is R/W?
Then again, that wouldn't explain the /dev/loop9 mount ...
Jim
Click to expand...
Click to collapse
Hi,
Creating the profile file manually, it wouldn't persist,i.e., it was gone after rebooting, so I installed gojimi's zip usung CWM, and that worked.
I also did a mount w/o getting temp root, and /system/bin is not on /dev/loop9, so I'm guessing that when z4root sets temp root, it might be remounting /system/bin on /dev/loop9 itself.
Jim

You would have to download one of those sketchy apps to really be affected anyways, right? Who would do that?!

Appreciate the patch. This highlights the two problems with android though, google fixed this security issue in 2.2.2, but most carriers still haven't released that update. And the market needs some oversight, not authoritarian apple like, but some.
Sent from my T-Mobile G2 using XDA App

Is it possible to sticky this thread
Mods is it possible to sticky this thread so that it is easily visible.
Thanks

Hello guys. Is there a way to find out if our tablet is infected or not?
I mean if we have installed any of the apps in the list that automatically means that we are infected or not?
If infected what is preferred to do wipe the tablet or go back to stock rom??
Is there any manual for windows 7 noobies users?
Thanks.

Doctor LeVa said:
Hello guys. Is there a way to find out if our tablet is infected or not?
I mean if we have installed any of the apps in the list that automatically means that we are infected or not?
If infected what is preferred to do wipe the tablet or go back to stock rom??
Is there any manual for windows 7 noobies users?
Thanks.
Click to expand...
Click to collapse
Please read the thread completely, it is stated you can download lookout security to run a scan to see if you are infected.

downloading.....see what happens

There is a DroidDreamKiller app that allows you to check to see if you are already infected and install the patch. There is also a beta test app that gives you other information. Just search the market for DroidDreamKiller.

To devs: Thank You
TO Everyone else DO THIS ASAP

How do I flash the zip file after downloading it?
Thanks

Start cwm using volume up while powering on.
Once menu comes up select install zip using vol buttons
Use home to select.
Navigate to where you saved zip file
Select it with home button
Once install complete reboot from cwmod

MODs Please make this a sticky . It is being overlooked.

Shortcut Scripts for Flashing Nightlies/Themes/Etc

DISCLAIMER: These scripts have worked for me without issue. It would behoove you to ensure you have a solid back up to recover from in the event that something goes horribly wrong. These scripts should be considered a WIP. I will edit them and provide information as needed if something does not work as it should. Please feel free to post here or PM me if you have issues and bear with me if they do not work properly for you. END DISCLAIMER
To be honest, I am lazy. I flash CM nightlies and sometimes themes, and I didn't like having to navigate through recovery over and over again to wipe cache and dalvik-cache. So, I decided to write a script that would just do it for me. Then I got even lazier. I found that I had written several scripts and now I was tired of having to flash them all in a certain order. Which is why I wrote one all inclusive script.
Here I will provide you with two separate scripts. The first does just enough and the second does that much and a few more personal tweaks.
The first script is a rather simple one. It formats your /cache partition and deletes /data/dalvik-cache.
Wipe_Cache_Dalvik.zip
Edify version to work with Clockword Mod Recovery
1. Back up your current rom
2. Flash Wipe_Cache_Dalvik.zip
3. Flash your nightly/theme of choice
4. Reboot
The second script is where my personal preferences come into play. This script is meant to be flashed after you install your nightly rom. This script will format /cache, delete /data/davlik-cache, delete certain system apps that I do not personally use, and then copy an edited build.prop into /system so that the DPI is set to 190 immediately after you reboot from installing the nightly rom. This script will more than likely have to be changed to suit your needs. I understand that people will want different DPI settings and would like to retain the use of apps that I do not use.
Wipe_Delete_Copy.zip
1. Edit the script if you so choose. (Directions will be given in the second post)
2. Back up your current rom
3. Flash your nightly
4. Flash Wipe_Delete_Copy.zip
5. Reboot
Many thanks to Omegasun and his BareBone App and Sense Removal Plus Community Tools Thread.
This was the thread that got me started writing scripts. I learned a lot from him. My script would not have been possibl without his.
Many thanks to unCoRrUpTeD and his unCoRrUpTeD Dual Boot V1 Thread. I did a lot of testing for unCoRrUpTeD on his dualboot setup. I learned a lot from him in regard to using updater-scripts and updater-binaries. Without him I would not have been able to write the second script.
A thank you also to Calkulin for his format_all.zip which was another source of inspiration for the first wipe script.
As always a giant thanks to Cyanogen, Team Douche, TeamWin, and the Snap Team. The information and aid that they have provided to me is second to none. Without them I wouldn't know half of what I do now. Their contributions are what make this community great.
Any gratitude that you may feel towards me for these scripts should be directed towards those mentioned above. I wrote these to benefit myself and now feel that I should give them back to you all. I hope they work as described and make flashing a little bit easier on you.

These are rudimentary directions for the time being. I will edit and make them more precise later tonight. Also included a few things for reference. Like I said, it is basic info for now and it will become more detailed and informative.
You will need a text editor to edit any of these scripts. I primarily use Notepad++ on Windows. If you are on a *nix box then I am sure you are more than able to find a text editor that suits your needs.
1. Unzip Wipe_Delete_Copy.zip
2. Navigate to *\META-INF\com\google\android\
3. You will see two files: updater-script and update-binary
4. Open updater-script with your favorite text editor. (In my case, I right click and choose "Edit with Notepad++")
5. Edit Away
6. Save
7. Rezip
For reference, these are the files deleted from /system/app:
ADW Launcher
Browser
Car Home Google
CM Wallpapers
Development
DSP Manager
Email
FM
File Manager
Google Quick Search Box
Genie Widget (News and Weather)
Live Wallpapers
Live Wallpaper Picker
Pro Tips (The CM Widget that appears after a clean install)
Sound Recorder
VoiceDialer
Notice "ADW Launcher." This means you will need Launcher Pro/ADW EX/etc before you flash this. Or you will need to remove this line from the script.
If you don't want to change your DPI settings:
1. Open up the script in your text editor
2. Delete
Code:
ui_print("");
ui_print("");
ui_print("");
ui_print("Copying build.prop to retain proper dpi");
show_progress(0.200000, 5);
package_extract_dir("system", "/system");
3. Save
4. Delete the "system" folder found in the original zip
5. Rezip

This will be very handy. Thank you, sir.

+1 for this when I get to mess around with it after work tomorrow. Great job
swyped from my cyanogenized and gingerbreaded EVO

i have been thinking about making a cache/dalvik wipe script forever, but never got the will. thanks for making my life easier karadore.

I appreciate the thanks. I know the basic script will work just fine. It is very straight forward. The second one is kind of tricky because it uses an updater/binary. I just recently started working with them and had a few issues to begin with. The more feedback you all give me on this the better. Hope they help.

i dont know how to write in edify, but i would like to. if you dont mind whipping up a little tutorial, that would be fantastic so all the peoplez can stop complaining that they get an error after flashing my zips on cwm 3+. it would help me and a lot of others as well.

dkdude36 said:
i dont know how to write in edify, but i would like to. if you dont mind whipping up a little tutorial, that would be fantastic so all the peoplez can stop complaining that they get an error after flashing my zips on cwm 3+. it would help me and a lot of others as well.
Click to expand...
Click to collapse
I may just do that. Would give me a nice little project in the next few days to help me procrastinate from school and work a little more

Anyway to update these to work on CW 3+ recoveries?

sminker said:
Anyway to update these to work on CW 3+ recoveries?
Click to expand...
Click to collapse
The second script should work because it is written in edify. I will update the first one so that it works. Leaving for work now but I should be able to do it all from my phone. Will post up the new version in a few.

sminker said:
Anyway to update these to work on CW 3+ recoveries?
Click to expand...
Click to collapse
Just did a quick edit from my phone. This new zip should work on all CW Recoveries. Let me know if there are more issues. Will update the op once I am off work.
http://db.tt/sBi95OV

Karadorde said:
Just did a quick edit from my phone. This new zip should work on all CW Recoveries. Let me know if there are more issues. Will update the op once I am off work.
http://db.tt/sBi95OV
Click to expand...
Click to collapse
Awesome. Haven't tested yet but thanks for updating.

All I ask is that you let me know if it works or not. No reason why it shouldn't, but the more R&D the better.

are you still planning on giving an edify tutorial? and if not do you have any helpful pages or just all-telling .zips i can look at? thanks a bunch karadorde

Wait you flash first and then wipe caches? I've always done it the other way around. Does it even matter? Guess not...
Sent from my PC36100 using XDA App

matt2053 said:
Wait you flash first and then wipe caches? I've always done it the other way around. Does it even matter? Guess not...
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
You can do it either way. I always used to wipe and then flash.
The reason I am wiping after flashing the nightly is because of the other code in the second script. The second script deletes all of those system apps that I don't use and copies my edited build.prop back into /system. If I flashed the script before the nightly, then those system apps would be reinstalled and I would lose my edited build.prop.

dkdude36 said:
are you still planning on giving an edify tutorial? and if not do you have any helpful pages or just all-telling .zips i can look at? thanks a bunch karadorde
Click to expand...
Click to collapse
I have started putting together the thread. I will be adding to it today. I will dig up some other threads for you as well. Here is a link to the one I just started in Evo General.
http://forum.xda-developers.com/showthread.php?t=994940

nice work.. definitely helps me with flashing nightlies.. i would always have to go and remove most of that stuff.. the only thing i wanted to keep was DSP so i went and simply edited script..
works.

pre-rooted stock 6.2.1 update

See: http://forum.xda-developers.com/showthread.php?t=1402440
Sorry - don't have enough posts to reply directly in the dev tree, but it would seem to me that if all the updates are just zip files, couldn't they be modified to include root? Then the normal update system would handle the installation? You wouldn't need root then.. Just dump it into the "kindleupdates" folder and let it do its thing. It would just install it.
It looks like the install is just running a script.. one of the first things it does is wipe the system folder.. doesn't mean you can't include additional files and copy them in afterwards with the script does it?

AndrewTL said:
See: http://forum.xda-developers.com/showthread.php?t=1402440
Sorry - don't have enough posts to reply directly in the dev tree, but it would seem to me that if all the updates are just zip files, couldn't they be modified to include root? Then the normal update system would handle the installation? You wouldn't need root then.. Just dump it into the "kindleupdates" folder and let it do its thing. It would just install it.
It looks like the install is just running a script.. one of the first things it does is wipe the system folder.. doesn't mean you can't include additional files and copy them in afterwards with the script does it?
Click to expand...
Click to collapse
You need to go through all the lines of code for that and I believe some of them are binary files as well. Possible but will take much time. For now we must wait until someone finds a better solution.
Sent from my Kindle Fire using Tapatalk

signature issues.

6.2.1 experiment?
transfuntioner said:
signature issues.
Click to expand...
Click to collapse
Maybe I don't follow the process.. but I'm guessing no signatures..
not a signed bootloader.. no signatures required...
Get beyond compare and look at the differences between the OTA updates and the zip that Eldarerathis put together.
The ".bin" files are just ".zip" files renamed.
Look at
META-INF/com/google/android/updater-script in the bin files they release.
It is just a script.
And to do the things that it is doing, it has to be getting root permissions while it is running.
I don't know how to recover if it doesn't work, but I half wonder if you were to take the zip that fellow created, change the extension to ".bin" and just dump it into the update folder if the fire would install it for you?
He took out the image files from the script. He's just updating the system tree directly. He doesn't update the bootloader, recovery or backup trees.
For that matter if those contained something nasty, they could probably be pulled from an earlier update.
== cut ===
package_extract_file("recovery.img", "/dev/block/platform/mmci-omap-hs.1/by-name/recovery");
show_progress(0.100000, 10);
package_extract_file("u-boot.bin", "/dev/block/platform/mmci-omap-hs.1/by-name/bootloader");
format("ext4", "EMMC", "/dev/block/platform/mmci-omap-hs.1/by-name/backup");
mount("ext4", "EMMC", "/dev/block/platform/mmci-omap-hs.1/by-name/backup", "/backup");
package_extract_file("backup_userdata.zip", "/backup/backup_userdata.zip");
== cut ===
Please nobody try this idea that doesn't know enough to recover if it doesn't work, because I've not a clue how.
But could someone explain why wouldn't it work?
Worst case the rev might need to be manually edited to bump it one for the script.
Seems like it might be an easy way to get around headaches with OTA updates.

Andrew,
Are you having issues with getting into recovery so that you can test this? The Devolopers have a copy of TWRP 2 working perfectly on the device so you can get a clean backup of the OS before you test.
You sound like you may know what to do to fix the issue and I just want to help you get a good recovery in case it doesn't pan out or for testing.
~enjoy.

Actually I'm just afraid of messing up what I have working now.
I've got TWRP 2 running with the 6.2.1 image.
I'm setting these up as gifts. I spent a good 12 hours yesterday fighting the darn things. Guess I'm getting gun shy. Had a lot of issues with adb. Kudos to the new utility and setting the second ports up. I'm learning.
The OTA install wipes the system directory. It's in the script.
I was tempted to just comment that line out and see if it would leave the rest alone.
If I brick the thing its going to be painful for me to sort out.
I also didn't want to risk losing root. I also haven't tried loading an older OTA version.
At the time, I couldn't ask the fellow that developed the rooted 6.2.1 zip the question in his thread as I didn't have enough posts.
I'm going to be out of pocket for quite some time. I'm not going to have time to spend like this again for at least a few days.
But I was checking the zip he made versus the .bin/.zip files that the OTA releases using beyond compare. I wanted to see what files had actually changed.
That's when I found that script. It is manipulating permissions directly. It has to be running at a root level. I don't see anything like a signature on it, so why couldn't their own update system be used to tweak their own updates to allow for root?