Hacking [POC] - Fixing OFW Blackscreens with Boot9strap

[liomajor]

All of them, if it errors, there might be something broken.

 

[leerz]

All of them, if it errors, there might be something broken.

Thanks, I will try, Could you be more specific?
it will error Upon what?

How to check exactly?
(I know you want me to use decrypt9)
but what do I need to do exactly?

 

[liomajor]

decrypt9 > sysNAND Options > System File Dump... > all of them

If decrypt9 fails to dump, there is something faulty!

 

[leerz]

decrypt9 > sysNAND Options > System File Dump... > all of them

If decrypt9 fails to dump, there is something faulty!

Interesting, The ticket.db dump failed!

NCCH FIRMS Dump Failed

 

[mitroux]

if all fails , then do a ctrnand transer to 9.2 and check again with the 0 key sed file ( try patching the new 11.4 nand you just updated a little while ago)

 

[liomajor]

Interesting, The ticket.db dump failed!

NCCH FIRMS Dump Failed

Do the following, use your first dump file (BS9 not yet installed).

Install BS9 with the correct .firm for your version.

Use decrypt9 to ctrtransfer 9.2, reboot and try again.

(your current install might be fragmented and beyond repair)

 

[mitroux]

Do the following, use your first dump file (BS9 not yet installed).

Install BS9 with the correct .firm for your version.

Use decrypt9 to ctrtransfer 9.2, reboot and try again.

(your current install might be fragmented and beyond repair)

i am sorry , but didn't he try that before?
like that :
Test 0 - Raw setup - Blackscreen but still with sounds
Test 1 - CTRNAND Donor Ctrnand 11.3 - Blackscreen but still with sounds
Test 2 - CTRNAND NEW 9.2(same region) - Blackscreen but still with sounds
Test 3 - CTRNAND NEW 9.2 (different region) - Blackscreen but still with sounds
Test 4 - CTRNAND old/new 2.1 (same Region) - Just an error on Luma

 

[leerz]

if all fails , then do a ctrnand transer to 9.2 and check again with the 0 key sed file ( try patching the new 11.4 nand you just updated a little while ago)

Already did the ctr trans to 9.2 then 0 movable and cleared data

Do the following, use your first dump file (BS9 not yet installed).

Install BS9 with the correct .firm for your version.

Use decrypt9 to ctrtransfer 9.2, reboot and try again.

(your current install might be fragmented and beyond repair)

I'll retry all that.


Right now this is what I'm doing

while browsing the ctrnand I saw a ticket.bak
I deleted the db file and renamed to ticket.db

I can now dump the ticket.db

Will retry more stuff later.

 

[liomajor]

i am sorry , but didn't he try that before?

My guess was that he did use godmode9 for ctrtransfer or might somehow broken it after ctrtransfer one after another.

 

[MelonGx]

BLACK SCREEN WITH SOUND - ISN'T it the camera broken, a hardware error?

 

[leerz]

BLACK SCREEN WITH SOUND - ISN'T it the camera broken, a hardware error?

From what I've read, what they meant about "black screen" was from the Field of View of the Camera inside the App, instead of the picture, it only shows: "black screen"

see: http://www.nintendolife.com/forums/3ds/3ds_outer_camera_problem
http://www.ign.com/boards/threads/3ds-outer-cameras-not-working.201056139/
https://gbatemp.net/threads/3ds-camera-black-screen.288661/

not exactly ruling out a hardware problem, just basing from what I've read

 

[OrGoN3]

Already did the ctr trans to 9.2 then 0 movable and cleared data

I'll retry all that.


Right now this is what I'm doing

while browsing the ctrnand I saw a ticket.bak
I deleted the db file and renamed to ticket.db

I can now dump the ticket.db

Will retry more stuff later.

Why do the 0-key movable.sed?

 

[MelonGx]

From what I've read, what they meant about "black screen" was from the Field of View of the Camera inside the App, instead of the picture, it only shows: "black screen"

see: http://www.nintendolife.com/forums/3ds/3ds_outer_camera_problem
http://www.ign.com/boards/threads/3ds-outer-cameras-not-working.201056139/
https://gbatemp.net/threads/3ds-camera-black-screen.288661/

not exactly ruling out a hardware problem, just basing from what I've read

It's a different thing than what you listed.
If the camera's FFC is damaged, the system will be in black screen, the keys will have no response, but the sound works.
In this case, I fixed it by removing camera's FFC (and finally completely fixed it by replacing a good camera module).

 

[OrGoN3]

It's a different thing than what you listed.
If the camera's FFC is damaged, the system will be in black screen, the keys will have no response, but the sound works.
In this case, I fixed it by removing camera's FFC (and finally completely fixed it by replacing a good camera module).

And different still from http://kotaku.com/5786225/is-the-3ds-suffering-from-a-black-screen-of-death

 

[MelonGx]

And different still from http://kotaku.com/5786225/is-the-3ds-suffering-from-a-black-screen-of-death

Yes it's also a different thing.
Since black screen from damaged Camera FFC is pure black, but this has an error message.

 

[OrGoN3]

Yes it's also a different thing.
Since Camera-FFC-caused-black-screen is pure black, but this has an error message.

Top screen is still pure black

 

[MelonGx]

Top screen is still pure black

Camera-FFC-Damaged case is dual screen pure black.

 

[OrGoN3]

Camera-FFC-Damaged case is dual screen pure black.

With sound? Does the home menu still load just can't see it? (does moving around and selecting something play a different sound?)

 

[MelonGx]

With sound? Does the home menu still load just can't see it? (does moving around and selecting something play a different sound?)

Yes. In Camera-FFC-Damaged case, the Home Menu still gets loaded.
Only the display, the key input and the touch screen input get no response.

 

[leerz]

So just an Update

Strange as it seems, the 3DS is now OK

My theory is it is as fckd up as i hoped it would be.

1. The FFC slot was ok, the FFC Cable had corrosion
I've confirmed it by my visual inspection, I thought it is almost likely since the Home button had corrosion as well.
I unplugged it and now the HM shows up.


2. Not exactly sure if my initial fiddling helped at all, the 3DS is now in US region coming from Jap.

3. the title.db is now dumping as it should.


anyway, I would like to thanks everyone for their Inputs!
I hope my venture can help out other users in the future.