Mengganti kartu Sim Indosat lama dengan Kartu SIM Nano Indosat/Ooredoo 4G/LTE

Pastikan nomor SIM-nya terdaftar sesuai data diri di-KTP anda.

Untuk mengeceknya, gunakan URL https://myim3.indosatooredoo.com/registration/index.

Bila anda memerlukan penyesuaian data diri, lakukan dengan mengirimkan SMS ke-4444 dengan format:
ULANG#[no_ktp]#[no_kk]#
tanpa tanda [], contoh ULANG#1234567890123456#1234567890123456#.
Anda akan menerima SMS jawaban "Terima kasih nomor Anda telah BERHASIL diregistrasi ulang". Catatan: hanya berlaku untuk eKTP.

Selanjutnya, siapkan copy KTP dan KK untuk melakukan penggantian Kartu SIM Indosat lama dengan Kartu SIM Nano Indosat/Ooredoo 4G/LTE di-Gerai Indosat/Ooredoo terdekat. Jam operasional gerai 8:00 s/d 20:00, Senin s/d Sabtu.

Petugas akan melakukan validasi data diri anda dan memberikan Kartu SIM Nano Indosat/Ooredoo 4G/LTE. Petugas akan menyampaikan bahwa kartu SIM baru anda baru bisa digunakan 1 jam kemudian dan menginstruksikan agar kartu lama dimatikan/tidak digunakan.

Setelah 2 jam (disuruhnya sih 1 jam), viola, Kartu SIM Nano Indosat/Ooredoo 4G/LTE sudah bisa digunakan tanpa kendala.

Anda juga akan merima pesan SMS "Kartu SIM Anda berhasil diganti, Terima kasih!" dan "Pelanggan Setia Indosat Ooreddo, permintaan layanan Penggantian Kartu Pascabayar Anda 62816xxxxx telah diproses, Selamat menggunakan layanan dari Indosat Ooredoo. Terima kasih.".

Android adb: analyzing Android

Adb for analyzing Android 

Personal note

in linux

adb logcat -d -b events | grep boot

in windows 

adb logcat -d -b events | findstr /L "boot" or
adb logcat -d -b events | findstr /R "boot"

in linux

adb logcat -d | grep preload

in windows 

adb logcat -d -b events | findstr /L "preload" or
adb logcat -d -b events | findstr /R "preload"

To get android property
adb shell getprop

List AMD Processor does not need AMD Catalyst in Windows 10 x64 and x32

List AMD Processor does not need AMD Catalyst in Windows 10 x64 and x32:

• AMD A8-7410
• AMD A8-4500M
• AMD A6-6310
• AMD A4-4020

From original  (as a copy in case the reference deleted):

This document provides information about Windows® 10 driver support for APUs with AMD Radeon™ Graphics.

For the purpose of this document the term “APU Graphics” refers to the On-die graphics adapter on an AMD APU that is the designated primary graphics controller on a system.

This document does not apply to Discrete AMD Radeon™ Graphics products. For more information about Windows 10 driver support for Discrete AMD Radeon™ Graphics products, please visit: Windows® 10 Driver Support for Discrete AMD Radeon™ Graphics Products

The following AMD APU products with AMD Radeon™ Graphics support up to WDDM 2.0 and DirectX® 12 on Windows® 10:

• AMD A6/A8/A10/FX-8000 Series APUs
• AMD A4 Pro/A6 Pro/A8 Pro/A10 Pro/A12 Pro-8000 Series APUs
• AMD E1/E2/A4/A6/A8/A10/FX-7000 Series APUs (except A4-7300 APUs)
• AMD A4 Pro/A6 Pro/A8 Pro/A10 Pro-7000 Series APUs
• AMD E1/E2/A4/A6-6#10 Series APUs
• AMD E1/A4/A10 Micro-6000 Series APUs
• AMD A4-5000, A4-5100 and A6-5200 APUs
• AMD Athlon 5000 series APUs
• AMD Sempron 2650 and 3850 APUs
  
