Flash Android Factoryimage without loss of Data ....

... with fastboot (works fine with eg. Android 6.0.0)

Make sure your computer recognizes your device by typing: fastboot devices

If not, then try this:

# reboot into fastboot mode
adb reboot bootloader

# grab you fastboot/bootloader device ids
lsusb
> Bus 001 Device 035: ID **18d1:d00d** Google Inc.

# install the ids into /etc/udev/rules.d/99-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="d00d", MODE="0666", OWNER="username"

# restart udev
/etc/init.d/udev restart

# try fastboot (only on bootloader mode)
fastboot devices

Unlock your bootloader (if you have not already done so): fastboot oem unlock
You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept. Note: you use the volume keys to change the option and the power button to accept. You cannot use the touch screen.
#Reboot by typing: 
fastboot reboot-bootloader
#Flash the bootloader: 
fastboot flash bootloader bootloader-mako-makoz10o.img (or whatever the name of the bootloader image is).
#Reboot: 
fastboot reboot-bootloader
#Flash the radio:  (if available)
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img (or whatever the name of the radio image is).
#Reboot: 
fastboot reboot-bootloader
#Flash the system partition: 
fastboot flash system system.img
Optional, but read note. Flash the data partition: 
fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.
#Flash the kernel/ramdisk: 
fastboot flash boot boot.img
#Flash the recovery partition: 
fastboot flash recovery recovery.img (don't flash if you have a custom recovery rom)
#Flash the vendor: (if available)
fastboot flash vendor vendor.img
#Erase the cache partition: 
fastboot format cache
#Reboot: 
fastboot reboot
Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache. 

#Reboot:
adb reboot bootloader
#Flash the recovery partition: 
fastboot flash recovery twrp-2.8.7.0-mako.img (or whatever the name of the recovery image is).
#Reboot: 
fastboot reboot-bootloader
#Optional flash SuperSu with your favorite RecoveryROM to have rootaccess

#Reboot to Recovery from fastboot (eg. if the Volumebuttons are defect)
fastboot boot recovery.img (or whatever the name of the recovery image is).

Fedora 18 (preconfigure)

sudo yum install vino

you can change it after installing by using the hostnamectl command. Hostname is now in your /etc/hostname file and not in /etc/sysconfig/network
sudo hostnamectl set-hostname <newhostname> --static

sudo service sshd start
sudo chkconfig sshd on
service sshd status

sudo systemctl stop firewalld.service
sudo systemctl disable firewalld.service

sudo vi /etc/sysconfig/selinux
# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
#enforcing - SELinux security policy is enforced.
#permissive - SELinux prints warnings instead of enforcing.
#disabled - SELinux is fully disabled.
SELINUX=disabled # change
# SELINUXTYPE= type of policy in use. Possible values are:
#targeted - Only targeted network daemons are protected.
#strict - Full SELinux protection.
SELINUXTYPE=targeted

LTE on N4

Mit Hilfe der Tastenkombination *#*#4636#*#* hat der Besitzer im darauf erscheinenden Telefon-Menü die LTE-Fähigkeit seines Nexus 4 aktivieren können.

Reduce REDRAW with launcherpro/ADW

If you use ADW or LauncherPro and if after using your browser, email or any other apps for awhile, then if you press the 'HOME' button, if it takes forever to redraw your home screen, and you are sick of that HORRIBLE LAG, then try this: In a terminal,
type su and enter.
Then type echo ro.HOME_APP_ADJ=1 >> /data/local.prop and enter.
Then reboot.
Now evaluate whether or not this fixes your lag.

If you want to undo what this command does, simply remove that toggle from: /data/ local.prop

Wii Controller on Android 4.2+

To get around the issue with there not being an ascii equivalent of the the android or wiimote mac, we can change the android mac to 30:30:30:30:30:30, giving us a pin of "000000". This is confirmed working on my Nexus 7 2013 with Android 4.3, and would probably work on

To change the (rooted) Android MAC, turn off bluetooth and then run the following in a shell:

su
cd /persist/bluetooth
cp .bdaddr .bdaddr.orig
echo -n 000000 > .bdaddr
Note, that is six zeros in the echo line. Now restart bluetooth and the Android BT MAC will have changed. Use the red button under the battery cover of the wiimote to pair with pin "000000".

Now the problem is that we need some kind of software to make the wiimote useful in games... Maybe RWiimote or "Wiimote Controller" can be modified to look for already-paired wiimotes instead of trying to handle the pairing automatically... anyone have ideas here?

Xoom MZ601 Tablet - Install CWM-Recovery (under Linux)

Step 1:

Setup your Xoom to enable “USB Debugging”, found Settings -> Applications -> Development

Step 2:

Install Android SDK.

Step 3:

Reboot into “Fastboot” mode, by holding down the “Volume Down” button while you press the "Power Button". You will see the Text "Fastboot" in the first line of the Tabletscreen.

Step 4:

Change to the Directory where the fastboot binary from the SDK is installed.

Run fastboot oem unlock to unlock the Bootloader.

Step 5:

Download the ClockworkMod Recovery ROM from here and copy it to the same directory where the fastboot binary is located.

Step 6:

Flash the ClockworkMod Recovery ROM with following command:

fastboot flash recovery recovery-clockwork-4.0.0.4-stingray.img

Step 7:

Now enter “Recvoery Mode”, by pressing “Volume Down” about 2 seconds after DualCore Motorola logo is on the screen. Choose “Recovery Mode” by pressing “Volume Down”, then press “Volume Up”.

Step 8:

Select "Backup and Restore" from Menue by changing to it with the "Volume Up/Down"  and select it with the Power Button.

Flash blob on ASUS Transformer 101(G)

1. Download latest firmware from asus (TF101)
2. Unzip using ES File Explorer (you will have another zip)
3. Unzip blob from extracted zip to /sdcard
4. Download Terminal Emulator
5. Open Terminal Emulator and switch to root

su

6. Ran the dd-command:

dd if=/sdcard/blob of=/dev/block/mmcblk0p4

7. Ran the sync-command (not required as it only syncs filesystems and no block devices, but it feels good to do)

sync;sync

8. Wait two minutes (should not be needed either)
9. Shutdown the device
10. Boot the device. you will see a progress bar.

Depending on the ROM you previously used, the transformer might be able to boot. 

It will take feeled 15 min. to be able to log in ;-)

If it does not boot, don't worry:

- Hold down the minus-volume button (down) when booting
- Wait till the message about cold-boot appears
- Re-press Down to switch the icon from Android to 'WIPE DATA'-icon.
- Press Up and Press Up again to confirm.

Even if your transformer did boot fine, without wiping, I do recommend a factory reset (via method above or via settings).

Be aware that this will erase all your data, also on the internal sdcard. External SD-card will not be touched.