so obviously, it is possible to damage your iphone running software only
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.
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.
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.
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
The packaged included secpack, ieraser, bbupdater etc...
How could it be an "badly extracted secpack".
Just ran ieraser and that's it.
We're off-topic to this current thread.Quote:
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.
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"
- 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.
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.
So what's the veridict? Are we stuck with the 1011 Error for good?
You talked about boot loader, not BB boot loader... It's okay to be wrong you know from time to time...
Hold on, come out of your high-horse and stop patronising people.Quote:
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.
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
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.Quote:
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.
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.