Database Info

[TOOL] [Linux / OSX] Splash Screen creator / flasher

Hello there!
This is a G1 / Magic tool to easily convert images in splash screen ones.
This tool is based upon ffmpeg and you need it installed on your system before proceeding (it will prompt you about the program missing in any case)
REQUIREMENTS
ffmpeg installed on your system
a 320x480 image
a 320x480 device (i.e. G1 / Magic) with engineering SPL
USAGE
Code:
./file [--help][-h]
Prints out how to use the script
Code:
./file your_image_file
Converts your image into a flashable splash screen, if you want the script will continue flashing the file directly.
NOTE: if you wish to make this script work with the Nexus One or any other device which doesn't share the same 320x480 resolution, just change these two variables:
Code:
size_check=307200
size_desc="320x480"
size_check is in bytes, size_desc is just a descriptive string.
I ASSUME NO RESPONSABILITY ABOUT THE USAGE OF THIS SCRIPT. USE IT "AS IS", LOOK AT THE OUTPUTS AND YOU'LL AVOID BRICKS!
Please, if you wish to redistribute this script, give the right credits and don't change the prog_header please (maybe link this discussion in a text file)!
Here the code is, just slap it in a text file, give it the executive permission (chmod +x filename) and use it!
Code:
#!/bin/bash
prog_header() {
echo "###############################"
echo "####### EleGoS's FFMPEG #######"
echo "# G1/Sapphire/MyTouch3G/Magic #"
echo "### Splash Screen converter ###"
echo "###############################"
echo "version 1.0"
echo ""
}
if [ "$1" == "--help" ] || [ "$1" == "-h" ]; then
prog_header
echo "Usage"
echo "$0 your_image_file"
exit 0
fi
warning() {
printf "\e[0;31m$1\e[0m \n"
}
check_ok() {
printf "\e[0;32m$1\e[0m \n"
}
ffmpeg_check=$(which ffmpeg)
size_check=307200
size_desc="320x480"
if [ "$ffmpeg_check" != "" ]; then
OUTPUT=$(echo "$1" | cut -d'.' -f1).raw565
clear
prog_header
ffmpeg -i $1 -f rawvideo -pix_fmt rgb565 $OUTPUT
clear
prog_header
FILESIZE=$(cat $OUTPUT | wc -c)
if [ $FILESIZE -eq $size_check ]; then
check_ok "$OUTPUT is ready to be flashed."
else
rm $OUTPUT
warning "$OUTPUT filesize mismatches! Wrong image size ($size_desc)? Aborted."
exit 0
fi
echo "In order to flash this image you have to plug your phone in fastboot mode."
read -p "Flash it now? (y/n) "
if [ "$REPLY" == "y" ] || [ "$REPLY" == "Y" ]; then
fastboot devices | grep -q "fastboot"
if [ $? -ne 0 ]; then
warning "The USB cable is not plugged, or the device is not in fastboot mode."
echo "To flash the splash screen, manually execute this command once in fastboot mode:"
echo "fastboot flash splash1 $OUTPUT"
exit 0
else
fastboot flash splash1 $OUTPUT
fi
else
echo "To flash the splash screen, execute this command once in fastboot mode:"
echo "fastboot flash splash1 $OUTPUT"
exit 0
fi
else
warning "ffmpeg not found! Please install it before running this script!\ni.e. (DEBIAN) apt-get install ffmpeg / (OSX) sudo port install ffmpeg"
fi
Some ready-to-flash raw565 images (link on the images):

Thanks, this simplifies the process Works great on my Mac OSX SL.

Where can i download it for the Mac would love to create my own Splash Screen..

You need:
- MacPorts installed
- ffmpeg installed via macports (sudo port install ffmpeg)
- Open the terminal -> nano splash_creator
- copy / paste the code
- [CTRL]+O, then [ENTER]. [CTRL]+X
- chmod +x splash_creator
- Put the image you want as splash screen in a folder where the script is (it is actually in your home)
- Open terminal -> cd your/folder/here
- ./splash_creator your_image_here.whatever

great tools
really great tools man .. works really nice on my ubuntu ..
anyway, have any idea how to create the boot animation?

nope, I only know it's in /system/media/bootanimation.zip (at least in the latest cyanogenmod), but I haven't figured out how's supposed to be created =\

splash
Thank you guys.
The best/simple guide to change boot splash screen in 1 minute!
I've only added "sudo" to my ubuntu terminal to run it!
my own splash
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Thanks!
Wow, thanks, works like a charm.
For anyone who happens to like Jeanne d'Arc (Joan of Arc), here is my splash screen, feel free to use it:
And an associated boot animation
(I wrote my undergrad thesis about her)
Thanks again!

ok where is the link lol?

elegos said:
You need:
- MacPorts installed
- ffmpeg installed via macports (sudo port install ffmpeg)
- Open the terminal -> nano splash_creator
- copy / paste the code
- [CTRL]+O, then [ENTER]. [CTRL]+X
- chmod +x splash_creator
- Put the image you want as splash screen in a folder where the script is (it is actually in your home)
- Open terminal -> cd your/folder/here
- ./splash_creator your_image_here.whatever
Click to expand...
Click to collapse
You don't necessarily need to download macports. Just grab an ffmpeg binary from wherever (included in lots of software distributions on Mac, like the KMTTG TiVo file decoder, Handbrake, etc) and just do it from the command line.
ffmpeg -i mygraphic.jpg -f rawvideo -pix_fmt rgb565 mygraphic.raw656

elegos said:
size_check=307200
size_desc="320x480"
Click to expand...
Click to collapse
I have an EVO the size is 480x800 the size _desc= would be 480x800 what would be the size_check=
Not sure how to calc the value
thanks

@mplaines: for 480x800 it needs to be 768000
Works great for my Desire, thanks for the script!

Very nice and useful, thanks a bunch, I will definately keep the header and credits. Also you may want to add to your OP to install ffmpeg just do $ sudo apt-get install ffmpeg

The low-dough ghetto version
I have a Mac and found an interesting way to work around...
Get an image editor (I used Gimp) and create a 320 x 480 BMP of your splash image.
Flip it vertically so that it looks upside down and backwards.
Save it as a bitmap (.bmp) and select the 565 setting.
Use a hex editor to strip off the first 70 bytes of the header. That's 70 in decimal, not hex! To confirm, the resulting file size should be 307,200 bytes exactly.
Flash away!
If you are flashing a 480 x 800 image to an HDPI device, the file size will be 768,000 bytes and not a nibble more.

gee one said:
I have a Mac and found an interesting way to work around...
Get an image editor (I used Gimp) and create a 320 x 480 BMP of your splash image.
Flip it vertically so that it looks upside down and backwards.
Save it as a bitmap (.bmp) and select the 565 setting.
Use a hex editor to strip off the first 70 bytes of the header. That's 70 in decimal, not hex! To confirm, the resulting file size should be 307,200 bytes exactly.
Flash away!
If you are flashing a 480 x 800 image to an HDPI device, the file size will be 768,000 bytes and not a nibble more.
Click to expand...
Click to collapse
I didn't have to mess around in gimp and rotate things, just us the script and you'll have no problems

Repost?
I have reposted this for the G1 section, just kept the OP from here the same as there and gave you all credits. Also here are my splash screens, more to come!

I'd really like if this would work on the Nexus One too... haven't found anything about!

if i read correctly what this does. it changes the UGLY green mytouch3g logo before the boot animation? if so i'm interested.. where can i get linux copies of fastboot and Adb?

Very Nice work .. Good instructions

[DUMP] Sidekick 4G Partition + Kernel Source (Bootloader, Recovery, etc)

