I am not an iPhone developer, but the code doesn't seem unreasonable to me.
Can anybody explain what is special about this code?
Found a nice bug in IOS today, bricks your phone and kills the Simulator
11–20 of 35 posts
Re: Found a nice bug in IOS today, bricks your phone and kills the Simulator
#12Earlier quoted context omitted.
More apt would have been that it disables your iphone temporarily until a factory reset or restore is performed. Saying it bricks it causes me to think back to messing up the flashing of firmware on a device and the device never working again.
Yeah, I know. Its to bad though because all the discussions are turning into discussions about the proper use of "bricking".
Well, I'm pretty sure that getting "fscked" is not that bad. I mean, running file-system checks is probably a good idea to do periodically.
Re: Found a nice bug in IOS today, bricks your phone and kills the Simulator
#13Im the original poster, that found the bug. Nah it doesnt brick it, it does however require (atleast on 4.1. for me) a factory reset. The problem seems to be that springboard locks up in an endless loop, restarting the device wont help it because its still loading the offending notification from the cache.
Wait. Is it really an endless loop, or just a queue that is getting filled up faster than it empties resulting in a more DOS-style problem? Because it sounds much more like the second case, in which case not only does it not brick the phone, but it isn't even a bug...
Re: Found a nice bug in IOS today, bricks your phone and kills the Simulator
#14Earlier quoted context omitted.
I'll accept "brick" when recovery requires flashing via JTAG. But not when you just have to press a few buttons.
This is the definition used by people that actually hack hardware, people who are used to performing brain surgery on set-top-boxes and such like. It's not bricked unless unbricking requires a soldering iron or similar, and some JTAG action. These days its getting harder and harder to brick devices, as bootloaders are becoming more and more advanced and more separate from the cores of the devices themselves. Once upo…
Most of the newer SoC chips like Freescale iMX and TI OMAP have the USB core hardware built into the chip, so it's easy to have the chip provide it's own USB bootloader that doesn't require any code out of flash or RAM to get started. The only trick is to make sure the chip can start in this mode when necessary, usually a little helper PIC or some custom gates takes care of that.
Re: Found a nice bug in IOS today, bricks your phone and kills the Simulator
#15Im the original poster, that found the bug. Nah it doesnt brick it, it does however require (atleast on 4.1. for me) a factory reset. The problem seems to be that springboard locks up in an endless loop, restarting the device wont help it because its still loading the offending notification from the cache.
Wait. Is it really an endless loop, or just a queue that is getting filled up faster than it empties resulting in a more DOS-style problem? Because it sounds much more like the second case, in which case not only does it not brick the phone, but it isn't even a bug...
[deleted]
Re: Found a nice bug in IOS today, bricks your phone and kills the Simulator
#16I am not an iPhone developer, but the code doesn't seem unreasonable to me. Can anybody explain what is special about this code?
It's a function that configures ten timers to call itself. So it causes an exponential number of timers to be set.
Re: Found a nice bug in IOS today, bricks your phone and kills the Simulator
#17Im the original poster, that found the bug. Nah it doesnt brick it, it does however require (atleast on 4.1. for me) a factory reset. The problem seems to be that springboard locks up in an endless loop, restarting the device wont help it because its still loading the offending notification from the cache.
Wait. Is it really an endless loop, or just a queue that is getting filled up faster than it empties resulting in a more DOS-style problem? Because it sounds much more like the second case, in which case not only does it not brick the phone, but it isn't even a bug...
OP:Nope, you didnt read the code. Try reading the other version I posted. Works without a loop as well.
Re: Found a nice bug in IOS today, bricks your phone and kills the Simulator
#18I am not an iPhone developer, but the code doesn't seem unreasonable to me. Can anybody explain what is special about this code?
It's a function that configures ten timers to call itself. So it causes an exponential number of timers to be set.
Thats not the bug though. Can do it without a loop as well. This was an old version, check the other one I posted here in this thread.
Re: Found a nice bug in IOS today, bricks your phone and kills the Simulator
#19Also here is a nicer version that still triggers the bug http://www.pastie.org/private/8a48wgmcuuhjjwbupbk3g
So what's the bug then? If there's no loop here?
Re: Found a nice bug in IOS today, bricks your phone and kills the Simulator
#20Earlier quoted context omitted.
It's a function that configures ten timers to call itself. So it causes an exponential number of timers to be set.
Thats not the bug though. Can do it without a loop as well. This was an old version, check the other one I posted here in this thread.
Ok. I would be very grateful for an explanation, then. ;-)