Homebrew NAND Emulated sneek/usneek

  • Thread starter Thread starter johw
  • Start date Start date
  • Views Views 13,186
  • Replies Replies 84
  • Likes Likes 1
it's possible that's the reason. the wii isn't designed to take advantage of the speeds of an ssd, so it's not worth using one with it.
 
  • Like
Reactions: johw
it's possible that's the reason. the wii isn't designed to take advantage of the speeds of an ssd, so it's not worth using one with it.

See my wii is missing any cIOs or IOS?
I tested it with HD and it still doesn't work
Pen drive works perfect.


SysCheck HDE v2.4.0 HacksDen Edition by JoostinOnline, Double_A, R2-D2199, and Nano
...runs on IOS58 (rev 6176).
Region: NTSC-U (original region: PAL)
System Menu 4.3U (v513)
Priiloader installed
Drive date: 02.13.2007
Homebrew Channel 1.1.2 running on IOS58
Hollywood v0x11
Console ID: 63040567
Console Type: Wii
Shop Channel Country: Brazil (16)
Boot2 v4
Found 87 titles.
Found 57 IOS on this console. 5 of them are stubs.
IOS4 (rev 65280): Stub
IOS9 (rev 1034): No Patches
IOS10 (rev 768): Stub
IOS11[60] (rev 65535, Info: rev 6174): Trucha Bug
IOS12 (rev 526): No Patches
IOS13 (rev 1032): No Patches
IOS14 (rev 1032): No Patches
IOS15 (rev 1032): No Patches
IOS16 (rev 512): Stub
IOS17 (rev 1032): No Patches
IOS20[60] (rev 65535, Info: rev 6174): Trucha Bug
IOS21 (rev 1039): No Patches
IOS22 (rev 1294): No Patches
IOS28 (rev 1807): No Patches
IOS30[60] (rev 65535, Info: rev 6174): Trucha Bug
IOS31 (rev 3608): No Patches
IOS33 (rev 3608): No Patches
IOS34 (rev 3608): No Patches
IOS35 (rev 3608): No Patches
IOS36 (rev 3608, Info: rev 3351): Trucha Bug, ES Identify, NAND Access
IOS37 (rev 5663): No Patches
IOS38 (rev 4124): No Patches
IOS40[60] (rev 65535, Info: rev 6174): Trucha Bug
IOS41 (rev 3607): No Patches
IOS43 (rev 3607): No Patches
IOS45 (rev 3607): No Patches
IOS46 (rev 3607): No Patches
IOS48 (rev 4124): No Patches
IOS50[60] (rev 65535, Info: rev 6174): Trucha Bug
IOS51 (rev 4864): Stub
IOS52 (rev 5888): Stub
IOS53 (rev 5663): No Patches
IOS55 (rev 5663): No Patches
IOS56 (rev 5662): No Patches
IOS57 (rev 5919): No Patches
IOS58 (rev 6176): USB 2.0
IOS60 (rev 65535, Info: rev 6174): Trucha Bug
IOS61 (rev 5662): No Patches
IOS62 (rev 6430): No Patches
IOS70[60] (rev 65535, Info: rev 6174): Trucha Bug
IOS80[60] (rev 65535, Info: rev 6174): Trucha Bug
IOS202[60] (rev 65535, Info: hermes-v5.1): Trucha Bug, NAND Access, USB 2.0
IOS222[38] (rev 65535, Info: hermes-v5.1): Trucha Bug, ES Identify, NAND Access, USB 2.0
IOS223[37] (rev 65535, Info: hermes-v5.1): Trucha Bug, NAND Access, USB 2.0
IOS224[57] (rev 65535, Info: hermes-v5.1): Trucha Bug, NAND Access, USB 2.0
IOS225[37] (rev 65535, Info: hermes-v5.1): Trucha Bug, NAND Access
IOS236[36] (rev 65535, Info: rev 3351): Trucha Bug, ES Identify, NAND Access
IOS245[37] (rev 21008, Info: d2x-v8final): Trucha Bug, NAND Access, USB 2.0
IOS246[38] (rev 21008, Info: d2x-v8final): Trucha Bug, ES Identify, NAND Access
IOS247[53] (rev 21008, Info: d2x-v8final): Trucha Bug, NAND Access, USB 2.0
IOS248[55] (rev 21008, Info: d2x-v8final): Trucha Bug, NAND Access, USB 2.0
IOS249[56] (rev 21008, Info: d2x-v8final): Trucha Bug, NAND Access, USB 2.0
IOS250[57] (rev 21008, Info: d2x-v8final): Trucha Bug, NAND Access, USB 2.0
IOS251[58] (rev 21008, Info: d2x-v8final): Trucha Bug, NAND Access, USB 2.0
IOS252[56] (rev 21010, Info: d2x-v10beta53-alt): Trucha Bug, NAND Access, USB 2.0
IOS254 (rev 65281): BootMii
IOS255[38] (rev 65535, Info: d2x-v6): Trucha Bug, ES Identify, NAND Access, Beer Ticket
BC v6
MIOS v65535
Report generated on 02/16/2021.
 
