i upgrade with the(6.2 exfat) in c
choidujournx , but im using a fat32 card right now.
if the problem persist send me pm and i will sent you the files im using , but for now im going work.
Why do you say that ? If you go to discord and those people who are highly expert on those things. AutoRCM IS NOT BRICK IT! STOP BEING A FAKE EXPERT. IF YOU DONT KNOW THEN DONT SAY IT.
Please don't be a false information to panic him. AutoRCM do not cause brick at all. DEFINITELY NOT, 100 percent. NOT!
I highly recommended you to go to Discord and join and have them help you. Your Switch is not brick. Something is just missing or something. If you want to join Discord.. Let me know and I will gladly send you an invitation so you can talk with ReiNX developer team. They are awesome people. I talked with them all the time. They are highly skill and an experience who responsible for ReiNX and they know all about ChoiNX as well. Pm me if you want.
I will try a few suggestions posted when I get home from work. I was in a couple discords last night but it was late, still some helpful people.
Thanks will report back later
Wait i thought i read that when you use choinx to update your fw you can not boot to official fw because it will burn your fuse and your sysnand will be updated. How come you updated again your fw? Isn't your fw supposed to be uodated already when you booted on/to ofw? I am confused.
It's somekind of brick that you can undo at anytime just by disable it.
It corrupt some bits on BOOT0,that's why your console cant boot on OFW and enter into rcm mode
Last edited by ucef,
I think you can boot ofw FROM hekate, since hekate ignores fuses. Correct me if I'm wrong
People dont want to pay closed source pirates for stolen code.
I dont want to start a discussion here, its just to clarify why people dont have emunand (yet).
Last edited by benjo,
That's funny. Thanks for the laugh. If you had any knowledge at all you would know that autoRCM started out as "Brickme". Its a soft brick. It purposefully soft bricks your Switch forcing it to RCM. Discord is full of people regurgitataing info that has been known and talked about for months on gbatemp.
Last edited by Kafluke,
Taken a turn for the worse. restored NAND tried to boot into CFW.
Tried OFW with SD card in no luck.
Tried OFW with SD card out no luck
Tried OFW with RCM off no luck
Guess i will follow this now https://guide.sdsetup.com/#/manualchoidowngrade
I'd also really like to know the cause of this. Either the OP is leaving out information on what he did that may have caused this or even worse, he did everything right and this still happened.
Not sure what else I can provide. If someone wants to know the 6.2 Firmware file I used to upgrade? It was supplied from a pretty reputable source. Seems to me that's the variable since I was able to boot RajNX and ReiNX on 5.1. The moment I upgraded to 6.2 is when I can no longer boot OFW or CFW.
--------------------- MERGED ---------------------------
I guess it COULD be the SD card since I have yet to test another, but I still cant boot OFW from my NAND, unless that was corrupted but hekate verified. Only other thing is...I am 90% sure it was FW 4~ when I made the NAND hekate states I have 5 burnt fuses. What if it was 3.0FW NAND and thats why I cant boot into OFW now because fuse count to high?
I assume you also flashed the boot0 and boot1 files as part of your nand restore since they are fw specific, if not you'll need to rebuild them using choidujour, etcher and memloader.
You could also have a corrupted fs, in which case you may need to format the system and User partitions using guiformat with a 16k cluster ensuring you format them using hacdismount by mounting the partitions using the correct keys.
Did you restore a nand or rebuild, restoring would mean it's likely the boot0/1 files. If you rebuilt could be boot files or corrupted fs.
Although if you've disabled autoRCM then it won't be the boot files. It'll be data on the system partition not compatible with the firmware ( delete all but 80000...20 in the system partition save folder, which will do a system initialise) or it's a corrupted fs.
Or you've used the wrong BISKEYS in the rebuild or used someone else's nand backup.....
You could also have a corrupted fs, in which case you may need to format the system and User partitions using guiformat with a 16k cluster ensuring you format them using hacdismount by mounting the partitions using the correct keys.
Did you restore a nand or rebuild, restoring would mean it's likely the boot0/1 files. If you rebuilt could be boot files or corrupted fs.
Although if you've disabled autoRCM then it won't be the boot files. It'll be data on the system partition not compatible with the firmware ( delete all but 80000...20 in the system partition save folder, which will do a system initialise) or it's a corrupted fs.
Or you've used the wrong BISKEYS in the rebuild or used someone else's nand backup.....
Last edited by PrEtZaL,
Similar threads
