Stuck at "waiting for your NES Mini" when synchronising games

[Auss1e]

I'm trying to add some games to my NES Classic on 2.16b but when it asks me to plug in the NES classic and turn it on (just turn it on. none of the hold reset then turn on power) it doesnt pick up my NES Mini. It picks it up when I hold the reset then turn the power on and let go of it after a few seconds but it doesnt install the games. The driver is installed.

[ClusterM]

Hi. Seems like clovercon mod is not installed for some reason. Can you turn your NES Mini (without reset button) and check device manager? Can you see it there? Driver installed? Can you say VID and PID of device?

[sao123]

I have this same issue. Cant get past waiting for your NES Mini to add games to an already modded system.

if I turn it on without holding reset, my windows 10 system sees: CLV-S-NESY Device USB\VID_1F3A&PID_EFE8\86581af8a9376c118000 Driver Name: oem6.inf

if I trn it on while holding reset my windows 10 system sees: NES Mini Device USB\VID_1F3A&PID_EFE8\5&2301df1d&0&1 Driver Name: oem6.inf

Both say: This device is working properly.

[DANTHEMAN9]

I have this same issue it works fine on 2.12 but after that, I get stuck at "waiting for your NES Mini" and ends with write error. Try 2.13E, 2.14B, 2.15 and 2.16C not sure what change after update 2.12 For it to stop working for me?

[Neite99]

Hey all,

Just had the same issue. It seems to be with the newer version they just released. You can tell by the emblems changing on the front of the box. It also says BFC-CLV-S-NESA-USZ-C3 on one of the side flaps. The original one I have says C0 on the end.

2.15 and 2.16 got stuck in the same place you guys are talking about on the newer model. I tested right after with my older version and it loaded just fine on both

2.14B loaded the games fine on the new version. I would use 2.14B until Cluster gets a chance to figure this out.

@Cluster Let me know if I can get you any debug files or anything else I can help with. Your the man!!

[flywithsean]

I have the -C3 model as well and get stuck on the sync new games screen.

Im using 2.16c

[Neite99]

Just tested for quite awhile. The only way I could get the problem to reoccur was to factory reset in 2.16C and then flash custom kernel from there and then try to sync, which it will never do because it just gets stuck waiting for the nes.

Odd think is that if you flash the custom kernel in 2.15 it will load just fine when you sync in 2.16C

So to all paying attention. Just make sure that the initial custom kernel flash (one of the first steps) is done in 2.15 or 2.14B. then you can use 2.16C like normal.

BTW. I did reset my old one to factory in 2.16C and flashed the recovery from the same image but it synced just fine. It only happened on the new one.

Hope that helps everyone.

Edit:

aaand now I can't recreate it. Weird.

I have a couple people with new systems coming over in the next few days. I will try and pinpoint it more then.

To anyone having the sync issues. Just use 2.15 or 2.14b to dump the original Kernel and then flash the custom one in there. Then jump back (if you want to) 2.16c and go about business as usual.

[flywithsean]

Not sure what you did Neite99 I went back to factory in 2.16c then flashed the custom kernel in 2.15 and getting the same thing happening in 2.15 that was happening in 2.16c. Its appears to flash fine but when you go to add games it acts like it isn't connected. And this is with the -C3 model. I am suspecting Nintendo did something different on these

[Vertabray]

I have the same issue. I can dump the kernal but unable to copy games. Appears that 2.13e works but after the change to LibWinUsb its a no go

When just turning on I get USB\VID_057E&PID_2041&REV_0233 When using reset method I get USB\VID_1F3A&PID_EFE8&REV_0233

[Neite99]

What modules are you installing with it?

Do you have an image from a different system you can put in the dump folder you can use to see if that fixes it?

After I got it to run once I couldn't recreate the problem. I will have a couple systems to test with in the next few days. Hopefully we can pinpoint the issue.

[flywithsean]

As for me I am trying no modules just a custom kernel flash and then adding games.

[ringbuffer]

I've had the same issue. I can only sync if I flash with the custom kernel first.

[flywithsean]

@ringbuffer which version of the NES Classic do you have the -C0 or -C3?

[willysjeepman]

I bought an NES Classic last week as part of the last batch. It appears to be a -C3. Using hakchi 2.16 I experienced the same issue.

Here's the thing, the first time I used hakchi, I dumped the original kernel for safekeeping, downloaded the custom kernel, and was able to sync over additional ROMs. All was well.

It was only when I reattached my NES Classic back to my PC to add more ROMs that I experienced the "waiting for the NES" prompt.