Last edited by johw,
you have some mixed d2x in there. I don't know if that could cause the problem. this might be a question for @Cyan . I don't understand why it's working for a flash drive though.
 
Sorry if this was asked already, but does the same USB work with usbloaders (not in neek)?

It could just be an incompatible drive. If u have done everything the same on a different drive that works, and u still want to try to troubleshoot this, I would try different versions of neek2o. If that still doesn't work, I would disable Modmii's neek2o option and build the original neek, and if that doesn't work I'd try older versions of that too.

The only other thing I can think of is if the drive isn't getting enough power or it's very slow to initialize. But if u can load the HDD from GX and launch uneek from within the app then it should already be initialized. So if u try that we can rule that out too.

you have some mixed d2x in there. I don't know if that could cause the problem. this might be a question for @Cyan . I don't understand why it's working for a flash drive though.
Nah his syscheck looks fine (perhaps a bit cluttered, but fine). That wouldn't be causing this issue.
 
  • Like
Reactions: johw
Sorry if this was asked already, but does the same USB work with usbloaders (not in neek)?

It could just be an incompatible drive. If u have done everything the same on a different drive that works, and u still want to try to troubleshoot this, I would try different versions of neek2o. If that still doesn't work, I would disable Modmii's neek2o option and build the original neek, and if that doesn't work I'd try older versions of that too.

The only other thing I can think of is if the drive isn't getting enough power or it's very slow to initialize. But if u can load the HDD from GX and launch uneek from within the app then it should already be initialized. So if u try that we can rule that out too.


Nah his syscheck looks fine (perhaps a bit cluttered, but fine). That wouldn't be causing this issue.

Yes my USB HD works well with usbloaderGX and Wiiflow
the problem will be the case of hd?
over the weekend I'll buy another one and test
 
hmm...is the hdd activity light flashing at all? that's one way to know it's actually doing something.
 
  • Like
Reactions: johw
wait a minute, maybe I do have it. check this out from one of my hdds:

View attachment 244381

--------------------- MERGED ---------------------------

I think kernel.bin, di.bin, and font.bin might be what you want. that's how it is with the vwii except it's the vwiikernel.bin. I don't know if font and di.bin are the same on both systems though.

--------------------- MERGED ---------------------------

I also have this: View attachment 244382
Holy fuck, MY EYES! You burned my eyes out with that, lol. Dark mode everything for the win.
 
I have the dark theme on my wii, and a dark blue theme for the virtual wii.

--------------------- MERGED ---------------------------

good question.
Blinking delay is between 1 minute to blink

dunno. mine flashes quickly. it could be the hdd enclosure, but why would other things work in usb loader gx. are you loading neek directly in the features section or just trying to load a game via neek?
 
  • Like
Reactions: johw
I have the dark theme on my wii, and a dark blue theme for the virtual wii.

--------------------- MERGED ---------------------------



dunno. mine flashes quickly. it could be the hdd enclosure, but why would other things work in usb loader gx. are you loading neek directly in the features section or just trying to load a game via neek?
I'm trying to access directly through the channel neek2o NK2O_1 .wad
 
@godreborn, very smart question to ask!

It got me thinking, the other thing he could try is a bare minimum nand!

