i am on 5.0.1. and did it OTA while being jailbroken!

[BLiNK]

so last week when 5.0.1 was released i was in beta 2 of 5.0.1 so i downgraded to 5.0 while Apple was still signing it. not too long after downgrading i received an update badge on my Settings app (http://forums.tipb.com/jailbreak-unlock-forum/223976-update-badge-settings-app-now-what.html) in an attempt to get rid of the badge i went ahead and started the download process knowing that it would not work since i am jailbroken.. at least that's what i thought.

I AM ON 5.0.1 (9A405)!!! and did it OTA while being jailbroken! this evening i plugged into iTunes and noticed in my summary section my build was 5.0.1. i could not believe what i was seeing. after the OTA download was complete my device went into safe mode and i just simply did a tether reboot and all went well. did not notice until tonight

so much for staying on 5.0 FML

 

[BrindawithanI]

Apple is on to you Blink!

 

[Peligro911]

So you JB 5.0.1 ! Interesting


Sent Into Orbit from my iPhone 4S using Tapatalk

 

[iDonev]

Kinda makes sense, doesn't it? I mean the same exploit is used to JB both 5.0 and 5.0.1 so obviously the OTA doesn't patch the vulnerability.

 

[BLiNK]

yes, it does make sense. however, all during the iOS 5.0 betas it was a known thing that delta updating would not work IF you were jailbroken. i never tried it during that time since i was stock during the beta process. very odd..

anyways, i went ahead and restored to iOS 5.0.1 and re-jailbroke. Semi-Sethered works great! in fact if the semi-tethered works with every update i would not feel the need for the Untethered

 

[Massie]

BLiNK, I'm not totally clear?did you need to re-jb after the OTA update, and set up all your Cydia apps again, or did all of that survive the process? It sounds like nothing changed, but then you mentioned restoring and re-jb'ing?

 

[BLiNK]

after i realized what happened, a couple of days later, i tried to verify if the semi-tethered option still worked. it did not, even after uninstalling and resinstalling, so that is the main reason why i restored as new and re-jb

everything seemed to be working properly since the OTA update up to me restoring