1) launchctl, ok
2) ienew, lost wi-fi, continued on mobileterminal
4) iunew, ok
5) bbupdater -v, failed
6) lost wi-fi, repair needed
7) tried various methods for fixing baseband
8) tried ALL firmwares: 100, 102, 111, 112 and even 113 - all said no-wifi, repair needed

Any suggestions?

I think you will need to follow the instructions in this post to gain access to your phone and then:

1. See if your bootloader downgrade was successful.
2. If you are on 3.9BL, then attempt to use bbupdater to load the baseband.
3. If you are still on 4.6BL, then reattempt the downgrade.

Hope that helps! It seems somewhat hit or miss for people depending on where the failure occurred in the process.

how to check bootloader, when bbupdater -v times out?

Are you unloading the commcenter.plist first?

If it is still timing out, I would consider repeating the unlock process - perhaps you had the bad nor file the first time.

I am now on 102, but when I try to run iunew it says: "Did you erase your flash first?", however bbupdater -v still says that "baseband unresponsive to pinging".
Is this because I upgraded to 113?

Edit: forgot to mention thet ienew stays at "Waiting for data..."

Originally Posted by bbad

Is this because I upgraded to 113?

jes this is because you updated to 1.1.3 - now you are stuck on new baseband with 4.6 bootloader (Wait for 1.1.4 now)

I've the same problem but i don't upgrade to 1.1.3. I try everything but i've the same error.

bbupdater -v "baseband unresponsive to pinging"
bbupdater -e 03.14.08_G.eep -f 03.14.08_G.fls "Error Baseband bootloader is too old update to 1.8..."

Idon't know to do.

But interesting thing is that after upgrading to 113, I still had "Repair needed" message. Maybe this means, that I screwed communication board, during testpointing?

This thread fixed my problem: http://www.hackint0sh.org/forum/showthread.php?t=24095
it should be sticky.

thanks wildbomb