iPhone Upgrading from 6.1.3 to 7.0.4

[Smokin House]

Hey people, I wouldn't normally ask this question but this time feel the need to due to no software to make custom ios7 firmware and with newer versions of itunes not accepting custom firmware.

I am thinking of upgrading from 6.1.3 to 7.0.4 on my iphone 4.

Before you all jump on and say "You cant do it now because apple are only signing 7.1 now", I have my blobs for 7.0.4 saved on the cydia server and locally on the pc

I also have not updated my itunes for some time so that is still on version 11.0.4.4

I used tinyumbrella to get the blobs so I believe they are stable blobs.

My question then is:

If I want to update to 7.0.4 do I run TU (with my blobs there) behind itunes and shift/restore with the official restore 7.0.4 firmware and then jailbreak with evasion as if it was an original install?

Basically what I'm saying is, will the blobs running on the TSS server still sign my 7.0.4 that I try to install with itunes?

Any assistance would be appreciated

ps the only god dam reason im thinking of upgrading is because tons of apps from the app store are now ios7+ (WHAT A PAIN!)

 

[007p]

No you can't update to 7.0.4.

I know your using an iphone 4, and maybe soon you will be able to. But right now iTunes 11 afaik doesn't accept custom firmware. A workaround needs to be found, that doesn't use iTunes to restore the firmware. Currently there isn't even a way to downgrade iphone 4 from 7.1 to 7.0.x - well not publicly. You can only use an old version of iTunes to go back to ios 6 (from 7.x).

I would stick on 6 for the time being, then hopefully a new method of installing custom firmware will be out and you can go to 7.0.4 with your blobs. I think sn0w is working on one, but hasn't really been any progress updates on it lately.

Alternatively, you could jump to 7.1 and tether jailbreak when that comes out in the very near future (within the next couple of weeks - or you can use one right now but its not in 'english'). But you may prefer to stick with untethered.

 

[Smokin House]

Thanks for the reply but I wouldn't be installing custom firmware as I know there's nothing out there to make a custom 7. What I'm asking is if my blobs running on tu will still sign OFFICIAL 7.0.4 firmware when installed with iTunes.

Also I believe it was from 11.1 that the custom firmware got blocked on iTunes.

 

[dhlizard]

There is no way to install 7.0.4 on iPhone 4 since neither of the two apps (Sn0wbreeze or Redsn0w) is capable of doing so for iOS7, Apple doesn't even use SHSH for authentication in iOS7.

You can install older iOS6 firmware on iPhone4 (up to 6.1.3 using Sn0wbreeze) but not iOS7

TinyUmbrella won't work for hosts past iOS4

 

[Smokin House]

There is no way to install 7.0.4 on iPhone 4 since neither of the two apps (Sn0wbreeze or Redsn0w) is capable of doing so for iOS7, Apple doesn't even use SHSH for authentication in iOS7.

You can install older iOS6 firmware on iPhone4 (up to 6.1.3 using Sn0wbreeze) but not iOS7

No offence but OMG!!! guys I'm NOT trying to install a custom firmware!!!!!!

If apple do not use shsh to sign firmware for 7+ then what was the point in TU having the capability of getting SHSH? seems pointless really.

What do they use now then if not SHSH/APTicket?

 

[007p]

No offence but OMG!!! guys I'm NOT trying to install a custom firmware!!!!!!

If apple do not use shsh to sign firmware for 7+ then what was the point in TU having the capability of getting SHSH? seems pointless really.

What do they use now then if not SHSH/APTicket?

I'm pretty sure that you are forced to used 'custom firmware' when you re-build it using your shsh/aptickets. As said, TU won't work for hosts.

You also need itunes 11.1 to install ios 7. Which is the version it started blocking custom firmware. I don't have an iphone 4, so I haven't actually done anything like this and am no means an expert. But I am fairly certain what you want to do isn't possible, for now.

Here is what sn0w 'blogged' when ios 7 got released, maybe this will explain it better?

iTunes 11.1 - WHAT IS THIS?! GO AWAY?!
Along with Apple pushing iOS 7, they updated iTunes to 11.1. This actually brought more headaches than convenience.

When a user hits the restore button, they often see "iTunes will erase and restore your iDevice to iOS x.x.x and will verify the restore with Apple". What this does is submit a request to Apple for an apticket + SHSH blobs. Previous revisions of the iTunes Mobile Device Library would just use the BuildManifest included inside of an IPSW to supply the request to Apple with the essential "hashes" of each image within the IPSW. When tools like sn0wbreeze, PwnageTool, seas0npass, or redsn0w modified images such as iBSS, iBEC, ramdisk to avoid signature checks during the restore, iTunes didn't care or know.

