Page 1 of 7 1234567 LastLast
Results 1 to 10 of 62
Discuss [1.1.2 (1.1.2 OTB week 50) ][IMEI & ICCID Unknown and Repair Nedeed] at the Hardware Unlock - Hackint0sh.org; ...
  1. #1
    Newbie Array

    Join Date
    Feb 2008
    Posts
    5
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Default [1.1.2 (1.1.2 OTB week 50) ][IMEI & ICCID Unknown and Repair Nedeed]

    I have a problem ! I read all posts in the forum and no found soluction for my case...

    look my case...

    Ihave one iphone fw 1.1.2 OTB week 50 !
    I try to harsware unlock on my iphone ... And when i erase the baseband and write it again... Have a problem... And i restart the iphone .. I try to restone the iphone for the fw 1.1.1 .. I thought its complete this step the iphone back to the normal mode... But after the iphone show me the error Reapair Nedeed and the *#307# + Call not employee... and i try to restore my iphone for the fw's 1.1.1, 1.1.2, 1.1.3... I try to restore for fw 1.0.2 but my iphone is 50 week and the iphones up for the 49 week no accept the fw 1.0.2... The iTunes sayng... ¨Waiting the phone¨ all the time... I try too downgrade from iBrickr... and not employee too....
    All the restores show me the error 1011... ever... I try to normal mode... and in DFU mode (Home + Power) ele sempre da o erro 1011...
    I try to restore in all version of iTunes.. 7.4~7.6...
    All the people sayng in the forum after retore the iphone for fw 1.1.3.. its back... But my iphone no... Its presents the error 1011 ever... and dont have the imei and ICCI...

    Anybody helpme ???
    Please... Thanks a lot !


    PS: Sorry for bad english.



  2. #2
    Rookie Array

    Join Date
    Jan 2008
    Posts
    26
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Default

    Quote Originally Posted by tckmarco View Post
    I have a problem ! I read all posts in the forum and no found soluction for my case...

    look my case...

    Ihave one iphone fw 1.1.2 OTB week 50 !
    I try to harsware unlock on my iphone ... And when i erase the baseband and write it again... Have a problem... And i restart the iphone .. I try to restone the iphone for the fw 1.1.1 .. I thought its complete this step the iphone back to the normal mode... But after the iphone show me the error Reapair Nedeed and the *#307# + Call not employee... and i try to restore my iphone for the fw's 1.1.1, 1.1.2, 1.1.3... I try to restore for fw 1.0.2 but my iphone is 50 week and the iphones up for the 49 week no accept the fw 1.0.2... The iTunes sayng... ¨Waiting the phone¨ all the time... I try too downgrade from iBrickr... and not employee too....
    All the restores show me the error 1011... ever... I try to normal mode... and in DFU mode (Home + Power) ele sempre da o erro 1011...
    I try to restore in all version of iTunes.. 7.4~7.6...
    All the people sayng in the forum after retore the iphone for fw 1.1.3.. its back... But my iphone no... Its presents the error 1011 ever... and dont have the imei and ICCI...

    Anybody helpme ???
    Please... Thanks a lot !


    PS: Sorry for bad english.
    dal nome credo che sei italiano.

    I am in your same situation, i think we are fu...ed

  3. #3
    Newbie Array

    Join Date
    Feb 2008
    Posts
    5
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Default

    Quote Originally Posted by tckmarco View Post
    I have a problem ! I read all posts in the forum and no found soluction for my case...

    look my case...

    Ihave one iphone fw 1.1.2 OTB week 50 !
    I try to harsware unlock on my iphone ... And when i erase the baseband and write it again... Have a problem... And i restart the iphone .. I try to restone the iphone for the fw 1.1.1 .. I thought its complete this step the iphone back to the normal mode... But after the iphone show me the error Reapair Nedeed and the *#307# + Call not employee... and i try to restore my iphone for the fw's 1.1.1, 1.1.2, 1.1.3... I try to restore for fw 1.0.2 but my iphone is 50 week and the iphones up for the 49 week no accept the fw 1.0.2... The iTunes sayng... ¨Waiting the phone¨ all the time... I try too downgrade from iBrickr... and not employee too....
    All the restores show me the error 1011... ever... I try to normal mode... and in DFU mode (Home + Power) ele sempre da o erro 1011...
    I try to restore in all version of iTunes.. 7.4~7.6...
    All the people sayng in the forum after retore the iphone for fw 1.1.3.. its back... But my iphone no... Its presents the error 1011 ever... and dont have the imei and ICCI...

    Anybody helpme ???
    Please... Thanks a lot !


    PS: Sorry for bad english.

    Anybody Help ME ???

  4. #4
    Professional Array Gstar's Avatar

    Join Date
    Jan 2008
    Location
    Germany
    Posts
    92
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    11

    Default

    no one cares about us since the SW unlock is out. perhaps our phones are really irreparable. WE ARE LOST AND OUR IPHONES ARE GARBAGE !!!!

    4 weeks ago geohot told us that there is no SW unlock in the near future. we have bricked our phones and now there is the easiest unlock ever available.

    i am FRUSTRATED!!! 400 bucks blown away

  5. #5
    Newbie Array

    Join Date
    Jan 2008
    Posts
    2
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Default How I fixed my bricked phonee

    Quote Originally Posted by Gstar View Post
    no one cares about us since the SW unlock is out. perhaps our phones are really irreparable. WE ARE LOST AND OUR IPHONES ARE GARBAGE !!!!

    4 weeks ago geohot told us that there is no SW unlock in the near future. we have bricked our phones and now there is the easiest unlock ever available.

    i am FRUSTRATED!!! 400 bucks blown away
    I found what the problem was with my bricked phone, I suspect it is tv same problem that you all have. The problem with mine was that the line used for the testpoint was broken and did not allow the iPhone to erase or reflash the baseband. A friend of mine using a special camera to zoom in was able to reconstruct track 17 after that I restored my iPhone to 1.1.3 and then took it back to 1.1.1, jailbreaked it an unlocked using gunlock. Hope this helps, I know how you guys feel, I really was very frustrated until I found the problem. Please write if it works for you.


  6. #6
    Professional Array Gstar's Avatar

    Join Date
    Jan 2008
    Location
    Germany
    Posts
    92
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    11

    Default

    do you mean with a conductive pen? if so i'll check the trace with a microscope and then repair it.

    thx gstar

  7. #7
    Rookie Array

    Join Date
    Jan 2008
    Posts
    26
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Default

    i will check to..

  8. #8
    Newbie Array

    Join Date
    Feb 2008
    Posts
    1
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Default

    exactly the same problem, the only diference its that mi iphone is from week 46 and i restored to 1.0.2 but no luck with flashing the baseband (bbupdater -f *.fls -e *.eep) and when i restore always error 1011 so think i have an expensive paper holder

  9. #9
    Professional Array Gstar's Avatar

    Join Date
    Jan 2008
    Location
    Germany
    Posts
    92
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    11

    Default

    hi,

    yesterday i've talked to apple care center. it was a funny telefon call... he asked me how i activated the phone w/o att or t-mobile contract... he told me that it is my iphone and that i can do what i want but he tried to help me.

    the error 1011 is a connection error. the result of a restoring or update procedure is saved in a log file on your computer. path for XP: C:\Documents and Settings\[username]\Application Data\Apple Computer\iTunes\iPhone Updater Logs
    ok here is an extract of mine when i tried to make a full restore to 1.1.3 to fix my baseband:

    Code:
    Restoring  ....10....20....30....40....50....60....70....80....90....100
    Copied 255595008 bytes in 81.99 seconds, 3044.23 KiB/s
    	Verifying  ....10....20....30....40....50....60....70....80....90....100
    Verified SHA-1 checksum 255595008 bytes in 55.80 seconds, 4473.21 KiB/s
    entering mount_filesystems
    executing /sbin/fsck_hfs
    ** /dev/rdisk0s1
    ** Checking HFS Plus volume.
    ** Detected a case-sensitive catalog.
    ** Checking Extents Overflow file.
    ** Checking Catalog file.
    ** Checking Catalog hierarchy.
    ** Checking volume bitmap.
    ** Checking volume information.
    ** The volume LittleBear4A93.UserBundle appears to be OK.
    executing /sbin/mount_hfs
    executing /sbin/fsck_hfs
    ** /dev/rdisk0s2
    ** Checking HFS Plus volume.
    ** Detected a case-sensitive catalog.
    ** Checking Extents Overflow file.
    ** Checking Catalog file.
    ** Checking Catalog hierarchy.
    ** Checking volume bitmap.
    ** Checking volume information.
    ** The volume Data appears to be OK.
    executing /sbin/mount_hfs
    entering fixup_var
    remove_path /mnt1/private/var
    executing /bin/rm
    creating directory (owner=0 mode=755) /mnt1/private/var
    entering unmount_filesystems
    entering clear_persistent_boot_args
    executing /usr/sbin/nvram
    entering update_NOR
    flashing NOR data
    flashing NOR data
    flashing NOR data
    flashing NOR data
    flashing NOR data
    flashing NOR data
    flashing NOR data
    flashing NOR data
    flashing LLB data
    entering update_baseband
    perform_baseband_update: update_baseband_bootloader=1 force_baseband_update=0
    executing /usr/local/bin/bbupdater
    Resetting target...
    pinging the baseband...
    baseband unresponsive to pinging
    no appropriate bootloader found
    Done
    executing /usr/local/bin/bbupdater
    Resetting target...
    pinging the baseband...
    baseband unresponsive to pinging
    will update with /usr/local/standalone/firmware/ICE04.03.13_G.fls
        and /usr/local/standalone/firmware/ICE04.03.13_G.eep
    Preparing to flash using /dev/tty.baseband at 750000 baud
    Please reset target
    Resetting target...
    ProcessOutlineUpdated: Process time was 10.0 sec.
    Retry attempt 1
    Resetting target...
    ProcessOutlineUpdated: Process time was 10.0 sec.
    Retry attempt 2
    Resetting target...
    ProcessOutlineUpdated: Process time was 10.0 sec.
    Retry attempt 3
    Resetting target...
    ProcessOutlineUpdated: Process time was 10.0 sec.
    Retry attempt 4
    Resetting target...
    ProcessOutlineUpdated: Process time was 10.0 sec.
    Retry attempt 5
    Resetting target...
    ProcessOutlineUpdated: Process time was 10.0 sec.
    Retry attempt 6
    Resetting target...
    ProcessOutlineUpdated: Process time was 10.0 sec.
    Retry attempt 7
    Resetting target...
    ProcessOutlineUpdated: Process time was 10.0 sec.
    Retry attempt 8
    Resetting target...
    ProcessOutlineUpdated: Process time was 10.0 sec.
    Retry attempt 9
    Resetting target...
    ProcessOutlineUpdated: Process time was 10.0 sec.
    Retry attempt 10
    Error: Baseband bootloader is too old; update to 1.8 or later and try again
    Done
    matching ICE04.03.13_G.fls...
    currVers 0x47, fileVers 0x4030d47
    will update with this version
    
    ==== end of device restore output ====
    [libusbrestore: 0x270, 13:20:19.296] => <Restore Device 022C2D58>: Restore failed (result = 1011)
    so i think that the trace is broken or the baseband chip is totally damaged.
    any suggestions?

    gstar
    Last edited by Gstar; 02-12-2008 at 02:01 PM.

  10. #10
    Rookie Array

    Join Date
    Feb 2008
    Location
    Italy
    Posts
    16
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Default

    Quote Originally Posted by Gstar View Post
    hi,

    yesterday i've talked to apple care center. it was a funny telefon call... he asked me how i activated the phone w/o att or t-mobile contract... he told me that it is my iphone and that i can do what i want but he tried to help me.

    the error 1011 is a connection error. the result of a restoring or update procedure is saved in a log file on your computer. path for XP: C:\Documents and Settings\[username]\Application Data\Apple Computer\iTunes\iPhone Updater Logs
    ok here is an extract of mine when i tried to make a full restore to 1.1.3 to fix my baseband:

    Code:
    Restoring  ....10....20....30....40....50....60....70....80....90....100
    Copied 255595008 bytes in 81.99 seconds, 3044.23 KiB/s
    	Verifying  ....10....20....30....40....50....60....70....80....90....100
    Verified SHA-1 checksum 255595008 bytes in 55.80 seconds, 4473.21 KiB/s
    entering mount_filesystems
    executing /sbin/fsck_hfs
    ** /dev/rdisk0s1
    ** Checking HFS Plus volume.
    ** Detected a case-sensitive catalog.
    ** Checking Extents Overflow file.
    ** Checking Catalog file.
    ** Checking Catalog hierarchy.
    ** Checking volume bitmap.
    ** Checking volume information.
    ** The volume LittleBear4A93.UserBundle appears to be OK.
    executing /sbin/mount_hfs
    executing /sbin/fsck_hfs
    ** /dev/rdisk0s2
    ** Checking HFS Plus volume.
    ** Detected a case-sensitive catalog.
    ** Checking Extents Overflow file.
    ** Checking Catalog file.
    ** Checking Catalog hierarchy.
    ** Checking volume bitmap.
    ** Checking volume information.
    ** The volume Data appears to be OK.
    executing /sbin/mount_hfs
    entering fixup_var
    remove_path /mnt1/private/var
    executing /bin/rm
    creating directory (owner=0 mode=755) /mnt1/private/var
    entering unmount_filesystems
    entering clear_persistent_boot_args
    executing /usr/sbin/nvram
    entering update_NOR
    flashing NOR data
    flashing NOR data
    flashing NOR data
    flashing NOR data
    flashing NOR data
    flashing NOR data
    flashing NOR data
    flashing NOR data
    flashing LLB data
    entering update_baseband
    perform_baseband_update: update_baseband_bootloader=1 force_baseband_update=0
    executing /usr/local/bin/bbupdater
    Resetting target...
    pinging the baseband...
    baseband unresponsive to pinging
    no appropriate bootloader found
    Done
    executing /usr/local/bin/bbupdater
    Resetting target...
    pinging the baseband...
    baseband unresponsive to pinging
    will update with /usr/local/standalone/firmware/ICE04.03.13_G.fls
        and /usr/local/standalone/firmware/ICE04.03.13_G.eep
    Preparing to flash using /dev/tty.baseband at 750000 baud
    Please reset target
    Resetting target...
    ProcessOutlineUpdated: Process time was 10.0 sec.
    Retry attempt 1
    Resetting target...
    ProcessOutlineUpdated: Process time was 10.0 sec.
    Retry attempt 2
    Resetting target...
    ProcessOutlineUpdated: Process time was 10.0 sec.
    Retry attempt 3
    Resetting target...
    ProcessOutlineUpdated: Process time was 10.0 sec.
    Retry attempt 4
    Resetting target...
    ProcessOutlineUpdated: Process time was 10.0 sec.
    Retry attempt 5
    Resetting target...
    ProcessOutlineUpdated: Process time was 10.0 sec.
    Retry attempt 6
    Resetting target...
    ProcessOutlineUpdated: Process time was 10.0 sec.
    Retry attempt 7
    Resetting target...
    ProcessOutlineUpdated: Process time was 10.0 sec.
    Retry attempt 8
    Resetting target...
    ProcessOutlineUpdated: Process time was 10.0 sec.
    Retry attempt 9
    Resetting target...
    ProcessOutlineUpdated: Process time was 10.0 sec.
    Retry attempt 10
    Error: Baseband bootloader is too old; update to 1.8 or later and try again
    Done
    matching ICE04.03.13_G.fls...
    currVers 0x47, fileVers 0x4030d47
    will update with this version
    
    ==== end of device restore output ====
    [libusbrestore: 0x270, 13:20:19.296] => <Restore Device 022C2D58>: Restore failed (result = 1011)
    so i think that the trace is broken or the baseband chip is totally damaged.
    any suggestions?

    gstar



    same output

    Code:
    ==== device restore output ====
    entering wait_for_storage_device
    entering create_filesystem_partitions
    executing /sbin/newfs_hfs
    Initialized /dev/rdisk0s1 as a 300 MB HFS Plus volume
    executing /sbin/newfs_hfs
    Initialized /dev/rdisk0s2 as a 7443 MB HFS Plus volume
    entering restore_images
    executing /usr/sbin/asr
    Waiting for connection attempt from server
    	Validating target...done
    	Validating source...done
    Warning: the target volume may not be bootable
    
    	Erasing target device /dev/disk0s1...done
    	Retrieving scan information...done
    	Validating sizes...done
    	Restoring  ....10....20....30....40....50....60....70....80....90....100
    Copied 255595008 bytes in 82.54 seconds, 3023.98 KiB/s
    	Verifying  ....10....20....30....40....50....60....70....80....90....100
    Verified SHA-1 checksum 255595008 bytes in 52.44 seconds, 4760.03 KiB/s
    entering mount_filesystems
    executing /sbin/fsck_hfs
    ** /dev/rdisk0s1
    ** Checking HFS Plus volume.
    ** Detected a case-sensitive catalog.
    ** Checking Extents Overflow file.
    ** Checking Catalog file.
    ** Checking Catalog hierarchy.
    ** Checking volume bitmap.
    ** Checking volume information.
    ** The volume LittleBear4A93.UserBundle appears to be OK.
    executing /sbin/mount_hfs
    executing /sbin/fsck_hfs
    ** /dev/rdisk0s2
    ** Checking HFS Plus volume.
    ** Detected a case-sensitive catalog.
    ** Checking Extents Overflow file.
    ** Checking Catalog file.
    ** Checking Catalog hierarchy.
    ** Checking volume bitmap.
    ** Checking volume information.
    ** The volume Data appears to be OK.
    executing /sbin/mount_hfs
    entering fixup_var
    remove_path /mnt1/private/var
    executing /bin/rm
    creating directory (owner=0 mode=755) /mnt1/private/var
    entering unmount_filesystems
    entering clear_persistent_boot_args
    executing /usr/sbin/nvram
    entering update_NOR
    flashing NOR data
    flashing NOR data
    flashing NOR data
    flashing NOR data
    flashing NOR data
    flashing NOR data
    flashing NOR data
    flashing NOR data
    flashing LLB data
    entering update_baseband
    perform_baseband_update: update_baseband_bootloader=1 force_baseband_update=0
    executing /usr/local/bin/bbupdater
    Resetting target...
    pinging the baseband...
    baseband unresponsive to pinging
    no appropriate bootloader found
    Done
    executing /usr/local/bin/bbupdater
    Resetting target...
    pinging the baseband...
    baseband unresponsive to pinging
    will update with /usr/local/standalone/firmware/ICE04.03.13_G.fls
        and /usr/local/standalone/firmware/ICE04.03.13_G.eep
    Preparing to flash using /dev/tty.baseband at 750000 baud
    Please reset target
    Resetting target...
    ProcessOutlineUpdated: Process time was 10.0 sec.
    Retry attempt 1
    Resetting target...
    ProcessOutlineUpdated: Process time was 10.0 sec.
    Retry attempt 2
    Resetting target...
    ProcessOutlineUpdated: Process time was 10.0 sec.
    Retry attempt 3
    Resetting target...
    ProcessOutlineUpdated: Process time was 10.0 sec.
    Retry attempt 4
    Resetting target...
    ProcessOutlineUpdated: Process time was 10.0 sec.
    Retry attempt 5
    Resetting target...
    ProcessOutlineUpdated: Process time was 10.0 sec.
    Retry attempt 6
    Resetting target...
    ProcessOutlineUpdated: Process time was 10.0 sec.
    Retry attempt 7
    Resetting target...
    ProcessOutlineUpdated: Process time was 10.0 sec.
    Retry attempt 8
    Resetting target...
    ProcessOutlineUpdated: Process time was 10.0 sec.
    Retry attempt 9
    Resetting target...
    ProcessOutlineUpdated: Process time was 10.0 sec.
    Retry attempt 10
    Error: Baseband bootloader is too old; update to 1.8 or later and try again
    Done
    matching ICE04.03.13_G.fls...
    currVers 0x47, fileVers 0x4030d47
    will update with this version
    
    ==== end of device restore output ====
    [libusbrestore: 0x98, 20:19:18.814] => <Restore Device 02202A30>: Restore failed (result = 1011)


 

 
Page 1 of 7 1234567 LastLast

Similar Threads

  1. [Solution] IMEI: Unknown | ICCID: Unknown | No WiFi | etc...
    By Letusgo2Hell in forum iPhone "2G" (Rev. 1)
    Replies: 248
    Last Post: 08-16-2008, 07:42 PM
  2. Replies: 39
    Last Post: 02-29-2008, 04:13 AM
  3. (1.1.2 OTB week 50) ][IMEI & ICCID Unknown and Repair Nedeed]
    By tckmarco in forum iPhone "2G" (Rev. 1)
    Replies: 0
    Last Post: 02-10-2008, 06:14 PM
  4. 1.1.2 OTB week 51,Imei:Unknown ICCID:Unknown
    By Manuelmattar in forum iPhone "2G" (Rev. 1)
    Replies: 2
    Last Post: 02-09-2008, 07:01 PM
  5. [1.1.2 OTB] HW Unlock completed, unknown imei, unknown iccid...
    By bryscomat in forum iPhone "2G" (Rev. 1)
    Replies: 19
    Last Post: 01-26-2008, 12:08 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 © 2014 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 01:58 PM.
twitter, follow us!