Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

General TUTORIAL: This is how you can remove expiration from 7.1b2 to preserve JB in iOS 7.1!

1. Changed the thread title to reflect the new info provided by forum members.

2. I tweeted iH8sn0w the URL of this # some 15 hours ago; he hasn't answered so far.
 
Menneisyys2 said:
1. Changed the thread title to reflect the new info provided by forum members.

2. I tweeted iH8sn0w the URL of this # some 15 hours ago; he hasn't answered so far.
Click to expand...

So did I, he probably won't answer now since it will be lost :p

I found its best to tweet him when he starts responding to others, since then it will be at the top for him, unlikely he goes back through 100's over 24 hours.

Even with that said, he's pretty busy atm so I don't mind him not responding right now, hopefully in a few days he will be able to look into it.
 
007p said:
So did I, he probably won't answer now since it will be lost :p

I found its best to tweet him when he starts responding to others, since then it will be at the top for him, unlikely he goes back through 100's over 24 hours.

Even with that said, he's pretty busy atm so I don't mind him not responding right now, hopefully in a few days he will be able to look into it.
Click to expand...

Indeed. However, I decided not to wait until then with posting this warning (by changing the thread title) as Apple can any time stop signing 7.0.4. It's safer for everyone to downgrade to 7.0.4 now. If, then, he posts a fix to his original post, we may still have the chance to upgrade to b2 (or b3 if the latter is still vulnerable) - but at least we're on a non-expiring, JB'able iOS version.
 
fardeenah said:
i am on beta 2 and i dont want to go to 7.0.4.
Click to expand...

1, your choice. As it seems now, iH8sn0w based on his advice on previous iOS versions. It worked back then - but not any more.

2, you can always switch back and forth (I do it very often), assuming Apple still sign the target iOS version.
 
Menneisyys2 said:
Indeed. However, I decided not to wait until then with posting this warning (by changing the thread title) as Apple can any time stop signing 7.0.4. It's safer for everyone to downgrade to 7.0.4 now. If, then, he posts a fix to his original post, we may still have the chance to upgrade to b2 (or b3 if the latter is still vulnerable) - but at least we're on a non-expiring, JB'able iOS version.
Click to expand...

I agree and I am glad you changed the title, need to get as many people alerted to it as possible (that upgraded of course).

Really he should re-tweet that it in fact it doesn't work, only to stop the massive amount of hate he might receive if/when beta 2 expires and people have lost their jailbreak due to a 7.0.5 or 7.1 being out.
 
Is it possible for someone to release a tweak that would allow the beta to stay active? I wish I was smart enough to do that.... :( I only did what you mentioned, so I guess that's not going to work.
 
the guy is right 7.1 beta 2 is so much better and faster than 7.0.4. no way i am going back to 7.0.4, its just too slow and unstable. at this point io7 itself needs patch and optimised and fixed, then comes the jailbreak part. i do hope that the jailbreak will still be alive when 7.1 GM comes out else it would be such a huge loss
 
Menneisyys2 said:
On 32-bit systems, the difference isn't THAT big, except for Safari / UIWebView stability, particularly on non-iPads.
Click to expand...

Any idea what it's like on the 5s? Wondering what I'm gonna miss out on :(

Edit: unless of course the evaders jailbreak 7.1 (which is not out of the realm of possibility)
 
Menneisyys2 said:
(Original thread title: Did anyone actually test the alleged 7.1b2 ReleaseType Beta Value removal?)

Unfortunately, iH8sn0w's advice HERE (also repeated in this very forum quite often; for example HERE) doesn't seem to work. If you do remove the ReleaseType/beta key/value pair from /System/Library/CoreServices/SystemVersion.plist :
Click to expand...

Looks like the advice was almost right. If you also amend the build number within that same plist file to be iOS 7.0.4's then the beta does not expire if date is set beyond the 27 Jan 2014 expiry date so suggests will never expire.

Basically change ProductBuildNumber key to 11B554a as well as deleting the 'Beta' key altogether per iH8sn0w's advice. You can also change ProductVersion to 7.0.4 if you really like to spoof 7.1b2 as 7.0.4 completely but that doesn't seem to affect the expiry.

Hope that helps - certainly did for me :)
 
jonmiller said:
Looks like the advice was almost right. If you also amend the build number within that same plist file to be iOS 7.0.4's then the beta does not expire if date is set beyond the 27 Jan 2014 expiry date so suggests will never expire.

Basically change ProductBuildNumber key to 11B554a as well as deleting the 'Beta' key altogether per iH8sn0w's advice. You can also change ProductVersion to 7.0.4 if you really like to spoof 7.1b2 as 7.0.4 completely but that doesn't seem to affect the expiry.

Hope that helps - certainly did for me :)
Click to expand...

