Originally Posted by sam

There is no way to damage your phone with the sw unlock, you can just mess it up and have to restore in a "funny" process, but that happens if someone plays around with the wrong toys too much. It's life.

Just running ierase managed to totally screwed up my iphone which can't be restored now (error 1011)...
so obviously, it is possible to damage your iphone running software only

Originally Posted by jyavenard

Just running ierase managed to totally screwed up my iphone which can't be restored now (error 1011)...
so obviously, it is possible to damage your iphone running software only

To reproduce your problem you must have doen something else before. iEraser can as any sw solution ONLY delete the firmware of the phone. If you caused other damage you must have done somthing wrong (i.e used SecPack of a higher versions bl or similar). It's not possible to damage a phone another way. As iEraser requires no user made data we can assure you it won't cause you such problems.

Originally Posted by pendalf

a lot of guys respond many problems to run anysim even on brand new iPhones
and i don´t see any reaction from the dev team!

what is going on?

It's goign on that you shoudl update your firmware to 1.0.2 or 1.0.0 from package before you do osmthng or the alignment in your NOR might be wrong. Thats been said before and is content in numerous guides.
Another bunch of error is simply caused by not reading but just blind doing something and than moan afterwards. The application itself is easy as it could be just a bit of "sense" is required.
Also DON'T use it just for fun on your already unlocked phone, thats the same way bad or be unhapyp if you done strange things to your bb before.
Basicly all things you can usaly expect of a user. All tests we made were successful and it have been plenty. For any phone with a retial fw of a update package + anysim it worked so far in our test.
More we can seriously not do but just hope enough user are happy they now can unlock their phone the most easy, free way.

Originally Posted by sam

To reproduce your problem you must have doen something else before. iEraser can as any sw solution ONLY delete the firmware of the phone. If you caused other damage you must have done somthing wrong (i.e used SecPack of a higher versions bl or similar). It's not possible to damage a phone another way. As iEraser requires no user made data we can assure you it won't cause you such problems.

Nope, I was about to to a hardware upgrade (needle version posted here as a sticky). But before doing that I wanted to trial the different steps.
So I loaded all the tools on the phone, unloaded the commcenter, than ran ieraser to see what it would do (yes, I know silly me). I followed all the steps until ieraser.
Then I turned off the phone.

When I turned it back on, no wifi, no sound, no SIM card recognised. And a restore in iTunes would always give me a 1011 error.

I am 100% of the steps I've taken... I didn't run any other commands than the one mentioned in the needle guide, except that I didn't even open the phone.

I haven't been able to reflash my phone since.

Jean-Yves

Well you eraser your Baseband and rebootet. teh bootlaoder shall stille exist. Boot your Phone into recovery mode (home + powerbutton) and plug it to iTunes if it shows the triangle warn sign.

Originally Posted by sam

Well you eraser your Baseband and rebootet. teh bootlaoder shall stille exist. Boot your Phone into recovery mode (home + powerbutton) and plug it to iTunes if it shows the triangle warn sign.

You haven't read my message properly. You seem to assume that I do not know what I'm doing nor what have been tried.

When trying to restore with itunes, it will always fail with an error 1011. You just can not reflash the baseband anymore.
There are a lot of people in the same situation as me... It always happened after running a software command and rebooting straight after (the information about not rebooting the iphone after running ieraser was only found *after* people had problem, it was too late back then).

When trying to run manually bbupdater, it will fail after 10 attempts and a message that the bootloader has to be version 1.0.

So saying you can't damage your iphone by running software it very incorrect.

It looks to me that the baseband bootloader got corrupted somehow and you can't flash it anymore

Jean-Yves

Originally Posted by jyavenard

You haven't read my message properly. You seem to assume that I do not know what I'm doing nor what have been tried.

I assume you use a secpack extractes badly, possibly a stage 0 one and blow your bootloader. thats not a mistake of the author of the software you used.

Originally Posted by jyavenard

[...]
There are a lot of people in the same situation as me... It always happened after running a software command and rebooting straight after (the information about not rebooting the iphone after running ieraser was only found *after* people had problem, it was too late back then).
[...]