Now, prior to iTunes sending the TSS request to Apple, they ignore the values already in the BuildManifest and "re-hash" every image within the IPSW to create the TSS request. Meaning if 1 byte of any image is modified, when iTunes calculates the new "hash" and sends the TSS request, the TSS server will refuse to fulfill the request (Error 3194 is displayed). This essentially kills iOS 7 custom IPSW restores via iTunes.

Moving on to Error 11... This error seems to only be related to devices with basebands that require bbtickets (So basically the iPhone 4). Even though iFaith/sn0wbreeze removes the baseband requirement, iTunes 11.1 is expecting the iPhone 4 baseband firmware to be signed no matter what and notices that it isn't. This causes it to error out with code 11 (Error 11). It is worth noting that this issue was already present in the Mac OS MobileDevice framework on iTunes 11.0.x. When iTunes 11.1 was released for Windows, it looks like they finally merged code. Thus bringing the issue to Windows with iTunes 11.1. This does not affect the iPhone 3GS (bbfw is always pre-signed),

A temporary workaround to fixing Error 11 on Windows is by downgrading to iTunes 11.0.x. You can find download links to old revisions of iTunes over here (thanks cj!).

One more thing worth mentioning is iREB for the iPhone 2G, iPhone 3G, and iPod touch 1G is broken with the iTunes 11.1 update. This is on my list of things to fix, but again... a workaround is typed up above.

sn0wbreeze/iFaith updates for iOS 7 please?!
As I have said above, iTunes 11.1 essentially kills iOS 7 custom IPSW restores via iTunes due to the "re-hashing" that is performed prior to the restore. I am working on a workaround for this, it will probably end up being something like the actual restore occurring within sn0wbreeze/iFaith itself (similar to redsn0w's "Restore" functionality).

As far as saving the iOS 7 apticket + SHSH blobs, iFaith can already fetch these blobs by selecting the "Show available caches on server" button and following on-screen prompts. This will work on all devices (including A5+ devices) except for the new iPhone 5C and iPhone 5S.

Dumping functionality to dump iOS 7 blobs+apticket on the iPhone 4 will come when I get around the silly iTunes issue sorted.

 

[dhlizard]

No offence but OMG!!! guys I'm NOT trying to install a custom firmware!!!!!!

If apple do not use shsh to sign firmware for 7+ then what was the point in TU having the capability of getting SHSH? seems pointless really.

What do they use now then if not SHSH/APTicket?

I know that, but you do not understand how Apple authentication functions.
Custom firmware does not only include preserving baseband.
Do some additional reading, you will eventually understand.

 

[Smokin House]

I'm pretty sure that you are forced to used 'custom firmware' when you re-build it using your shsh/aptickets. As said, TU won't work for hosts.

You also need itunes 11.1 to install ios 7. Which is the version it started blocking custom firmware. I don't have an iphone 4, so I haven't actually done anything like this and am no means an expert. But I am fairly certain what you want to do isn't possible, for now.

Here is what sn0w 'blogged' when ios 7 got released, maybe this will explain it better?

I know that, but you do not understand how Apple authentication functions.
Custom firmware does not only include preserving baseband.
Do some additional reading, you will eventually understand.

OK Cheers guys.

 

[Applejuiced]

No offence but OMG!!! guys I'm NOT trying to install a custom firmware!!!!!!

If apple do not use shsh to sign firmware for 7+ then what was the point in TU having the capability of getting SHSH? seems pointless really.

What do they use now then if not SHSH/APTicket?

You can't do it dude.
Try it and see how far you get.
You need redsnow or snow breeze to be updated and be able to create a custom Ipsw with those saved blobs stitched on it.
You cannot restore to official noncustom firmware even if you have blobs saved. Those days are over.

 

[Smokin House]

Gutted. It seems that apple is trying every way possible to stop us jailbreakers. What have they got to hide ffs!

 

[Applejuiced]

Tell me about. They're been making it harder and harder with every software and hardware update.
But the jb community sooner or later always comes with ways around things

 

[Smokin House]

Agreed. It's almost like try have the 'bill gates syndrome', they want to monopolise everything!

Well fingers crossed. Hopefully we will get something soon.