• AMD E1-2000 Series and E2-3000 Series APUs
• AMD A4/A6-1000 Series APUs

The following AMD APU products with AMD Radeon™ Graphics support up to WDDM 1.3 and DirectX® 11 on Windows® 10

• AMD A4-7300 APUs
• AMD A4/A6/A8/A10-6000 Series APUs
• AMD A4/A6/A8/A10-5000 Series APUs (except A4-5000, A4-5100, and A6-5200)
• AMD A4/A6/A8/A10-4000 Series APUs

NOTE: If your graphics product is included on the list of supported products above, please install the latest AMD Catalyst™ Driver for Windows® 10 to fully enable its feature set. AMD Catalyst™ Driver can be downloaded from: http://www.amd.com/drivers

The following AMD APU products with AMD Radeon™ Graphics support up to WDDM 1.2 and DirectX® 11 on Windows 10:

• AMD A4/A6/A8-3000 Series APUs
• AMD E2-2000 APU
• AMD E1/E2-1000 Series APUs
• AMD E-200/300/400 Series APUs
• AMD C-Series APUs
• AMD Z-Series APUs

NOTE: These APU products must be installed only using the display driver version available via Windows Update. If you have upgraded to Windows® 10, please DO NOT install the AMD Catalyst™ Driver. Instead, enable Windows Update and allow it to detect and install the appropriate driver.

If you have already upgraded to Windows® 10 and installed the AMD Catalyst™ Driver, please follow the steps listed below to resolve this issu

1. Uninstall the AMD Catalyst™ Driver using the Program and Features option in the Control Pane
2. Reboot the system
3. Use Windows Update to install the appropriate graphics driver for the APU.

References:

https://community.amd.com/docs/DOC-1312

How to install Raspbian Stretch to SD Card for Raspberry-pi using Windows (bonus how to unlock SD Card using Windows)

You need to download Raspbian Stretch from https://www.raspberrypi.org/downloads/
File 2017-11-29-raspbian-stretch.zip size: 1.64 GB (1,764,972,666 bytes)

Extract it.
File 2017-11-29-raspbian-stretch.img size: 4.58 GB (4,919,918,592 bytes)

Download and install Win32 Disk Imager from https://sourceforge.net/projects/win32diskimager/. 

Step to write your Raspbian Stretch image into SD Card:

1. Put your SD Card into slot and run Win 32 Disk Imager.
2. Select image files and point device to your SD Card.
3. Click Write and wait until it finish. It will take some times, the image size is big :).

It takes 5-10 minues on my PC.

In case your SD Card state Write Protect or something like that, and you are sure that your SD Card switch is Unlock please follow these to unlock your SD Card (bonus): 

Caution: Use with your own risk! These instructions below may destroy your existing system/data on your hard drive if not careful.

A. Remove SD Card protection policy by running regedit

1. Open Computer -> HKEY_LOCAL_MACHINE -> System -> Current Control Set -> Control
2. Create (if not exist) or edit Storage Device Policies to DWORD (32 bit) Value to 0
3. Restart your windows 

B. Unlock and remove any partition on SD Card

1. Run diskpart
   Microsoft DiskPart version 10.0.16299.15
   Copyright (C) Microsoft Corporation.
   On computer: DEDET2013
2. List your disk (CAUTION: Please read/select your disk carefully otherwise you may remove partition on your hard drive)
   DISKPART> list disk
     Disk ###  Status         Size     Free     Dyn  Gpt
     --------  -------------  -------  -------  ---  ---
     Disk 0    Online          465 GB   451 MB        *
     Disk 1    Online         7580 MB  3072 KB
3. Choose/select your sd card
   DISKPART> select disk 1
   Disk 1 is now the selected disk.
   DISKPART> list disk
     Disk ###  Status         Size     Free     Dyn  Gpt
     --------  -------------  -------  -------  ---  ---
     Disk 0    Online          465 GB   451 MB        *
   * Disk 1    Online         7580 MB  3072 KB
