Homebrew [A9LH + Luma] "An error has occurred." when launching HBL CIA on 11.0

[Deleted member 333767]

Adding to the ever growing list of problems my 3DS has begun developing, I can't run the homebrew launcher via the hbl cia.

In Luma mode alone, it crashes back to the home menu and displays "An error has occurred. Please save your data in any software currently in use, then restart the system"

In Gateway mode, it freezes at "the homemenu ropbin is ready" and gives me a black bottom screen.

I've tried using versions 1.0, 1.1 and 1.2 of the cia, it's the same result for all of them.

I've tried downloading my own payloads for my specific firmware and renaming them appropriately.

I've tried on both 11.0 and my native sysNAND firm (holding R on boot) of 9.0, still gives the same error.

Please help. Thanks for reading

My units details are:
-New 3DS XL
-11.0.0-20E
-Luma updated sysNAND mode
-Base firmware is 9.0.0-20E
-/3ds/ folder from starter kit + boot.3dsx is definitely on the SD card, as are the correctly named payloads for my specific firmware on the root of SD and duplicated in the /hblauncherloader/ folder that the newer HBL.cia creates.

 

[Manurocker95]

If you are on Luma+a9lh why don't you update to the latest fw? Btw, do you have patched checks on Luma Options?

 

[erman1337]

Update luma mate

 

[Deleted member 333767]

Update luma mate

It's on the latest stable already.

 

[Deleted member 333767]

If you are on Luma+a9lh why don't you update to the latest fw? Btw, do you have patched checks on Luma Options?

I can't update to the latest firmware which is a seperate problem on its own. Here's my other thread:

http://gbatemp.net/threads/a9lh-lum...le-to-update-trying-to-update-to-11-2.451084/

My 3DS appears to be one amongst thousands of 3DSs to have these issues.

When my 3DS was on menuhax + gateway, I never had any of these problems EVER. It just worked!

Im starting to think either Luma3DS is a piece of shit, or my 3DS has manufacturing faults.

 

[Giodude]

I can't update to the latest firmware which is a seperate problem on its own. Here's my other thread:

http://gbatemp.net/threads/a9lh-lum...le-to-update-trying-to-update-to-11-2.451084/

My 3DS appears to be one amongst thousands of 3DSs to have these issues.

When my 3DS was on menuhax + gateway, I never had any of these problems EVER. It just worked!

Im starting to think either Luma3DS is a piece of shit, or my 3DS has manufacturing faults.

So let's see if we can address this now. So what happens when you go to system settings and update normally?

 

[Deleted member 333767]

So let's see if we can address this now. So what happens when you go to system settings and update normally?

"An error has occurred, unable to update" There is no error code associated with the error screen. The progress bar jumps instantly to what appears to be about 20-25% and hangs there for a few seconds and then fails. Same thing happens when I try to update through the eShop.

It was on 9.0 before when I had this problem, but I used a pokemon cart to get 11.0 and still the issue persists

 

[el_gonz87]

"An error has occurred, unable to update" There is no error code associated with the error screen. The progress bar jumps instantly to what appears to be about 20-25% and hangs there for a few seconds and then fails. Same thing happens when I try to update through the eShop.

It was on 9.0 before when I had this problem, but I used a pokemon cart to get 11.0 and still the issue persists

Hmmmm, can you set up an EmuNAND and do a CTRTRANSFER, then see if this will update?

Try this on a new created EmuNAND: https://3ds.guide/9.2.0-ctrtransfer.html

 

[Deleted member 333767]

I know the obvious solution is to just perform system format and start over again, but that's not possible for a number of reasons.

The largest one being I am about 600 kilometers from a PC in the middle of the Australian outback.

I've also had to system format and start from scratch well over 10 times now. Quite frankly, i'm tired of this being the ultimate solution for fixing hacked 3DSes that aren't performing like they should be.

It took multiple days of slaving over a PC reading tutorials, scouring forums, unscrewing backplates, removing and reinserting SD cards to get my 3DS in current state it is now. I absolutely refuse to start over from the beginning and desperately seek a solution.

I just want to know why my 3DS is just a single unit in amongst thousands and thousands of hacked ones that has persistent issues like these ALL THE TIME

 

[Giodude]

"An error has occurred, unable to update" There is no error code associated with the error screen. The progress bar jumps instantly to what appears to be about 20-25% and hangs there for a few seconds and then fails. Same thing happens when I try to update through the eShop.

It was on 9.0 before when I had this problem, but I used a pokemon cart to get 11.0 and still the issue persists

No custom dns or anything?

 

[Deleted member 333767]

No custom dns or anything?

If you've got a spare 5 mins, you can check out my other thread to see the things I've tried already.

But yes, I tried Auto Obtain DNS and the Google DNS. Same result everytime.

 

[el_gonz87]

I know the obvious solution is to just perform system format and start over again, but that's not possible for a number of reasons.

The largest one being I am about 600 kilometers from a PC in the middle of the Australian outback.

I've also had to system format and start from scratch well over 10 times now. Quite frankly, i'm tired of this being the ultimate solution for fixing hacked 3DSes that aren't performing like they should be.

It took multiple days of slaving over a PC reading tutorials, scouring forums, unscrewing backplates, removing and reinserting SD cards to get my 3DS in current state it is now. I absolutely refuse to start over from the beginning and desperately seek a solution.

I just want to know why my 3DS is just a single unit in amongst thousands and thousands of hacked ones that has persistent issues like these ALL THE TIME

