Cool man, let me take a ride some time, I have a couple of things to change too.Good thing I picked up that Delorean the other day on ebay.
PS: Talking serious, perhaps it is a good idea to send it back as it is anyway.
Cool man, let me take a ride some time, I have a couple of things to change too.Good thing I picked up that Delorean the other day on ebay.
I called Nintendo today. They gave me a free return label to print and send back to them. If there are costs in repairing it. I am more than happy to pay them to be honest. It's only fair I pay the price for doing things that I shouldn't be doing.PS: Talking serious, perhaps it is a good idea to send it back as it is anyway.
Cool man, let me take a ride some time, I have a couple of things to change too.
PS: Talking serious, perhaps it is a good idea to send it back as it is anyway.
Yes, under Section 6 of original post I detail that.have you tried creating an emunand out of your backup yet and loading that??
What does this mean?You have to update SysNand via hard boot
Already tried the recovery mode function. Screen is blank, wifi orange LED lights up, but screen is blank.If you want your 3ds, update the SysNand but you will lose all the pirated stuff
http://www.gamefaqs.com/boards/997614-nintendo-3ds/71168246
hard mod won't save you, like i said, we have the same problem and i have a hard mod + i have firmware's 2.1/9.2 9.5 10.3 10.4 10.5 10.6 and 10.7 none of them works, all of them will work as emunand but if i flash them to sysnand it will only boot a9lh when available and all my nand backups that dont have a9lh will just black screen instantly.Good thing I picked up that Delorean the other day on ebay.
--------------------- MERGED ---------------------------
No hardmod. I am really bad with hardware. I don't even know how to use a drill properly.
Ahhh, thanks for clearing that up. The difference is, I can't boot with either EmuNAND or SysNand. Also, did you send yours in for repair? Or can are you fine with using EmuNAND?hard mod won't save you, like i said, we have the same problem and i have a hard mod + i have firmware's 2.1/9.2 9.5 10.3 10.4 10.5 10.6 and 10.7 none of them works, all of them will work as emunand but if i flash them to sysnand it will only boot a9lh when available and all my nand backups that dont have a9lh will just black screen instantly.
i'm fine with emunand, it does all it need's and do you have a9lh on the not working sysnand? if not that's the reason you can't boot emunand, ther are couple of files on your nand and firm0 = sysnand 9.2 and firm 1 = for 10.0+ firm's and since firm0 is corrupt we can't boot 9. stuff but emunand with 10.7 is fine, and my emunand can be downgraded to 9.2 because then it uses firmware files from luma instead of the sysnand partition :cAhhh, thanks for clearing that up. The difference is, I can't boot with either EmuNAND or SysNand. Also, did you send yours in for repair? Or can are you fine with using EmuNAND?
Edit: I'm dumb, you have hardmod. lol. You wouldn't send that in...
It had A9LH to begin with. All the SysNAND back ups I have are A9LH infused. SO, I'm pretty sure it's working.do you have a9lh on the not working sysnand?
right i remember you can open luma config and stuff, i see no reason why emunand is not working, try different firmware files and try no firmware files and try toggling settings in config about firmware files?It had A9LH to begin with. All the SysNAND back ups I have are A9LH infused. SO, I'm pretty sure it's working.
I don't think that's how FIRM works. FIRM1 is just a backup that's used when FIRM0 is corrupted.i'm fine with emunand, it does all it need's and do you have a9lh on the not working sysnand? if not that's the reason you can't boot emunand, ther are couple of files on your nand and firm0 = sysnand 9.2 and firm 1 = for 10.0+ firm's and since firm0 is corrupt we can't boot 9. stuff but emunand with 10.7 is fine, and my emunand can be downgraded to 9.2 because then it uses firmware files from luma instead of the sysnand partition :c
so if firm0 is corrupt, should we dump our firm 1 and replace 0 with 1?I don't think that's how FIRM works. FIRM1 is just a backup that's used when FIRM0 is corrupted.
It shouldn't matter, firm1 is used automatically if firm0 is corrupted.so if firm0 is corrupt, should we dump our firm 1 and replace 0 with 1?
so what about the corruption on firm0 is affecting us not being able to boot sysnand?It shouldn't matter, firm1 is used automatically if firm0 is corrupted.
tried that already, nope, i have clean 9.2's and lot's of other backup's and also formatted 9.2 emunand's that i wrote to sysnand, they all work as emunand but won't boot as sysnand even though a9lh get's booted from the sysnand partionWhat about downgrading your emunand and then flashing it to the sysnand? Would that fix the problem or am I just talking out of my butt?