Hacking An exception occurred: Arm 9, Prefetch Abort (SvcBreak) on boot.

[GShark]

I am getting, An exception occurred: Arm 9, Prefetch Abort (SvcBreak) when I boot. Anyone have any input about this and how to fix it?

This is happening after fixing a blue screen brick using the Lazarus script, installing B9S, and Luma successfully. Any ideas what to try next?

@AnalogMan

 

[Lacius]

• When you boot the 3DS while holding the Select button, which version of Luma3DS is displayed at the top of the configuration settings?
• Have you tried booting without the SD card? If so, what happens?

 

[GShark]

Looks like Luma 9.0. Booting without the sd card results in the same error that I posted about up top.

 

[zoogie]

Dump your movable.sed and tell us how big it is.

It's in CTR-NAND
/private/movable.sed

You can do this with Godmode9

 

[Lacius]

I know you might have already done this via another means, but as a matter of troubleshooting, I recommend following this guide to perform a CTRTransfer.

 

[GShark]

Dump your movable.sed and tell us how big it is.

It's in CTR-NAND
/private/movable.sed

You can do this with Godmode9

My movable.sed in 1:/sysnand ctrnand/private is 320 bytes. I’m in GM9 but not sure how to dump it.

 

[zoogie]

My movable.sed in 1:/sysnand ctrnand/private is 320 bytes. I’m in GM9 but not sure how to dump it.

Ok, if it's 320 bytes then that's not the issue I'm thinking of. You don't have to dump it.

 

[GShark]

I know you might have already done this via another means, but as a matter of troubleshooting, I recommend following this guide to perform a CTRTransfer.

I completed the ctrtransfer per the guide and everything completed successfully. Still getting error on boot. What next?

 

[TurdPooCharger]

I completed the ctrtransfer per the guide and everything completed successfully. Still getting error on boot. What next?

Try removing and reinserting your battery and booting the 3DS without the SD card. It sounds really stupid, but this sometimes fixes weird boot issues.

 

[GShark]

I tried the Ctrtransfer in Decrypt9 and it passed except I noticed at the very end it said movable.sed is corrupt. Is that a big cause of concern?

 

[zoogie]

I tried the Ctrtransfer in Decrypt9 and it passed except I noticed at the very end it said movable.sed is corrupt. Is that a big cause of concern?

So it was the movable.sed, hmm..

System won't boot without a good movable.sed.

Try this. Use Godmode9 to change the 6th byte of the movable.sed to 00. That should fix it.
Edit, on second thoughts, your msed has pretty severe issues to be able to trigger that error.
https://github.com/d0k3/Decrypt9WIP...60cdd1512a5a6b93d/source/decryptor/keys.c#L94
In other words, it is badly corrupted somehow.

 

[GShark]

So it was the movable.sed, hmm..

System won't boot without a good movable.sed.

Try this. Use Godmode9 to change the 6th byte of the movable.sed to 00. That should fix it.
Edit, on second thoughts, your msed has pretty severe issues to be able to trigger that error.
https://github.com/d0k3/Decrypt9WIP...60cdd1512a5a6b93d/source/decryptor/keys.c#L94
In other words, it is badly corrupted somehow.

So this is my moveable.sed in hex. This has a lot of 00 already, that normal?

 

[zoogie]

So this is my moveable.sed in hex. This has a lot of 00 already, that normal?

Yeah, that's not gonna cut it

PM me.

 

[GShark]

Hail zoogie, boot issue was from corrupt movable.sed. A new working one fixed the issue. From blue screen to working with lazarus, B9S, Ctrtransfer, and the help of you guys, Thanks.

 

[KikoStart]

I'm having the same issue. I system transferred from a New 3DS XL to a 2DS XL, set it up for homebrew following the same guide, and am having this exact same error on bootup. SD in there or not. How were you able to fix your moveable.sed? I can't find any info on fixing the corruption or how I'd get a new one?

Thanks! Hopefully this isn't too severe a bump.. I can't quite send PMs yet.

 

[AbsolAron]

I really don't want to bump an old thread, but I am having the same issue that GShark was having. I am on Luma 10.0 and get the same error GShark was getting. I really need help.

 

[TurdPooCharger]

I really don't want to bump an old thread, but I am having the same issue that GShark was having. I am on Luma 10.0 and get the same error GShark was getting. I really need help.

If your system is not a n2DSXL, first try the battery trick. Try booting both with and without the SD card.

 

[AbsolAron]

Same error. With and without the SD.

Edit: Decrypt9 is telling me that I have a corrupt moveable.sed. I have tried to use brute-force moveable to get another, but it still doesn't work.

 

[TurdPooCharger]

Same error. With and without the SD.

I have a bad hunch about your softbrick. ARM9 SvcBreak error can indicate bricked firmware due to corrupt or missing NAND files.

***

Try this,

• n00b help from pretty much square one [post #2]

Overview (of the above)
-------------
1 - Copy everything off the SD card.
2 - Reformat in FAT32 + 32 KB cluster size + MBR disk + Primary partition
3 - Full Write + Verify the empty card in H2testw. Hardware test for errors.
4 - Create a reference SD setup using that CFW starter kit. Do not add back your main setup.
5 - Backup the SysNAND *.bin image (for safety, even if it's currently bricked).
6 - Attempt firmware repair with CTRTransfer + updating to 11.10 firmware with Recovery Mode or System Setting.
7 - If the above CTRTransfer fails, restore the SysNAND *.bin image.
8 - Attempt firmware repair again but this time with CTRTransfer (Type D9) + update to 11.10.


If 3DS is still bricked at this point, you will need to examine certain NAND files with hex editor. Please get in contact later after trying the above for additional help.

Edit: Decrypt9 is telling me that I have a corrupt moveable.sed. I have tried to use brute-force moveable to get another, but it still doesn't work.

Ah, Decrypt9.. I'm going to have a field day with your brick as I have a pretty good guess what might have gone wrong.

 

[AbsolAron]

It is still a brick.

My moveable.sed looks nothing like the one in the picture. I can upload a screenshot of it if needed.