iPadOS 18 bricked my iPad M4

See this article.

Apple Pulls iPadOS 18 for M4 iPad Pro After Bricking Complaints

I have an iPad Pro M4 and updated to iPadOS 18 without issue. The above article suggests (but does say for certain) that those iPads previously using iPadOS 17.7 may have this issue.

I'm not sure what version of iOS was on my iPad since I downloaded the beta iPad OS18 shortly after starting it up. The beta version (as it turns out) became the RC version (22A3354) and was installed on my iPad 2024 M4 without issue. After reading this thread and others, I can only assert that some pre-condition (either existing version of iOS), or there is a hardware issue with some iPads 2024 M4. It is peculiar that the issue seemed to only impact a small percentage of these machines, I do hope Apple provides some detailed explanation of what was in fact the root cause of this issue.

Update: My device will be replaced with a new one.

I went to the store where I bought it, and they sent it to their repair department. I just received an email from them saying that the entire device is unresponsive and needs to be replaced.

I used Passverse iOS System Recovery program to install V17.7 after my iPad Pro (M4) bricked when I tried to install V18. Passverse runs on Windows 11 and is connected to the iPad with an USB cable. My wife also has an iPad Pro (M4) and she installed V17.7 followed by V18 without any problems. After all this effort, I noticed the offer to install V18 was gone from the update menu.

My M4 downloaded IOS 18 but couldn’t install the update. I had been using the beta version with no trouble.

The iPad still worked but was stuck in a cycle of trying and failing to install the update. Tech at the Apple Store tried everything but couldn’t get rid of the download.

They said it was an emerging issue, apologised and gave me a new iPad with iOS 17. I wasn’t able to use a backup to set up the new iPad in case it carried over the issue to the new iPad. I also wasn’t able to transfer my e sim between devices, the two devices just would not communicate (when they were bought near to each other).

Staff were v v helpful.

I was told up to 2 weeks for the replacement. The Genius Bar gave me the number of the service centre, when I called I was told that there is a delay due to the high volume of iPads with this issue.

I was told that the replacement will be as new, either a returned product or in the authorisation of work document that you would have signed it would say something like this, "Apple may use parts or products that are new or previously used Apple genuine parts that have been tested and passed Apple functional requirements."

It is a bit gutting when you have paid out a lot of money for a new product to possibly get a refurbed unit sent back, but I imagine that I won't notice the difference.

I'm still waiting, I haven't heard anything about the progress of the repair, 6 days now.

Same here. In Poland Apple service is a disaster. 2 days phone talk with mid technical cuz they need to ensure it’s really dead. In local apple service don’t have no recourses (people) to deal witch 1200€ iPad. Right now we know at least that apple (and maybe someone else) have the abilities to bricked your device anytime eg. intentional aging…

I can see the lines in the screenshot as well. I have checked with the apple support right after I saw the issue with my screen. There is no damage to the iPad as I use it very carefully. This issue happened only after I updated it to the new IPad Os 18 update.

Took a reservation to an apple service centre and got informed that there is no damage, but the iPad is not repairable and I have to pay the cost of a new iPad Pro to exchange it with my old one. This doesn’t make any sense of apple rolling out an update that will destroy your warranty expired iPad Pro. It’s only 2 years old. I only bought an iPad instead of an android tablet as I was told iPads are reliable, I have the exact opposite experience.

DaveDolphin wrote:

so I have the iPad M4 - Pro (1TB) - updated to iPad OS 18 and it bricked. Crazy thing is that just a couple weeks earlier, my iPhone 15 Pro also bricked when updating to iOS18! - they sent me a new phone - didn't fix it. ended up I could set up as new but could not restore from my diligently backed up backup! - then, same thing happens to iPad. I see now the known issue with iPad - wondering how they could be connected? I spent hours on phone with tech support in both cases, and went to Apple store for a GB visit. - both cases they sent (and are sending) me a new device. I'm wondering if my replacement iPad will be able to restore from backup. At this point, I have little hope. Maybe it will come with iPad OS 17 and that will be how it works. It is SO MUCH WORK! to get my device back to the way it was set up previously - when not being able to use backup to restore. Putting apps in folders, signing in to accounts,... - so many things you don't even think about until they are gone! VERY VERY frustrating!

-Has anybody else has issue with iPad AND iPhone?

Your new iPad Pro M4 will be able to update to iPadOS 18.0.1 without issue - after which you will be able to restore your pre-existing iPadOS backup.

The update from iPadOS 18 to 18.1 bricked my iPad gen 7. All subsequent efforts to restore terminate with an "Unknown" error. Apple tech support can resolve it, and suggest I take it to an Apple store. Haven't done that yet. Closest is 30 miles away.

My IPad Pro 11inch with WiFi and cellular is doing exactly the same thing. I have tried everything and nothing works. Good luck is there any way for you to update the fix. I don’t live near a store so I will be sending mine in.

I have the same issue. Took it to the Genius Bar today and was told the connection was bad - Error 6 so it cannot be updated. The iPad Pro is only 3 years old. How is it okay for them to tell me to buy a new iPad when the problem happened with their update?

I'm affected too.

I unbrick it, now i'm trying to recover it, bar doesn't move again.

[Edited by Moderator]

I’m bricked too from the update - multiple attempts at force restart and no luck