Hardware Help my 3DS failed to downgrade!

  • Thread starter Thread starter ArviDroid
  • Start date Start date
  • Views Views 3,913
  • Replies Replies 46
I hope this isn't directed at me, as I never gave you "false" information. While FBI may be all you need, setting up MenuHAX+RedNAND//EmuNAND is essential to playing those games, and having an updated RedNAND//EmuNAND to be able to play games that may need a higher FW. Also, you need signature patches, which are not at all possible on SysNAND only with just FBI.

Again, here are the posts that I made.
No, of course not. I´m talking about one of my other threads were I thought people said that I needed to follow the whole guide. As I´m writing this I also do realize that I was partially at fault since no one actually said what I just wrote. They said to stop at the FBI part. But didn´t say that luma and all of that wasn´t necessary. So I believe that both parts made a mistake.
EDIT: WHY DIDN´T I READ EVERYTHING YOU SAID AND ONLY ANSWERED TO YOUR FIRST SENTENCE?! I´m terribly sorry. Maybe this was why I got myself bricked.

--------------------- MERGED ---------------------------

5 hours well spent! If someone invents a time-machine in the next few hours pm me.
 
Last edited by ArviDroid,
  • Like
Reactions: wormdood
lol someone made the same mistake yesterday of running the 2.1.0 downgrade on Sysnand even though it says in nice bold text On RedNAND
 
lol someone made the same mistake yesterday of running the 2.1.0 downgrade on Sysnand even though it says in nice bold text On RedNAND
But I did it on RedNAND I think. You just made me unsure of what I actually did now...
EDIT: Gods sake, you were right. I did downgrade on SysNAND. I FORGOT TO SWITCH TO THE FLIPPIN´ DARN REDNAND!
 
Last edited by ArviDroid,
But I did it on RedNAND I think. You just made me unsure of what I actually did now...
After reading over you didn't run the 2.10 downgrade on redNAND but instead on Sysnand which is a guaranteed brick. You were supposed to downgrade redNAND then run OTPhelper's once click setup which unbricks redNAND, verify's it, rights it to Sysnand, then verify's it again before asking to reboot.
 
After reading over you didn't run the 2.10 downgrade on redNAND but instead on Sysnand which is a guaranteed brick. You were supposed to downgrade redNAND then run OTPhelper's once click setup which unbricks redNAND, verify's it, rights it to Sysnand, then verify's it again before asking to reboot.
Yeah I know. I got caught up in the previous instructions and rushed it.
 
After reading over you didn't run the 2.10 downgrade on redNAND but instead on Sysnand which is a guaranteed brick. You were supposed to downgrade redNAND then run OTPhelper's once click setup which unbricks redNAND, verify's it, rights it to Sysnand, then verify's it again before asking to reboot.
No unbricking necessary on his o3DS. But yeah, from what I've read it does sound like he ran it through SysNAND. Even though, he said he ran it on RedNAND, however all the symptoms of his system, point to it having been done on SysNAND.
 
No unbricking necessary on his o3DS. But yeah, from what I've read it does sound like he ran it through SysNAND. Even though, he said he ran it on RedNAND, however all the symptoms of his system, point to it having been done on SysNAND.
Oh, I said that I did it on RedNAND? My bad then. I know now that I didn´t do it, thanks to you and my memory.

--------------------- MERGED ---------------------------

Well you guys have probalby cleared up everything possible. I now know that I actually didn´t have to downgrade to 2.1.0 or install luma or any of that. I only needed the good ol´9.2 and FBI. Since I didn´t know this until one hour ago; I tried to downgrade and failed because of a small detail. My fault.
Thanks everyone for your help.
 
Last edited by ArviDroid,

Site & Scene News

Popular threads in this forum