iPhone iOS 13.3'[NSPOSIXErrorDomain – 0x1C (28)]'iPhone XS Max Found it stuck at the apple logo in the morning...

[JhnsSch]

iPhone XS Max iOS 13.3 I found it stuck at the apple logo in the morning, whilst my new iPhone was literally laying on the same desk (still sealed), waiting for me to make a backup of the XS Max in the morning, in order to then transfer my data to the new 11 Pro Max..

It did not reboot, I tried restarting it - that didn't work, I tried giving it some time - that didn't work, draining the battery - left me where I started when plugging into a power outlet.

I then tried to use iTunes to update the phone manually, reinstall iOS 13.3 such that I keep my data, however the XS Max is stuck with 'unknown error occurred (47)'

My data is on there - access to my data is denied..!

| There’s no need for anyone to mention the fact that I should have had a backup, I do have an iCloud backup, this would give me access to some apps that I need to have access to, however it would mean losing 400GB of images stored on this phone. |

| In case someone is wondering why those images are not stored in iCloud - well, at this point I'm wondering, if I may be the only person that found and enabled the 4K at 60fps Video setting years ago (before Apple just recently included it in the default camera app). In that case, there is just no way for anyone, to treat the 2TB of iCloud Fotos storage as anything but a laughing stock. ..& I'm truly grateful for anyone who thinks of bringing up Google Fotos. Thank you, I pass. |

 

[TiggrToo]

Hate the be the bearer of bad news, but error 47 used to indicate a hardware failure in the baseband chipset.

If a DFU isn't working AND you've rebooted the computer you're connected to, AND you've tried different cables & ports then...

Do you have Apple Care or a warranty on the device?

You might also have to consider all the data lost on it as, even if Apple agree to deal with it, it's far more likely that they'll just swap it for a replacement. If it is the baseband hardware then they'll probably not attempt to fix it.

You may get better luck at an independent repair shop who are far more likely (for a price) pull the chip out and make a fix. However if you do find yourself going down this road then you should ascertain if such a fix will wipe any data.

Another option might be if the repair shop can at least get you to the where the phone boots in a harness to the point where you can at least download the pictures.

Brace yourself.

 

[JhnsSch]

That is big news..

Thank you for your elaborate and conclusive response!

..I meanwhile tried some steps to make ground in some way. In that I noticed the iPhone getting strangely hot in the area marked in the attached image, reminding me of the 6s Plus which had that Touch IC issue causing my unit to get super hot in exactly the spot.
I know the internals are different, however I wanted to mention that, because I think it supports what you said? That the reason is likely some

hardware failure in the baseband chipset

Apple Device Manager 2 meanwhile provided me with what I assume is the complete/ real error code:

(AMRestoreErrorDomain-Fehler 47 - Failed to handle message type StatusMsg) [AMRestoreErrorDomain – 0x2F (47)]

I tried using AC2 in order to get device information and try to update the installed iOS that way.

 

[JhnsSch]

Meanwhile.. I found something useful on discussions.apple.com, which is somewhat of a highlight itself, cause (at least in my case) that has not ever happened before. 🥳

User L8N-JR

After following these steps, I got further than ever before.
After AC2 unpacked iOS (step 3/4) & everything seemed promising. Then my MacBook told me that my storage was full.

Which is weird, I had about 17GB free storage when starting the repair operation in AC2 & the 5,3GB of iOS 13.3 were downloaded already.
I was forced to reboot, given my Macbook told me it had only 62.4MB of available storage:

Before that, I was just able to obtain another error code:

The operation could not be finalised. There is no file and no such folder. [NSPOSIXErrorDomain – 0x2 (2)]

Then I rebooted my Macbook. 🥳 Surprise:

Short aside
- It seems like my iPhone has never heard of error 47 at this point -​

Well, here we go again:

The operation could not be finalised. There is no storage available on the device. [NSPOSIXErrorDomain – 0x1C (28)]

Without having any real idea what that might mean,
and my research being unsuccessful..

It sound like my iPhone tired to update to iOS 13.3 & crashed, because in the process of doing that, it all of the sudden noticed that there's not enough storage to complete the update?

Hence it is unable to finish the update process, because it lacks storage space available to install iOS 13.3?

Well, that kind of does make sense, as my iPhone did tell me, available storage is low, that day before it 'left' whilst I was asleep..

t.b.c.​

 

[lgjay]

