Troubleshooting TSF software/builds

1. Device not detected by USB

After flashing device was not detected by USB, but battery charging was showing.

Tried to enabled developer options and USB debugging in phone settings, but no success.

Finally, got it working by doing factory reset from phone settings.


2. Error Flashing Phone app 

adb push ~/work/tsf/jamesonwilliams/out/target/product/mako/system/app/Phone.apk /system/app/


Read only file system error:
adb root
adb remount

Flash factory image of google nexus 4.2.2

Flash factory image of google nexus 4.2.2

adb reboot bootloader
fastboot oem unlock

Unzip  Google-Nexus-4.2.2.zip
(Downland from http://weavebytes.com/downloads/tsf/Google-Nexus-4.2.2.zip)

cd /home/nsk/work/tsf/Original-Image-Nexus-4/Google-Nexus-4.2.2/occam-jdq39

Execute the flash-all script. 

./flash-all.sh

Flashing the complete package

Flashing the complete package
 
cd /home/nsk/work/tsf/jamesonwilliams

adb reboot bootloader

fastboot -w update out/target/product/mako/full_mako-img-eng.nsk.zip

Binaries Generated By AOSP - Android Source Build

Binaries Generated By AOSP - Android Source Build

1. boot.img
boot.img contains the kernel and ramdisk, critical files necessary to load the device before the filesystem can be mounted. You have to generate the boot.img yourself using mkbootimg, a tool provided by AOSP.

2.kernel
Binary for linux kernel.

3. ramdisk.img
ramdisk.img is a small partition image that is mounted read-only by the kernel at boot time.
It only contains /init and a few config files.
It is used to start init which will mount the rest of the system images properly and run the init procedure.

A Ramdisk is a standard Linux feature.


4. ramdisk-recovery.img
Recovery image for ramdisk.

5. recovery.img
It is the Android recovery image.

A bootable program on an Android flash memory partition that is used to perform a factory reset or restore the original OS version. In order to install a different OS version (a different ROM), the stock recovery image must be replaced with a custom version such as ClockworkMod Recovery. After rooting the Android, utilities such as ROM Manager install the custom recovery, which is then used to install the custom ROM.

6. userdata.img
userdata.img is a partition image that can be mounted as /data and thus contains all application-specific and user-specific data.   

7. system.img
system.img is a partition image that will be mounted as / and thus contains all system binaries

8. full_mako-img-eng.nsk.zip
A full update is one where the entire final state of the device (system, boot, and recovery partitions) is contained in the package. As long as the device is capable of receiving the package and booting the recovery system, the package can install the desired build regardless of the current state of the device.