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.
iOS 13.2 Beta 2 Bricking Some iPad Pro Models, Update Now Unavailable
- Thread starter MacRumors
- Start date
- Sort by reaction score
iOS Friday 13th is probably a more fitting name for this release.
Excellent point! lol maybe that’s why their devices are getting bricked lol incompatibility 😂Shouldn’t they be using ipadOS on an ipad pro ?
but seriously I hope they fix this issue soon.
Sounds like some folks are getting truly bricked.
In the article " We've seen several complaints from iPad Pro owners who were affected by the issue, and in some cases, even a restore from DFU mode failed to work. "
There a little comfort now knowing it just wasn’t me. My 2018 Pro got stuck on the Apple logo for hours. It wouldnt even respond to holding the Vol Up and Sleep buttons together. Finally did the hard reset by Vul Up, Vol Down and holding Sleep, put it in DFU mode and started over. But now just getting the No Longer Connected to the Internet error.
Beta testers I would like to thank you for being a beta testers.
It makes my software work
It makes my software work
Explains why I kept getting errors this morning trying to install it. Not sure how 13.2 made it to Public Beta, feels more like an alpha. Very unstable. First noticeable I had was the USB-C/3 speeds came tumbling down when I was trying to import photos using an SD to USB-C cable. Then, the actual process of importing kept crashing (also on iOS 13.2 on iPhone using a lightning to SD card). Figured I'd restore back to 13.1 since I had a trip coming up that I need a more stable system for. So yeah, turn off "Find my iOS device." Couldn't do it. I'd see the keyboard pop up and ask me for my password, but had no where to type. Tried restarting, nothing. Oh also my keyboard kept jumping all over the place (had the small keyboard enabled). Every time I tapped it would bounce about half a cm down.... >.< Finally threw it into DFU you'd think that would be it. Nope. It said it restored, but when it booted it was not touched. Took about 3 tries for it to finally go through. Never have had something this unstable before. Thought I was on the fast ring on my Surface Pro 3 for a moment.
Doesn't bricking mean that they can't be restored and the device needs to be thrown away? So are they being bricked, or are they simply unable to boot?
I've lost several devices entirely due to bricking after trying to do updates over the years (both regular and beta) so I wouldn't be surprised if this was in fact true bricking that needs a full device replacement.
They're testing next generation engineering for obsolescence. Sounds like a success.
Happened on both my iPad Pros. Even DFU won;t work to restore. Now stuck with two literal bricks.
Just kidding. I really just wanted to fit in.
Just kidding. I really just wanted to fit in.
The purpose of a beta is to discover these types of issues, which is why betas should not be installed on devices that you depend on.
Just had this conversation this morning with @I7guy People who don't have a high tolerance for potentially buggy software shouldn't do betas. I don't, so I don't. For those who do... thank you for your service.
Bricked my 11” iPad Pro and went through hell on my iPhone XS Max. The XS Max successfully completed after I forced a restart at hour three, but the iPad needed a full restore from the downloaded firmware. It took, literally thirteen hours to fix, update and restore my backup.
Bricking is not an almost.
[automerge]1570822515[/automerge]
Not a bricking. Pain is expected in betas. That's why they're betas. Especially developer betas, where you're expected to give a resigned sigh and set to work fixing it rather than panicking.
Same exact thing for me. Update looked like it was finished installing (progress bar was all the way across), but, it never restarted. I would press the sleep/wake button, and it would say that the iPad will restart when update is complete. After about 30 minutes of that, I did a force reboot...ta daaaa! I was relieved because I have a 2011 iMac that doesn't have USB C for me to connect it to iTunes.
[automerge]1570822837[/automerge]
So a device is only bricked if it cannot be fixed? Interesting.Bricking is not an almost.
[automerge]1570822515[/automerge]
Not a bricking. Pain is expected in betas. That's why they're betas. Especially developer betas, where you're expected to give a resigned sigh and set to work fixing it rather than panicking.
Last edited:
Yup... BRICKED Mine (soz put it in capitals) cos it took three hours and a lot of faffing around to get my ipad back...dreaded the idea of having to rale it to the apple store. Sheeesh.... but managed to make it breath again (lol .. looking back) the releif when it started to actually restore to 13.1.2 was laughable. I feel for ithers on here who were not so lucky... its 20:40 uk time and appke have allowed my ipad to redownload what i assume to be a fixed update for 13.2b2 which did work....
Post install 50% of apps are crashing with no icon...oh well...suppose my ipad suffering. Beware!1
Post install 50% of apps are crashing with no icon...oh well...suppose my ipad suffering. Beware!1
Last edited:
I had the issue as well, went to dfu and restored to the previous beta. I at least got to use Catalina's finder for iPad the first time. I actually like it better it through the finder.
Not a bricking. Pain is expected in betas. That's why they're betas. Especially developer betas, where you're expected to give a resigned sigh and set to work fixing it rather than panicking.
Well actually, not being able to restore from DFU is something that's not supposed to happen in a beta. And needing to go to DFU at all isn't really supposed to happen in a beta release.
Beta used to mean "it's mostly sort of ready to go," not "there may be issues that will cause you hours of pain and suffering." The latter is supposed to be more of an alpha/gamma release.