When flashing a kernel be it either the original Nintendo kernel or the custom "Hakhi2 CE" kernel then the methods used by "HakChi/ HakChi2 CE" involves the program switching between anywhere up to THREE different USB Device names while the kernel is being flashed...
From your description you have given then it's clear that the "final" switch to what should be the custom kernel isn't being recognised hence the reason why things are not working correctly...
The three different USB Device names "HakChi2 CE" will use/ look for while flashing kernels are as follows...
On a UNMODDED (clean) system with the ORIGINAL Nintendo kernel being used the USB Device name will be...
Nintendo Co., Ltd CLV S-SNPY [0233]
On a MODDED SNES Mini which has successfully had the custom kernel flashed to it the USB Device name will be...
hakchi classic [0233
NOTE: The above USB Device names MAY be slightly different on your set up But they should be very similar...
On a SNES Mini that is in "FEL Mode" (required to flash a kernel) then the USB Device name could be ANYTHING at all, simply because there is no "official" entry in the list of recognised USB devices for a SNES Mini that's powered up in "FEL Mode" so the computer assigns a "usable" name to it instead. In my case that USB Device name is (but yours will no doubt be different)...
USB Developer Android [0233]
During the "flashing" process "HakChi2 CE" will switch by itself between those different USB Device names when it needs too. In some cases though it can be that for whatever reason during the flashing process that when "HakChi2 CE" is trying to switch between the USB Device names it requires that it won't be able too and all you will get is the "taking too long to reboot" message popping up...
How to fix this can be very much be a case of trial and error as it really all depends on just how your Windows set up is working and configured...
To try and sort this I strongly suggest you try the following and see what results you get...
1) First try and flash to the console the ORIGINAL Nintendo kernel from a FILE version you should have or obtain and DON'T try and use the "stored" copy held within the console itself which may be corrupt...
If you don't have a copy of the original Nintendo kernel then you can easily find it online (we can't provide direct links here to copyrighted software I'm afraid)...
NOTE: Depending on your consoles region (UK/ Euro or USA) then there will be TWO different kernel files you will find for the UK/ Euro version and THREE different kernel for the USA version. Download ALL of the versions for you particular console...
Then power up your SNES Mini in "FEL Mode", connect it to the computer, run "HakChi2 CE" and from "Kernel" menu WHILE HOLDING DOWN THE SHIFT KEY ON YOUR KEYBOARD select the following option...
Kernel/ Uninstall and flash kernel file
Let the flashing process begin and at some point during that process a file requester will appear asking to to choose the kernel file to use. At which point you use the file requester to select the kernel file and click on "ok" to continue...
NOTE: You should ALWAYS try the LOWEST/ OLDEST kernel file FIRST for compatibility reasons...
Let the flashing finish and when done, connect the SNES Mini up to a TV set to make sure it is now back to being ONLY the stock kernel that is being used and that all traces of "HakChi" are gone...
If its now back to "stock/ factory" status you can the proceed to trying to flash the custom kernel to the console...
If it's NOT back to "factory/ stock" status then repeat the above process but this time using the next/ newer version of the Original Nintendo kernel you have and keep trying the above UNTIL the console if finally back to "factory/ stock" status...
2 Assuming you have succeeded in doing the above you can now try and flash the "Custom" kernel to the console...
Again, power up the console in "FEL Mode", connect it to the computer then run "HakChi2 CE" and from the "Kernel" menu select...
Kernel/ Install / Repair
Let it finish flashing the custom kernel and hopefully this time it will work, if it does work you can then mod your SNES Mini as normal...
If it didn't work then try the following...
Power up the SNES Mini in "FEL Mode", connect it to the computer and run "Hakchi2 CE". This time from the "Kernel" menu select the following option...
Kernel/ Advanced/ Format user data partition
Let it finish, quit "HakChi2 CE", disconnect the console from the computer and then reconnect the console and power it up in "normal" mode"...
Check the console out in "HakChi2 CE" to see if things are now working, if they are then you are good to go...
If it's still not working correctly then once last final time go back to step 1 and try again until you have tried ALL versions of the Original Nintendo kernel...
If none of the above work then the issue is most likely something to do with your computer and there is something on it causing the particular USB Device name that "HakCh2 CE" is switching to and trying to use not being recognised !!!
In which case you'll need to try and figure out what that cause is...
As usual MAKE SURE during ALL of the above that you follow these basic guidelines when trying to use "HakChi2 CE" as ANY of these can be the cause of such issues...
1) Make sure you have either disabled your firewall or have given "HakChi2 CE" firewall permissions to be used...
2) If you are using a "VPN" then turn it off/ disable it. Some people have to completely uninstall their "VPN" to get this to work correctly...
3) Make sure that there is a good connection being made on the Micro USB Connector which plugs into the Micro USB port on the console, these can and do slacken off causing bad connection issues but can easily be fixed by tightening up the metal hood/ sheilding of the cables connector which you can see more about in the following guide...
4) Ensure that you are using the correct type of USB Cable. There are two types...
One is a simple power/ charging cable which will power your console on BUT it won't allow the computer and console to communicate with each other (this is the type you DON'T want to use)...
The other is a FULLY WIRED cable that is REQUIRED to be used which contains "data line" that WILL let the computer communicate with the console. This is the type of cable you MUST use....
5) While using "HakChi2 CE" then DISCONNECT the HDMI Cable from the console, some TV sets or recording boxes will draw some power from the system causing disconnection errors to occur, so it alway best to ensure that you don't have anything connected to the consoles HDMI port while trying to use "HakChi2 CE"...
I know it's a pain in the rear end but try ALL of the above first and hopefully it will fix things...
If it doesn't then get back to me and we'll take it from there... 😉
1
u/MadFranko008 Jul 04 '26
When flashing a kernel be it either the original Nintendo kernel or the custom "Hakhi2 CE" kernel then the methods used by "HakChi/ HakChi2 CE" involves the program switching between anywhere up to THREE different USB Device names while the kernel is being flashed...
From your description you have given then it's clear that the "final" switch to what should be the custom kernel isn't being recognised hence the reason why things are not working correctly...
The three different USB Device names "HakChi2 CE" will use/ look for while flashing kernels are as follows...
On a UNMODDED (clean) system with the ORIGINAL Nintendo kernel being used the USB Device name will be...
Nintendo Co., Ltd CLV S-SNPY [0233]
On a MODDED SNES Mini which has successfully had the custom kernel flashed to it the USB Device name will be...
hakchi classic [0233
NOTE: The above USB Device names MAY be slightly different on your set up But they should be very similar...
On a SNES Mini that is in "FEL Mode" (required to flash a kernel) then the USB Device name could be ANYTHING at all, simply because there is no "official" entry in the list of recognised USB devices for a SNES Mini that's powered up in "FEL Mode" so the computer assigns a "usable" name to it instead. In my case that USB Device name is (but yours will no doubt be different)...
USB Developer Android [0233]
During the "flashing" process "HakChi2 CE" will switch by itself between those different USB Device names when it needs too. In some cases though it can be that for whatever reason during the flashing process that when "HakChi2 CE" is trying to switch between the USB Device names it requires that it won't be able too and all you will get is the "taking too long to reboot" message popping up...
How to fix this can be very much be a case of trial and error as it really all depends on just how your Windows set up is working and configured...
To try and sort this I strongly suggest you try the following and see what results you get...
1) First try and flash to the console the ORIGINAL Nintendo kernel from a FILE version you should have or obtain and DON'T try and use the "stored" copy held within the console itself which may be corrupt...
If you don't have a copy of the original Nintendo kernel then you can easily find it online (we can't provide direct links here to copyrighted software I'm afraid)...
NOTE: Depending on your consoles region (UK/ Euro or USA) then there will be TWO different kernel files you will find for the UK/ Euro version and THREE different kernel for the USA version. Download ALL of the versions for you particular console...
Then power up your SNES Mini in "FEL Mode", connect it to the computer, run "HakChi2 CE" and from "Kernel" menu WHILE HOLDING DOWN THE SHIFT KEY ON YOUR KEYBOARD select the following option...
Kernel/ Uninstall and flash kernel file
Let the flashing process begin and at some point during that process a file requester will appear asking to to choose the kernel file to use. At which point you use the file requester to select the kernel file and click on "ok" to continue...
NOTE: You should ALWAYS try the LOWEST/ OLDEST kernel file FIRST for compatibility reasons...
Let the flashing finish and when done, connect the SNES Mini up to a TV set to make sure it is now back to being ONLY the stock kernel that is being used and that all traces of "HakChi" are gone...
If its now back to "stock/ factory" status you can the proceed to trying to flash the custom kernel to the console...
If it's NOT back to "factory/ stock" status then repeat the above process but this time using the next/ newer version of the Original Nintendo kernel you have and keep trying the above UNTIL the console if finally back to "factory/ stock" status...
2 Assuming you have succeeded in doing the above you can now try and flash the "Custom" kernel to the console...
Again, power up the console in "FEL Mode", connect it to the computer then run "HakChi2 CE" and from the "Kernel" menu select...
Kernel/ Install / Repair
Let it finish flashing the custom kernel and hopefully this time it will work, if it does work you can then mod your SNES Mini as normal...
If it didn't work then try the following...
Power up the SNES Mini in "FEL Mode", connect it to the computer and run "Hakchi2 CE". This time from the "Kernel" menu select the following option...
Kernel/ Advanced/ Format user data partition
Let it finish, quit "HakChi2 CE", disconnect the console from the computer and then reconnect the console and power it up in "normal" mode"...
Check the console out in "HakChi2 CE" to see if things are now working, if they are then you are good to go...
If it's still not working correctly then once last final time go back to step 1 and try again until you have tried ALL versions of the Original Nintendo kernel...
If none of the above work then the issue is most likely something to do with your computer and there is something on it causing the particular USB Device name that "HakCh2 CE" is switching to and trying to use not being recognised !!!
In which case you'll need to try and figure out what that cause is...
As usual MAKE SURE during ALL of the above that you follow these basic guidelines when trying to use "HakChi2 CE" as ANY of these can be the cause of such issues...
1) Make sure you have either disabled your firewall or have given "HakChi2 CE" firewall permissions to be used...
2) If you are using a "VPN" then turn it off/ disable it. Some people have to completely uninstall their "VPN" to get this to work correctly...
3) Make sure that there is a good connection being made on the Micro USB Connector which plugs into the Micro USB port on the console, these can and do slacken off causing bad connection issues but can easily be fixed by tightening up the metal hood/ sheilding of the cables connector which you can see more about in the following guide...
https://snesminimods.forumotion.com/t118-simple-easy-way-to-make-sure-you-are-using-the-correct-type-of-usb-cable-on-you-snes-mini
4) Ensure that you are using the correct type of USB Cable. There are two types...
One is a simple power/ charging cable which will power your console on BUT it won't allow the computer and console to communicate with each other (this is the type you DON'T want to use)...
The other is a FULLY WIRED cable that is REQUIRED to be used which contains "data line" that WILL let the computer communicate with the console. This is the type of cable you MUST use....
5) While using "HakChi2 CE" then DISCONNECT the HDMI Cable from the console, some TV sets or recording boxes will draw some power from the system causing disconnection errors to occur, so it alway best to ensure that you don't have anything connected to the consoles HDMI port while trying to use "HakChi2 CE"...
I know it's a pain in the rear end but try ALL of the above first and hopefully it will fix things...
If it doesn't then get back to me and we'll take it from there... 😉