Easy way to install bootanimations - Droid Eris Themes and Apps

###OK I haven't really written a tutorial before so if you catch a mistake please let me know so I can make the changes###
In my method we will be using Android Commander on a PC
Note: This does work on Win7
Android Commander is a free program that allows you to see the root and sd locations of your phone without having to type codes through adb. With this you can drag and drop anything anywhere onto or off of your phone.
Lets begin!
1: Ensure your phone drivers are installed and updated. Also that your phone is plugged in
2: Ensure you have the latest sdk downloaded and installed. You need this for adb. You'll see why in a minute
3. Download and install the attached file at the bottom. This is the Android Commander program.
4. On the first run of Android Commander if you don't know what the options that are shown meen then select the I don't know/ autodetect option.
5. When AC finally opens you will see two windows. On mine the left is Windows Files and the right is Android Files
Personally I don't use the Windows Files side for anything. Its all about your preferance because AC allows you to drag directly from your desktop to the Android Files window.
You should notice on the Android files side all your android "system" folders. locate your original bootanimation like this: Double click "data" then double click "local" Once inside the local folder you will actually be able to see the original bootanimation.zip file. From here select the check box next to it and hit the copy button. By default AC will "copy" the selected file to whatever window is open on the Windows side but you can choose to copy it to your choice. If you don't want to copy it AC allows you to right click it and simply delete it. Your choice. I won't be held responsible if you do delete it and later you decide you want it back!!!
Moving on, once you've done what you want to the original bootanimation.zip you need to locate the new bootanimation of your choice and simply click and drag it to the AC window. When you drop it a window will pop up asking where to put it. Obviously you will want to push it to the android side so if android is on the right then select right window and select ok. Another window will pop up showing the push in progress. I have mine set to close on finish so that window goes away once the file is moved.
Done!
After this you can restart your phone to watch the animation on start up or you can cmd into your phone and actually play the bootanimation to see it working on your phone without restarting!
To use adb to see it without restarting your phone open cmd by winkey+r then type cmd and then hit enter. in cmd navigate to your adb tools like this:
NOTE: I'll use mine as an example.
Code:
C:\Users\Name>cd C:\Android\platform-tools
NOTE: I typed "cd" then my tools location. Important.
Press Enter
Code:
adb remount
Press Enter
Code:
adb shell
Press Enter
Code:
bootanimation
Press Enter. Once you press enter this time the animation will play instantlly on your phone if all has went well. Also if it plays then the install has worked obviously...
To stop the animation press ctrl+c
I know this tut may seem a bit long, but once you do it a couple times I believe you will see this is the easiest and quickest way to change your bootanimation.
If your still confused, watch my Instruction Video file at youtube:
http://www.youtube.com/watch?v=LIeia2HAXXk

Will this work with the Samsung Fascinate? Thank you

i found bootanimation in data\media folder not data\local

Related

Standalone apk installer with adb

I made a little file where u can drag'n'drop files u want to install on ur phone.
No need of any settings.
When your phone is allready "adb ready" you dont need to have anything running.
Just take the apk File and drag on the exe and it will install. thats all.
perhaps i'll add more features soon. i made it for myself, to install the apk's faster after a full-wipe i made.
In Windows7 and Vista, it needs Admin rights (so it asks when starting) and AFTER its done, it gives an error. But it works how it should!
so don't worry
PS: Doubleclicking it won't do anything! Its Drag'n'Drop only!!
Another one by me
copy and paste the following into a file and save it on your desktop as install.bat (or whatever you fancy)
@echo off
adb install %1
pause
Then drag and drop files onto it, or associate apk files with install.bat and double click an apk file and will install to your phone.
htcmagic said:
copy and paste the following into a file and save it on your desktop as install.bat (or whatever you fancy)
@echo off
adb install %1
pause
Then drag and drop files onto it, or associate apk files with install.bat and double click an apk file and will install to your phone.
Click to expand...
Click to collapse
What do u want to say with ur post?
Did i made any question? i think not, so what r u explaining and for WHO??
It's just what i made in my "tool".
Made little bigger better Tool with 5 Options now
if anyone wants it, its at the bottom.
Now u can install apks, uninstall non-stock apks, push and pull files to & from /system/app/ and reboot ur phone.
ahhh, and not it wont make any errors or need for "admin rights" when starting the tool.
Works like a charm and now it has an Sketched android in it ! Yeehaaa
your program (the install part) doesnt really work. it doesnt install. i found that making the batch file was better.
hmm ok, thats weird. for me the new tool works perfekt.
And it IS a batchfile, i just merged the needed files from adb and the .bat file to one exe file. thats all.
do u get any error when trying to install ?
You do drag and drop the file to the exe and choose install apk, right?
Geeze, are people these days so lazy that they can't move their hand off the mouse? Just type the command!!!! Its easy... "adb install {file.apk}".
You know, back in the dark ages of not very long ago, NOBODY had a mouse. Or drag and drop. EVERYTHING was on the keyboard and involved typing commands.
If you guys want and you are running Windows, check out our app. www.androidmanager.net ... we added feature for installing apk-s by double-clicking few days ago

