Hacking SysUpdater brick after "an error occurred" - What can I do?

[Axido]

Hello, guys.

I downgraded an o3DS on 11.1 via DSiwarehax, downgraded further to 9.2 via the GW time machine and tried to get to 2.1 using SysUpdater. SysUpdater got stuck on #4 the first time, on #5 the second time. After starting ftbrony beforehand it started correctly and I initiated a downgrade to 2.1.0E. A few .cia files installed successfully before I decided to just let it happen. When I came back the bottom screen showed a messsge that an error occurred and that I should turn off my 3DS. When I turned it back I got two black screens and nothing else (no Wi-Fi blinking). I tried everything I found on the web (removing SD card, removing certain folders on the SD card, acessing the recovery mode via L+R+A+Up on boot) without success.

Sadly I didn't make a NAND backup made on this exact 3DS. The only thing there is is my other 3DS that I system transfered to the now bricked one in order to downgrade it. I transfered an EmuNAND I can recover from a dump, but I'm not quite sure if a NAND dump of a system transfer donor would work on the receiving console. So, am I screwed or is there still something I can do about this?

 

[Aerocool]

Man, you should have used the Plailect guide... GW time machine is a no-go and normal sysUpdater isnt very stable. Im sorry man but your system is unrecoverable without a backup. :/

 

[Deleted User]

there are so many things you did wrong that I can't even list them all

 

[kamesenin888]

You tried to get to 2. 1 using sys updater?

 

[el_gonz87]

Hello, guys.

I downgraded an o3DS on 11.1 via DSiwarehax, downgraded further to 9.2 via the GW time machine and tried to get to 2.1 using SysUpdater. SysUpdater got stuck on #4 the first time, on #5 the second time. After starting ftbrony beforehand it started correctly and I initiated a downgrade to 2.1.0E. A few .cia files installed successfully before I decided to just let it happen. When I came back the bottom screen showed a messsge that an error occurred and that I should turn off my 3DS. When I turned it back I got two black screens and nothing else (no Wi-Fi blinking). I tried everything I found on the web (removing SD card, removing certain folders on the SD card, acessing the recovery mode via L+R+A+Up on boot) without success.

Sadly I didn't make a NAND backup made on this exact 3DS. The only thing there is is my other 3DS that I system transfered to the now bricked one in order to downgrade it. I transfered an EmuNAND I can recover from a dump, but I'm not quite sure if a NAND dump of a system transfer donor would work on the receiving console. So, am I screwed or is there still something I can do about this?

Sell it for parts, try to send it into ninty if under warranty, buy a new mother board... Only potions right now

 

[ebericus]

Only hardmod will fix your problem. There are tutorials on this forum on how to do that.

 

[nechigawara]

Only hardmod will fix your problem. There are tutorials on this forum on how to do that.

I won't think that hardmod can recovery from this state.

 

[Alex658]

Only hardmod will fix your problem. There are tutorials on this forum on how to do that.

He doesn't have a NAND backup, afaik nothing can save him from his own doom...

 

[ebericus]

It is possible if you flash the proper image for your unit from Plailect's guide (https://github.com/Plailect/Guide/wiki/9.2.0-ctrtransfer) after doing the hardmod. This image is for those who have no sysnand backups.

 

[Alex658]

It is possible if you flash the proper image for your unit from Plailect's guide (https://github.com/Plailect/Guide/wiki/9.2.0-ctrtransfer) after doing the hardmod. This image is for those who have no sysnand backups.

For that to be plausible the console has to be able to even boot until decrypt9 comes in and fixes the CTRnand transfer image... how would you validate the movable.sed, secureinfo_a and other sensitive files? AFAIK, you can't.
He's doomed. Correct me if i'm wrong, though.

 

[el_gonz87]

New motherboard or send to Nintendo if new and tell them it bricked on system transfer

 

[ebericus]

Hmm. What I did from mine after it got bricked is that I went to a friend of mine to hardmod it. After he has attached the necessary cables to the NAND chip and the sdcard adapter, we inserted the sdcard adapter to the card reader then connected the card reader to the PC. We used win32diskimager to flash the proper image from Plailect's guide to the unit. We desoldered the cables from the NAND and turned on the 3ds. After a while it booted to the vanilla Home menu 9.2.

 

[Alex658]

Let's wait for someone else more knowledgeable on the matter to confirm it then..

 

[ebericus]

No problem.

 

[vb_encryption_vb]

Hmm. What I did from mine after it got bricked is that I went to a friend of mine to hardmod it. After he has attached the necessary cables to the NAND chip and the sdcard adapter, we inserted the sdcard adapter to the card reader then connected the card reader to the PC. We used win32diskimager to flash the proper image from Plailect's guide to the unit. We desoldered the cables from the NAND and turned on the 3ds. After a while it booted to the vanilla Home menu 9.2.

You had a backup of your console nand that you flashed. No nand backup, nothing can be done.

 

[Alex658]

whereas a CTR transfer is essentially a backup, it's still missing critical files to be able to boot (which is why decrypt9 has to fix it before being able to boot)
So if your 3ds can't boot enough just for decrypt9 to fix the ctr transfer you're trying to flash, nothing can be done.

 

[nickelci]

Recovery mode should still boot, youll be on ofw 11.1 tho afterwards