Hacking Hardware Misc Yo chat! I'm I cooked?

  • Thread starter Thread starter xixion
  • Start date Start date
  • Views Views 1,391
  • Replies Replies 26
If your unit looks like the picture below, then you have yourself a dev unit.
Anything else is just a botched attempt to put the dev unit firmware on a production unit.
View attachment 577667

If that is the case, then you need to rebuild the nand and re-sign it with the shit that Sthetix releases.
The console keys are linked to your console so you can dump them with lockpick_rcm.
NO! it's not a devkit, Them are @Maq47's words not mine.

If you have these folders on your sd card delete them.
/atmosphere/contents/0100000000000033
/atmosphere/contents/0100000000000014

Maybe you installed some patch, mod, sysmodule or similar that added that folder, which broke the es and audio process
I don't have them folders.


Those are done by sys-patch for sigpatches. Don't tell them to remove stuff willy-nilly without actually researching it first. A quick Google search for both '0100000000000033' and '0100000000000014' brings up a result for sys-patch each, both from GBAtemp. At this point you're spreading misinformation.

Edit: Okay, '0100000000000014' is for sys-tune, made by the creators of sys-patch, so it's still a legit folder. If I am right, and this is indeed an EDEV unit, then sys-patch is expected to break booting atmosphere, and stock booting still won't work, so this isn't really progress.
Humm , maybe I'm suppose to have them?
 
Update:
Booting stock sticks at the white switch logo.
Booting stock through hekate gives
1781913104055.png

Booting sysnand through fusee or hekate
1781913596214.png


Try to install sys-patch.
Tried that and still got the same issues.
 
Update:
Booting stock sticks at the white switch logo.
Booting stock through hekate gives
View attachment 578739
Booting sysnand through fusee or hekate
View attachment 578741


Tried that and still got the same issues.
Check if your /bootloader/hekate_ipl.ini file contains an entry somewhat like this:
Code:
[Stock sysMMC]
pkg3=atmosphere/package3
emummc_force_disable=1
stock=1
 
Check if your /bootloader/hekate_ipl.ini file contains an entry somewhat like this:
Code:[config]
autoboot=0
autoboot_list=0
bootwait=0
verification=1
backlight=100
autohosoff=2
autonogc=1
updater2p=1

[100% STOCK OFW]
ofw=1
icon=bootloader/res/ofw.bmp

[SEMI-STOCK (SYSMMC)]
pkg3=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/stock.bmp



[CFW (SYSMMC)]
pkg3=atmosphere/package3
emummc_force_disable=1
icon=bootloader/res/sysnand.bmp



[CFW (EMUMMC)]
pkg3=atmosphere/package3
emummcforce=1
icon=bootloader/res/emummc.bmp
 
  • Like
Reactions: xixion
SOLVED
boot into hekate
Lockpick_RCM_Pro.bin payload ---->Dump prod.keys
Prodforge.bin payload ----> Dump prodinforge.dec

Mount SD to PC using hekate
Move prod.keys and proinforge.dec to PC

Launch NxNandManager File>Open File > prodinforge.dec

Options> Configure keyset > prod.keys >
1781960616259.png
save as file > PRODINFO.bin

Launch NAND-FixPro
Settings> Offline Mode > Stick the things in the holes>

Move BOOT0 BOOT1 and RAWNAND.bin to SD:\backup > [unique ID] > restore

Eject SD

Using hekate
Restore eMMC BOOT0 & BOOT1
Restore eMMC RAW GPP
power off

Not sure if this is what did the trick... but see what da happen was
I didn't realize my jig wasn't in and an my big hands put me into factory reset.
So I did. YMMV
 

Site & Scene News

Popular threads in this forum