newspaint

Documenting Problems That Were Difficult To Find The Answer To

Monthly Archives: January 2016

Monopoly Deal Sort Order

From a new pack the cards are (bottom face down to top face down):

* (Brown) Old Kent Road
* (Brown) Whitechapel Road
* (Light Blue) Euston Road
* (Light Blue) Pentonville Road
* (Light Blue) The Angel, Islington
* (Purple) Northumberland Avenue
* (Purple) Pall Mall
* (Purple) Whitehall
* (Orange) Bow Street
* (Orange) Marlborough Street
* (Orange) Vine Street
* (Red) Fleet Street
* (Red) Strand
* (Red) Trafalgar Square
* (Yellow) Coventry Street
* (Yellow) Piccadilly
* (Yellow) Leicester Square
* (Green) Bond Street
* (Green) Oxford Street
* (Green) Regent Street
* (Rich Blue) Mayfair
* (Rich Blue) Park Lane
* (Black) Fenchurch St. Station
* (Black) Kings Cross Station
* (Black) Liverpool St. Station
* (Black) Marylebone Station
* (Pale Green) Electric Company
* (Pale Green) Water Works
* (Brown/Light Blue) Property Wild Card
* (Light Blue/Black) Property Wild Card
* (Purple/Orange) Property Wild Card
* (Purple/Orange) Property Wild Card
* (Red/Yellow) Property Wild Card
* (Red/Yellow) Property Wild Card
* (Green/Rich Blue) Property Wild Card
* (Green/Black) Property Wild Card
* (Black/Pale Green) Property Wild Card
* (Rainbow) Property Wild Card
* (Rainbow) Property Wild Card
* Deal Breaker
* Deal Breaker
* Forced Deal
* Forced Deal
* Forced Deal
* Sly Deal
* Sly Deal
* Sly Deal
* Just Say No
* Just Say No
* Just Say No
* Debt Collector
* Debt Collector
* Debt Collector
* It's My Birthday
* It's My Birthday
* It's My Birthday
* Double Rent
* Double Rent
* House
* House
* House
* Hotel
* Hotel
* Pass Go (x10)
* (Brown/Light Blue) Rent
* (Brown/Light Blue) Rent
* (Purple/Orange) Rent
* (Purple/Orange) Rent
* (Red/Yellow) Rent
* (Red/Yellow) Rent
* (Green/Rich Blue) Rent
* (Green/Rich Blue) Rent
* (Black/Pale Green) Rent
* (Black/Pale Green) Rent
* (Rainbow) Rent
* (Rainbow) Rent
* (Rainbow) Rent
* Bank 1M (x6)
* Bank 2M (x5)
* Bank 3M (x3)
* Bank 4M (x3)
* Bank 5M (x2)
* Bank 10M

Viber Location System Could Not Identify Your Location

I found Viber, one day, to be mysteriously pausing for 20-30 seconds after sending a message before getting the following error message:

The system could not identify your location. Your message was sent without location.

The system could not identify your location

The system could not identify your location

Then you would have to press Ok before your message would actually get delivered. So what was causing this? Turned out to be very simple (but you wouldn’t know unless you were told). And would probably only happen if you had blocked location reporting to the application using Privacy Guard for Android 5.1.1 (in CyanogenMod 12.1).

You need to press the following icon so that it turns grey in order to stop sending your location with messages.

Viber location on/off icon

Viber location on/off icon

This can be found next to where you enter text:

Press the location icon until it turns grey to turn off location transmission

Press the location icon until it turns grey to turn off location transmission

So that the icon should turn back to grey (location reporting disabled):

Viber location icon should be grey

Viber location icon should be grey

No more errors when sending messages!

Backing Up Encrypted Data Partition On Android Phone

I have CyanogenMod 12.1 (Android 5.1.1) on my phone. And the data partition is encrypted. Unfortunately TWRP (recovery) cannot access this encrypted data partition – so I cannot back up my data in recovery.

Making Backup From Phone

So, when booted normally into Android, one can use adb to make a backup of the data partition.

This Stack Exchange forum post suggests executing:

$ adb root # connect as root user when running adb shell in future
$ adb pull -p /dev/block/dm-0 /tmp/dm0backup.img

An alternative technique might be to use the following command (using the adb shell command will produce invalid output):

$ adb exec-out "cat /dev/block/dm-0 |gzip -c" >/tmp/dm0backup.gz
$ adb exec-out "gzip -c /dev/block/dm-0" >/tmp/dm0backup.gz

Pushing Backup Back To Phone

$ adb root # connect as root user when running adb shell in future
$ adb push -p /tmp/dm0backup.img /dev/block/dm-0

Pull the battery out (don’t shut down normally and give the system a chance to write all over your newly restored backup), put it back in, and restart the phone.

A better way is via TWRP documented in this forum post:

After booting phone into recovery (TWRP), in one terminal start:

me@myhost:~$ adb forward tcp:5678 tcp:8765
me@myhost:~$ adb shell
~ # busybox nc -l -p 8765 >/dev/block/mmcblk0p43

In another terminal run:

me@myhost:~$ dd if=your-image-file.img | nc localhost 5678

While the dd transfer is running you can check progress by finding the PID and running (in another terminal):

me@myhost:~$ kill -USR1 pid

Mounting Android Data Partition Image In Linux

F2FS

2019-04-26 update: note that F2FS, rather than ext4, has been used of late so mounting as ext4 may not work. If this is the case then you can install the following package for Ubuntu:

$ sudo apt-get install f2fs-tools
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following additional packages will be installed:
  libf2fs0
The following NEW packages will be installed:
  f2fs-tools libf2fs0
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 69.7 kB of archives.
After this operation, 226 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
...

The options required to mount F2FS are different from ext4 as the noload option is not supported. The norecovery option is required in order to mount as read-only (otherwise an error message of “cannot mount /dev/loop0 read-only” will be encountered).

# make a mount point
sudo mkdir /mnt/android

# mount dirty partition
#   noexec     - do not allow direct execution of binaries on mount
#   norecovery - do not attempt to replay dirty log which requires read-write
#   ro         - read only
sudo mount -o ro,norecovery,noexec -t f2fs /tmp/dm0backup.img /mnt/android

# look into mounted partition
ls -al /mnt/android

# unmount when you're finished
sudo umount /mnt/android

ext4

You can mount your backed up partition in Linux using the command (thanks to this article):

# make a mount point
sudo mkdir /mnt/android

# mount dirty partition
#   noload - don't load journal on mounting
#   noexec - do not allow direct execution of binaries on mount
#   ro     - read only
sudo mount -o ro,noexec,noload -t ext4 /tmp/dm0backup.img /mnt/android

# look into mounted partition
ls -al /mnt/android

# unmount when you're finished
sudo umount /mnt/android