Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Anyone on iPadOS 13.2 that can tell me if you csn CMD-Space in an app, search for another app and drag it to multitask next to the app you're in (without tapping Cancel in the search field)? This feature was in iOS 12 and I miss it so much. Will Apple ever fix it??

Works!
 
  • Like
Reactions: fredrik9
What the heck is going on with their software? Bugs, failures, disappeared data, it's a mess.

I'll hold off Catalina until a .5 update, I think. It makes me wonder what else is lurking under the hood in their new iOS, iPadOS, and macOS. Yikes...
[automerge]1570898798[/automerge]
If DFU restore fails that's a brick.

Or an expensive Frisbee...
 
I wouldn't call it 'bricking.' I just went in and deleted the Beta Profile and restarted. The update is gone now. I even re-downloaded and tried again, thinking it was just a corrupt download. No dice on the second go-round. But really - having to delete the profile and restart my iPad 2x wasn't tear-worthy and hardly 'bricking' at all.

my iPad pro identifies as a brick
 
Yep, I never understood the carping about beta software. Any sane individual would never, ever install a beta on their primary machine anyway, let alone start blathering on about bugs. Betas are supposed to have bugs. That’s why they are called betas.
- - Post

Betas have bugs, so what is the excuse when the final release has the same bug during beta? Same bug that apple was aware of.

iOS 13 beta had a contacts bug where you could access them without unlocking. Some bug bounty hunter reported it to apple but didn't get paid cause "betas have bugs". iOS 13 final comes out and the bug was still there, it didn't get fixed untill ios13.1
 
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.

A device is never (firmware) hard bricked, internally there are contacts on the board to directly upload firmware into the chips.
I had devices bricked, opened them, soldered wires to pins and uploaded new/fresh firmware on it, rebooted and it works.

I always flash the full image via iTunes... not a fan of incremental updating.

You are wasting your time, in the end you get exactly the same OS, whether you use the full installer or just the smaller Delta Update.
It amazes me that people still think they somehow get a cleaner faster system when doing things like this, or reinstalling macOS.
People think Apple is stupid.
It does NOT make any difference.
My Macs run on updated systems, guess where I started.....yup, almost 2 decades ago on OS X 10.0b, never reinstalled, runs like a charm.
 
Last edited:
Can we not use the term "Bricking" when the device can be made to work again via a restore.

Bricking means... the device is now equal to a brick. A heavy useless thing. If it can be made to work again ... it is not a brick.

Its a lost cause. People don't know what the term brick was originally supposed to mean, and argue that a non-working device that is recoverable is bricked. Its the same thing that happened to the term hacker in the early 90s, with cracker being the one who destroyed systems and the like. Now we have white hat vs black hat hacker to show the difference.
 
well, they are betas... "exceptions"

I blame Google for labeling products BETA for years.

What else can you do to alert people these are supposed to be 'testing only" ? People have trouble with this now, and you wanna confuse it more?

Evidence points to how many people would rather run the beta, than act like it should be a stable release.
 
Lmaoooo well mine was truly nothing but paperweight with hardware. Couldn’t even freaking fix it via DFU mode. I didn’t have a working iPad for 3 days. Thank God I didn’t have class in any of those days.

Lesson learned. Read experience reports first before updating and update via iTunes when possible. 11” Pro. For some odd reason, the genius rep was able to restore it using DFU mode on their MBA yet I couldn’t with PC.

Beta 2 has been smooth sailing since installing via iTunes yesterday.
 
Lesson learned. Read experience reports first before updating and update via iTunes when possible. 11” Pro. For some odd reason, the genius rep was able to restore it using DFU mode on their MBA yet I couldn’t with PC.

Interestingly i couldn't get the restore to work with a 2012 macbook pro but my PC did so fine.

I noticed as the file was unpacking and verifying the iPad would drop connection to the Mac thus giving a cannot be restored because device wasn't found.

With a 3900x and a Type-C 3.2 gen2 connection to the PC the unpacking and transfer went much faster, potentially doing so before the iPad disconnected again.

I also noticed the restore wouldn't actually trigger at all normally and instead kept redownloading the file. I had to move the previously downloaded file to another directory and rely on option/alt clicking restore to manually choose the file.
 
Can we not use the term "Bricking" when the device can be made to work again via a restore.

Bricking means... the device is now equal to a brick. A heavy useless thing. If it can be made to work again ... it is not a brick.
We always need those dramatic effects!
[automerge]1571003679[/automerge]
ThankGod I decided to jump out of iOS 13 beta train as soon as iOS 13 goes official. I can’t risk ”bricking” any of my devices as restore process is tedious and painful, plus several hours of downtime.
 



Following the release of iOS 13.2 beta 2 yesterday, some 2018 iPad Pro owners found that the update failed to install properly, ultimately bricking their tablets and requiring a full restore.

ios132ipadproerror-800x683.jpg

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. From the MacRumors forums:
Amid these reports, Apple appears to have pulled the iOS 13.2 beta 2 update for the iPad Pro as attempting to install the software at this time now produces an error message that the update was unable to be verified because of a lack of an internet connection, despite a connection being available.

Apple appears to have been blocking the iOS 13.2 beta update from the iPad Pro as of last night, and the company likely has a new version in the works that is safer to install. For now, iPad Pro owners should avoid attempting to install iOS 13.2.

Article Link: iOS 13.2 Beta 2 Bricking Some iPad Pro Models, Update Now Unavailable

Yes, happened to me. Against my better judgement I decided to update as a number of apps I use had lost key functionality. So, I backed up (note I can not find my backup) and started the process. As many now know, the process froze. After a great deal of time, I received a box instructing me firmware was out of date, "click to install". Did that.

No luck.

Then did some reading - it seemed the update was incompatible with iTunes. So updated iTunes. Then iTunes was incompatible with the computer OS. So updated the OS, against my better judgement.....I could continue, but NO such luck.

Used Home-brew lsusb to attempt to find the files on the iPad. No luck . . . . Looks like indeed do have a brick. Lost files.

For record, with the number of issues on updates, the keyboards, the screens, it is really hard to say Apple is any different than Windows. In fact, I think Apple is now more the "PC Guy" than the "PC Guy" himself........
 
13.2 non-beta bricked my 2nd gen iPad Pro 12.9" top of the line, 2.5yrs old. Can enter DFU mode but it doesn't respond/restart. Apple Genius said it is beyond help Gee thanks.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.