Home User CP Donate Chat Register Today!  
  Get New posts Faq / Help?
   


Go Back   Hackint0sh > Projects and Hacks > iPhone > iPhone "2G" (Rev. 1) > Hardware Unlock

Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 02-10-2008, 12:21 AM
tckmarco
Status: Offline
Junior Member
 
Join Date: Feb 2008
Posts: 5
Rep Power: 0
tckmarco is on a distinguished road
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.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote
  #2 (permalink)  
Old 02-10-2008, 02:31 AM
alino74
Status: Offline
Junior Member
 
Join Date: Jan 2008
Posts: 26
Rep Power: 0
alino74 is on a distinguished road
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
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote
  #3 (permalink)  
Old 02-10-2008, 07:09 PM
tckmarco
Status: Offline
Junior Member
 
Join Date: Feb 2008
Posts: 5
Rep Power: 0
tckmarco is on a distinguished road
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 ???
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote
Sponsored links Remove advertisements
Advertisement
Advertisement

  #4 (permalink)  
Old 02-10-2008, 08:24 PM
Gstar's Avatar
Gstar
Status: Offline
Member
 
Join Date: Jan 2008
Location: Germany
Posts: 92
Rep Power: 6
Gstar is on a distinguished road
Send a message via Skype™ to Gstar
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
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote
  #5 (permalink)  
Old 02-10-2008, 11:44 PM
xantor
Status: Offline
Junior Member
 
Join Date: Jan 2008
Posts: 2
Rep Power: 0
xantor is on a distinguished road
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.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote
  #6 (permalink)  
Old 02-11-2008, 12:00 AM
Gstar's Avatar
Gstar
Status: Offline
Member
 
Join Date: Jan 2008
Location: Germany
Posts: 92
Rep Power: 6
Gstar is on a distinguished road
Send a message via Skype™ to Gstar
Default

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

thx gstar
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote
Sponsored links Remove advertisements
Advertisement
Advertisement

  #7 (permalink)  
Old 02-11-2008, 12:49 AM
alino74
Status: Offline
Junior Member
 
Join Date: Jan 2008
Posts: 26
Rep Power: 0
alino74 is on a distinguished road
Default

i will check to..
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote
  #8 (permalink)  
Old 02-11-2008, 04:32 AM
Inutero
Status: Offline
Junior Member
 
Join Date: Feb 2008
Posts: 1
Rep Power: 0
Inutero is on a distinguished road
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
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote
  #9 (permalink)  
Old 02-12-2008, 02:57 PM
Gstar's Avatar
Gstar
Status: Offline
Member
 
Join Date: Jan 2008
Location: Germany
Posts: 92
Rep Power: 6
Gstar is on a distinguished road
Send a message via Skype™ to Gstar
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 03:01 PM.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote
Sponsored links Remove advertisements
Advertisement
Advertisement

  #10 (permalink)  
Old 02-12-2008, 09:37 PM
p01s0n
Status: Offline
Junior Member
 
Join Date: Feb 2008
Location: Italy
Posts: 16
Rep Power: 0
p01s0n is on a distinguished road
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)
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On




All times are GMT +2. The time now is 09:42 PM.



Powered by vBulletin® Version 3.8.2
Copyright ©2000 - 2009, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 3.3.2 Ad Management by RedTyger
follow us on Twitter!

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105