QUOTE(theevilhacker63 @ Aug 12 2009, 09:59 PM)

that's exactly what I was thinking if your booting off a completely different nand chip then why does the new update make it all magically not work? unless the update changes how stuff is initialized but I still don't see how that would be since it's all stored in flash..??
unless I'm all wrong on this unless there only talking about consoles with only one nand chip which is the majority of consoles out there since this new Cygnos v2 chip just came out. but still if you have that it should be safe to update to the new dash and still be able to run this hack...right?
This is the question of the day, we are still asking this amongst ourselves and not quite sure on the answer. Since 2BL is in the NAND, and you can add a second (or more!) NAND via either Cygnos or an XD card mod, it would seem that you can have a completely functional dual-boot setup, including access to live. I'm not completely sure on this, but it seems plausible. (IMG:
style_emoticons/default/biggrin.gif)
QUOTE(Mhawk134 @ Aug 12 2009, 10:05 PM)

Because the new update rewrites the bootloader. And that fixes this exploit. The bootloader is most likely not updated in all the updates. And in the latest update is when they patched the exploit that they are using.
Hawk
Bootloader = 2BL = in the NAND
The problem would be running a second kernel, since you would need CPU key, which you cant get if you already updated to 849x. However, if you wait until this hack is completely released, and get your cpu key + a second NAND, you should be able to have a dual-kernel setup. (IMG:
style_emoticons/default/smile.gif)