Splash screen shows but black screen after that

Question

Splash screen shows but black screen after that

Closed this issue 6 years ago · 16 comments

So, I saw that #109 was fixed in the latest hotfix, I loaded up the new version but this time, I get a black screen after the splash. Not sure if I can provide any logs, TegraRCM just says:

Uploading payload (mezzo size: 92, user size: 76598, total size: 142814, total padded size: 143360)... Smashing the stack! Smashed the stack with a 0x7000 byte SETUP request! Payload successfully injected

I'm on 6.2.0 FW, all that was changed was the ReiNX version from 2.0 to 2.1.1

One thing I did notice was that it hung on the splash screen longer than normal, not sure if that helps.

RetroGamer74 commented 6 years ago

Where?

Answer 1 · 2019-04-01T01:33:58.000Z

try the latest release as of basically right now.. you might have a jank dl

Answer 2 · 2019-04-01T02:52:25.000Z

I had issues with the 2.1 release (#109). I updated to the 2.1.1 release. I have the splash screen but after it, it boots Horizon OS instead of the CFW. I am still on 6.2. Should I update to 7.0.1? Thanks for your great work either way!

Answer 3 · 2019-04-01T21:46:25.000Z

Hotfix 2.1.1 is wrong. It reboots after SEPT. In my case back to RCM ( because of AutoRCM ). Fix required.

Answer 4 · 2019-04-01T21:47:50.000Z

@EliseZeroTwo

Answer 5 · 2019-04-01T21:50:19.000Z

@flxdhc if you're booting into HOS, thats cfw. Theres no mechanic for booting into unmodified firmware.

Answer 6 · 2019-04-01T21:51:40.000Z

@RetroGamer74 You're required to have ReiNX.bin on the SD card

Answer 7 · 2019-04-01T21:51:47.000Z

I think he means, because after SEPT, ReiNX reboots, then OFW starts its loading.

Answer 8 · 2019-04-01T21:55:18.000Z

If you've copied everything in the zip to the SD (preferably after deleting existing reinx files), everything should work. A lot of people either dont drop everything from the release on to SD, or some people dont clean out old files and have weird issues because old and new are running together.

Answer 9 · 2019-04-01T21:56:01.000Z

Ok. I'm gonna try again.

Answer 10 · 2019-04-01T21:59:02.000Z

It works!!! The issue was ReiNX.bin. Why now is mandatory on the root of SD?

Answer 11 · 2019-04-01T22:03:18.000Z

Because sept is very fussy and juggling around the payload was causing issues, so the solution was to just
reinx -> sept -> custom payload -> reinx.bin off sd

Answer 12 · 2019-04-01T22:07:16.000Z

I keep updated a boot manager which is RetroReloaded. I don't want to do spam, but now in my case it does:
Custom Payload (RR) -> /RR/payload/ReiNX.bin -> Sept ->custom payload -> /ReiNX.bin

So I've got two times your ReiNX.bin. Further than this, everything works ok!!.

Answer 13 · 2019-04-01T22:44:38.000Z

So if I'm on a FW under 7.0, no sept folder required? I moved the .bin to the SD root this time to test, but am still getting a black screen. I wiped out the old ReiNX folder also, replaced with new version, no luck.

Edit: Sept folder seems required, it booted fine when it was put on the SD card. Except now the Album launcher doesn't open homebrew menu, just screenshots. I reverted to ReiNX 2.0 for now as everything works perfect on that version.

Answer 14 · 2019-04-01T23:25:21.000Z

you probably forgot to include the hbl.nsp.. its on our guide. I've never repacked it with the cfw. Also i'm using 2.1.1 fine on 6.2 without sept.

Answer 15 · 2019-04-02T02:06:09.000Z

@flxdhc if you're booting into HOS, thats cfw. Theres no mechanic for booting into unmodified firmware.

@Reisyukaku thanks, all good for me, I had not noticed that hbl.nsp was needed...