1. 2k1's Avatar
    There wont be a jailbreak for it for a while i would expect not to see one till late decemeber early next year for it
    That's fine no rush I'll have fun with the iPhone 5
    2012-09-15 04:17 AM
  2. Cowboy's Avatar
    I dont really have a reason to jailbreak other than theming and killbackgrounder
    2012-09-15 04:19 AM
  3. Simon's Avatar
    Anyone have a clue how to check an ATT order? Got my confirmation number but when I try to check online it asks to link to an account. Which then asks for wireless number, problem is I dont have one yet.
    2012-09-15 04:21 AM
  4. Cowboy's Avatar
    https://www.att.com/eos/unauth/eosLo...tType=wireless
    on the left drop down box where it says wireless number change it to say order number
    2012-09-15 04:27 AM
  5. Simon's Avatar
    https://www.att.com/eos/unauth/eosLo...tType=wireless
    on the left drop down box where it says wireless number change it to say order number
    Ya, been to that screen, changed it to order number and put in order number but clicking the box doesnt do anything, the box itself is kinda greyed out (well blue but you know what I mean).
    2012-09-15 04:30 AM
  6. Cowboy's Avatar
    i Just did it with out putting in a wireless number
    2012-09-15 04:31 AM
  7. Simon's Avatar
    i Just did it with out putting in a wireless number
    Had to use firefox to do it. Wasnt working in chrome. Order says it has been cancelled
    2012-09-15 04:34 AM
  8. Bo Troxell's Avatar
    Had to use firefox to do it. Wasnt working in chrome. Order says it has been cancelled
    Wut? Cancelled.

    I'll bet the jailbreak is out way before December, it's already there (tethered), just waiting to see what Apple does with the OS6.
    smaller sig.png
    2012-09-15 05:48 AM
  9. Simon's Avatar
    Ya sucks, that one was for one of my friends here. Probably got cancelled cause I tried to use my passport number as a social security number. Oh well. My UK order is still good though. That order is prepared for shipment status already
    2012-09-15 05:51 AM
  10. Cowboy's Avatar
    Wut? Cancelled.

    I'll bet the jailbreak is out way before December, it's already there (tethered), just waiting to see what Apple does with the OS6.
    But is more than just breaking down the OS they have a new chip as well with the A6.

    I am sure Orby can explain in higher details then I can.
    2012-09-15 06:07 AM
  11. Orby's Avatar
    But is more than just breaking down the OS they have a new chip as well with the A6.

    I am sure Orby can explain in higher details then I can.
    Tag-team!

    /tag

    Let's start with a what a jailbreak is, in its purest essence. A jailbreak mounts the filesystem as fully writable and patches all sorts of integrity checks out of the kernel, thereby allowing any program or process the user wants to run on the device to actually run. Merely trying to write these patches to the kernel will fail due to the kernel's integrity checks that prevent exactly this sort of thing.

    Therefore, you either have to find a way that allows you to write unsigned code to the kernel's privileged areas. This can be done by finding a way in the operating system to write that code without breaking the checks, or finding an exploit further up the "chain of trust" (e.g., blackra1n, an exploit in iBoot was used that will allow an unsigned kernel to boot, or 24kpwn, an exploit in LLB that allowed both an unsigned iBoot and kernel to run) to ignore, bypass, or fabricate the integrity checks on the kernel.

    Kernel-level "userland" exploits are usually present in most or all devices on a particular iteration of an operating system. They are very easy to patch from Apple's perspective, but generally speaking, such exploits are more plentiful, as there's a whole lot of code to work with in the userland. As a general rule of thumb, the more raw code and processes there are in a system, bugs present in the system increase proportionally. With more bugs present, the chances of one or more of those bugs being vulnerable to our machinations increase.

    iBoot-level exploits are usually also present in most or all devices on a particular version of iBoot (which changes less frequently than every OS revision, usually). They are still patchable by Apple, but are a tougher task to patch a hole out while making sure all function is retained and operates wholly bug-free. There's less code here, so bugs and therefore exploits are probably less frequently appearing, but an exploit here can be considered "more valuable" due to the fact you can have your way with the kernel at this stage, and you have access to more system hardware functions not available to the kernel.

    "Bootrom" exploits are in very low-level code that overwrite or disrupt the hardware-based function of the device. Such exploits are very rare (there are a grand total of five for all iOS devices) and very specific for a particular processor or device. These exploits are worth their weight in gold, as Apple cannot patch them at all on a device already made, and they allow for all sorts of integrity-flouting code mayhem. However, as the bootrom is incredibly bare-bones in its functionality, bugs and thus exploits are, as noted, damn rare.

    iOS 6, the current version of iBoot, and the iPhone 5's bootrom, probably have no known exploits in them--and thus all work for a jailbreak on that combination is probably starting from scratch.
    2012-09-15 06:53 AM
  12. catstide's Avatar
    Wow! good info....thanks!
    2012-09-15 07:09 AM
  13. Cowboy's Avatar
    Tag-team!

    /tag

    Let's start with a what a jailbreak is, in its purest essence. A jailbreak mounts the filesystem as fully writable and patches all sorts of integrity checks out of the kernel, thereby allowing any program or process the user wants to run on the device to actually run. Merely trying to write these patches to the kernel will fail due to the kernel's integrity checks that prevent exactly this sort of thing.

    Therefore, you either have to find a way that allows you to write unsigned code to the kernel's privileged areas. This can be done by finding a way in the operating system to write that code without breaking the checks, or finding an exploit further up the "chain of trust" (e.g., blackra1n, an exploit in iBoot was used that will allow an unsigned kernel to boot, or 24kpwn, an exploit in LLB that allowed both an unsigned iBoot and kernel to run) to ignore, bypass, or fabricate the integrity checks on the kernel.

    Kernel-level "userland" exploits are usually present in most or all devices on a particular iteration of an operating system. They are very easy to patch from Apple's perspective, but generally speaking, such exploits are more plentiful, as there's a whole lot of code to work with in the userland. As a general rule of thumb, the more raw code and processes there are in a system, bugs present in the system increase proportionally. With more bugs present, the chances of one or more of those bugs being vulnerable to our machinations increase.

    iBoot-level exploits are usually also present in most or all devices on a particular version of iBoot (which changes less frequently than every OS revision, usually). They are still patchable by Apple, but are a tougher task to patch a hole out while making sure all function is retained and operates wholly bug-free. There's less code here, so bugs and therefore exploits are probably less frequently appearing, but an exploit here can be considered "more valuable" due to the fact you can have your way with the kernel at this stage, and you have access to more system hardware functions not available to the kernel.

    "Bootrom" exploits are in very low-level code that overwrite or disrupt the hardware-based function of the device. Such exploits are very rare (there are a grand total of five for all iOS devices) and very specific for a particular processor or device. These exploits are worth their weight in gold, as Apple cannot patch them at all on a device already made, and they allow for all sorts of integrity-flouting code mayhem. However, as the bootrom is incredibly bare-bones in its functionality, bugs and thus exploits are, as noted, damn rare.

    iOS 6, the current version of iBoot, and the iPhone 5's bootrom, probably have no known exploits in them--and thus all work for a jailbreak on that combination is probably starting from scratch.
    Yup what he said.
    Thanks partner!
    Learned a few new things myself.
    2012-09-15 07:36 AM
  14. Cer0's Avatar
    Yea I don't think Dinosaurs was aimed at younger kids or even tweens. Or we just had messed up shows growing up. Alchol promotion and this episode tonight had them watching some game show talking about how the blind dates went and she complained about the guy and the host says let's ask gary how the night went. The camera pans and all you see is him dangling like he hung himself.
    ________________
    The new LittleSnitch seems like great improvement over the already awesome app.
    Last edited by Cer0; 2012-09-15 at 09:56 AM.
    [CENTER][SIGPIC][/SIGPIC][/CENTER]
    2012-09-15 09:38 AM
  15. Saved0ne's Avatar
    Haha one of my topics made it to the main page of the MMi app
    2012-09-15 08:48 PM
  16. Anonymous's Avatar
    With iOS 6 right around the corner, will you guys be waiting for a jailbreak or upgrading right away? I'm thinking about just upgrading right away.
    2012-09-16 10:18 PM
  17. 2k1's Avatar
    I'll be Gitting the new phone so I'll have this to mess with jailbreak tweaks and other for just phone until they come out with one.
    2012-09-16 10:30 PM
  18. Anonymous's Avatar
    I'll be Gitting the new phone so I'll have this to mess with jailbreak tweaks and other for just phone until they come out with one.
    I gotcha. I have my 3GS (old bootrom) which is "always" jailbreakable, and my 4S, which is my primary iDevice.
    2012-09-16 10:37 PM
  19. 2k1's Avatar
    Same here
    2012-09-16 10:50 PM
  20. Cowboy's Avatar
    So I am on a one week vacation. Went into work work twice already and now the honeydew list
    Attached Thumbnails The randomly off topic thread-imageuploadedbymodmyi1347836909.739633.jpg  
    2012-09-17 02:08 AM
LINK TO POST COPIED TO CLIPBOARD