Lazarus3DS
Lazarus3DS copied to clipboard
AnalogMan151
002-0121 error code (ban) after using this script.
Because PMing you through GBATemp was a futile effort. I used your script and successfully unbricked an N3DS XL, only to find that it obtained a 002-0121 ban, restricting access to all online services, including e-shop. I had help from someone who used this script and they too had the same error code. My donor console was banned with an 002-0102, but his wasn't banned at all. So it can't be the fact that my donor console being banned had an effect on the unbricked console. Is this intentional? An error on my end? Is there even a solution outside of injecting an LCFS_B from another (unbanned) console?
Please note this has not had a public release yet and so troubleshooting may be limited.
I will treat your situation and the other persons as unrelated and separate due to lack of information.
This issue should only happen if the donor CTRNAND was not made using the donor creation script. Since that script requires files that have not been publicly released, some people have been using the CTRtransfer images hosted on the official guide. If this is what happened, then simply delete the LocalFriendCodeSeed_B on the revived console using GodMode9 and the console will recreate it from scratch using information stored within the console's hardware upon next boot.
The donor CTRNAND was made with the prep script, I have not obtained it from 3ds.guide.
Then it was made improperly as an important file, ticket_combo.db, is not yet publicly available. You can still try deleting the LocalFriendCodeSeed_B from 1:/rw/sys/ and reboot the 3DS to have it regenerate the original one that 3DS came with. Feel free to report back if that works or not.
and the console will recreate it from scratch using information stored within the console's hardware upon next boot
The 3DS regenerates the LocalFriendCodeSeed_B all by itself if it's missing.
That doesn't do anything, it regenerates an LCFS_A, and the ban message returns.
Ah, yours is one of the consoles that uses _A instead of _B. I have yet to come across one personally for testing. One more thing to try, rename SecureInfo_A in the same folder to SecureInfo_B. If that still does not grant it access to online then it seems that FriendCodeSeed was simply banned at some point. I will keep this issue open though for when the script releases publicly.
And about the ticket_combo.db, why isn't it publicly available? I used this script as I read d0k3 recommending it. His word valued as gold, I followed through.
ticket_combo contains title keys for system apps. I'm still working out if pre-including it would be allowed or not under the copywrite rules on various sites. If not, then pre-made donor images may be hosted on the official guide at some point.
The renaming of secureinfo_a to _b didn't work. The thing is this console was bricked for 2 years and I recall no banning on it. Maybe it got banned right after it bricked, I know for sure the brick happened when trying to install downgrade files to it, but foolishly using O3DS files instead of N3DS ones.
At the moment these are the only two instances I know of and none of the testers for Lazarus, nor my own console which it was tested on, has had banning issues. But if more information pops up or I find a cause, following traditional unbanning methods will need to suffice for now.
Hey @AnalogMan151, I'm the other person that @ForcedToRock was referring to. I was also able to recover a bricked n3ds xl using your scripts. Keep up the great work on this!
Here are the details on how I ended up with the banned console error after the recovery (replacing the LocalFriendCodeSeed_x did fix error)
I ran the prep script on a n3ds that was region converted from E to U. I also used the ticket.db from that console instead of the unreleased ticket_combo.db This resulted in the banned console error.
After talking with @ForcedToRock, I ran the prep script on a US n3ds xl instead of my region converted system. I did use the same ticket.db from the region converted system though. After using these new donor files to re-flash the unbricked n3ds xl I still got the ban error. After replacing the LocalFriendCodeSeed_x with the original from the bricked nand backup, the ban error message went away.
I don't know if any of this info is helpful but I figured I would share my experience. Thanks again and keep up the great work on this amazing tool!
