|
| ||
| Views: 1,609,122 | Main | Rules/FAQ | Memberlist | Active users | Last posts | Calendar | Stats | Online users | Search | 11-21-24 09:44 AM |
| Guest: | ||
| 0 users reading Certain apps crash on launch; problem is persistent across NAND images. | 1 bot |
| Main - Unbricking and fixing - Certain apps crash on launch; problem is persistent across NAND images. | Hide post layouts | New reply |
| Wowfunhappy |
| ||
|
Newcomer Normal user Level: 6 Posts: 1/5 EXP: 663 Next: 244 Since: 04-05-15 Last post: 3509 days ago Last view: 3506 days ago |
Hi! I posted about this on GBATemp, but it's been three days and no one has been able to provide useful information, so I thought it would be worth asking here.
I have a NAND-modded, small New 3DS. I paid someone else to install the mod for me, and I'm relatively confident he did a good job. I did not begin having problems until a while after the mod was installed. I had successfully performed an EU -> US region change, and was flashing back and forth between different NAND images. For a while, this worked fine. At one point, however, I went from a 9.6 US NAND to a 9.6 EU NAND. I had successfully done this at least once before, but this time, something went wrong. Upon trying to open certain applications and applets, the system would crash to a black screen (with the standard error message). No problem, I figured—I had tons of NAND backups. I first tried flashing my 9.6 US NAND image, which had been working fine less than an hour ago. Same issue. I have since tried flashing other images, all of which were previously working fine. The problem refuses to go away. Firmwares 9.0–9.2 run perfectly, but the problem returns as soon as I run a system update. I have not tested 9.3, but firmwares 9.4, 9.5, and 9.6 all experience the issue. Does anyone know what could be happening here? What could cause an issue to persist across different NAND images? And lastly, is there any place other than the NAND and SD Card where rewritable data is stored? Thank you so much! Things I have tried: -Removing/replacing/reformatting the SD card. -Verifying that images are being written properly. -Disabling Wifi. -Updating via a Xenoblade game cart. -Performing a system format before updating. Broken Software: -NNID Settings -Camera Applet -Face Raiders -Notifications -Xenoblade -eShop -Amiibo Settings -Streetpass Plaza -MiiVerse, but only when an NNID is linked Working Software -AR Games -Web Browser -Cubic Ninja -Friends List -Activity Log -Camera Application -Mii Maker -Download Play -3DS Sound -Health & Safety -Game Notes -MiiVerse when no NNID is linked |
| StapleButter |
| ||
|
Member blarg Level: 30 
Posts: 67/184 EXP: 151356 Next: 14513 Since: 10-27-14 From: France Last post: 2648 days ago Last view: 2558 days ago |
This looks related to online functionality, but not entirely sure. Weird.
Maybe Nintendo detected your shit and banned you from their services. That doesn't explain all of it, though. ____________________ blargSNES -- SNES emu for 3DS More cool stuff |
| Wowfunhappy |
| ||
|
Newcomer Normal user Level: 6 Posts: 2/5 EXP: 663 Next: 244 Since: 04-05-15 Last post: 3509 days ago Last view: 3506 days ago |
Posted by StapleButter I thought of that, but I performed an experiment which (I think) makes it impossible: 1) Disable WiFi 2) Flash vanilla NAND (made long before I started messing with stuff) 3) Update via Xenoblade After the above steps, the problem is still present, even though this NAND has not been connected to the internet in almost a month. Plus, the apps crash within two seconds of being launched, if even that much. The app never starts—the crash happens midway through the "Nintendo 3DS" loading animation. In that little time, it's hard to believe that the program is getting instructions from the internet. |
| StapleButter |
| ||
|
Member blarg Level: 30
Posts: 68/184 EXP: 151356 Next: 14513 Since: 10-27-14 From: France Last post: 2648 days ago Last view: 2558 days ago |
All I can think of is something getting stored somewhere else than in the NAND (or in some NAND spot that didn't get affected by your flashes), and fucking things up. Weird.
Unrelatedly, it would be nice if you avoided editing your posts so much just to do little formatting changes  We have a preview feature, you can use that.____________________ blargSNES -- SNES emu for 3DS More cool stuff |
| Wowfunhappy |
| ||
|
Newcomer Normal user Level: 6 Posts: 3/5 EXP: 663 Next: 244 Since: 04-05-15 Last post: 3509 days ago Last view: 3506 days ago |
Posted by StapleButter Does this exist? I know that keys etc are stored in the CPU, but that's read-only. |
| StapleButter |
| ||
|
Member blarg Level: 30
Posts: 69/184 EXP: 151356 Next: 14513 Since: 10-27-14 From: France Last post: 2648 days ago Last view: 2558 days ago |
No idea. ____________________ blargSNES -- SNES emu for 3DS More cool stuff |
| Wowfunhappy |
| ||
|
Newcomer Normal user Level: 6 Posts: 4/5 EXP: 663 Next: 244 Since: 04-05-15 Last post: 3509 days ago Last view: 3506 days ago |
ErrDisplay log:
PID:0x00040130_00004002
Exact same entry was generated five times from launching five different apps.
REV:0061031 AID:0xFFFFFFFF_FFFFFFFF ADR:0x00101E6C RSL:0xF9617590 0004013000004002 is the NFC title, which was updated on 9.3, so that explains why the error doesn't occur on 9.0-9.2. |
| StapleButter |
| ||
|
Member blarg Level: 30
Posts: 70/184 EXP: 151356 Next: 14513 Since: 10-27-14 From: France Last post: 2648 days ago Last view: 2558 days ago |
So that means that for whatever reason the NFC hardware is fucked.
Or you have the old 3DS NFC module installed. ____________________ blargSNES -- SNES emu for 3DS More cool stuff |
| Wowfunhappy |
| ||
|
Newcomer Normal user Level: 6 Posts: 5/5 EXP: 663 Next: 244 Since: 04-05-15 Last post: 3509 days ago Last view: 3506 days ago |
Installing the Old 3DS NFC module actually (for whatever reason) allows most of the broken apps to launch under 9.4. A few—namely, the ones that actually use NFC, such as Amiibo settings—crash to the home menu (although not a black screen!), but it's still a massive improvement. On 9.6, however, it just causes infinite loading screens.
For whatever it's worth: the problem has randomly disappeared twice. The first time it happened was in USA 9.6 firmware. Everything continued to work even after rebooting the console, but broke again after I connected my NAND mod (to back up the NAND—I didn't write anything!). It fixed itself again yesterday, on EU 9.6. This time, however, it only lasted until I rebooted the console. In both cases, I cannot for the life of me think of anything special that I did. |
| dark_samus |
| ||
|
Newcomer Normal user Level: 7 Posts: 2/8 EXP: 1330 Next: 118 Since: 06-02-15 Last post: 2996 days ago Last view: 2796 days ago |
I'd say most likely that this is a hardware issue.... isn't the NFC module disconnectable from the motherboard? If so it's likely that there is a connection issue and something happens (you bump the unit or move it in a certain way) that causes the connection to break again and causing the random intermittent issues... |
| nopy4869 |
| ||
|
Newcomer Normal user Level: 3 Posts: 1/1 EXP: 57 Next: 71 Since: 09-28-15 Last post: 3342 days ago Last view: 3333 days ago |
It is entirely possible that the nand chip is gaining bad blocks. That might account for the changed behavior when you started using a new NFC module(one located in a different place on NAND).
I don't have a good explanation for the random fixing thing though. |
| Syphurith |
| ||
|
Member Normal user Level: 18 Posts: 13/59 EXP: 26088 Next: 3809 Since: 10-26-15 Last post: 3234 days ago Last view: 3184 days ago |
I second the post by nopy. The NAND chip of your new 3ds is a MLC one, which holds 2 bits in a cell. MLC has a typical write lifespan as 10K times for every cell, however this is for MicroN produced ones, Check here for typical times. Not only your flashing would cost its write cycles, the normal use of your console, when writing files, would cost some too. So, I doubt what stored in your NAND has already been broken.
To check it is or not, just get your NAND Fat xorpad to decrypt both images, the "working" one you flash which was dumped when it was working at last, and the "current" one you dumped after flash the "working" one. Decrypt both images with xorpad, and extract the "titles" folder to be compared, you can use the tool WinMerge2011 for such comparison. If you don't care about totally brick it, or it confirmed your NAND chip is worn out, you might want to try replace the chip yourself. If so, good luck - the chip is just around where you connect the pins, not hard to be found, and please notice you better get a same chip of product id. |
| Main - Unbricking and fixing - Certain apps crash on launch; problem is persistent across NAND images. | Hide post layouts | New reply |
|
Page rendered in 0.017 seconds. (2048KB of memory used) MySQL - queries: 26, rows: 85/85, time: 0.006 seconds. ![[powered by Acmlm]](img/poweredbyacmlm.png "powering nostalgia")
Acmlmboard 2.064 (2018-07-20)© 2005-2008 Acmlm, Xkeeper, blackhole89 et al. |