search

d0k3 / GodMode9

GodMode9 Explorer - A full access file browser for the Nintendo 3DS console :godmode:
GNU General Public License v3.0
2.15k stars 194 forks source link

Bonus Drive formatted New3DS's screen blinked #79

Closed MelonGx closed 7 years ago

MelonGx commented 7 years ago

I don't know if it's a BonusDrive issue or a Luma3DS issue. Unchecking all boxes of Luma3DS setup can reduce the blink but cannot remove it.

To fix this problem, we need to either uninstall B9S or uninstall BonusDrive. (Both of them are confirmed myself.)

But I need to restore a 1.8GB full NAND backup in order to uninstall BonusDrive. If I only had 1.2GB minimized NAND backup, then the BonusDrive would be still there after restored it.

d0k3 commented 7 years ago

The bonus drive can't cause this, absolutely impossible. This is a N3DS, right? Can you give me a more detailed description of exactly what you did? And, did you actually try restoring a minsize backup?

Also, is anything special about this console?

MelonGx commented 7 years ago

Minsize never wipes out Bonus Drive. If it could, I would have already resolved my last 1.84GB N3DSLL's blinking problem. I can only uncheck every Luma3DS setting choice to reduce the blinking.

I have 3 1.84GB Toshiba NAND N3DS(LL)s currently (one of them is for sale). Two of them have 1.84GB backup. One of them have only Minsize backup but available to uninstall B9S.

Steps:

  1. B9Sed them
  2. Format Bonus Drive
  3. Reboot and see the blinking happen on touch screen's wide edge
  4. Restore 1.84GB NAND backup which contains no Bonus Drive, to remove existed Bonus Drive
  5. Reboot and see the blinking vanished
d0k3 commented 7 years ago

The bonus drive has nothing to do with this. I've got one, too. There was another issue on that NAND of yours.

arbingordon commented 7 years ago

I set up a bonus drive since it first was available in GodMode9... never had any issues in 4+ nand backups/restorations, you have another issue.

It sounds like your screen is acting up, so I recommend opening it up and pulling the battery out for a bit and then seeing if you still have the issue. I had a screen issue before on my N3DS, where there was a weird flickering issue, which was resolved by doing the former.

MelonGx commented 7 years ago

@arbingordon It doesn't work. Still blinking on that N3DSLL. @d0k3 I'll change the CFW into either ReiNAND or CakesFW. If the blinking still happens on both of them, I can only treat it as either BonusDrive or BonusDrive on specific region's issue. BTW, all my consoles are in JPN region. No USA/EUR/KOR/TWN/CHN.

BTW2, it only blinks on Nintendo 3DS OS, both SysNAND and EmuNAND, it doesn't happen on A9LH/B9S payloads.

BTW3, all my 3 consoles have different blinking. N3DSLL blinks at touch screen strongly. N3DS-A blinks at upper screen strongly. N3DS-B blinks at upper screen weakly but still can be discovered by entering Flipnote 3D, Taiko no Tatsujin, etc. All of them never blinks after uninstalling Bonus Drive or becoming non-exploited.

BTW4, I have tried to record a video about it but I need a 100fps+ recorder otherwise it can't capture the blinking.

arbingordon commented 7 years ago

How long did you leave the battery out?

MelonGx commented 7 years ago

@arbingordon 15 minutes.

ghost commented 7 years ago

This does seem to be a legitimate issue. I'm experiencing it as well, however, it did not trigger for me immediately on creating a bonus drive. I triggered it like this:

  1. Mounted a title from A:
  2. Copied that title's .code to my SD card
  3. Rebooted.
  4. Afterwards, the screens began blinking and Luma would not progress past the splash screen; the screens would never turn back on afterwards.
  5. I saw this issue, re-formatted the bonus drive, and now Luma boots but the screens are still blinking.

Solutions I've attempted:

  1. Left the system off for several minutes.
  2. Pulled the system's battery and waited several minutes.
  3. Pulled the system's battery and discharged any remaining current by holding the power button, then waited a few several minutes.

Notes: Intensity of the blinking seems to go down the longer the system is on, but never disappears entirely. Additionally, there's a whitish border around the edges of the screen.

d0k3 commented 7 years ago

Okay, this seems to be a legit issue. @MelonGx - we need to get behind the real issue. The bonus drive itself resides in unused space and can't have any effect on the system.

Where you using the latest release or the latest hourly of GodMode9? What branch?

Now, do this: Do what you have to do to get this issue on one of your consoles, but make (1) a minsize NAND backup, (2) a CTRNAND backup before. After you got the issue, do the same, so that you now have pre- and post-issue backups of both.

Now, restore the minsize backup from before twice, without rebooting in between. Does that fix it?

Also compare those dumps you made. Where's (which offset) the first difference for the two minsize NAND dumps? Which files are different in the CTRNANDs? You'll need to mount both on PC (via OSFMount) and compare via WinMerge.

