Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

spinstorm

macrumors 68000
Original poster
Sep 14, 2007
1,643
195
I should be crying but because it was an "accident" I am just hoping someone can help me!

I had 1.0.2 and it was unlocked using iunlock!

I decided to run IPSF and see if it would fix my unlock and I usd wininstaller for that.

WinInstaller crashed with a communication error and then I got the dreaded yellow triangle.

So I thought id update to 1.1.1 and then downgrade to 1.0.2 and unlock it using IPSF that way.

SO I tried restoring to 1.1.1 and I got error 11, so I tried again and I got error 1604.

SO I tried restoring to 1.0.2 after downloading it and I keep getting the same error!

Stuck on the yellow triangle!

Please someone tell me how to fix this - I am using Windows XP. Thanks.
 
I have had it connected for almost ten minutes and it says:

CannectRecoveryCallback: Bad Stage: 1
Stage 1: 1: Recovering
Stage 1: 2: Attempting to boot iphone in normal mode...

It has gone no further! So I am guessing Apptapp will not help me now

Any other suggestions?
 
I connected my iPhone to my windows PC and restored it to 1.0.2

I should probably leave it alone now.

But I am willing to upgrade it to 1.1.1 and then downgrade it again as I do have an IPSF license so I will try it - lets hope I dont break it for real this time!
 
Thanks for the reply.

I used iPhoneSimFree though and I now have an unlock running on modem firmware 04.01.13_G on 1.0.2.

All I need is a nice easy way to activate and jailbreak 1.1.1 and I can upgrade now and keep my unlock!
 
I should be crying but because it was an "accident" I am just hoping someone can help me!

I had 1.0.2 and it was unlocked using iunlock!

I decided to run IPSF and see if it would fix my unlock and I usd wininstaller for that.

WinInstaller crashed with a communication error and then I got the dreaded yellow triangle.

So I thought id update to 1.1.1 and then downgrade to 1.0.2 and unlock it using IPSF that way.

SO I tried restoring to 1.1.1 and I got error 11, so I tried again and I got error 1604.

SO I tried restoring to 1.0.2 after downloading it and I keep getting the same error!

Stuck on the yellow triangle!

Please someone tell me how to fix this - I am using Windows XP. Thanks.

This is about as far from an accident as you can get. Seriously, just switch to AT&T already.
 
lol! If I was in the US I would already!

It would make my life much easier but as much as this is a pain when it goes wrong - the sense of satisfaction you feel when you successfully pull off a hack is great!

I hacked my touch as soon as I felt I could handle the tutorial (when it had about 10 stages) and now I have got the latest unlocked modem firmware on my phone I just need an easier way to jailbreak.

Actually looking at the jailbreak and activation it doesn't look that hard - its no more complicated than the touch one I did BUT there are a few steps I am not sure about so I will wait a bit longer!

http://iphone.fiveforty.net/wiki/index.php/Jailbreak_1.1.1#Forcing_read-write_mode
 
I also got stucked on stage 1:2 attempting to boot iphone in normal mode.

I also got stucked on stage 1:2 attempting to boot iphone in normal mode...

you found a way to restore your iphone propertly yet?
please help~~
 
If it is stuck, on the Yellow Triangle, and nothing works, just box it up and take it back to the Apple Store. Tell them you were upgrading to 1.1.1 and there was a power outage and now you are locked out.

But in all seriousness... force an update to 1.1.1 again, that should get it back.
 
It would make my life much easier but as much as this is a pain when it goes wrong - the sense of satisfaction you feel when you successfully pull off a hack is great!

So I guess the question you have to ask yourself, does the satisfaction override the pain when the hack goes bad?

Sorry to hear about your problem, good luck fixing it.
 
Help! Brick my iPhone by accident

This is completely impossible.

No, there seem to be a couple instances of people on un-unlocked phones- virgins- that got bricked when upgrading to 1.1.1.... But you would be right in saying that was not an accident, Apple did it.
 
No, there seem to be a couple instances of people on un-unlocked phones- virgins- that got bricked when upgrading to 1.1.1.... But you would be right in saying that was not an accident, Apple did it.

My GFs iPhone was one of the phones you are talking about. Two weeks old, never hacked and it had to be restored while upgrading. Took 4 tries and a restart to get it to work. These iPhones were not bricked, just had restore and sync issues which were easily correctable.
My iPhone, on the other hand, which had been hacked since day 1 had no issues with the upgrade. Go figure.
 
My GFs iPhone was one of the phones you are talking about. Two weeks old, never hacked and it had to be restored while upgrading. Took 4 tries and a restart to get it to work. These iPhones were not bricked, just had restore and sync issues which were easily correctable.
My iPhone, on the other hand, which had been hacked since day 1 had no issues with the upgrade. Go figure.

That is pretty funny. But I think it is not the hacks, really, that caused the bricks (and why your phone was OK).... it was the Unlocks.

Could have just been an upgrade gone awry on the GF.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.