4. It will mark * for selected disk, now you can unlock and remove any partition on selected disk.
   DISKPART> clean
   DiskPart succeeded in cleaning the disk.
5. Exit diskpart by type exit command
   DISKPART> exit

Running Raspberry Stretch for first time:

1. Default user is pi with password raspberry, to change default password for pi user:
   $ passwd 
2. Set password for root:
   $ sudo passwd root

References: 

• https://www.raspberrypi.org/documentation/installation/installing-images/ 
• https://www.raspberrypi.org/documentation/installation/installing-images/windows.md 
• https://www.easeus.com/storage-media-recovery/remove-write-protection-in-windows-10-8-7.html 

Detecting DNS flood using dns-flood-detector

You need to install dns-flood-detector
# apt-get install dns-flood-detector

dns-flood-detector will give you warning in dmesg something like:
[1309426.142779] TCP: request_sock_TCP: Possible SYN flooding on port 53. Sending cookies.  Check SNMP counters.

To show where it is come from
# /etc/init<dot>d/dns-flood-detector status
* dns-flood-detector<dot>service - LSB: start and stop the dns-flood-detector daemon
   Loaded: loaded (/etc/init<dot>d/dns-flood-detector; generated; vendor preset: enabled)
   Active: active (running) since Fri 2018-01-05 14:25:46 WIB; 2 weeks 1 days ago
     Docs: man:systemd-sysv-generator(8)
    Tasks: 2 (limit: 4915)
   CGroup: /system<dot>slice/dns-flood-detector<dot>service
           `-475 /usr/bin/dns-flood-detector -d -v -v -t5 -w3
Jan 20 18:09:20 mars dns_flood_detector[475]: source [66<dot>220<dot>156<dot>144] - 3 tc…AA]
Jan 20 18:09:23 mars dns_flood_detector[475]: source [173<dot>252<dot>90<dot>118] - 3 tc…AA]
Warning: Journal has been rotated since unit was started<dot> Log output is incomplete or unavailable<dot>
Hint: Some lines were ellipsized, use -l to show in full<dot>

or
# service dns-flood-detector status
* dns-flood-detector<dot>service - LSB: start and stop the dns-flood-dete
ctor daemon
   Loaded: loaded (/etc/init<dot>d/dns-flood-detector; generated; vendor preset: ena
bled)
   Active: active (running) since Fri 2018-01-05 14:25:46 WIB; 2 week
s 1 days ago
     Docs: man:systemd-sysv-generator(8)
    Tasks: 2 (limit: 4915)
   CGroup: /system<dot>slice/dns-flood-detector<dot>service
           `-475 /usr/bin/dns-flood-detector -d -v -v -t5 -w3
Jan 20 18:09:20 mars dns_flood_detector[475]: source [66<dot>220<dot>156<dot>144] -
3 tcp qps : 3 udp qps [1 qps A] [5 qps AAAA]
Jan 20 18:09:23 mars dns_flood_detector[475]: source [173<dot>252<dot>90<dot>118] -
3 tcp qps : 3 udp qps [1 qps A] [5 qps AAAA]
Warning: Journal has been rotated since unit was started<dot> Log output is incomple
te or unavailable<dot>

Lets we find out who they are
# whois 66<dot>220<dot>156<dot>144
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www<dot>arin<dot>net/whois_tou<dot>html
#
# If you see inaccuracies in the results, please report at
# https://www<dot>arin<dot>net/public/whoisinaccuracy/index<dot>xhtml
#
#
# The following results may also be obtained via:
# https://whois<dot>arin<dot>net/rest/nets;q=66<dot>220<dot>156<dot>144?showDetails=true&showARIN=false&showNonArinTopLevelNet=false&ext=netref2
#
NetRange:       66<dot>220<dot>144<dot>0 - 66<dot>220<dot>159<dot>255
CIDR:           66<dot>220<dot>144<dot>0/20
NetName:        TFBNET3
NetHandle:      NET-66-220-144-0-1
Parent:         NET66 (NET-66-0-0-0-0)
NetType:        Direct Assignment
OriginAS:       AS32934
Organization:   Facebook, Inc<dot> (THEFA-3)
RegDate:        2009-02-13
Updated:        2012-02-24
Ref:            https://whois<dot>arin<dot>net/rest/net/NET-66-220-144-0-1
...