d0k3 commented 7 years ago

@MelonGx - just writing this so you can continue your experiments. if you're really, really convinced that the bonus drive is responsible, copy the bonus.bin from S:/ brfore setting it up. Set it up, reboot to check the issue is there. Then boot back to GM9 and write the bonus.bin back to remove the bonus drive. Reboot again. Now, is it gone?

MelonGx commented 7 years ago

I'm going to bed that I will do that 1 day later.

MelonGx commented 7 years ago
  1. Make a full 1.84GB NAND backup
  2. Make a 1.21GB NAND_minsize backup
  3. Make a CTRNAND_FAT backup
  4. Make a bonus_0x26C000 backup
  5. Install Bonus Drive
  6. Make a 1.21GB NAND_minsize2 backup
  7. Make a CTRNAND_FAT2 backup
  8. To see whether the issue happen or not (Since entering Home Menu writes saves into CTRNAND, I do the "2" backups before this step)
  9. If the issue still happens, restore NAND_minsize twice without rebooting in between and check whether the issue is gone or not
  10. Restore the full 1.84GB NAND backup (or anything can remove Bonus Drive)
  11. Install Bonus Drive
  12. Restore bonus_0x26C000 backup and check whether the issue is gone or not
  13. Compare NAND_minsize with NAND_minsize2, CTRNAND_FAT with CTRNAND_FAT2 (Question: Are they all decrypted?)

Now I'm waiting for the processes to be done.

d0k3 commented 7 years ago

Okay, and some more... (1) you can also compile GM9 from up to date master (hourlies page borked atm) also (2) does the problem happen after a poweroff, too? Or only after a reboot?

Also question 13) - the NAND dump is encrypted. Doesn't matter, though, I only need to know where the first change happens.

MelonGx commented 7 years ago

Weird results..... When performing everything on N3DS-A, the issue on N3DS-A didn't happen again even got Bonus Drive formatted. When restoring N3DS-A's bonus_0x26C000 into N3DSLL (which has no 1.84GB backups), the Bonus Drive was gone but the issue on N3DSLL didn't vanish.

MelonGx commented 7 years ago

Just ran them a day. N3DS-A has no symptoms of this issue even with Bonus Drive installed. N3DSLL still blinks even with Bonus Drive uninstalled - Only disabling Luma's choices can reduce the blinking. So I think this is probably a hardware-based legit issue currently. Temporary closing this issue.

MelonGx commented 7 years ago

Try exchanging lower screen on N3DSLL and the blinking never happens anymore even with enabling multiple Luma options. Seems that it's a hardware issue more than others.

d0k3 commented 7 years ago

Exchanging the screens? You mean you had a broken screen on there? Reopening this, just to make sure I know everything I need to know.

MelonGx commented 7 years ago

@d0k3 It's not broken but possibly in a not-so-good condition. Now the blinking on that N3DSLL is mainly caused by enabling Luma3DS Splash when that not-so-good lower screen equipped, regardless of installing Bonus Drive. I can't remember whether it's blinking or not before the first time I set up Bonus Drive & Luma3DS Splash enabled + not-so-good lower screen equipped.

Luma3DS Splash caused nothing when the good lower screen equipped, from yesterday's test.

MelonGx commented 7 years ago

@d0k3 It seems to be an IPS-lower-screen x enabling Luma3DS Splash issue now. Just exploited a Double-IPS N3DSLL with 1.21GB Samsung NAND - which cannot establish a Bonus Drive. The lower screen blinks after B9S installed & Luma3DS Splash enabled.

d0k3 commented 7 years ago

Okay, thank you. Can you close and reopen this issue on the Luma 3DS repo? Also recheck if it still happens with the most recent releases of boot9strap (v1.1) and Luma.

MelonGx commented 7 years ago

@d0k3 Since I checked that not only Luma3DS but also ReiNAND & Corbenik had this problem either, I put it into boot9strap's issue list. BTW 1.1 + Luma3DS + Splash also has this.

(Edit) Since A9LH also has this issue, I close it on B9S's issue list. So it's probably a legit issue or a hardware problem.

ghost commented 7 years ago

Just had this reoccur for me after launching and rebooting from GM9. Seems really random, wish we could get to the bottom of this.

WubTheGame commented 7 years ago

.........what's a bonus drive and what's it for?

ihaveamac commented 7 years ago

@WubTheGame README has information on this

WubTheGame commented 7 years ago

i know, but i just don't really understand its use.

ghost commented 7 years ago

@WubTheGame Either way, GitHub issues are not the appropriate place to ask questions. You've been doing this pretty consistently across multiple 3DS-related repos, could you stop?

WubTheGame commented 7 years ago

sorry... i guess i didn't notice... i'll try to stop.