Credit to sofauxboho for performing dumps.
Partition Dump
http://gititbit.ch/sk4g2 - partition dump
Code:
bml1 256 KB contains boot.bin (262144 bytes), Primary Boot Loader (low-level hardware initialization)
bml2 256 KB contains PIT file first 512 bytes
bml3 10240 KB /dev/block/stl3 /efs
bml4 1280 KB contains Sbl.bin (1310720 bytes) Secondary Boot Loader (loads the Linux kernel and passes the necessary arguments)
bml5 1280 KB contains Secondary Boot Loader (for recovery, ect)
bml6 5120 KB param.lfs /mnt/.lfs j4fs
bml7 7680 KB contains zImage and initramfs
bml8 7680 KB empty - on Epic 4G and Fascinate, contains recovery.bin
bml9 293376 KB factoryfs.rfs ( /system RFS Partition) /dev/block/stl9
bml10 137216 KB dbdata.rfs ( /dbdata RFS Partition) /dev/block/stl10
bml11 35840 KB cache.rfs ( /cache RFS Partition) /dev/block/stl11
bml12 12800 KB modem.bin
EDIT: It has come to my attention that the Super One Click works, no need for a script.
More Mirrors
http://gititbit.ch/sk41 - Sidekick 4G system dump
http://gititbit.ch/sk4g1 - Sidekick 4G Info Dump
dev.txt
devblock.txt
efs.txt
mount.txt
partitions.txt
proc.txt
Kernel + Platform Source
http://gititbit.ch/sk4g5 - SGH-T839_OpenSource.zip
Now for custom roms...
SK4G development chat can be found at irc.freenode.net #sk4g

hey, sorry i'm not super code-savvy.... do i simply place the .rar file on my sd card, or open it with say, 7zip, and copy the autoroot folder over? i'm getting 'unable to chmod, operation not permitted' the second way, and 'not found, no such directory, etc' when i place the .rar file on my sd card. both of these are appearing after the first line with chmod 755 etc.

Use winrar to extract the .rar then place the extracted folder onto the sdcard.

dasmoover said:
Use winrar to extract the .rar then place the extracted folder onto the sdcard.
Click to expand...
Click to collapse
ok, think i did that, but am still getting 'operation not permitted'..... perhaps i'll hold off and see if someone else has success with it?

Hmm...
Should line 14 specify the su file rather than the containing directory?
It currently reads:
Code:
cp su /system/xbin/ && chmod 4755 /system/xbin/
But perhaps it should read:
Code:
cp su /system/xbin/ && chmod 4755 /system/xbin/su

Updated the script in the main download.

yogi2010 said:
hey, sorry i'm not super code-savvy.... do i simply place the .rar file on my sd card, or open it with say, 7zip, and copy the autoroot folder over? i'm getting 'unable to chmod, operation not permitted' the second way, and 'not found, no such directory, etc' when i place the .rar file on my sd card. both of these are appearing after the first line with chmod 755 etc.
Click to expand...
Click to collapse
Im getting this when I try the lines too.

When I copied the autoroot folder to my SK4G, the contents of the folder were already set to 775, so there should be no need to chmod (though I also get the permission error when trying to chmod them).
The bigger issue is that my device doesn't have the cp command. I'd assume it would be in /system/bin along with things like ls and mv, but it's not.

Huh. That's odd. You guys are using the newer download, right?
Do you have any idea which chmod command is erroring out? I'm wondering if it's the chmod on the rage...bin in line 9 or the chmod on su in line 14.
Unfortunately I can't test without wiping my SK4G back to unrooted, which I would rather not do as it's my primary handset.
If you don't know which line is causing the trouble, could you try copying the kit but then entering each line manually?

sofauxboho said:
Huh. That's odd. You guys are using the newer download, right?
Do you have any idea which chmod command is erroring out? I'm wondering if it's the chmod on the rage...bin in line 9 or the chmod on su in line 14.
Unfortunately I can't test without wiping my SK4G back to unrooted, which I would rather not do as it's my primary handset.
If you don't know which line is causing the trouble, could you try copying the kit but then entering each line manually?
Click to expand...
Click to collapse
No I was usin the old link didn't try new one yet. Still says same thing on new version
Sent From SK4G

sofauxboho said:
Huh. That's odd. You guys are using the newer download, right?
Do you have any idea which chmod command is erroring out? I'm wondering if it's the chmod on the rage...bin in line 9 or the chmod on su in line 14.
Unfortunately I can't test without wiping my SK4G back to unrooted, which I would rather not do as it's my primary handset.
If you don't know which line is causing the trouble, could you try copying the kit but then entering each line manually?
Click to expand...
Click to collapse
I tried the newer download. All of the chmods error because my user doesn't own those files or already have write permissions for any of them. I don't have read, write, or execute permissions for /data/local/tmp either, so I can't list or copy to that location. But, separate from that, there is no cp command, so I can't copy anything anywhere.

jarrodlombardo said:
When I copied the autoroot folder to my SK4G, the contents of the folder were already set to 775, so there should be no need to chmod (though I also get the permission error when trying to chmod them).
The bigger issue is that my device doesn't have the cp command. I'd assume it would be in /system/bin along with things like ls and mv, but it's not.
Click to expand...
Click to collapse
Ah, right! That's why I used cat instead of cp when I rooted mine.
Try this:
Code:
#!/bin/sh
#autoroot script for sidekick v0.1
#chmod 755 autoroot.sh
echo "Copying binaries to /data/local/tmp/"
cat su > /data/local/tmp/su
cat Superuser.apk > /data/local/tmp/Superuser.apk
cat rageagainstthecage-arm5.bin > /data/local/tmp/rageagainstthecage-arm5.bin
cd /data/local/tmp/
echo "I'm about to chmod rageagainstthecage-arm5.bin"
chmod 755 rageagainstthecage-arm5.bin
echo "Executing exploit, please wait"
./rageagainstthecage-arm5.bin
sleep 20
echo "Attempting to spawn root shell"
sh
whoami
echo "Attempting to mount /system read-write"
mount -o remount,rw /dev/block/stl9 /system
echo "Attempting to copy and chmod su"
cat /data/local/tmp/su > /system/xbin/su && chmod 4755 /system/xbin/su
echo "Attempting to copy Superuser.apk"
cat /data/local/tmp/Superuser.apk > /system/app/Superuser.apk
sleep 5
mount -o remount,ro /dev/block/stl9 /system
#add root entry to passwd and group
echo "root::0:0:root:/data/local:/system/bin/sh" > /etc/passwd
echo "root::0:" > /etc/group
echo "autoroot completed succesfully."
I've also added a bunch of echoed comments to help us track where things go wrong if it doesn't work.

sofauxboho said:
Ah, right! That's why I used cat instead of cp when I rooted mine.
Try this:
Code:
#!/bin/sh
#autoroot script for sidekick v0.1
#chmod 755 autoroot.sh
echo "Copying binaries to /data/local/tmp/"
cat su > /data/local/tmp/su
cat Superuser.apk > /data/local/tmp/Superuser.apk
cat rageagainstthecage-arm5.bin > /data/local/tmp/rageagainstthecage-arm5.bin
cd /data/local/tmp/
echo "I'm about to chmod rageagainstthecage-arm5.bin"
chmod 755 rageagainstthecage-arm5.bin
echo "Executing exploit, please wait"
./rageagainstthecage-arm5.bin
sleep 20
echo "Attempting to spawn root shell"
sh
whoami
echo "Attempting to mount /system read-write"
mount -o remount,rw /dev/block/stl9 /system
echo "Attempting to copy and chmod su"
cat /data/local/tmp/su > /system/xbin/su && chmod 4755 /system/xbin/su
echo "Attempting to copy Superuser.apk"
cat /data/local/tmp/Superuser.apk > /system/app/Superuser.apk
sleep 5
mount -o remount,ro /dev/block/stl9 /system
#add root entry to passwd and group
echo "root::0:0:root:/data/local:/system/bin/sh" > /etc/passwd
echo "root::0:" > /etc/group
echo "autoroot completed succesfully."
I've also added a bunch of echoed comments to help us track where things go wrong if it doesn't work.
Click to expand...
Click to collapse
Type this into terminal right?

Actually, I whipped up a modified version of dasmoover's tool with my changes:
http://notfine.com/android/sk4g/autoroot-V01b-sfb.zip
Unzip that and copy the "autoroot" folder to your SD card.
Next, eject your SK, turn off USB Storage mode, and unplug it from your computer.
Then follow dasmoover's instructions (I've cleaned them up slightlly):
1. Place autoroot folder on sdcard
2. Install the Terminal Emulator app from the Marketplace
3. Open the Terminal Emulator app and type the following commands exactly, one at a time, hitting enter at the end of the line:
Code:
chmod 755 /sdcard/autoroot/autoroot.sh
./sdcard/autoroot/autoroot.sh
If the sdcard is mounted as noexec, follow these steps:
1. Place autoroot folder on sdcard
2. Install the Terminal Emulator app from the Marketplace
3. Open the Terminal Emulator app and type the following commands exactly, one at a time, hitting enter at the end of the line:
Code:
cat > /sdcard/autoroot/autoroot.sh /data/local/tmp/autoroot.sh
chmod 755 /data/local/tmp/autoroot.sh
cd /sdcard/autoroot/
./data/local/tmp/autoroot.sh
Click to expand...
Click to collapse
All credit to dasmoover, btw! Thanks, and I hope you don't mind me modifying and repackaging your tool. Just trying to help get it working.

