Error code 001-0502 and help to patch from github?

Support
1

i’ve looked up this error code before on this server, and get a basic idea of it, but things i dont understand: are the servers that pretendo uses overloaded? could my wifi be blocking access to it, and how would i check that? and lastly, i got this after downloading the update from the homebrew update app, and havent used my 3ds online a while before then, so i didnt think to check before the update (i also updated luma thru the downloader, so i dont know if that would factor into it)

if i need to update it from the github, can someone run me thru what to do, bullet point list style?

2

I haven’t personally dealt with 001-0502 really but see if this works.

I’d rather link it directly than try to sum it up into bullet points.

I think this error also appears when there’s an outage but I think it’s unlikely that one happened.

2 Likes
3

thank you! this will help alot, however currently other people are using the internet so i wont be able to try this untill later tonight when everyones asleep

EDIT: forgot to add that the version downloaded, the version on universal updater, and the current recent github version all seem to be the same, i have not tried a fresh install from github yet

4

Usually when you make an IP reservation, the internet only goes down for a minute or so (know this from experience) and you don’t necessarily have to make a reservation anyways

5

i fixed it, and i dont know how, if ur coming to this thread for a solution, heres what i did

  • settings
    internet settings
    connection settings
    the connection i was on (connection 1)
    change settings
    press the right arrow
    ip address
    set auto obtain to no

open phone,
check ip adress on it
enter, but did not have the bottom 2 ip options, left them blank
(subnet mask and gateway)

had the wrong ip, or wouldnt work without those 2 options

went to a site that lists ur ip, used that option, which was different from what the phone disclosed but a more familiar looking ip (when using file transfer at least)

used that one, still didnt work

set back to auto obtain,

no longer had the error

1 Like
6

It’s interesting that setting it back to auto-obtain is what fixed the issue. I wonder if deleting the connection and recreating it would have also fixed it?

1 Like