Apple Silicon Soldered SSD Upgrade Thread

[waterchill]

I will try to reball tomorrow and try again. SDSF will not work K5A8 also not working.

 

[Bassy_92]

Hi folks,

today I got another M4 Air for an upgrade. But this MacBook didn’t have the usual K5A3 NANDs – instead it came with SDFRL5 chips. First, I tried replacing them with SDSFGK 1TB, but the restore failed. After that, I tried K5A8, same error. Then I tried K8A5 – the error was different this time, but still couldn’t restore. So I soldered back the original NANDs, and the restore worked perfectly fine.

My P15 programmer reports all the NANDs as OK, except the K8A5 which throws an error (apparently that’s normal with these chips). Any ideas what could be going on?

I have purchased a set of k8a5’s recently (sold as brand new). When inspecting the NANDs they did appear to look brand new and no signs of previously being soldered. However when I checked them with p15 I don’t get any errors, but they do show up as “incomplete partition” as tho they had been written on previous. Really odd

So my guess would be they it’s a set of bad NANDs if you are getting an error

 

[waterchill]

This message is normal, JCID have not updated they library for this NAND's

 

[mlucianoeze]

Hey there! Sorry if this isn't the right place to ask this, but have any of you had any experience with K5A5 before?

I currently have a base model Mac mini M4 with 256GB of storage, and planning to buy next month a MacBook Air M4 with 24GB RAM and 512GB. I want to upgrade both of them to 1TB each, so I'll go for 4xK5A5.

I've found this supplier that claims their chips are empty, but states that they need to be programmed manually. I assume that this is going to be done when restoring through DFU, right? So I won't need a NAND programmer I guess.

The thing is, I have a rather tight budget and I can't buy the programmer "just in case" (and even if I did, I'd need dump configs for both the mini and the MBA), so I really need to trust those chips are actually blank. I know I can't know that for sure, but if you've bought any K5A5 and want to recommend any supplier that had worked in the past, it'd be really appreciated

 

[Sauve Mon Mac]

You’re right, no need to program, they’ll be empty and DFU restore should work.

 

[mlucianoeze]

You’re right, no need to program, they’ll be empty and DFU restore should work.

Cool, thanks! I guess it boils down to trusting the supplier then. In your opinion, do you think the one I linked looks reliable? Do you have any other recommendations that have worked for you in the past?

 

[Wedlock]

First if i am going off topic with my question in this thread please delete me.

Anyway i wanted to upgrade my Studio M1 Max with a 2tb module from my standard 512gb config.
I contacted Polysoft asking when they would get new modules ready for pre-order but didn’t get a response.
Now i saw a seller on Aliexpress which sells 2tb for around 390 euro’s.
Now did anybody get a chance to try these and is it trustworthy to buy them ?

 

[maflynn]

I contacted Polysoft asking when they would get new modules ready for pre-order but didn’t get a response.
Now i saw a seller on Aliexpress which sells 2tb for around 390 euro’s.

Check out this thread. The post I pointed you towards is a member who actually bought an ali express nand upgrade module. Further back in the thread there's another member with screen shots.

I understand your hesitation with ali express, I voiced the same concerns in the thread I linked too. I will say however that people are seemingly happy with their purchases.

Looks like as I was pulling up the url info for my reply I see giles responding. He's largely been absent in providing any sort of feedback and polysoft seems perpetually out of stock. At this point I wonder if he's just sourcing them from the same locations as the Ali Express people

 

[Wedlock]

Thanks for your reply Maflynn.

I checked the link out and i am more confident in buying from Aliexpress now than before. I would have gladly ordered from Giles as i think he has an excellent track record. But since his personal situation and that all the ssd's are out of stock plus he never replied to my message i send through the website i think i have to go with Ali to source the modules.
Most likely i end up getting the 2 TB module from that seller the other member linked to so we shall see what i get in the mail

 

[Wefix]

Hi! Just want to share info. Today I’ve tried to move 2tb config (4xHN3T2DT8) from a2780 m2pro to a2992 m3pro and it doesn’t work. Can’t restore through DFU. Soldered back 512gb config to a2992 and it started as usual without flashing. HN3T2DT8 Was 100% working , I’m removed them from iCloud donor board. Btw there is no blank Hynix dump, so in this way Hynix is not interchangeable on different cpu models.

