Hi there!

Well, I went and did something silly: I restored after the iEraser step, but before the iUnlocker step when trying to unlock my iPhone. Yes, I really regret this move. Now all I get is the following error in iTunes: "The iPhone "iPhone" could not be restored. An unknown error occurred (1002)."

I have double-checked everything and the hardware looks as clean as a whistle, (was using needles, etc). I can use iPhuc to put it into interactive restore mode, but I have no idea what to do from this point.

Does anyone have any ideas?

Cheers, Chris W.

well i'd just go to the next apple store, with your receipe, and say you were updating to 1.0.2, while your house had a blackout, and all power was gone, and the computer (stationary, not laptop!) crashed too.

Try if this works, somebody mentioned this a few threats down. He got the instructions from Apple Care

The Fix: Force Restore - (Thank You AppleCare)

1) Turn Off iPhone, disconnect from computer
2) Launch iTunes
3) Hold "Home" button on iPhone
4) Connect iPhone USB to computer and iPhone - KEEP HOLDING
5) iTunes should mount iPhone and force restore

I had this same problem last night when i stopped my restore in the middle because it was stuck. All I did was uninstall itunes and reinstall and it was able to restore ok.

Thanks guys, but none of the suggestions to fix without returning have worked and I still have a bricPhone.

I saw some speculation that the reason it is failing is because it doesn't try updating the modem firmware as the version number hasn't changed. Maybe Apple will release an update in the future that will contain an update and fix this?

Still keen on any other ideas to force a reflash!

Cheers, Chris W.

try downgrading to 1.0 maybe.
haven´t done this myself yet, but i´ve read then when holding the "ALT" key while clicking on restore in itunes you can choose your update file. so just grab the 1.0 ipsw and choose it.

http://appldnld.apple.com.edgesuite....a_Restore.ipsw

try downgrading to 1.0 maybe.

Downgrading is not possible.

There were two threads addressing this issue a while ago.

Cheers, James

Hmm I don't know what I did, but the iPhone Update Log ~/Library/Logs/iPhone Updater Logs from my last attempted restore now has some useful errors in it. In particular when iTunes get to near to the last operation (number 19) this repeats over and over again before it gives up:

ProcessDetailUpdated: Boot-loader is active
ProcessDetailUpdated: EBL version: 3.9_M3S2 3..9
ProcessDetailUpdated: Boot mode is: CC
ProcessDetailUpdated: Baud rate set to 750000
ProcessDetailUpdated: Get flash id.
ProcessDetailUpdated: CFI stage 1
ProcessDetailUpdated: Flash ID is: 88620089
ProcessDetailUpdated: CFI stage 2
ProcessDetailUpdated: Boot process finished
ProcessOutlineUpdated: Reading SW version data
ProcessDetailUpdated: Receiving data.
ProgressUpdated: 100
ProcessDetailUpdated: Upload OK
ProcessOutlineUpdated: Process time was 132 msec.
Upgrade from to
Downloading EEP
ProcessOutlineUpdated: Start downloading from file /usr/local/standalone/firmware/ICE03.14.08_G.eep.
ProcessDetailUpdated: Sending sec-pack.
ProcessDetailUpdated: Load region 0
ProcessDetailUpdated: Sending end-pack.
ProcessOutlineUpdated: Process time was 2632 msec.
Error: Failed to download .EEP: Expected checksum D510 got D548
Done
matching ICE03.14.08_G.fls...
currVers 0x47, fileVers 0x30e0847
will update with this version
matching ICE03.14.08_G.fls...
currVers 0x47, fileVers 0x30e0847
will update with this version
matching ICE03.14.08_G.fls...
currVers 0x47, fileVers 0x30e0847
will update with this version
matching ICE03.14.08_G.fls...
currVers 0x47, fileVers 0x30e0847
will update with this version
matching ICE03.14.08_G.fls...
currVers 0x47, fileVers 0x30e0847
will update with this version
matching ICE03.14.08_G.fls...
currVers 0x47, fileVers 0x30e0847
will update with this version
matching ICE03.14.08_G.fls...
currVers 0x47, fileVers 0x30e0847
will update with this version
matching ICE03.14.08_G.fls...
currVers 0x47, fileVers 0x30e0847
will update with this version
matching ICE03.14.08_G.fls...
currVers 0x47, fileVers 0x30e0847
will update with this version
matching ICE03.14.08_G.fls...
currVers 0x47, fileVers 0x30e0847
will update with this version
done.
UpdateBaseBand...Resetting target...
pinging the baseband...
baseband unresponsive to pinging
no appropriate bootloader found
Done
Resetting target...
pinging the baseband...
baseband unresponsive to pinging
will update with /usr/local/standalone/firmware/ICE03.14.08_G.fls
and /usr/local/standalone/firmware/ICE03.14.08_G.eep
Preparing to flash using /dev/tty.baseband at 750000 baud
Please reset target
Resetting target...

Hmm - so a new version of the software may not help here. Does anyone have an idea why it is failing the checksum (not sure how to read this). Appreciate anyone's help!

Full log here - iPhone Updater Log

Cheers, Chris W.

If I do a grestore in iPHUC and then after reconnecting issue "force UpdateBaseBand", it outputs the following:

UpdateBaseBand..Resetting target..
pinging the baseband..
baseband unresponsive to pinging
will update with /usr/local/standalone/firmware/ICE03.14.08_G.fls
and /usr/local/standalone/firmware/ICE03.14.08_G.eep
Preparing to flash using /dev/tty.baseband at 750000 baud
Please reset target
Resetting target...

Then it does 10 retry attempts and fails with message

Error: Baseband bootloader is too old; update to 1.8 or later and try again

Any ideas on that?

Same here and I do not know what it means. It is very frustrating, but I am coming to the realisation that I may have damaged the comms board. I have asked the ifixit.com guys for notification when they get a working one in, but this could be a while. In the meantime I may have to buy another one! At least they are cheaper now...

Cheers, Chris W.