While in the process of preparing the update (After the backup done by the upgrade program) I suddenly notice that I have a picture of a USB connector with an Arrow pointing toword a circle designated as iTune. Can't get rid of it. Tried to reset the iPOD ( Long press on the power button) . Nothing.
By the way. I didn't have any jailbreak on it. No Cidia. Nothing. Just a new iPAD one month old with very few free programs, and some books.

Originally Posted by peled

While in the process of preparing the update (After the backup done by the upgrade program) I suddenly notice that I have a picture of a USB connector with an Arrow pointing toword a circle designated as iTune. Can't get rid of it. Tried to reset the iPOD ( Long press on the power button) . Nothing.
By the way. I didn't have any jailbreak on it. No Cidia. Nothing. Just a new iPAD one month old with very few free programs, and some books.

Hopefully you backed up...you are in DFU mode and the only way out is to restore.

That's part of the update process. Did you disconnect?

I had the same thing happen. my base PC said that the transfer did not happen and my i pad locked for anextended time. I don't think that this is part of any good process.

how do I get back to a usable i pad?

Before it did the download it synced. You should be able to plug it into iTunes and do a restore.

I too had problems with installing 4.2. It performed a mysterious and very prolonged backup after the install and then hung up in the verification, crashing iTunes. After various unsuccessful attempts to fix things with the help of Apple, I ended up doing a full restore and it turned out that the backup was basically useless. I've had to resync the iPod completely from iTunes. The caution for this situation is that I guess I'll lose whatever is not visible in iTunes without the iPad (such as word processing documents). So be careful out there.

Originally Posted by rwsimon

I too had problems with installing 4.2. It performed a mysterious and very prolonged backup after the install and then hung up in the verification, crashing iTunes. After various unsuccessful attempts to fix things with the help of Apple, I ended up doing a full restore and it turned out that the backup was basically useless. I've had to resync the iPod completely from iTunes. The caution for this situation is that I guess I'll lose whatever is not visible in iTunes without the iPad (such as word processing documents). So be careful out there.

Well, that sucks. Mine went smooth as can be. Everything was explained as the process was occurring. I'm assuming you used a PC. Did Apple tell you how you could of avoided it or did they just say stuff happens?

Originally Posted by rwsimon

I too had problems with installing 4.2. It performed a mysterious and very prolonged backup after the install and then hung up in the verification, crashing iTunes. After various unsuccessful attempts to fix things with the help of Apple, I ended up doing a full restore and it turned out that the backup was basically useless. I've had to resync the iPod completely from iTunes. The caution for this situation is that I guess I'll lose whatever is not visible in iTunes without the iPad (such as word processing documents). So be careful out there.

Same thing happened to me, It seems like the reason was that iTunes filled my entire c: with backup data and upon running out of room corrupted the backup file....which in turn actually made it so it would crash iTunes in both Mac and Windows.

I am now backing up the backup so I can restore some hard drive space and try again. How annoying.

No need to rest or to get out of it, just download tinyumbrella and there is a button you click to get out of dfu.

Well mine wasn't stuck in DFU I had to put it into DFU in order to restore...Mine was stuck in the finalize stage with a progress bar under the apple. And hard resetting caused it to go back to that screen and plugging it in caused iTunes to crash. I got it up and running but when I tried to use my back up it said it couldn't because I was out of disk space...now fixing that problem.