And here is the question. I can order from China 4xK5A5 chips for my a2992 m3pro and get 2tb config, but I saw on everymac that’s a2992 could be 4tb config. Someone knows what kind of 4pcs nand I need to get 4tb config on m3 pro?

 

[dosdude1]

Hi! Just want to share info. Today I’ve tried to move 2tb config (4xHN3T2DT8) from a2780 m2pro to a2992 m3pro and it doesn’t work. Can’t restore through DFU. Soldered back 512gb config to a2992 and it started as usual without flashing. HN3T2DT8 Was 100% working , I’m removed them from iCloud donor board. Btw there is no blank Hynix dump, so in this way Hynix is not interchangeable on different cpu models.

And here is the question. I can order from China 4xK5A5 chips for my a2992 m3pro and get 2tb config, but I saw on everymac that’s a2992 could be 4tb config. Someone knows what kind of 4pcs nand I need to get 4tb config on m3 pro?

4x K5A8 will get you 4TB on M3 Pro.

 

[YSE]

On A2992 I tried to upgrade from 1TB 4 NANDs set to 2TB 2 K5A8 NANDs set, I have programmed them with jc p15 as blank & also tried with dosdude1 k5a8 blank dump. at first it didn't switch from DFU mode to recovery mode, because I was on 15.3, I updated to 15.6.1. and now it gives this error below. does Apple blocked SSD upgrades with the new version?

11:18:12.6863] entering clean_NAND


[11:18:12.6863] DKIOCFORMAT ioctl failed: Input/output error


[11:18:12.6863] Disk format failure detail: This configuration is not supported on this device.


[11:18:12.6863] [00:01:31.0781-GMT]{5>7} CHECKPOINT FAILUREFAILURE:35) RESTORED:[0x064E] clean_nand [0]D(failed to clean NAND)


[11:18:12.6863] restore-step-results = {0x1107064E:{0:35}}


[11:18:12.6863] restore-step-codes = {0x1107064E:{0:35}}


[11:18:12.6863] restore-step-domains = {0x1107064E:{0:"AMRestoreErrorDomain"}}


[11:18:12.6863] restore-step-error = {0x1107064E:"[0]D(failed to clean NAND)"}


[11:18:12.6863] restore-step-uptime = 28


[11:18:12.6863] restore-step-user-progress = 0


[11:18:12.6863] [00:01:31.0782-GMT]{5>7} CHECKPOINT NOTICE: (NVRAM set) restore-step-user-progress=0 [sync=true] (first failure)


[11:18:12.6863] [00:01:31.0782-GMT]{5>7} CHECKPOINT BEGIN: RESTORED:[0x067C] cleanup_boot_command


[11:18:12.6863] restore-step-ids = {0x1103064E:44;0x1103067C:45}


[11:18:12.6863] restore-step-names = {0x1103064E:clean_nand;0x1103067C:cleanup_boot_command}


[11:18:12.6863] restore-step-uptime = 28


[11:18:12.6863] restore-step-user-progress = 0


[11:18:12.6863] entering reset_boot_command_if_in_values


[11:18:12.6863] 40A0DDD2-77F8-4392-B4A3XXXXXXXXX6516:recovery-boot-mode = <delete>


[11:18:12.6863] 40A0DDD2-77F8-4392-B4A3XXXXXXXXX6516:iboot-failure-reason = <delete>


[11:18:12.6863] [00:01:31.0782-GMT]{5>7} CHECKPOINT END: RESTORED:[0x067C] cleanup_boot_command


[11:18:12.6863] restore-step-ids = {0x1103064E:44}


[11:18:12.6863] restore-step-names = {0x1103064E:clean_nand}


[11:18:12.6863] restore-step-uptime = 28


[11:18:12.6863] restore-step-user-progress = 0


[11:18:12.6863] [00:01:31.0782-GMT]{5>7} CHECKPOINT BEGIN: RESTORED:[0x1613] cleanup_recovery_os_volume


[11:18:12.6863] restore-step-ids = {0x1103064E:44;0x11031613:46}


