Page 2 of 6 FirstFirst 123456 LastLast
Results 11 to 20 of 55
Discuss [1.1.4] 04.04.05 Baseband Experiences (Warning!) at the iPhone "2G" (Rev. 1) - Hackint0sh.org; Try this method. ziphone -e ( this will erase the BB). then try the virginizer ...
  1. #11
    Senior Professional Array

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

    Default

    Try this method.

    ziphone -e ( this will erase the BB).
    then try the virginizer stuff.

    It is same steps to get rid of 1.1.3 bb.


  2. #12
    Senior Professional Array

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

    Default

    Quote Originally Posted by lilxvietxboi View Post
    i shouldn't need the new secpack if im on bootloader 3.9
    yes you do you need current version of secpack or higher version of secpack to mess with BB on BL3.9, while 4.6 was accepting only higher version.

  3. #13
    Rookie Array

    Join Date
    Oct 2006
    Posts
    14
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Default

    Quote Originally Posted by ikuwara View Post
    Try this method.

    ziphone -e ( this will erase the BB).
    then try the virginizer stuff.

    It is same steps to get rid of 1.1.3 bb.
    nope, tried that. thanks for the suggestion though.
    T-Mobile iPhone Official Dev Team 1.1.3
    Fully Unlocked, Everything Works
    LIFELINE // OTB111 (Jailbreakme.com w/ anySim 1.1) // 112 (touchFree w/ anySim 1.2.1u) // NateTrue 113 // Dev Team 113

  4. #14
    Senior Professional Array

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

    Default

    You need to have the correct secpack to erase...

    So in order to erase 1.1.4 baseband you need the 1.1.4 secpack...

    this is the same with all versions.
    This is why people brick their communications boards, because they use the wrong secpacks.

  5. #15
    Rookie Array

    Join Date
    Oct 2006
    Posts
    14
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Default

    Quote Originally Posted by nicscoopers View Post
    You need to have the correct secpack to erase...

    So in order to erase 1.1.4 baseband you need the 1.1.4 secpack...

    this is the same with all versions.
    This is why people brick their communications boards, because they use the wrong secpacks.
    How can I tell if I bricked my com board?
    T-Mobile iPhone Official Dev Team 1.1.3
    Fully Unlocked, Everything Works
    LIFELINE // OTB111 (Jailbreakme.com w/ anySim 1.1) // 112 (touchFree w/ anySim 1.2.1u) // NateTrue 113 // Dev Team 113


  6. #16
    Professional Array

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

    Default

    Like everyone is saying, you shouldnt of messed with it if you really dont know what you are doing. If you were unaware that you needed the seckpack from the firmware you are on to delete that firmware, then you realllllly shouldnt have messed with it. This has been the case for all firmwares.
    The difference between 3.9bootloader and 4.6 was the fact that you WERE able to delete the firmware once you had the most up to date seckpack. 4.6 you were obviously not able to for awhile.

    You didnt brick your commboard, it takes more then just running current iEraser or virginizer (which basically uses a lower version seckpack) to brick your comm board.

  7. #17
    Rookie Array

    Join Date
    Oct 2006
    Posts
    14
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Default

    Quote Originally Posted by darkcloudy View Post
    Like everyone is saying, you shouldnt of messed with it if you really dont know what you are doing. If you were unaware that you needed the seckpack from the firmware you are on to delete that firmware, then you realllllly shouldnt have messed with it. This has been the case for all firmwares.
    The difference between 3.9bootloader and 4.6 was the fact that you WERE able to delete the firmware once you had the most up to date seckpack. 4.6 you were obviously not able to for awhile.

    You didnt brick your commboard, it takes more then just running current iEraser or virginizer (which basically uses a lower version seckpack) to brick your comm board.
    I realize that I did not know 100% of what I was doing, but I do know how to read.
    But now I have a better understanding of how the iPhone works. I'll see what I can do with this new information =).
    T-Mobile iPhone Official Dev Team 1.1.3
    Fully Unlocked, Everything Works
    LIFELINE // OTB111 (Jailbreakme.com w/ anySim 1.1) // 112 (touchFree w/ anySim 1.2.1u) // NateTrue 113 // Dev Team 113

  8. #18
    Senior Professional Array

    Join Date
    Aug 2006
    Posts
    204
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    18

    Default

    Just wait the newer seckpak, they probably already have extracted it......
    I am almos sure as they have the key of liberty for now..... If I good understood!

  9. #19
    Rookie Array

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

    Default

    I went through something similar when I tried to repair problems caused by 1.1.3 Soft Upgrade.

    The thing I learned when trying to Restore was that there is a big difference between Recovery Mode (which causes the bad Error 1 message) and DFU mode (which causes the Error 1015 good message). It's all explained on an old thread here:

    http://www.hackint0sh.org/forum/showthread.php?t=27348

    Another thing you need to know is how to kick the iPhone out of Recovery mode (which shows the Connect to iTunes graphic on the phone) when you were not able to achieve DFU mode. I used iJailbreak (mac) and when thing got really tough, I switched to iBrickr (PC). Then try you can put the iPhone into the correct DFU mode (with the black screen) and then restore.

    Once you get the right error 1015 message (sometime you have to restore twice), you can Jailbreak your phone and bring it back to life.

  10. #20
    Senior Professional Array

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

    Default

    Quote Originally Posted by SoLoR View Post
    yes you do you need current version of secpack or higher version of secpack to mess with BB on BL3.9, while 4.6 was accepting only higher version.
    True.

    @lilxvietxboi
    The secpack was available 0day. You need to extract it yourself, though. See here:
    http://www.hackint0sh.org/forum/show...658#post236658
    I probably can't post the secpack on the net, but if you need further help extracting it, just post back here.


 

 
Page 2 of 6 FirstFirst 123456 LastLast

Similar Threads

  1. [3.1 baseband][Warning] Only so many ways to say it!
    By n350z in forum Ultrasn0w (3G(S)/iPhone 4 unlock)
    Replies: 0
    Last Post: 07-01-2009, 08:00 AM
  2. Replies: 5
    Last Post: 06-04-2009, 10:46 PM
  3. [Warning] 2g baseband is back to "original" Restoring to beta 5
    By ArB in forum iOS 3.x (iPhone OS 3.x)
    Replies: 18
    Last Post: 05-16-2009, 02:27 PM
  4. WARNING: 1.1.2 baseband NOT downgradable
    By nabbas in forum General
    Replies: 4
    Last Post: 11-13-2007, 03:39 AM

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 07:55 AM.
twitter, follow us!