If my assumtion from above is correct (the secpack used by iEraser and co. simply don't allow to write in areas below 0x20000 and are save) it's a problem on user side. With anySIM we have excluded this and similar problem cases by NOT allow user input anymore.

Originally Posted by sam

I assume you use a secpack extractes badly, possibly a stage 0 one and blow your bootloader. thats not a mistake of the author of the software you used.

It was using the package provided here and succesfully used by other people.
The packaged included secpack, ieraser, bbupdater etc...
How could it be an "badly extracted secpack".

Just ran ieraser and that's it.

If my assumtion from above is correct (the secpack used by iEraser and co. simply don't allow to write in areas below 0x20000 and are save) it's a problem on user side. With anySIM we have excluded this and similar problem cases by NOT allow user input anymore.

We're off-topic to this current thread.
But are you saying that it should be possible to reprogram the bootloader provided ieraser (or bbupdater) could access areas below 0x20000?
By bootloader I guess you mean the baseband bootloader, as my iphone has no problem to start. Just no wifi, no sim access etc.

It is unfortunate that you make your opinion so quickly and refuse to see different side of things...
You've discarded the possibility with a "it's not possible" and bang, you just refuse to admit that it may not be the case.
You wouldn't read so many people with a 1011 error during a restore if it just "not possible"

Originally Posted by jyavenard

It was using the package provided here and succesfully used by other people.

First problems:
- package was provided by third party, we removed it cause it violates copyright to include firmware
- there canbe problems using other people's packs, that's why anysim produces all needed info of your phones baseband.

Originally Posted by jyavenard

The packaged included secpack, ieraser, bbupdater etc...
How could it be an "badly extracted secpack".

Many reasons. Secpack contains a section to erase the bootlaoder for reflash if it indicates a higher version, so using a secpack of 102 firmware on a 102 factory firm of earlier build or even 100 can follow up by undesireable results liek destroied bootlaoder.
anySIM takes all this things away from user as it seems to god given that lot of people get stroke by their lazieness to use prepacked stuff possibly not suiteable for their phone in the hope it will somehow work -> means stop complain on the tools, it's not the tool makign things bad it's the user most of the time.
Now, tools are pretty much advanced but it was specificly said that one should give the tool secpack extracted of the version owns fw fls as geo published ieraser.

Originally Posted by jyavenard

Just ran ieraser and that's it.

Exactly.

Originally Posted by jyavenard

We're off-topic to this current thread.
But are you saying that it should be possible to reprogram the bootloader provided ieraser (or bbupdater) could access areas below 0x20000?

Usalyl not, if you use the CORRECT secpack, it's impossible. Altering the secpack is also impossible cause it's signed.

Originally Posted by jyavenard

By bootloader I guess you mean the baseband bootloader, as my iphone has no problem to start. Just no wifi, no sim access etc.

BB bootloader has nothing to do with the phone system starting, I really suggest reading things up before do a complain orgy here. This forum has a really useful search function btw.

Originally Posted by jyavenard

It is unfortunate that you make your opinion so quickly and refuse to see different side of things...
You've discarded the possibility with a "it's not possible" and bang, you just refuse to admit that it may not be the case.

No I know the system, you obviously don't even know the approx. background of things but come here and want to tell me what is possible or not. If one has no clue I suggest just stfu. I don't say this often but exactly such posts are why one shouldn't give out any infos anymore to the public. Maybe go unlock your phone yourself next time.

Originally Posted by jyavenard

You wouldn't read so many people with a 1011 error during a restore if it just "not possible"

I have talsk to serval of them and all used the illegal prepacked package with the wrong secpack and blow themself up. Before doing things liek flashing around on firmware it's advised to read at least the basics on what you do, especially if using a hack in such a early stage.

So what's the veridict? Are we stuck with the 1011 Error for good?

Originally Posted by sam

["BB bootloader has nothing to do with the phone system starting, I really suggest reading things up before do a complain orgy here. This forum has a really useful search function btw."]

This is exactly what I had been saying. I was just re-confirming it. Please read!
You talked about boot loader, not BB boot loader... It's okay to be wrong you know from time to time...

No I know the system, you obviously don't even know the approx. background of things but come here and want to tell me what is possible or not. If one has no clue I suggest just stfu. I don't say this often but exactly such posts are why one shouldn't give out any infos anymore to the public. Maybe go unlock your phone yourself next time.

Hold on, come out of your high-horse and stop patronising people.
I have probably done more work on firmware, mobile phones and other embedded device than you have. This is what I've been doing for a living for over 12 years.

Now that the phone has been screwed up, weither be a *user* fault or a *tool* fault is irrelevant. The result would have been the same.

So people can't damage their phone using *official* software unless they don't use it properly.
All I am looking for is for a solution on how to fix this problem

I have talsk to serval of them and all used the illegal prepacked package with the wrong secpack and blow themself up. Before doing things liek flashing around on firmware it's advised to read at least the basics on what you do, especially if using a hack in such a early stage.

The package used to create the 1011 was a *sticky* for over 2 weeks, made sticky by yourself I presume. This makes it official enough for me.

Do you think that there is a solution to the problem or not?
Saying "you used the wrong secpack", "it's your fault" etc... doesn't help much.