[Amazon Fire Phone] Bingo Bronson:
PART 2 of 2 - SYSTEM OPTIMIZATION, TWEAKS, RECOVERY, FACTORY IMAGES, TIPS

Picture for stock lock screen:

./sdcard0/lock/user-photo/user_photo.jpg

./sdcard0/lock/user-photo/user_photo_thumbnail.jpg

Replaced the original JPGs with a black 1x1 px JPG.

Change / Replace Lock Screen:

I used "Next Lock Screen" (NLS) as a replacement, not my favorite but it's a suitable example.

After installation, make sure to give notification access to the new lock screen. In the NLS settings, choose 'compact' or 'hide' as status bar mode. Doing this will prevent problems showing the quick access panel from NLS.

[IMG="Notification Access"]http://i.imgur.com/9O17sCV.png[/IMG] [IMG="Status Bar Mode"]http://i.imgur.com/CksL9be.png[/IMG]

Stock Ringtones, Alarms, Notifications, UI Sounds, Boot Animation:

./system/media/audio

I deleted most of the files in the subfolders, since I don't need / like them.

./system/media/fremedia

Contains 4 videos (01s.mp4, 02s.mp4, 03s.mp4, 04s.mp4). 20 MB of useless data = deleted.

They are used for the Fire "tutorial" that you can choose to watch when you first boot up a "factory fresh" phone.

./system/media

boot.wav & bootanimation.zip = default boot logo & audio, deleted, who cares.

Textures (for the atrocious "dynamic perspective"):

./system/euclid/vbls/home_icons/...

and folders like "home_icons-de", "home_icons-es", etc. depending on your OS version

The textures folder in the above mentioned folder(s) can be removed if you don't use "dynamic perspective".

Text to Speech:

./system/tts/ivona

One folder for each language, e. g. "deu.deu.marlene_1418201400000", "eng.usa.nina_1418201400000".

The two folders above have over 340 MB(!) of data. Folders can be deleted if you don't use TTS.

./system/tts/lang_pico

The bin files inside this folder can also be deleted if you don't need TTS.

Factory Data Reset Whitelist - "protects" the following folders & files:

/data/app

/data/dalvik-cache

/data/resource-cache

/data/app-res

/data/app-lib

/data/system/packages.list

/data/system/packages.xml

/data/media/0/Android/data/com.amazon.kindle/files/dictionaries

/data/securedStorageLocation/com.amazon.providers.contentsupport/tts/ivona

/data/system/uiderrors.txt

/data/system/dropbox

Just to show you which parts exactly get spared when FR is executed.

Delete Fonts:

./system/sqfs/container.sqfs

Stored in a compressed sqfs container (read only), because including 160 Fonts was a good idea. -.-

The fonts folder weighs over 180 MB, compressed into a container it's still 109 MB.

Replacing the XMLs ➜ clicked on settings ➜ FC, third party apps still work (e.g. root explorer) ➜

Replacing the container.sqfs ➜ clicked on settings ➜ everything ok ➜ restart phone ➜ everything ok ➜ power off phone ➜ boot up phone ➜ stuck in boot ➜ black screen ➜

Copied the fonts from the container to a temp directory ➜ deleted the container.sqfs file ➜ created a real folder namend "fonts" in ./system ➜ moved the fonts back into the real fonts folder ➜ survives restart & complete power off

I deleted the CN and JP fonts, font configuration list:

DELETE:

STKai

STYuanMedium

TBGothic_213

TBMincho_213

TsukuMinPr5

MYingHeiSMedium

STBShusong

STYuanMedium

MTChineseSurrogates

MHeiM-Big5HKSCS_E

Code2000

DroidNaskh

DroidSansEthiopic

DroidSansHebrew

NotoSansThai

NotoSansThaiUI

DroidSansArmenian

DroidSansGeorgian

NotoSansDevanagari

NotoSansTamil

NotoSansMalayalam

NotoSansBengali

NotoSansTelugu

NotoSansKannada

NotoSansKhmer

NotoSansLao

NanumGothic

Padauk-book

NotoSansSymbols

AndroidEmoji

NotoColorEmoji

MTLmr3m

KEEP:

Roboto

DroidSerif

DroidSans

DroidSansFallback

Helvetica

LucidaSans

Baskerville

Palatino

Verdana

Georgia

Amazon DCP Menu / OTA Dashboard:

I will just link the post from rbeavers since it explains it perfectly.

[IMG="DCP Menu"]http://i.imgur.com/69PQitw.png[/IMG] [IMG="OTA updates progress"]http://i.imgur.com/3vjmAeK.png[/IMG]

Final Steps:

Used SD Maid Pro to clean up unused Libs, obsolete & orphaned files (e. g. Epson & Canon Printer Libs, etc.) won another ~ 50 MB of system space.

I made an exception for:

./data/data/vitals.db

./data/data/vitals.db-wal

You can delete them when SD Maid offers to, but they will be generated again by the system.

Using Greenify depends on the selection of your apps, some people will profit more from using it than others.

Stock Apps (pre-installed) / Updated Apps:

3 archives. One with all system apps, the other with all priv-apps and the third with all updated apps as of 2015-06-21.

Download - System Apps Archive

Download - Priv-Apps Archive

Download - Updated Apps

Recovery / Sideload Factory Images:

If your OS is messed up "beyond repair", try re-installing it.

All images are multi language (English, Spanish, French, Italian, German, regarding the UI & keyboard, some TTS languages need to be downloaded if the user wants to have proper support), so you could use the US version for an EU user / phone.

You might run into problems using certain WiFi channels (e. g. CH 13) because of the WiFi country codes. Advanced users know how to handle / fix that, ofc. The US image is the so called "GSM unlocked" version, suitable for most users.

1.a Download the *.bin file (FireOS 4.6.1):

——————————————————

US - Amazon Server DDL

US - Mega.nz Mirror

——————————————————

UK - Amazon Server DDL

UK - Mega.nz Mirror

——————————————————

GER - Amazon Server DDL

GER - Mega.nz Mirror

1.b or download the *.bin file (FireOS 4.6.3):

——————————————————

US - Amazon Server DDL

——————————————————

UK - Amazon Server DDL

——————————————————

GER - Amazon Server DDL

2. Connect device to PC & boot in recovery: PWR + VOL. UP (hold both buttons until recovery screen appears)

From the list, choose "Apply update from ADB"

3. adb sideload 'name_of_your_bin_file'

I recommend renaming the the downloaded file to "update.bin" so you can just type in cmd: adb sideload update.bin

4. If you have trouble getting your device recognised after entering recovery / ADB sideloading mode:

If you boot up your phone in recovery mode / ADB mode, you will need additional ADB device drivers for your Windows system.

The regular (Amazon / Kindle) USB driver that is used when you connect your phone to the PC won't work, it's simply not the same method.

That's why your phone "disappears" as soon as you (re)boot into recovery / ADB sideload mode.

Open your "device manager" (assuming, you're using Windows as your main OS) and check for your device with missing drivers.

Try this tool (& driver) http://xdaforums.com/showthread.php?t=2588979

You can even use (old) "Google USB drivers", I successfully tested google drivers from 2010 on Win 7 x64 with this phone in ADB mode.

If everything worked as planned, it should look like this: next to your device name, it will say "sideload"