BTW, here are some good goodies on how this root exploit works for the technical and curious:
I'd read this one first: http://intrepidusgroup.com/insight/2010/09/android-root-source-code-looking-at-the-c-skills/
And this one second:
http://dtors.org/2010/08/25/reversing-latest-exploid-release/

How did you get rid of the $ sign and get a # ? When I type the first line with the ca it sayd directory can't be found.
Sent From SK4G

I copied the new cat version onto my device and did the following:
$ chmod 755 /sdcard/autoroot/autoroot.sh
Unable to chmod /sdcard/autoroot/autoroot.sh: Operation not permitted
$ cat /sdcard/autoroot/autoroot.sh > /data/local/tmp/autoroot.sh
Cannot create /data/local/tmp/autoroot.sh: permission denied
So, I'm still stuck since /data/local/tmp isn't writable. (Also, you'll note I fixed the small error in the cat line I used.)

Ace42 said:
How did you get rid of the $ sign and get a # ? When I type the first line with the ca it sayd directory can't be found.
Sent From SK4G
Click to expand...
Click to collapse
So, the # means root. The $ means not root. The whole point of this is to get the #, which indicates a root prompt.
If it says the directory can't be found then either the command was typed incorrectly or the files are in the wrong place. The files have to be in the exact right places with the exact right names.
Download my modified version:
http://notfine.com/android/sk4g/autoroot-V01b-sfb.zip
Unzip it, and it should give you a folder called "autoroot". Inside that should be four files:
autoroot.sh
rageagainstthecage-arm5.bin
su
Superuser.apk
Make sure there is only a folder named "autoroot" with those four files inside. If there is another directory inside it won't work. If the names are at all different it won't work.
Copy this "autoroot" folder to the top level of your SD card. There should be other folders there like Music, DCIM, Playlists, and Android. Maybe some others. Make sure it's at the very top level, along with these other directories.
Here, take a look at my directory structure:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(Yes, I'm on a Mac, but your SK and Android don't care. File locations work the same on Windows or Linux or whatever. Also, I may have some folders you don't have. That's ok.)
Next, eject your SK, turn off USB Storage mode, and unplug it from your computer. **I forgot this part earlier! It's important.**
Then open up Terminal Emulator an your SK4G. Type:
Code:
cd /sdcard/autoroot
Then type:
Code:
ls
This should list the same four files above. If it does, you're ready to start the instructions I posted previously.
If it doesn't, type:
Then type:
Code:
ls /sdcard/
Let me know what it says.

jarrodlombardo said:
I copied the new cat version onto my device and did the following:
$ chmod 755 /sdcard/autoroot/autoroot.sh
Unable to chmod /sdcard/autoroot/autoroot.sh: Operation not permitted
$ cat /sdcard/autoroot/autoroot.sh > /data/local/tmp/autoroot.sh
Cannot create /data/local/tmp/autoroot.sh: permission denied
So, I'm still stuck since /data/local/tmp isn't writable. (Also, you'll note I fixed the small error in the cat line I used.)
Click to expand...
Click to collapse
Yeah, I've confirmed this problem.
Folks, this thing won't work right now. We need a location that is both writable and allows execution. Any ideas?
(To confirm, you can still root by using adb to manually put these files at /data/local/tmp/ For some reason, adb has rights to this location. However, the standard Terminal Emulator does not. This is only a hang-up for on-device rooting, not rooting in general.)

sofauxboho said:
Yeah, I've confirmed this problem.
Folks, this thing won't work right now. We need a location that is both writable and allows execution. Any ideas?
Click to expand...
Click to collapse
I've poked around some and not found anywhere yet. :/

[TOOL][WINDOWS][RECOVERY][SYSTEM][SNAPS][VIDEO][GUI]android-shot! (version 2.1)

#android-shot
#your one stop screenshot solution!
#screenshot recovery for windows!
#screenshot system for windows!
#video_record recovery for windows!
#video_record system for windows!
Looking for a Linux Version???
Go Here: http://forum.xda-developers.com/showthread.php?t=2260704
This solely uses the SD Card, which, by default is always kept mounted by
a partition. So, you wouldn't run into any trouble except when you try to
partition or format the SD Card.
I repeat, no need to mount any partition... By default, the SD Card is always mounted, so, I thought using it will be way better than using the /data partition
To take a screenshot:
Code:
Run "shot.bat"
Your screenshot will be saved in a folder named screenshots automatically.
To capture video:
Code:
Run "record.bat"
Press "Ctrl+C" when you have finished recording.
This will basically start recording your screen frame by frame, and automatically
save it in your SD card. Note that recording the video alone is not enough.
Do the following to pull those frames from the SD card, and make a video out of them.
Code:
Run "mkvideo.bat"
Enter the Name that you want to name your video. DON'T ADD AN EXTENSION!
The files will be collected from the SD Card, and a video will be made out
of them. Then, the temporary files will be cleaned automatically, from both
your SD card, and your system.
Downloads:
Version 2.1 (GUI) (Android-Andi): http://forum.xda-developers.com/showpost.php?p=45891403&postcount=59
Version 2.1.3 (Android-Andi): http://forum.xda-developers.com/showpost.php?p=44447366&postcount=40
Version 2.1.2 (Android-Andi): http://forum.xda-developers.com/showpost.php?p=44288806&postcount=36
Version 2.0.1 (Android-Andi): http://forum.xda-developers.com/showpost.php?p=44011267&postcount=17
Version 2.0 (Thanks to Android-Andi): http://forum.xda-developers.com/showpost.php?p=43982996&postcount=12
Version 1.0: http://www.mediafire.com/download/26gi88xdd5c6rly/android-shot_windows.zip
Note: A GUI version can be found here: http://forum.xda-developers.com/showpost.php?p=45891403&postcount=59
Not personally tested by me, as I don't have the appropriate tools (i.e. windows) no more...
Credits:
Kyan He (https://plus.google.com/116857119889961125943) and his wonderful tool "fb2png" (https://code.google.com/p/android-fb2png/)
Whiskey103 (http://forum.xda-developers.com/member.php?u=2632943) and his guide (http://forum.xda-developers.com/showthread.php?p=40260716) on taking screenshot in windows.
Android-Andi (http://forum.xda-developers.com/member.php?u=5153662) for version 2.0 and some cool ideas
Sample:
Recovery!
Recovery & System Video Sample! [With instructions ]

not working and said
"ECHO off 'and' is not recognized as an internal or external command, operable program or batch file.
'C:\Doccuments' is not recognized as an internal or external command, operable program or batch file.
will try your linux version, when get home

Strange....
antutu said:
not working and said
"ECHO off 'and' is not recognized as an internal or external command, operable program or batch file.
'C:\Doccuments' is not recognized as an internal or external command, operable program or batch file.
will try your linux version, when get home
Click to expand...
Click to collapse
Anyways, thanks for your report
I will look into it, as soon as possible
P.S. Only problem is... I don't have Windows :silly: So, it would be a beta :angel:

vineethraj49 said:
Anyways, thanks for your report
I will look into it, as soon as possible
P.S. Only problem is... I don't have Windows :silly: So, it would be a beta :angel:
Click to expand...
Click to collapse
Take your time mate:thumbup:

Sorry bro i just found out how this can work out
I've to put it in root folder
It's working great now:thumbup::thumbup:

Thanks al lot! That´s what i was looking for.
I tried to get better Video-Quality (libx264 as *.mp4).
I modified the .bat
Code:
ECHO off
REM snaps mode
REM fb2png credits go to respective developers
REM thanks to whiskey103 for his screenshot.bat for windows
REM thanks to vineethraj49 for his mkvideo.bat (video as *.avi)
REM thanks to me and my computer
IF EXIST %~dp0tmp ECHO tmp directory found! :)
IF NOT EXIST %~dp0tmp ECHO tmp directory not found! :( && MKDIR tmp && ECHO initialised new tmp directory! :)
IF EXIST %~dp0output_video ECHO output_video directory found! :)
IF NOT EXIST %~dp0output_video ECHO output_video directory not found! :( && MKDIR output_video && ECHO initialised new output_video directory! :)
%~dp0tools\adb pull /sdcard/fb2png/screens/ tmp
SET /P name=Enter the name for your video:
%~dp0tools\ffmpeg.exe -f image2 -r 2 -i tmp/1%%09d.png -c:v libx264 -r 30 output_video/%name%.mp4
%~dp0tools\adb shell rm /sdcard/fb2png/screens/*
rm tmp/*
REM hit enter to exit
pause
Someone knows how to make the quality better then with my modified bat?

Me again:
To use your shot.bat i had to download 2 *.dll´s to get "date.exe" working (libiconv2.dll and libintl3.dll). Without these .dll screenshot not possible.
Maybe you can add these two *.dll into your tool directory (don´t know if it´s allowed, check it here).
Download (GnuWin) Libintl.exe(?) from here and install it.
You´ll find the 2 needed *.dll at "C:\Program Files (x86)\GnuWin32\bin".
I´m, running Windows 8 Pro.

Maybe you can add (after changeing directory path) my modified "record.bat" for taking screenshots from running androidsystem
Code:
@ECHO off
REM Record_running_Android
IF EXIST %~dp0new ECHO new directory found! :)
IF NOT EXIST %~dp0new ECHO new directory not found! :(
mkdir new
ECHO initialised new directory! :)
:loop
%~dp0tools\adb shell screencap -p /extSdCard/screen.png
%~dp0tools\adb pull /extSdCard/screen.png %~dp0new
%~dp0tools\adb shell rm /extSdCard/screen.png
FOR /F "tokens=*" %%i in ('%~dp0tools\date.bat') do SET DATE=%%i
MOVE %~dp0new\screen.png %~dp0new\%DATE%.png
goto loop
pause
I´m using extSdCard as directory, because my Micro-SD-Card is mounted there.
Maybe change it like this:
Code:
@ECHO off
REM Record_running_Android
IF EXIST %~dp0new ECHO new directory found! :)
IF NOT EXIST %~dp0new ECHO new directory not found! :(
mkdir new
ECHO initialised new directory! :)
:loop
%~dp0tools\adb shell screencap -p /sdcard/screen.png
%~dp0tools\adb pull /sdcard/screen.png %~dp0new
%~dp0tools\adb shell rm /sdcard/screen.png
FOR /F "tokens=*" %%i in ('%~dp0tools\date.bat') do SET DATE=%%i
MOVE %~dp0new\screen.png %~dp0new\%DATE%.png
goto loop
pause

Whoa! Someone actually cares
Android-Andi said:
Thanks al lot! That´s what i was looking for.
I tried to get better Video-Quality (libx264 as *.mp4).
I modified the .bat
Code:
ECHO off
REM snaps mode
REM fb2png credits go to respective developers
REM thanks to whiskey103 for his screenshot.bat for windows
REM thanks to vineethraj49 for his mkvideo.bat (video as *.avi)
REM thanks to me and my computer
IF EXIST %~dp0tmp ECHO tmp directory found! :)
IF NOT EXIST %~dp0tmp ECHO tmp directory not found! :( && MKDIR tmp && ECHO initialised new tmp directory! :)
IF EXIST %~dp0output_video ECHO output_video directory found! :)
IF NOT EXIST %~dp0output_video ECHO output_video directory not found! :( && MKDIR output_video && ECHO initialised new output_video directory! :)
%~dp0tools\adb pull /sdcard/fb2png/screens/ tmp
SET /P name=Enter the name for your video:
%~dp0tools\ffmpeg.exe -f image2 -r 2 -i tmp/1%%09d.png -c:v libx264 -r 30 output_video/%name%.mp4
%~dp0tools\adb shell rm /sdcard/fb2png/screens/*
rm tmp/*
REM hit enter to exit
pause
Someone knows how to make the quality better then with my modified bat?
Click to expand...
Click to collapse
Remember that the *quality* is always the same. It pulls the images (frames) in the same resolution as of your phone. If you are talking about the FPS, you should modify this line...
Code:
ffmpeg -r 4
The -r switch controls the FPS.
Again, the FPS depends upon how many screens are actually captured by your device. If you have a fast SD-Card, and a fast processor, it is indeed likely that the frames captured would be more. You can try increasing the -r 4 by 2/3 frames and see if the video is suitable to your needs. (eg. -r 5/ -r 6, etc...)
Android-Andi said:
Me again:
To use your shot.bat i had to download 2 *.dll´s to get "date.exe" working (libiconv2.dll and libintl3.dll). Without these .dll screenshot not possible.
Maybe you can add these two *.dll into your tool directory (don´t know if it´s allowed, check it here).
Download (GnuWin) Libintl.exe(?) from here and install it.
You´ll find the 2 needed *.dll at "C:\Program Files (x86)\GnuWin32\bin".
I´m, running Windows 8 Pro.
Click to expand...
Click to collapse
Didn't know about that... It worked for me without those two DLLs. Anyways, I will just add it for safety.
Android-Andi said:
Maybe you can add (after changeing directory path) my modified "record.bat" for taking screenshots from running androidsystem
Code:
@ECHO off
REM Record_running_Android
IF EXIST %~dp0new ECHO new directory found! :)
IF NOT EXIST %~dp0new ECHO new directory not found! :(
mkdir new
ECHO initialised new directory! :)
:loop
%~dp0tools\adb shell screencap -p /extSdCard/screen.png
%~dp0tools\adb pull /extSdCard/screen.png %~dp0new
%~dp0tools\adb shell rm /extSdCard/screen.png
FOR /F "tokens=*" %%i in ('%~dp0tools\date.bat') do SET DATE=%%i
MOVE %~dp0new\screen.png %~dp0new\%DATE%.png
goto loop
pause
I´m using extSdCard as directory, because my Micro-SD-Card is mounted there.
Maybe change it like this:
Code:
@ECHO off
REM Record_running_Android
IF EXIST %~dp0new ECHO new directory found! :)
IF NOT EXIST %~dp0new ECHO new directory not found! :(
mkdir new
ECHO initialised new directory! :)
:loop
%~dp0tools\adb shell screencap -p /sdcard/screen.png
%~dp0tools\adb pull /sdcard/screen.png %~dp0new
%~dp0tools\adb shell rm /sdcard/screen.png
FOR /F "tokens=*" %%i in ('%~dp0tools\date.bat') do SET DATE=%%i
MOVE %~dp0new\screen.png %~dp0new\%DATE%.png
goto loop
pause
Click to expand...
Click to collapse
You could change it yourself... Reason why I wouldn't change it? Because different devices have different mount points. If it is extSDcard, you can change accordingly. (If that wasn't the point, please clarify the last post. I understood it as: my mountpoint for sdcard is different :silly
p.s. thanks.. i was thinking no one cared

vineethraj49 said:
Remember that the *quality* is always the same. It pulls the images (frames) in the same resolution as of your phone. If you are talking about the FPS, you should modify this line...
Code:
ffmpeg -r 4
The -r switch controls the FPS.
Again, the FPS depends upon how many screens are actually captured by your device. If you have a fast SD-Card, and a fast processor, it is indeed likely that the frames captured would be more. You can try increasing the -r 4 by 2/3 frames and see if the video is suitable to your needs. (eg. -r 5/ -r 6, etc...)
Click to expand...
Click to collapse
This will change how long the picture stays (i set it down to 2, beacause in my case it was to fast).
MP4 and libx264 codec will give you better quality. I tested it yesterday the whole evening Trust me. Screenshot added (mp4 more clearly).
Try that one (video looks better):
Code:
ECHO off
REM snaps mode
REM fb2png credits go to respective developers
REM thanks to whiskey103 for his screenshot.bat for windows
REM thanks to vineethraj49 for his mkvideo.bat (video as *.avi)
REM thanks to me and my computer
IF EXIST %~dp0tmp ECHO tmp directory found! :)
IF NOT EXIST %~dp0tmp ECHO tmp directory not found! :( && MKDIR tmp && ECHO initialised new tmp directory! :)
IF EXIST %~dp0output_video ECHO output_video directory found! :)
IF NOT EXIST %~dp0output_video ECHO output_video directory not found! :( && MKDIR output_video && ECHO initialised new output_video directory! :)
%~dp0tools\adb pull /sdcard/fb2png/screens/ tmp
SET /P name=Enter the name for your video:
%~dp0tools\ffmpeg.exe -f image2 -r 2 -i tmp/1%%09d.png -c:v libx264 -r 30 output_video/%name%.mp4
%~dp0tools\adb shell rm /sdcard/fb2png/screens/*
rm tmp/*
REM hit enter to exit
pause
vineethraj49 said:
Didn't know about that... It worked for me without those two DLLs. Anyways, I will just add it for safety.
Click to expand...
Click to collapse
Adding will take you on the safe side Thanks I think they are under GPLv2, but i´m not shure.
You can also download libiconv-1.9.2-1-bin.zip and libintl-0.14.4-bin.zip. DLL´s are in the "bin" directory after extracting.
vineethraj49 said:
You could change it yourself... Reason why I wouldn't change it? Because different devices have different mount points. If it is extSDcard, you can change accordingly. (If that wasn't the point, please clarify the last post. I understood it as: my mountpoint for sdcard is different :silly
Click to expand...
Click to collapse
Code:
[user=279333]@ECHO[/user] off
REM Record_running_Android
IF EXIST %~dp0new ECHO new directory found! :)
IF NOT EXIST %~dp0new ECHO new directory not found! :(
mkdir new
ECHO initialised new directory! :)
:loop
%~dp0tools\adb shell screencap -p /sdcard/screen.png
%~dp0tools\adb pull /sdcard/screen.png %~dp0new
%~dp0tools\adb shell rm /sdcard/screen.png
FOR /F "tokens=*" %%i in ('%~dp0tools\date.bat') do SET DATE=%%i
MOVE %~dp0new\screen.png %~dp0new\%DATE%.png
goto loop
pause
Internal SD? Same path you use in your batch-scripts. Should work for everyone.
[The Script i posted before was for use on micro-sd (working for my device) - i have changed it later ( ) to use on internal-sd for everyone]
Only one problem: the name of the files... can´t use the mkvideo.bat to make a video... i had to rename them after captureing using Ant Renamer2.
But you can add the 2 .bat from me as a "Bonus" into your zip if you want.

Sure!
Android-Andi said:
This will change how long the picture stays (i set it down to 2, beacause in my case it was to fast).
MP4 and libx264 codec will give you better quality. I tested it yesterday the whole evening Trust me. Screenshot added (mp4 more clearly).
Try that one (video looks better):
Code:
ECHO off
REM snaps mode
REM fb2png credits go to respective developers
REM thanks to whiskey103 for his screenshot.bat for windows
REM thanks to vineethraj49 for his mkvideo.bat (video as *.avi)
REM thanks to me and my computer
IF EXIST %~dp0tmp ECHO tmp directory found! :)
IF NOT EXIST %~dp0tmp ECHO tmp directory not found! :( && MKDIR tmp && ECHO initialised new tmp directory! :)
IF EXIST %~dp0output_video ECHO output_video directory found! :)
IF NOT EXIST %~dp0output_video ECHO output_video directory not found! :( && MKDIR output_video && ECHO initialised new output_video directory! :)
%~dp0tools\adb pull /sdcard/fb2png/screens/ tmp
SET /P name=Enter the name for your video:
%~dp0tools\ffmpeg.exe -f image2 -r 2 -i tmp/1%%09d.png -c:v libx264 -r 30 output_video/%name%.mp4
%~dp0tools\adb shell rm /sdcard/fb2png/screens/*
rm tmp/*
REM hit enter to exit
pause
Adding will take you on the safe side Thanks I think they are under GPLv2, but i´m not shure.
You can also download libiconv-1.9.2-1-bin.zip and libintl-0.14.4-bin.zip. DLL´s are in the "bin" directory after extracting.
Code:
[user=279333]@ECHO[/user] off
REM Record_running_Android
IF EXIST %~dp0new ECHO new directory found! :)
IF NOT EXIST %~dp0new ECHO new directory not found! :(
mkdir new
ECHO initialised new directory! :)
:loop
%~dp0tools\adb shell screencap -p /sdcard/screen.png
%~dp0tools\adb pull /sdcard/screen.png %~dp0new
%~dp0tools\adb shell rm /sdcard/screen.png
FOR /F "tokens=*" %%i in ('%~dp0tools\date.bat') do SET DATE=%%i
MOVE %~dp0new\screen.png %~dp0new\%DATE%.png
goto loop
pause
Internal SD? Same path you use in your batch-scripts. Should work for everyone.
[The Script i posted before was for use on micro-sd (working for my device) - i have changed it later ( ) to use on internal-sd for everyone]
Only one problem: the name of the files... can´t use the mkvideo.bat to make a video... i had to rename them after captureing using Ant Renamer2.
But you can add the 2 .bat from me as a "Bonus" into your zip if you want.
Click to expand...
Click to collapse
cool! i have no objection. as of mp4 encoding too, you could add it as a feature, but do release it in this thread only. I sure would give you credits for a version 2.0 :angel: i don't want xda to be weeded by one more thread. there are already many (by a gazillion n00bs )

I did some cool batch-scripts (modified scripts from yours). You can download from here. Extract and copy the *.bat into the android-shot folder.
What have i done?
E.g. you can set a different path for storing the *.png on your device untill they get pulled. You can also change the destination-folder (on your local computer).
(All codes only from line 7 to ~ line 15 in batch-script)
1. batch: screenshot_recovery-universal.bat
Click to expand...
Click to collapse
Code:
REM Please enter the path where your internalstorage or micro-SD is mounted in recovery
[COLOR="Red"]set extpath=/sdcard[/COLOR]
REM
REM E.g. set "extpath=/extSdCard" if your micro-sd is mounted at /extSdCard.
REM (default-path: /sdcard for internal storage)
REM
REM
REM Please enter the name of your destinationfolder on your computer:
[COLOR="Red"]set pngpath=screenshots[/COLOR]
REM (default-path:screenshots)
Mountpoint of micro SD is different on any devices, you can change it to your´s.
You can change also the destination folder - but leave it as it is If you do: you have to change it in the converting-video batch-script too.
2. batch: record_recovery-universal.bat
Click to expand...
Click to collapse
Code:
REM Please enter the path where your internalstorage or micro-SD is mounted in recovery:
[COLOR="Red"]set extpath=/sdcard[/COLOR]
REM e.g. set "extpath=/external_sd" if your micro-sd is mounted IN RECOVERY at /external_sd
REM (default-path: /sdcard for internal storage)
Mountpoint of micro SD is different on any devices, you can change it to your´s.
3. batch: record_running_android-universal.bat
Click to expand...
Click to collapse
Code:
REM Please enter the path where your internalstorage or micro-SD is mounted:
[COLOR="Red"]set extpath=/sdcard[/COLOR]
REM E.g. set "extpath=/extSdCard" if your micro-sd is mounted at /extSdCard
REM (default-path: /sdcard for internal storage)
REM
REM
REM
REM Please enter the name of your destinationfolder on your computer:
[COLOR="Red"]set destpath=tmpandroid[/COLOR]
REM (default-path: tmpandroid)
Mountpoint of micro SD is different on any devices, you can change it to your´s.
You can change also the destination folder - but leave it as it is If you do: You have to change it in the converting-video batch-script too.
4. batch: mkvideo_mp4_recovery-universal.bat
Click to expand...
Click to collapse
Code:
REM Please enter the path where your internalstorage or micro-SD is mounted in recovery
[COLOR="Red"]set extpath=/sdcard[/COLOR]
REM e.g. set "extpath=/external_sd" if your micro-sd is mounted IN RECOVERY at /external_sd
REM (default-path: /sdcard for internal storage)
REM
REM
REM Please enter the name of your png-folder on your computer
REM (same as "destpath" in record_recovery-universal.bat)
[COLOR="Red"]set pngpath=tmp[/COLOR]
REM (default-path:tmp - if you have modified the path do the same here)
Mountpoint of micro SD is different on any devices, you can change it to your´s. If you have changed it in the record_recover-batch-script - you have to do it too.
You can change also the destination folder - but leave it as it is If you have changed it in the record_recovery-batch-script - you have to do it too.
5. batch: mkvideo_mp4_running_android-universal.bat
Click to expand...
Click to collapse
Code:
REM Please enter the name of your png-folder on your computer
REM (same as "destpath" in record_runnning_android-universal.bat)
[COLOR="Red"]set pngpath=tmpandroid[/COLOR]
REM (default-path:tmpandroid - if you have modified the path do the same here)
You can change also the png folder - but leave it as it is If you have changed it in the record_running_android-batch-script - you have to do it too.
Please use Notepad++ if you want to change something in the batch-script.
For watching the .mp4 you can use Media Player Home Cinema.

Cool, but, one small change that I would like to say...
Android-Andi said:
I did some cool batch-scripts (modified scripts from yours). You can download from here. Extract and copy the *.bat into the android-shot folder.
What have i done?
E.g. you can set a different path for storing the *.png on your device untill they get pulled. You can also change the destination-folder (on your local computer).
(All codes only from line 7 to ~ line 15 in batch-script)
Code:
REM Please enter the path where your internalstorage or micro-SD is mounted in recovery
[COLOR="Red"]set extpath=/sdcard[/COLOR]
REM
REM E.g. set "extpath=/extSdCard" if your micro-sd is mounted at /extSdCard.
REM (default-path: /sdcard for internal storage)
REM
REM
REM Please enter the name of your destinationfolder on your computer:
[COLOR="Red"]set pngpath=screenshots[/COLOR]
REM (default-path:screenshots)
Mountpoint of micro SD is different on any devices, you can change it to your´s.
You can change also the destination folder - but leave it as it is If you do: you have to change it in the converting-video batch-script too.
Code:
REM Please enter the path where your internalstorage or micro-SD is mounted in recovery:
[COLOR="Red"]set extpath=/sdcard[/COLOR]
REM e.g. set "extpath=/external_sd" if your micro-sd is mounted IN RECOVERY at /external_sd
REM (default-path: /sdcard for internal storage)
Mountpoint of micro SD is different on any devices, you can change it to your´s.
Code:
REM Please enter the path where your internalstorage or micro-SD is mounted:
[COLOR="Red"]set extpath=/sdcard[/COLOR]
REM E.g. set "extpath=/extSdCard" if your micro-sd is mounted at /extSdCard
REM (default-path: /sdcard for internal storage)
REM
REM
REM
REM Please enter the name of your destinationfolder on your computer:
[COLOR="Red"]set destpath=tmpandroid[/COLOR]
REM (default-path: tmpandroid)
Mountpoint of micro SD is different on any devices, you can change it to your´s.
You can change also the destination folder - but leave it as it is If you do: You have to change it in the converting-video batch-script too.
Code:
REM Please enter the path where your internalstorage or micro-SD is mounted in recovery
[COLOR="Red"]set extpath=/sdcard[/COLOR]
REM e.g. set "extpath=/external_sd" if your micro-sd is mounted IN RECOVERY at /external_sd
REM (default-path: /sdcard for internal storage)
REM
REM
REM Please enter the name of your png-folder on your computer
REM (same as "destpath" in record_recovery-universal.bat)
[COLOR="Red"]set pngpath=tmp[/COLOR]
REM (default-path:tmp - if you have modified the path do the same here)
Mountpoint of micro SD is different on any devices, you can change it to your´s. If you have changed it in the record_recover-batch-script - you have to do it too.
You can change also the destination folder - but leave it as it is If you have changed it in the record_recovery-batch-script - you have to do it too.
Code:
REM Please enter the name of your png-folder on your computer
REM (same as "destpath" in record_runnning_android-universal.bat)
[COLOR="Red"]set pngpath=tmpandroid[/COLOR]
REM (default-path:tmpandroid - if you have modified the path do the same here)
You can change also the png folder - but leave it as it is If you have changed it in the record_running_android-batch-script - you have to do it too.
Please use Notepad++ if you want to change something in the batch-script.
For watching the .mp4 you can use Media Player Home Cinema.
Click to expand...
Click to collapse
drawbacks of your method :fingers-crossed: :
not all devices are fast enough to process the "capture>pull>remove" loop which you have implemented.
except that, awesomeness quotient is great. you have added support for capturing the screen while android is running in normal mode :victory:
It can be just downloaded and extracted into the folder where you already have the files... releasing it as version 2.0
p.s. Guess its time for me to update the linux version

vineethraj49 said:
drawbacks of your method :fingers-crossed: :
not all devices are fast enough to process the "capture>pull>remove" loop which you have implemented.
Click to expand...
Click to collapse
Maybe i can make 2 batch files (pulling as a second step). Maybe add the pull line into the "mkvideo_mp4_running_android-universal.bat".
I can test it after sleeping :silly:
And you´re right: its not so fast like in recovery (on my Galaxy Tab 2 7.0 P3110)
vineethraj49 said:
except that, awesomeness quotient is great. you have added support for capturing the screen while android is running in normal mode :victory:
Click to expand...
Click to collapse
Thank you Thanks for your great work before my modification - my modification wouldn´t be possible without you :good:
vineethraj49 said:
It can be just downloaded and extracted into the folder where you already have the files... releasing it as version 2.0
p.s. Guess its time for me to update the linux version
Click to expand...
Click to collapse
Do it
Because i´m not running a linux i couldn´t make it (and i´m not that good at linux).

Maybe i can make 2 batch files (pulling as a second step). Maybe add the pull line into the "mkvideo_mp4_running_android-universal.bat".
I can test it after sleeping :silly:
And you´re right: its not so fast like in recovery (on my Galaxy Tab 2 7.0 P3110)
Click to expand...
Click to collapse
Yeah, recovery... too slow
Thank you Thanks for your great work before my modification - my modification wouldn´t be possible without you :good:
Click to expand...
Click to collapse
Thank Kyan He and Whiskey103 too
Do it
Because i´m not running a linux i couldn´t make it (and i´m not that good at linux).
Click to expand...
Click to collapse
https://github.com/vineethraj49/android-shot
If you are interested, you can send in pull requests to https://github.com/vineethraj49/android-shot/tree/windows. PM me if interested to maintain the git,I will add you as a collaborator.

vineethraj49 said:
Yeah, recovery... too slow
Thank Kyan He and Whiskey103 too
https://github.com/vineethraj49/android-shot
If you are interested, you can send in pull requests to https://github.com/vineethraj49/android-shot/tree/windows. PM me if interested to maintain the git,I will add you as a collaborator.
Click to expand...
Click to collapse
sure, big thank @ Kyan He and Whiskey103 too!
i'll release update 2.0.1 later. i'm working on it. PM to you later.
pull won't work on windows. i tryed over vbs but didn't got it work.

Version 2.0.1 (extra batch-files)​
Download 2.0.1 from here
Installation:
Download and extract V 1.0 from op.
Extract "universal-bat2.0.1.zip" and copy all *.bat to "android-shot" directory.
Changes:
Code:
[LIST][*]not pulling data from your device (slowed down the recording process) @ record_running_android-universal.bat
[*]pulling before converting (better for recording process) @ mkvideo_mp4_running_android-universal.bat[/LIST]
How-To make a video in recovery:
1. start "record_recovery-universal.bat" (press CTRL + C if you are finished)
2. start "mkvideo_mp4_recovery-universal.bat" and follow the instructions.
How-To make a video in running android:
1. start "record_running_android-universal.bat" (press CTRL + C if you are finished)
2. start "mkvideo_mp4_running_android-universal.bat" and follow the instructions.
You can change the path from sdcard (default) to your micro-SD like before (different devices = different mountpoints) (instructions)
Thanks
@vineethraj49
Kyan He (https://plus.google.com/116857119889961125943) and his wonderful tool "fb2png" (https://code.google.com/p/android-fb2png/)
Whiskey103 (http://forum.xda-developers.com/member.php?u=2632943) and his guide (http://forum.xda-developers.com/showthread.php?p=40260716) on taking screenshot in windows.
Edit 30.07.2013:
Changed Download-Link, still 2.0.1 (some UI changes of the running batch)

time to update thread title I guess!
@Android-Andi, could you post a video for android_running_system for video recording as a sample?

vineethraj49 said:
@Android-Andi, could you post a video for android_running_system for video recording as a sample?
Click to expand...
Click to collapse
Shure,can do it next days,maybe today.

for rooted devices
is there anyby some gesture

[GUIDE]To Unpack/Repack livesuit flashable images

While browsing XDA i didn't find anything for unpacking Livesuite images so i created this THREAD.
Things you need
Allwiner kitchen
Stock Firmware
Linux image tool
Ubuntu 64 bit
Click to expand...
Click to collapse
Lets start
Step 1
Extracting and building the stock image (Windows)
Extract a10_flash_kitchen_v1.zip and look inside the directory, you'll see packer_gb and packer_ics. packer_ics is for Android ICS, so that is the one you will be using.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Open packer_ics and you will notice a bunch of directories and a couple of .bat scripts. We will spend a lot of time in these directories.
Extract the stock firmware you downloaded earlier, and copy the .img file into this directory. Rename the file to original.img.
Run the extract_image.bat script, and a command window will pop up while it is extracting.
The command window will output like the following, it will display Press any key to continue . . . when it is complete. Press a key to close the window.
Once the command window is closed, open the _extract directory and all of the extracted files will be there. The three following files are the ones we are interested in: RFSFAT16_BOOT_00000000000.fex (the boot partition), RFSFAT16_RECOVERY_0000000.fex (the recovery partition), RFSFAT16_SYSTEM_000000000.fex (the system partition, ext4 sparse).
NOTE and WARNING Some systems may also have a RFSFAT16_BOOTLOADER_00000.fex, which may also be required for your device to boot properly. There are some vague instructions @ this TechKnow forums post. I (the reader) will attempt to clarify and modify this page with the updated additional instructions for these devices to aid in making these instructions more universal for anyone using LiveSuit.
Click to expand...
Click to collapse
Step 2
Extracting, modifying and building partitions (Linux)
Copy your Extracted files to ubuntu
Rename the files as follows:
RFSFAT16_BOOT_00000000000.fex -> boot.img
RFSFAT16_RECOVERY_0000000.fex -> recovery.img
RFSFAT16_SYSTEM_000000000.fex -> system.fex
Click to expand...
Click to collapse
Copy the tools.tar.gz archive you downloaded earlier into the same directory.
To extract the tools, right click on the file and click Extract here.
This will extract the tools into a tools subdirectory.
Type terminal to show the terminal application. Hit enter and the terminal will appear.
Boot partition
Code:
$ cd "custom image"
$ tools/split_bootimg.pl boot.img
$ ls
Now extract the ramdisk file into a ramdisk subdirectory.
Code:
$ mkdir ramdisk
$ cd ramdisk
$ gunzip -c ../boot.img-ramdisk.gz | cpio -i
$ ls
You are now able to modify the files as needed.
Once you have finished modifying the file, we will rebuild the image. Run the following commands.
Code:
$ cd ..
$ tools/mkbootfs ramdisk | gzip > ramdisk-new.gz
$ tools/mkbootimg --base 0x40000000 --kernel boot.img-kernel --ramdisk ramdisk-new.gz --cmdline 'console=ttyS0,115200 rw init=/init loglevel=8' -o new-boot.img
$ ls
Recovery partition
his follows the same process as the boot partition. Execute the following commands to extract the image:
Code:
$ tools/split_bootimg.pl recovery.img
$ rm -rf ramdisk
$ mkdir ramdisk
$ cd ramdisk
$ gunzip -c ../recovery.img-ramdisk.gz | cpio -i
$ ls
rebuild the image with the following commands:
Code:
$ cd ..
$ tools/mkbootfs ramdisk | gzip > ramdisk-new.gz
$ tools/mkbootimg --base 0x40000000 --kernel recovery.img-kernel --ramdisk ramdisk-new.gz --cmdline 'console=ttyS0,115200 rw init=/init loglevel=8' -o new-recovery.img
$ ls
System partition
The process for the system partition is different, because it is not bootable and because it is ext4 sparse, so it cannot be mounted straight away. Execute the following commands to convert and mount the image:
Code:
$ tools/simg2img system.fex system.img
$ mkdir system
$ sudo mount -o loop system.img system
$ cd system
$ ls
Once you are done, execute the following commands to rebuild the system image:
Code:
$ cd ../tools
$ sudo ./mkuserimg.sh -s ../system ../new-system.fex ext4 ../tmp 300M
$ cd ..
$ sudo umount system
$ ls
Now switch back to the file browser and you will see many new files in your directory. The three files that you are interested in are new-boot.img, new-recovery.img, new-system.fex
Copy these to your Windows drive to the directory a10_flash_kitchen_v2/packer_ics/_input
Click to expand...
Click to collapse
Step 3
Building the new image (Windows)
Once the files are copied, jump back to Windows and rename the files as following:
new-boot.img -> root.fex
new-recovery.img -> recovery.fex
new-system.fex -> system.fex
Click to expand...
Click to collapse
http://i.imgur.com/klTA5.png/img]
Now we need to make some modifications to the image config file. Navigate to the files directory and you should see image.cfg.
[img]http://i.imgur.com/Wg6Ov.png/img]
Open this file using your text editor that supports Unix line endings. Using Notepad will break this file. Locate the two lines that reference OEM and VOEM as is highlighted below.
[img]http://i.imgur.com/YxczH.png
Comment these lines by adding a semicolon ( to the start of each line. Do not make any other modifications. Save the file once you have made the change.
http://i.imgur.com/urMMN.png/img]
Go back to the packer_ics root directory and find the create_image.bat script. It will open a console while it is creating the new image.
[img]http://i.imgur.com/X2O6l.png
Once the process is complete, you will see Press any key to continue . . . and you will have a new image called output.img.
AND JUST FLASH IT AND YOU ARE DONE
Click to expand...
Click to collapse

Credits
miniandwiki
To ME
To Everyone who helped me creating this one

do i have to use 64bit liux?? i only have a 32 bit computer?? thnx

Permission denied
Hey....
I installed Ubuntu on an external disk. But even logged at su (also tried sudo su) I dont have the permission to perform with the Linux-tool. When I click at the roo-folder, it is already set to rw permission for root.
What am I doing wrong?

Links are broken, can you kindly update them.

Links are broken Pls Upload to another host

How to mount & modify system.img (Ubuntu)

Hi to all. I am a newbie ... but I try to do all my best
Above all please make a directory under /mnt (I called the directory "MyMount1"); "mylogin" represents your login name.
Open the terminal and type the next commands:
-sudo mkdir /mnt/MyMount1
-sudo chown mylogin:mylogin /mnt/MyMount1
-copy system.img & paste it into MyMount1 (computer/mnt/MyMount1)
-cd /
-cd mnt
-cd MyMount1
-mkdir sys/ && sudo mount -t ext4 -o loop system.img sys/
-sudo chown mylogin:mylogin sys (without this command you will not be able to copy and modify anything)
-cd sys
-sudo chown mylogin:mylogin addon.d (without this command you will not be able to copy and modify anything)
-then copy addon.d & paste it into Ubuntu Desktop (now you can make any changes you want)
-then delete addon.d into /mnt/MyMount1/sys
-copy addon.d (into Ubuntu Desktop) & paste it into /mnt/MyMount1/sys
-then apply the same command to every folder inside system.img (/mnt/MyMount1/sys) and repeat the procedure (copy it into Ubuntu Desktop, make changes and paste it into /mnt/MyMount1/sys).
The following screenshot will help you better understand all the steps :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Before "sudo chown mylogin:mylogin sys" command :
After "sudo chown mylogin:mylogin sys" command :
Before "sudo chown mylogin:mylogin addon.d" command :
After "sudo chown mylogin:mylogin addon.d" command :
That's all ... for now
XDA:DevDB Information
System.img, ROM for all devices (see above for details)
Contributors
Cleopatra Bianchi
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Testing
Created 2016-03-24
Last Updated 2016-03-24

hey there!!! i can give you a couple of suggestion, even if i don't get if you are only extracting or also editing and repacking since i don't see any repack code.. anyway.. first of all you definitely should use -R in yoour chown code.. this means recursive.. so you don't have to do it for every folder, subfolder and so on!! do a chown -r for sys and you're done with it.
then another thing.. i personally use a script that will handle all this by itself, i put it in the file explorer script folder and so you can access it from everywhere just right-clicking on the file you want to mount.. it will need to edit path for pass it as variable, but it's easy.. at least once you know how to
so this is my script:
Code:
#!/bin/bash
CWD=(pwd)
simg2img [email protected] img.img; mkdir /tmp/system; mate-terminal -x sudo mount -t auto -o loop img.img /tmp/system; mate-terminal -x sudo chown -R login:login /tmp/system
just to explain, you see simg2img because i work with sparse img ( from samsung) that must be converted to regular img before get mounted, so i have the simg2img binary compiled and moved into /usr/local/bin path to access it from any path.. you will need to do the same or to remove that part if you don't need it.
also you must change mate-terminal to plain terminal since you're on unity i can see
then move the script to /home/your_login/.nautilus/script (again because you're on unity using nautilus i think) check if it has the exec bit enbled from permission and then enjoy..
oh another thing.. in case you need to copy keeping the permissions and ownership, so that you don't ahve to fix all that later you simply don't set the last part of the script - the chown part, since you can access the subfolders and files anyway and for ex. use the "cp -a /tmp/system/app /your_desired_path to work on it.

Wuby986 said:
hey there!!! i can give you a couple of suggestion, even if i don't get if you are only extracting or also editing and repacking since i don't see any repack code.. anyway.. first of all you definitely should use -R in yoour chown code.. this means recursive.. so you don't have to do it for every folder, subfolder and so on!! do a chown -r for sys and you're done with it.
then another thing.. i personally use a script that will handle all this by itself, i put it in the file explorer script folder and so you can access it from everywhere just right-clicking on the file you want to mount.. it will need to edit path for pass it as variable, but it's easy.. at least once you know how to
so this is my script:
Code:
#!/bin/bash
CWD=(pwd)
simg2img [email protected] img.img; mkdir /tmp/system; mate-terminal -x sudo mount -t auto -o loop img.img /tmp/system; mate-terminal -x sudo chown -R login:login /tmp/system
just to explain, you see simg2img because i work with sparse img ( from samsung) that must be converted to regular img before get mounted, so i have the simg2img binary compiled and moved into /usr/local/bin path to access it from any path.. you will need to do the same or to remove that part if you don't need it.
also you must change mate-terminal to plain terminal since you're on unity i can see
then move the script to /home/your_login/.nautilus/script (again because you're on unity using nautilus i think) check if it has the exec bit enbled from permission and then enjoy..
oh another thing.. in case you need to copy keeping the permissions and ownership, so that you don't ahve to fix all that later you simply don't set the last part of the script - the chown part, since you can access the subfolders and files anyway and for ex. use the "cp -a /tmp/system/app /your_desired_path to work on it.
Click to expand...
Click to collapse
Thank you very much for your suggestions
I have to admit that I am a newbie/noob ... particularly on Linux (I have installed Ubuntu OS just a week ago ... I come from the planet Windows). I have tried "android_img_repack_tools-android-6.0.1_r3_x64.tar.gz" ... but simg2img doesn't works (I am not able to convert system.img in raw). I'm trying to mod a system.img Mediatek Marshmallow.
Kindest Regards.

Cleopatra Bianchi said:
Thank you very much for your suggestions
I have to admit that I am a newbie/noob ... particularly on Linux (I have installed Ubuntu OS just a week ago ... I come from the planet Windows). I have tried "android_img_repack_tools-android-6.0.1_r3_x64.tar.gz" ... but simg2img doesn't works (I am not able to convert system.img in raw). I'm trying to mod a system.img Mediatek Marshmallow.
Kindest Regards.
Click to expand...
Click to collapse
i hano NO idea about mediatek devices, you should ask in the corresponding fora, but most likely you don't need simg 2 img since that's not a sparse img, so you could be able to mount it strait away.. or at least try first without converting it.
what's the error you're getting in terminal?

Wuby986 said:
i hano NO idea about mediatek devices, you should ask in the corresponding fora, but most likely you don't need simg 2 img since that's not a sparse img, so you could be able to mount it strait away.. or at least try first without converting it.
what's the error you're getting in terminal?
Click to expand...
Click to collapse
This is the error in terminal :

Cleopatra Bianchi said:
This is the error in terminal :
Click to expand...
Click to collapse
yeah then is definitely not a sparse img.. maybe a regular img or other kinda of..
you should search for the mtk device forum for this info.. or better yet maybe the @dsixda kitchen has a conversion binary for it, so you can see which is and use it instead of the simg2img.. this kitchen is not anymore updated, so you cannot use it for everything like repack or root, but should work for unpack

Wuby986 said:
yeah then is definitely not a sparse img.. maybe a regular img or other kinda of..
you should search for the mtk device forum for this info.. or better yet maybe the @dsixda kitchen has a conversion binary for it, so you can see which is and use it instead of the simg2img.. this kitchen is not anymore updated, so you cannot use it for everything like repack or root, but should work for unpack
Click to expand...
Click to collapse
Ok ... I'll do it. Thank you very much for your suggestions.
Happy Easter

Cleopatra Bianchi said:
Hi to all. I am a newbie ... but I try to do all my best
Above all please make a directory under /mnt (I called the directory "MyMount1"); "mylogin" represents your login name.
Open the terminal and type the next commands:
-sudo mkdir /mnt/MyMount1
-sudo chown mylogin:mylogin /mnt/MyMount1
-copy system.img & paste it into MyMount1 (computer/mnt/MyMount1)
-cd /
-cd mnt
-cd MyMount1
-mkdir sys/ && sudo mount -t ext4 -o loop system.img sys/
-sudo chown mylogin:mylogin sys (without this command you will not be able to copy and modify anything)
-cd sys
-sudo chown mylogin:mylogin addon.d (without this command you will not be able to copy and modify anything)
-then copy addon.d & paste it into Ubuntu Desktop (now you can make any changes you want)
-then delete addon.d into /mnt/MyMount1/sys
-copy addon.d (into Ubuntu Desktop) & paste it into /mnt/MyMount1/sys
-then apply the same command to every folder inside system.img (/mnt/MyMount1/sys) and repeat the procedure (copy it into Ubuntu Desktop, make changes and paste it into /mnt/MyMount1/sys).
The following screenshot will help you better understand all the steps :
Before "sudo chown mylogin:mylogin sys" command :
After "sudo chown mylogin:mylogin sys" command :
Before "sudo chown mylogin:mylogin addon.d" command :
After "sudo chown mylogin:mylogin addon.d" command :
That's all ... for now
XDA:DevDB Information
System.img, ROM for all devices (see above for details)
Contributors
Cleopatra Bianchi
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Testing
Created 2016-03-24
Last Updated 2016-03-24
Click to expand...
Click to collapse
pro tip use -R to make chown reclusive and include all the subfolders
sudo chown login:login -R (folder in sys)
---------- Post added at 08:59 AM ---------- Previous post was at 08:59 AM ----------
Cleopatra Bianchi said:
Hi to all. I am a newbie ... but I try to do all my best
Above all please make a directory under /mnt (I called the directory "MyMount1"); "mylogin" represents your login name.
Open the terminal and type the next commands:
-sudo mkdir /mnt/MyMount1
-sudo chown mylogin:mylogin /mnt/MyMount1
-copy system.img & paste it into MyMount1 (computer/mnt/MyMount1)
-cd /
-cd mnt
-cd MyMount1
-mkdir sys/ && sudo mount -t ext4 -o loop system.img sys/
-sudo chown mylogin:mylogin sys (without this command you will not be able to copy and modify anything)
-cd sys
-sudo chown mylogin:mylogin addon.d (without this command you will not be able to copy and modify anything)
-then copy addon.d & paste it into Ubuntu Desktop (now you can make any changes you want)
-then delete addon.d into /mnt/MyMount1/sys
-copy addon.d (into Ubuntu Desktop) & paste it into /mnt/MyMount1/sys
-then apply the same command to every folder inside system.img (/mnt/MyMount1/sys) and repeat the procedure (copy it into Ubuntu Desktop, make changes and paste it into /mnt/MyMount1/sys).
The following screenshot will help you better understand all the steps :
Before "sudo chown mylogin:mylogin sys" command :
After "sudo chown mylogin:mylogin sys" command :
Before "sudo chown mylogin:mylogin addon.d" command :
After "sudo chown mylogin:mylogin addon.d" command :
That's all ... for now
XDA:DevDB Information
System.img, ROM for all devices (see above for details)
Contributors
Cleopatra Bianchi
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Testing
Created 2016-03-24
Last Updated 2016-03-24
Click to expand...
Click to collapse
pro tip use -R to make chown reclusive and include all the subfolders
sudo chown login:login -R (folder in sys)