Hey guys, I just got a iPhone 4 to replace my 3gs. However, I cannot upgrade the phone to 4.3.4! It says "device is not eligible for requested build". Lol what the hell? Any help is appreciated. Thanks!
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
New iPhone4 cannot update to 4.3.4
- Thread starter BenXiaoHai
- Start date
- Sort by reaction score
Have you ever jail broken? If so this may be the problem. Apple tell you how to restore the correct lines of code on their website that pops up when you hit the more info button on your dialog box
new iPhone
if your on Verizon I believe you can only go up to 4.2.9
ATT is 4.3
I don't believe Verizon with catch up till 5.0 is out
if your on Verizon I believe you can only go up to 4.2.9
ATT is 4.3
I don't believe Verizon with catch up till 5.0 is out
I have a non jailbroken verizon iphone 4 and I am also getting "not eligible for the requested build." This is the only thread I could find in which someone says verizon phones are not eligible. I doubt that, by the way-- why would apple put out a bug fix upgrade that is not usable by millions? Any suggestions?
Verizon's iPhone bug fix is built at "4.2.10". It addresses the same SSL exploit. If your build is 4.2.10, then you're fine.
Last night I spent an hour and a half on the line with Apple Tech support. I had to buy Applecare for $70 (which I would have probably done anyway). I was bounced between iphone and mac support (their scripts had not been adjusted for Lion terminal, apparently). They had me reload itunes-- no dice. Then they had me set up a test admin account and try to upgrade. No dice. We agreed to stop there and see if anything develops; I will call the service tech later this week,
Download this: http://appldnld.apple.com/iPhone4/041-1959.20110721.jvP29/iPhone3,3_4.2.10_8E600_Restore.ipsw
Shift+click update and redirect to that file.
Shift+click update and redirect to that file.
Thanks-- I tried that. Didn't work, but I appreciate your response. It was a better try than anything Apple has suggested so far.