[Clarification Needed] Restore SysNAND (Full) script, no longer works? #366
Comments
|
The difference is that ntrboot is booting from a flash card, but sighax is booting from the firmware. I don’t get why this matters though. There’s emunand9, Gateway launcher, and perhaps other tools that can flash a full nand.bin. The scripts are more for REPAIRING a nand, if you were numb enough to not have a backup. |
|
Eh... You know, these scripts are there to help noobs, mainly, and don't even provide functionality that is not available otherwise? Just copy the backup to S:/. The check will stay in the script so that anyone using it is at least sure to have a means of repairing any mess they may cause. |
|
Closing this, feel free to reopen if you think it's not solved. |
|
@urherenow, the person I'm trying to help has a backup of his SysNAND .bin dump. He was messing around mixing and matching themes that got him into his current predicament, the details which can be read at the thread mentioned above. What we're hoping to accomplish is fully restoring his NAND in hopes of repairing his audio bug issue. I was curious as to why the SysNAND Restore (Full) script no longer works for current GodMode9. Reading the script's name description, as the reader, I am lead to believe the (Full) version is somehow more thorough or complete in restoring the NAND files than the (Safe) one. If that's not the case, then I would like be corrected that there's no functional difference in the end result in their restore process, and that the difference now lies in how one goes about running the respective scripts. |
|
@dok3, I have no permission to reopening this issue. All I can do is comment. Basically, my questions now comes down to whether the current revision of the SysNAND Restore (Full).gm9 is no longer intended to be used as-is when you normally start up GodMode9 holding the (Start) button. If that's the case, is there a guide in booting GodMode9 through NTRboot? I don't recall the 3ds.hack.guide mentioning anything about launching GM9 with a flash cart. |
|
Fully restoring a NAND backup probably wouldn’t help - AFAICT the only diffference is that in “Safe” the firm partitions are not touched. |
|
@SirNapkin1334, that's what I would do exactly if I was in the position of using the (Full) version of this script myself. However, the person who I intended to have in using this is @garbageburger back in GBAtemp forum. This script would be a last ditch effort in trying to fix his newly purchased N3DSXL. If his actions tinkering with themes/Anemone ended up negatively affecting his SysNAND, I would hope the (Full) restore could be the solution as the (Safe) one didn't cut it. Is @kazuma77 still the sole author credited to these restore scripts? I will need to get in contact with him to learn why he rewrote the HAX check and how one goes about launching (Full) version in NTRboot mode. @SirNapkin1334 , would you happen to be in contact with him? Is his alias in Discordapp, Raistlin77, or is that a different user who happens to share 77 as coincidence? |
|
Kazuma77 (aka @MadScript77) is on the GM9 Discord as Raistlin77. You didn't get my point earlier, though. The NTRBOOT check is there as some limited safety simply cause novice users should not use this script and should use the safe one instead. A full restore is a last resort solution. I also just told you what to do. Rename the backup to EDIT: Or, you know, edit teh script yourself, remove the check, and send it to that user. |
|
@d0k3, thank you. I didn't mean to suggest Kazuma/MadScript/Raistlin77 should rewrite his script as I suspected there was a good reason why that HAX safety check was put there in the first place. I'll go hit him up at Discordapp in how one uses it in NTRboot; this I'm curious in as I've never heard of running GodMode9 in NTRboot mode. I think most of my concerns are answered here before I go back to @garbageburger in what he should do next. Really crossing my fingers that his problem is software and not hardware based. Heads up in case I come back to announce bad news if it doesn't work out using the (Full) restore method. Potential Warning Clarification (not related to GodMode9, just presented here for your readings. I;'ll probably share this at Anemone3DS github):
More research will be need to determine what went wrong. Edit - I just read your @SirNapkin1334 post about getting GodMode9 to work on flash cart. That's super neat. Yah, that wiki definitely needs to cover that topic. :) |
|
Adding my 5 cents here (dammit, @d0k3, do you always have to have the last word?)... A full NAND restore will most likely not change anything either. It would only help in case the FIRM partitions got damaged, and in that case you'd have a bluescreen. And, that is most likely a better explanation than earlier... In short: The full NAND restore makes only sense if you got a blue screen (and, you know, for fixing that you will need NTR boot). The safe NAND restore will do the job in all other cases. |
|
Haha! No lasts word for you @d0k3 (not yet at least :P). I got in contact with @GarbageBurger. He said he traded his N3DSXL to a friend's. The crashes he was getting were ARM11 ones, with exception handler ignored in Luma3DS. This may have been a contributor to the audio issue. Guess we'll never know if restoring FIRM partitions would have fixed the bug. :/ About to wrap up discussion with him in what he did* in Anemone and Nintendo's theme shuffler. I have a hunch in how he did it but will need to read it in his own words. It doesn't sound good, but I'm hoping there's a way that 3DS theme managers are able to patch this pitfall. Edit - Yah, this issue has ran its course. It's out of scope. Nothing more to add. |
|
@TurdPooCharger (no, I will get the last word!) Honestly, I don't think that restoring FIRM partitions would be the cause of the issue. Perhaps it's an error with NATIVE_FIRM in CTRNAND? He should have tried updating the system or CTRtransfer. Perhaps this is an issue with the DSP firmware? |
|
@SirNapkin1334, DSP firmware was hash checked to be intact. @PabloMK7, the dev who made the blue wavy homebrew logo splash screen [the one you see after launching freeShop], was in that thread and explained that couldn't be it due to the crackling/popping noise also happening in the DS and GBA modes. These are separate firmwares to the 3DS one and don't use DSP. The sound bug carries through in the headphone jack, so it couldn't be the 3DS speakers being damage. The bug also appeared when the volume slider was set to off. !!! GarbageBurger didn't get a chance to do CTRtransfer. I'm reluctant about recreating this bug on my own N3DSXL as I'm not ready to risk destroying my audio. Still got some GM9 scripts to make. @SirNapkin1334, I'll continue discussion about this on Discordapp if you'd like. Someone else be the last one stand with words in. 😆 |
While helping out a user at this thread here, due to a strange audio bug, I suggested @GarbageBurger to try the (Full) version of Restore SysNAND with a NAND backup made prior to the occurrence of the sound bug.
This is done as a process of elimination to determine whether his issue is software based before declaring that the issue is hardware in nature.
He has already tried using the (Safe) version of that script.
The (Full) script quits stating "This script requires ntrboot to run." at line 008:
chk $[HAX] "ntrboot"Previous version of this script used to work before the 'HAX' command was introduced.
echo $[HAX]states that custom firmware isApologies for opening this issue. I tried researching what the differences are between sighax and ntrboot in GBAtemp threads, and when/why the (Full) restore is appropriate to use.
The text was updated successfully, but these errors were encountered: