Page 1 of 3 123 LastLast
Results 1 to 10 of 29
Discuss [1.1.2 OTB] HW BL Downgrade gone wrong and the log from my update to 1.1.3 at the iPhone "2G" (Rev. 1) - Hackint0sh.org; I lost Wifi too, so I did everything from the MobileTerminal. iunew finished and bbupdater ...
  1. #1
    Advanced Array

    Join Date
    Jun 2007
    Posts
    40
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Default [1.1.2 OTB][BRICK FIXED - READ HERE!] HW BL Downgrade gone wrong

    I lost Wifi too, so I did everything from the MobileTerminal.
    iunew finished and bbupdater -v gave no output.
    So I restored 1.1.1 -> IMEI: unkown ICCID: unknown
    So I restored 1.1.2 -> IMEI: unkown ICCID: unknown
    So I restored 1.0.2 -> IMEI: unkown ICCID: unknown
    Jailbreaked & activated 1.0.2
    Tried everything I could imagine and nothing, so back to 1.1.2
    So I restored 1.1.2 again -> IMEI: unkown ICCID: unknown
    So I restored 1.0.2 again -> IMEI: unkown ICCID: unknown
    Jailbreaked & activated 1.0.2 again -> nothing, tried every secpack, ieraser, ienew (waiting for data), iunew, bbupdater, nothing

    So I said, what the hell, let's update to 1.1.3
    In the meantime I found the IphoneUpdater.log files in Windows and was looking at them on every update. In the end Itunes always gave me an error 1011.

    I updated to 1.1.3 and again Error 1011 and no way to get out of recovery mode.
    So I looked at the log again and this was the 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 7444 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 91.51 seconds, 2727.50 KiB/s
    	Verifying  ....10....20....30....40....50....60....70....80....90....100
    Verified SHA-1 checksum 255595008 bytes in 57.16 seconds, 4366.50 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: 0xFC0, 08:20:03.687] => <Restore Device 050B7E78>: Restore failed (result = 1011)
    (I highlighted some interesting parts)

    Any ideas? The only thing I can think of is that maybe I scratched a little too much and need to repair the A17 trace with a repairing pen, since my baseband don't seem to respond. Looking at the device restore output I think a broken bootloader would be repaired by the 1.1.3 restore or not?

    Any ideas? I'm willing to try anything. Remember that the only Firmware where I can try things out is 1.0.2

    BTW: I used the i.unlock.no package before it was updated. Maybe that nor was wrong and that's why my bootloader is wrong, since I read that there are many people with the same symptoms. Anyway to try it again? geohot?
    Last edited by wildbomb; 01-20-2008 at 06:14 PM.



  2. #2
    Rookie Array

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

    Default

    So u r stuck at step 5 as well, I dont think A17 interface is damaged since it wuldnt complete the iunew, you have to hold for at list 30 sec. Im downloadind 1.1.3, but maybe we need to select UPDATE instead of RESTORE to restore BB? Maybe also for 1.1.2 but how to get to UPDATE button.. This sucks.. I was waitnig for month to release some sw now this.. its not worht it..

  3. #3
    Rookie Array

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

    Default

    the same happened to me.. I put 1.1.3 to try recover BB and couldnt get out of recovery mode . Before my bl was successfully downgraded, at list that was the com messagess . I restarted downgrade (holding power & home) and now is donwgrading to 1.1.2

  4. #4
    Advanced Array

    Join Date
    Jun 2007
    Posts
    40
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Default

    I tried again with 1.1.1 and got this:

    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 7444 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 243786240 bytes in 81.48 seconds, 2921.95 KiB/s
    	Verifying  ....10....20....30....40....50....60....70....80...could not receive message
    .90....100
    Verified SHA-1 checksum 243786240 bytes in 54.48 seconds, 4369.57 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 Snowbird3A109a.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
    executing /bin/rm
    executing /bin/mkdir
    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
    executing /usr/local/bin/bbupdater
    Resetting target...
    pinging the baseband...
    baseband unresponsive to pinging
    will update with /usr/local/standalone/firmware/BOOT03.01_M2S1.fls
    Preparing to flash using /dev/tty.debug at 115200 baud
    Please reset target
    Resetting target...
    synchronized
    ProcessOutlineUpdated: Process time was 10.0 sec.
    Retry attempt 1
    Resetting target...
    synchronized
    ProcessOutlineUpdated: Process time was 10.0 sec.
    Retry attempt 2
    Resetting target...
    synchronized
    ProcessOutlineUpdated: Process time was 10.0 sec.
    Retry attempt 3
    Resetting target...
    synchronized
    ProcessOutlineUpdated: Process time was 10.0 sec.
    Retry attempt 4
    Resetting target...
    synchronized
    ProcessOutlineUpdated: Process time was 10.0 sec.
    Retry attempt 5
    Resetting target...
    synchronized
    ProcessOutlineUpdated: Process time was 10.0 sec.
    Retry attempt 6
    Resetting target...
    synchronized
    ProcessOutlineUpdated: Process time was 10.0 sec.
    Retry attempt 7
    Resetting target...
    synchronized
    ProcessOutlineUpdated: Process time was 10.0 sec.
    Retry attempt 8
    Resetting target...
    synchronized
    ProcessOutlineUpdated: Process time was 10.0 sec.
    Retry attempt 9
    Resetting target...
    synchronized
    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
    
    ==== end of device restore output ====
    Isn't that a bootloader file? So Itunes is trying to "update" my bootloader to 3.01?
    Does that mean that bootloader updates ARE possible with bbupdater?

    So what I'm seeing here is, that the nor-file from i.unlock.no was bad, so I wrote shit to my flash and now I don't have a working bootloader. geohot, is there any way to solve this?

  5. #5
    Advanced Array

    Join Date
    Jun 2007
    Posts
    40
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Default

    No comments? Advices?


  6. #6
    Advanced Array

    Join Date
    Jun 2007
    Posts
    40
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Default

    So, I FIXED IT!
    ienew -> Waiting for data
    iunew -> did you erase your baseband?

    So i ran iunew again with the testpoint active and it detected the testpoint! went ahead and got stuck after 3 lines on: Attempting to read[1]...45
    The iPhone was kind of stuck, so i tried to get out of the terminal, nothing, pressed the off button a couple of seconds and the slide to power of came, so i canceled it.
    I was back at the springboard. Copied the 3.14 fls and eep files over and ran bbupdater -e *.eep -f *.fls and it worked!

    Now I have a 1.1.2 OTB with BL 3.9!!!!

    So try it out!

    Mod, please change title!!!
    Last edited by wildbomb; 01-20-2008 at 06:00 PM.

  7. #7
    Rookie Array

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

    Default

    Im getting 1011 error with every firmware and cant jailbreak. Latest I was using 1.0.2. with Ibrickr 0.91. but just endless restarts.

  8. #8
    Advanced Array

    Join Date
    Jun 2007
    Posts
    40
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Default

    Quote Originally Posted by danac View Post
    Im getting 1011 error with every firmware and cant jailbreak. Latest I was using 1.0.2. with Ibrickr 0.91. but just endless restarts.
    Just keep trying. Eventually iBrickr will work and you can jailbreak 1.0.2
    After that use the original pacay to activate it so you can use the phone. Install the BSD Subsystem and MobileTerminal, copy the files with iBrickr and try again!

    Wish you luck!

  9. #9
    Advanced Array

    Join Date
    Nov 2007
    Posts
    48
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Default

    Okay so question for wildbomb... I WAS OTB112

    I upgraded to 1.1.3 because I also thought that there was no way out.. but my update went through and now i DO have an IMEI# and IICID..

    Does this mean I can or CANT downgrade back to 1.1.2 and try the hw unlock (again for the second time).. is that possible or not at all because i upgraded to 1.1.3??

  10. #10
    Rookie Array

    Join Date
    Dec 2007
    Posts
    22
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Default

    Quote Originally Posted by wildbomb View Post
    Just keep trying. Eventually iBrickr will work and you can jailbreak 1.0.2
    After that use the original pacay to activate it so you can use the phone. Install the BSD Subsystem and MobileTerminal, copy the files with iBrickr and try again!

    Wish you luck!
    @wildbomb
    Can you explain details please?
    I downgradet to 1.0.2 jailbreaked with iBrickr i just installed terminal and BSD Susystem through Ibrickr and i set permision 777 to /usr/bin folder and what next ?


 

 
Page 1 of 3 123 LastLast

Similar Threads

  1. update 3g with pwnage 4.1.2 wrong ipsw-file
    By tschensie in forum PwnageTool
    Replies: 7
    Last Post: 10-28-2010, 11:03 PM
  2. Replies: 16
    Last Post: 02-27-2008, 09:28 AM
  3. [1.1.2 OTB] - something went wrong on the bl downgrade
    By duduh in forum iPhone "2G" (Rev. 1)
    Replies: 5
    Last Post: 01-26-2008, 05:35 PM
  4. [1.1.2 (1.1.1 OTB)] update went wrong
    By McMark in forum General
    Replies: 2
    Last Post: 01-25-2008, 05:38 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 04:53 AM.
twitter, follow us!