Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

not an issue just something id like to point out. the root password on my spectrum router was the serial number, maybe its the same for you #1

Open
DCFUKSURMOM opened this issue Nov 23, 2023 · 2 comments

Comments

@DCFUKSURMOM
Copy link

No description provided.

@DCFUKSURMOM
Copy link
Author

on mine the password was set at startup by a script (found it when poking around in failsafe mode, which logs in automatically without a password.) after finding the password i was able to boot normally, disable the script, and change the root password.

@DCFUKSURMOM DCFUKSURMOM changed the title not an issue just something id like to point out. the root password on my spectrum router was the serial number, it has the same login for the warehouse page so maybe the root pass is the same for you not an issue just something id like to point out. the root password on my spectrum router was the serial number, maybe its the same for you Nov 23, 2023
@dangerweenie
Copy link

dangerweenie commented May 24, 2024

This initially worked for me (interrupting via keystroke in the three seconds countdown), then logging in with root:serial, but after flashing to a snapshot (I flashed many due to an at-the-time mysterious issue with WAN not working that was ultimately resolved with a patch via commit), that prompt indicates "wrong password". No idea why this happened - I didn't think uboot would get modified.

Trying with the wrong password, it then drops me to an IP807x# uboot shell prompt with very few commands (I think this is busybox), can't copy in the open.sh and run it, but I was able to get back to booting via tftpboot by copying and pasting the lines one by one to set the env variables (had to change from "fw_setenv" to just "setenv".

Having no idea what was going on, and to follow whatever directions were available, I shorted the clock pin to 3.3v during the window described in this repo and was able to get everything back together as described above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants