Will our 5.1.1 blobs be useful to redo jailbreak?

[stlmac08]

Originally Posted by Yumraaj

Have you not been reading what already posted??? Your query has been answered already.

Anyway just to recap:
Yes you can restore/downgrade even if apple has stopped signing but it will update to the latest firmware first then downgrade.

So make sure you don't rely on software/sim interposed unlock as it will upgrade your baseband.

I saw what you just stated in my reading, but have a concern about that detail. Isn't it possible that Apple can do something in the next upgrade, so that the downgrade tool is foiled when it updates to (future) current version and then tries to go back to 5.1.1 and find itself unable? Or does the manner in which the tool is implemented make the downgrade a sure thing, from any future iOS version? And I am aware of the unlock risk, but for this question, I am merely exploring how safe our option to go back to 5.1.1 really is (say for an ipad 2 or ipad 3 wifi)?

[stlmac08]

Originally Posted by stlmac08

I saw what you just stated in my reading, but have a concern about that detail. Isn't it possible that Apple can do something in the next upgrade, so that the downgrade tool is foiled when it updates to (future) current version and then tries to go back to 5.1.1 and find itself unable? Or does the manner in which the tool is implemented make the downgrade a sure thing, from any future iOS version? And I am aware of the unlock risk, but for this question, I am merely exploring how safe our option to go back to 5.1.1 really is (say for an ipad 2 or ipad 3 wifi)?

Any comment?

[spawn]

im curious too..i have the new ipad with shsh 5.1.1 saved. was wondering if it is still possible to downgrade or restore to 5.1.1 once apple has stop signing for it.

[uaelaelil]

Another way to put the question is would you be able to update to 5.1.1
Using redsnow and choose not downgrade to 5.0.1 on A5 devices

With saved blobs that is

[stlmac08]

Originally Posted by uaelaelil

Another way to put the question is would you be able to update to 5.1.1
Using redsnow and choose not downgrade to 5.0.1 on A5 devices

With saved blobs that is

The concern is that Redsnow installs an outdated iOS 5.x by first updating to the current version, and then uses an exploit in the restore ramdisk to put the outdated target version in place.

When current is past 5.1.1 and 5.1.1 is outdated, the ramdisk may not be the same anymore. If the tool goes and puts a post 5.1.1 version to start, it may break down when moving to the next step of installing a jailbreakeable 5.x such as 5.1.1 or 5.0.1.

If the ramdisk is secured post 5.1.1, I see there could be hope for those with A5 devices needing a restore and jailbreak after Apples stops signing 5.1.1, if they are able to restore their device to 4.3.3 with that version's blobs, in two ways:

1) The hackers may revise the tool to work by first restoring to 4.3.3 (with blobs) and then to the 5.1.1 or 5.0.1 of the user's choice also with blobs, if 4.3.3 had the ramdisk exploit, but versions beyond 5.1.1 do not have it.

2) If not, the only other recourse for such people is to install 4.3.3, and jailbreak with jailbreakme.com (which I hope will be maintained as a fallback)

[hbhbhb]

Apple can never stop old IOS with blobs, so chill out
Whatever comes as new like IOS6, will be dealt with accordingly


so lemme recap all.
Booooooooooooooooooooooobs all the way for now, ohhh blobs or whateva, nomsayin

[stlmac08]

Originally Posted by hbhbhb

Apple can never stop old IOS with blobs, so chill out

What you say is correct for iOS 4 on all devices and I think iOS 5 on A4 devices. But, the ability to restore outdated iOS 5 versions on A5 devices is still an open concern the way I see it. See my posts above and read them carefully.

[l0k0]

5.1.2 is set to release within the next week. Pretty sure Apple has fixed the JB and also the downgrade of A5 devices via RedSnow. A4 devices are still in the clear because of the limera1n exploit, so these can easily be downgraded via stitched firmware. And of course 5.1.2 will be tethered for all A4 devices, A5 isn't going to be so lucky (for the moment).

PS: Someone mentioned iPad2 and preserving baseband. Why would u want to preserve baseband when the iPads are factory unlocked anyways. Baseband preservation is long past dead and is useless to anyone except those on iP4 with 01.59.00.

[stlmac08]

Originally Posted by l0k0

5.1.2 is set to release within the next week. Pretty sure Apple has fixed the JB and also the downgrade of A5 devices via RedSnow. A4 devices are still in the clear because of the limera1n exploit, so these can easily be downgraded via stitched firmware. And of course 5.1.2 will be tethered for all A4 devices, A5 isn't going to be so lucky (for the moment).

PS: Someone mentioned iPad2 and preserving baseband. Why would u want to preserve baseband when the iPads are factory unlocked anyways. Baseband preservation is long past dead and is useless to anyone except those on iP4 with 01.59.00.

What would be useful for restores for some of our A5 devices is a version of RedSnow that installed 5.1.1 by using an SHSH blob to install 4.3.3 and then using the RAM disk exploit to put 5.1.1 with an SHSH blob. Of course this will require the iDevice owner to have both SHSH blobs and both iOS install files. I hope the Dev Team will at least do this, as it would give me a restore option for my ipad 2 that had been 4.3.3 jailbroken and is not 5.1.1 jailbroken, in case I should mess up my device.

[l0k0]

Originally Posted by stlmac08

What would be useful for restores for some of our A5 devices is a version of RedSnow that installed 5.1.1 by using an SHSH blob to install 4.3.3 and then using the RAM disk exploit to put 5.1.1 with an SHSH blob. Of course this will require the iDevice owner to have both SHSH blobs and both iOS install files. I hope the Dev Team will at least do this, as it would give me a restore option for my ipad 2 that had been 4.3.3 jailbroken and is not 5.1.1 jailbroken, in case I should mess up my device.

What would be even more useful is breaking down the code between each iOS firmware and their SHSH blobs, and seeing where the changes are. Then implementing those changes per each UDID for those firmwares.

Su u study IOS 5.0 between a few of ur devices, and u learn the change in code. Now u take that IOS 5.0 firmware and compare it to a newer firmware SHSH and make the changes from the new SHSH to match what should be used in the old SHSH....This way the new device on newer firmware could be stitched back to an earlier firmware with a "cooked SHSH"....Thus fooling iOS into thinking that the device actually had a true SHSH for that iOS, although in reality it was just made up to match the way it should have IF apple had signed it to start with............IF THIS MAKES ANY SENSE.

I's be willing to bet that the info inside the SHSH of 5.0 isn't much different that the info inside SHSH of 5.1.1......So if u knew the change that needed to be made per each UDID, then u would be onto something worth having.

[iphonehckr]

Ramdisk exploit to downgrade on the A5 is too niche for Apple to fix now....

If they did, a new way to aptticket signing and restore method has to be redesigned.

Relax you can restore without issues.

[karma]

Blobs saved on non-A5 devices are safe, but A5+ devices aren't safe until a bootrom exploit is found. Apple stopped A5 users from downgrading with blobs (up until recently) and they will stop us again with iOS6. The method used to allow A5 devices to downgrade with blobs can be patched by a firmware upgrade, as stated by the devs. So assuming they drop a firmware before the iOS6 GM, my guess is that the downgrade method will be patched in whatever firmware comes out next.