Closed GoogleCodeExporter closed 8 years ago
Just a further comment to mention that this is not a normal "no signal" black
screen, the video output is doing something but I am only getting a black
screen on the TV rather than "no signal" which normally happens when SNEEK is
not setup correctly.
Original comment by retroh...@gmail.com
on 29 Jul 2010 at 2:40
I found patching the system menu (4.2 0000008b.app 4.3 0000009b.app) with
IOSKPatch fixed this issue.
Original comment by retroh...@gmail.com
on 29 Jul 2010 at 8:25
[deleted comment]
Have the same issue, and tried it with patching 4.2 0000008b.app -u -d but its
dont helped.
Doese someone now another solution?
Original comment by habekein...@googlemail.com
on 1 Aug 2010 at 5:45
Patch it with -p only, that worked for me.
Original comment by retroh...@gmail.com
on 2 Aug 2010 at 1:25
Still no System Menu, same like before :/
Original comment by habekein...@googlemail.com
on 2 Aug 2010 at 2:44
This is the same as issue 61, issue 54 and issue 34.
Just slow usb drives the do not get initialized properly.
See issue 34 for a solution.
Original comment by digd...@zonnet.nl
on 2 Aug 2010 at 3:48
I dont think so, i tried this solutions also but no one works >.<
And everytime when the shared 2 folder is deletet it will boot by the first try
>.<
But when theres a Shared folder its never boot all the try´s.
In Uneek r 104 was all ok with it, but since i updatet to uneek di r114 it dont
want to work .
Original comment by habekein...@googlemail.com
on 2 Aug 2010 at 4:22
Still have the same issue with r115.
Everytime i boot with Shared 2 folder he wont boot.
Everytime i boot without shared2 folder he boot correctly >.<
Original comment by habekein...@googlemail.com
on 2 Aug 2010 at 6:21
Can you give a directory listing of shared2? Maybe there is something odd there.
Original comment by digd...@zonnet.nl
on 3 Aug 2010 at 6:47
I don't think it is the same issue as the others. Adding the delays did not fix
my problem nor did waiting for the warning screen then rebooting. Patching the
system menu was the only way I could sort this out.
You could try my installer which creates a virgin NAND for you. Clean your SD
and USB of all SNEEK and NAND files then run the installer, choose option 3 and
follow the prompts. Takes about 5 mins:
http://www.mediafire.com/download.php?d7cp634qcl3rktb
Original comment by retroh...@gmail.com
on 4 Aug 2010 at 1:38
Original comment by urt...@gmail.com
on 4 Aug 2010 at 10:50
I had exactly the same behaviour as habekeininternet.
What I found is that works with an usb flash drive but not with my hdd.
I remember an old version of UNEEK rev 93 worked on that hdd so i tried to find
the changes that let this problem happen.
As expected, it should be a delay problem. UNEEK up to 94 works well, than
95-97 doesn't work because a mess in the fs-usb module. 98 is the first
revision with that problem, and 99 (surprise surprise) solved the problem
adding a delay in diskio.c.
The strange thing is that revision up tu 94 does not have this delay and works.
Then, in r100 all the fs-usb module was reverted to revision 93, including the
diskio.c file. And from then UNEEK doesn't work with my hdd. Simply readding
that delay makes everything work!
However, the problem seems related to the system menu, that write this output:
<< RVL_SDK - NCD release build: Dec 12 2008 03:06:03 (0x4199_60831) >>
try again!! in "iplNCDSetting.cpp" on line 1078.
Address: Back Chain LR Save
0x816a8f08: 0x816a8f98 0x8152e8e8
0x816a8f98: 0x816a8fd8 0x813fb974
0x816a8fd8: 0x816a9548 0x8133496c
0x816a9548: 0x816a9558 0x81360824
0x816a9558: 0x816a9568 0x81379790
0x816a9568: 0x816a9698 0x8137af20
0x816a9698: 0xffffffff 0x813300a4
And hang.
When working, the output is
<< RVL_SDK - NCD release build: Dec 12 2008 03:06:03 (0x4199_60831) >>
MAC: XX-XX-XX-XX-XX-XX
That makes me think could be a problem with the wireless device
Original comment by thegoo...@gmail.com
on 27 Aug 2010 at 1:50
I found a Wii (owned by a friend) with this exact same issue (only booting with
a clean shared2), and I was surprised to find that retrohead's suggestion of
patching the System Menu with IOSKPatch -p worked!
So, if anyone else has this issue: try it, it works (assuming there are no
harddrive problems involved, of course).
Original comment by ja...@vietors.com
on 29 Oct 2010 at 1:28
Original issue reported on code.google.com by
retroh...@gmail.com
on 28 Jul 2010 at 11:35