[Galaxy S Plus I9001 Android Development] skywalker01:
Well, that's completely impossible because these are the very same progs. And you can even check this yourself by byte comparing (fc /b with DOS for example) the two exe files inside these archives. You will find that they not only have the same size but other date and filename but actually they are completely identical to the very last bit ;-)

I still guess that your problems and those of others while flashing derive from a partly broken/incomplete flash. I don't know if this is also true for YardE because he is the only one who really "messed" with critical ROM settings so it rather seems that his failed flash is the only software related brick IMHO.

So what can be the "hardware" reasons for the "broken" flash and the resulting brick ?

From my experience as an IT professional I can tell you numerous reasons and examples, even very rare and exotic ones, so I just stick to a few of them:

- the main reason is mostly a partially or completetly interrupted data stream either while flashing or even before that namely when copying the flashfile

- this can be for example due to corrupt cables or instable connections/plugs

- this can also be due to short circuits and even voltage fluctuations either somewhere in your system where the data stream passes by - and there are a lot of components involved - or in the power supply of your device or even before that somewhere in your power line.

But these causes are extremely technical and scientific and further explanantion would be rather boring and hard to understand for the majority. For those who want to learn more about it: in computer science this is called side effect when it shows up in coding, but similar effects can also happen even on the lowest hardware layer. Due to voltage fluctuations and tolerances in the electronic components there is always a slight chance of an undefined electrical state which can lead to unforeseen side effects on the upper layers of hardware and therefore also in software in the end. This electronic effect is similar to the digital cliff effect on software level, but you can lookup all of these on wiki if you are really interested ;-)

- other parts of the hardware also may have unstable states sometimes, i will give now two examples, one for this cause and one for the first cause

1. I have a customer who had some bad files on his external harddisk which he noticed some weeks later after copying these files when he wanted to unpack a zip archive. It showed that only very few files were corrupted and I have analyzed that only one single bit was different from the original file. But this made the file useless as it couldn't be uncompressed. It turned out that the reason for these file corruptions was obviously a corrupt USB cable which very rarely but constantly produced this failure. It was impossible to measure the defect of the cable by any means, only the long term testing of the harddisk and different cables showed that indirectly. This is a problem that most people - even IT experts - will seldom find although it is a rather common one. Even this very same customer had this problem twice in about 5 years and it definitely were two different USB cables, I disposed the first one personally years ago ;-)

Another customer had the same problem but this time it wasn't the cable but his SATA-to-USB-Adapter.

2. I flashed a WD media player some months ago with a new firmware and after that everything worked fine except that movie sheets just were not displayed at all. Neither in the menu nor on the selection page. Naming and contents of files were OK, even in picture mode the sheets could be normally displayed one by one as single pictures. There was no error message while flashing and no other indication that something went wrong because everything else functioned perfectly. As a last resort I flashed an older firmware and that one worked completely fine. So I tried an reflash with the latest firmware again and this time everything worked until now.

So it can happen that a flash is not completely successful although you made no mistake and there was no error message at all. And actually this error is not so uncommon as you might think or even wish.

So this is also a main reason why it says everywhere and over and over again: flashing may brick your phone, don't do it when you can't live with the potential consequences.

And one more remark: this is also what divides the pros from the n00bs. A pro like YardE would never discuss or even complain about the brick but just curse himself and the damn hardware. And then he will try to get it fixed as soon as possible. And that's the way it always should be. Nevertheless my deep regret to YardE that he had this bad luck with his phone, something like this even happens to the best :-(

But I will try to give my best and support you in testing the CM port when your phone is up and running again.

Well, I don't need to mention what the noobish style is when they brick their phone, do I ?

Just wanted to explain to perzonator and others what some technical reasons for that could be (notice that the list is incomplete !) and that this can happen to everyone, so you are absolutely right there, perzonator. In your case I think you had a (partially) broken flash with the bootloader part and my regrets go also to you of course. Hope you learned at least some technical reasons why this could have happened.