Nano4G firmware upgrade process - Revision history

User890104 at 20:42, 8 June 2025

2025-06-08T20:42:21Z

← Older revision		Revision as of 20:42, 8 June 2025
Line 51:		Line 51:

	==Automated image uploading==		==Automated image uploading==
	There's an app that implements this protocol. Its source code is available at [~~http~~://~~svn~~.freemyipod.~~org~~/tools/ipodscsi~~/ our SVN~~]. Use MinGW to compile it (or get the binary [http://files.freemyipod.org/misc/ipodscsi.exe here])~~, only Windows version available at the moment~~. It's written with [[Classic 1G]], [[Classic 2G]], and [[Classic 3G]] in mind, ~~but~~ also works with [[Nano 3G]] ~~and~~ [[Nano 4G]]~~. More details to come soon on a separate page. We'll be happy if someone could test if it works on~~ [[Nano 5G]] ~~and~~ [[Nano 6G]] and ~~post the results on the~~ [[~~Talk:Nano4G_firmware_upgrade_process\|Discussion page~~]].		There's an app that implements this protocol. Its source code is available at out GitHub for [https://github.com/freemyipod/freemyipod/tree/master/tools/ipodscsi_linux Linux] or [https://github.com/freemyipod/freemyipod/tree/master/tools/ipodscsi Windows]. The Linux version can be compiled using gcc (get the build-essential package on Ubuntu). Use MinGW to compile the Windows version (or get the binary [http://files.freemyipod.org/misc/ipodscsi.exe here]). It's written with [[Classic 1G]], [[Classic 2G]], and [[Classic 3G]] in mind, and it also works with [[Nano 3G]], [[Nano 4G]], [[Nano 5G]], [[Nano 6G]] and [[Nano 7G]].

User890104 at 21:57, 8 February 2015

2015-02-08T21:57:37Z

← Older revision		Revision as of 21:57, 8 February 2015
Line 51:		Line 51:

	==Automated image uploading==		==Automated image uploading==
	There's an app that implements this protocol. Its source code is available at [http://svn.freemyipod.org/tools/ipodscsi/ our SVN]. Use MinGW to compile it (or get the binary [http://files.freemyipod.org/~~tmp~~/ipodscsi.exe here]), only Windows version available at the moment. It's written with [[Classic 1G]], [[Classic 2G]], and [[Classic 3G]] in mind, but also works with [[Nano 3G]] and [[Nano 4G]]. More details to come soon on a separate page. We'll be happy if someone could test if it works on [[Nano 5G]] and [[Nano 6G]] and post the results on the [[Talk:Nano4G_firmware_upgrade_process\|Discussion page]].		There's an app that implements this protocol. Its source code is available at [http://svn.freemyipod.org/tools/ipodscsi/ our SVN]. Use MinGW to compile it (or get the binary [http://files.freemyipod.org/misc/ipodscsi.exe here]), only Windows version available at the moment. It's written with [[Classic 1G]], [[Classic 2G]], and [[Classic 3G]] in mind, but also works with [[Nano 3G]] and [[Nano 4G]]. More details to come soon on a separate page. We'll be happy if someone could test if it works on [[Nano 5G]] and [[Nano 6G]] and post the results on the [[Talk:Nano4G_firmware_upgrade_process\|Discussion page]].

User890104 at 03:15, 27 November 2011

2011-11-27T03:15:14Z

@@ Line 1: / Line 1: @@
   the whole firmware update is done through a custom 0xc6 scsi command
@@ Line 30: / Line 31: @@
   -- [[User:TheSeven|TheSeven]] 22:21, 30 November 2009 (UTC)
 To send these commands on linux you need the scsirastools (http://scsirastools.sourceforge.net/). On Debian you have to build it youself using configure, make, make install.
 Once you built it run as root: sgdiag -I
 You will get a prompt. First type c to send a custom command, then the number of the device (the list is just above). The CDB length is 10, then the bytes are c6 ... (eg c6 97 00 01 00 00 00 00 00 00 for the first one). Response data length is 4 byte for the first command, 0 for the ones with no data stage or for uploading firmware or log sending, 4096 for log reading). The Output data length is the size of data sent to the ipod (excluding the command). That's it. If the device is an ipod you should get a response, if it isn't you will get an error message.

Cmwslw: moved Nano4G Firmware Upgrade Process to Nano4G firmware upgrade process

2010-07-13T16:31:41Z

moved Nano4G Firmware Upgrade Process to Nano4G firmware upgrade process

← Older revision	Revision as of 16:31, 13 July 2010
(No difference)

Cmwslw: moved 4G Firmware Upgrade Process to Nano4G Firmware Upgrade Process

2010-07-13T16:31:17Z

moved 4G Firmware Upgrade Process to Nano4G Firmware Upgrade Process

← Older revision	Revision as of 16:31, 13 July 2010
(No difference)

Polobricolo: Explained how to send this custom command to a nano 4g with linux

2009-12-10T20:50:21Z

Explained how to send this custom command to a nano 4g with linux

← Older revision		Revision as of 20:50, 10 December 2009
Line 29:		Line 29:

	-- [[User:TheSeven\|TheSeven]] 22:21, 30 November 2009 (UTC)		-- [[User:TheSeven\|TheSeven]] 22:21, 30 November 2009 (UTC)

			To send these commands on linux you need the scsirastools (http://scsirastools.sourceforge.net/). On Debian you have to build it youself using configure, make, make install.

			Once you built it run as root: sgdiag -I
			You will get a prompt. First type c to send a custom command, then the number of the device (the list is just above). The CDB length is 10, then the bytes are c6 ... (eg c6 97 00 01 00 00 00 00 00 00 for the first one). Response data length is 4 byte for the first command, 0 for the ones with no data stage or for uploading firmware or log sending, 4096 for log reading). The Output data length is the size of data sent to the ipod (excluding the command). That's it. If the device is an ipod you should get a response, if it isn't you will get an error message.

TheSeven at 22:21, 30 November 2009

2009-11-30T22:21:56Z

← Older revision		Revision as of 22:21, 30 November 2009
Line 27:		Line 27:

	that's the whole deal.		that's the whole deal.

			-- [[User:TheSeven\|TheSeven]] 22:21, 30 November 2009 (UTC)

TheSeven: Created page with ' the whole firmware update is done through a custom 0xc6 scsi command first, the update is initiated by a c6 96 00 00 00 00 00 00 00 00 packet, that will get a 4-byte response...'

2009-11-30T22:21:29Z

Created page with ' the whole firmware update is done through a custom 0xc6 scsi command first, the update is initiated by a c6 96 00 00 00 00 00 00 00 00 packet, that will get a 4-byte response...'

New page

the whole firmware update is done through a custom 0xc6 scsi command

first, the update is initiated by a c6 96 00 00 00 00 00 00 00 00 packet, that will get a 4-byte response (meaning unknown)

maybe the count of update log entries?

then the last update log page (4KB) is read using a c6 97 00 01 00 00 00 00 00 00 packet

then a new log page (4KB) is written using a c6 98 00 01 00 00 00 00 00 00 packet

then there is a c6 94 00 02 80 00 00 00 00 00 00 00 00 00 00 00 packet, no idea what it's good for, no data stage

the next stage is uploading the "N58s.bootloader.release.rb3" file, using a c6 90 <type> <size> 00 00 00 00 00 00 00 00 00 packet

<type> is 00 for the MSE, and 01 for the RB3 file, size is the big endian 32bit file size

the transfer itself is done using c6 91 00 10 00 00 00 00 00 00 packets, each (besides the last one, which is trimmed to the
number of bytes left to be transferred) followed by 5 data stages, being 16384, 3584, 16384, 16384 and 12800 bytes in size

I can't think of any reason for this weirds splitting, maybe it isn't even neccessary and just an itunes weirdness

then the transfer is closed using a c6 92 00 00 00 00 00 00 00 00 00 00 00 00 00 00 packet

the next step is uploadinf "Firmware.MSE" the same way

finally a c6 31 00 00 00 00 00 00 00 00 00 00 00 00 00 00 is sent (no data stage), and another log entry is written

that's the whole deal.