Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Nope. It lacks the necessary drivers, and even then you can't install it due to Apple's signing system.
 
The main problem would be that Darwin 13.0 is not compiled to 64 bits (neither are the drivers on that version)

Historically, a 32 bit OS can run just fine on a 64 bit processor, though can't address more than 4 GB of RAM or use the 64 bit CPU to its potential. Just look at Windows XP running on Core 2 Duo PCs. I am not sure how that would hold to iOS.

Though, in summary it isn't going to ever work without serious modifications to the firmware and falsifying the signing process. That is a lot of work that I think only Apple could really achieve since it is their process and code. Working off of someone else's code is a royal nightmare.
 
Historically, a 32 bit OS can run just fine on a 64 bit processor, though can't address more than 4 GB of RAM or use the 64 bit CPU to its potential. Just look at Windows XP running on Core 2 Duo PCs. I am not sure how that would hold to iOS.

Though, in summary it isn't going to ever work without serious modifications to the firmware and falsifying the signing process. That is a lot of work that I think only Apple could really achieve since it is their process and code. Working off of someone else's code is a royal nightmare.

That's because most 64 bit processors emulate 32 bits (x86-64 architecture), but I'm not sure if the 5S processor has that capacity, but I agree with you, in our end it would be almost impossible getting a 5S to run iOS 6
 
That's because most 64 bit processors emulate 32 bits (x86-64 architecture), but I'm not sure if the 5S processor has that capacity, but I agree with you, in our end it would be almost impossible getting a 5S to run iOS 6

The 5S' A7 does have 32-bit emulation. Otherwise it wouldn't be able to run older iOS apps that are not 32/64-bit or 64-bit binaries. The thing that would hang it up is the bootrom. It wouldn't properly initialize the hardware for a 32-bit OS.
 
The 5S' A7 does have 32-bit emulation. Otherwise it wouldn't be able to run older iOS apps that are not 32/64-bit or 64-bit binaries. The thing that would hang it up is the bootrom. It wouldn't properly initialize the hardware for a 32-bit OS.

That doesn't mean it can run a 32 bit kernel, windows can run 32 bit apps by using WoW64 (http://en.wikipedia.org/wiki/WoW64).

The apps themselves only need to be rewritenn if they use kernel level functions
 
Absolutely impossible. There was never a iOS 6 version for iPhone 5s so its just impossible.

Nothing is impossible, as it was already stated, the only big issue would be dealing with the different CPU architecture, and lack of drivers, but remember that the Darwin kernel is exactly the same used in Mavericks so it should be "easy" (read possible) to compile it to ARM, and for the lack of drivers, it's a pain in the ass, but it's the same difficulty as making drivers for OS X to run on Windows machines and that has been done for years for a multitude of devices.

In short, it would be very difficult, but nonetheless possible
 
Nothing is impossible, as it was already stated, the only big issue would be dealing with the different CPU architecture, and lack of drivers, but remember that the Darwin kernel is exactly the same used in Mavericks so it should be "easy" (read possible) to compile it to ARM, and for the lack of drivers, it's a pain in the ass, but it's the same difficulty as making drivers for OS X to run on Windows machines and that has been done for years for a multitude of devices.

In short, it would be very difficult, but nonetheless possible

Well close enough to impossible. And you would completely lose the touch ID
 
The limitations are moot because there isn't even any way of putting iOS6 onto an iPhone 4 now! Not unless you have a 'blob' or are prepared to put a possibly tampered with and unsecure o/s sourced from the net onto your phone.
 
That doesn't mean it can run a 32 bit kernel, windows can run 32 bit apps by using WoW64 (http://en.wikipedia.org/wiki/WoW64).

The apps themselves only need to be rewritenn if they use kernel level functions

While you can install a 32 bit O/S, such as XP on a 64 bit machine, you can't install a 64 bit O/S on a 32 bit processor. Try it and see.

Although Windows is a bit different as Windows XP for example, won't know about newer processors, but it will install anyway on any processor as Intel builds their new processors to be 100% compatible through the generations.

And while I don't specifically know how IOS identifies processors, IOS 6 probably doesn't have the smarts to work with the A7, and who knows if the A7 can even be booted in 32 bit mode. Not to mention the signing of the IOS operating system.
 
While you can install a 32 bit O/S, such as XP on a 64 bit machine, you can't install a 64 bit O/S on a 32 bit processor. Try it and see.

Although Windows is a bit different as Windows XP for example, won't know about newer processors, but it will install anyway on any processor as Intel builds their new processors to be 100% compatible through the generations.

And while I don't specifically know how IOS identifies processors, IOS 6 probably doesn't have the smarts to work with the A7, and who knows if the A7 can even be booted in 32 bit mode. Not to mention the signing of the IOS operating system.

Intell stated that the A7 can do full 32 bit emulation in order to run older apps not using the new 64 bit architecture. That being said, the boot loader would not initialize the 32 bit kernel properly.
 
Nothing is impossible, as it was already stated, the only big issue would be dealing with the different CPU architecture, and lack of drivers, but remember that the Darwin kernel is exactly the same used in Mavericks so it should be "easy" (read possible) to compile it to ARM, and for the lack of drivers, it's a pain in the ass, but it's the same difficulty as making drivers for OS X to run on Windows machines and that has been done for years for a multitude of devices.

In short, it would be very difficult, but nonetheless possible
Even if you could get through all of that there's no signed version of the firmware to install so there wouldn't be a way to install it on the phone even if you had something that could be compatible.
 
iOS 6 could easily be made to run on the 5S if Apple wanted it to. If they can force iOS 7 onto the 4, they can update 6 to work on the 5S.

Otherwise the signing is the first thing you would have to worry about anyway.
 
iOS 6 could easily be made to run on the 5S if Apple wanted it to. If they can force iOS 7 onto the 4, they can update 6 to work on the 5S.

But why on earth would or should they spend even a nanosecond working on such a thing? I'm sorry but if you bought a 5S, you bought a phone that runs IOS 7, end of story; you have absolutely no excuse for whining about IOS 6 if you paid Apple for a phone that has only ever run IOS 7.
 
Nothing is impossible, as it was already stated, the only big issue would be dealing with the different CPU architecture, and lack of drivers, but remember that the Darwin kernel is exactly the same used in Mavericks so it should be "easy" (read possible) to compile it to ARM, and for the lack of drivers, it's a pain in the ass, but it's the same difficulty as making drivers for OS X to run on Windows machines and that has been done for years for a multitude of devices.



In short, it would be very difficult, but nonetheless possible


Nothing is impossible is the biggest lie I've ever heard.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.