[11:18:12.6863] restore-step-names = {0x1103064E:clean_nand;0x11031613:cleanup_recovery_os_volume}


[11:18:12.6863] restore-step-uptime = 28


[11:18:12.6863] restore-step-user-progress = 0


[11:18:12.6863] [00:01:31.0783-GMT]{5>7} CHECKPOINT END: RESTORED:[0x1613] cleanup_recovery_os_volume


[11:18:12.6863] restore-step-ids = {0x1103064E:44}


[11:18:12.6863] restore-step-names = {0x1103064E:clean_nand}


[11:18:12.6863] restore-step-uptime = 28


[11:18:12.6863] restore-step-user-progress = 0


[11:18:12.6863] [00:01:31.0783-GMT]{5>7} CHECKPOINT BEGIN: RESTORED:[0x0647] cleanup_check_result


[11:18:12.6863] restore-step-ids = {0x1103064E:44;0x11030647:47}


[11:18:12.6863] restore-step-names = {0x1103064E:clean_nand;0x11030647:cleanup_check_result}


[11:18:12.6863] restore-step-uptime = 28


[11:18:12.6863] restore-step-user-progress = 0


[11:18:12.6863] [00:01:31.0783-GMT]{5>7} CHECKPOINT END: RESTORED:[0x0647] cleanup_check_result


[11:18:12.6863] restore-step-ids = {0x1103064E:44}


[11:18:12.6863] restore-step-names = {0x1103064E:clean_nand}


[11:18:12.6863] restore-step-uptime = 28


[11:18:12.6863] restore-step-user-progress = 0


[11:18:12.6863] [00:01:31.0783-GMT]{5>7} CHECKPOINT BEGIN: RESTORED:[0x06C2] cleanup_send_crash_logs


[11:18:12.6863] restore-step-ids = {0x1103064E:44;0x110306C2:48}


[11:18:12.6863] restore-step-names = {0x1103064E:clean_nand;0x110306C2:cleanup_send_crash_logs}


[11:18:12.6863] restore-step-uptime = 28


[11:18:12.6863] restore-step-user-progress = 0


[11:18:12.6863] [00:01:31.0784-GMT]{5>7} CHECKPOINT END: RESTORED:[0x06C2] cleanup_send_crash_logs


[11:18:12.6863] restore-step-ids = {0x1103064E:44}


[11:18:12.6863] restore-step-names = {0x1103064E:clean_nand}


[11:18:12.6863] restore-step-uptime = 28


[11:18:12.6863] restore-step-user-progress = 0


[11:18:12.6863] [00:01:31.0784-GMT]{5>7} CHECKPOINT BEGIN: RESTORED:[0x0648] cleanup_send_final_status


[11:18:12.6863] restore-step-ids = {0x1103064E:44;0x11030648:49}


[11:18:12.6863] restore-step-names = {0x1103064E:clean_nand;0x11030648:cleanup_send_final_status}


[11:18:12.6863] restore-step-uptime = 28


[11:18:12.6863] restore-step-user-progress = 0


[11:18:12.6863] gress = 0


[11:18:12.6863]


[11:18:12.6863] ==== end of device restore output ====


[11:18:12.6875] sock 21: closed


[11:18:12.6875] AMRAuthInstallDeletePersonalizedBundle


[11:18:12.6875] preserved personalized bundle: (null)


[11:18:12.6875] <Restore Device 0x6ac810000>: Restore failed (result = 35)


[11:18:12.6875] Can't send dump_console command since device is not in recovery mode


[11:18:12.6876] Finished RestoreOS Restore Phase: Failed


[11:18:12.6876] State Machine Dump, status:ERROR - [stateFU remaining-cycles:1] -> [state:Recovery remaining-cycles:0] -> [state:RestoreOS remaining-cycles:0 (current state)]


[11:18:12.6881] Changing state from 'Restoring' to 'Error'


[11:18:12.6881] State is now set to error: AMRestorePerformRestoreModeRestoreWithError failed with error: 35


[11:18:12.6895] Restore completed, status: 35


[11:18:12.6895] Elapsed time (in seconds): 68


[11:18:12.6895] Restore Checkpoint Fingerprint: 064E.0023


[11:18:12.6895] Failure Description:


