1. dobongo

    OP dobongo Newbie
    Newcomer

    Joined:
    Sep 5, 2019
    Messages:
    5
    Country:
    United Kingdom
    How it happened : update firmware to 8.1.0, (fuse count 10). Was using incognito to stop nintendo access. Decided id prefer being online and couldnt remove incognito without a nand backup. The nand backup was when it was on 7.0.0. without realising this i backed it up.
    Switch can access rcm only. when booting cfw from payload, screen flashes a few times then blacks out. Switch will not boot into rcm for 45-60mins.

    I have so far followed all threads related, coming closest using choidujour on pc. I am attempting to upgrade back to 8.1.0 with this method.
    The problem i have is the lockpick_rcm is only recovering keys on my 7.0.0 switch (nand backup), since i backed up to this point.
    I am assuming this is why i am getting "missing keys" error on choidujour. I made sure to replace the keys taken off a template with my keys from prod.keys file.
    So this is the furthest i have managed to get, following many threads on here and switch.homebrew.guide website.
    I have come to accept that this switch life is over, and have bought another unpatched switch (8.1.0).
    Now i am wondering, with this new switch, would i able to use the keys off this console anduse them for choidujour to try and fix the other console?
     
  2. pLaYeR^^

    pLaYeR^^ Doctor Switch
    Member

    Joined:
    Sep 18, 2014
    Messages:
    2,939
    Country:
    Austria
    If it would be only a problem of the fuse count, you could simply boot to CFW with custom bootlaoder (Hekate).
     
  3. dobongo

    OP dobongo Newbie
    Newcomer

    Joined:
    Sep 5, 2019
    Messages:
    5
    Country:
    United Kingdom
    Im sure i do this everytime using tegrarcm every time i turn off (using jig and pc). Whichever custom bootloader i use, it always has the same result.
    So from injecting payload, then launch cfw. Same couple screen flashes showing hekate, then blacked for a long time.
    When i do get home il post clear details with images of whats going on for a better understanding
     
  4. pLaYeR^^

    pLaYeR^^ Doctor Switch
    Member

    Joined:
    Sep 18, 2014
    Messages:
    2,939
    Country:
    Austria
    Maybe try to clean the sd card and use a fresh atmosphere release.
    You could have saved yourself a lot of time if you would simply have created a backup of prodinfo which normally incognito creates automatically.
     
  5. linuxares

    linuxares I'm not a generous god!
    Moderator

    Joined:
    Aug 5, 2007
    Messages:
    7,283
    Country:
    Sweden
    Do you still have your keys? Biskeys especially.
     
  6. dobongo

    OP dobongo Newbie
    Newcomer

    Joined:
    Sep 5, 2019
    Messages:
    5
    Country:
    United Kingdom
    Youre right, i might as well begin all steps as
    yes sir, 'biskeydump_usb.bin
     
  7. dobongo

    OP dobongo Newbie
    Newcomer

    Joined:
    Sep 5, 2019
    Messages:
    5
    Country:
    United Kingdom
    so this is the part i am stuck on currently regarding upgrading firmware via PC. (ChoiDujour)
    i followed the edited keys.txt document and replaced the keys with my own, however there are keys missing which i do not have according to the template, which are :
    key_area_key_system_source
    key_area_key_ocean_source
    key_area_key_application_source
    header_key

    choi.png
    now as for redownloading latest firmwares and everything. i did so using sdsetupcom. made sure everything was all up to date.
    this time however, hekate now doesnt black out the switch when trying to launch in rcm. it now returns back to rcm. so it shows the logo a few times and returns to rcm options ( like after youve injected payload.) so i guess this is some progress.
     
Draft saved Draft deleted
Loading...

Hide similar threads Similar threads with keywords - downgrade, Possible, bricked