and
# whois 173<dot>252<dot>90<dot>118
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www<dot>arin<dot>net/whois_tou<dot>html
#
# If you see inaccuracies in the results, please report at
# https://www<dot>arin<dot>net/public/whoisinaccuracy/index<dot>xhtml
#
#
# The following results may also be obtained via:
# https://whois<dot>arin<dot>net/rest/nets;q=173<dot>252<dot>90<dot>118?showDetails=true&showARIN=false&showNonArinTopLevelNet=false&ext=netref2
#
NetRange:       173<dot>252<dot>64<dot>0 - 173<dot>252<dot>127<dot>255
CIDR:           173<dot>252<dot>64<dot>0/18
NetName:        FACEBOOK-INC
NetHandle:      NET-173-252-64-0-1
Parent:         NET173 (NET-173-0-0-0-0)
NetType:        Direct Assignment
OriginAS:       AS32934
Organization:   Facebook, Inc<dot> (THEFA-3)
RegDate:        2011-02-28
Updated:        2012-02-24
Ref:            https://whois<dot>arin<dot>net/rest/net/NET-173-252-64-0-1

Ops they are Facebook.inc :D

Lets we block it
# ipset add mynetrules 66<dot>220<dot>156<dot>144
# ipset add mynetrules 173<dot>252<dot>90<dot>118
# iptables -L | grep mynetrules
DROP       all  --  anywhere             anywhere             match-set mynetrules src

These are how to block class C
Jan 21 10:11:31 mars dns_flood_detector[475]: source [173<dot>252<dot>124<dot>119] - 3 t…AA]
Jan 21 10:11:34 mars dns_flood_detector[475]: source [173<dot>252<dot>124<dot>125] - 3 t…AA]
Jan 21 10:11:34 mars dns_flood_detector[475]: source [173<dot>252<dot>124<dot>126] - 3 t…AA]
Jan 21 10:11:34 mars dns_flood_detector[475]: source [173<dot>252<dot>124<dot>123] - 3 t…AA]

Jan 21 10:11:34 mars dns_flood_detector[475]: source [173<dot>252<dot>124<dot>124] - 3 t…AA]

Just check one of them
# whois 173<dot>252<dot>124<dot>124
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www<dot>arin<dot>net/whois_tou<dot>html
#
# If you see inaccuracies in the results, please report at
# https://www<dot>arin<dot>net/public/whoisinaccuracy/index<dot>xhtml
#
#
# The following results may also be obtained via:
# https://whois<dot>arin<dot>net/rest/nets;q=173<dot>252<dot>124<dot>124?showDetails=true&showARIN=false&showNonArinTopLevelNet=false&ext=netref2
#
NetRange:       173<dot>252<dot>64<dot>0 - 173<dot>252<dot>127<dot>255
CIDR:           173<dot>252<dot>64<dot>0/18
NetName:        FACEBOOK-INC
NetHandle:      NET-173-252-64-0-1
Parent:         NET173 (NET-173-0-0-0-0)
NetType:        Direct Assignment
OriginAS:       AS32934
Organization:   Facebook, Inc<dot> (THEFA-3)
RegDate:        2011-02-28
Updated:        2012-02-24
Ref:            https://whois<dot>arin<dot>net/rest/net/NET-173-252-64-0-1

Lets we block it
# ipset add mynetrules 173<dot>252<dot>124<dot>0/24