simpletalk
The iPhone ‘iPhone’ could not be restored. An unknown error occurred
To restore iPhone with IOS firmware (IPSW) in recovery mode, but facing error as per title, may try to comment “gs.apple.com” in hosts file as image below:
Resource from: https://support.apple.com/en-my/HT201442
Flash ZTE Blade Q Lux
Trying to flash my niece’s phone with other rom which hope to have light weight OS, but no luck and end up with infinite boot screen load 🙁
Google around but also no luck to get any useful info (at least for this model of phone), some people sharing to use SP Flash, any other alternative which doesn’t work for my case too. End up I found the solution from ZTE site, which is to download the original rom and flash it…. phew….
- Download original rom from ZTE support or here.
- Copy into sd card (FAT32) formatted.
- Boot your phone into recovery mode by pressing Volume Up + Power key.
- Press Power key again once you are in recovery mode to enter menu selection mode.
- Press Volume Down key to select the menu and Volume Up key to enter.
(Recommend to wipe data/factory reset before apply update from sd card) - Done!
Landfill Harmonic
My New Gadget – Pine64
Here is how I did to install the OS (using MacOS)
- Download image from Pine64.com or Pine64.org.
- Format your Micro SD card using Disk Utility.
- Launch terminal and list the available disk using diskutil command as below (we going to use disk2 base on the identifier):
$ diskutil list /dev/disk0 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *500.3 GB disk0 1: EFI EFI 209.7 MB disk0s1 2: Apple_CoreStorage Macintosh HD 499.4 GB disk0s2 3: Apple_Boot Recovery HD 650.0 MB disk0s3 /dev/disk1 (internal, virtual): #: TYPE NAME SIZE IDENTIFIER 0: Apple_HFS Macintosh HD +499.1 GB disk1 Logical Volume on disk0s2 6D6E4910-AC62-4CC8-8F14-3A1227171470 Unlocked Encrypted /dev/disk2 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: FDisk_partition_scheme *32.4 GB disk2 1: DOS_FAT_32 ROOT 32.4 GB disk2s1
- Unmount the disk.
$ diskutil unmountDisk /dev/disk2 Unmount of all volumes on disk2 was successful
- Unzip the downloaded image and burn the img file into disk.
sudo dd if=/Users/dickson/Downloads/remix-v2.0-20160415-pine64-32GB.img of=/dev/disk2 bs=1m Password:
- Upon burning successfull, you will see the message as below:
$ sudo dd if=/Users/dickson/Downloads/remix-v2.0-20160415-pine64-32GB.img of=/dev/disk2 bs=1m Password: 30255+0 records in 30255+0 records out 31724666880 bytes transferred in 47100.051106 secs (673559 bytes/sec)
- Eject the disk if it still mounted.
$ diskutil eject /dev/disk2 Disk /dev/disk2 ejected
p/s: For Windows user, you may format using Disk Management tool under [Control Panel\System and Security\Administrative Tools\Computer Management], and burn img file using Win32DiskImager. And if you feel the writing speed is too slow in MacOS, you may try using rdisk instead of disk, as they using different write mechanism.
UPDATED : Just found this handy GUI tool etcher.io to burn image.
Credit to : rayhightower.com && www.hostvirtual.com && serenity.ee
Reset Epson L210 Counter / Ink Out Error
Received the used printer from brother.
As usual, “free + old” stuff normally doesn’t works well without some tweak …. phew….. here we go.
First, fixed “Service required” which mentioned printer counter exceed (can’t recall the exact message)
Download the Epson adjustment program here and follow instruction here.
Second, fixed “Ink out error”
Follow instruction here to reset ink level.
Credit to :
askindoprinter.blogspot.my
www.downloaddrivers.in
Mobile Ate The World
Very insightful presentation.
Watch Titanic Sinks in Real Time
Top 10 Country To Launch Startup
Surprisingly, my country being rate by Forbes as one of it.
Source from www.forbes.com
My Plant – Little Harmony (小和谐)
It used to be healthy like this…
And when it’s thirsty, it switch to standby mode…
When it’s super thirsty, it switch to hibernate mode… And… no one take action after long time hibernate, it tend to switch to shutdown mode 🙁
After intensive therapy treatment, it seems ok now, and I see hope 🙂