Crashes into safe mode that often? That's a result of the evasi0n jailbreak. My 3Gs rarely if ever crashes into safe mode. A testament to its well designed bootrom jailbreak. Apple will never stop signing the latest version of iOS for the 3Gs unless Apple stops to existing. Else they'd have a big lawsuit on their hands for rendering millions of devices inoperable. They haven't stopped signing the latest version of iOS for the iPad 1 and iPod Touch 3 yet. Why would they stop with the iPhone 3Gs?
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
General Jailbreak Ends @ 6.1.2 - Pod2g
- Thread starter Auxo
- Start date
- Sort by reaction score
Crashes into safe mode that often? That's a result of the evasi0n jailbreak. My 3Gs rarely if ever crashes into safe mode. A testament to its well designed bootrom jailbreak. Apple will never stop signing the latest version of iOS for the 3Gs unless Apple stops to existing. Else they'd have a big lawsuit on their hands for rendering millions of devices inoperable. They haven't stopped signing the latest version of iOS for the iPad 1 and iPod Touch 3 yet. Why would they stop with the iPhone 3Gs?
Same here. It's strange some people accept it as the cost of jailbreaking, when it's really not. ;-)
A G4 blaming safe mode on a jailbreak????????
Certain tweaks may not interact well, but it is certainly not evasi0n!
Btw i have 100 cydia apps/tweaks installed, thats excluding all the support tweaks for all the apps/tweaks
Last edited:
It's how the tweaks interact with the underlying OS. evasi0n itself is very slightly unstable due to all of the steps needed to break the trust of the kernel. Putting on certain kinds of tweaks pushes the complex userland jailbreak too far resulting in a safe mode hook trigger. Those that designed the evasi0n jailbreak cannot test every single thing in Cydia for stability when using the jailbreak. Just look at the problems with the weather app. It was eventually fixed, but the first release or two had problems with it. It's also a generally known that bootrom exclusive jailbreaks are inherently more stable because they don't exploit bugs within the stock firmware to get the end result.
Well definitely don't waste it on 6.1.3. There's a really bad passcode bug in that. Release it for 6.1.4 at the soonest.
I think whoever wrote that article needs to hire a native English speaking person to start doing their writing for them.
And don't forget about the potential iOS update for T-Mobile LTE and/or AWS 3G support! Unless the passcode bug fix is going to be combined with the network support update
LTE/AWS support is hardware not software, T-mobile gets a hardware tweaked phone for it which is likely to replace the current IP5 model.
https://www.macrumors.com/2013/03/2...a-tweaked-model-a1428-phone-with-aws-support/
Besides that carrier updates are seperate from firmware update and don't effect iOS version.
----------
This going to be fun!
He's just messing around. It won't work, I tried once when I messed up my 4s. It couldn't access Internet, thus couldn't checkin with apple. Once I had Internet access, it restored.
Hey they say you can turn coal into gold.
I just haven't got the time to try it yet.
While it seems Apple is electing to only sell the modified A1428 for Tmobile's AWS network, the current A1428 could be enabled in theory via firmware to handle AWS, as it has the AWS bands on the chip, just disabled via firmware.
That said, current A1428 should still receive a baseband or firmware update to natively handle Tmobile's LTE network, which can easily be enabled via a software update ... unless Apple's going to be a PITA and intentionally not do this either. Regardless people have found ways to modify the phone settings to enable Tmobile LTE on the current A1428, so hopefully Apple does it for us to make it easier.
I wonder what would happen if one were to install modified A1428 firmware on a current A1428 device, or how they are differentiated internally by Apple. I'm thinking that unless there actually is a significant internal hardware change to the wireless chip, hackers/jailbreakers will find a way to unlock the AWS bands on current A1428. But it will take more time and inspection first.
Love your assumptions even after its confirmed that newer hardware is needed. I guess some will like to hope still
That's not something as easy or simple to alter. The JB doesn't have that deep access into the hardware to modify the chips bands used to send/receive LTE signal.
If it was easy as a software update Apple would have done it instead of putting out another phone. Its hardcoded from the factory.
Love your assumptions even after its confirmed that newer hardware is needed. I guess some will like to hope still
That's not something as easy or simple to alter. The JB doesn't have that deep access into the hardware to modify the chips bands used to send/receive LTE signal.
If it was easy as a software update Apple would have done it instead of putting out another phone. Its hardcoded from the factory.
A modified A1428 with the same wireless chip but broadened firmware. The chip is the same, I repeat, the chip is the same (per reports, hence it doesn't carry a new model designation).
Jail breaking would permit carrier profiles to be messed with more easily, similarly to how existing A1428's can be messed with to run on tmobiles LTE network unofficially.
You and I both know hardware can't be swapped via software, but early reports suggest this refreshed model is hardly changed. Initial A1428 models were likely locked with AWS off at AT&T's request for obvious reasons.
The only reason why I think there'll be an iOS update for this is because I remember there was an update back in iOS 6 that had a change log saying "added more support for LTE networks".
Apple changed the way on whether LTE is worthy to be on the phone or not. That's why I'm doubtful it'll come in the form of a carrier update
edit: here it is, it was for 6.1 http://support.apple.com/kb/DL1624
This is only my opinion and I'm sure ill get ***** for it but I don't think there is even a reason to jailbreak anymore with the amount of jailbreaks that are/aren't coming out. There's one, or two if we're lucky, jailbreaks a year. If that. We get a jailbreak and a couple weeks later its patched and then we're waiting again for the next software update which still takes months after the release. I mean yea let's wait for iOS 7 but do you honestly think the jb will be there right away? It hasn't happened like that since iOS 4.0 came out. There's going to be a long wait for people who aren't jailbroken currently.
The only thing I miss about android is the rooting and the amount of developers working on rooting and s-off. The AT&T One X, I still believe to this day, was the most locked down phone to ever be released yet they have root and s-off.
I think what we need is more developers looking to achieve a jail break instead of these scammers just trying to cash in on free releases.
Again this is just my opinion. I'm sure it's different than yours but feel free to flame if you must. I know some people can't help it. =)
The only thing I miss about android is the rooting and the amount of developers working on rooting and s-off. The AT&T One X, I still believe to this day, was the most locked down phone to ever be released yet they have root and s-off.
I think what we need is more developers looking to achieve a jail break instead of these scammers just trying to cash in on free releases.
Again this is just my opinion. I'm sure it's different than yours but feel free to flame if you must. I know some people can't help it. =)
No way a JB could go in and alter a chips wireless communications protocol that is disabled.
Its not as simple, it needs to be flashed during manufacturing process in the factory.
If it didn't Apple would have done it via a firmware or carrier update. They don't go and release and updated version of A1428 for fun if they can just do it the easy way.
Sure hardware can be enabled with additional functionality via software. The N-enabler opened new functionality of the wireless chips in Apple Macs and was available for $.99. And we see firmware updates for Macs all the time.
And Apple rarely makes things sensible or easy for the user when it comes to "switching" anything. For example, the 4S hardware wise is the same as a CDMA or GSM "model", but Apple forces a certain hardware designation before leaving the factory.
I think in theory it COULD be easily enabled via software, but Apple won't. I guess I agree with you in that it's almost completely certain that the A1428 cannot be updated to the Tmobile variant, but it should at Apple's discretion. We will know when we get the teardown
I hope you're right man. But I'm not holding my breath
I do agree with you on this. The hardware for AWS in the GSM variant already, but I don't think Apple has issued firmware updates for iPhones before, and won't make an exception this time around.
Good that you guys are not holding your breath...
"Apple affirmed to us that it's not something that can be enabled via a simple software update for A1428 iPhone units already in circulation. To say that another way, existing iPhone 5 owners on AT&T cannot simply apply a software patch to have AWS support added. You'll need to buy a new phone next month."
http://www.engadget.com/2013/03/26/iphone-5-att-aws-unlocked-plans-t-mobile/
"Apple affirmed to us that it's not something that can be enabled via a simple software update for A1428 iPhone units already in circulation. To say that another way, existing iPhone 5 owners on AT&T cannot simply apply a software patch to have AWS support added. You'll need to buy a new phone next month."
http://www.engadget.com/2013/03/26/iphone-5-att-aws-unlocked-plans-t-mobile/