[11:18:12.6895] Depth:0 Code:-1 Error:AMRestorePerformRestoreModeRestoreWithError failed with error: 35


[11:18:12.6895] Depth:1 Code:35 Error:Failed to handle message type StatusMsg (An error occurred while formatting the NAND)


[11:18:12.6895] Depth:2 Code:35 Error:failed to clean NAND

 

[Wefix]

On A2992 I tried to upgrade from 1TB 4 NANDs set to 2TB 2 K5A8 NANDs set, I have programmed them with jc p15 as blank & also tried with dosdude1 k5a8 blank dump. at first it didn't switch from DFU mode to recovery mode, because I was on 15.3, I updated to 15.6.1. and now it gives this error below. does Apple blocked SSD upgrades with the new version?

11:18:12.6863] entering clean_NAND


[11:18:12.6863] DKIOCFORMAT ioctl failed: Input/output error


[11:18:12.6863] Disk format failure detail: This configuration is not supported on this device.


[11:18:12.6863] [00:01:31.0781-GMT]{5>7} CHECKPOINT FAILUREFAILURE:35) RESTORED:[0x064E] clean_nand [0]D(failed to clean NAND)


[11:18:12.6863] restore-step-results = {0x1107064E:{0:35}}


[11:18:12.6863] restore-step-codes = {0x1107064E:{0:35}}


[11:18:12.6863] restore-step-domains = {0x1107064E:{0:"AMRestoreErrorDomain"}}


[11:18:12.6863] restore-step-error = {0x1107064E:"[0]D(failed to clean NAND)"}


[11:18:12.6863] restore-step-uptime = 28


[11:18:12.6863] restore-step-user-progress = 0


[11:18:12.6863] [00:01:31.0782-GMT]{5>7} CHECKPOINT NOTICE: (NVRAM set) restore-step-user-progress=0 [sync=true] (first failure)


[11:18:12.6863] [00:01:31.0782-GMT]{5>7} CHECKPOINT BEGIN: RESTORED:[0x067C] cleanup_boot_command


[11:18:12.6863] restore-step-ids = {0x1103064E:44;0x1103067C:45}


[11:18:12.6863] restore-step-names = {0x1103064E:clean_nand;0x1103067C:cleanup_boot_command}


[11:18:12.6863] restore-step-uptime = 28


[11:18:12.6863] restore-step-user-progress = 0


[11:18:12.6863] entering reset_boot_command_if_in_values


[11:18:12.6863] 40A0DDD2-77F8-4392-B4A3XXXXXXXXX6516:recovery-boot-mode = <delete>


[11:18:12.6863] 40A0DDD2-77F8-4392-B4A3XXXXXXXXX6516:iboot-failure-reason = <delete>


[11:18:12.6863] [00:01:31.0782-GMT]{5>7} CHECKPOINT END: RESTORED:[0x067C] cleanup_boot_command


[11:18:12.6863] restore-step-ids = {0x1103064E:44}


[11:18:12.6863] restore-step-names = {0x1103064E:clean_nand}


[11:18:12.6863] restore-step-uptime = 28


[11:18:12.6863] restore-step-user-progress = 0


[11:18:12.6863] [00:01:31.0782-GMT]{5>7} CHECKPOINT BEGIN: RESTORED:[0x1613] cleanup_recovery_os_volume


[11:18:12.6863] restore-step-ids = {0x1103064E:44;0x11031613:46}


[11:18:12.6863] restore-step-names = {0x1103064E:clean_nand;0x11031613:cleanup_recovery_os_volume}


[11:18:12.6863] restore-step-uptime = 28


[11:18:12.6863] restore-step-user-progress = 0


[11:18:12.6863] [00:01:31.0783-GMT]{5>7} CHECKPOINT END: RESTORED:[0x1613] cleanup_recovery_os_volume


[11:18:12.6863] restore-step-ids = {0x1103064E:44}


[11:18:12.6863] restore-step-names = {0x1103064E:clean_nand}


[11:18:12.6863] restore-step-uptime = 28


[11:18:12.6863] restore-step-user-progress = 0


[11:18:12.6863] [00:01:31.0783-GMT]{5>7} CHECKPOINT BEGIN: RESTORED:[0x0647] cleanup_check_result


