Hacking Stuck on the "arm11.bin loading" screen

  • Thread starter Thread starter Nicole201
  • Start date Start date
  • Views Views 19,238
  • Replies Replies 71
Let me poke some more people to see if they can help here with some other points of view (although I don't know when/if they will respond)

@Plailect ; @Quantumcat ; @KunoichiZ ; @gnmmarechal ; @gamesquest1 ; @astronautlevel and other's who may see this, can you help to solve this?

There's no hurry, it's just that I've spent hours trying to get this exploit to run and it's beginning to frustrate me a little. I'm still clueless as to what the route of the problem is!
 
Damn, this is really weird.
And I feel sorry but I don't know what else I can tell you to solve this.

Have you tried to format your console on system settings? Other than that, I'm out of ideas.

Let me poke some more people to see if they can help here with some other points of view (although I don't know when/if they will respond)

@Plailect ; @Quantumcat ; @KunoichiZ ; @gnmmarechal ; @gamesquest1 ; @astronautlevel and other's who may see this, can you help to solve this?

Omg someone called me for help :D lemme see the issue

EDIT: Huh. Try backing up the files, formatting the card to FAT32 and copy them back in?
 
Last edited by gnmmarechal,
I tried to help last night in the Noob Help thread and we got nowhere. I think this is something only the devs could answer.
 
  • Like
Reactions: Nicole201
try updating back up to 4.x+ then perform the ctrtransfer again, iirc the FIRM downgrade is done last and if the ctrtransfer fails it will downgrade everything except FIRM, updating and downgrading may fix it
 
  • Like
Reactions: gnmmarechal
Yeah sounds like you may be on a bit of a frankenfirm iirc decrypt9 can be booted on 2.1 and I think it uses the normal browser exploit instead of the 2xrsa one, so that may work to do a ctrtransfer

if not you may need a game with a higher FW than you started off on
 
What do you suggest I do?
If the FIRM didn't downgrade (like gamesquest1 said in posts above) from when you originally started, then you need to go back to same version and try again. The normal cart update procedure might be failing due to FIRM on console being newer than expected.

Either try updating using game cart. It has to be same update as the one that you originally had, if you had 9.0~9.2 then try updating to that first and avoid game carts that contain 9.9 or higher (9.9 and onwards game cart update has dummy browser).

If you don't have such game carts then you can somehow try loading HBL using some sort of browserhax for 2.x since MSET might not work until you update to 4.x. Once on HBL you can try sysUpdater to upgrade back to firmware you originally had using cia packs.
 
Last edited by Just3DS,
try updating back up to 4.x+ then perform the ctrtransfer again, iirc the FIRM downgrade is done last and if the ctrtransfer fails it will downgrade everything except FIRM, updating and downgrading may fix it

Yeah sounds like you may be on a bit of a frankenfirm iirc decrypt9 can be booted on 2.1 and I think it uses the normal browser exploit instead of the 2xrsa one, so that may work to do a ctrtransfer

if not you may need a game with a higher FW than you started off on
I know that there was a "updates" folder on SD root in the beginning which gives the notion that a downgrade was made (to 9.2) before the whole process started.
Didn't consider that situation (of frankenfirmware) since the Decrypt9.log had every step successful.

Now that you mentioned it, it's the only thing that can be preventing the install (if there were errors from before, they'll trample over to the CTR-Transfer).
But I was convinced that the Decrypt9 would always fail if there were a bad/failed 9.2 downgrade (seems I was mistaken).

@Nicole201 Can you resume what you've done on the console and most of all, what was your starting FW before doing the guide?
 
I know that there was a "updates" folder on SD root in the beginning which gives the notion that a downgrade was made (to 9.2) before the whole process started.
Didn't consider that situation (of frankenfirmware) since the Decrypt9.log had every step successful.

Now that you mentioned it, it's the only thing that can be preventing the install (if there were errors from before, they'll trample over to the CTR-Transfer).
But I was convinced that the Decrypt9 would always fail if there were a bad/failed 9.2 downgrade (seems I was mistaken).

@Nicole201 Can you resume what you've done on the console and most of all, what was your starting FW before doing the guide?
yeah the ctrtransfer is done with ctr partition , then the firm partition downgrade, I recovered a n3ds that was bricked when the 2.1 ctrtransfer completed but it turns out that the firm partition was not, so on the n3ds this would result in a brick, on a o3ds it would probably just leave you on a frankenfirm I.e 9.2 native_firm but all the 2.1 system apps

(luckily the n3ds doesn't need the 2.1 downgrade any more so the worst that can happen is with o3ds's getting franken FW'd)
 
Last edited by gamesquest1,
  • Like
Reactions: Just3DS and cravas
yeah the ctrtransfer is done with ctr partition , then the firm partition downgrade, I recovered a n3ds that was bricked when the 2.1 ctrtransfer completed but it turns out that the firm partition was not, so on the n3ds this would result in a brick, on a o3ds it would probably just leave you on a frankenfirm I.e 9.2 native_firm but all the 2.1 system apps
In that case, maybe it's possible to launch Oothax (or any other Cart points) or even Browserhax (wishing). Launch Sysupdater to bring back a full 9.2 and then 2.1 CTR-transfer with D9.

@Nicole201 can you try it? Launch the browserhax and see it goes through?
 
In that case, maybe it's possible to launch Oothax (or any other Cart points) or even Browserhax (wishing). Launch Sysupdater to bring back a full 9.2 and then 2.1 CTR-transfer with D9.

@Nicole201 can you try it? Launch the browserhax and see it goes through?
Browserhax is down.
 
I know that there was a "updates" folder on SD root in the beginning which gives the notion that a downgrade was made (to 9.2) before the whole process started.
Didn't consider that situation (of frankenfirmware) since the Decrypt9.log had every step successful.

Now that you mentioned it, it's the only thing that can be preventing the install (if there were errors from before, they'll trample over to the CTR-Transfer).
But I was convinced that the Decrypt9 would always fail if there were a bad/failed 9.2 downgrade (seems I was mistaken).

@Nicole201 Can you resume what you've done on the console and most of all, what was your starting FW before doing the guide?

My sysnand was originally on 9.2 firmware and then I downgraded to 2.1. I will see if I can get into browserhax later.
 
Unfortunately, there are no games that will update to 9.0 - 9.2, I've tried browserhax but it doesn't seem to work as it's down.
 

Site & Scene News

Popular threads in this forum