Page 2 of 2 FirstFirst 12
Results 11 to 15 of 15
Discuss Deadly Restore Error 1002 - Help! at the General - Hackint0sh.org; How do you load the "new" version filed in iPhuc? I get all the same ...
  1. #11
    Professional Array

    Join Date
    Aug 2007
    Posts
    72
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    9

    Default

    How do you load the "new" version filed in iPhuc?
    I get all the same errors as you guys, but mine tries to update to an older version of the firmware, while I was on V1.02 before it got fucked:

    Anyone know what 1014 means?
    Same problems as others in this thread report, diffent code though

    Restorelog also shows:
    [libusbrestore: 0xC24, 00:25:39.765] => <Restore Device 070FBDB0>: operation 18 progress -1
    [libusbrestore: 0xC24, 00:25:57.453] => <Restore Device 070FBDB0>: operation 19 progress -1
    [libusbrestore: 0xC24, 00:29:15.984] => _AMRestoreModeDeviceFinalize: 070FBDB0
    [libusbrestore: 0xB64, 00:29:15.421] => _AMRecoveryModeDeviceFinalize: 01F7DE40

    Where it used to show:
    [libusbrestore: 0x1124, 21:35:13.109] => <Restore Device 05050630>: operation 18 progress -1
    [libusbrestore: 0x1124, 21:35:32.734] => <Restore Device 05050630>: operation 19 progress -1
    [libusbrestore: 0x1124, 21:35:41.468] => <Restore Device 05050630>: operation 20 progress -1
    [libusbrestore: 0x1124, 21:35:42.593] => <Restore Device 05050630>: operation 21 progress -1

    So it skips steps 20 and 21?
    Anyone know what these two steps are? I suspect its the baseband?

    Usually force UpdateBaseBand gives a bunch of retries. Starts with:
    will update with usr/local/standalone/ICE03.12.06_G.fls and usr/local/standalone/ICE03.12.06_G.eep
    And then ends with bootloader is too old update to 1.8 or later and try again...

    But once in a while, it starts updating? Last time I connected with grestore phonedmg (fw1.0) after getting to restore, I replaced the contents of phonedmg with the files of the new firmware.... Then it started doing "something" and counting: ProgressUpdated: 01 - 100

    Which ended with: ProcessDetailUpdated: Sending end-pack.
    ProcessDetailUpdated: Process time was 2 min 3 sec.
    Error: Failed to download .FLS: Could not verify downloaded image.
    Done
    done.


  2. #12
    Rookie Array

    Join Date
    Sep 2007
    Location
    Christchurch, NZ
    Posts
    19
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Default

    Has anybody had any luck getting past the Yellow Triangle on a Mac with this error?

    Cheers, Chris W.

  3. #13
    Rookie Array

    Join Date
    Aug 2007
    Posts
    27
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Default

    I am still stuck with this problem. I got past the yellow triangle using wiNstaller but no luck getting past activation and the "Repair Needed" message. Any help would be greatly appreciated.

  4. #14
    Rookie Array

    Join Date
    Sep 2007
    Location
    Christchurch, NZ
    Posts
    19
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Talking

    PROBLEM IS FIXED!!! WOO HOO!

    Ok, I had another comms board on order so I thought: what did I have to loose? So, I cracked the iPhone up again and had a close look at the trace under 8x magnification. It is damn tiny so it was hard to make out, but after a while it seemed to me like the trace may have been damaged.

    So I grabbed a scraping tool (metal and pointy) and gently, and I mean gently, scraped off all of the green off the trace in the direction of the trace. It took about 10 minutes and I could see an unbroken line of copper heading around the small black surface mount diode/capacitor (not sure which) and towards the big black square chip (S-Gold).

    It all looked good, so I fired up bbupdater -f *.fls *.eep in my previously uploaded directory. It actually worked this time! Then a quick bbupdater -v to confirm and I was away.

    I did a restore in iTunes back to 1.0.2 and then loaded everything up again including the software unlock (had to use iUnlock as the anySIM one gave me the no matching bytes error).

    It wasn't necessary, but the rescue Wi-Fi kit is in this thread: http://www.hackint0sh.org/forum/showthread.php?t=5026

    Oh, to get past the Yellow Triangle I used iNdependence. Simply running it seemed to trip it to the activation screen. Then using iPhuc I uploaded lockdownd to the correct place, restarted and had access (but no Wi-Fi, etc).

    Thanks to go out to Sam and the Dev team!

    Cheers, Chris W.

  5. #15
    Guest Array

    Join Date
    Sep 2007
    Posts
    43
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Default Hi chris

    do you have some picture where is the damage?


 

 
Page 2 of 2 FirstFirst 12

Similar Threads

  1. Error 1002 After restore
    By cosmoprog in forum iPhone 3GS
    Replies: 1
    Last Post: 09-12-2011, 10:04 AM
  2. 3GS Restore Error 1002
    By RB30DET in forum iOS 4.x (iPhone OS 4.x)
    Replies: 4
    Last Post: 09-02-2011, 10:14 AM
  3. Error 1002 while Firmware restore
    By salo12 in forum iPhone 3G
    Replies: 3
    Last Post: 01-03-2011, 01:35 PM
  4. [Problem] Can't restore. Error 1002
    By chmd in forum iPhone 3G
    Replies: 5
    Last Post: 10-14-2008, 07:07 PM
  5. Cant Restore Error 1002 & 1011 Help
    By Sinister in forum Hardware Unlock
    Replies: 13
    Last Post: 03-10-2008, 07:55 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Powered by vBulletin®
Copyright © 2013 vBulletin Solutions, Inc. All rights reserved.
Search Engine Friendly URLs by vBSEO
(c) 2006-2012 Hackint0sh.org
All times are GMT +2. The time now is 12:14 PM.
twitter, follow us!