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.
Related
I flashed pudding on my 1.83 ATT atrix. This worked fine, and I am trying to get CWM for unlocked bootloaders now. I am following the instructions directly from the thread: http://forum.xda-developers.com/showthread.php?t=1138541
Problem is, after extracting the zip to C: and running "fastboot flash recovery C:\(image name).img", I get "fastboot is not recognized as an internal or external command..."
This leads me to believe that I don't have adb set up properly. I have standard adb set up for pushing apk's, but am I missing something specific for fastboot?
All i have under android-sdk-windows>platform-tools is adb.exe adbwinapi.dll and adbwinusbapi.dll. I DO have USB debugging on lol.
I seem to remember having more stuff under platform tools at an earlier date. All the threads for setting up adb are LONG buried, and after exhaustive searching, I finally gave up and decided to post (at least not in dev ). Even turning to google for adb help, I only get a bunch of the ad-farming tip websites that are outdated.
Please help me out guys. I can usually help myself after enough research, but I admit defeat on this one :/
Thanks much,
-omni
omni_angel7 said:
I flashed pudding on my 1.83 ATT atrix. This worked fine, and I am trying to get CWM for unlocked bootloaders now. I am following the instructions directly from the thread: http://forum.xda-developers.com/showthread.php?t=1138541
Problem is, after extracting the zip to C: and running "fastboot flash recovery C:\(image name).img", I get "fastboot is not recognized as an internal or external command..."
This leads me to believe that I don't have adb set up properly. I have standard adb set up for pushing apk's, but am I missing something specific for fastboot?
All i have under android-sdk-windows>platform-tools is adb.exe adbwinapi.dll and adbwinusbapi.dll. I DO have USB debugging on lol.
I seem to remember having more stuff under platform tools at an earlier date. All the threads for setting up adb are LONG buried, and after exhaustive searching, I finally gave up and decided to post (at least not in dev ). Even turning to google for adb help, I only get a bunch of the ad-farming tip websites that are outdated.
Please help me out guys. I can usually help myself after enough research, but I admit defeat on this one :/
Thanks much,
-omni
Click to expand...
Click to collapse
If your on linux it's "./moto-fastboot" not just fastboot.
Windows 7 64 bit. sorry, should have specified.
Nobody with win 7 knowledge/advice?
Alrighty, let us see here...
Try this.
1: Create a folder named fastboot (or whatever you prefer, just something simple like that) on the root of your C drive.
2: Download this file, http://www.mediafire.com/?yl17mz8l7w9h687
3: Unzip contents of said file into the folder you created in step 1
4: Click on Start, type cmd into the bar at the bottom and hit enter
5: Type cd C:\fastboot (or whatever you named the folder in step one)
6: Type moto-fastboot flash recovery recovery-en-goapk-0630-1029.img
That should work. The recovery included in the flash is current AS OF THIS POST. Obviously, the instructions will change if you download a newer copy of CWM as they are released, since the filename of the recovery file will change.
If you are wondering why it is moto-fastboot, the fastboot I included is the modified one that allows for larger img flashing. Not particularly useful anymore, with CWM working well now and all... but hey.
Diviance said:
Alrighty, let us see here...
Try this.
1: Create a folder named fastboot (or whatever you prefer, just something simple like that) on the root of your C drive.
2: Download this file, http://www.mediafire.com/?yl17mz8l7w9h687
3: Unzip contents of said file into the folder you created in step 1
4: Click on Start, type cmd into the bar at the bottom and hit enter
5: Type cd C:\fastboot (or whatever you named the folder in step one)
6: Type moto-fastboot flash recovery recovery-en-goapk-0630-1029.img
That should work. The recovery included in the flash is current AS OF THIS POST. Obviously, the instructions will change if you download a newer copy of CWM as they are released, since the filename of the recovery file will change.
If you are wondering why it is moto-fastboot, the fastboot I included is the modified one that allows for larger img flashing. Not particularly useful anymore, with CWM working well now and all... but hey.
Click to expand...
Click to collapse
Thanks SO much for the quick response and all the effort I'd actually updating OTA from 1.26 because I flashed back, thinking no one was gonna help! Well, when I feel up to it another night. I'll give this another shot. Thanks for the custom fastboot, too!
i get < waiting for device >
did i do something wrong?
Me too. ^^^^^^^
I figured it out, i forgot to put it into fastboot mode!
did not work for me
when I do what you told the other guy it says system cant find the path specified couls you please help I have spent a couple of days trying different things and also when I try to erase the recovery installer file it want let me
Ok, this will be a bit of a technical thread, so bear with me. This is so people have an understanding of how to find and look at the update files that get put on a phone. If you are reading thru this, I will assume that you have a basic understanding of ADB and possibly of shell commands like ls and cd
When you go into settings -> About Phone - Software update, your phone does many checks to the file system. One of them is at a file /data/fota/ipth-muc.prop . Most people do not know this directory exists as when you are in ADB you can not do a list command on the /data directory without root. This file is re-created each time you boot your phone. If we do the following command, we can dowload the file to our computer:
ADB pull /data/fota/ipth-muc.prop
If we open the file, it will look a lot like this.
firmware.version=VS920ZV3
max.pkg.size=157286400
This file can also contain additional data. The string we want to add in there is where to download and place update packages. This can be defined as such:
pkg.location=
If this line does not exist, it will default to /cache/fota . Being as we can not cd into /cache or pull/push files there, this is a bad spot to put it. How ever, we can make directories and read/write to them under /data/local . Using this info we can do the following.
ADB shell
mkdir /data/local/temp
exit
From there, we can edit the original ipth-muc.prop file we pulled to look like this:
firmware.version=VS920ZV3
max.pkg.size=157286400
pkg.location=/data/local/temp
If you edit the file, use a true file editor. Notepad will not save it correctly, but Wordpad had no issues. From there we do the following
ADB push ipth-muc.prop /data/fota
Now when we do the update, it will place the downloaded files into our temp directory (note, you must do this after the phone is fully booted, but before you have the phone look for an update). Once the files are done downloading, click remind me later. Then we can go into ADB and pull the files.
ADB pull /data/local/temp
You will get two files. One will be the update "ipth_package.bin" and the manifest files "ipth_package.bin.dd" . The manifest file also contains the link to the original file name as link to it on the host server. The ipth_package.bin file is a simple zip file that can be opened with almost any archiving program.
The zip is signed by LG using their personal key, so modifying it and pushing it back to the phone is not currently possible. We can however see the contents of an update and see what is being change. I hope to use this in the near future to either break the LG key or find a way to find a glitch in a patch being done.
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?
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