Bootneuter allows to flash the bootloader from the iphone itself (no DFU, no external program). Amazing, but ...

If the program (bootneuter) crashes during the flashing process or if some other process on the iphone hangs completely the iphone and I have to reboot the phone before the flashing is complete, is my iphone definitely a brick?

The potential is there. Same is true with gunlocker, iLiberty+, and ziphone when they flash the bootloader. Of all of them, though, ziphone has the most potential to crash because its running from a disintegrating ramdisk.

With the others though, the system as a whole is stable. So don't interrupt the process. Let BootNeuter do its thing...it only needs to do it that once Keep your finger away from the home key, and don't do it when you have 1% battery remaining.

what about the old "set auto-lock to never"-issue? will bootneuter do this for you? does it affect the upgrading /flashing process?

Auto-lock doesn't interrupt BootNeuter. If set to 1 minute you'll see it lock but after you slide the slider you'll see BootNeuter is still doing its thing. Just don't power off or hold down the home key.

It's the same issue when you update the BIOS on your PC, or even when you apply certain firmware changes on Macs. If you interrupt that process at just the wrong time, you have the potential to "brick" your PC or Mac (there was a recent macbook keyboard firmware update with this kind of warning).

Originally Posted by MuscleNerd

The potential is there. Same is true with gunlocker, iLiberty+, and ziphone when they flash the bootloader. Of all of them, though, ziphone has the most potential to crash because its running from a disintegrating ramdisk.

With the others though, the system as a whole is stable. So don't interrupt the process. Let BootNeuter do its thing...it only needs to do it that once Keep your finger away from the home key, and don't do it when you have 1% battery remaining.

I agree with you, but there is a substantial difference; bootneuter runs on the iphone whereas the others methods run on the external computer. Let us suppose that a buggy program has been installed on the iphone and crashes it (well I suppose program on iphone crashes more often than programs on Macs :p) during a flash of the bootloader (not just after pwnage, where there is no potential software installed and running), well bang, the iphone is transmuted into a brick. Am i right?

I'd say it was safer on the iPhone

If your running a flashing program from a desktop ( not a laptop ) and it loses power ! You're in trouble.

As programs cant really run in the background - i'd just restart the iPhone before you do anything and then it will be clean

Would airplane mode make this operation a little safer?

While running iPlus a while ago, I got an incoming call, that really scared me!!!

Why not just call forwarding

Originally Posted by iFeun

Would airplane mode make this operation a little safer?

While running iPlus a while ago, I got an incoming call, that really scared me!!!

BootNeuter sets airplane mode. That's why it refuses to run if CommCenter isn't running...because CommCenter needs to be running to enable airplane mode.

That was one of the primary safeguards in BootNeuter actually....enabling airplane mode.

Originally Posted by potaman75

I agree with you, but there is a substantial difference; bootneuter runs on the iphone whereas the others methods run on the external computer.

No, actually all methods run on the iphone. Only via the /dev/tty.baseband and /dev/tty.debug interfaces on the iPhone itself can you interact with the bootloader.

ziphone runs gunlocker inside a disintegrating ramdisk environment where every malloc() you do eats into your ramdisk filesystem. iLiberty+ does it safely by running gunlocker on iphone as secondary payload. iNdependence wisely avoids the issue and doesn't change the bootloader. gunlocker itself is meant to run from a normal stable environment. pwnage runs inside a stable environment like iLiberty+ and gunlocker where malloc()s don't risk corruption of the filesystem you're running from.