*#2663#, actualizar firmware touch tsp

luego ajustes, entrada de texto y idioma, abajo de todo hay una opción que dice velocidad del puntero, subir la velocidad (probar antes y despues)

adb start-server adb devices (verify your device is shown) adb shell

~ # mount rootfs on / type rootfs (rw) tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755) devpts on /dev/pts type devpts (rw,relatime,mode=600) proc on /proc type proc (rw,relatime) sysfs on /sys type sysfs (rw,relatime) /dev/block/platform/omap/omap_hsmmc.0/by-name/cache on /cache type ext4 (rw,nodev,noatime,nodiratime,barrier=1,data=ordered) /dev/block/platform/omap/omap_hsmmc.0/by-name/userdata on /data type ext4 (rw,nodev,noatime,nodiratime,barrier=1,data=ordered) /dev/block/platform/omap/omap_hsmmc.0/by-name/system on /system type ext4 (rw,nodev,noatime,nodiratime,barrier=1,data=ordered)

~ # umount /data

adb pull /dev/block/platform/omap/omap_hsmmc.0/by-name/userdata (referencia: http://ph34r.net/2013/03/31/acquiring-android-forensic-images/)

Terminal Method:

  Download RomDump from the link given below, extract the file named ‘install’ from the downloaded zip archive to your computer and copy it to the root of your phone’s storage card.
  Launch Android Terminal Emulator (or any other terminal app of your choice) on your Android phone and enter these commands:

  su -
  cat /sdcard/install >/data/local/install
  chmod 04755 /data/local/install
  /data/local/install

  You will see some output of the above command. Wait till the output finishes.
  After this last line has appeared, enable and then disable Wi-Fi on your phone. If it was already enabled, disable, enable and then disable it again.
  Type this command in Terminal Emulator:

  /system/bin/romdump

  Wait patiently till the process finishes and you’re done. You may now exit Terminal Emulator.

(referencia: http://dan3lmi.blogspot.com.es/2012/10/mobile-forensics-imaging-android.html)

  Enter the following command:

  cat proc/mtd

   (o tambien mount - > cat /proc/emmc y cat /proc/dumchar_info)

  You will get an output similar to this (results may differ from the output below and you must proceed according to the output that you get):

  dev:    size   erasesize  name
  mtd0: 000a0000 00020000 "misc"
  mtd1: 00480000 00020000 "recovery"
  mtd2: 00300000 00020000 "boot"
  mtd3: 0fa00000 00020000 "system"
  mtd4: 02800000 00020000 "cache"
  mtd5: 093a0000 00020000 "userdata"

  To dump the recovery image to your SD card, make note of the first word of the line which says “recovery” in the end. It is "mtd1" in case of this example but may be another entry for you. Now use this command, replacing "mtd1" according to the mtdN in your output, if different:

  dd if=/dev/mtd/mtd1 of=/sdcard/recovery.img bs=4096

  Similarly, to dump the boot image to your SD card, make note of the first word of the line which says "boot" in the end, which is "mtd2" in our case but may differ for you. Use this command now, replacing "mtd2" according to the "mntdN" entry in your output, if different:

  dd if=/dev/mtd/mtd2 of=/sdcard/boot.img bs=4096

Now, the recovery.img and boot.img are backed up on the root of your SD card.

(referencia: http://dan3lmi.blogspot.com.es/2012/10/mobile-forensics-imaging-android.html)

https://blog.avast.com/2014/07/09/android-foreniscs-pt-2-how-we-recovered-erased-data/

http://www.sleuthkit.org/autopsy/features.php

You can enable this by going to Settings→Developer Options, then checking the box next to “Bluetooth HCI Snoop Log.(android >= 4.4)

adb shell cat /etc/bluetooth/bt_stack.conf –>

default trace level 3 (middle)

get btsnoop file from /sdcard/btsnoop_hci.log or from “filename” above in bt_stack.conf (rooted phone, change bt_stack at your pleasure)

wireshark open, frame display - hci find - decode tab - ¿link key? as example

http://www.fte.com/WebHelp/BPA600/Content/Documentation/WhitePapers/BPA600/Encryption/GettingAndroidLinkKey/UsingComProbeSWToGetLinkKey.htm

en samsung se podria obtener asi: adb shell dumpsys bluetooth_manager > bt_snoop.log

caso samsung: flash complete, flash combination (to get adb access, or enable usb debugging) flash complete again (usb debugging activated) boot step previous to “insert gmail account” key: adb shell content insert –uri content:settings/secure –bind name:s:user_setup_complete –bind value:s:1 click next use google now to enter in settings (ajustes) developer options OEM unlock enable factory reset OK http://forum.gsmhosting.com/vbb/f777/universal-samsung-galaxy-s6-s7-note-5-note-7-frp-bypass-all-samsung-devices-2124806/ (metodo 1234 at dial) recuperar script.bin en tablets allwinner: CLS MODE CON: COLS=78 LINES=3 SET TITLE=Back up Script.bin SET AUTHOR=By mrkindaiji SET MODIFY_LAST=09/7/2012 :STARTUP COLOR 07 TITLE %TITLE% %AUTHOR% cls mkdir script_bin cls adb.exe devices cls adb.exe shell “mount -o remount,rw /system” cls adb.exe shell mkdir /sdcard/nanda cls adb.exe shell mount -t vfat /dev/block/nanda /sdcard/nanda cls adb.exe pull /sdcard/nanda/script.bin script_bin cls adb.exe shell umount /sdcard/nanda cls exit getenforce returns Enforcing Then maybe you should call setenforce 0 mount -o rw,remount /system setenforce 1