nexus one system png files

hi, i just tried to open a nexus one image to extract all the png files, but failed. does anyone know how or where to get all these files, like banners, battery meters etc.?
thanks in advance!
They are in /system/framework/framework-res.apk. If you adb pull that file onto your PC you should be able to unzip it to get the pngs.
alright, thanks. i'll try this at home - i just dl adb but dont know how to use it. when i doubleclick adb.exe the windows opens and shuts very quickly, probably because i dont have admin rights here.
Alternatively, you could install a file manager like Astro that lets you browse the system folders and just email it to yourself from there. I've done that with a few of the files just because it's convenient and I don't have to dig out the USB cable.
woelv said:
alright, thanks. i'll try this at home - i just dl adb but dont know how to use it. when i doubleclick adb.exe the windows opens and shuts very quickly, probably because i dont have admin rights here.
Click to expand...
Click to collapse
adb is a command line app. Anyway Mike's suggestion of using Astro is an easier way.
my problem is the adb window wont stay open, so i have no chance to write a command line. i need all the files for themeing, so Astro seems inappropriate to me.
The Astro method should work. If you browse to /system/framework with it you should see the framework-res.apk. Long press on it and tap send. It should attach it to a new email which you can send to yourself. You can then unzip it with a program like 7-zip.
This will be easier than using adb as you will need to install the adb usb drivers, connect the phone to your PC and use a DOS prompt.
go start menu for xp and click run and type CMD and you'll get your command line. vista or 7 go to start and right above it type CMD. theres a little more to but that will get you your command line
woelv said:
my problem is the adb window wont stay open, so i have no chance to write a command line. i need all the files for themeing, so Astro seems inappropriate to me.
Click to expand...
Click to collapse
So run it like every other command line app. From the command line. (terminal, console, cmd, etc...)
craz6r said:
go start menu for xp and click run and type CMD and you'll get your command line. vista or 7 go to start and right above it type CMD. theres a little more to but that will get you your command line
Click to expand...
Click to collapse
Clarkster said:
So run it like every other command line app. From the command line. (terminal, console, cmd, etc...)
Click to expand...
Click to collapse
So I am pretty sure if the OP hasn't figured this out over six months later, they have either given up, or figured it out.
Good job bringing things back from the dead.

How To: Keep your old Fascinate clock

Here's a "How to" using nothing but your phone and computer (or Mac):
1.) If you JUST want the clock, you'll need to download onto your Mac or PC either "missing.zip" or "iofthestorm.zip" from here: http://forum.xda-developers.com/showthread.php?t=940456&page=6
2.) Extract the zip file, and open the folder: missing>system>app. Both of these zips have extras bundled into them, so locate Clockpackage.apk. Now, keep this window open.
3.) You'll need a file manager (I like Root Explorer) that allows you to see the "system" (you won't see "" around these files w/in your phone) file. Within in the "system" file, is the "app" file . You'll need to remove the previously bundled clock, but before you do you have to bypass the "system" file's r/o permission. For noobs, r/o = read only. r/w = read/write.
4.) I don't have the link, so click search from w/in the Android Market on your phone and type: mount /system. It'll be the first app that appears on the list. Mount /System is literally the name of the app, so the spacing, etc., is not a typo. Download and install.
5.) When finished with step # 4, fire up your new app, Mount /System, and click the button that says, "Mount r/w."
6.) Remove your old clock from the system/app folder. I first made a copy into my download folder just in case anything went wrong. Once the copy was in a place I could locate again, I went back to system/app folder and deleted the previously bundled clock.
7.) I plugged my phone via usb (settings/applications/development/USB debugging) into my computer. Locate the folder in step #2. Find the clock. Then, drag and drop onto your system/app file.
8.) You're done! Close Root Explorer, and you should see your old Samsung Clock in your app drawer on your phone.
Please note, I'm not a software developer nor am I a hacker. I know only about my device, a Samsung Fascinate, so please don't ask me how to use this mod for other devices. Those who would like to do so would be better off following some of the adb tutorials posted on these forums.

