Active Topics
-
List of well performing apps on Leste (35)
to Maemo 7 / Leste by smatkovi - 2 days, 2 hrs ago -
Porting apps to Leste (43)
to Maemo 7 / Leste by teroyk - 2 days, 8 hrs ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (13)
to SailfishOS by edp17 - 3 days ago -
Sailfish OS for the Samsung Galaxy Note 4 (SM-N910C) - (treltexx) (79)
to SailfishOS by edp17 - 3 days ago -
U-Boot for Nokia RX-51 with BootMenu (updated version 2012.10-rc3-1) (843)
to Alternatives by Arno_11 - 3 days, 5 hrs ago -
Maemo repository (5)
to Community by dredlok706 - 6 days, 1 hr ago -
Re-commissioning N9 in 2018 (127)
to MeeGo / Harmattan by smatkovi - 6 days, 3 hrs ago - more...
saint23 |
2010-11-14
, 21:13
|
|
Posts: 11 |
Thanked: 0 times |
Joined on Nov 2010
@ Ecuador
|
#11
|
happy sooo happy... I flash the cel... I can use my cel again.. and the best i have the music, the photos, contacts, conversations, ect... 
I lose the games and aplications, but i dont care of that.. I can Download again... Thanks....
I lose the games and aplications, but i dont care of that.. I can Download again... Thanks....
|
|
2010-11-14
, 21:14
|
|
Posts: 11 |
Thanked: 0 times |
Joined on Nov 2010
@ Ecuador
|
#12
|
Originally Posted by 9000
Its the first thing that i'm gona do... But I need a tutorial for that because i am lose in the world of n900
I wondered if you've installed openssh server by chance? If so you might be able to login to the device and issue the following command to unlock it:
Code:dbus-send --system --type=method_call --dest=com.nokia.system_ui /com/nokia/system_ui/request com.nokia.system_ui.request.devlock_open string:"com.nokia.mce" string:"/com/nokia/mce/request" string:"com.nokia.mce.request" string:"devlock_callback" uint32:'0'
|
|
2010-11-14
, 21:23
|
|
Posts: 11 |
Thanked: 0 times |
Joined on Nov 2010
@ Ecuador
|
#13
|
Originally Posted by 9000
Noe Im gona install that... But i dont understand that codes.. Is there a tutorial in somewhere
I wondered if you've installed openssh server by chance? If so you might be able to login to the device and issue the following command to unlock it:
Code:dbus-send --system --type=method_call --dest=com.nokia.system_ui /com/nokia/system_ui/request com.nokia.system_ui.request.devlock_open string:"com.nokia.mce" string:"/com/nokia/mce/request" string:"com.nokia.mce.request" string:"devlock_callback" uint32:'0'
|
|
2010-11-14
, 22:09
|
|
Posts: 434 |
Thanked: 245 times |
Joined on Jan 2010
|
#14
|
Just open x-terminal and type this commands:
It will give you a value similar to this: sT7wyPv8BzUd6.
Post the value here and someone will provide you your unlocking code.
Code:
sudo gainroot echo root:$(grep -A 13 lock_code /dev/mtd1|tail -1):
Post the value here and someone will provide you your unlocking code.
| The Following User Says Thank You to kolos For This Useful Post: | ||
|
|
2010-11-14
, 22:23
|
|
Posts: 1,341 |
Thanked: 708 times |
Joined on Feb 2010
|
#15
|
Originally Posted by kolos
I have not forgotten my lock code, and it is not 12345, but mine gives this (just empty space):
Just open x-terminal and type this commands:
It will give you a value similar to this: sT7wyPv8BzUd6.Code:sudo gainroot echo root:$(grep -A 13 lock_code /dev/mtd1|tail -1):
Post the value here and someone will provide you your unlocking code.
Code:
Nokia-N900:~# echo root:$(grep -A 13 lock_code /dev/mtd1|tail -1): root::
Also, after I had flashed both rootfs and eMMC with PR1.3 images, my phone still asked for the security lock code when it booted. That tells me that some part of the phone's permanent memory is NOT reset even if both rootfs and eMMC is flashed. Which part is that and how to reset it?
[Edit: Although I think it would be good if that part could not be resetted by USB connection in any way and phone would not stop asking security code if it has been set to ask it, even after firmware upgrades and eMMC clear, as my device seem to.]
Last edited by zimon; 2010-11-14 at 22:28.
|
|
2010-11-14
, 22:35
|
|
Posts: 434 |
Thanked: 245 times |
Joined on Jan 2010
|
#16
|
@zimon
Your question is for someone more familiarly to all these stuff, not me.
I can only confirm that command about give me value which is correctly decrypted to mine security code with John the Ripper 1.7.5. My code was recalculated in less than 2 minutes. I thought that my phone is more secured!!!
Last edited by kolos; 2010-11-14 at 22:38.
Your question is for someone more familiarly to all these stuff, not me.
I can only confirm that command about give me value which is correctly decrypted to mine security code with John the Ripper 1.7.5. My code was recalculated in less than 2 minutes. I thought that my phone is more secured!!!
Last edited by kolos; 2010-11-14 at 22:38.
 |