[11:18:12.6863] restore-step-ids = {0x1103064E:44;0x11030647:47}


[11:18:12.6863] restore-step-names = {0x1103064E:clean_nand;0x11030647:cleanup_check_result}


[11:18:12.6863] restore-step-uptime = 28


[11:18:12.6863] restore-step-user-progress = 0


[11:18:12.6863] [00:01:31.0783-GMT]{5>7} CHECKPOINT END: RESTORED:[0x0647] cleanup_check_result


[11:18:12.6863] restore-step-ids = {0x1103064E:44}


[11:18:12.6863] restore-step-names = {0x1103064E:clean_nand}


[11:18:12.6863] restore-step-uptime = 28


[11:18:12.6863] restore-step-user-progress = 0


[11:18:12.6863] [00:01:31.0783-GMT]{5>7} CHECKPOINT BEGIN: RESTORED:[0x06C2] cleanup_send_crash_logs


[11:18:12.6863] restore-step-ids = {0x1103064E:44;0x110306C2:48}


[11:18:12.6863] restore-step-names = {0x1103064E:clean_nand;0x110306C2:cleanup_send_crash_logs}


[11:18:12.6863] restore-step-uptime = 28


[11:18:12.6863] restore-step-user-progress = 0


[11:18:12.6863] [00:01:31.0784-GMT]{5>7} CHECKPOINT END: RESTORED:[0x06C2] cleanup_send_crash_logs


[11:18:12.6863] restore-step-ids = {0x1103064E:44}


[11:18:12.6863] restore-step-names = {0x1103064E:clean_nand}


[11:18:12.6863] restore-step-uptime = 28


[11:18:12.6863] restore-step-user-progress = 0


[11:18:12.6863] [00:01:31.0784-GMT]{5>7} CHECKPOINT BEGIN: RESTORED:[0x0648] cleanup_send_final_status


[11:18:12.6863] restore-step-ids = {0x1103064E:44;0x11030648:49}


[11:18:12.6863] restore-step-names = {0x1103064E:clean_nand;0x11030648:cleanup_send_final_status}


[11:18:12.6863] restore-step-uptime = 28


[11:18:12.6863] restore-step-user-progress = 0


[11:18:12.6863] gress = 0


[11:18:12.6863]


[11:18:12.6863] ==== end of device restore output ====


[11:18:12.6875] sock 21: closed


[11:18:12.6875] AMRAuthInstallDeletePersonalizedBundle


[11:18:12.6875] preserved personalized bundle: (null)


[11:18:12.6875] <Restore Device 0x6ac810000>: Restore failed (result = 35)


[11:18:12.6875] Can't send dump_console command since device is not in recovery mode


[11:18:12.6876] Finished RestoreOS Restore Phase: Failed


[11:18:12.6876] State Machine Dump, status:ERROR - [stateFU remaining-cycles:1] -> [state:Recovery remaining-cycles:0] -> [state:RestoreOS remaining-cycles:0 (current state)]


[11:18:12.6881] Changing state from 'Restoring' to 'Error'


[11:18:12.6881] State is now set to error: AMRestorePerformRestoreModeRestoreWithError failed with error: 35


[11:18:12.6895] Restore completed, status: 35


[11:18:12.6895] Elapsed time (in seconds): 68


[11:18:12.6895] Restore Checkpoint Fingerprint: 064E.0023


[11:18:12.6895] Failure Description:


[11:18:12.6895] Depth:0 Code:-1 Error:AMRestorePerformRestoreModeRestoreWithError failed with error: 35


[11:18:12.6895] Depth:1 Code:35 Error:Failed to handle message type StatusMsg (An error occurred while formatting the NAND)


[11:18:12.6895] Depth:2 Code:35 Error:failed to clean NAND

seems that you need 4x k5a5.

 

[YSE]

seems that you need 4x k5a8 or 4x k5a5. I've saw 2 bank config only on A2779 macbooks

on JC tool they say it will be good for this model, probably it's their mistake

 

[YSE]

Also on T2 machines I was always soldered less NANDs than originally was before successfully. so M1+ is different I guess?

 

[Wefix]

