Have you try it on 1.0.2 yet? Could you downgrade to 1.0.2?
Try on 1.1.1 too if you can or even 1.1.2.

When running it, i get some of the text, and after opened dev lalala i get

Can't write

Hi i'm looking for someone who could help me in Madrid to do the testpoint...

Thanks

I succesfully unbricked my bricked error 1011 iPhone!

Here is my story:

In the first week of April, I bought an iPhone 16 GB in the United States and I unlocked it succesfully with iLiberty+. When I was back in Europe I heard the first version of the Pwnage tool was released. I experimented with it and neutered my bootloader with the Bootneuter.app.
But, I experimented way too much, while flashing my bootloader to the original condition (non-fakeblanked, non-neutered), it went completely wrong: I pushed the homebutton by accident and so I interrupted the flashing process.

My iPhone was bricked, no sound, no network, no wifi, repair needed,... and error 1011 after every firmware restore in Itunes.

I tried every software solution, I put my iPhone in the freezer,... nothing helped. So my only hope was the A17 testpoint method. This brought my iPhone back to live!

This is what I did:

0) I had an iPhone 16 GB OTB firmware 1.1.4 with error 1011 because I interrupted the Bootneuter flashing proces.

1) DFU restore to firmware 1.1.4 and got error 1011
2) Followed the tutorial of NewWayAround starting at step 2 till step 10.
3) I have to admit I cutted the antenna cable while opening the iPhone, but I ordered a new one at cnn.cn and replaced it.
4) I pwned my iPhone with WinPwn 2 and restored the custom 2.0 firmware with Itunes 7.7
5) I have now a fully working iPhone 16 GB with firmware 2.0

Originally Posted by virtona

I succesfully unbricked my bricked error 1011 iPhone!

Congratulations!

Did you have the "waiting for data" and "Spamming AT" problems. If so, how did you get past them. When I try to use ienew I get "waiting for data" and with iunew I get "Spamming AT". Or maybe it was different for you and when you executed iunew, it just asked you to connect testpoints? Thanks

Originally Posted by DarkRival

Congratulations!

Did you have the "waiting for data" and "Spamming AT" problems. If so, how did you get past them. When I try to use ienew I get "waiting for data" and with iunew I get "Spamming AT". Or maybe it was different for you and when you executed iunew, it just asked you to connect testpoints? Thanks

If you get "waiting for data" with ienew that's OK.
I didn't got "Spamming AT" with iunew, but there should be a solution for "Spamming AT" somewhere.
On my iPhone, iunew just asked to connect the testpoint. But, I tried connecting the testpoints several times before I got "TESTPOINT WORKS: 55" A magnifying glass is a must!

Congrats virtona... i'll follow MyWayAround's method and do the testpoint myself... scary scary mosnter... but i get a 1600 error with 1.1.1, 1.1.2, 1.1.4 firmwares...

help!!!!

Originally Posted by sndsep

Congrats virtona... i'll follow MyWayAround's method and do the testpoint myself... scary scary mosnter... but i get a 1600 error with 1.1.1, 1.1.2, 1.1.4 firmwares...

help!!!!

If you are on fw 2.0 you need to reinstall itunes 7.5 to restore to 114 or below

Thanks MickieF.... i didn't realize that my other iphone is running 2.0 pwned so my itunes version is 7.7... i'll try on another computer... thanks again

Originally Posted by virtona

My iPhone was bricked, no sound, no network, no wifi, repair needed,... and error 1011 after every firmware restore in Itunes.

I tried every software solution, I put my iPhone in the freezer,... nothing helped. So my only hope was the A17 testpoint method. This brought my iPhone back to live!

This has just been confirmed by the people form the Linux on the iPhone project.
In this post (where they differenciate 2 bootloaders), a comment previously made on the no IMEI, ICCID, BT, WF issue was adressed:

... asked me about "bootloader corruption" as it pertains to basebands. As I said earlier, the bootloader I am talking about is on the S5L8900. The baseband/commboard has its own bootloader and its own non-volatile memory (also NOR flash, probably the same bit of flash its bootloader and firmware sits on too). The recovery mechanism on the baseband is far less robust than the one on the S5L8900. The only sure way seems to be using that hardware testpoint to force it to accept a new bootloader, and even that can be defeated by carefully crafting the NOR contents. In other words, it sucks.

In addition, a lot of the problem is due to bad software overwriting the seczone with bad data, stuff that's unique to your phone. Therefore, information is irretrievably lost and there may not be a way to recover.

So, apparently the only solution is the one virtona used: tespoint method.
How is this working for those of you with the same problem?