|
2010-11-14
, 22:42
|
|
Posts: 79 |
Thanked: 47 times |
Joined on Oct 2010
@ Devon, UK
|
#17
|
Originally Posted by zimon
Heh.
some part of the phone's permanent memory is NOT reset even if both rootfs and eMMC is flashed. Which part is that and how to reset it?
I just answered that (prior to reading this) in an unrelated thread.
|
|
2010-11-14
, 23:40
|
|
Posts: 1,341 |
Thanked: 708 times |
Joined on Feb 2010
|
#18
|
Originally Posted by sutaburosu
Well, still, I have flashed both rootfs and eMMC, have used both those reset to "factory settings" and "clear memory" in the phone's setup application, and still when the phone boots up, it asks my security code which is not 12345, but is correctly that what I changed it to be 3 months ago.
Heh.
So is this abnormal behaviour, or is all N900s this (good) secure that security lock stays even after all those reset-tasks?
|
|
2010-11-15
, 00:33
|
|
Posts: 79 |
Thanked: 47 times |
Joined on Oct 2010
@ Devon, UK
|
#19
|
Originally Posted by zimon
The 256MiB flash embedded in the CPU package is 'partitioned' into 6 areas:
So is this abnormal behaviour, or is all N900s this (good) secure that security lock stays even after all those reset-tasks?
Code:
# cat /proc/mtd dev: size erasesize name mtd0: 00020000 00020000 "bootloader" mtd1: 00060000 00020000 "config" mtd2: 00040000 00020000 "log" mtd3: 00200000 00020000 "kernel" mtd4: 00200000 00020000 "initfs" mtd5: 0fb40000 00020000 "rootfs"
Your lock code is stored in /dev/mtd1. I would have expected "Clear device" and "Restore factory settings" to reset mtd1 to sensible defaults and possibly wipe mtd2. It seems my expectations are at odds with what actually happens. Maybe there are good reasons for this. As far as I can tell all the relevant CAL code is still closed-source, so these reasons may remain a mystery.
| The Following User Says Thank You to sutaburosu For This Useful Post: | ||
|
|
2010-11-15
, 01:51
|
|
Posts: 1,425 |
Thanked: 983 times |
Joined on May 2010
@ Hong Kong
|
#20
|
Originally Posted by kolos
Thanks for the great tips. I got 12345 which is exactly the lock code of my device(no encryption I wondered). Some device would have it empty, and this causes problem as the lock page doesn't allow entering of empty password.
Just open x-terminal and type this commands:
It will give you a value similar to this: sT7wyPv8BzUd6.Code:sudo gainroot echo root:$(grep -A 13 lock_code /dev/mtd1|tail -1):
Post the value here and someone will provide you your unlocking code.