Theming Android 2.1

Okay I'm sure some ppl still run Android 2.1 so I hope this isn't a complete waste of time. I did post this on VR ages ago before their site went tits up and lost everything.
"How to perform "simple" theme changes in 2.1 based roms (tested on VR12).
Firstly, if I can do this, you can.
The only tool (apart from winrar and some photo editing software) you'll really need is AndroidSDK because you need to push/pull things using ADB (android debugging bridge) ->
http://developer.android.com/sdk/index.html
Download and follow setting up instructions.
So now we have to "pull" the files from the phone we want to change.
1) Load command prompt and change the directory to "androidsdk\tools" eg:
C:\Documents and Settings\user>
C:\Documents and Settings\user>cd c:\androidsdk\tools <hit enter>
C:\AndroidSDK\tools>
(If you cannot find command prompt, type into search "cmd" and it should come up.)
2) Ensure your phone is connected via usb and select "charge only".
You can type "adb devices" into the command prompt to check that your phone is connected tho this isn't necessary...useful to check if you're having issues tho.
3) Now to pull the files we want. In this example we are only going to look at pulling "framework-res.apk" as this is the file that contains the images for the status bar, it's icons and the background of the status bar...amongst other things.
Type the following into ADB: adb pull <location of file you want to pull (+ file name)> <location you want the file to be pulled to (+ file name)>
So in the case of pulling framework-res.apk we type:
adb pull /system/framework/framework-res.apk c:\androidapps\framework-res.apk
"/system/framework/framework-res.apk" is the location of the file on the phone and "c:\androidapps\framework-res.apk" is the location the file will be placed on your computer. c:\androidapps is the folder on my c drive where I pull .apk's to (you'll need to make your own folder like this).
4) Locate the file framework-res.apk on your computer (in c:\androidapps if you're using the same folder name as myself) and open it with winrar. Do not extract anything we just want to have a look for some .png's. (.png is a type of image compression that preserves transparency)
Now that you've opened framework-res.apk open the folder named "res" then open the folder named "drawable-mdpi". In here you can find all the .png images I've previously mentioned. Do not close winrar as you will need it.
The .png for the status bar is named "statusbar_background.png" you can drag and drop this to you computer and open it with some image editing software.
I personally recommend GIMP as it is free and very good (http://www.gimp.org/). If you are not confident with image editors you can use http://fotoflexer.com/ for basic editing (clicking on the layers tab on fotoflexer allows you to edit the transparency of the image...remember to save images as .png)
5) Now that you have edited your .png you can drag and drop it back to the res\drawable-mdpi folder hopefully still open in winrar. Close winrar now...it's time to push the edited framework-res.apk back to your phone!
6) Go back to command prompt, if you have removed the usb from your phone at any time, plug it back in and type "adb remount" into command prompt. This remounts the phone for editing.
Now type the following into ADB: adb push <location of file on computer> <location of file on phone>
In this case:
adb push c:\androidapps\framework-res.apk /system/framework/framework-res.apk
and hit enter! This is how it should appear in command promt:
C:\AndroidSDK\tools>adb push c:\androidapps\framework-res.apk /system/framework/framework-res.apk
You phone should restart sense but if it freezes/gets a bit schizy type "adb reboot" into the command prompt to manually reboot the phone.
And it's as simple as that.
You can look through the .png's in res\drawable-mdpi to find more images you might want to edit. The background of the status bar drop down is called "status_bar_background.png" and actual drag down bar is named "status_bar_close_on.9.png".
I think I'll save the explaination of how to edit the bar at the bottom of the screen with the app drawer, phone and + for another time as it requires the knowledge of how to sign .apk's which tho isn't hard is probably quite time consuming for me to explain (due to my very limited knowledge)."
Hope this attempt at 'giving something back' helps someone.
Mark
thanks alot .. Really like it

