Separate names with a comma.
Discussion in 'Jailbreaks and iOS Hacks' started by nwmtnbiker, Mar 28, 2012.
Is it safe to download with jailbroken 4s?
Nobody with a jailbroken 4s has updated yet or know anything?
I haven't had any issues with the update.
iPhone 4S & iPhone 4 both jailbroken. Absinthe & pwnage tool.
it is ok to update.
Thanks for the reply. Wish I had a place to check info like that. I lost my sync due to that once before
I thought the the devteam site had updated info but couldn't find?
you have to check the dev team's twitter, including the individuals too. and some other ios hackers twitters. very handy.
Musclenerd used to tweet if it was safe but there has never been a issue with Itunes updates in the 3 years I've been jailbreaking. The only issue I've ever heard is updating your firmware by accident.
That could've been it. I've been around for awhile but make ill mistakes often lol. Don't want to lose the jb
Thanks for the answers to my questions.
Updating iTunes cannot cause a loss of jailbreak.
Worst case it might do is not allow the install of custom/No_BB IPSW's
A while back an iTunes update (9.1 or 9.2 maybe?) broke something with the Blackra1n software that killed your ability to boot tethered. I think a fix came out for it pretty quickly though. Muscle nerd use to tweet about the updates. & if the update had an affect on jailbreaks/ unlocks but I haven't seen him mention the updates lately.
Ive updated and am using an iPhone 4 on 5.0.1 untethered using redsn0w with no issues.
I also check various blogs too to make sure it's safe to update.
Better being safe than sorry !!
Whats different on 10.6.1 ? Anything significant or just another incremental upgrade ?
Some bug fixes
Has there ever been an iTunes update that has thrown off a jailbreak?
By the looks of it no. But being on a 4s I thought I'd rather be safe than sorry. I would hate to upgrade and not have the sync option and lose syncing pictures or music. Then would have to post here and say I lost my jb and I'm a total noob for not checking
Thanks for all the info greatly appreciated.
Yes, read post 10
But the fix was easy, just add back in a .dll file