Quote:
Originally Posted by npoland
That's good to hear. I am an EE student so I find this kind of stuff very interesting. I am just wondering where I go from here? I am not really sure how to keep toying with this device.
Also I have images of the entire teardown including what is underneath the rf shielding if anyone wants to see what is going on inside...
|
Sure we do - just attach them all to a post.
You found that right after power-on, you could reach the u-boot command line.
The (other) K5 products use a "split" u-boot - so a capture of any information you can get out of u-boot would be nice to see.
Then (you can see this in the boot log you attached), u-boot loads the kernel which includes its initial ramfs system.
That is what is issuing that "... recovery system"
See if you can get into the recovery system at that stage.
It probable just expects any character - try return/enter/escape/whatever_works
Again, capture anything you can get out of it.
Why all of the capture requests?
Comparison of the 'new' with the 'known' is a powerful forensics tool.
In the boot log you attached, you will see that the kernel, when done running the initial ramfs system, does a switch root to the final runtime system.
That is what issued the login prompt.
When all of the messages end, it is still sitting at the login prompt, waiting for you to log in.
Let's see if they changed the user 'framework' and its password:
login: framework
password: mario
The worst that can happen is it will refuse to let you in.