@johw, presumably you have the exact same files on both your HDD and Flash drive right now yes? If so, I would open up the problematic one using showmiiwads and proceed to delete all games and unnecessary content like photo channel and things like that. If you're not sure what something is, don't uninstall it. Then you should have the bare minimum on your emunand, and you still have a backup on your other drive.

And if you go shopping for a Wii HDD this link may come in handy
https://wiki.gbatemp.net/wiki/USB_Devices_Compatibility_List

It may contain a bit dated info, but when purchasing a Wii HDD, newer isn't better, think no bells and whistles, very simple HDD. Seagate and WD are generally pretty good.
 
  • Like
Reactions: johw
I don't remember much about booting neek outside of usb loader gx on the virtual wii. I used it on the wii, and that was before I had used usb loader gx. I was using cfg usb loader, but I don't think I loaded it through there. I'm thinking it was via sneek channel, because I have a nand backup of 3.2 and 4.1. I think uneek was using 3.2, but I don't remember exactly:

upload_2021-2-16_14-36-32.png
 
  • Like
Reactions: johw
I'm trying to access directly through the channel neek2o NK2O_1 .wad
A lot of these apps need to rename folders to work, and if you're having issues you should troubleshoot try by manually renaming your bootmiineek or bootmiiuneek or whatever folder to SD:\bootmii and launching bootmii. Or use usbloader gx which doesn't require the SD:\bootmii folder to launch neek, just the SNEEK folder on either SD or USB
 
  • Like
Reactions: johw and godreborn
@godreborn, very smart question to ask!

It got me thinking, the other thing he could try is a bare minimum nand!

@johw, presumably you have the exact same files on both your HDD and Flash drive right now yes? If so, I would open up the problematic one using showmiiwads and proceed to delete all games and unnecessary content like photo channel and things like that. If you're not sure what something is, don't uninstall it. Then you should have the bare minimum on your emunand, and you still have a backup on your other drive.

And if you go shopping for a Wii HDD this link may come in handy
https://wiki.gbatemp.net/wiki/USB_Devices_Compatibility_List

It may contain a bit dated info, but when purchasing a Wii HDD, newer isn't better, think no bells and whistles, very simple HDD. Seagate and WD are generally pretty good.
Thank you for the tip
next week I'll be back with more testing
 
I'm not sure what else to try. it's just been too long since I used neek on the wii. I had to look up how to get into priiloader after having forgotten a few weeks ago. I know neek pretty well on the virtual wii, but the wii is a blur.
 
I'm not sure what else to try. it's just been too long since I used neek on the wii. I had to look up how to get into priiloader after having forgotten a few weeks ago. I know neek pretty well on the virtual wii, but the wii is a blur.
you mind refreshing my memory? I'm fairly certain I'm doing everything correctly but I can't boot into priiloader on my emunand anymore, and I'm certain I used to be able to. I know it's installed and working to a certain degree, because I can see it in the emunand and that it moved the original SM .app file and took it's place i.e. My SM is moved to 1000007c.app, and priiloader.app is saved to 0000007c.app; and so it must be working because priiloader is forwarding properly to my SM at 1000007c.app cuz I see the system menu. But holding reset or launching the magicword.dol isn't successful in accessing the neek Priiloader menu

TLDR: how do you consistently have success accessing Priiloader on EmuNAND?

stay tuned I'm editing this message right now...

edit:
some more info. ModMii has the option to install a special neek version of Priiloader v0.7 to EmuNANDs, and back in the day I was able to get this to work but not the official Priiloader. I have documented that the Priiloader menu is accessible by holding reset when booting neek, so I must have had this working on my Wii HDD, but it's not working now.

Btw, I tested the current Priiloader v0.9 installed app file on an emunand with the same results as the v0.7 neek mod. I'd like to see if I can get Priiloader v0.7neek mod working again, and then try v0.9 under otherwise identical circumstances to see if it works too. If I can get this working I'd very easily be able to update ModMii to use priiloader v0.9 on EmuNANDS (already updated to v0.9 on real nand in the latest ModMii beta)
 
Last edited by XFlak,

Site & Scene News

Popular threads in this forum