I LOVE THE SMELL OF FLASHED SPLASH SCREENS IN THE MORNING! IT SMELLS LIKE VICTORY!
Okay, I have finally figured out how to make custom splash screens for viewpad 7 and flash them into it (finally got rid of those birds, lol)
Unfortunately, I did not figure out how to dump the old screen (for some reason, flash_image dumps a 100% black image, but at least of correct size) but it's not hard to reproduce if worst comes to worst (aka warranty lol)
However, the new screen is flashed okay.
I'll describe the process of converting any vanilla image file to a viewpad-friendly splash screen (or, rather for that matter, any device-friendly, as long as you can dump the splash/splash1/whatev. partition at least as "black" file in order to get the exact correct size ) and feeding it to the device later, in next post. Now need some sleep lol.
Okay, so, quick instructions for reflashing viewpad image
First, get the flash_image program (see attachment flash_image.zip below, or mirror)
load it up to your sdcard.
Fire up ADB shell in cmd prompt. To do so, do cmd from "run..." in windows start menu, navigate via cd to wherever adb is for you, like for instance
Code:
cd c:\Program Files\Switcher\FM6F_4027\
then do
Code:
adb shell
then do
Code:
su
then do
Code:
cp /sdcard/flash_image /system/bin
then finally
Code:
chmod 755 /system/bin/flash_image
okay, that should get your ready to dump a (lame approximation of) original splash image dump.
To carry that out, first type
Code:
cat /proc/mtd
to find out what partitions are out there (the splash one will have "splash" in its name, duh). Note that viewsonic has the splash partition name being simply splash and not splash1 as most devices have.
On my device, the splash was mtd2
Now, let's try to back up the original splash.
Code:
cat /dev/mtd/mtd2 > /sdcard/splashbackup.img
Okay, here stuff goes weird for me because the file ends up all black (why oh why) but to hell with that, I only need it not to mess up image size.
Okay, now shut down the device and get the file splashbackup.img to your PC.
Rename it to say splashbackup.rgb565 (yes, change the extension)
Now, install Paint.NET and this plugin (both included in my mod pack btw)
Open the splashbackup.rgb565 with paint.net and likely the suggested dimensions will be the ones you want (might not be so for other devices, so take care. But don't worry - you can't kill the device by flashing a FUBAR splash image, so experiment bravely!)
Now, use paint.net to open a desired image in a "vanilla" format that you have likely cooked up in Photoshop or downloaded from the web. Copy its contents to splashbackup.rgb565 and save the stuff as SPLASH.rgb565
You're almost there.
Now, download the zombiegoaste mod of glorious splash screen creator (VibrantOwnr thx!) and rename your desired SPLASH.rgb565 to SPLASH.IMG
Put SPLASH.IMG to "Results" folder of the modified SSC
Now, run Run This Program.CMD and it should guide you through the rest.
GOOD LUCK!
P.S.:
However, bear in mind that devices treat orientation...weirdly it seems, so get ready to manipulate the original image in the program of your choice to rotate stuff (rotate sucks in paint.net) and then redo the steps above that deal with turning a vanilla image into a SPLASH.rgb565
P.P.S.:
All files attached to post and uploaded to a file sharing service, just in case.
Hope this helps folks to easily make and flash custom splash images
Thank you for share, but Im think Im will try hardly to do every way to see splash screen just one or maybe two time in a mounth.
Sent from my ViewPad7 using xda premium
Thanks for posting.. Mac + Photoshop?
Im using a mac and have photoshop. Is there a way to open the rgb565 file in photoshop as I cannot use paint.net? I know that I can save any image I create as a rgb565 file using photoshop but I just cant open one... Perhaps you can give me the dimensions of the image you open up in paint.net to see if that works?
Related
Guys,
Don't know if this has been posted yet, but I figured I would throw it in here just in case (I searched around and didn't see anything - I know there's a thread out there on flashing a zip over the boot animation, but I saw nothing specific to the BootUp sound. Forgive me if I missed it). You can also manually replace the The MyTouch Boot Screen (the second one that loads with all the gaudy animations) in the same directory as listed below.
(Obligatory 'I'm not responsible for your phone exploding' notice)
Make sure you do your removing/pushing of files from your command prompt while in clockwork recovery - AFTER mounting the system.
In order to remove the uber-irritating T-mobile BootUp sound (must have root and have flashed SlideMEROOT2):
adb shell
cd /system/customize/resource
rm TMO_Bootup_sound.mp3
You can change this sound to something else as well - just rename your own file as named above. Same with the Boot Screen: just replace MyTouch_v8_Final.gif with a gif that is named the same.
To replace the file:
adb push [file location & name] /system/customize/resource
I pulled my gif from here: http://forum.xda-developers.com/showthread.php?t=567291
Nice find with the mp3, will give it a try in a bit.
Thankssss!
Awesome! Doing this tonight after I get done with the Fathers Day activities...
Awesome
It worked perfectly for me. I pulled a GIF of my "Stark Industries" boot animation that someone made for me on the G1 themes forum, and my 'Good evening Mr Stark, how may I assist you" boot sound I made from an Iron Man commercial. I feel like Tony Stark
And to go with it, a quick transformers boot theme. Just because I felt like making one for myself...
Sorry, forgot the desktop wallpaper to go with the transformers boot theme...
The tall one if for the lock screen.
Re: HowTo: Remove/Replace T-Mobile BootUp Sound/Animation
Can you post the stark industries mp3 . Thanks
Sent from my android device using tapatalk
Stark Industries
This is the link to the Stark Industries boot sound from the G1 forum.
http://forum.xda-developers.com/showpost.php?p=6538090&postcount=5
Re: HowTo: Remove/Replace T-Mobile BootUp Sound/Animation
Nice thanks
Sent from my android device using tapatalk
so if I wanted to use the Transformers one I would rename the sound file to "TMO_Bootup_sound" and the .gif to MyTouch_v8_Final to get it to work? and then push it out?
what about the wallpaper zip?do we just install them on the sd card?
Yep
@Ravenwulf yep thats exactly how you do it.
and the wall paper zip just gets put on the sd card right?
everytime I try the following commands it tells me it failed because it is a read only file
adb shell
cd /system/customize/resource
rm TMO_Bootup_sound.mp3
I'm working on a new kit for the transformers theme that also has the animation morph into the locked desktop, and re-timing the sound file.
And, it's done...
This kit needs you Android Mytouch Slide to be rooted.
Copy the files into your tools directory of your android-sdk and CD into it.
Then run the following commands:
adb push autobot.gif /system/customize/resource/MyTouch_v8_Final.gif
adb push transformers-hum.mp3 /system/customize/resource/TMO_Bootup_sound.mp3
Copy the following files to your SD card:
autobot-black.png
autobot-blue.png
autobot-lock.png
autobot-lockFF.png
The black and blue autobot images allow you two choices for backgrounds, while autobot-lock acts as a good lock screen. autobot-lockFF shows an example of how to edit the image to add a name to the bottom bar.
Click to expand...
Click to collapse
Hope this makes it simple enough to use.
(The changes are making the animation shift into the locked screen without text, and making the sound match the animation)
RavenWulf said:
and the wall paper zip just gets put on the sd card right?
everytime I try the following commands it tells me it failed because it is a read only file
adb shell
cd /system/customize/resource
rm TMO_Bootup_sound.mp3
Click to expand...
Click to collapse
That would mean your phone is not rooted. None of the startup animation kits can be used without a rooted phone. Root is what gives you write access.
I know what root is and my phone IS rooted. I was running Legend to Slide until the lack of KB lights was making me nuts (no offense eugene) and am now running SlideMEROOT2 with the Matrix bootloader animation. with the way you are showing the adb commands shouldn't the supplied files overwrite the stock images?
RavenWulf said:
I know what root is and my phone IS rooted. I was running Legend to Slide until the lack of KB lights was making me nuts (no offense eugene) and am now running SlideMEROOT2 with the Matrix bootloader animation. with the way you are showing the adb commands shouldn't the supplied files overwrite the stock images?
Click to expand...
Click to collapse
<frowns> Yes. I never had a problem overwriting even once. Works fine on mine.
You should never be denied write access if you are root. It's just not the way it works. I would advise you can -shell into the phone and delete them first, then add them, but now I'm worried about the way your phone's acting.
Foolish Frost said:
<frowns> Yes. I never had a problem overwriting even once. Works fine on mine.
You should never be denied write access if you are root. It's just not the way it works. I would advise you can -shell into the phone and delete them first, then add them, but now I'm worried about the way your phone's acting.
Click to expand...
Click to collapse
just a possible theory but is it possible that it isn't acting as it should because I am running one of the bootloader animations from here http://forum.xda-developers.com/showthread.php?t=705279
and maybe I need to re-flash SlideMEROOT2 and start fresh to get it to work... am a huge Transfan
RavenWulf said:
and the wall paper zip just gets put on the sd card right?
everytime I try the following commands it tells me it failed because it is a read only file
adb shell
cd /system/customize/resource
rm TMO_Bootup_sound.mp3
Click to expand...
Click to collapse
Raven, Where are you trying those commands from? Are you booting into stock recovery, then applying the update to get to get to clockwork and mounting the system?
jadambpharm said:
Raven, Where are you trying those commands from? Are you booting into stock recovery, then applying the update to get to get to clockwork and mounting the system?
Click to expand...
Click to collapse
straight from the command prompt : adb shell in command prompt
do we need to go into clockwork first? then use the commands Foolish Frost put in post #13
RavenWulf said:
straight from the command prompt : adb shell in command prompt
do we need to go into clockwork first? then use the commands Foolish Frost put in post #13
Click to expand...
Click to collapse
Yes, you do. The system has to be mounted and the only place you can do that from (at the moment) is clockwork. Get into there, mount, open up your command prompt and go from there
I'll update the original post w/ that info.
Hello:
I'm attempting to create a custom rom for my Samsung Galaxy S Vibrant. I've downloaded a firmware for my phone (UGJK3), but I've run into a small problem: Samsung doesn't seem to use the default "system.img, boot.img, etc" file structure, and instead uses various factoryfs.rfs, zImage, etc files.
I'm unable to cook my rom using the HTC android kitchen due to this problem: I'm required to have the *.IMG files in order to cook it.
I've mounted the .RFS files in linux, but it has gotten me no closer.
This problem is probably quite easy to fix, I'm just unsure where to start.
Any help is appreciated,
thanks.
It seems like other folks are making flashable zips. I just grabbed one and it's setup very similar to ours, although it appears that the kernel is done differently.
http://forum.xda-developers.com/forumdisplay.php?f=711
Existence. said:
Hello:
I'm attempting to create a custom rom for my Samsung Galaxy S Vibrant. I've downloaded a firmware for my phone (UGJK3), but I've run into a small problem: Samsung doesn't seem to use the default "system.img, boot.img, etc" file structure, and instead uses various factoryfs.rfs, zImage, etc files.
I'm unable to cook my rom using the HTC android kitchen due to this problem: I'm required to have the *.IMG files in order to cook it.
I've mounted the .RFS files in linux, but it has gotten me no closer.
This problem is probably quite easy to fix, I'm just unsure where to start.
Any help is appreciated,
thanks.
Click to expand...
Click to collapse
gnarlyc said:
It seems like other folks are making flashable zips. I just grabbed one and it's setup very similar to ours, although it appears that the kernel is done differently.
http://forum.xda-developers.com/forumdisplay.php?f=711
Click to expand...
Click to collapse
Yeah, I've noticed that, however I'd prefer to work with a kernal and ROM that is stock; that is, hasn't been modified at all. I was able to import a custom ROM into the kitchen that has already been modified (namely Doc's rom), but I view this as a learning experience, and would ideally like to de-odex, zipalign, remove bloatware, etc etc myself.
I'd imagine there would be a veary easy way to change this .tar file to a flashable zip, however I'm at a loss on how to do this.
If someone created a flashable, stock, UGJK3 rom, that would be different, and I'd be able to work with that.
Existence. said:
Yeah, I've noticed that, however I'd prefer to work with a kernal and ROM that is stock; that is, hasn't been modified at all. I was able to import a custom ROM into the kitchen that has already been modified (namely Doc's rom), but I view this as a learning experience, and would ideally like to de-odex, zipalign, remove bloatware, etc etc myself.
I'd imagine there would be a veary easy way to change this .tar file to a flashable zip, however I'm at a loss on how to do this.
If someone created a flashable, stock, UGJK3 rom, that would be different, and I'd be able to work with that.
Click to expand...
Click to collapse
Sure. I like to start with as close to stock or source if possible too. I'm just wondering if there's a how-to in the Vibrant forum or if those folks might know better than those of us who don't have Vibrants. I recently tried helping a friend to root his Vibrant and it was different enough for me to get lost.. .
gnarlyc said:
Sure. I like to start with as close to stock or source if possible too. I'm just wondering if there's a how-to in the Vibrant forum or if those folks might know better than those of us who don't have Vibrants. I recently tried helping a friend to root his Vibrant and it was different enough for me to get lost.. .
Click to expand...
Click to collapse
Yeah, I've already posted a thread in the Galaxy I9000 Q&A section of the forum, but to no avail (not the Vibrant section, as the T-Mobile US-variant differs from my Bell-based Vibrant). I was thinking, what if I install the UGJK3 stock rom on my phone, take a nandroid backup, then use the .IMG files in that backup in the kitchen?
Eh, it's worth a try. I'll see how it goes.
Existence. said:
Yeah, I've already posted a thread in the Galaxy I9000 Q&A section of the forum, but to no avail (not the Vibrant section, as the T-Mobile US-variant differs from my Bell-based Vibrant). I was thinking, what if I install the UGJK3 stock rom on my phone, take a nandroid backup, then use the .IMG files in that backup in the kitchen?
Eh, it's worth a try. I'll see how it goes.
Click to expand...
Click to collapse
okay so was there anything to report because i am on this trek myself at the moment and am looking for any pockets of air as i feel i am drowning in the ocean of dead ends!
Okay, I'm feeling kind today, so here goes:
SAMSUNG ODIN ROMS – Applies to Galaxy S and all derivatives (Vibrant, Captivate, etc)
For anyone unaware, ODIN is the Samsung equivalent of HTC’s RUU. Both are full ROMs containing the images, and both can only be installed via Windows. The ODIN ROMs can be used to restore a semi-bricked phone, that won’t boot to recovery or into the full OS, as all that is needed is Download mode. Download mode is simply accessed by unplugging the phone from the USB cable, holding the volume buttons and plugging in!
BEFORE YOU START, YOU WILL NEED:
- Windows & Relevant ODIN drivers (note – if you’re on 64 bit, you will need to disable signature enforcement on boot before ODIN will work)
- A Linux installation (possibly OS-X, but I haven’t written this guide for that)
So... Working on ODIN roms is a little different to typical ROM ‘cooking’ (I hate that term by the way... cooking can be applied to winzip warriors.. what we're doing here is a tad more technical).
1. First, flash the base ROM using ODIN. Be sure it is a pre-rooted version, or at least root it yourself after.
2. Install an FTP server app to the phone, and connect to it via your computer. It can be done using file managers and shell commands, but will take you ages.
3. Mount system as read write:
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
4. Once you’ve found the issues/things you'd like to change, make the changes directly on the phone itself using FTP/filemanager/shell commands
Add custom boot, build.prop, sounds, fonts, whatever you want (SEE NOTES).
5. Once you’re happy with the build, it’s time to dump the necessary partitions to build the ODIN rom.
To do this, you will need to install a terminal emulator or use adb shell, and ensure the ROM has root access & SU. Let’s work on the assumption that if you’re reading this, you know roughly what you’re doing.
In terminal, type the following commands to dump the /system partition, cache (not necessary), zImage (kernel) and modem.bin (radio) to the INTERNAL SD Card:
su
dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096
dd if=/dev/block/stl11 of=/sdcard/cache.rfs bs=4096
dd if=/dev/block/bml7 of=/sdcard/zImage bs=4096
dd if=/dev/block/bml12 of=/sdcard/modem.bin bs=4096
6. You’ll need to boot into your Linux machine/VM. The next step is to create the tarball of the dumped partitions. Do this by typing the following command into the Linux terminal:
tar -H ustar -c factoryfs.rfs cache.rfs modem.bin zImage > gals.tar
OPTIONAL:
7. Next, md5 it up, as ODIN can check the md5 before writing the image. Do this with the following command:
md5sum –t gals.tar >> gals.tar
mv gals.tar gals.tar.md5
8. Contratulations! That’s your ODIN flashable ROM.
9. You will need a PIT file in ODIN to flash this ROM. This can be obtained by Googling for it, or by asking me... or if you need to know how to make you’re own, it’s a piece of piss, just dump it in the same way as above.
su
dd if=/dev/block/bml2 of=/sdcard/FILENAME.pit bs=4096
More congratulations: you can now do the job of Samsung.
PS - please, oh please, can we stop calling it cooking?
You said:
nprussell said:
Add custom boot, build.prop, sounds, fonts, whatever you want (SEE NOTES).
Click to expand...
Click to collapse
Any chance you have a link to said notes? I would like to read further if they exist.
nprussel: How would you go about creating a CWM flashable version instead of Odin?
Edit: Found this guide, but it's geared towards creating an update.zip for specific purposes instead of for a full rom. Its there a way to automatically generate the update-script for a full stock rom? Maybe just by doing a nandroid backup like the OP suggested?
http://www.londatiga.net/it/how-to-create-android-update-zip-package
nprussell said:
Okay, I'm feeling kind today, so here goes:
SAMSUNG ODIN ROMS – Applies to Galaxy S and all derivatives (Vibrant, Captivate, etc)
For anyone unaware, ODIN is the Samsung equivalent of HTC’s RUU. Both are full ROMs containing the images, and both can only be installed via Windows. The ODIN ROMs can be used to restore a semi-bricked phone, that won’t boot to recovery or into the full OS, as all that is needed is Download mode. Download mode is simply accessed by unplugging the phone from the USB cable, holding the volume buttons and plugging in!
BEFORE YOU START, YOU WILL NEED:
- Windows & Relevant ODIN drivers (note – if you’re on 64 bit, you will need to disable signature enforcement on boot before ODIN will work)
- A Linux installation (possibly OS-X, but I haven’t written this guide for that)
So... Working on ODIN roms is a little different to typical ROM ‘cooking’ (I hate that term by the way... cooking can be applied to winzip warriors.. what we're doing here is a tad more technical).
1. First, flash the base ROM using ODIN. Be sure it is a pre-rooted version, or at least root it yourself after.
2. Install an FTP server app to the phone, and connect to it via your computer. It can be done using file managers and shell commands, but will take you ages.
3. Mount system as read write:
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
4. Once you’ve found the issues/things you'd like to change, make the changes directly on the phone itself using FTP/filemanager/shell commands
Add custom boot, build.prop, sounds, fonts, whatever you want (SEE NOTES).
5. Once you’re happy with the build, it’s time to dump the necessary partitions to build the ODIN rom.
To do this, you will need to install a terminal emulator or use adb shell, and ensure the ROM has root access & SU. Let’s work on the assumption that if you’re reading this, you know roughly what you’re doing.
In terminal, type the following commands to dump the /system partition, cache (not necessary), zImage (kernel) and modem.bin (radio) to the INTERNAL SD Card:
su
dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096
dd if=/dev/block/stl11 of=/sdcard/cache.rfs bs=4096
dd if=/dev/block/bml7 of=/sdcard/zImage bs=4096
dd if=/dev/block/bml12 of=/sdcard/modem.bin bs=4096
6. You’ll need to boot into your Linux machine/VM. The next step is to create the tarball of the dumped partitions. Do this by typing the following command into the Linux terminal:
tar -H ustar -c factoryfs.rfs cache.rfs modem.bin zImage > gals.tar
OPTIONAL:
7. Next, md5 it up, as ODIN can check the md5 before writing the image. Do this with the following command:
md5sum –t gals.tar >> gals.tar
mv gals.tar gals.tar.md5
8. Contratulations! That’s your ODIN flashable ROM.
9. You will need a PIT file in ODIN to flash this ROM. This can be obtained by Googling for it, or by asking me... or if you need to know how to make you’re own, it’s a piece of piss, just dump it in the same way as above.
su
dd if=/dev/block/bml2 of=/sdcard/FILENAME.pit bs=4096
More congratulations: you can now do the job of Samsung.
PS - please, oh please, can we stop calling it cooking?
Click to expand...
Click to collapse
Ok, so I'm trying to create a Factory Odin Flash for the Samsung Galaxy S Showcase.. (brother of the fascinate and Mesmerize)...
I've followed your instructions (step 5-9) to a T, using a Rooted Showcase...
But it fails..
Here the start of the Thread
This is the post of the guy that tested it HERE
Guys ANY info you can help me with this would be GREATLY appreciated, because as of now we have no way to get back to stock!!!
I'm trying to create an Odin Flash now using MY files. I'm on a deodexed PicknPack Rom/Voodoo Kernel. There's several people that have messed up phones and are simply trying to get on our network, so I'm hoping I can atleast help them with that..
Thanks in advance,
elijahblake
nprussell said:
Okay, I'm feeling kind today, so here goes:
SAMSUNG ODIN ROMS – Applies to Galaxy S and all derivatives (Vibrant, Captivate, etc)
For anyone unaware, ODIN is the Samsung equivalent of HTC’s RUU. Both are full ROMs containing the images, and both can only be installed via Windows. The ODIN ROMs can be used to restore a semi-bricked phone, that won’t boot to recovery or into the full OS, as all that is needed is Download mode. Download mode is simply accessed by unplugging the phone from the USB cable, holding the volume buttons and plugging in!
BEFORE YOU START, YOU WILL NEED:
- Windows & Relevant ODIN drivers (note – if you’re on 64 bit, you will need to disable signature enforcement on boot before ODIN will work)
- A Linux installation (possibly OS-X, but I haven’t written this guide for that)
Click to expand...
Click to collapse
Windows is not needed to flash ODIN packages. You can use an alternate open-source software called Heimdall, which is considered by many to be more stable than ODIN. Heimdall is available for Linux, MacOS, and yes even Windows. There is also a GUI, compiled for those platforms (except Linux 32-bit, have to do it yourself or use command-line. 64bit Linux has a compiled version of GUI available)
I have only needed Heimdall once so, but it was easy to use the command-line text from the example given-- I guess maybe I'll learn more complex bits as I soft-brick more times ;-)
The main difference seems to be that you uncompress the ROM archive first, but maybe they will add support for opening the archives (tar files) within Heimdall.
William
Linux FTW! (the others parts could prob be done on Windows somehow, but as our phones run Linux, everything needed is there or easier to install)
Is there a way to port an HTC rom to the vibrant or say the Galaxy Tab (preferred)?
There is a flavour of the Android Kitchen made for the Galaxy S, if you're lazy and/or need some hand-holding: ;-)
It's by RMGeren but still in a beta stage:
https://github.com/dsixda/Android-Kitchen/tree/galaxy_s
Just click on the "Downloads" link on the top right part of the page.
@nprussel: Thanks for that detailed guide!
FOR LINUX!!! UBUNTU!!!!
I did not come up with this, just posting it here, as I didn't find an actual Ubuntu Linux thread version here.
I got most of the info here:
http://forum.xda-developers.com/showthread.php?t=1193698
but also got some here:
http://ivegotavirus.wordpress.com/2011/08/01/changing-htc-desire-boot-splash-in-linux-ubuntu/
And the application was written by this guy here:
http://pof.eslack.org/2008/07/03/nbimg-htc-splash-screen-tool/
You will need to know how to use adb and fastboot for this. Have your phone hooked up and whatnot for those apps (adb and fastboot) to communicate with it.
Download the nbimg.zip file attached to this thread and unzip it to your android SDK directory (wherever your fastboot and adb files already are, this is for simplicity as you'll need to use fastboot to flash it later). This file contains the nbimg executable, and two script files "makesplash.sh" and "flashsplash.sh". The script files are just text, you can open them in a text editor to view their contents. I just created these for convenience.
Make an image file size 540 x 960. Personally I use GIMP. You can just open any image file and resize/crop it to fit as well as it can into that resolution of 540 x 960. Then save the file in 24 bit .bmp format. Save it as "splash1.bmp" without quotes, to your same directory as where fastboot and adb are, again, this is for simplicity.
Now from the command line run
Code:
sh makesplash.sh
It will then create the flashable splash file. Now you have to boot into the bootloader. You can do
Code:
sudo ./adb reboot bootloader
to get into it. Then, on your phone in the bootloader, select fastboot if it's not already saying FASTBOOT USB. Then just run the other script by typing
Code:
sh flashsplash.sh
and type in your password. It will flash and then you can reboot your phone to check out the splashscreen!
This is great you can also put your personal info like if the phone gets stolen or lost.
Please give me your feedback! Let me know if anyone had any trouble.
EDIT: This will *NOT* work unless you are full S-OFF
DISCLAIMER: do this at your own risk, blah blah blah, etc. etc. etc. the usual don't blame me if this causes anything bad to happen, you take full responsibility for your device and what you do to it.
Can I take the image from an already made up splash, alter the image, save it, then re-PG86IMG it through bootloader? Just want to change the color and add an android to my current splash.
gokart2 said:
Can I take the image from an already made up splash, alter the image, save it, then re-PG86IMG it through bootloader? Just want to change the color and add an android to my current splash.
Click to expand...
Click to collapse
If you can save it as a file and open it with an image editor, but I don't know if or how that's possible.
Yes, it's possible, and yes, it's pretty much exactly the same process as on your phone. If you've done it there, you can do it on Wear.
Oh, apologies if this is old news to you, but I couldn't find threads on this particular topic, and I'm quite satisfied that it worked, so why not share.
Now, the stock Wear boot animation is great. I personally love it, at least -- so why change it? Well, why do we do most things on XDA? Because we can. Do at your own risk, I take no responsibility if you screw up. Take these notes as suggestions. I mean, they work, but you know. Backups are always a good idea.
tl;dr for people who don't need help with adb:
push the bootanimation.zip to /system/media (back up the original!), then
chmod 644 bootanimation.zip
reboot
done.
Stuff you'll need:
1. An Android Wear device (any should do, I have a Sony Smartwatch 3) that has root access and ADB debugging enabled
2. A custom kernel that has adbd insecure (I used this)
3. ADB drivers on your computer
4. A boot animation. Duh. I used this for testing purposes because the resolution is meh x close enough.
Optional: a file explorer that works on Wear. I use ES.
How to do it (the way I did, I know there are other ways):
1. On your computer: move the .zip file your animation comes in to the folder where you have ADB installed. It's probably something like "C:\Users\yourname\AppData\Local\Android\android-sdk\platform-tools".
2. Open a command window in that location by shift+right clicking on the folder and selecting "Open command window here".
3. Connect your watch to your computer no later than now. If prompted, allow debugging (note that if it's your first time, the prompt should show. If not, check developer settings again).
4. In the command prompt, type
Code:
adb devices
This lists the devices that are connected to your computer. You should see the text "List of devices attached", your watch's serial number, and the text "device" next to it. If you don't, check your drivers.
5. Copy the .zip onto your watch:
Code:
adb push bootanimation.zip /sdcard/
The directory doesn't actually matter, just make sure it's not /system and somewhere you can remember.
6. Why not /system? Because it's, by default, a read-only partition we can't access via normal adb commands. Yet that's where that zip is headed. This is where the adbd insecure kernel comes in: with it, you can remount /system as read-write. For that, enter the adb shell:
Code:
adb shell
It'll show (don't write this!)
Code:
[email protected]:/ $
To get the root privileges you'll need, type
Code:
su
What you should get is
Code:
[email protected]:/ $ su
[email protected]:/ #
The # means you're rooted. If it shows without typing "su," great.
7. Remount /system as read-write by typing the following:
Code:
mount -o rw,remount /system
8. We can now alter the partition, and we'll start by backing up your stock boot animation. To do that, we need to "move" the file to an identical file with a different name. If that sounds like it doesn't make sense, that's because it doesn't -- it's stupid, but adb shell doesn't have a rename command. This is to avoid the stock animation from getting overwritten by the new one if anything goes wrong. Anyway, to accomplish that, type
Code:
mv /system/media/bootanimation.zip bootanimation.zip1
This changes the animation's extension to .zip1, which doesn't exist. The point of this is that Android looks for /system/media/bootanimation.zip when booting up, so "bootanimation.zip1" gets ignored and is out of our way. If you'd reboot the watch now, there would be no boot animation, just a plain "Android" text (or as is the case with my 320x320 SW3, "NDROI")
9. Now we'll need to move our new animation to replace the old one. To accomplish that, use the aforementioned "move" command:
Code:
mv /sdcard/bootanimation.zip /system/media/
10. Finally, to make the animation actually display, we'll need to give it proper permissions, which are rw-r-r. "chmod" is the command that alters permissions, rw is represented by a six, and r by a four.
Code:
chmod 644 /system/media/bootanimation.zip
11. Close down /system
Code:
mount -o ro,remount /system
12. Done! Reboot your watch and enjoy your new boot animation!
Worked thanks
Gave this a try on the train on my way home from work and it worked a treat thanks now off to find some more suitable boot anims to play around with
Smackedgnome said:
Gave this a try on the train on my way home from work and it worked a treat thanks now off to find some more suitable boot anims to play around with
Click to expand...
Click to collapse
Good to hear! Now all we need is that the artistically inclined among us make some awesome-looking animations for our itty-bitty screens.
If you find any, please post them here so I can add them to the OP.
[NUMINIT] said:
Now all we need ... some awesome-looking animations for our itty-bitty screens.
If you find any, please post them here so I can add them to the OP.
Click to expand...
Click to collapse
Went looking for them and found a few, thought that I would share.
There appears to be a size limit to what boot animation can be used (at least with my Sony Smartwatch 3), the biggest file used being ~3000KB.
Watchdogs
view here
https://www.youtube.com/watch?v=ZhH-4zsMB5w
This is the one I currently use
Cyanogenmod12
(sorry dont have a link/ gif - it looks good trust me )
Nexus 7 boot animation
(no link either sorry and tbh havent tried it yet - theoretically works)
I made none of these myself, they belong to the original owners. (I just cant remember where from lol)
Files are aptly named, dont forget to rename to bootanimation.zip
Enjoy
On my aw2 huawei 2 sport 4g sawshark, the time shows during the boot process. Any way to remove for aw2 or add for aw1?
Sent from my amami using XDA Labs
I finally changed the boot logo in my phone. By keeping permissions the same and not extracting the the whole param file... and root because i am lazy.
Take the .zip from the end of the file name and paste the poison simply as PARAM and reboot and enjoy your new green logo. Of course back up original.
Permissions should not be an issue and i attached a screen of the file info i took prior to editing it.
I forgot to say what i used to change the logo.jpg
Linux and xarchiver utility. Extracted and replaced with my image and set permissions. Checked to make sure file size was similar and proper resolution and that's it. Hope to figure a way to flash it soon so i can wreck stuff faster.
Ah... probably should mention to do this NOT on stock ROM or at all. The more i read on it the more stupid it is to mess with this area unless you know what you're doing. I'll leave it up but don't think anyone should try it.
Ok! I hope this is useful because i've been able to change the initial image with perhaps a MUCH safer way.
Using Linux, i installed Heimdall.
I extracted stock ROM within Linux and used Ark to extract what the Mint archive wouldn't.
Already i had prepared my 2220x1080 jpg to 75 kb and simply deleted logo.jpg within param.bin while viewing with Xarchiver. I did not extract the param.bin file. Then i added my logo.jpg and closed up Xarchiver. The new logo.jpg was also set to r--r--r-- before insertion.
Then, with phone plugged in while in download mode (usb enabled prior in dev options and tested of course)... opened up the terminal from the folder containing param.bin and typed:
sudo su
Heimdall flash --PARAM (dragged param.bin into terminal window and hit enter)
Device booted with new image and then into twrp. I figured a cache wipe was needed so i did that and all was good. Would like to know if this is a horrible idea. Just using rooted stock ROM with twrp.
I posted the image... but of course my phone didn't change anything at the bottom. No way.
Does the image need to be the same file size i have tried making my own logo but it does not really work