Hello! I've been trying to set up ubuntu on my switch but keep getting the same error that says "Failed to mount rootfs". I've tried doing the installation process from scratch multiple times with different versions of ubuntu but no luck. Below is a log that was in a note file on the root of the fat32 partition. I think it says whats wrong but I don't really understand it. Does anyone know what it means? Thanks in advance.
[ 3.397086] [ 15:19:50.078 ] Searching for rootfs
[ 3.398489] [ 15:19:50.079 ] Root device found:
[ 3.709593] [ 15:19:50.390 ] Root device found: /dev/mmcblk0p2
[ 3.711240] [ 15:19:50.392 ] Found dev node: /dev/mmcblk0p2
[ 3.712772] [ 15:19:50.394 ] Checking dev node for errors
[ 3.744397] tegra-xusb 70090000.xusb: entering ELPG
[ 3.745025] tegra-xusb 70090000.xusb: entering ELPG done
[ 3.793294] exFAT-fs (mmcblk0p2): invalid boot record signature
[ 3.793323] exFAT-fs (mmcblk0p2): failed to read boot sector
[ 3.793343] exFAT-fs (mmcblk0p2): failed to recognize exfat type
[ 3.794142] F2FS-fs (mmcblk0p2): Magic Mismatch, valid(0xf2f52010) - read(0x690aff3a)
[ 3.794170] F2FS-fs (mmcblk0p2): Can't find valid F2FS filesystem in 1th superblock
[ 3.794581] F2FS-fs (mmcblk0p2): Magic Mismatch, valid(0xf2f52010) - read(0x41f41e1f)
[ 3.794607] F2FS-fs (mmcblk0p2): Can't find valid F2FS filesystem in 2th superblock
[ 3.794641] F2FS-fs (mmcblk0p2): Magic Mismatch, valid(0xf2f52010) - read(0x690aff3a)
[ 3.794664] F2FS-fs (mmcblk0p2): Can't find valid F2FS filesystem in 1th superblock
[ 3.794688] F2FS-fs (mmcblk0p2): Magic Mismatch, valid(0xf2f52010) - read(0x41f41e1f)
[ 3.794710] F2FS-fs (mmcblk0p2): Can't find valid F2FS filesystem in 2th superblock
[ 3.797859] [ 15:19:50.479 ] FATAL: ERROR: /dev/mmcblk0p2 mount fail...
[ 3.876309] [ 15:19:50.557 ] Boot drive found
[ 3.397086] [ 15:19:50.078 ] Searching for rootfs
[ 3.398489] [ 15:19:50.079 ] Root device found:
[ 3.709593] [ 15:19:50.390 ] Root device found: /dev/mmcblk0p2
[ 3.711240] [ 15:19:50.392 ] Found dev node: /dev/mmcblk0p2
[ 3.712772] [ 15:19:50.394 ] Checking dev node for errors
[ 3.744397] tegra-xusb 70090000.xusb: entering ELPG
[ 3.745025] tegra-xusb 70090000.xusb: entering ELPG done
[ 3.793294] exFAT-fs (mmcblk0p2): invalid boot record signature
[ 3.793323] exFAT-fs (mmcblk0p2): failed to read boot sector
[ 3.793343] exFAT-fs (mmcblk0p2): failed to recognize exfat type
[ 3.794142] F2FS-fs (mmcblk0p2): Magic Mismatch, valid(0xf2f52010) - read(0x690aff3a)
[ 3.794170] F2FS-fs (mmcblk0p2): Can't find valid F2FS filesystem in 1th superblock
[ 3.794581] F2FS-fs (mmcblk0p2): Magic Mismatch, valid(0xf2f52010) - read(0x41f41e1f)
[ 3.794607] F2FS-fs (mmcblk0p2): Can't find valid F2FS filesystem in 2th superblock
[ 3.794641] F2FS-fs (mmcblk0p2): Magic Mismatch, valid(0xf2f52010) - read(0x690aff3a)
[ 3.794664] F2FS-fs (mmcblk0p2): Can't find valid F2FS filesystem in 1th superblock
[ 3.794688] F2FS-fs (mmcblk0p2): Magic Mismatch, valid(0xf2f52010) - read(0x41f41e1f)
[ 3.794710] F2FS-fs (mmcblk0p2): Can't find valid F2FS filesystem in 2th superblock
[ 3.797859] [ 15:19:50.479 ] FATAL: ERROR: /dev/mmcblk0p2 mount fail...
[ 3.876309] [ 15:19:50.557 ] Boot drive found
Is installing DLC unlockers the same process as installing a normal DLC? Anytime I use DBI it says "[Transfer OK] [Signature: invalid]. The base game plays just fine, but would like to have the DLC as well.
As far as I know, it is. Signature being invalid means that the file has probably been tampered with so make sure that you're getting it from a trusted source.
I've tried from probably 5-6 different (reputable) sources. All have the same outcome, and unable to activate the DLC in game. Any other ideas on what I could try to get it to work?
Which game are you trying to install the DLC for?
Personally, I make sure that I have the latest Hekate, Atmosphere and supported firmware, as well as latest DBI and sigpatches/sys-patch and that usually does the trick. There are some games with require you to link NNID in order to work so, since I don't have one, I use linkalho for that to generate a fake one. The only problematic game for me was the Animal Crossing: New Horizons where I needed to link a real NNID in order to get some in-game Mario-themed items.
Disney Dreamlight Valley trying to install the Rift in Time DLC. I guess there's a cutscene that activates when you launch the game after the DLC is installed, but I've never gotten the cutscene to trigger or for the DLC to work. I've tried using the liinkalho but haven't gotten that to work. I've tried reinstalling base game and DLC, installing separately. Nothing's worked. I'm on 18.0.0, AMS 1.7.0. I updated a few weeks ago after not having been using my switch for a while, I updated sigpatches when I updated firmware.
Good day. I come here because I'm a little desperate and in hopes this is the right place to find some help. I recently modded my OLED Switch through a modchip. I paid the services of a local videogame store to do the job as I'm not even remotely tech savvy enough to open up my console, let alone solder an electric component to it without destroying it. From that moment to today the console worked great on handheld mode, I installed several pieces of homebrew and even backed up some of my physically owned games and all worked great.
The issues started, however, when I tried to play on docked mode, as any controller I tried to pair to the console disconnected either immediately or after a few instants of use. I tried both the stock joycons as well as a third party controller from PowerA, both worked flawlessly before installing the modchip, and on docked mode, but now they are unusable. Sometimes I can get the PowerA controller to pair up and work properly, but only if I'm extremely close to the docked console. If I move to my couch, about 1.5 meters away, it immediately disconnects, which obviously never happened before. This issue happens both on OFW and CFW.
I tried several alleged fixes posted online, some here on gbatemp even, and none of them worked. I disabled the option to enable USB 3.0 on my CFW. I tried applying a script that synced bluetooth data from the OFW to the CFW true the TegraExplorer payload, I tried detaching and reattaching all my controllers on both OFW and CFW and vice versa, on different orders. I deleted sys-clk from the SD card. Nothing works.
¿Is there anything else I can do? ¿Has anyone gone through a similar issue?
For reference, my Switch is running the current versions of both Hekate (6.2.0) and Atmosphere (1.7.1) as of the time of writing, and the official firmware is the most recent one as well (18.1.0). I don't know what other information about the console would be useful, that's all I can think of for now. I already tried looking for information on both the Hekate and Atmosphere official Github repositories but nothing came out of that either.
Any help would be much appreciated. Thanks in advance!
The issues started, however, when I tried to play on docked mode, as any controller I tried to pair to the console disconnected either immediately or after a few instants of use. I tried both the stock joycons as well as a third party controller from PowerA, both worked flawlessly before installing the modchip, and on docked mode, but now they are unusable. Sometimes I can get the PowerA controller to pair up and work properly, but only if I'm extremely close to the docked console. If I move to my couch, about 1.5 meters away, it immediately disconnects, which obviously never happened before. This issue happens both on OFW and CFW.
I tried several alleged fixes posted online, some here on gbatemp even, and none of them worked. I disabled the option to enable USB 3.0 on my CFW. I tried applying a script that synced bluetooth data from the OFW to the CFW true the TegraExplorer payload, I tried detaching and reattaching all my controllers on both OFW and CFW and vice versa, on different orders. I deleted sys-clk from the SD card. Nothing works.
¿Is there anything else I can do? ¿Has anyone gone through a similar issue?
For reference, my Switch is running the current versions of both Hekate (6.2.0) and Atmosphere (1.7.1) as of the time of writing, and the official firmware is the most recent one as well (18.1.0). I don't know what other information about the console would be useful, that's all I can think of for now. I already tried looking for information on both the Hekate and Atmosphere official Github repositories but nothing came out of that either.
Any help would be much appreciated. Thanks in advance!
Since you're on a fairly recent firmware revision, I doubt that updating to the latest and greatest will fix the issue you're having, but you can try that as well.
I've checked the DLC file and, indeed, signature is invalid, while the hash is fine which usually isn't bad thing if it's from a trusted source. I've read that people are having trouble triggering this DLC even with the legit purchases, so it's not an isolated issue and could be the problem with the game as well.
Sadly, none of the installers are currently being actively maintained so that may be a problem as well.
not sure if this is the right place to post i just put CFW on my switch again after months of not being able to get it to work. I'm able to get into emummc but every single time i inject the payload i have to complete the initial switch startup process./ how do i fix this?
Post automatically merged:
when i am able to get into the payload option it says 2162 0002
The invalid signatures usually stem from one of two things. XCI converted to NSP, or the header was tampered with. In the case of DLC it is likely the latter. I have noticed that DLC releases from both SUXXORS and VENOM (maybe more) have modified headers to include their scene name in them. While it shouldn't effect the DLC working properly, it's still a shady and shitty practice. I wish scene rules would put an immediate stop to it.
I recommend making sure Atmosphere and Hekate are both up to date and working properly, then updating your Switch to 18.1.0, and completely ditch sigpatches and use sys-patch instead. Also, did you install the Dreamlight Valley 1.11.0 update? You only mentioned installing the base game and DLC.
Attachments
Last edited by RedColoredStars,
Yeah, I just updated to 1.11.0 a day or two ago, it came out last week. I was previously on 1.10.2. The base game is only like 34mb and the update file is 3 or 4gb, requires the update to play. Either way currently on 1.11.0. I'll try updating to 18.1.0 tonight, is sys-patch the same process as installing sigpatches?
You just extract the contents to your SD card. So yes. Make sure to use the latest version here:
https://gbatemp.net/download/sys-patch-1-5-2-binary-fw-18-1-0-atmosphere-1-7-1.38686/
Found my son's old switch long abandoned in a box in the closet. Unpatched so I jailbroke it and added a bunch of games.
Here's my question/issue - my son had dozens of little freeware/shovelware games he had downloaded that aren't actually on the switch anymore (new SD card), but Tinfoil and the Switch OS still list them in the library. Effectively the library now has a bunch of games listed, and some of them are really there (the ones I added) and some are not (these).
These are not games someone over elementary school age would want, so I'd like to delete them. Do I have to do it one at a time or is there a way to delete multiple games at once?
Thanks!
Here's my question/issue - my son had dozens of little freeware/shovelware games he had downloaded that aren't actually on the switch anymore (new SD card), but Tinfoil and the Switch OS still list them in the library. Effectively the library now has a bunch of games listed, and some of them are really there (the ones I added) and some are not (these).
These are not games someone over elementary school age would want, so I'd like to delete them. Do I have to do it one at a time or is there a way to delete multiple games at once?
Thanks!
- No one is chatting at the moment.
haven't seen robot chicken media in ages