Hacking So...is my N3DS dead?

  • Thread starter Thread starter 3dsn00b
  • Start date Start date
  • Views Views 33,852
  • Replies Replies 295
He wrote it in first post... Installed the game via BBM, there was no game after succesfull install, he then rebooted console and bam...black screen.

This makes me wonder about BBM, I am using it for quite some time frome when i used GW emuNAND. I also tried the latest FBI, but it freezes.
Is there any other alternative for a9lh/Luma?

DevMenu

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

is FBI 2.x safe to install to H&S now?

You can just install the cia to your home menu
 
This is like a new era in CIA installing! :P But seriously, just try it! ;) It has a different title ID so you can keep the old FBI while trying this new one out.
Do you know how to update FBI injected in the HS app? I didn't keep the hs.app file so I don't know how am I supposed to do this.
 
Just redump the hs.app(currently old FBI) then use the generated hs.app to generate a new hs.app with the new FBI.cia using the Universal Injector, inject it in your console.
 
So what happened? We're all dying over here!
I ran into a similar issue with another 3DS and am waiting for the feedback of the latest suggestion.

At the moment it seems Luma3DS is either not finding and patching the NATIVE_FIRM or it's an issue with the 3DS itself. Will update with more info when I hear back about the latest results.
 
This is like a new era in CIA installing! :P But seriously, just try it! ;) It has a different title ID so you can keep the old FBI while trying this new one out.

wow man, i gave it a try and this one looks fantastic ! so much cleaner and better than the original fbi !

and it is no longer sloppy/slow ! it is a very good cia installer , many thanks man ! (btw. does it install cia's in the background now also or do i have to keep the lid up?)
 
  • Like
Reactions: SomeGamer
I ran into a similar issue with another 3DS and am waiting for the feedback of the latest suggestion.

At the moment it seems Luma3DS is either not finding and patching the NATIVE_FIRM or it's an issue with the 3DS itself. Will update with more info when I hear back about the latest results.

If its the first statement (not finding NATIVE_FIRM), maybe use the firmware.bin for ntr use, in this case Luma wont have to find the NATIVE_FIRM ?
Or all I say is false and I must dont speak here anymore ? :D (explain if false pls :p)
 

sad to hear , your luck must have run out man :(

i have a hardware related issue with my Nexus 6 (Phone) and the issue is in the Screen, i have some ugly gradient like bars appearing on certain solid backgrounds.. and i am still using the phone (yes my luck was crap with the phone, when i first bought it , it was perfect looking perfect, but after some 3weeks i noticed the issue on screen).

i guess whatever device we buy there might be a certain % of bad luck in it and we might have recived the one of the bad % of a lemon.

hopefully the op of this thread can get his working, but to me it seems he has the same issue as you.
 
What files do you have in the "luma" folder? And have you at all by chance overwritten your HomeMenu CIA?

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

There's a way to check your NAND files with A9LH, I'll get back to you on that solution. It involves using GodMode9 and taking screenshots (NOT DELETING ANYTHING THOUGH OR YOULL GET AN ABSOLUTE PERMABRICK)
 
I just found something weird. Inside Decrypt9 > Maintenance Options > System Info the Serial Number doesn't match the one on the back of my 3DS. Actually it's only missing a '1' at the end.
 
Last edited by 3dsn00b,

Site & Scene News

Popular threads in this forum