For beta 1 we have until january 13.....
 
jonmiller said:
Looks like the advice was almost right. If you also amend the build number within that same plist file to be iOS 7.0.4's then the beta does not expire if date is set beyond the 27 Jan 2014 expiry date so suggests will never expire.

Basically change ProductBuildNumber key to 11B554a as well as deleting the 'Beta' key altogether per iH8sn0w's advice. You can also change ProductVersion to 7.0.4 if you really like to spoof 7.1b2 as 7.0.4 completely but that doesn't seem to affect the expiry.

Hope that helps - certainly did for me :)
Click to expand...

going to try this when i jailbreak
 
jonmiller said:
Looks like the advice was almost right. If you also amend the build number within that same plist file to be iOS 7.0.4's then the beta does not expire if date is set beyond the 27 Jan 2014 expiry date so suggests will never expire.

Basically change ProductBuildNumber key to 11B554a as well as deleting the 'Beta' key altogether per iH8sn0w's advice. You can also change ProductVersion to 7.0.4 if you really like to spoof 7.1b2 as 7.0.4 completely but that doesn't seem to affect the expiry.

Hope that helps - certainly did for me :)
Click to expand...

Great find! I test it too (particularly whether it refuses to accept apps with a deployment target of 7.1 - if the build nr messes that part up, it won't) and report back.
 
^
If it works, and it sounds like it's going to, please bullet point a quick walk through on what it is we need to do.

Right now, I am back on 7.1 beta 2 without a jailbreak as running 7.0.4 with a jailbreak (and the limitations that come with it right now) wasn't worth it.

Thanks for your hard work and dedication to this issue!
 
braddick said:
^
If it works, and it sounds like it's going to, please bullet point a quick walk through on what it is we need to do.

Right now, I am back on 7.1 beta 2 without a jailbreak as running 7.0.4 with a jailbreak (and the limitations that come with it right now) wasn't worth it.

Thanks for your hard work and dedication to this issue!
Click to expand...

Basically:
  1. Jailbreak device and install iFile.
  2. Then navigate to System/Library/CoreServices and open the SystemVersion.plist in Property List viewer.
  3. Within there, delete the 'ReleaseType' Beta key per the advice from iH8sn0w and as stated at start of this thread
  4. Also within same file, overwrite the value for the key ProductBuildVersion to be 11B554a
  5. Close iFile and reboot/respring for good measure
  6. You can then test this by setting clock forwards to after the 27 January expiry for b2 and it will still reboot without going to activation issues.


----------
Menneisyys2 said:
Great find! I test it too (particularly whether it refuses to accept apps with a deployment target of 7.1 - if the build nr messes that part up, it won't) and report back.
Click to expand...

Apps with deployment target of 7.1 seem to work just fine. Just tested out on an app I've been developing and set target to 7.1 and it works as I'd expect (not withstanding the fact that the code itself needs some updating).

:D
 
Last edited:
Menneisyys2 said:
particularly whether it refuses to accept apps with a deployment target of 7.1 - if the build nr messes that part up, it won't
Click to expand...

No issues. (I've tested this with THIS Xcode project. Deployment target is 7.1, which means it installs/ runs OK on 7.1b2 devices but can't be installed on truly 7.0.4 ones.

The build nr-hacked version runs it just fine.

All in all, this tweak seems to be the one to go for.

----------
jonmiller said:
Apps with deployment target of 7.1 seem to work just fine. Just tested out on an app I've been developing and set target to 7.1 and it works as I'd expect (not withstanding the fact that the code itself needs some updating).

:D
Click to expand...

I've also experimented with this (see above); same results.
 
jonmiller said:
Basically:
  1. Within there, delete the 'ReleaseType' Beta key per the advice from iH8sn0w and as stated at start of this post
  2. Also within same file, overwrite the value for the key ProductBuildVersion to be 11B554a
Click to expand...

Alternatively, assuming you have / use iExplorer or iFunBox, you can install afc2add and, then, overwrite the same file with this one: https://dl.dropboxusercontent.com/u/81986513/122013/26b2extension/SystemVersion.plist , followed by a reboot, to avoid having to manually edit the plist file.

----------
thadoggfather said:
If you change expiration to past that date without modifying the files it will stop working?
Click to expand...

It will, see my previous (last two) screenshots in my OP showing what the iDevice / the desktop shows in this case.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back