Bootloader vs device drivers

[baniaczek]

Hello. I have a question. May be any of our mastahackers can explain :)

What are the deepest changes of ROM still safe?

As "safe" I understand - I still can start bootloader and recover: start upgrade/downgrade using any of good NBFa and can still use my device?

As "unsafe" I understand "I've got a brick".

As I was able to find - changes of partitions table can be unsafe.

I think, that bootloader doesn't depend on device drivers [for example disk or USB drivers], because I can downgrade to Wm2003 using ActiveSync 3.x, but I'm not sure.

Many thanks in advance. You are fantastic guys :)

[mamaich]

As I was able to find - changes of partitions table can be unsafe.
They are safe. In the worst case I had to reflash WM2003. For BlueAngel unsafe operation is playing with TRUEFFS partitions. The binary partition contains some data, for example BT chip MAC-address. You would not get a brick if you'll destory it, but your MAC would be zeroed (though there is a tool that can rewrite it).
But be careful, theoretically it is possible to force ROM to rewrite bootloader, in this case you'll get a brick.
I think, that bootloader doesn't depend on device drivers [for example disk or USB drivers], because I can downgrade to Wm2003 using ActiveSync 3.x, but I'm not sure.Bootloader is completely independent from OS image. Once I've flushed a garbage into the ROM (incorrectly encrypted NBF file) and still was able to recover.

[baniaczek]

Many, many thanks :)

[tsiros]

But... how does one use the bootloader? i mean... i got my 9100, CID unlocked and flashed with the 'official' 2.8.7.1 rom... then i make the activesync connection... then i go into RAPI mode and run the "enterbootloader.exe" i see in the \windows folder (heh, handy)

and... then? what do i do? :/