I rewrote TrueBlue_Drew's Splash Flasher for use on Linux systems.
Features:
Convert jpg, bmp, and png files to .img for flashing through the bootloader.
Backup current boot splash to .img folder
Convert .img splash to .png for editing on computer
Flash .img through bootloader automatically.
To use this tool you will need ffmpeg tool. To get run: sudo apt-get install ffmpeg
Also, to run either place both this conversion file and your photo in the folder with adb and fastboot or set up your path so those can be accessed from any folder (for details go here: http://goo.gl/a9k5m)
I will look into making a flashable zip file with this program in the coming days.
Final information: Be sure to click the thanks button at the bottom of this post and go here and thank TrueBlue_Drew: http://goo.gl/IqGoh
Updated file ENJOY: http://goo.gl/Tbkt8
Thanks a lot man! It works well on natty =)
Good to hear
Sent from my ThunderBolt using XDA Premium App
Would like to know if it's worth looking into making a create a flashable zip option.
Sent from my ThunderBolt using XDA Premium App
So I got some updates made. The file is now error free
Changelog:
Fixed the typo in png conversion
Added a pause before clear on all conversions so you can see if they throw an error.
When flashing the device will now wait for the device before rebooting for debugging.
Changed the wait for user input from read ... -n1 to needing an enter because sh was telling me that was illegal.
Fixed an error on exit
Properly Credited TrueBlue_Drew in opening comments
If you have any bugs, questions, or suggestions please pm me as I may not be able to check this daily.
ENJOY: http://goo.gl/Tbkt8
Hello all. I have been looking for this for a way to do this for a while now but i have finally discovered how to install the NEWEST iWnn IME on to the DHD with a custom ROM. Quite simple actually.
Get the iWnnIME.zip by googling.
save it to your SDcard.
Install it using the Clockwork Recovery mode and install zip from sdcard.
Restart phone
You will have the IME installed. OLD crappy version not for the DHD....
To update to the more user friendly version ACTUALLY FOR the DHD:
You need to extract the iWnnime.apk from either a NANDROID backup or a RUU from softbank FOR YOUR DHD
Howto: Nandroid.
Download unyaffs for windows
copy your nandroid backup to the same directory as the unyaffs exe and the cigwin1 file.
Open a CMD window and cd into the directory with unyaffs
Type unyaffs system.img
This will extract the folders contained within system.img.
Once extracted open the app folder and find iWnnime.apk file and simply copy it to your sd card, put it in your phone and using an explorer type software go to the sd card and intall the apk.
Done! You should now have the NON crappy version 1.40
so i was trying some stuff and turns out it works so i dont know if anyone would want this but it helps if you flash kernels through fastboot.
So what you do is :
1. open a fresh notepad, ( hit the windows button, type notepad then enter )
2. type: START fastboot flash boot boot.img
3. save as or just save, then make sure the extension is .bat
( example : flashkernel.bat ) and save it to the folder where your adb and fastboot are. usually the platform-tools folder
4. make sure the option under extension is selected as all files. or it will save as .txt file
5. run the bat file while you are in fastboot and you will see it works.
again i dont know if this should be here so mods, delete if you think it should be deleted. just let me know i can put it in general if needed.
hit that thanks button if this was usefull
Marshmellow92 said:
so i was trying some stuff and turns out it works so i dont know if anyone would want this but it helps if you flash kernels through fastboot.
So what you do is :
1. open a fresh notepad, ( hit the windows button, type notepad then enter )
2. type: START fastboot flash boot boot.img
3. save as or just save, then make sure the extension is .bat
( example : flashkernel.bat ) and save it to the folder where your adb and fastboot are. usually the platform-tools folder
4. make sure the option under extension is selected as all files. or it will save as .txt file
5. run the bat file while you are in fastboot and you will see it works.
again i dont know if this should be here so mods, delete if you think it should be deleted. just let me know i can put it in general if needed.
hit that thanks button if this was usefull
Click to expand...
Click to collapse
It's often referred to as batch file programming
Sent from my HTC PH39100 using xda premium
thanks ;p lol
i was not really sure if it would work but then i used this and it worked it beats having to type put fastboot flash boot boot.img haha. but i made one for the recovery as well and im trying to see what i can do with this and see if i can try to make a one click root with a cmd window
Hello everyone,
I've been playing around with adding root to my stock ROM these past few days, and have found it very slow and tedious trying to remember all the commands to unpack and repack the images.
To make things simpler I've created a script that automates almost the whole process.
I've named it worker as it does all the work for you, and it is just simply a bash script. But it makes things a lot quicker and easier.
I have only been able to test with my S3 Mini, but should work with any ROM that has boot.img and system.img
Simply extract the .img files from the tar.md5 or .zip ROM file, and place them in the original folder.
Once you have those in the original folder just simply run the worker.txt file from the terminal, making sure you are in the worker folder directory.
When the script is run you will be given the options to unpack/repack system.img, mount system.img (This is after you extract it do not try and mount the original file it wont work), unpack/repack boot.img, unpack/repack ramdisk, create ROM (This will create an odin flashable tar.md5 from the repacked files) and finally clean up (This will clear all unpacked and repacked files only leaving the files in the original folder)
To select an option simply type y then enter to execute that command or just hit enter to skip.
When the system.img is mounted it will be mounted in the mount folder.
When repacking the system.img you will be prompted to enter the file size, if you have and S3 Mini I8190N simply type s3mini for the size (This may work for other S3 models but I have no way of testing so let me know). If you have a different device use the file size of the original UNMODIFIED system.img, enter the size in bytes or MB (If entering in MB use this format, xxx being a number. xxxM).
Please give me feedback for improvements or problems,
Thanks for reading.
P.S. Sorry if in wrong place please move if necessary
EDIT: If you can't run the script with the ./ command, chmod +x the file
Antonyb1995 said:
Hello everyone,
I've been playing around with adding root to my stock ROM these past few days, and have found it very slow and tedious trying to remember all the commands to unpack and repack the images.
To make things simpler I've created a script that automates almost the whole process.
I've named it worker as it does all the work for you, and it is just simply a bash script. But it makes things a lot quicker and easier.
I have only been able to test with my S3 Mini, but should work with any ROM that has boot.img and system.img
Simply extract the .img files from the tar.md5 or .zip ROM file, and place them in the original folder.
Once you have those in the original folder just simply run the worker.txt file from the terminal, making sure you are in the worker folder directory.
When the script is run you will be given the options to unpack/repack system.img, mount system.img (This is after you extract it do not try and mount the original file it wont work), unpack/repack boot.img, unpack/repack ramdisk, create ROM (This will create an odin flashable tar.md5 from the repacked files) and finally clean up (This will clear all unpacked and repacked files only leaving the files in the original folder)
To select an option simply type y then enter to execute that command or just hit enter to skip.
When the system.img is mounted it will be mounted in the mount folder.
When repacking the system.img you will be prompted to enter the file size, if you have and S3 Mini I8190N simply type s3mini for the size (This may work for other S3 models but I have no way of testing so let me know). If you have a different device use the file size of the original UNMODIFIED system.img, enter the size in bytes or MB (If entering in MB use this format, xxx being a number. xxxM).
Please give me feedback for improvements or problems,
Thanks for reading.
P.S. Sorry if in wrong place please move if necessary
Click to expand...
Click to collapse
work on gt-i8200n to?
linklusitano said:
work on gt-i8200n to?
Click to expand...
Click to collapse
No reason why not, I'm just not able to test others
Antonyb1995 said:
No reason why not, I'm just not able to test others
Click to expand...
Click to collapse
testing
linklusitano said:
testing
Click to expand...
Click to collapse
Great let me know if it works!
EDIT: Make sure you enter the right size for the system.img file, the pre entered size using s3mini may work fine as they are very similar devices.
Antonyb1995 said:
Great let me know if it works!
EDIT: Make sure you enter the right size for the system.img file, the pre entered size using s3mini may work fine as they are very similar devices.
Click to expand...
Click to collapse
how do i run worker.txt?
linklusitano said:
how do i run worker.txt?
Click to expand...
Click to collapse
Your using Linux right?
Open a terminal and change directory to the worker folder, once there type ./worker.txt and it should run. If it doesn't issue this command chmod +x worker.txt that should fix it.
Antonyb1995 said:
Your using Linux right?
Open a terminal and change directory to the worker folder, once there type ./worker.txt and it should run. If it doesn't issue this command chmod +x worker.txt that should fix it.
Click to expand...
Click to collapse
windows 8.1
linklusitano said:
windows 8.1
Click to expand...
Click to collapse
Ah okay, If you install Cygwin you can run bash scripts in Windows.
LINK: https://www.cygwin.com/
Hi,
Here is how you can change or create your own bootlogo for Infinix Hot 2 with ease!
Disclaimer:
Code:
Standard disclaimer always applies.
I'm NOT responsible of any damage to your device if you
follow an even small part of this tutorial.
If something wrong happens, consider it as fate
and live with it!
What you need:
- A Windows Computer
- Logo Builder from here mega.co.nz
- A bootlogo of your choice, or an image of your choice (images must be 720x1280)
Click to expand...
Click to collapse
Instructions:
1) Create a folder on your desktop or somewhere you wish and name it STOCK LOGO. If you want to port a Logo (assuming you have the bootlogo you want to port), then also create another folder and name it PORT LOGO.
2) Unzip LogoBuilder_v1.6.zip and open the unzipped folder. Double click on LogoBuilder.exe
3) Click on "Create new project". Locate your stock logo.bin . Now point to STOCK LOGO folder. It will extract your stock logo to that folder. If you want to use another device's bootlogo, then repeat this step with port logo , but choose port logo.bin and point it to PORT LOGO.
4) Now, if you want to use your own picture as logo, then go with a) otherwise, go with b)
a) - Copy your image to STOCK LOGO folder. Images must be in PNG format and resolution must be 720x1280 (this is very important)
- Delete img1.png and img39.png from STOCK LOGO
- Copy your image to STOCK LOGO and name it img1.png
- Copy it again to STOCK LOGO and name it this time to img39.png
b) If you want to use a device's boot logo. Then follow. (If image size isn't 720x1280, you obviously need to resize it!)
- Assuming that you already unpacked the port logo.bin to PORT LOGO
- Go to PORT LOGO folder, copy img1.png and paste it in STOCK LOGO (replace when prompted).
- Go to PORT LOGO folder, copy img1.png and paste it on your DESKTOP. Rename it to img39.png .
- Copy it from your DESKTOP to STOCK LOGO folder.
5) Go back to Logo Builder and click on "Make" button.
When done, you w'ill find your new logo.bin inside STOCK LOGO folder. There will also be a flashable zip BUT DON'T FLASH THAT FILE! I suggest you take the logo.bin inside that zip archive instead and flash it with SP Flash tools. If you still want to flash with Recovery. Then download this file META-INF (mega.co.nz) and extract it, put the created new logo.bin and the extracted META-INF folder inside a folder. Zip both files and flash via Recovery.
Credits:
kadan for the awesome tool @ Google Sites
KUL let me check it out