GTV FileSystem - Revision history

Pi3832: /* File System Layout */

2012-06-28T20:52:31Z

File System Layout

← Older revision		Revision as of 20:52, 28 June 2012
Line 24:		Line 24:
	\| 0x00200000-0x00a00000		\| 0x00200000-0x00a00000
	\| "cefdk"		\| "cefdk"
	\| The boot loader. Presumably compiled under Intel's "Consumer Electronics Firmware Development Kit"<br/>It's data—wouldn't say it is encrypted, but no strings visible. It may contain a console.		\| The boot loader. Presumably compiled under Intel's "Consumer Electronics Firmware Development Kit" ([http://software.intel.com/en-us/articles/intel-tools-for-intel-atom-processors/ Got $2,000?])<br/>It's data—wouldn't say it is encrypted, but no strings visible. It may contain a console.
	\|		\|
	\|-		\|-

Pi3832: /* File System Layout */

2012-06-28T20:49:59Z

File System Layout

← Older revision		Revision as of 20:49, 28 June 2012
Line 24:		Line 24:
	\| 0x00200000-0x00a00000		\| 0x00200000-0x00a00000
	\| "cefdk"		\| "cefdk"
	\| ~~Boot~~ loader. It's ~~Data - Wouldn~~'t say it is encrypted, but no strings visible. It may contain a console		\| The boot loader. Presumably compiled under Intel's "Consumer Electronics Firmware Development Kit"<br/>It's data—wouldn't say it is encrypted, but no strings visible. It may contain a console.
	\|		\|
	\|-		\|-
	\| 0x00a00000-0x00c00000		\| 0x00a00000-0x00c00000
	\| "redboot"		\| "redboot"
	\| All FF's		\| All FF's <br /> [http://www.redhat.com/services/custom/embedded/redboot/ "Red Hat Embedded Debug and Bootstrap"]
	\|		\|
	\|-		\|-
Line 85:		Line 85:
	* MTD Parition listing came from [http://googletv.pastebin.com/233dZqZx Revue Boot Output]. ([http://my.safaribooksonline.com/book/operating-systems-and-server-administration/embedded-linux/0136130550/mtd-subsystem/ch10lev1sec3 What's an MTD partition?])<br/>		* MTD Parition listing came from [http://googletv.pastebin.com/233dZqZx Revue Boot Output]. ([http://my.safaribooksonline.com/book/operating-systems-and-server-administration/embedded-linux/0136130550/mtd-subsystem/ch10lev1sec3 What's an MTD partition?])<br/>
	* Partition mount points came from /init.rc & init.<board>.rc		* Partition mount points came from /init.rc & init.<board>.rc

	== Kernel ==		== Kernel ==
	Information on the Kernel can be found at [[Logitech Revue Kernel]]. Important to note that the Revue Kernel has been modified from what is available in the Google Open Sourced GTV Source.		Information on the Kernel can be found at [[Logitech Revue Kernel]]. Important to note that the Revue Kernel has been modified from what is available in the Google Open Sourced GTV Source.

Jbjonesjr at 22:26, 22 January 2011

2011-01-22T22:26:51Z

← Older revision		Revision as of 22:26, 22 January 2011
Line 64:		Line 64:
	\| 0x07200000-0x1f200000		\| 0x07200000-0x1f200000
	\| "system"		\| "system"
	\| ~~/system partition.~~ Holds most of the crucial system files. It's YAFFS		\| Holds most of the crucial system files (including the Kernel). It's YAFFS
	\|		\| /system
	\|-		\|-
	\| 0x1f200000-0x3fa00000		\| 0x1f200000-0x3fa00000
Line 85:		Line 85:
	* MTD Parition listing came from [http://googletv.pastebin.com/233dZqZx Revue Boot Output]. ([http://my.safaribooksonline.com/book/operating-systems-and-server-administration/embedded-linux/0136130550/mtd-subsystem/ch10lev1sec3 What's an MTD partition?])<br/>		* MTD Parition listing came from [http://googletv.pastebin.com/233dZqZx Revue Boot Output]. ([http://my.safaribooksonline.com/book/operating-systems-and-server-administration/embedded-linux/0136130550/mtd-subsystem/ch10lev1sec3 What's an MTD partition?])<br/>
	* Partition mount points came from /init.rc & init.<board>.rc		* Partition mount points came from /init.rc & init.<board>.rc
			== Kernel ==
			Information on the Kernel can be found at [[Logitech Revue Kernel]]. Important to note that the Revue Kernel has been modified from what is available in the Google Open Sourced GTV Source.
	== Updates ==		== Updates ==
	Updates to the Google TV, unlike the incremental updates that most Android phones receive, come as a complete file system meant to replace the previous. It is assumed that since Google TV devices are meant to be connected to high speed internet connections, downloading a full File System is more palatable than on a limited-bandwidth mobile device.		Updates to the Google TV, unlike the incremental updates that most Android phones receive, come as a complete file system meant to replace the previous. It is assumed that since Google TV devices are meant to be connected to high speed internet connections, downloading a full File System is more palatable than on a limited-bandwidth mobile device.

KernelJayOmega: Revised the updates section

2011-01-16T23:14:47Z

Revised the updates section

← Older revision		Revision as of 23:14, 16 January 2011
Line 88:		Line 88:
	Updates to the Google TV, unlike the incremental updates that most Android phones receive, come as a complete file system meant to replace the previous. It is assumed that since Google TV devices are meant to be connected to high speed internet connections, downloading a full File System is more palatable than on a limited-bandwidth mobile device.		Updates to the Google TV, unlike the incremental updates that most Android phones receive, come as a complete file system meant to replace the previous. It is assumed that since Google TV devices are meant to be connected to high speed internet connections, downloading a full File System is more palatable than on a limited-bandwidth mobile device.

	~~Updates are retrieved without user intervention~~ from the ~~Google Servers~~. ~~You~~ can use the ~~device version number~~ to check ~~your current file system implementation~~ (See [[GoogleTV - Version Numbers]] for more information). Updates are distributed as signed zip files including ~~the base file system image~~, ~~the system files~~, ~~as well as~~ updated ~~certificates~~ and ~~any public keys necessary~~. ~~The current update packages are:~~		The Google TV software uses the [[com.google.android.systemupdater]] activity to periodically query Google's servers looking for available updates based on the devices serial number. Under normal circumstances, during initial setup of a device (i.e. configuring from a wiped or factory default state), the [[com.google.android.systemupdater]] activity will prevent completion of first time setup until any available updates have been downloaded and applied. This can be bypassed by removing the files /system/app/SystemUpdater.{apk,odex} from the file system. If a previously configured device finds an available update at boot, it will display a prompt asking the user if they wish to install or defer the update. If the system is not in use at this time, the update will be applied without user interaction. Based on network traffic it appears that the Logitech Revue is configured to check for updates in the early AM hours. The currently installed build number can be checked through '''Applications > Settings > About'''. (See [[GoogleTV - Version Numbers]] for more information). Updates are distributed as signed zip files including [[boot.img]], [[kernel.img]], [[ota.prop]], updated content, and meta-information (signing data, install scripts, etc).

	~~[http://android~~.~~clients.google.com/packages/ota/logitech_ka/c9914396d183.mp-~~signed~~-ota_update-b42449~~.~~zip Logitech Revue b42449]~~		Until a new recovery image with is prepared for Google TV devices, it is unlikely that anyone will be able to prepare homebrew updates since it is computationally infeasible to produce signatures matching Google's private key. This same logic applies when considering modification of a properly signed update.

	List of all updates for:		List of all updates for:

Resno at 19:15, 13 January 2011

2011-01-13T19:15:35Z

← Older revision		Revision as of 19:15, 13 January 2011
Line 118:		Line 118:
	== Files of interest within the File System ==		== Files of interest within the File System ==

	~~== So, why can't I just edit a File System and use it to update my review? ==~~		[[Category:Contribute]]

Jbjonesjr at 04:37, 10 January 2011

2011-01-10T04:37:56Z

← Older revision		Revision as of 04:37, 10 January 2011
Line 96:		Line 96:

	The Updates each include:		The Updates each include:
	boot.img: A file system including the root file system for the device.<~~br/>~~		* boot.img: A file system including the root file system for the device.<
	The "system" folder: This is the guts of the Google TV and it's applications. These files are copied into the system folder on update.~~<br/>~~		* The "system" folder: This is the guts of the Google TV and it's applications. These files are copied into the system folder on update.
	~~The~~ META-INF directory ~~which includes~~ the manifest and other certificates shipped with the device for authentication.		* META-INF directory: Includes the manifest and other certificates shipped with the device for authentication.

	== File System Obfusication ==		== File System Obfusication ==

Jbjonesjr at 04:37, 10 January 2011

2011-01-10T04:37:11Z

← Older revision		Revision as of 04:37, 10 January 2011
Line 96:		Line 96:

	The Updates each include:		The Updates each include:
	boot.img: A file system including the root file system for the device.		boot.img: A file system including the root file system for the device.<br/>
	The "system" folder: This is the guts of the Google TV and it's applications. These files are copied into the system folder on update.		The "system" folder: This is the guts of the Google TV and it's applications. These files are copied into the system folder on update.<br/>
	The META-INF directory which includes the manifest and other certificates shipped with the device for authentication.		The META-INF directory which includes the manifest and other certificates shipped with the device for authentication.

Jbjonesjr at 04:36, 10 January 2011

2011-01-10T04:36:26Z

← Older revision		Revision as of 04:36, 10 January 2011
Line 2:		Line 2:

	== Still Needs ==		== Still Needs ==
	* Finishing merging update information from the [[ ~~Logitech Technical~~]] page including proper truncation and hex editting steps. also mentions odex.		* Finishing merging update information from the [[ Logitech_Revue_Technical]] page including proper truncation and hex editting steps. also mentions odex.
	* Description of how the Update Signing process works and how it works (And why we can't just copy an edited zip to a usb key and root the box). This is a common noob question.		* Description of how the Update Signing process works and how it works (And why we can't just copy an edited zip to a usb key and root the box). This is a common noob question.
	* Description of the seperation between the boot loader steps, recovery kernel, and the actual "device" file system/kernel. This can be key for explaining how the UART1 console was used and when it was used. There is often discussion on "I was looking for output during X boot stage" that this data could provide a definition for.		* Description of the seperation between the boot loader steps, recovery kernel, and the actual "device" file system/kernel. This can be key for explaining how the UART1 console was used and when it was used. There is often discussion on "I was looking for output during X boot stage" that this data could provide a definition for.

Jbjonesjr at 04:34, 10 January 2011

2011-01-10T04:34:36Z

← Older revision		Revision as of 04:34, 10 January 2011
Line 24:		Line 24:
	\| 0x00200000-0x00a00000		\| 0x00200000-0x00a00000
	\| "cefdk"		\| "cefdk"
	\| Boot loader? It's Data - Wouldn't say ~~crypted~~, but no strings.		\| Boot loader. It's Data - Wouldn't say it is encrypted, but no strings visible. It may contain a console
	\|		\|
	\|-		\|-
Line 39:		Line 39:
	\| 0x01000000-0x01800000		\| 0x01000000-0x01800000
	\| "splash"		\| "splash"
	\| ~~Says its~~ a BMP~~, doesnt totally look like one (on quick look)~~		\| Splash image, [ http://img413.imageshack.us/img413/3144/splashc.png visible here] . It reports itself as a BMP even though it is a PNG
	\|		\|
	\|-		\|-
	\| 0x01800000-0x01900000		\| 0x01800000-0x01900000
	\| "fts"		\| "fts"
	\| ~~Repeats this data, mostly~~: "F*TS..e.L.......bootloader.command=boot-recovery.bootloader.recovery=recovery.--wipe_data."		\| Flash Transaction Key/Value Storage. (Contents seem to be just seems to be just: "F*TS..e.L.......bootloader.command=boot-recovery.bootloader.recovery=recovery.--wipe_data.")
	\|		\|
	\|-		\|-

Jbjonesjr at 04:26, 10 January 2011

2011-01-10T04:26:08Z

← Older revision		Revision as of 04:26, 10 January 2011
Line 1:		Line 1:
	The Google TV File System is similar to most other Android Operating Systems.		The Google TV File System is similar to most other Android Operating Systems.

			== Still Needs ==
			* Finishing merging update information from the [[ Logitech Technical]] page including proper truncation and hex editting steps. also mentions odex.
			* Description of how the Update Signing process works and how it works (And why we can't just copy an edited zip to a usb key and root the box). This is a common noob question.
			* Description of the seperation between the boot loader steps, recovery kernel, and the actual "device" file system/kernel. This can be key for explaining how the UART1 console was used and when it was used. There is often discussion on "I was looking for output during X boot stage" that this data could provide a definition for.

	== File System Layout ==		== File System Layout ==