Related
In framework-res.apk, what controls the color of the text for the status bar, such as notifications and the digitial clock? Are these controlled independently by seperate apks?
I'm considering diving in and attempting to skin my android but I want to know what I'm getting into.
I've tried replacing framework.apk that I built from source on a real device and emulator. Only bad things came of it. Had to reflash. Let me know if you have better luck.
I'm pretty sure it failed because a lot of the stuff in framework.apk is stubbed closed source stuff.
Koush,
Have you looked at this post by Living_Sword?
I suggest you enter the following commands using adb, because its faster and reliable than telnet or any other method. If you do not have adb setup, read here, if you do, then just enter adb shell in the console while the phone is connected.
In simple words, you have to re-sign the framework-res.apk with your own key. You should know that you will loose all your data while doing this mod. Here are the steps,
1. Re-sign and re-upload all the .apk files in /system/app with your own key or the test-keys. The command used for signing is included in the readme file alongwith the signing jar here.
2. Take a backup of /system/framework/framework-res.apk. Now, you would want to edit some stuff in framework-res.apk, for that the easiest method is to rename the apk file to .jar/.zip, put in your own files(with same name as original png) and rename it back to .apk. You have to re-sign this apk with the same key like you did in the first step.
3 . Upload the apk file to /system/framework. The phone will hang, and in few secs it will most likely go back to the android robot screen.
4. Take out the battery, then do a data reset by going into recovery mode and pressing ALT+L to see the log text and then ALT+W to wipe out /data. Obviously, you will loose all your apps and settings and will have to re-activate the phone.
5. After the wipe is complete, press HOME + BACK to reboot. The phone should reboot normally now.
I know its a pain to loose all the data and apps, but this is the easiest method until we figure out something more elegant, and its required to be done only once. Also, there is no need to keep the png file size same. And in future, you will be able to replace the framework-res.apk without any hassles.
Also, since each stock app's icon is in its own apk, once you re-sign every apk in /system/app, you can easily replace their icons with your own.
Source: http://www.modmygphone.com/forums/showthread.php?p=16871#post16871
Ok, so I have successfully replaced framework-res.apk with my own build which includes custom icons and things like that. However, I am running into two problems:
1: I keep running out of room in my system folder. Everytime I replace framework-res.apk I am losing space somehow, eventually I have to do the mod rc30 update all over again to get my memory back so I can push this file over, where is this space going? Whats eating it up? Oh, and it isn't the file size growing, this will happen if I pull a file and directly try to push it back onto the phone.
2: I still don't know how to change the default color of the text. I assume it is in one of these xml files but I'm not sure, and I haven't found it yet. Could it be in /res/color/?
If anyone could help me on these two issues I would be so appreciative.
This is what I've done so far, see the status bar and the icons?
Stericson
Stericson said:
Koush,
Have you looked at this post by Living_Sword?
I suggest you enter the following commands using adb, because its faster and reliable than telnet or any other method. If you do not have adb setup, read here, if you do, then just enter adb shell in the console while the phone is connected.
In simple words, you have to re-sign the framework-res.apk with your own key. You should know that you will loose all your data while doing this mod. Here are the steps,
1. Re-sign and re-upload all the .apk files in /system/app with your own key or the test-keys. The command used for signing is included in the readme file alongwith the signing jar here.
2. Take a backup of /system/framework/framework-res.apk. Now, you would want to edit some stuff in framework-res.apk, for that the easiest method is to rename the apk file to .jar/.zip, put in your own files(with same name as original png) and rename it back to .apk. You have to re-sign this apk with the same key like you did in the first step.
3 . Upload the apk file to /system/framework. The phone will hang, and in few secs it will most likely go back to the android robot screen.
4. Take out the battery, then do a data reset by going into recovery mode and pressing ALT+L to see the log text and then ALT+W to wipe out /data. Obviously, you will loose all your apps and settings and will have to re-activate the phone.
5. After the wipe is complete, press HOME + BACK to reboot. The phone should reboot normally now.
I know its a pain to loose all the data and apps, but this is the easiest method until we figure out something more elegant, and its required to be done only once. Also, there is no need to keep the png file size same. And in future, you will be able to replace the framework-res.apk without any hassles.
Also, since each stock app's icon is in its own apk, once you re-sign every apk in /system/app, you can easily replace their icons with your own.
Source: http://www.modmygphone.com/forums/showthread.php?p=16871#post16871
Click to expand...
Click to collapse
framework-res.apk is just the resources. framework.apk contains the actual code used by every application in the system. Attempting to replace THAT file the result of the android build process will fail.
I think we're talking about two different files.
Oh yep, definetly we are...I thought you were talking about that but I figured you would clarify if you were indeed. Thanks.
so you guys are making progress on some themes... GOOD ****..
jzajzz said:
so you guys are making progress on some themes... GOOD ****..
Click to expand...
Click to collapse
Agreed. Once this process is mastered, and some polished themes, or a tool to make your own (or something) comes out, our G1's will look even sweeter.
jzajzz said:
so you guys are making progress on some themes... GOOD ****..
Click to expand...
Click to collapse
Well, I was making progress, but now my phone is bricked. Don't know how it happened. Was doing the same thing I've done over 20 30 times, suddenly started giving me problems, reflashe JF update and voila! bricked phone. So now I'm getting a new one sent to me and hoping that it comes pre-rc30. Sucks too because I am pretty sure I found out where the text color is set. Thats why I'm trying to get this to work under the emulator, but I can't get it to work. The dang emulator won't reboot or shutdown. So I can't see the changed made.
It sounds like it's too late to help now. But how was the phone bricked? Did it go into an infinite reboot cycle? Stay on the G1 screen?
Also, I assume you hadn't loaded the dev bootloader? That could have easily saved your phone from brickage
JesusFreke said:
It sounds like it's too late to help now. But how was the phone bricked? Did it go into an infinite reboot cycle? Stay on the G1 screen?
Also, I assume you hadn't loaded the dev bootloader? That could have easily saved your phone from brickage
Click to expand...
Click to collapse
My phone does have the dev bootloader on it. However, now it just stays on the boot splash screen and I can't do the update because it says the /dev file is gone! Can I reflash all of that and save my phone?
Btw, I actually think the entire folder /system is gone, because I can't abd with root, and when I did it in the update screen my system folder wasn't showing. So, I have no idea how this happened.
Is it possible to push that entire folder back on there and then recover or something?
Yes, you can reflash the recovery partition using the fastboot protocol, which the dev bootloader supports. There isn't a windows binary for it yet, but if you have a linux or mac handy, turn on the phone into bootloader mode, then plug in the USB cable. "Serial0" should change to "FASTBOOT". now you can use the fastboot binary on your computer to flash anything on the phone. You might try re-flashing the recovery image that's in my modified update. If that doesn't work, maybe try flashing the radio too.
If you have the dev bootloader, I'm almost positive your phone can be saved. Give me at IM if you want to talk about it.
I *think* the fastboot binary is in the sdk for linux/mac. I could be wrong though. There are copies of both floating around though, just ask if you need one.
I managed to repack framework-res.apk and resign all other packages without wiping. The problem is with the signatures in /data/system/packages.xml - they no longer match after resigning. The solution is to simply delete all <sigs> sections (and the <certs> within), and the PackageManager will automatically regenerate them as they are launched. I just now successfully booted, so can't say this is thoroughly tested, but I'll report back here if any problems crop up.
donniesmit said:
I managed to repack framework-res.apk and resign all other packages without wiping. The problem is with the signatures in /data/system/packages.xml - they no longer match after resigning. The solution is to simply delete all <sigs> sections (and the <certs> within), and the PackageManager will automatically regenerate them as they are launched. I just now successfully booted, so can't say this is thoroughly tested, but I'll report back here if any problems crop up.
Click to expand...
Click to collapse
A good check after doing something like this is to take a look at the call log, and actually receieve a call (call yourself from your home phone, or whatever). Both of these like to error out when messing around with resigning.
To create themes, or to edit themes to your liking, you will need a working knowledge of android, adb, how to resign apk's, knowledge of your own O/S.
Before you start be aware that you will probably end up wiping your phone once, if not more. So lets go over the things that you will need.
You will need JF's RC30, RC8, or ADP1 V1.3, depending on what version you intend to create for.
Here is the link to these: http://forum.xda-developers.com/showthread.php?t=466174
You will also want to get the dev bootloader installed on your phone and to HIGHLY suggest everyone trying your theme to install it as well.
Link to dev bootloader: http://forum.xda-developers.com/showthread.php?t=455860
You will also need to resign all the apks located in /system/app and framework-res.apk located in /system/framework. When you push all of these to your phone, you will need to do a wipe.
JesusFreke was kind enough to build a custom signing tool for me that would allow me to right click on an apk and resign it from there. I am posting it here for others to use as well. Note that this is a courtesy of JF, so thank him for it. I cannot stress how much time this has saved me and will save you.
Here is the link: Http://www.FightForthePits.com/testsign(2).zip
Before using this you need to know how to set this up:
I will assume that you have the sdk downloaded and extracted somewhere(if not, do that now), extract both files to the tools directory of your sdk.
Now you will need to add the tools dir of your sdk to the environment variable CLASSPATH.
To do this, right click on My Computer click properties, then choose the tab that says advanced. Click the button that says environmental variables. Go to system variables find the one that says CLASSPATH, double click it, go to the end of variable value. There should be a semicolon ; at the end. type in the path to the testsign.jar located in the tools directory of your SDK, for example the path to my testsign.jar was c:\sdk\android-sdk-windows-1.0_r1\tools\testsign.jar If CLASSPATH is not in your system variables then create it.
If you find the right click menu not working for some reason you can type the following in cmd to sign your files: java testsign whateverfiletosign
Now right click the reg file that you extracted and choose to install it, or merge.
Now, right click an apk, do you see an option that says ResignApk? If not hit the windows key and R at the same time. Type in regedit. go to HKEY_CLASSES_ROOT and expand it. Now find .apk and click it. Double click on (Default) and erase apk_auto_file. Hit ok and close the Reg editor. Now right click an apk and the option ResignApk should be there.
Now through doing this you have done two things, first off you have made the resigning process extremely easy, secondly you will not have to cd to the tools dir of the sdk to use adb or any other tool in the sdk.
You will also need a version of linux installed or running vmware with linux, so that you can create an update file which will install the theme onto the users phone.
You need to make sure that you do this correctly, because if you don't then you will have the potential to create problems for people trying to install your theme. You also need to be specific in addressing what version your theme is for, RC8, RC30, or ADP1. Make sure every file gets signed. Make sure you test the update.zip before you release it.
Every .apk contains the images relating to itself. However, every apk has the ability to use the images in framework-res.apk. The images for every apk is located inside of res and more specifically in folders that are named Drawable, drawable-land, drawable-port, etc. Some things you cannot edit unless you rebuild the entire apk from source, which we will not go into here.(another tutorial, another time) Just know that at this time you SHOULD NOT edit, or even open images with the extension .9.png. If you do you will have problems...Trust me. These are special images called ninepatch images and android resizes these images to fit wherever android, or any other apk, needs it to. if you do open them or edit them they will no longer render correctly when resized. I believe that in order to edit these you must do so and then put them into the source and rebuild the entire apk.
Before getting started you must also realize that you cannot simply resign one or two apk's and stick them in your phone and expect them to work. You must resign every apk inside of /system/app and framework-res.apk and put them on your phone at the same time.
To simplify this process for you though, I have provided an update which will do all of this for you. Note that these updates will not completely wipe your phone, your apps will be retained, however, they will require you to re-enter your Google info, and you will lose you call history.
Links down
Just put the correct update.zip, depending on what version you are running, onto your sd card, boot into recovery and hit alt + s.
Now you can push your own apk's one at a time without re-wiping your phone.
Now, your ready to start changing things up.
You will now need to open the apk, which you can do by adding .zip after .apk, effectively changing it to a zip. Note that if you are using windows you will need to unhide known file extension types.
See here to unhide known file extension types for Xp: http://www.mediacollege.com/microsoft/windows/extension-change.html
See here to unhide file extension types for Vista: http://maximumpcguides.com/windows-vista/how-to-change-a-file-extension/
After changing the apk to a zip open it go to res and copy the folders that have drawable in their name. Go to your desktop, or wherever, create a new folder called Images, or whatever. Open the folder, paste the drawable folders in there. Now you can see what the files look like without opening them. Btw, you may also want to add -frame, or -launcher, to the end of the folders you cope over to keep them separated from others.
Finally, you've edited the images put them all in the apk renamed it back to an apk and resigned it. Now it's time to push it to your phone and see the changes you've made.
Important! : Whenever pushing files to the phone NEVER do it while the phone is running. Do this in recovery mode! If you do this while the phone is running normally you will begin to lose space in /system.
So, boot into recovery plug your phone in and open a cmd prompt. From the cmd prompt type adb shell mount /system then type the following: adb push c:\whereveryourfileis\whateveryourpushing.apk /system/app (system/framework if your pushing framework-res.apk)
Now reboot your phone. If it doesn't boot, try doing a wipe, if that doesn't work reinstall an update and try again. There are alot of things people can do wrong, I can't explain them all here. If you get real stuck, you can ask for help here or contact me on Gtalk [email protected].
So now your theme is done and your ready to make an update.zip for others to install your theme.
This must be done in LINUX! Not WINDOWS! Yes it may work for you if you do it in windows but other people's phones will enter an indefinite loop! Just do it from Linux! If you absolutely cannot make your own update.zip, contact me and we'll see if I can make one up for ya.
I have created a template for you to make your own update.zip. Just download, open in Linux, and add the system apps to app, and framework to framework. Zip it up, SIGN IT, TEST IT YOURSELF, and then distribute it!
Empty update.zip template: Http://www.FightForthePits.com/Androidstuff/update_empty.zip
If anyone has any questions please try asking for help in this thread before emailing me for help Usually I will respond to questions in this forum.
I hope this Tutorial has been helpful. I will add on to it as needed.
Stericson
Links of interest:
Downloading SDK: http://code.google.com/android/intro/installing.html
Using ADB: http://code.google.com/android/reference/adb.html
Working with ninepatch should be straightforward if you use the draw9patch tool included in the SDK. Documentation on usage here:
http://code.google.com/android/reference/draw9patch.html
JF could also save theme users a wipe by resigning /system/app/* and /system/framework/framework-res.apk in his builds with the test keys. Nice tutorial, btw.
However it doesn't. I have used that to no avail. I believe you need to edit the images, put them in the source then rebuild the apks from the source.
As for JF's update, it does not currently wipe your phone after install. So, for him to do this he would have to have his update do a wipe. So technically, they would still have to do this initial wipe.
Stericson
Stericson said:
However it doesn't. I have used that to no avail. I believe you need to edit the images, put them in the source then rebuild the apks from the source.
Click to expand...
Click to collapse
Good point. I thought you could simply drop a similarly dimensioned PNG in but apparently there is some metadata that only the android tool can create.
As for JF's update, it does not currently wipe your phone after install. So, for him to do this he would have to have his update do a wipe. So technically, they would still have to do this initial wipe.
Click to expand...
Click to collapse
True, but a user who is upgrading to a JF update after having put in customized (and test-key signed) system apps will have to wipe again anyway =) Anyone using custom themes will have to wipe every time a JF update (or any update) comes out. However if JF resigns, custom theme users would not have to wipe and stock theme users only have to wipe once. (Nevermind the fact I think everyone should wipe when updating...)
thx stericson this will help big time how long before I can get resigned rc30 last night when you said all the apk. need to be resigned I was like this is going to be a long night but I see jf hooked you up save some big time with his resigning tool
jashsu said:
Good point. I thought you could simply drop a similarly dimensioned PNG in but apparently there is some metadata that only the android tool can create.
True, but a user who is upgrading to a JF update after having put in customized (and test-key signed) system apps will have to wipe again anyway =) Anyone using custom themes will have to wipe every time a JF update (or any update) comes out. However if JF resigns, custom theme users would not have to wipe and stock theme users only have to wipe once. (Nevermind the fact I think everyone should wipe when updating...)
Click to expand...
Click to collapse
Ah, good point
The resigned apps will be released maybye sometime tonight...I had them done but ran into a script problem on adp1 and I have yet to try the rc30 and rc8 ones yet. so I won't release those until I've tested them. If you want to be a Guinea pig however, just let me know
Stericson
Stericson said:
Ah, good point
The resigned apps will be released maybye sometime tonight...I had them done but ran into a script problem on adp1 and I have yet to try the rc30 and rc8 ones yet. so I won't release those until I've tested them. If you want to be a Guinea pig however, just let me know
Stericson
Click to expand...
Click to collapse
The resigned apps have been released, each update file will resign all of apps in /system/app and framework-res.apk. However, these updates make no changes to them whatsoever...Meaning your phone will look just like a brand new phone without any modifications.
rc30 works thx Stericson made it easy for use
Issues with using the update.zip above
Hi all,
I just wanted to point out that after I applied the update.zip above and rebooted applications kept force closing randomly and constantly even through the initial setup (where you have to click the green android to start).
Prior to this, I had JF's RC30 1.3, and the engineering bootloader V2 no sigcheck.
First I did just a alt+s then a alt-w and alt+s. And still nothing.
I'm new to all this so I'm not even sure where to begin troubleshooting. Should I be using the HardSPL?
Thanks in advance and I appologize if this isn't the right place for this post.
Update:
After reflashing with JF's 1.3 RC30 and the problem persisted I noticed that there was a new release 1.31 and this has fixed the problem. I hope this helps anyone else who runs into the same problem.
I still don't know what went wrong though, can anyone shed some light on this? thanks.
Truly there's no telling, sounds like J'f's update fixed it. Can I ask what version you tested?
I would also like to announce that now, thanks to JF, again, you do not have to wipe your phone completely to apply the resigned app updates. However, you will have to re-enter your google info and your call history and other minor things will be gone, but all of your apps will be retained.
Stericson
Stericson said:
Truly there's no telling, sounds like J'f's update fixed it. Can I ask what version you tested?
I would also like to announce that now, thanks to JF, again, you do not have to wipe your phone completely to apply the resigned app updates. However, you will have to re-enter your google info and your call history and other minor things will be gone, but all of your apps will be retained.
Stericson
Click to expand...
Click to collapse
Hey, I tested it with this one:
Rc30 resigned: http://www.fightforthepits.com/Andro...pdate_Rc30.zip
Update went fine, until I booted back up then the applications kept force quitting, without me even doing anything.
Thanks,
Limitlis
yes there is a temp problem with those right this moment I am on the problem as we speak, expect a fix tonight...
Stericson
Can we get the fix cuz it bricking fone I had to flash rc29 nbh
Edit: I forgot please.... feel kinda rude when ur helping me out lol but it bricking some phones and for our less experince members we don't global meltdown lol
These files have been fixed and uploaded.
Stericson
I found the cyclon boot effect images in in framework-res/assets/images,
is there any way to replace the android boot image with those images?
Is there anyway to make the theme with a custom boot screen? Also is there a way to change the second boot screen(The one that says Android and has the little robot)
i tried using the testkeys from JF to resign my apks, but the update still says there is not signature =[
hello, I used the tutorial and everything worked great. I'm trying to change the background to the notification section but I can't find that file. Could you tell me where it is? Thank you.
hey stericson, how do u create a theme for rc33?
This tool is designed for the Samsung Galaxy S 4G ONLY.
I am not responsible for any damage caused by this tool. I don't see how it could happen, but who knows...
This tool will allow you to upload your bootanimation.zip and it will send you back a CWM-flashable zip file to flash.
Requirements
Samsung Galaxy S 4G
CWM Recovery (tested on 3.x and 5.x)
A kernel that supports custom boot animations.
Frozen Yogurt: Here
Gingerbread: Here
Notes
A QR Code will be generated that you can scan with Barcode Scanner (or equivalent) and download your zip file directly to your phone.
Maximum number of characters for the zip filename is 20.
Uploaded file must be named bootanimation.zip.
Maximum file size for bootanimation.zip is 10mb.
Your chosen filename will have a Unix-style timestamp attached to prevent duplicate names.
Your download url will remain valid for one (1) day.
Source Code
The source code is written in PHP and is available on my GitHub. If you want to try it yourself, your web server's PHP installation must have the Zip PECL extension installed.
Link: http://bootanim.crackpot.co
I moved the script to a new home at http://bootanim.crackpot.co, along with changed the GitHub project name to "bootanim". Everything should function normally.
Package Download: undefined
Failed to move uploaded bootanimation.zip file.
Tested and I get the above error message.
Tried again 12:25 pm still get same error
There is another one that I use.
Racing19969 said:
Package Download: undefined
Failed to move uploaded bootanimation.zip file.
Tested and I get the above error message.
Tried again 12:25 pm still get same error
Click to expand...
Click to collapse
What browser are you using?
I think I corrected the issue. I think it was an issue with my PHP config only allowed 2mb uploads max.
Version 1.1 is live now with A LOT of updates.
For reasons I can't quite explain even though the script is correctly creating the zip files, once flashed they do not work. At first I figured it was a permissions issue, but that doesn't seem to be the case. So my best guess is the zip file isn't being created properly.
With that in mind, I am going to rewrite the script to use the zip class FB used on his debloater script.
We'll see what happens, shouldn't take long.
After talking with FB, I think we finally nailed the issue and it should be functioning like normal now.
Thanks FB!!!!
crackpot said:
After talking with FB, I think we finally nailed the issue and it should be functioning like normal now.
Thanks FB!!!!
Click to expand...
Click to collapse
No problem.
Script updated to version 2.1. It will now generate a QR image for you to scan from your phone, using Barcode Scanner, to download the package directly to your phone!
Works great! thanks
Johnmonkey0 said:
Works great! thanks
Click to expand...
Click to collapse
Glad you like it!
I have read the information on manually changing the boot animations, but has anyone used a tool to do it? Rom Tool Box and a slew of other apps have change boot animation functions. I was just wondering if anyone has successfully used any stand alone app to accomplish this? also boot logos?
henbone11 said:
I have read the information on manually changing the boot animations, but has anyone used a tool to do it? Rom Tool Box and a slew of other apps have change boot animation functions. I was just wondering if anyone has successfully used any stand alone app to accomplish this? also boot logos?
Click to expand...
Click to collapse
I tried Rom Toolbox but it doesn't chance animation on mine. I don't know nor can find where the settings or the directory is on the tf700 is to change it in Rom toolbox. If you know... please share it or a link to the answer. Thanks
Ice, rooted and unlocked. NVflash backup
Boot Animations works fine.
Apparemtly tf700 users can't get this to work either. just need to know which dir tf700 actually uses.
andyk11 said:
just need to know which dir tf700 actually uses.
Click to expand...
Click to collapse
I've copied an LCARS one to /data/local and works perfectly.
How To Change, Customize & Create Android Boot Animation [Guide]
So you have found a boot animation that you want to install on your phone? Created one of your own and can’t wait to see it in action on your device? All you have to do is copy it at a certain location on your device. There are two locations you can copy it: /data/local and /system/media, and both have their advantages and disadvantages.
Advantages of copying it to /data/local is that you will not require root access for it and it should work for all non-rooted devices without running the risk of changing anything in the /system partition. Furthermore, if a bootanimation.zip file is found in both locations, Android ignores the one found in /system/media and gives priority to the one in /data/local. A disadvantage of this method is that upon a hard reset (also called a full data wipe or a factory reset), the new boot animation will be lost.
Copying the boot animation to /system/media/ is possible only if your device is rooted and you have read+write access to the /system partition. An advantage of this method is that upon a hard reset, the new boot animation will still remain and there will be no need to apply it again. A disadvantage is that it requires ADB or a root level file browser such as Root Explorer or Super Manager.
Click to expand...
Click to collapse
xcal321 said:
I've copied an LCARS one to /data/local and works perfectly.
How To Change, Customize & Create Android Boot Animation [Guide]
Click to expand...
Click to collapse
Thanks for the info. I saw that and tried it but no luck. Not sure what I'm doing wrong. Tried to change it with ROM Toolbox pro also an doesn't work. Am rooted and unlock but no JOY. I did find the /system/media/bootanimation.zip file but it just doesn't load.
Update: I copied the animation.zip files to both /system/media and also data/local. The only thing that loads is the White Asus sign for about 5 sec then a Black screen for about 20 sec then boots normally. Theres got to be a setting that directs the bootanimation file to load but can't find what file the boot looks for to load where to find bootanimation.zip.
andyk11 said:
Update: I copied the animation.zip files to both /system/media and also data/local. The only thing that loads is the White Asus sign for about 5 sec then a Black screen for about 20 sec then boots normally. Theres got to be a setting that directs the bootanimation file to load but can't find what file the boot looks for to load where to find bootanimation.zip.
Click to expand...
Click to collapse
This, to me, looks like the animation is corrupt or is not a boot animation. Check out this tool. Restore the original animation to /system/media and then use the one in the link of my previous post and put that in /data/local.
Thanks. I checked out the program and tried it but got errors pushing the file. to /media but it worked going to /local. tried previewing with romtools pro but not working. I'm stumped. Found a bunch of treads for this problem but nothing. files are not corrupted. I can get the boot animation files to run outside of android on a pc ect but not while trying to get them to animate inside there folders.... /local or /media. Somewhere in the boot process it's not loading. Need to find out why the White Asus animation works for a few seconds and where it is. It used to turn Brown/ Goldish and rotate but no longer. Anyone else with any guess's?
Also: Forgot to mention am using the JB bootloader.
andyk11 said:
Thanks. I checked out the program and tried it but got errors pushing the file. to /media but it worked going to /local. tried previewing with romtools pro but not working. I'm stumped.
Click to expand...
Click to collapse
Have you tried viewing the animation in the tool I mentioned?
andyk11 said:
Need to find out why the White Asus animation works for a few seconds and where it is.
Click to expand...
Click to collapse
That is not the boot animation of Asus, it's a still image embedded in either the bootloader or something close to it. It's not mean to be customized, the metallic ASUS logo with the light effect and then the circular progress indicator are part of the default bootanimation.zip
andyk11 said:
Anyone else with any guess's?
Click to expand...
Click to collapse
I haven't given up yet Would you be willing to share the bootanimation that you are trying to use, with us. This way we can have a look an see if it works for us.
andyk11 said:
Also: Forgot to mention am using the JB bootloader.
Click to expand...
Click to collapse
As am I. I'm on JB 4.1.1 (WW 10.4.4.18).
xcal321 said:
Have you tried viewing the animation in the tool I mentioned?
That is not the boot animation of Asus, it's a still image embedded in either the bootloader or something close to it. It's not mean to be customized, the metallic ASUS logo with the light effect and then the circular progress indicator are part of the default bootanimation.zip
I haven't given up yet Would you be willing to share the bootanimation that you are trying to use, with us. This way we can have a look an see if it works for us.
As am I. I'm on JB 4.1.1 (WW 10.4.4.18).
Click to expand...
Click to collapse
Yes of Course I'd be willing to share it. As I said I can view it outside of the floders on a Windows PC running the boot animtion progam. The one I was tring to install comes with RomToolbox Pro. The droid Peeing on an APPLE... need a few hours sleep as am to tied to keep messin with this. will get back to you... OH... I deleted all animation zip files also and still get the ASUS screen. non animated. whereever that file is it's corrupted I think.
andyk11 said:
Yes of Course I'd be willing to share it. As I said I can view it outside of the floders on a Windows PC running the boot animtion progam. The one I was tring to install comes with RomToolbox Pro. The droid Peeing on an APPLE... need a few hours sleep as am to tied to keep messin with this. will get back to you... OH... I deleted all animation zip files also and still get the ASUS screen. non animated. whereever that file is it's corrupted I think.
Click to expand...
Click to collapse
Sorry for the wait. I have no way of uploading the animation file in question here. Looking for somewhere to upload it so you can look at it but as I said the file is not the problem. I need to reinstall the bootloader which is 9.4.5.30r01 Not sure how to just do that as I haven't looked into it. The 9.4.5.30r01 came from the nvflash tread in this forum. I need to research if I install a jb bootloader if I still have nvflash "JUST IN CASE" Have a nice day.
andyk11 said:
Sorry for the wait. I have no way of uploading the animation file in question here.
Click to expand...
Click to collapse
No problem, I have ROM Toolbox myself and got the animation. While playing around (copying animations to my tablet from my NAS) I figured out what might be wrong on your side.
Make sure your bootanimation.zip is in /data/local and set the file permissions to rw-r--r--.
xcal321 said:
No problem, I have ROM Toolbox myself and got the animation. While playing around (copying animations to my tablet from my NAS) I figured out what might be wrong on your side.
Make sure your bootanimation.zip is in /data/local and set the file permissions to rw-r--r--.
Click to expand...
Click to collapse
Thanks I already tried that. I found that in a post days ago but no luck. permissions where set right. Since my last post I updated to the 10.4.4.18 the odex version and I got bootanimation back. I backed it up using trwp 2.3.1.0 and tried changing it with Rom toolbox again. I set the paths to data/local in the settings. I installed the new bootanimation.zip file and rebooted. It would not boot up at all. Got past the white asus and went blank and I waited 10-15 min but noting. I rebooted by holding down power button for like 10-15sec and still would not boot up. Had to go back to trwp and reinstall my .18 backup and it started right up. Am going to give up for now till I can find out what is causing this for me and not others. Theres just something I'm missing and haven't pinned it down. Thanks for your time and effort. really appreciate it.
Update: 10-22 @11:34 pm. I got it working... Installed CleanRom 2.3 http://forum.xda-developers.com/showthread.php?t=1919851
Not even sure what I did other than flashed, wiped and reset. I checked the location of the bootanimation directory in this rom and it was only in /system/media. I read all the treads and info I could find. I used Rom Toolbox pro https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolboxpro&feature=search_result and changed settings to install it in /data/local as everywhere I read suggested that directory. If you've read what I've tried in the past I already did that over and over. Checked the permissions of the file and all. the one thing I didn't do was remount the zip file after copying to the directory. I didn't think I would have needed to since toolbox would have handled that... I though. Thats the only thing I can think of why it wouldn't load on boot is because it wasn't remounting. Anyways. I got it working but to be honest I still don't know why and I actually wanted to know why... A learning experiance if you want. One more time... Thanks a million for your time.
andyk11 said:
Thanks I already tried that. I found that in a post days ago but no luck. permissions where set right. Since my last post I updated to the 10.4.4.18 the odex version and I got bootanimation back. I backed it up using trwp 2.3.1.0 and tried changing it with Rom toolbox again. I set the paths to data/local in the settings. I installed the new bootanimation.zip file and rebooted. It would not boot up at all. Got past the white asus and went blank and I waited 10-15 min but noting. I rebooted by holding down power button for like 10-15sec and still would not boot up. Had to go back to trwp and reinstall my .18 backup and it started right up. Am going to give up for now till I can find out what is causing this for me and not others. Theres just something I'm missing and haven't pinned it down. Thanks for your time and effort. really appreciate it.
Update: 10-22 @11:34 pm. I got it working... Installed CleanRom 2.3 http://forum.xda-developers.com/showthread.php?t=1919851
Not even sure what I did other than flashed, wiped and reset. I checked the location of the bootanimation directory in this rom and it was only in /system/media. I read all the treads and info I could find. I used Rom Toolbox pro https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolboxpro&feature=search_result and changed settings to install it in /data/local as everywhere I read suggested that directory. If you've read what I've tried in the past I already did that over and over. Checked the permissions of the file and all. the one thing I didn't do was remount the zip file after copying to the directory. I didn't think I would have needed to since toolbox would have handled that... I though. Thats the only thing I can think of why it wouldn't load on boot is because it wasn't remounting. Anyways. I got it working but to be honest I still don't know why and I actually wanted to know why... A learning experiance if you want. One more time... Thanks a million for your time.
Click to expand...
Click to collapse
The reason why it don´t work is that Asus maybe has integrated a check of system files in some asus app or in the kernel (don´t now)
Changing Bootanimation does only work for me with a cleanrom and cm10.
as you sad when you change it in the stock rom it wont boot anymore.
So Asus dont want that someone removes their bootanimation i think
blackmambazzz said:
The reason why it don´t work is that Asus maybe has integrated a check of system files in some asus app or in the kernel (don´t now)
[-->8--]
So Asus dont want that someone removes their bootanimation i think
Click to expand...
Click to collapse
You don't have to remove/replace the Asus bootanimation. Just place your own in /data/local set the correct permissions and you're good to go.
EDIT: WIFI ONLY - Not the LTE Version!
Title says it all. Hope this saves someone hours of searching for it like I did before giving up and pulling it from the stock JSS15R image. I know we should all make backups but life happens. This is for all of you [like myself] who found you could not upgrade to Stock 4.4 because of changes to your build.prop file.
In my case I forgot to uninstall a custom framework I had installed on a stock 4.3 image [root but stock recovery] and the 4.4 OTA failed. I never got another prompt to try again from Google so after removing the framework I downloaded the image manually and tried to install it through ADB. Again it failed this time telling me the file build.prop had the wrong checksum. The framework had restored the build.prop but the file checksum was off. The one below was pulled from the original stock image using ext4_unpack. I copied it to my system folder over the "original" and ran the update again. Worked like a charm.
If you run into the same issues try the stock file above. We really should just start a repository for these stock build.prop files.