Hi,
I'm releasing a tool for changing the splash image inside the bootloader. It is available in 2 version, GUI & cmd line. The GUI is only for windows while the cmd line is platform independent.
GUI version info:
This tool is written in Python and using pygame library as the image manipulator.
Sorry, there's no mouse button to click, use keyboard to input command.
Sometimes the open file popup window become out of focus,use ALT + TAB to reselect the window.
You can load image that is supported by pygame
(JPG,PNG,GIF(non animated,BMP,PCX,TGA (uncompressed),TIF,LBM (and PBM),PBM (and PGM, PPM),XPM
Image dimension
EEEPAD logo : 300x100, ASUS logo : 300x90, NVIDIA logo : 300x30
GUI version features:
Only for windows
Replace eeepad, asus, nvidia logo
Can load any version of bootloader (build 8.6.5.9 tested)
Extract image from bootloader
Save as blob
GUI version screenshot:
{
"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"
}
GUI version quick guide:
1. Load the bootloader
2. Load the image you want to change.
3. Save the bootloader, and test it via nvflash
4. Save the blob, flash to your device via dd
nvflash test command:
nvflash.exe --bct transformer.bct --setbct --configfile flash.cfg --bl patched_bl.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --go
Click to expand...
Click to collapse
dd flash command:
dd if=blob of=/dev/block/mmcblk0p4
Click to expand...
Click to collapse
CMD line version info:
Requires python, python-imaging (PIL).
The script flow is nearly same as the GUI version except it use PIL to load/convert image.
Please browse the source code to get better understanding
CMD line version features:
Platform independent
Replace eeepad, asus, nvidia logo
Can load any version of bootloader (build 8.6.5.9 tested)
Save as blob
CMD line version guide:
Bootsplash patcher for ASUS Transformer TF101 (v1.0 | python | cmd line)
Usage: cmd_patcher.py -b bootloader.bin -e eeepad.bmp -a asus.bmp -n nvidia.bmp
Options:
-h, --help show this help message and exit
-b bootloader.bin Bootloader file
-e eeepad.bmp EEEPAD logo replacement
-a asus.bmp ASUS logo replacement
-n nvidia.bmp NVIDIA logo replacement
-o patched_bl.bin Patched bootloader file (Optional)
-f custom_blob Patched BLOB file (Optional)
Click to expand...
Click to collapse
UPDATE:
Python command line tool is now available.
Disclaimer:
This tool is intended for advanced user/themer. USE AT YOUR OWN RISK!!
REMEMBER : There's always a chance for a messed up bootloader.Please test the bootloader before proceeding to flash the blob.
I'm not liable for any problem arising such as bricked,loosed data..etc.
Click to expand...
Click to collapse
Download:
Get it from here
I'll try it this weekend. thanks for your work.
Moving to Themes & Apps.
I might get the "IRON FIST" but this works great. Thanks for your work.
I have a question I downloaded the Revolution HD 2.2 rom for the TF, then extracted the kernelblob and amended the splash images using this software then used the save command and it created the file named 'blob' , my question is how do i flash it back do i use adb ?
I will appriciate any help
4.0.3
Does anyone know if this will work on ICS?
I tried this with Prime 2.1.1 (HC ROM) and the tool says it's the wrong bootloader (I chose the blob file at the root of the ROM .zip file).
Isn't there anything easier than this to flash a new splash screen? Any help please?
Related
Here are some instructions to create the splash:
You have to use a 320x240 BMP and Pof’s nbimg with this command:
for Dash 3G
nbimg -p 108512 -t 255 -w 320 -h 240 -F splash.bmp -T 0x600 –S 64 -D MAPL*****
for Ozone:
nbimg -p 108512 -t 255 -w 320 -h 240 -F splash.bmp -T 0x600 –S 64 -D CEDA*****
Thanks oOkBa for checking this out
Here is one I created for the Ozone.
{
"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"
}
This is good info. Once the splash file is created, how do we flash it?
P
PriTyan said:
This is good info. Once the splash file is created, how do we flash it?
P
Click to expand...
Click to collapse
i was hoping someone would have answered this question in here by now.
and can we get a non technical answer..like in laymans terms. thanks!
SoCalSpecialist said:
i was hoping someone would have answered this question in here by now.
and can we get a non technical answer..like in laymans terms. thanks!
Click to expand...
Click to collapse
What he said...
This is all fine and dandy, but on the Ozone I can't find the OEM .nb files.
I found 2 .nb0 files in the \Windows folder.
I copied them to computer, renamed them and ran the utility.
Neither are te HTC splash screen.
To update the splash, your device needs to be unlocked by using jockyw's hardspl for your device.
Next download Ozone-splash.zip from here http://forum.xda-developers.com/showpost.php?p=4381312&postcount=24
Replace the splash.nbh file extracted from the zip with your custom image, then run ROMUpdateUtility.exe from the same directory as your updated splash.nbh to flash at your own rick of course
I did this on my Ozone with out any problems. Can not confirm this will work on other devices.
P
Does "flashing" it wipe the device?
brent372 said:
Does "flashing" it wipe the device?
Click to expand...
Click to collapse
Yea unfortunately it does. Make sure you back up all of your info so you don't lose your contacts and ActiveSync it.
Hello!
Now I'll start off with what this thread is and all the associated warnings and disclaimers. First off, If you are looking to flash a Viewsonic g Tablet with a custom bootscreen, YOU ARE IN THE RIGHT PLACE.
Now one of my favorite hacks to any device is to customize the bootscreen, it just completes the "hacked device" feel for me. I have found that the info on how to do this is fairly advanced, many people who may want to do this could be turned off by that fact! However, that being said flashing anything with nvflash is very risky and you could lose personal data and/or soft/hard brick your tablet so, if your head is on backwards, or you are just stupid, I'd avoid this anyways
Make a back-up of any personal data anyways!
Also, this guide is mainly for windows users, I am writing this because most of the limited info currently available was for Linux. This may be useful to linux users still, but don't be surprised if you are not finding what you need for a linux problem.
Now the first thing you need to do, if you haven't before, is download two ESSENTIAL tools:
NVFlash (choose the windows one AND the gTablet one): http://db.tt/Wm25t7U
NOTE: I've heard this link can be picky, I've had good luck but beware.
The APX driver for windows: http://www.myadventvega.co.uk/SystemUSB.zip
------------------------------------------
From here you have too extract the windows nvflash into a directory (just do what I did and call it NVFlash, put somewhere like your desktop).
Now extract just the bootloader.bin file from the gtablet nvflash zip file, also put it into that directory.
Now, to put your tablet into APX mode, power it down, then hold down the power and VOLUME - buttons until the current bootscreen comes up and then goes blank (let go at that point). Windows should now detect a new device, the installation will fail, but after that go into Device Manager and right-click on APX then choose Update drivers. Choose to specify a location, then extract the SystemUSB.zip and point it to the folder containing the i386 and amd64 folders. It should install and then you should be good.
Now your tablet is ready to be flashed, which means we are going to define some terms. First off, what I will refer to as the first boot screen is located in partition 6, it defaults to the viewsonic birds and is the first one to show up. What I will refer to as the second boot screen is actually part of the ROM you use and is much trickier to change. It defaults to gTablet in an oval.
To flash the first boot creen locate a 24-bit bitmap file, 1024x600, I use the one below. This is not the actual bmp though, the actual bootscreen is attached to this post. Now once you have a file, place it in your NVFlash directory.
{
"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"
}
Now you need to open a command prompt into your NVFlash directory and run:
Code:
nvflash --bl bootloader.bin --download 6 yourfile.bmp
You should now have a nice new bootscreen, if you have a problem, see the bottom for the FAQ.
To flash the second bootscreen you must not only want this pretty bad, but be ready to lose stuff! The second bootscreen is actually part of the ROM you are using. You can either find a premodified boot.img in this thread:
http://forum.xda-developers.com/showthread.php?t=876488
or make your own using those instructions.
YOU MUST USE THE BOOT.IMG FROM YOUR EXACT ROM, IF IT'S NOT THE EXACT SAME YOU WILL SOFT-BRICK YOUR TABLET!!! QUADRUPLE CHECK THIS!!!!
once you have a boot.img and you've placed it in the NVFlash directory, run this command:
Code:
nvflash --bl bootloader.bin --download 10 boot.img
You may want to keep different images seperate by renaming them or keeping them in a different folder, just remember that you have to flash boot.img, don't change the file name!
To save some time you can use this batch file:
Code:
@echo off
rem If your edit this file, you also accept any responsibility for the damages incurred to your tablet!
:terms
echo ------------------ TERMS OF USE ------------------
echo --- ---
echo --- If you use this batch file, you accept all ---
echo --- responsibility for anything that happens ---
echo --- to your gTablet! ---
echo --- ---
echo --- This process is risky and can cause damage ---
echo --- to your tablet! I don't accept any ---
echo --- responsibility for these damage! ---
echo --- ---
echo --- BASICALLY, USE AT YOUR OWN RISK! ---
echo --- ---
echo --------------------------------------------------
set /p terms=If you agree to these terms type "agree" (no quotes) or else type "decline":
if '%terms%'=='agree' goto top
goto exit
:top
cls
echo Make sure that you have bootloader.bin and nvflash.exe in thie same directory as this file or in PATH!
echo Make sure that your tablet ic connected in APX Mode and ready to be flashed!
echo 1 = Flash initial bootscreen (viewsonic birds is original) (part 6)
echo 2 = Flash secondary bootscreen (gTablet in an oval is original) (part 10)
echo Q = Quit
@set /p ui=Choose one to continue:
if '%ui%'=='1' goto part6
if '%ui%'=='2' goto part10
if '%ui%'=='q' goto exit
if '%ui%'=='Q' goto exit
goto top
:part6
cls
set /p fname6=Enter the file name (relative to this directory):
set /p confirm=Is %fname6% correct? Press y or n, confirm this carefully or you will likely brick your tablet!:
if '%confirm%'=='y' goto flash6
goto part6
:flash6
echo Flashing %fname6% to partition 6 of the connected g Tablet
nvflash --bl bootloader.bin --download 6 %fname6%
pause
goto top
:part10
cls
set /p fname10=Type the location of the proper boot.img (relative to this directory) (this should be a modified version specific to your flashed ROM):
set /p confirm=Is %fname10% the correct location and is this the boot.img for the correct ROM? Press y or n, confirm this carefully or you will likely brick your tablet!:
if '%confirm%'=='y' goto flash10
goto part6
:flash10
echo Flashing %fname10% to partition 10 of the connected g Tablet
nvflash --bl bootloader.bin --download 10 %fname10%
pause
goto top
:exit
exit
Just save this as bootscreen.bat in your NVFlash directory!
And that's about it!
Common errors (FAQ):
Code:
Couldn't find usb device
- Your drivers aren't installed properly or you aren't in APX mode.
Credits (threads I learned this from):
http://forum.xda-developers.com/showthread.php?t=861950
http://forum.xda-developers.com/showthread.php?t=859383
Also the above mentioned thread!
Thanks and have a nice day!
i follow your steps but nothing happen / file not fund error, i put the windows , bootloader bin , and the new image in a folder and run the gtab batch and i just get that error. what im doing wrong .
thanks for any help
patne83 said:
i follow your steps but nothing happen / file not fund error, i put the windows , bootloader bin , and the new image in a folder and run the gtab batch and i just get that error. what im doing wrong .
thanks for any help
Click to expand...
Click to collapse
Well, your explanation of your problem isn't very clear, but I'm assuming you are trying to flash the first boot screen and you are having issues. Please supply some more information or try rereading the steps you're having trouble with.
{
"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"
}
ICL23D - Galaxy Nexus Boot/Recovery/System Dump
From Modaco.com
Below are links to a ICL23D Ice Cream Sandwich development build for the Galaxy Nexus!
Some points to note about the files...
All 3 files are completely stock and unedited
This build is a dev build, not a release build
This build is from a test Galaxy Nexus
This build is not odexed!
I know a lot of people are hacking up ports for other devices, so hopefully the non-odexed nature of this release together with the fact it includes the boot and recovery images will help make that happen.
All I ask is that you don't mirror the files elsewhere, that you link back to this topic rather than deeplinking the files and that if you use them you credit the source. So here they are...
Galaxy Nexus ICL23D boot image - DOWNLOAD - MD5: 8ad48c176eb12b33e436f38a8d9711f8
Galaxy Nexus ICL23D recovery image - DOWNLOAD - MD5: c02fe19e8b0d162e225597aab26704cb
Galaxy Nexus ICL23D system image (tar.gz) - DOWNLOAD - MD5: 7a47451ace5689b0fefbec64a7b911a0
Click to expand...
Click to collapse
DO NOT FLASH
LET THE PORTING BEGIN!
If you like this thread: Press the Thanks Button
Superboot - rooting the Galaxy Nexus
Superboot is a boot.img that when booted, will root your device the first time you boot (installing su and the superuser APK). No need to flash any partitions, no need to mess around with ADB, no messing with the contents of your data partition, no overwriting the shipped ROM on your device, just boot the boot image using the instructions below and you're done!
APPLY THIS AT YOUR OWN RISK!
Superboot r1 - DOWNLOAD (Filesonic) - MD5: 1e988380d12fa3a4cc3e9db975e96b27
The superboot image is also 'insecure', allowing you to use 'adb remount' as well as having full ADB root access to your device until such time as you reboot after running this process (it's a non permanent ADB root as it's a 'fastboot boot' and not a 'fastboot flash').
How to use Superboot - Windows, Linux and OSX
- Download the Superboot zip file above and extract to a directory
- Put your device in bootloader mode - Turn off the phone then turn on with the 'volume up' and 'volume down' buttons both pressed to enter the bootloader (as pictured below)
- WINDOWS - double click 'install-superboot-windows.bat'
- MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-mac.sh' followed by './install-superboot-mac.sh'
- LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-linux.sh' followed by './install-superboot-linux.sh'
Note: If you are using a retail Galaxy Nexus, you may need to unlock the bootloader first, using './fastboot-windows oem unlock' (or the appropriate version for your machine). Note that the OEM unlock sequence wipes your device.
Click to expand...
Click to collapse
All Credits to Modaco.com
Haha that pic was took with a iPhone. There's got to be a joke there somewhere ..
Source-built from CyanogenMod 10.0 (jellybean tree)
New in "ver2":
- Support for newer CM11 zips
- Off-mode charging fixed (recovery is no longer usable behind it)
- Images resized to better fit the small screen (and save a bit of space)
CWM v6.0.2.8 with off-mode charging
http://goo.gl/gfKyNS
c7f804a6d9980745f8577cc33504ae3f
{
"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"
}
Alternate mirror: https://www.mediafire.com/?ao1688h7gtta881
CWM v6.0.2.8 without off-mode charging (boots into recovery when plugged in - useful for broken power buttons)
http://goo.gl/eiW0ib
f75223f8e95bf2d928d45c562cc4df26
Alternate mirror: https://www.mediafire.com/?on2rstc0nvq7xo6
Install with your current recovery (most should work).
Or, you can extract recovery.img from the zip and flash it with fastboot.
Building yourself
I won't be going over basic building stuff, but because our newer kernel used on ICS & up is too big it makes it a little more difficult to build, so I'll explain that.
With all of the source from my manifest (https://github.com/WinSuk/android/tree/jellybean), build the recovery normally (make recoveryimage).
Then, copy the last command it runs before finishing, but replace the kernel with recovery_kernel in device/htc/liberty/prebuilt
Something like this:
Code:
out/host/linux-x86/bin/mkbootimg --kernel device/htc/liberty/prebuilt/recovery_kernel --ramdisk out/target/product/liberty/ramdisk-recovery.img --cmdline "no_console_suspend=1 console=null" --base 0x12c00000 --output out/target/product/liberty/recovery.img
The resulting out/target/product/liberty/recovery.img should be small enough to flash with fastboot
To disable offmode charging, open device/htc/msm7x27-recovery/BoardConfigCommon.mk with a text editor, and uncomment (remove #) the following line:
Code:
#BOARD_RECOVERY_OFFMODE_CHARGING := false
then rebuild
Kernel source:
https://github.com/WinSuk/htc-kernel-msm7227/tree/master-tlscompat
Commit: 104446203d2871ffe595a2266a9e109157c80ea8
Compiled with cyanogen_msm7227_recov_defconfig and arm-eabi-4.4.0
Updated with recovery-installable zips, and fixed a bug with the power button on the version without offmode charging
WinSuk said:
Updated with recovery-installable zips, and fixed a bug with the power button on the version without offmode charging
Click to expand...
Click to collapse
I have extracted the recovery.img and placed it in my folder with the fastboot.exe.
What is the fastboot command for fastboot flashing the recovery.img file?
Is it "fasboot flash recovery.img" or is there something more complicated?
Revolutionary recovery wouldn't let me do anything. Just showed me a screen with "Revolutionary" no matter what I selected in recovery.
duckredbeard said:
I have extracted the recovery.img and placed it in my folder with the fastboot.exe.
What is the fastboot command for fastboot flashing the recovery.img file?
Is it "fasboot flash recovery.img" or is there something more complicated?
Revolutionary recovery wouldn't let me do anything. Just showed me a screen with "Revolutionary" no matter what I selected in recovery.
Click to expand...
Click to collapse
fastboot flash recovery recovery.img
I have a pretty dumb question I'm sure... I have an Aria I use as an ipcam, and when it reboots when plugged in (randomly happens.. kernel crash or what not), it boots in CWM and I have to poke it to boot into the ROM. So I read that it might be CWM doing it, and I'm using an ancient 2.5.0.1.
I've tried flashing this a few times, it doesn't fail, but doesn't update either. HBoot is really old (0.57.0000) on it, so that might be part of it.
I don't want to do anything special to the thing, just want it to not get stuck in CWM when it reboots itself every 2-3 days.
Recovery updated Download links in first post
Support for newer CM11 packages has been added, and the off-mode charging derpyness (where recovery was still usable behind it) has been fixed.
I also resized some of the images to better fix the small screen, which also saves a bit of space.
I haven't changed the version number from 6.0.4.8, as it's still based on that same version of ClockworkMod.
Galaxy Tab 4 7.0 (3G) system dump
~~~~~~~
Apps:
HERE
~~~~~~~
priv-app - folder:
HERE
~~~~~~~
media - folder:
HERE
~~~~~~~
Framework:
HERE
~~~~~~~
lib - folder:
HERE
~~~~~~~
bin - folder:
HERE
~~~~~~~
vendor - folder:
HERE
~~~~~~~
etc - folder:
HERE
~~~~~~~
recovery.img:
(I´m not sure if this image is working please give feedback)
HERE
~~~~~~~
boot.img:
(I´m not sure if this image is working please give feedback)
HERE
~~~~~~~
build.prop:
HERE
~~~~~~~
Note: I´m not responsible for any damage to your device
~~~~~~~
Wrong device ?
Galaxy Tab 4 10.1 dump here
Galaxy Tab 4 8.0 dump Coming soon
Make your own dumps Coming soon
Thank you so much bro
Waiting for this \m/
Sent from an expensive Toaster (SM-T211)
Boot
Hey I'm trying to make a boot.img dump myself. Did you find out if you dumped the right mount point? I downloaded Partition Table from the play store and it shows all the mount points but I'm not sure which one is the boot. It doesn't actually specify a boot partition and if i go into the /dev/block/platform/soc,2/by-name folder it doesn't have a boot file in there or an aboot file. So I'm confused.
ubuntu is the solution
TheOriginalist said:
Hey I'm trying to make a boot.img dump myself. Did you find out if you dumped the right mount point? I downloaded Partition Table from the play store and it shows all the mount points but I'm not sure which one is the boot. It doesn't actually specify a boot partition and if i go into the /dev/block/platform/soc,2/by-name folder it doesn't have a boot file in there or an aboot file. So I'm confused.
Click to expand...
Click to collapse
Hey,
I can't help you with that using a phone.
I have done this multiple times using Ubuntu.
PHP:
sudo apt-get install abootimg
sudo abootimg -x boot.img
mkdir workspace
cd workspace
gzip -cd initrd.img | cpio -i
I could upload the dump, too !?
UAdeveloper said:
Hey,
I can't help you with that using a phone.
I have done this multiple times using Ubuntu.
PHP:
sudo apt-get install abootimg
sudo abootimg -x boot.img
mkdir workspace
cd workspace
gzip -cd initrd.img | cpio -i
I could upload the dump, too !?
Click to expand...
Click to collapse
Wait I don't quite understand did you successfully dump the boot img from the tablet? Cause it looks like your just making a boot img there (not too linux friendly I mainly use windows)
TheOriginalist said:
did you successfully dump the boot img from the tablet?
Click to expand...
Click to collapse
Yes (using the linux method) ...
Do you need it? I could upload it tomorrow
Hi, all I really need is the keyboard files but, I cannot see the files. I can ony see so many and the list cuts off. Also, I cannot download the .zips. Is there any way you could just link me to the keyboard files, please?
{
"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"
}
UAdeveloper said:
Wrong device ?
Galaxy Tab 4 10.1 dump here
Galaxy Tab 4 8.0 dump Coming soon
Make your own dumps Coming soon
Click to expand...
Click to collapse
still waiting for 'make your own dumbs'
bubenking said:
still waiting for 'make your own dumbs'
Click to expand...
Click to collapse
I don`t work with Samsung Tab´s anymore, sorry.
If someone wants me to link him to his work, pm me.