If I cancel out of the "waiting for the NES" prompt and re-download the custom kernel, I can sync ROMs. (that's while the NES Classic is still in developer mode)

Since it appears that the NES Classic soft-boots after the custom kernel is downloaded, the problem may be isolated to a "cold-boot" of the NES Classic.

[Neite99]

@willysjeepman

That sounds exactly right. I couldn't recreate it after the first time but it makes sense that it would get stuck there.

I am modding one tonight. I will test this theory on my end.

It seems like it just get stuck. Like it can't use the driver in a certain state. I am curious if that happens with the old units too so I will test that later as well.

[flywithsean]

@Neite99 So what did you discover on the ones you modded? I still can't get anywhere for adding ROMS

[Neite99]

With the ones I did after I haven't had any issues. I think it was like willysjeepman said. If it's not a cold start then it seems to load them.

Have you tried restoring to factory?

I would also try flashing the custom kernel with a different image.

You may want to redownload the program too just in case you got a corrupt file somewhere

Let me know what you have tried. I will help where I can.

[flywithsean]

Ive restored to factory, Tried an older version of Hakchi2, and every variation I can think of. When I load the custom kernel though it immediately reboots without any chance of being able to load ROMs. Were the ones you modded from the last batch?

[Neite99]

Okay. I have to ask a couple dumb questions but have you rebooted with the USB cable out and have you tried a different cable?

[flywithsean]

just got it to work and what I ended up doing was booting and rebooting and reinstalling the USB driver till it finally worked.

[Neite99]

That actually makes a lot of sense. I uninstalled the driver and rebooted and reinstalled but I didn't think that made the difference. Maybe that's what made the later ones work for me.

Nice work!

[flywithsean]

I was also using 2.17 not that it made a difference

[buddhahat]

Nothing working for me. On a mac using virtual box. Have tried 2.14 - 2.17. Always just get the 'waiting for your nes mini' dialog when I try and sync games.

[Neite99]

@buddhahat

I don't have any experience with the a mac setup but I would guess it is a driver issue.

I would try uninstalling the driver from the windows install and then rebooting the virtual machine and trying to reinstall the driver. Similar to what flywithsean did.

Alternately you could try and flash the custom kernel and then go straight to syncing. It seems like the driver gets stuck somewhere in that process so if you try and add modules in between those steps it may get stuck.

You can add the modules after the games sync.

[flywithsean]

When using VirtualBox after the custom kernel is loaded on delete the USB from the USB list on virtual box in the bottom right of the screen around your windows box and add it again when it says NES and not tablet in flashing mode

[buddhahat]

Thanks so much for the replies fellas. Flywithsean - I followed your instructions to the letter (as completely clueless with all this) and it worked! Have been tearing my hair out for hours over this but now finally able to play Dizzy on my Nes Mini!! You are a star.

[flywithsean]

You are welcome. Game On!!!

[sideshow01]

Another thing that might cause the problem is with the micro USB cable you're using. Make sure it's the right one. I accidentally used the one that came with my bluetooth speaker. Since it's only used as a charger it will not regonize the Nes Mini. So be sure not to make the same mistake as I did. Use the cable that came with the Nes Mini.

[mghtyred]

Any solution to this issue yet? I've scoured the net and nothing. I've been trying for hours now with 0 success. Please help.

[Neite99]

I have it happen randomly but it's usually just stuck. Unplug the NES and just press the power button without the reset button. The led should go red.

If that doesn't work you need to reinstall the driver.

Are you using the latest version of hakchi?

[mghtyred]

I've tried that, and tried multiple versions of hakchi2 including the most recent version. TBH, I am not even sure the kernel is properly flashing. The mod to reset the console using the controller does not seem to work when I try to use it after flashing the new kernel.

[timcannell]

Its happening to me with Win 10 and release build 2.0.20.15 - device with custom kernel wont even boot even though hakchi2 reports success; can flash back to original kernel OK.

[wolf81]

I had the same issue and I kinda did what @flywithsean suggested. Namely the following:

1. Go to Virtual Box app.
2. Remove the "Nintendo ..." setting from Ports > USB screen.
3. Disable the "Onda …" setting from Ports > USB screen.
4. Re-add the "Nintendo …" setting to the Ports > USB screen.
5. Restart VM.

Now I am able to install the games. Perhaps fewer steps are actually needed, but the above worked for me.

[HogCall64]

After Synchronice selected games with NES Mini is clicked during the Building the folder structure...

Mine is throwing the error:

Sorry, there are 216MBytes of games, it's too much.

Total writable memory size 0.0MBytes Available Memory for games: -10.0Bytes Used by saves: 0.0MBytes Used by other files: 0.0MBytes

Any ideas on fixing this? It's brand new just picked it up today, and I'm installing on a mac using virtualbox.

[welljose]

Hello, Everyone! I was facing a very similar issue and following the USB driver clues (I'm using Windows 10 Pro and my laptop just have USB 3.0 ports), I discovered Zadig and emulated an older version of the USB Driver. SOLVED!

[papat444]

Hi, can someone help me? It's been stuck for a long time and i don't know what to do!

[alejas7]

Just Reset the Kernel and problem fixed