Active Topics
-
The N900 is now 15 years old! (6)
to Nokia N900 by Macros - 1 day, 3 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 1 day, 16 hrs ago -
n770 youtube video (0)
to General by nmdv - 5 days, 15 hrs ago - more...
 |
|
2019-09-29
, 18:38
|
|
Posts: 584 |
Thanked: 1,550 times |
Joined on Sep 2019
|
#1382
|
Hello all,
I'm having some trouble getting into openmode.
I must have tried a dozen different ways, incl. the version in the wiki and the version in the README.
I use this flasher version, the firmware.bin and emmc.bin from here, and this openmode kernel.
Do all these files fit together?
I am not getting any errors.
The last command's full output:
It looks OK.
But no matter what and how I try, I keep getting a yellow warning triangle when I boot.
At some point I managed to ssh into the phone and executed this command:
I also tried the same command as user and got the same error.
Did the open kernel even flash properly? the uname command suggests otherwise?
I'm having some trouble getting into openmode.
I must have tried a dozen different ways, incl. the version in the wiki and the version in the README.
I use this flasher version, the firmware.bin and emmc.bin from here, and this openmode kernel.
Do all these files fit together?
I am not getting any errors.
The last command's full output:
Code:
# flasher -f -F firmware.bin -F emmc.bin -R ; flasher -a firmware.bin -k zImage_2.6.32.54-openmode_l2fix --flash-only=kernel -f -R
flasher 3.12.1 (Oct 5 2011) Harmattan
WARNING: This tool is intended for professional use only. Using it may result
in permanently damaging your device or losing the warranty.
USB device found at bus 001, device address 007.
Device identifier: 357923041515935 (SN: N/A)
Found device RM-696, hardware revision 1507
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3_PR_001
Sending ape-algo image (7096 kB)...
100% (7096 of 7096 kB, avg. 23734 kB/s)
Suitable USB interface (phonet) not found, waiting...
USB device found at bus 001, device address 008.
Device identifier: 357923041515935 (SN: N/A)
Raw data transfer EP found at EP2.
Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-696 rev. 1507
Server implements softupd protocol version 1.8
Image SW version DFL61_HARMATTAN_40.2012.21-3_PR_001
Image moslo not present
Image tar skipped
Image config skipped
Battery level 72 %, continuing.
image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] cert-sw [finished 100 % 1 / 1 kB NA ]
[x] cmt-2nd [finished 100 % 95 / 95 kB NA ]
[x] cmt-algo [finished 100 % 789 / 789 kB NA ]
[x] cmt-mcusw [finished 100 % 6050 / 6050 kB 2973 kB/s]
[x] xloader [finished 100 % 23 / 23 kB NA ]
[x] secondary [finished 100 % 94 / 94 kB NA ]
[x] kernel [finished 100 % 2714 / 2714 kB 1931 kB/s]
[x] rootfs [finished 100 % 1170282 / 1170282 kB 11121 kB/s]
[x] mmc [finished 100 % 1264659 / 1264659 kB 19622 kB/s]
Updating SW release
Success
flasher 3.12.1 (Oct 5 2011) Harmattan
WARNING: This tool is intended for professional use only. Using it may result
in permanently damaging your device or losing the warranty.
Picked ape-algo from a FIASCO file
Suitable USB interface (bootloader/phonet) not found, waiting...
USB device found at bus 001, device address 009.
Device identifier: 357923041515935 (SN: N/A)
Found device RM-696, hardware revision 1507
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3_PR_001
Sending ape-algo image (7096 kB)...
100% (7096 of 7096 kB, avg. 43805 kB/s)
Suitable USB interface (phonet) not found, waiting...
USB device found at bus 001, device address 010.
Device identifier: 357923041515935 (SN: N/A)
Raw data transfer EP found at EP2.
Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-696 rev. 1507
Server implements softupd protocol version 1.8
Image SW version <none>
Image cert-sw not present
Image cmt-2nd skipped
Image cmt-algo skipped
Image cmt-mcusw skipped
Image xloader skipped
Image secondary skipped
Image moslo skipped
Image rootfs skipped
Image mmc skipped
Image tar skipped
Image config skipped
Battery level 81 %, continuing.
image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] kernel [finished 100 % 2712 / 2712 kB 2105 kB/s]
Updating SW release
Success
But no matter what and how I try, I keep getting a yellow warning triangle when I boot.
At some point I managed to ssh into the phone and executed this command:
Code:
~ # whoami root ~ # uname -a Linux RM696 2.6.32.54-dfl61-20121301 #1 PREEMPT Sat Mar 2 23:11:21 EET 2013 armv7l GNU/Linux ~ # disclaimer-cal remove View-openmode CAL ERROR: nand_write: write (4096 bytes at around 0021f000): Input/output error disclaimer-cal: Failed to write to CAL
Did the open kernel even flash properly? the uname command suggests otherwise?
|
|
2019-10-01
, 16:29
|
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#1383
|
Originally Posted by nonsuch
Your device is in openmode after that, no problems there.
It looks OK.
But no matter what and how I try, I keep getting a yellow warning triangle when I boot.
However this does not get rid of the "ugly-triangle-and-warning" screen in the startup.
The problem is that to remove the openmode-warning with disclaimer-cal you need to do that before booting into openmode, because it is stored in a memory location hat is no longer accessible in openmode
So, the correct procedure is;
- 1. Flash the device clean in closed mode
- 2. remove the ugly warning
- 3. Flash the device back-to-back to openmode
Originally Posted by nonsuch
Yes, most likely the openmode flashing went quite OK.
At some point I managed to ssh into the phone and executed this command:
[~ # whoami
root
~ # uname -a
Linux RM696 2.6.32.54-dfl61-20121301 #1 PREEMPT Sat Mar 2 23:11:21 EET 2013 armv7l GNU/Linux
~ # disclaimer-cal remove View-openmode
CAL ERROR: nand_write: write (4096 bytes at around 0021f000): Input/output error
disclaimer-cal: Failed to write to CAL
I also tried the same command as user and got the same error.
Did the open kernel even flash properly? the uname command suggests otherwise?
The reason the kernel string in uname looks exactly like in the closed-mode kernel is because I made it so
If the kernel version string had changed, then you'd have to copy in new modules too. Now as it is the openmode kernel works as a drop-in and uses the same modules under /lib/modules/
__________________
Dave999: Meateo balloons. What’s so special with em? Is it a ballon?
Dave999: Meateo balloons. What’s so special with em? Is it a ballon?
| The Following 3 Users Say Thank You to juiceme For This Useful Post: | ||
|
|
2019-10-01
, 16:31
|
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#1384
|
Originally Posted by juiceme
I forgot to say, just if you don't believe that check the few first lines in dmesg to see the kernel build and version...
If the kernel version string had changed, then you'd have to copy in new modules too. Now as it is the openmode kernel works as a drop-in and uses the same modules under /lib/modules/
__________________
Dave999: Meateo balloons. What’s so special with em? Is it a ballon?
Dave999: Meateo balloons. What’s so special with em? Is it a ballon?
| The Following 3 Users Say Thank You to juiceme For This Useful Post: | ||
|
|
2019-10-01
, 17:01
|
|
Posts: 584 |
Thanked: 1,550 times |
Joined on Sep 2019
|
#1385
|
Originally Posted by juiceme
I actually figured it out while I was waiting for my post to be published! Sorry for the noise.
The problem is that to remove the openmode-warning with disclaimer-cal you need to do that before booting into openmode, because it is stored in a memory location hat is no longer accessible in openmode
I must say it's a bit of a treasure hunt wild web adventure with half the files referenced in the tutorials gone... But your (swagman.org yours?) website has everything I need now - I hope.
The reason the kernel string in uname looks exactly like in the closed-mode kernel is because I made it so
If the kernel version string had changed, then you'd have to copy in new modules too. Now as it is the openmode kernel works as a drop-in and uses the same modules under /lib/modules/
| The Following 3 Users Say Thank You to nonsuch For This Useful Post: | ||
 |
|
2019-10-01
, 19:01
|
|
Posts: 4,118 |
Thanked: 8,901 times |
Joined on Aug 2010
@ Ruhrgebiet, Germany
|
#1386
|
Originally Posted by juiceme
For the next poor soul that tries (is described elsewhere as well),
Your device is in openmode after that, no problems there.
However this does not get rid of the "ugly-triangle-and-warning" screen in the startup.
The problem is that to remove the openmode-warning with disclaimer-cal you need to do that before booting into openmode, because it is stored in a memory location hat is no longer accessible in openmode
So, the correct procedure is;
- 1. Flash the device clean in closed mode
- 2. remove the ugly warning
- 3. Flash the device back-to-back to openmode
with back-to-back is meant to do;
3.a flash device (firmware) in closed mode
do NOT boot up
3.b flash open-mode-kernel
Have fun!
__________________
SIM-Switcher, automated SIM switching with a Double (Dual) SIM adapter
--
Thank you all for voting me into the Community Council 2014-2016!
Please consider your membership / supporting Maemo e.V. and help to spread this by following/copying this link to your TMO signature:
[MC eV] Maemo Community eV membership application, http://talk.maemo.org/showthread.php?t=94257
editsignature, http://talk.maemo.org/profile.php?do=editsignature
SIM-Switcher, automated SIM switching with a Double (Dual) SIM adapter
--
Thank you all for voting me into the Community Council 2014-2016!
Please consider your membership / supporting Maemo e.V. and help to spread this by following/copying this link to your TMO signature:
[MC eV] Maemo Community eV membership application, http://talk.maemo.org/showthread.php?t=94257
editsignature, http://talk.maemo.org/profile.php?do=editsignature
|
|
2020-07-22
, 16:16
|
|
Posts: 139 |
Thanked: 176 times |
Joined on Oct 2012
|
#1387
|
Originally Posted by peterleinchen
This still eludes me, after doing 'disclaimer-cal remove View-openmode', how could i flash the device again without it restoring the warning message. Because that's what happend.
For the next poor soul that tries (is described elsewhere as well),
with back-to-back is meant to do;
3.a flash device (firmware) in closed mode
do NOT boot up
3.b flash open-mode-kernel
Have fun!
Finally, after removing the warning with 'disclaimer-cal remove View-openmode', i settled to not doing a full flash but just this:
Code:
./flasher64 -f -F main.bin -F emmc.bin --flash-only=mmc ./flasher64 -a main.bin -k zImage_2.6.32.54-openmode_l2fix --flash-only=kernel -f
Code:
rm -fr .accounts/* rm -fr .activesync/* rm -fr .aegis/*
Can somebody hint what could be wrong. Or what are the correct flashing commands, after disabling the warning message.
Last edited by veeall; 2020-07-22 at 16:24.
| The Following User Says Thank You to veeall For This Useful Post: | ||
|
|
2020-07-22
, 19:35
|
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#1388
|
It's exactly like you described; first do the 'disclaimer-cal remove View-openmode', then flash back to back.
However I cannot remember exactly what was the command line so that the device gets flashed so that the openmode warning is still off. (I should dig up one of my old N9's and check it...)
About the other problem, crashing of applications when installing stuff; I remember that was a problem which was patched and the patch/explanation should be somewhere on TMO too.
However I cannot remember exactly what was the command line so that the device gets flashed so that the openmode warning is still off. (I should dig up one of my old N9's and check it...)
About the other problem, crashing of applications when installing stuff; I remember that was a problem which was patched and the patch/explanation should be somewhere on TMO too.
__________________
Dave999: Meateo balloons. What’s so special with em? Is it a ballon?
Dave999: Meateo balloons. What’s so special with em? Is it a ballon?
|
|
2020-07-23
, 06:41
|
|
Posts: 4,118 |
Thanked: 8,901 times |
Joined on Aug 2010
@ Ruhrgebiet, Germany
|
#1389
|
Skimming through the README and the thread I just found (after 7y) that juiceme has a small quirk in his description which I never noticed as I was doing it on my own way.
See here
https://talk.maemo.org/show.hreadt.p...&postcount=698
and here (kne post earlier)
https://talk.maemo.org/showthread.ph...&postcount=697
afair you do not need to flash emmc for back-to-back, firmware is enough. It does not hurt either.
BUT what you must not give is the parameter '-R' for the firmware flash after disclaimer removal and before kernel flash.
which I never noticed as I was doing it on my own way.See here
https://talk.maemo.org/show.hreadt.p...&postcount=698
and here (kne post earlier)
https://talk.maemo.org/showthread.ph...&postcount=697
Originally Posted by juiceme
If you want to remove the openmode warning, you need to flash it clean to cosed mode first;
sudo flasher -F firmware.bin -F emmc.bin -f -R
Then remove the warning:
disclaimer-cal remove View-openmode
And last, do the back-to-back flashing.
The back-to-back flashing procedure is to make sure that when the device boots up the first time after a clean flash, it boots to open mode.Why this is important; After a clean flash, the first boot creates the aegis keys for the device. These keys are different for open mode and closed mode, and if you have closed mode keys in open mode device you will have lots of random problems.
So, how this is done, is you need to clean-flash, and then immediately flash an open mode kernel before the device boots after the clean flash.In Linux (as well as Windoze) you can enter 2 flashing commands on the same row, separated by semicolon, so that when first command is executed, the second command is executed right after it:
sudo flasher -F firmware.bin -F emmc.bin -f-R; sudo flasher -a firmware.bin -k zImage_2.6.32.54-openmode_l2fix --flash-only=kernel -f -R
BUT what you must not give is the parameter '-R' for the firmware flash after disclaimer removal and before kernel flash.
__________________
SIM-Switcher, automated SIM switching with a Double (Dual) SIM adapter
--
Thank you all for voting me into the Community Council 2014-2016!
Please consider your membership / supporting Maemo e.V. and help to spread this by following/copying this link to your TMO signature:
[MC eV] Maemo Community eV membership application, http://talk.maemo.org/showthread.php?t=94257
editsignature, http://talk.maemo.org/profile.php?do=editsignature
SIM-Switcher, automated SIM switching with a Double (Dual) SIM adapter
--
Thank you all for voting me into the Community Council 2014-2016!
Please consider your membership / supporting Maemo e.V. and help to spread this by following/copying this link to your TMO signature:
[MC eV] Maemo Community eV membership application, http://talk.maemo.org/showthread.php?t=94257
editsignature, http://talk.maemo.org/profile.php?do=editsignature
| The Following User Says Thank You to peterleinchen For This Useful Post: | ||
|
|
2020-07-23
, 17:03
|
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#1390
|
Thanks @peterleinchen; Indeed it has been quite a few years since I last played with those that I was not sure any longer what was the exact flasher command to get the desired result 
__________________
Dave999: Meateo balloons. What’s so special with em? Is it a ballon?
Dave999: Meateo balloons. What’s so special with em? Is it a ballon?
| The Following User Says Thank You to juiceme For This Useful Post: | ||