Thread: [Announce] BackupMenu - OS backup & restore | New version - Jul 9th(v1.1)
View Single Post
zimon is offline zimon
2010-12-06 , 22:15
Posts: 1,341 | Thanked: 708 times | Joined on Feb 2010
#431
Originally Posted by RobbieThe1st View Post
I'm slightly lost here - I thought that everyone who is not able to get their code via the mtd1 method was -also- not able to login with -any- code?

Now, one thing I -did- notice was that when I was testing out that /dev/mtd1 grabber script, the -first- time I tested it with root console, I got my encrypted code. The -second- and all following times, I got a blank string back.
...
Either way, would you mind trying to grab it by installing BackupMenu and SSH server, then logging in and running "getlockcode" from the console? I'd like to see if it's an OS thing, or there -is- something different here.
No, I have always been able to get in the system and my security code has been working. It asks it every time when I boot, whether it is normal boot or after roofs+emmc flash.

Something is weird in that, because now with the same system and through Backupmenu's ssh-terminal, I can see 5 "lock_code" strings, where the last three give DES-hash on the 13th row.
I can find the correct original (12345), my previous and the current security codes with 'john'.

But I am sure, before there wasn't any DES-strings found when I did the "grep -A 13 lock_code /dev/mtd1"-thing.

It is funny, you got the same result once also.
Seems like something little chaotic in the system.