So my console is acting like it's been banner bricked. It comes up to the first Health&Safety screen and will not proceed, the little 'A' icon near the bottom does not even show up. The controllers will sync, but I cannot do anything.
About a month ago I installed the Homebrew Chan and a few WAD files. The system still worked after that, I used it a few times afterwards. Then last week it just stopped going past that first screen.
Now the months leading up to this happening, I had a few issues where if the console stayed in standby for 2-3 days at a time, it would not turn on unless i unplugged the power and plugged it back in.
So I tried using 2 different trucha-signed disks to autoboot WAD-manager, nothing. Tried the Zelda ISO with the autoboot byte set and still nothing. At that point I was thinking it's not a banner brick and hardware failure. The console was sitting on top of my 360 for a while, maybe that wasn't such a great idea.
I took apart the console and disconnected the chip (Cyclowiz on launch console), same behavior. I completely disconnected the DVD drive and still got exact same behavior. So nothing I could do would get it past that first screen.
Does anyone have any ideas? I've tried everything I could think of. I'm thinking it's not chip/WAD related because of the power issues in the months before it died, maybe something in the system just finally went out.
BTW: It's a NTSC-U console, not sure if I'm running 3.2 or 3.3. I believe it's 3.2, but tested the Zelda ISO in case it was 3.3. Neither booted, and the Zelda ISO should boot even with 3.3 fw if it is in fact a banner brick.
About a month ago I installed the Homebrew Chan and a few WAD files. The system still worked after that, I used it a few times afterwards. Then last week it just stopped going past that first screen.
Now the months leading up to this happening, I had a few issues where if the console stayed in standby for 2-3 days at a time, it would not turn on unless i unplugged the power and plugged it back in.
So I tried using 2 different trucha-signed disks to autoboot WAD-manager, nothing. Tried the Zelda ISO with the autoboot byte set and still nothing. At that point I was thinking it's not a banner brick and hardware failure. The console was sitting on top of my 360 for a while, maybe that wasn't such a great idea.
I took apart the console and disconnected the chip (Cyclowiz on launch console), same behavior. I completely disconnected the DVD drive and still got exact same behavior. So nothing I could do would get it past that first screen.
Does anyone have any ideas? I've tried everything I could think of. I'm thinking it's not chip/WAD related because of the power issues in the months before it died, maybe something in the system just finally went out.
BTW: It's a NTSC-U console, not sure if I'm running 3.2 or 3.3. I believe it's 3.2, but tested the Zelda ISO in case it was 3.3. Neither booted, and the Zelda ISO should boot even with 3.3 fw if it is in fact a banner brick.