on JC tool they say it will be good for this model, probably it's their mistake View attachment 2547043

I think it's mistake. There wasn't m3pro with 2 banks. 512 use 4 banks, also 1-4tb also uses 4 banks

 

[dosdude1]

On A2992 I tried to upgrade from 1TB 4 NANDs set to 2TB 2 K5A8 NANDs set, I have programmed them with jc p15 as blank & also tried with dosdude1 k5a8 blank dump. at first it didn't switch from DFU mode to recovery mode, because I was on 15.3, I updated to 15.6.1. and now it gives this error below. does Apple blocked SSD upgrades with the new version?

11:18:12.6863] entering clean_NAND


[11:18:12.6863] DKIOCFORMAT ioctl failed: Input/output error


[11:18:12.6863] Disk format failure detail: This configuration is not supported on this device.


[11:18:12.6863] [00:01:31.0781-GMT]{5>7} CHECKPOINT FAILUREFAILURE:35) RESTORED:[0x064E] clean_nand [0]D(failed to clean NAND)


[11:18:12.6863] restore-step-results = {0x1107064E:{0:35}}


[11:18:12.6863] restore-step-codes = {0x1107064E:{0:35}}


[11:18:12.6863] restore-step-domains = {0x1107064E:{0:"AMRestoreErrorDomain"}}


[11:18:12.6863] restore-step-error = {0x1107064E:"[0]D(failed to clean NAND)"}


[11:18:12.6863] restore-step-uptime = 28


[11:18:12.6863] restore-step-user-progress = 0


[11:18:12.6863] [00:01:31.0782-GMT]{5>7} CHECKPOINT NOTICE: (NVRAM set) restore-step-user-progress=0 [sync=true] (first failure)


[11:18:12.6863] [00:01:31.0782-GMT]{5>7} CHECKPOINT BEGIN: RESTORED:[0x067C] cleanup_boot_command


[11:18:12.6863] restore-step-ids = {0x1103064E:44;0x1103067C:45}


[11:18:12.6863] restore-step-names = {0x1103064E:clean_nand;0x1103067C:cleanup_boot_command}


[11:18:12.6863] restore-step-uptime = 28


[11:18:12.6863] restore-step-user-progress = 0


[11:18:12.6863] entering reset_boot_command_if_in_values


[11:18:12.6863] 40A0DDD2-77F8-4392-B4A3XXXXXXXXX6516:recovery-boot-mode = <delete>


[11:18:12.6863] 40A0DDD2-77F8-4392-B4A3XXXXXXXXX6516:iboot-failure-reason = <delete>


[11:18:12.6863] [00:01:31.0782-GMT]{5>7} CHECKPOINT END: RESTORED:[0x067C] cleanup_boot_command


[11:18:12.6863] restore-step-ids = {0x1103064E:44}


[11:18:12.6863] restore-step-names = {0x1103064E:clean_nand}


[11:18:12.6863] restore-step-uptime = 28


[11:18:12.6863] restore-step-user-progress = 0


[11:18:12.6863] [00:01:31.0782-GMT]{5>7} CHECKPOINT BEGIN: RESTORED:[0x1613] cleanup_recovery_os_volume


[11:18:12.6863] restore-step-ids = {0x1103064E:44;0x11031613:46}


[11:18:12.6863] restore-step-names = {0x1103064E:clean_nand;0x11031613:cleanup_recovery_os_volume}


[11:18:12.6863] restore-step-uptime = 28


[11:18:12.6863] restore-step-user-progress = 0


[11:18:12.6863] [00:01:31.0783-GMT]{5>7} CHECKPOINT END: RESTORED:[0x1613] cleanup_recovery_os_volume


[11:18:12.6863] restore-step-ids = {0x1103064E:44}


[11:18:12.6863] restore-step-names = {0x1103064E:clean_nand}


[11:18:12.6863] restore-step-uptime = 28


[11:18:12.6863] restore-step-user-progress = 0


[11:18:12.6863] [00:01:31.0783-GMT]{5>7} CHECKPOINT BEGIN: RESTORED:[0x0647] cleanup_check_result


[11:18:12.6863] restore-step-ids = {0x1103064E:44;0x11030647:47}