Well, that kind of does make sense, as my iPhone did tell me, available storage is low, that day before it 'left' whilst I was asleep..

Recent years I have noticed that iOS and MacOS would often leave a device stuck while booting or stuck in boot loop when the device is critical low on storage. My late 2013 rmbp and iPhone 7 Plus had both experienced the issue.

I guess there were some fatal flaws in the way how Apple designed their software for handling low storage situations which lead to their devices having such issues.

Luckily, for the MacBook I was able to clone and restore the internal disk which somehow fixed the issue. And for the iPhone 7 Plus I was able to DFU the phone and restore backup.

 

[Jen52081]

Meanwhile.. I found something useful on discussions.apple.com, which is somewhat of a highlight itself, cause (at least in my case) that has not ever happened before. ?

User L8N-JR
View attachment 889376
After following these steps, I got further than ever before.
After AC2 unpacked iOS (step 3/4) & everything seemed promising. Then my MacBook told me that my storage was full.
View attachment 889379
Which is weird, I had about 17GB free storage when starting the repair operation in AC2 & the 5,3GB of iOS 13.3 were downloaded already.
I was forced to reboot, given my Macbook told me it had only 62.4MB of available storage:
View attachment 889378
Before that, I was just able to obtain another error code:

Then I rebooted my Macbook. ? Surprise:
View attachment 889380

Short aside
- It seems like my iPhone has never heard of error 47 at this point -​

Well, here we go again:

Without having any real idea what that might mean,
and my research being unsuccessful..

It sound like my iPhone tired to update to iOS 13.3 & crashed, because in the process of doing that, it all of the sudden noticed that there's not enough storage to complete the update?

Hence it is unable to finish the update process, because it lacks storage space available to install iOS 13.3?

Well, that kind of does make sense, as my iPhone did tell me, available storage is low, that day before it 'left' whilst I was asleep..

t.b.c.​

This thing literally happened to me. Were you able to get your photos and videos?
[automerge]1591717471[/automerge]
I had the same thing happen to me as described above. I have an iPhone XS Max 512 G. I love photos and videos and have 2 very young kids and captured their most treasured moments. Because I was worried iCloud backup would take forever an it's a large phone with a lot of data and since iCloud doesn't keep things that are off your phone, I decided to go the route of periodically just taking things off the phone and putting it on an external hard drive (and having a back up external hard drive as well). I tried unsuccessfully to take things off my phone 2 weeks ago since I was getting messages about it being close to full but it kept working (texts, emails, apps all worked fine). Then 3 days ago some of the apps weren't working and my Safari tabs were all closed but I checked and all of my videos and photos were there, so I restarted my phone and it never fully came back on - just the black screen w the white Apple logo. After 3 hours w Apple and trying to update the software (it downloaded 4.9G of something and gets to the progress bar each time with a speck of progress) it then stops and says "The iPhone "iPhone" could not be updated. An unknown error occurred (47)." Now I'm left with the screen either with the black background and white Apple logo or the black screen with the white link to support.apple.com/iphone/restore at the top. I have NOT done a restore of the phone so my data should all be on there. I so desperately want my photos and videos back. I would do anything for them. Apple recommended I send my phone to Ontrack.com. Anyone had success with retrieving photos and videos from this state? From the above link it looks like the "(47)" error maybe a hardware issue which I'm hoping will be able to fix. This whole experience has been devastating and making me more paranoid about back ups no matter how it's done. Anyone have any suggestions for retrieving my photos and videos?

 

[Natya Sadella]

Try icloud.com on your computer, all your photos are synced

 

[Jen52081]

Than you so much for responding. My iCloud only seems to have 16 photos and nothing else sadly. Has anyone successfully overcome "Error (47)" to retrieve photos and videos?
[automerge]1591797069[/automerge]

iPhone XS Max iOS 13.3 I found it stuck at the apple logo in the morning, whilst my new iPhone was literally laying on the same desk (still sealed), waiting for me to make a backup of the XS Max in the morning, in order to then transfer my data to the new 11 Pro Max..

It did not reboot, I tried restarting it - that didn't work, I tried giving it some time - that didn't work, draining the battery - left me where I started when plugging into a power outlet.

I then tried to use iTunes to update the phone manually, reinstall iOS 13.3 such that I keep my data, however the XS Max is stuck with 'unknown error occurred (47)'

My data is on there - access to my data is denied..!

Were you ever able to get your photos and videos? I am having the exact same challenge w the XS Max and "Error (47)"