I've numbered each point – as there are a lot – in the hope it makes it easier to reply or ask me for further info. Thanks!
- The Problem
- What I've Tried So Far...
- Next Steps?
- 2018 MBP Will not boot using Internet Recovery, nor any other type of Recovery thus far.
- Get variety of errors - 1008f, 2300f, 2100f.
- 2018 MBP is running Big Sur (possibly a recent beta version, icr)
- Have updated 2011 iMac to High Sierra 10.13.6. It's moving slowly, but it's definitely moving. It's a 3.4 GHz Intel Core i7, 8 GB 1333 MHz DDR3, plenty of free disk space - 1.76TB.
- I have most important stuff on the MBP backed up, but concerned due to medical reasons that vital things may not have been backed up in recent times - my eye has been off the ball somewhat...
- I really want to access the Data on the MBP if I possibly can.
- I fear the Logic Board might be on it's way, but hope I can salvage something.
What I've Tried Already
- Updated iMac to HS, to create bootable installer of High Sierra using Terminal commands. It's Extended Volume, not AFPS. Can make another in AFPS if it will remotely help.
- MBP did not boot to it. Still brings up Network prompt which ultimately seems to cause the fail each time.
- MBP appears to process connecting the MBP to WiFi Network each time, but then produces variety of error codes at the end, even when using bootable installer and Option key. 12 Have even put entire High Sierra OS on external drive, endeavouring to effectively use external drive as a Mac Mini with ailing MBP just the screen. Nope. Still wants to connect to to Network (this is for the Firmware, afaik?)
- Have today connected MBP to iMac using Thunderbolt 3 cable and USB-C to Thunderbolt adaptor.
- Endeavouring to boot using Target Disk Mode.
- Can see MBP Macintosh HD - Data in Disk Utility, but cannot perform First Aid, nor Mount it. IMAGE BELOW
- Also have a Drive titled Update in externals, which seems to show the Data and ?(Big Sur beta update?) maybe? (I haven't called it Update, and I'm not quite sure what it is) IMAGE BELOW
- Tried Terminal commands to Verify Data, getting a variety of Permission Denied errors. IMAGE BELOW
- Tried \\ diskutil verifyDisk disk2 \\ which gives: Unable to verify this whole disk: A GUID Partition Table (GPT) partitioning scheme is required (-69773)
- Tried \\ diskutil verifyDisk disk2s1 \\ (that's the volume(?) with the data on) which gives: "A whole disk must be specified"
- <mutters 'make your bloody mind up...'>
- Downloaded iBoysoft to try and recover data.
- It can see the Data, but there's a padlock on the Drive and it's asking: "Please enter the password of your encrypted APFS partition" IMAGE BELOW
- Wondering if this is a FireVault thing? I'm not sure if it's switched on, on the MBP or not. If it is, I have absolutely no idea what the encrypted partition password is, nor where I'd find such information.
- Apparently, I can run iBoysoft Data Recovery in macOS Recovery mode.
- I'm not sure if this will be complicated because I am also using Target Disk Mode, rather than running iBoysoft directly on the affected MBP, because I can't. A search of the iBoysoft FAQs fails to offer an answer to this query.
- Is there any point in creating another Bootable Installer, this time as APFS, rather than Extended Volume?
- Where can I find the encrypted APFS password info? (I'm not convinced I have one, but it may have switched on by default?) I am a devil for recording passwords so if I was aware this existed, I absolutely would have made a note of it. What would it look like format-wise?
- And where would I enter it for the Disk Utility or Terminal to be able to access 'MBP Macintosh HD - Data'?
- Would entering the command prompt \\ sudo Fsck_APFS /dev/disk2s1 \\ do anything helpful?
- I have a 2019 MBP running Big Sur which thoughtfully simultaneously fell over. This happened while I was awaiting delivery of the super-fast Thunderbolt 3 cable to do the data transfer. It has refused to switch on since, so I am pretty much stuck with the 2011 iMac as rescuer for now. (And yes, I've tried all the usual suspects NVRAM, SMC on the dead second MBP etc)
I am an absolute novice at all of this, so please speak ** s l o w l y ** to me in simple terms. This is my first post and I'm doing my best...