[11:18:12.6863] restore-step-names = {0x1103064E:clean_nand;0x11030647:cleanup_check_result}


[11:18:12.6863] restore-step-uptime = 28


[11:18:12.6863] restore-step-user-progress = 0


[11:18:12.6863] [00:01:31.0783-GMT]{5>7} CHECKPOINT END: RESTORED:[0x0647] cleanup_check_result


[11:18:12.6863] restore-step-ids = {0x1103064E:44}


[11:18:12.6863] restore-step-names = {0x1103064E:clean_nand}


[11:18:12.6863] restore-step-uptime = 28


[11:18:12.6863] restore-step-user-progress = 0


[11:18:12.6863] [00:01:31.0783-GMT]{5>7} CHECKPOINT BEGIN: RESTORED:[0x06C2] cleanup_send_crash_logs


[11:18:12.6863] restore-step-ids = {0x1103064E:44;0x110306C2:48}


[11:18:12.6863] restore-step-names = {0x1103064E:clean_nand;0x110306C2:cleanup_send_crash_logs}


[11:18:12.6863] restore-step-uptime = 28


[11:18:12.6863] restore-step-user-progress = 0


[11:18:12.6863] [00:01:31.0784-GMT]{5>7} CHECKPOINT END: RESTORED:[0x06C2] cleanup_send_crash_logs


[11:18:12.6863] restore-step-ids = {0x1103064E:44}


[11:18:12.6863] restore-step-names = {0x1103064E:clean_nand}


[11:18:12.6863] restore-step-uptime = 28


[11:18:12.6863] restore-step-user-progress = 0


[11:18:12.6863] [00:01:31.0784-GMT]{5>7} CHECKPOINT BEGIN: RESTORED:[0x0648] cleanup_send_final_status


[11:18:12.6863] restore-step-ids = {0x1103064E:44;0x11030648:49}


[11:18:12.6863] restore-step-names = {0x1103064E:clean_nand;0x11030648:cleanup_send_final_status}


[11:18:12.6863] restore-step-uptime = 28


[11:18:12.6863] restore-step-user-progress = 0


[11:18:12.6863] gress = 0


[11:18:12.6863]


[11:18:12.6863] ==== end of device restore output ====


[11:18:12.6875] sock 21: closed


[11:18:12.6875] AMRAuthInstallDeletePersonalizedBundle


[11:18:12.6875] preserved personalized bundle: (null)


[11:18:12.6875] <Restore Device 0x6ac810000>: Restore failed (result = 35)


[11:18:12.6875] Can't send dump_console command since device is not in recovery mode


[11:18:12.6876] Finished RestoreOS Restore Phase: Failed


[11:18:12.6876] State Machine Dump, status:ERROR - [stateFU remaining-cycles:1] -> [state:Recovery remaining-cycles:0] -> [state:RestoreOS remaining-cycles:0 (current state)]


[11:18:12.6881] Changing state from 'Restoring' to 'Error'


[11:18:12.6881] State is now set to error: AMRestorePerformRestoreModeRestoreWithError failed with error: 35


[11:18:12.6895] Restore completed, status: 35


[11:18:12.6895] Elapsed time (in seconds): 68


[11:18:12.6895] Restore Checkpoint Fingerprint: 064E.0023


[11:18:12.6895] Failure Description:


[11:18:12.6895] Depth:0 Code:-1 Error:AMRestorePerformRestoreModeRestoreWithError failed with error: 35


[11:18:12.6895] Depth:1 Code:35 Error:Failed to handle message type StatusMsg (An error occurred while formatting the NAND)


[11:18:12.6895] Depth:2 Code:35 Error:failed to clean NAND

You cannot deviate from officially supported configs. 2x K5A8 is not a valid config on that machine, 2TB must be achieved using 4x K5A5. You can, however, achieve 4TB using 4x K5A8, assuming it is an M3 Pro model with only 4 NAND pads. M3 Max with 8 NAND pads requires different configs, such as 8x K5A5 for 4TB and 8x K5A8 for 8TB. 2TB and lower only use 4 NANDs on M3 Max.

 

[Bradonis]

