Open N-Tayble opened 4 years ago
I'm having the same problem. I've been able to use Hakchi2.31 to restore the original kernel. Otherwise, no matter what version of Hakchi CE I try to use, it gets to 92% and times out at what looks like the last reboot before completing.
I've tried:
I've had the SNES Classic plugged into a monitor while trying to install the custom Kernel; when it's at the timeout, I can see a Hakchi splash screen with "Knock Knock", "Hakchi" and "hakchi.net" in mostly green text. When in this state, if I unplug it (which is the only way to turn off the system), when I turn it back on, it just hangs on this screen.
During the kernel install, I do see it go "Online" in the bottom left corner once or twice, but by the end, it doesn't matter.
Quick update. I have been able to add SNES games using Hakchiv2.31, so it can be done on my SNES Classic. Not sure why Hakchi CE versions always give the error "Your device is taking too long to reboot" when trying to install the Kernel.
I restored to stock and attempted to Install the custom Kernel using hakchi CE 3.8, but failed again. Attached debug log. Too_Long_To_Reboot_Debug_Log.txt
The hakchi, emulates a USB Ethernet adapter when connecting to computer. You must have a drivers problem. Try to locate the new NDIS network adapter when connecting the NES Classic. If doesn't show or show a driver error use the instructions on page for manually install the driver
at the "\driver\" folder of "hakchi2-ce-3.8.0-release.zip" there is a installer: "classic_driver.exe" you could use to manually install the drivers, old versions of Hakchi uses others drivers, you may be need to uninstall old drivers before new ones works.
Also look the post of DanTheMan827 on this URL: https://github.com/TeamShinkansen/Hakchi2-CE/issues/246#issuecomment-526645956
Is it possible for you to explain that in more detail? Sorry, this is all sorta new to me
Is more a Windows issue than a Hakchi one, so you need a little windows knowledge in order tobmake the diagnostics
Thanks for the info, I think I'm further. I used Device Manager to uninstall the drivers. It showed a "NES mini" before uninstalling (that was the driver installed from v2.31). After manually using the driver executable in the \driver folder, Device Manager now shows it as Nintendo Classic.
I must still be missing another driver though. Now when the Kernel Install gets to 92% and tries to reboot, Windows 10 gives me a "USB Device not recognized" error. Per the #246 thread, I don't see which Network Adapter may need updating, as 'Next, check under network adapters for anything resembling "Samsung classic" or "classic"'.
After unplugging the system and reconnecting, I can see a missing USB driver, so I don't know that the Network Driver is the problem. Is there a Windows driver I should choose from manually? If I run the manual driver again, it doesn't fix this one.
More steps taken. I've tried downloading Zadig, selecting the "Unknown USB Device" and installing the Driver. It says it's successfully installed, but doesn't show a "current" driver in Zadig, and it's still had the warning in Device Manager. I've also tried, with the same results, by choosing the WCID version of the driver.
I've tried uninstalling the driver in Device Manager before installing the drivers from Zadig.
I also just restored it and tried Installing the Kernel from CE v3.5.3. I did get a success message and a message saying I could now add games to my system. However, the lower left indicator still is red and Offline. When trying to sync games, it just waits for the system to be turned on. Whether in FEL mode or just turning it on, it's not recognized (not surprised). All I see is the "Knock Knock Hakchi" green splash screen.
Using the uninstall from 3.5.3 does successfully restore the SNESC to normal settings though, which is more than I can say when I've tried the same thing from 3.8.
Wanted to provide a quick update. Turns out following restoring my system using a kernel I downloaded solved my problem. Apparently the stock kernel that was dumped before starting any modding was the problem. So, while it looked like and functioned like it was back to stock, something still must not have fully been restored.
My recommendation for anyone else having "Reboot too long" issue is to not trust your original kernel dump. FWIW, I used 'kernel-dp-snesusa-release-v2.0.14-0-gd8b65c6.img'. By using this, hakchi 3.8 Uninstall finally worked and I successfully Installed the custom kernel.
I'll be adding games next, but after getting this far, I imagine I should be in the clear.
Thanks fir your advice,. When first i make the backup of my firmware I also comiste it checksum with the downloades one and match. But you must have the user backup also
One more update, I've been able to add multiple games for multiple systems and all is running smoothly, so no new problems anymore that I can see. Thanks for all the guidance.
Can you give me steps on how to get 3.8 to work
Are you having a specific problem/question? There are plenty of walkthroughs on youtube and elsewhere to get you started.
@tjc9801 I am seeing a similar issue on my Sega Genesis Mini. It too, does not reboot when trying to install the kernel step.
I went ahead and installed the classic driver from the driver folder but I think it just had drivers for the SNES Classic if I'm not mistaking. On my device manager, I can see Allwinner FEL Device listed which is my Genesis Mini but at this point I'm not sure what I should do in order to remedy my issue and get the Genesis to reboot and complete the installation. I saw someone had suggested uninstalling the driver which I also did, but it did not work either. Someone else had suggested allowing the application on the allowed list for Windows Firewall but it too, did not work.
Let me know if you, or anyone else has any suggestions on getting the Genesis Mini to reboot and complete the installation of Hakchi 3.8 CE
@albertperk Sounds like my problem (but on the SNES mini), which was remedied by not trusting my backed up kernel. I'd say search online for a fresh kernel and restore/uninstall custom kernel using that, then start over. Hopefully that helps you like it did in my situation.
@tjc9801 Gotcha. I'll see what I can find. Any ideas for search query to find it? "Genesis Mini Fresh Kernel" maybe? Also once I do find a fresh kernel, I assume that I'll go to Kernel > Advanced > Boot Custom Kernel From RAM right? Or somewhere else?
Sorry for all the questions; first time attempting this on my Genesis Mini after watching all the How To videos. Thanks again for your assist!
It looks like installing a kernel on the Genesis Mini may not be possible, according to this thread - https://github.com/TeamShinkansen/Hakchi2-CE/issues/353
@albertperk That sounds right to restore a backup Kernel from 3.8. I think there's a couple options. I may have used an older version of Hackchi that seemed to reliably restore the kernel, but any version should work as long as you can point to the specific kernel you want.
In terms of searching, if you join the "Rock the Classics" discord, this is the info they have (though I don't see the Genesis): So, you used Hakchi2.30, messed up your console, and now it just shuts down right away... and of course you want to fix it, right?
Well, depending on which system you have, you'll have to find one of these clean kernel backups from your favorite search engine (hint: search for the filename in quotes)
Super Nintendo / Super Famicom Classic
Famicom Classic
NES Classic (2016 Release)
NES Classic (2018 Release)
Shonen Jump Special Edition Famicom Classic
Then after you have the proper one for your system, you're going to need to download the latest release of Hakchi2 CE from http://github.com/teamshinkansen/hakchi2/releases and extract it to a nice and clean folder.
Enter FEL mode and select Kernel > Uninstall while holding shift, this will prompt you for a clean kernel dump (see above).
If you do not know what FEL Mode is, type !fel in main chat for a better explanation.
Hakchi should be removed from your system and it will start normally.
At this point, you can re-install hakchi using Hakchi2 CE and everything will work normally.
@tjc9801 , thank you for the extensive description of recovery steps.
So, you used Hakchi2.30, messed up your console, and now it just shuts down right away... and of course you want to fix it, right?
I believe, I've had the same problem, but with my snes mini and the version of Hakchi I used initially was 2.2.31.
Enter FEL mode and select Kernel > Uninstall while holding shift, this will prompt you for a clean kernel dump (see above).
I've been trying to do this in Hakchi 3.8.0 release version, and have got the following:
So at no point have I been prompted to select a custom kernel from disk. Do you have any idea how I can solve my problem?
Thanks in advance.
@arturwdowiarski If you go under Kernel -> Advanced -> Dump Original Kernel (Legacy), you'll be prompted for the kernel you want to use. That's where you can select the one you found online.
Hi, remember put the Mini in FEL mode is easy:
@tjc9801 , it seems that Kernel -> Advanced -> Dump Original Kernel (Legacy) actually tries to dump the kernel from my snes mini on disk. It doesn't allow me to upload a kernel from disk to my snes mini.
Do you have any other ideas? I'm starting to get desperate here ;P.
Is there anybody from Hakchi team here reading this?
Hold shift when clicking uninstall, it will prompt for a kernel file to use.
I had this problem and probably fussed for 3 hours before fixing it. If anyone is still having and issue with this, Heres what I did to fix it.
-FRESH Hackchi 2 CE install to new location (dont combine files from other versions/installs) -Rename the hackchi.exe to something different like hackchi2CE (cant confirm this matters but its what I did) -Add exception to the firewall using that exe -Put in FEL Mode (unplug cable, power on, hold reset, plug in cable, let go of reset after a few seconds) -Dont worry if theres no light on the SNES (its getting power) -go to KERNEL > install/repair
Good luck
Still has the same issue. I tried all different tricks - no luck.
I'm having the same problem. After a while (2 years?) I'm trying to add new games to my previously-hacked SNES Mini. I'm using the same PC and USB cable and Hakchi install to connect my SNES Mini. When I turn it on, Hakchi doesn't detect the SNES Mini. If I try to reinstall the kernel, it can tell it's been put into FEL mode, but the console hangs at the reboot step (Hakchi logo on screen).
I'm complete disabled my Windows Firewall, uninstalled my VPN software (NordVPN) and still it won't connect. Am I missing something? The only thing that's changed since last time is I installed Windows 11, are there any issues there I'm not aware of?
My SNES Classic will not reboot when Hakchi wants it to. It will always say that "Your device is taking too long to reboot." It is also displayed as Offline at the bottom left and when I try to synchronize games, it can't read that the console is on.
This is a real console, for one. I had used the exact same USB's and computer to use Hakchi on it once, which worked fine. I do not remember if the first time I used this was ce or not. When it says that it's trying to reboot, the power LED on the console will turn on, and stay on, even though my computer does not detect anything.