Hacking Successful a9lh but error 007-2503 launching eshop

[Solarius88]

If you still have an emuNAND on your card, you should get rid of it. Backup your SD card files, boot into the emuNAND9 payload, format your card with no emuNAND, then copy back the files.

Sure I'll do that too

 

[Majickhat55]

Your problem seems to be that you still have an emunand partition and you're booting into that on A9LH which is why you're getting the system version of 4.xx. It doesn't even seem like your protected sysNAND is updated. Also I'm pretty sure (someone correct me if I'm wrong) but after A9LH the NATIVE_FIRM is usually around 2.xx anyway while the system version is updated to 11.0.

 

[gkoelho]

Your problem seems to be that you still have an emunand partition and you're booting into that on A9LH which is why you're getting the system version of 4.xx. It doesn't even seem like your protected sysNAND is updated. Also I'm pretty sure (someone correct me if I'm wrong) but after A9LH the NATIVE_FIRM is usually around 2.xx anyway while the system version is updated to 11.0.

Not for the old guide at least. Im sure the old guide used 9.6 NATIVE_FIRM.

 

[Majickhat55]

Not for the old guide at least. Im sure the old guide used 9.6 NATIVE_FIRM.

I was referring to what it shows when I use 3DSident for the NATIVE_FIRM (2.51). I haven't used the new guide yet, my A9LH install is from June it's v1. Hence why I said I wasn't sure.

 

[gkoelho]

I was referring to what it shows when I use 3DSident for the NATIVE_FIRM (2.51). I haven't used the new guide yet, my A9LH install is from June it's v1. Hence why I said I wasn't sure.

I dont know what exaclty you mean as I didnt tryied 3DSident yet, but i'm sure no CFW can boot a 2.x native_firm so it is not its version stated there.

 

[Majickhat55]

I dont know what exaclty you mean as I didnt tryied 3DSident yet, but i'm sure no CFW can boot a 2.x native_firm so it is not its version stated there.

They can't boot a system version at 2.1. They aren't the same thing IIRC.

 

[The Real Jdbye]

I was referring to what it shows when I use 3DSident for the NATIVE_FIRM (2.51). I haven't used the new guide yet, my A9LH install is from June it's v1. Hence why I said I wasn't sure.

FIRM doesn't use the same version numbering as the rest of the system. You can see the list of FIRM versions and the corresponding firmware here: https://www.3dbrew.org/wiki/FIRM#NATIVE_FIRM

 

[Majickhat55]

FIRM doesn't use the same version numbering as the rest of the system. You can see the list of FIRM versions and the corresponding firmware here: https://www.3dbrew.org/wiki/FIRM#NATIVE_FIRM

"11.0.0 v24368 52 2.51-0" That's what I said Lol. I see what you were saying 2.51-0 is the firm for 11.0.0. I was still technically right in saying they were separate..... So a NATIVE_FIRM at 10.4 would be 2.50-11.... Gotcha, Learn something new everyday

 

[Solarius88]

I've got my o3ds sorted out.
It was a botched upgrade on sysnand CFW, I needed to retry upgrading it 3 times on my o3DS before it updated properly.

DSi downgrade for my o3DSXL was also successful with Plailects guide without any hickups so that was great..

If a MOD could just close this thread as I have everything figured out.

Thanks

 

[Majickhat55]

Threads aren't closed when they are "solved" in case another user encounters the same problem it could be useful to them.