Well the point of the CTRTRANSFER on EmuNAND is just to see what happens with a new setup, my suggestion was going to be start with that. Then port stuff over so that you don't have to start from scratch such as movable.sed, etc.. Finally when you have things working move back to SysNAND.

But if you don't wanna/can't fix it, then put that 3DS down and go enjoy the natural wonders of the outback. aight? MAAAAATE

 

[Deleted member 333767]

Well the point of the CTRTRANSFER on EmuNAND is just to see what happens with a new setup, my suggestion was going to be start with that. Then port stuff over so that you don't have to start from scratch such as movable.sed, etc.. Finally when you have things working move back to SysNAND.

But if you don't wanna/can't fix it, then put that 3DS down and go enjoy the natural wonders of the outback. aight? MAAAAATE

Lol, I work in lead/Zinc mine.... There isn't a single natural wonder as far as the eye can see, just black toxic shit everywhere and a big hole in the ground

So this CTR transfer thingy, will it carry over all my installed homebrew titles and CIA games with my save data?

 

[GerbilSoft]

I've tried downloading my own payloads for my specific firmware and renaming them appropriately.

That's the "otherapp" payload, right?

It could be that whatever's blocking system update from working correctly (frankenfirmware?) is also preventing the HBL ropbin from running correctly.

 

[Giodude]

Lol, I work in lead/Zinc mine.... There isn't a single natural wonder as far as the eye can see, just black toxic shit everywhere and a big hole in the ground

So this CTR transfer thingy, will it carry over all my installed homebrew titles and CIA games with my save data?

Ctrtransfer is basically flashing a new firmware manually, so everything should be fine

 

[el_gonz87]

Lol, I work in lead/Zinc mine.... There isn't a single natural wonder as far as the eye can see, just black toxic shit everywhere and a big hole in the ground

So this CTR transfer thingy, will it carry over all my installed homebrew titles and CIA games with my save data?

Well if you backup your SD card and setup an EmuNAND using EmuNAND9, then re-copy all of your SD card contents back on there, you can do a CTRTRANSFER on the EmuNAND (will backup and inject your system tickets).

This will not touch anything with your SysNAND.

After that you can format EmuNAND (make sure you are in EmuNAND!) and see if it can update to 11.2.

Then you can go about moving things over to the EmuNAND such as moveable.sed, this will allow contents on your SD card to be read from the EmuNAND.

The first thing is to identify if something is going on with the NAND that is preventing the system update such as a custom home menu etc... Once that is established then you can go about narrowing down the issue. So if EmuNAND with CTRTRANSFER updates, this basically confirms something is wrong with your firmware. We can then proceed how to restore system best from there.

 

[Deleted member 333767]

That's the "otherapp" payload, right?

It could be that whatever's blocking system update from working correctly (frankenfirmware?) is also preventing the HBL ropbin from running correctly.

It has to be related, for sure.

Back before hbl.cia wasn't getting 404 error, it downloaded otherapp payload itself.

I tried otherapp payload downloaded from smea's website and renamed appropriately.

I've also used an otherapp payload that was uploaded by another user that claimed to fix the same problem on their own 3DS.

They all don't work.

Also, my unit doesn't have Franken firm. It spent it's entire life on 9.0 Gateway emuNAND until I performed a system update to 11.0 in luma via pokemon cart last week.

 

[Majickhat55]

Lol, I work in lead/Zinc mine.... There isn't a single natural wonder as far as the eye can see, just black toxic shit everywhere and a big hole in the ground

So this CTR transfer thingy, will it carry over all my installed homebrew titles and CIA games with my save data?

It's worth noting that even stock 3DS' on OFW have issues regularly with updating. Even when I got a new DS out of the box last year it was doing exactly what you're describing. It fixed itself eventually after retrying a million times. Not saying that you haven't tried that but I know from experience (as well as other confirmations on stock) that it's entirely a problem with the quality of the internal wi-fi components of the console.

--------------------- MERGED ---------------------------

Maybe when you went from Menuhacks to A9LH like someone else said you ended up with a frankenfirm so now you have mismatched system titles. See if you have any "pending titles" in FBI and if you do, take note of them, delete them and install them with 3DNUS. Or you know, downgrade again if that is your problem....

 

[Deleted member 333767]

It's worth noting that even stock 3DS' on OFW have issues regularly with updating. Even when I got a new DS out of the box last year it was doing exactly what you're describing. It fixed itself eventually after retrying a million times. Not saying that you haven't tried that but I know from experience (as well as other confirmations on stock) that it's entirely a problem with the quality of the internal wi-fi components of the console.

--------------------- MERGED ---------------------------

Maybe when you went from Menuhacks to A9LH like someone else said you ended up with a frankenfirm so now you have mismatched system titles. See if you have any "pending titles" in FBI and if you do, take note of them, delete them and install them with 3DNUS. Or you know, downgrade again if that is your problem....

I am aware of the 3dses poor wifi modules, so I've tried updating on 100mbps fibre with the 3ds sitting on the router, also tried with a 4G hotspot underneath a mobile tower with the 3ds sitting on the phone. That's how desperate I've become.

Also:

 

[GerbilSoft]

Those title IDs correspond to: (all EUR)
00040010-00022100 == Download Play
00040010-00022900 == eShop
00040010-00022A00 == System Transfer
00040010-20022300 == N3DS Health and Safety
00040010-20022D00 == N3DS Face Raiders

Can you try cancelling those pending titles and doing another System Update? (I'd recommend a NAND backup first.)