Hi there, after upgrading my Macbook pro 16" m3 Pro i got some problems.
The laptop enters the DFU Mode but stucks at transitioning ... I tried several cables from USB C 2.0 over thunderbolt and the original Apple Thunderbolt 3.0 0,8m cable. it just ends with 4042 or 4047 error. maybe someone of you have an Idea? when i check the Voltage from the "Charger" it jumps every 3-4 seconds from 5 to 20V and back....


Hopefully the log will help. Best regards.

 

[Wefix]

Hi there, after upgrading my Macbook pro 16" m3 Pro i got some problems.
The laptop enters the DFU Mode but stucks at transitioning ... I tried several cables from USB C 2.0 over thunderbolt and the original Apple Thunderbolt 3.0 0,8m cable. it just ends with 4042 or 4047 error. maybe someone of you have an Idea? when i check the Voltage from the "Charger" it jumps every 3-4 seconds from 5 to 20V and back....


Hopefully the log will help. Best regards.

What kind and quantityof NANDs you’ve used for upgrade?

 

[Bradonis]

Hi,
I Ives 4x k5a5? So like one the first page recommended.

But there is no error in the log, that points on the nand.

I also tried another silicone Mac for restore und also with the configurator 2.

But actually no big difference

 

[YSE]

Hi there, after upgrading my Macbook pro 16" m3 Pro i got some problems.
The laptop enters the DFU Mode but stucks at transitioning ... I tried several cables from USB C 2.0 over thunderbolt and the original Apple Thunderbolt 3.0 0,8m cable. it just ends with 4042 or 4047 error. maybe someone of you have an Idea? when i check the Voltage from the "Charger" it jumps every 3-4 seconds from 5 to 20V and back....


Hopefully the log will help. Best regards.

what os version the mac you are using? i had the same issue which solved after upgrade it to the latest. also check if battery is connected & has a charge on the mac you are repairing

 

[Bradonis]

Hi, i tried 14.6… and 15.6.1. downloaded from ipsw.me? I tried it with external charger, without, with battery connected, without. I am unsure, how can bring him back to life

I also checked the Board with thermal camera and there is no real temperature increase. it stays about 30-40°.

Yeah ChatGPT told that there was a kind of hotfix from 14... to 15... because auf this transitioning error



PS. I just found this video:

at 4:34 he says, that a restore using the Keyboard DFU method wont work and tend to problems with brand new Chips. Could somebody confirm that?

 

[dosdude1]

Hi, i tried 14.6… and 15.6.1. downloaded from ipsw.me? I tried it with external charger, without, with battery connected, without. I am unsure, how can bring him back to life

I also checked the Board with thermal camera and there is no real temperature increase. it stays about 30-40°.

Yeah ChatGPT told that there was a kind of hotfix from 14... to 15... because auf this transitioning error



PS. I just found this video:

at 4:34 he says, that a restore using the Keyboard DFU method wont work and tend to problems with brand new Chips. Could somebody confirm that?

Just short SOC_FORCE_DFU pads. WAY easier than messing with the keyboard combos. Make sure you perform the restore under macOS Sonoma or later, using Finder and NOT Apple Configurator 2. That way you'll actually get logs in ~/Library/Logs/Mac Updater Logs.

 

[YSE]

Hi there, after upgrading my Macbook pro 16" m3 Pro i got some problems.
The laptop enters the DFU Mode but stucks at transitioning ... I tried several cables from USB C 2.0 over thunderbolt and the original Apple Thunderbolt 3.0 0,8m cable. it just ends with 4042 or 4047 error. maybe someone of you have an Idea? when i check the Voltage from the "Charger" it jumps every 3-4 seconds from 5 to 20V and back....


Hopefully the log will help. Best regards.

I just had the same issue now, I tried the new 26 IPSW, and it worked, just try the new version

 

[Bradonis]

hi, I am now one step further I think. attached is the new log. again, I tried it with several cables and the dfu usb port directly at the magsafe port. I tried it with uploading 15.6.1 and 26.0.0 both the same. now before he "shuts down" I see at least for like 30 second the apple logo an an empty "status" bar under. Maybe you have another idea? the tip with the soldered cable from force dfu and release after like 4 seconds was already much better.

I uploaded also a short with the blinking of the normal charger. That’s the problem I have pretty similar with 5v-20v.