2nd Generation (GE 08-present)The New Fit... Generation specific talk and questions here.
Welcome to Fit Freak!
Welcome to Fit Freak,
You are currently viewing our forum as a guest, which gives you limited access to view most discussions and access our other features. By joining our community, at no cost, you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is free, fast and simple, so please join our community today!
WARNING: If you're an iPod Touch user, the new 3.0 firmware makes your device incompatible with the Honda factory iPod integration (BMW too, so I've heard). I learned this the hard way ... although I can play music, I cannot select Playlists, Artists, or Albums. I'm trying to revert to 2.1.1 but no luck yet
{edit: Removed reference to iPhone}
Last edited by cruzitude; 06-21-2009 at 12:12 AM.
Sponsored Links
Registered users do not see this ad. Click here to register for free!
I got my 3GS today, and of course it has OS 3.0. I went to the car after reading this, and although it initially took some time for the words to show up, everything works perfectly like before. Don't know what you did^
__________________
2009 Fit Sport AT - "SSMONSTER"
DONE
32% front tint - 13% rear tint
Red 'H' JDM emblems, Red Steering Wheel Insert
USDM door visors
Accord horn - low & high
K&N Air Filter
Red Key Ring Illumination
JMD Non LED Tails
Good to know ... Maybe the hardware difference with the 3G S allows it to work. I have a 2nd gen Touch and it doesn't work with 3.0 even after trying a complete restore on it. On a different forum I saw a guy having a problem with his BMW and iPhone 3G with the 3.0 OS. So, unless you have the new iPhone that came out today, maybe stay away from 3.0.
I upgraded my 3g to 3.0 and it works perfectly in the Fit, just like before.
Quote:
Originally Posted by cruzitude
Good to know ... Maybe the hardware difference with the 3G S allows it to work. I have a 2nd gen Touch and it doesn't work with 3.0 even after trying a complete restore on it. On a different forum I saw a guy having a problem with his BMW and iPhone 3G with the 3.0 OS. So, unless you have the new iPhone that came out today, maybe stay away from 3.0.
Good to know ... Maybe the hardware difference with the 3G S allows it to work. I have a 2nd gen Touch and it doesn't work with 3.0 even after trying a complete restore on it. On a different forum I saw a guy having a problem with his BMW and iPhone 3G with the 3.0 OS. So, unless you have the new iPhone that came out today, maybe stay away from 3.0.
You can easily restore the iPod to the older firmware. Learned all of this when I jailbroke my iPod.
Download the firmware you would like to use then in Itune shift+click the restore button and navigate to the firmware you downloaded let it restore and your now back in business with the old firmware.
Checked with the wifeys 3G with 3.0 and that works fine too.
__________________
2009 Fit Sport AT - "SSMONSTER"
DONE
32% front tint - 13% rear tint
Red 'H' JDM emblems, Red Steering Wheel Insert
USDM door visors
Accord horn - low & high
K&N Air Filter
Red Key Ring Illumination
JMD Non LED Tails
I got my 3GS today, and of course it has OS 3.0. I went to the car after reading this, and although it initially took some time for the words to show up, everything works perfectly like before. Don't know what you did^
+1 there are no problems with the firmware and the USB integration in the Fit. Works just like the previous OS
Mods, please lock this thread, as it's just spreading fear and misinformation. Dunno what OP is up to.
True, I don't have firsthand knowledge about iPhone performance with 3.0 -- my own experience with my 2G Touch is real and I was including what I had read from other users in another forum about their iPhone experience with 3.0. I'm glad for iPhone users who are not having a problem, but it most certainly is a real problem for the Touch (and that part ain't misiformation). I know iPods and iTunes quite well, and I can tell you firsthand that my Touch no longer functions with my Fit after installing 3.0, and doing a complete factory Restore twice now.
As far as downgrading firmware, I know all about the Shift-Restore trick, but all I get is error (20), so it seems I'm stuck at the moment.
As far as what I'm "up to", I was hoping to alert fellow Fit users to a problem that is really pissing me off and didn't want others to experience the same. I've edited my original post to remove all reference to the iPhone, sorry for the alarm to iPhone users.
Going up in firmware (to a newer version) is easy with the shift+restore. Downgrading firmware won't work as easily. Here is a link on how to do it, but it requires jailbreaking: [DOWNGRADE] Downgrade iPhone 3G 3.0 to 2.2.1 - Hackint0sh
__________________
2009 Blue Sensation Pearl Fit Sport AT w/ Navi
We don't cover incidentals, so keep your ass out the minibar!
I know iPods and iTunes quite well, and I can tell you firsthand that my Touch no longer functions with my Fit after installing 3.0, and doing a complete factory Restore twice now.
You need to watch the way you phrase things then. It appeared to me, and the casual observer that you were declaring no 3.0 device would work, which is not the case.
Have you resolved the problem?
If you open a support ticket with Apple, they'd be more than happy to assist you. Might even want to try your local Honda dealership.
If that fails, I'd be more than happy to help you.
You need to watch the way you phrase things then. It appeared to me, and the casual observer that you were declaring no 3.0 device would work, which is not the case.
If you look you'll see that I have since revised my initial post and applogized for any confusion caused to iPhone users. This seems limited to iPod Touch, and perhaps the non-Nav head unit since someone above reports no trouble there with a Touch.
On the Apple forum you'll see many others with this problem, mostly BMW but also Lexus, Mercedes, and Honda, as well as Denon, Bose, and other accessory manufacturers. So it definitely is a problem with 3.0, though perhaps not under every condition. Consider yourself lucky.
I have since resolved this by going back to 2.2.1 by putting the Touch in DFU mode and doing a Shift-Restore.