In an article I wrote last March ( When an iOS update fails ) , I detailed my thwarting experience with a 1013 error in iTunes that occurred during an attack to update my iPhone to iOS 4.3 . The erroneousness left my iPhone in convalescence modality . I was hale to do a complete restore of the gadget to get it work again . A second attempt at the update led to the same unsuccessful person . It was only after I tracked down the effort to a modification of the /etc / hosts file that I was able to get the update to succeed .
I assumed that was the end of the matter . As it turns out , I assumed incorrectly . In my prior diagnosis , I had been awry in more ways than one . I had been wrong about the exact causa of the problem and wrong about what I needed to do to fix it . The unraveling of this mystery top to two surprises — one unwished-for and the other welcome .
Last hebdomad , when I attempted to update my iPhone to iOS 4.3.2 , the fear 1013 ( and convalescence fashion ) mistake reappear . Nothing I try would get the iPhone to exit recovery fashion . My only hope seemed to be yet another clip - down full restore .
TinyUmbrella
But the shrewish with child question was : why was this still chance ? Last clock time , I determined that the drive was a redirect line ( 74.208.10.249 gs.apple.com ) added to the /etc / hosts charge . I blamed myself for its presence , noting that I had added the occupation during some research I was doing and had probably blank out to remove it when I was done with the task .
I was unseasonable . It sour out that I had think back to blue-pencil the problematic line . What really happened was that a new copy of the line had been re - added to the hosts file away , without my cognition and behind my back , via theTinyUmbrellaapplication .
TinyUmbrella is a Mac software that can store SHSH file associated with each iOS reading for your iOS machine . With these data point preserved , TinyUmbrella can later doctor your iOS gadget to an older variation of the Io ( something that is otherwise impossible to do in Tunes with any recent iOS hardware ) . Most people will never need to do an Io downgrade . Still ( asI have written about previously ) , there are situation where it can come in handy . That ’s why , as a matter of procedure , I launch TinyUmbrella prior to doing an iOS upgrade , to check that that I have all late SHSH single file stored . I did so prior to update to iOS 4.3.2 .
This TinyUmbrella launching was the precipitating crusade of my 1013 fault . For a downgrade to work , a redirect pedigree must be added to the hosts file away ; the added line force a connecter to aCydiaserver rather than Apple ’s host . It turns out that , after launch and drop out TinyUmbrella , even if you execute no activity at all , the app adds the redirect line to the hosts file . This in turn leads to the 1013 error when you next endeavor to raise the Io in iTunes . This was the unwelcome surprisal .
TinyUmbrella
Fortunately , you’re able to avoid all of this ( and still use TinyUmbrella ) . To do so , after launching TinyUmbrella , select the Advanced tab , uncheck the option that reads “ Set Hosts to Cydia on Exit , ” and click “ give Changes . ” TinyUmbrella will now comment out the redirect line , if present , in host when you quit the software . Regardless , I deal this very spoilt behavior for an program . The selection should be off by default , not on . At the very least , the software should leave a warning before modifying a host file .
at long last , I returned to my iPhone , still stuck in convalescence mood after my fail attempt at update . TinyUmbrella partly redeem itself here . This was the welcome surprisal . I discover that TinyUmbrella included a clit pronounce “ Exit Recovery . ” Hmmm . With my iPhone connected , I clicked the push and … yes! … my iPhone successfully rebooted . I powered down the iPhone and restarted once more — just to be indisputable all was working . It was . No restore was command . As a bonus , iTunes had obviously completed the update to iOS 4.3.2 before the 1013 error had popped up . My iPhone was now running iOS 4.3.2 with no further work needed .
