Search results

  1. R

    Hardware eMMC Issue when connected to board

    I just want to take the time to mention and thank @lily2012 After asking a ton of question which were always answered quickly and with the guidance given I was able to get my switch to boot and update the firmware so that it would boot with and without RCM. Although lily2012 is a new member...
  2. R

    Hardware eMMC Issue when connected to board

    Ill send you a PM with what the output is.
  3. R

    Hardware eMMC Issue when connected to board

    The one i used for the Linkle prod.keys starts with keyblob_key_00 = 4f5a86e.... The output from linkle shows keyblob_key_00 = CE96C5... After doing all the steps and dumping my prod.key file i get keyblob_key_00 = CE96C5... Im pretty sure my issue lies within either linkle or ChoiDujour or...
  4. R

    Hardware eMMC Issue when connected to board

    Yeah, I can confirm I restored BCPKG files without encryption. I also tried step 14 and there was nothing in the folders anyway, I still copied it all over just in case. Everything I've used has been the latest version from the recommended sources in the guides. I'm restoring the full nand...
  5. R

    Hardware eMMC Issue when connected to board

    I must be doing something wrong. Followed the guide to the letter (im 100% sure of it) When it comes to step 13.10 "Return to the main menu, then select ‘Launch > FS_XXX-exfat_nocmac_nogc’ where XXX is the firmware version you downgraded to." I see the Kosmos Atmosphere screen and it just...
  6. R

    Hardware eMMC Issue when connected to board

    So... With the fixed keyblob biskeydumpv9 reports no errors and dumps the keys If I then follow the steps and use Choidujour to create the 5.1.0 firmware bins and put them on the console following this guide https://www.youtube.com/watch?time_continue=1926&v=JTYmXY0YbJw and try to run CFW via...
  7. R

    Hardware eMMC Issue when connected to board

    Getting closer now after fixing the keyblob :) Through hakate if I press Stock (sysnand) the Nintendo logo shows then blank screen which is more than I've had so far... Ill continue with the firmware side of things now
  8. R

    Hardware eMMC Issue when connected to board

    Sorry to be a pain in the ass lol I found a prod.keys file from Yuzu emulator which was added on the 22 March. Used this in my prod.key file but replaced only the tsec and secure boot keys with my dumped ones. Ran linkle and it did output lots of data including keyblob_00 - 05...
  9. R

    Hardware eMMC Issue when connected to board

    Brilliant, thank you Just one more question if I may. I saw on another thread that choidujour only works up to FW 6.1 so given that the tools I can find suggest its on 5.1.0 but my fuse burn count of 12 says it's 9.1.0 - 9.2.0 I should try doing this using FW 5.1 then updating to the correct...
  10. R

    Hardware eMMC Issue when connected to board

    Using LockPick it was able to generate a prod.key file with lots of keys (45 in total) however during this process it shows some errors Keyblob Source 0 - 5 where generated but I guess if I use these I'll get the same issues?
  11. R

    Hardware eMMC Issue when connected to board

    Using the link you sent I was able to get the BIS 0,1,2,3 Crypt and Tweak keys. Hacdiskmount actually has these pre filled and they are the same and all test ok. I can confirm the serial at this offset is the same as my console sticker
  12. R

    Hardware eMMC Issue when connected to board

    Firstly thanks for helping :) Using biskeydumpv9 it will show the following HWI: xxxx... SBK: xxxx... SBK AESE 0 (test) : xxx.... eMMC initialized, looking for TSEC FW... Found TSEC FW at offset 0x00101900 of boot0... TSEC FW CRC32: b035021f - CORRECT TSEC using carveout 0x4003b000 rev 1 TSEC...
  13. R

    Hardware eMMC Issue when connected to board

    I've managed to get it working with the eMMc plugged in. Had to get the Jig and then it was able to correctly get into recovery mode and dump a full nand backup and boot/0, boot/1 .bins Still wont boot into anything. Hekate says it has burnt 12 fuses which would put the firmware at 9.1.0-9.2.0...
  14. R

    Hardware failed to init emmc

    @Crossfader is it the one on the mainboard? if so the part number is 5009130302
  15. R

    Hardware eMMC Issue when connected to board

    No, the PC wont even detect the switch is connected so TegraRcmGUI wont see RCM mode.
  16. R

    Hardware eMMC Issue when connected to board

    I got an unpatched switch off eBay that was sold as not turning on. The issue seems to be related to the eMMc. If I disconnect the eMMC and plug into the computer RCM is detected and I can boot Hekate. If the eMMc is connected to the board the PC won't see the console. As this is from eBay I...
  17. R

    Hardware [HELP] Emmc Chip Problem

    Was this ever fixed? I have the same issue. Auto RMC is on but PC wont detect the switch unless the eMMc is removed from the board.
  18. R

    Hardware Switch wont turn on, no charge display and strange issues

    Hoping someone here can help as I'm at a loss right now. I purchased a faulty unpatched switch from eBay as I'm looking to learn a bit more about 1) repairing and 2) modding. It was listed as doesn't turn on or charge and the seller stated it had never been opened. Having received the console...
General chit-chat
Help Users
    Xdqwerty @ Xdqwerty: Hi