How to replace Siri with Google Assistant! [GUIDE]

So as you may know, Google released their Assistant SDK a couple days back. Naturally, my first instinct was to replace Siri with Google Assistant on my MacBook Pro.
Here we go...
NOTICE: I am not responsible for any loss of data or damage to your computer. I strongly recommend backing up your device before following this tutorial. Proceed at your own risk.
You are installing the Google Assistant SDK on to your device, and there are limitations and differences between it and Google Home.
This is not elegant by any means and doesn't have a fancy GUI like Siri, so be warned. It's a bodge. But hey, it works
1. Firstly, download and extract the zip file attached to the bottom of this post. I chose to do this in the Downloads folder. If you haven't already installed Python 3, go ahead and install it (the pkg file is located in the '1. Python' folder).
2. Go to the Project Page (console.cloud.google.com/project) of Google's Cloud Platform Console, and click 'Create Project'. Name your project "My Google Assistant". After your project has been created, close the page.
3. Enable the Google Assistant API by following this link (console.developers.google.com/apis/api/embeddedassistant.googleapis.com/overview) and clicking 'Enable'. Make sure your project is selected (the project title is displayed at the top of the page). Click "Create Credentials", and select "Other UI (e.g. Windows, CLI tool)" and "User Data" in the following dropdown boxes. Give your OAuth 2.0 Client ID a name, and hit 'Create Client ID'. Call your Product "My Google Assistant". When you are prompted to download credentials, click 'I'll do this later'. You will be brought to a page with a list of OAuth 2.0 Client IDs, and you should see the one you just made. Click the download button to the side, and download it to a folder called "googleassistant" in your Home Directory.
4. Ensure that "Web & App Activity", "Location History", "Device Information" and "Voice & Audio Activity" are all enabled in your Activity Control page (myaccount.google.com/activitycontrols) so that Assistant can be personalised to you.
5. Open a Terminal window (Applications > Utilities > Terminal.app), and install pip if you haven't already installed it, by entering the command:
Code:
sudo easy_install pip
6. Navigate to your googleassistant directory:
Code:
cd ~/googleassistant
7. Install these dependencies:
Code:
python -m pip install google-assistant-sdk[samples]
8. Enter the following command, changing XX to the name of the json file you downloaded earlier:
Code:
python -m googlesamples.assistant.auth_helpers --client-secrets XX.json
9. You will be given a URL. Enter it into your browser and login to your Google Account to authorise the application. You will be given a code. Copy it, and enter it back into the Terminal window - this may take a few minutes.
10. Test that your Google Assistant works with your Mic by entering the following command; it will record 5 seconds of audio and play it back to you.
Code:
python -m googlesamples.assistant.audio_helpers
11. If you can hear yourself, entering the following command to start talking to your new Google Assistant! It can take a couple of minutes to load when you first enter the command, and can take a minute to realise you've finished speaking, so be patient! It does become a lot more responsive after you've ran it for the first time. When you enter the command, wait for it to prompt the command "press Enter to send a new request", and ignore any warnings.
Code:
python -m googlesamples.assistant
Congrats, you just got Google Assistant working on your Mac!
12. Now to replace Siri with Google Assistant, go to the '2. Assistant App' folder from the archive you downloaded and extracted from this post earlier. Copy it, and place it in the ~/googleassistant directory you created earlier.
All this app does is run the Terminal command from step 11 when pressed (if you're worried, all of these apps can be opened in Automator so you can see there's no funny business here).
13. Next, go to System Preferences > Users & Groups > Login Items, and add the Assistant app as a login item, and click the checkbox to Hide the app so it runs in the background.
14. Go to the directory '/System/Library/CoreServices/SystemAppearance.bundle/Contents', and press Cmd-I to bring up the Get Info dialog box. Give yourself Read & Write access by clicking the padlock at the bottom of the window, clicking the '+' Icon, your username, and setting your Privilege to 'Read & Write'.
Next, enter into the 'Resources' folder and do exactly the same thing to the file 'Assets.car', giving yourself Read & Write access.
15. Repeat step 14 at the directory '/System/Library/CoreServices/Siri.bundle/Contents', again with the 'Resources' folder and 'Assets.car' file.
16. IF YOU DO NOT HAVE A TOUCH BAR, SKIP THIS STEP!
Open the '3. Icons' folder from the archive you extracted earlier, and open ThemeEngine.app. Click 'Open Document', go the directory '/System/Library/CoreServices/SystemAppearance.bundle/Contents/Resources',
and click on 'Assets.car'. Go to the "TouchBarControlStripSiriContent" element, and backup the original image by dragging the 'normal' image to your Desktop or location of your choice.
Next, go into the Images > TouchBar folder and drag the 'sharedArt...' image into the 'normal' box to replace it. Click File > Save and exit.
17. If you do not have ThemeEngine open from the last step, open the '3. Icons' folder from the archive you extracted earlier, and open ThemeEngine.app.
Click 'Open Document', but this time go the directory '/System/Library/CoreServices/Siri.bundle/Contents/Resources', and click on 'Assets.car'.
Go through each element, and backup the original images by dragging both of the images in 'StatusMenuDark', 'StatusMenuLight', and the two images in 'ZZZZPackedAsset-1.0' and 'ZZZZPackedAsset-2.0' to your Desktop or another safe location.
Next, go into the Images > StatusMenuDark in the archive you extracted earlier, and ensure the 'StatusMenuDark' element is selected in ThemeEngine. In the folder, there will be two images - one that begins with 'siri-menu-icon-darkmode_', and one that begins with '[email protected]_'.
Look at the image that is selected in Theme Engine, and drag the image with the same name into its place.
Repeat this with the 'StatusMenuLight', 'ZZZZPackedAsset-1.0' and 'ZZZZPackedAsset-2.0' elements + folders in the archive (sidenote: the PackedAsset elements only have one image inside each, unlike the StatusMenu elements). After this, click File > Save and exit.
18. At this point, you have replaced the Siri Icons with Google Assistant Icons, and have Google Assistant set to open in the Terminal when you login. But all those Siri apps still just open Siri! Lets fix that.
It turns out that when you click the Siri Icon on your Touch Bar, in your Status bar, or open Siri in the Applications folder, they're actually all just shortcuts for opening Siri.app in the CoreServices folder.
In System Preferences, click on Siri and make sure it is DISABLED - do not close this window!
Next, open Activity Monitor (Applications > Utilities > Activity Monitor.app) and search for Siri. Kill Siri and its related service if running.
Open a new Finder Window, and navigate to '/System/Library/CoreServices'. Copy Siri.app and back it up somewhere safe. Go the archive, open the folder '4. Siri Shortcut', and copy Siri.app into the CoreServices folder, replacing the Siri app that's already there. Go back to your System Preferences window, and enable Siri. Close out of your windows, restart your mac, and hey presto - Siri has been fully replaced by Google Assistant! You're welcome.
That Siri.app is again an AppleScript made in Automator, and it essentially just enters 'Return' into the Terminal window when pressed. In other words, it's the equivalent of clicking 'return' in that Terminal window when you were talking to Google Assistant earlier. As I said, it's a bodge, but it works!
When the Terminal window launches, don't exit it! Instead, press Cmd-H to hide the window.
If you want to go back to Siri just follow this tutorial again (in the correct order), but replace the Assistant files with the Siri files that you backed up.
I hope you found this useful!
If you did, please follow me on twitter (@_lucasys) and help share this guide around
ZIP FILE: drive.google.com/file/d/0B9n0ZPG3Fgh3emJaanRHT2ZMSWc/view?usp=sharing
Screenshots: imgur.com/s88t7hC, imgur.com/qIi5t9W
Thanks to Alexander S. Zielenski and Mishaal Rahman
Reserved
Reserved Post
Wow keep it up man!
Any tweaks like this for jailbroken iPhones?
Python
Valiante said:
Any tweaks like this for jailbroken iPhones?
Click to expand...
Click to collapse
I don't know if iPhone have the required version of python if yes then there is a way.
hi, nice hack! one of the best!
does this support local commands for the mac?
Would this work with an M1 Macbook Air and that thise post is like 6 years old?

Categories

Resources