Picofly oled boots hekate nothing else

[Bradle6]

So got a modded switch oled. Boots hekate fine but nothing else ofw it will get to Nintendo switch logo and no further.

it will copy and make a emunand but once again black screen and nothing.

cfw sysnand won't boot either

What are the chances of getting this to work without being banned online or will I need to use a unbrick guide that makes this emunand only?

no backup of any kind so nothing to restore.

 

[Hayato213]

Sound like problem is your sysnand/OFW since emunand is just 1:1 copy of sysnand.

 

[Bradle6]

Tried dumping keys from sysnand with the lockpick version 1.9.8 from my SD card not sure if old or not.

It does say FatFs Error no fat unable to mount system partition if that helps my issue or is that normal

 

[Hayato213]

Format the SD card to FAT32 again, and then try to load Atmosphere again.

 

[MoeXzl]

You will need to expand your resistors to an additional 47 ohms.

The modder probably messed up and wanted to make a quick profit. I always check something like this without an SD card and need to adjust it if necessary.

 

[Bradle6]

You will need to expand your resistors to an additional 47 ohms.

The modder probably messed up and wanted to make a quick profit. I always check something like this without an SD card and need to adjust it if necessary.

Would that stop it booting ofw?

 

[MoeXzl]

If you only see the logo and then the screen remains black, this is usually an indication that the resistors need to be adjusted.
Please take a look at Hekate to see what your Nand partition table looks like. Nothing should be missing there!

 

[Bradle6]

If you only see the logo and then the screen remains black, this is usually an indication that the resistors need to be adjusted.
Please take a look at Hekate to see what your Nand partition table looks like. Nothing should be missing there!

Think it's all fine

 

[jkyoho]

disconnect dat0 from modchip and see if OFW works.
You might already have dirty sysnand if you dont know the history of the mod

 

[Bradle6]

I can't browse the system folder in tegra explorer either says no fat error again like lock pick

 

[MoeXzl]

Then it is due to the resistances for CMD and DAT0 being too low.

 

[Bradle6]

disconnect dat0 from modchip and see if OFW works.
You might already have dirty sysnand if you dont know the history of the mod

Have not tried this yet but if it doesn't boot does it mean it's bricked

Post automatically merged: Feb 20, 2024

Then it is due to the resistances for CMD and DAT0 being too low.

Both need more resistors ?

 

[jkyoho]

Have not tried this yet but if it doesn't boot does it mean it's bricked

since you could see Nin logo, if dat0 disconnect still not boot to OFW, likely softbrick

 

[Bradle6]

since you could see Nin logo, if dat0 disconnect still not boot to OFW, likely softbrick

How would I fix that not being able to boot anything?

Post automatically merged: Feb 20, 2024

disconnect dat0 from modchip and see if OFW works.
You might already have dirty sysnand if you dont know the history of the mod

Won't boot with dat 0 not connected also won't go maintenance mode as far as I can tell

Post automatically merged: Feb 20, 2024

can't system wipe in tegra as doesn't mount says fatfs error no fat can't mount system same as lockpick etc so this must be something to do with


emmc benchmarks fine aswell so must be corrupt system maybe?

 

[rull_bull]

Most common problem, add resistors and ofw will work. It’s mentioned in almost every thread with ofw problems

 

[Bradle6]

D

Most common problem, add resistors and ofw will work. It’s mentioned in almost every thread with ofw problems

Doesnt work with dat 0 connected on the modchip so why would adding resistors make it work?

 

[jkyoho]

dump keys and make full backup then try to rebuild boot0/1, if system partition still good. Otherwise wipe system from Tegraexplorer

Post automatically merged: Feb 20, 2024

Won't boot with dat 0 not connected also won't go maintenance mode as far as I can tell

would you still see 1st logo when dat0 disconnect?
This kind of black screen after 1st logo would be caused by most common dat0 resistor interference by modchip so you need to add resistance to 100 ohm or up,
and also could be 17.0 Firmware issue from Atmosphere(fixed already)

 

[rull_bull]

D

Doesnt work with dat 0 connected on the modchip so why would adding resistors make it work?

Several people have said the same thing to you, if you cant boot to ofw, add resistors.

You have electrical interference thats stoppning sysnand from booting.
Try with 100ohm on dat0 and cmd.

 

[jkyoho]

check your hos version from Hekate, if not on 17.0.0+, You can ignore the 2nd scenario

 

[Bradle6]

check your hos version from Hekate, if not on 17.0.0+, You can ignore the 2nd scenario

I updated lockpick and boom system wipe worked I have now booted into cfw sysnand