Hi Guys and Gals. Can Blobs (to downgrade atv2 running 5.01 to an earlier version) be shared? would be nice if someone could upload previous version blobs. that would enable me to downgrade and jailbreak.
Conventional wisdom says that blobs cannot be shared because they are device specific. However there have been a number of posts claiming success using blobs from a different device so it is not clear what the real situation actually is.
If you’re willing to accept the consequences if there are any I will link you to both a 4.4.4 and a 4.3 SHSH blob for my device that you can attempt to use.
i have 4.4.4 one
i am seeking a 4.4.2 one
thx
i would love to try this to get back to 4.4.4 but i worry about bricking it!!
what do you mean with :
i worry about bricking it!
If you really want to attempt to do so I can post a 4.4.2 blob. Just note that no one here has purposely attempted it as it could be a pain in the ass to recover it or worse could brick your device. However people have stated that it has worked for them.
.
Render Useless. No Good No Mo
or maybe untill new jailbreak software is released
I don’t see why it would. Simply reflashing with a stock IPSW should fix it but then again I haven’t attempted to do it myself.
no i dont no if it would either! i just no that the blobs are unique to each device so its possible it will brick it!! but hey a JB is just around the corner so might as well just wait a few more days!!
I think a lot is talked about bricking idevices, but not sure if anyone has ever permanently damaged their device by attempting a jailbreak, because as Matty states just restoring your device will get it back to working. It would be on the latest firmware, but it should work fine
Even still if you have blobs for the version you are on currently or previous ones you could EASILY revert back to it.
Hi
Please post the 4.4.2 blobs to let me try it
.
No offence but You shouldn’t use the term (bricked) then because the term bricked for 69 years for me has meant
When used in reference to consumer electronics, “brick” describes a device that cannot function in any capacity (such as a device with damaged firmware).
. This may or may not apply to the apple tv 2.
If i needed shared blobs i would try it and see what happens but i have my own and don’t intend to test it for anyone else.
Hi guys, my first post here in this forum.
If someone posted thir blobs (haha) how would u proceed with the installation and such?
someone succeded to install 4.2.1 blobs for other machine on atv2 5.1 one …
see other topics
haha 8)
Salim,
Would it be possible if you can post the 4.4.4 blob?
Thanks
Andrew
The DFU state is implemented in the SecureROM, which suppose to be truly read-only. Unless certain invalid data in the nvram can cause it to hang, one should always be able to revert the device back to DFU, which by design should always be able to load a valid LLB, which in turn will load the rest of the FW. The chance of a DFU halt caused by invalid data in any part of the erasable memory is still possible (some early day PC BIOS would panic and require removing backup battery for a full reset) but probably very very slim with all iOS devices. Had it not been the case, there would’ve been far more outcry on bricked devices as results of interrupted/incomplete FW update process(due to power outage, loss of network/USB conmection etc); unless Apple has made the whole process transactional, which I don’t believe there is an evidence of.
If someone could post 4.4.3 blobs I’m willing to find out if the AppleTV bootrom and the different itunes releases will actually check the ECID. I will be VERY surprised if they don’t, cause that would be a huge miss on Apple’s part since to average users sharing ECID among AppleTVs doesnt really post the same level of concerns as doing the same on iPhones and iPads.
some guys here succeded to downgrade atv2 with 5.1 to 4.4.2 theethred using different machine blobs