Talk:Flashing the GSM Firmware

From Openmoko

(Difference between revisions)
Jump to: navigation, search
(Large microSD cards won't boot: Add confirmation of issue)
Line 161: Line 161:
 
We're busy on this. Follow wiki instructions, or come up with an automatism by yourself. Expect any update on january.
 
We're busy on this. Follow wiki instructions, or come up with an automatism by yourself. Expect any update on january.
  
== microSD size issue  4Gb KO, 1Gb Ok ==
+
== Large microSD cards won't boot ==
  
 
I use a usd 4Gb that boots well with Qi, but don't with NOR, this kind of usd can't be used then for flashing.
 
I use a usd 4Gb that boots well with Qi, but don't with NOR, this kind of usd can't be used then for flashing.
Line 167: Line 167:
  
 
[Philippelhardy 2009-06_27]
 
[Philippelhardy 2009-06_27]
 +
 +
: I had the same problem. 8 GB microSD wouldn't boot. 512 MB microSD worked fine. --[[User:Joejarvis|Joseph M. Jarvis]] 17:39, 4 August 2010 (UTC)
  
 
== bug #1024 ==
 
== bug #1024 ==

Revision as of 18:39, 4 August 2010

please refer to this very wikipage regarding -oo and flowcontrol Stephan_schmidt had exactly same issue and we fixed it yesterday, using these modifications


WARNING : Flash failed ! From Sleg on 2008/11/25 :


I had a problem during flashing my firmware ... I started again the module by typing 's3c24xx-gpio b7=1' as said in the wiki, and it started to flash the firmware. While it was flashing (I could see the progress ...) I failed by a 'Flash operation timeout'

The GSM module seems to not respond anymore :'(

If I retry, I get :

root@om-gta02:/usr/sbin# FLUID_PORT=/dev/ttySAC0 FLUID_FLOWCONTROL=h fluid.exe \
> -oO -b 115200 \
> -f $HOME/gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-moko10.m0
FLUID Revision 2.27, (23 Aug 2004). Copyright Texas Instruments, 2001-2004.
Reading image file: '/home/root/gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-moko10.m0' (2138kB) ok
Bootloader: 

But nothing append even if I start the module by typing in another terminal 's3c24xx-gpio b7=1'

Can somebody please help me ?? sleg AT tsleg -DOT- com


Thanks to Stefan Schmidt on the kernel mailing list My GSM went back !

here is what I did : (Without FLOWCONTROL and with -oo to choose the ROM bootloader)

root@om-gta02:~# opkg install http://people.openmoko.org/joerg/calypso_moko_FW/fluid_0.0+svn20070817-r2_armv4t_eabi.ipk
Downloading http://people.openmoko.org/joerg/calypso_moko_FW/fluid_0.0+svn20070817-r2_armv4t_eabi.ipk
Installing fluid (0.0+svn20070817-r2) to root...
Configuring fluid
root@om-gta02:~# opkg install http://people.openmoko.org/joerg/calypso_moko_FW/s3c24xx-gpio_1.0+svnr4130-r2.1_armv4t.ipk
Downloading http://people.openmoko.org/joerg/calypso_moko_FW/s3c24xx-gpio_1.0+svnr4130-r2.1_armv4t.ipk
Multiple packages (s3c24xx-gpio and s3c24xx-gpio) providing same name marked HOLD or PREFER.  Using latest.
Installing s3c24xx-gpio (1.0+svnr4130-r2.1) to root...
Configuring s3c24xx-gpio
root@om-gta02:~# wget http://people.openmoko.org/joerg/calypso_moko_FW/gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-moko10.m0
Connecting to 10.194.51.41:3128 (10.194.51.41:3128)
gsm_ac_gp_fd_pu_em_c 100% |**************************************************************************************************|  5419k 00:00:00 ETA
root@om-gta02:~# echo 0 >/sys/bus/platform/devices/neo1973-pm-gsm.0/power_on
root@om-gta02:~# echo 1 >/sys/bus/platform/devices/neo1973-pm-gsm.0/power_on
root@om-gta02:~# cd /usr/sbin
root@om-gta02:/usr/sbin# FLUID_PORT=/dev/ttySAC0 fluid.exe -oo -b 115200 -f $HOME/gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-moko10.m0
FLUID Revision 2.27, (23 Aug 2004). Copyright Texas Instruments, 2001-2004.
Reading image file: '/home/root/gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-moko10.m0' (2138kB) ok
Bootloader: (reset target) (ROM, version ?) ok
Checksumming (269 * 8kB = 2152kB):  ok
Flash Detect: (0xEC, 0x22A0) Samsung K5A3240CT ok
Program: (31 sectors, 243*8k=1944k) (******************) ok
root@om-gta02:/usr/sbin# 

And to wake up the GSM in another ssh window :

root@om-gta02:~# echo 0 >/sys/bus/platform/devices/neo1973-pm-gsm.0/power_on
root@om-gta02:~# echo 1 >/sys/bus/platform/devices/neo1973-pm-gsm.0/power_on



i recive instead of

"Program: (34 sectors, 267*8k=2136k) (*******************) ok"

this

"Program: (0 sectors, 0*8k=0k) () ok"

iam currently reflashing the old firmware, that seems to work.

iam using an non-us gsm-freerunner (recived yesterday so most likely the latest hardwar)

thakoman


[2008-11-19 04:46:39] <Wonka> DocScrutinizer: flashing to moko10-beta2 went though cleanly, i already had working ppp connects with the previously non-working SIM.

[2008-11-19 04:48:24] <Wonka> DocScrutinizer: but there are still problems... more often than not, the GSM chip does not answer. pppd opens the device, gets "AT command interpreter ready", utters "AT\n" and gets nothing. power off, power on, reset on, reset off, try gain... sometimes it works, but mostly not.


O2 UK prepay 3G SIM works with moko10-beta2, was previously not detected. T-mobile UK prepay SIM and old Orange UK contract SIM work with both old and new. Testing so far is cursory at best, but looks good. [quote: Alastair Johnson on devel-ML]

[2008-11-21] I flashed 6 out of our 8 Freerunner V.6 according to the GSM/Flashing- guide. I had no problems and the previously useless 3G- SIMs are working fine now. It seems like the 3G- SIM Issue, our beloved #666, is solved. You should point it out clearly. I heard a lot of users complain about this. The solution is simple and well hidden on the website. By the way, i have new 3G- SIM cards of the following german providers running without problems (O2, T- Mobile, E-Plus, Vodafone). Before the flashing procedure the Vodafone cards were not detected. Good work guys... thanks! Reiner

Contents

Works now with new gsm firmware moko10beta2 with O2 in Germany

Very great, I can make calls now after waiting for 5 month, big surprise :). Thanks a lot! --Kevin 15:18, 20 November 2008 (UTC)


I'm very happy to be able to report that the update went smoothly for me (without yielding any surplus "building materials") and that a new O2 SIM from http://freesim.o2.co.uk/ which never worked in my Freerunner before now seems to be working fine. Great work!

Tom

--

Thomas White Department of Materials Science and Metallurgy Electron Microscopy Group (PhD Student) University of Cambridge / Downing College




The flash worked without a hitch for me and now I am able to use a Vodafone prepaid SIM in my 850MHz unit while back in Europe. I am running Om2008.9 with the 20081023 FDOM modifications applied.

Great job!

-Jacob




Hello!

Replying under subject Success :) I've combined what Michael said (few echo 1 >> .... and echo 0 >> .... in the other terminal) and Joerg's suggestion (-oo instead of -oO) and it worked perfectly. The upgrade to moko10 was done.

So I can confirm the freerunner now works with Simobil's (Slovenian GSM operator) SIM.

Great job and thanks to all that took the time to do it.

Boštjan

State SD-image?

Any update on a SD-image for GSM flashing?


[joerg 2008-12-10 02:43:32]

We're busy on this. Follow wiki instructions, or come up with an automatism by yourself. Expect any update on january.

Large microSD cards won't boot

I use a usd 4Gb that boots well with Qi, but don't with NOR, this kind of usd can't be used then for flashing. I nevertheless did the test and i confirm that it worked only when i used a smaller 1Gb usd.

[Philippelhardy 2009-06_27]

I had the same problem. 8 GB microSD wouldn't boot. 512 MB microSD worked fine. --Joseph M. Jarvis 17:39, 4 August 2010 (UTC)

bug #1024

[Tebra 2009-01-13 07:45]

Hi. Are you working on moko11 to fix #1024 bug? Because of that bug I can't use android distribution.

German/Vodafone

Got a new Vodafone Prepaid SIM-Card. Didn't work with QTExtended nor with Android until I've used the procedure to upgrade the GSM-Firmware. Looks like it's not just "swiss sim cards". Regards, --Rtreffer 17:14, 25 January 2009 (UTC)

Broken GTA01bv4 GSM Modem Fix

I recently had to do a special process to recover my GTA01bv4 after breaking the gsm modem with a failed flash. The process is actually fairly simple.

  • Unplug USB and remove the battery for about 10s to ensure that the GSM chipset is powered off, then replace the battery and re-connect the USB
  • boot up from a distro that is neutered so that it does not access or turn on the gsm modem at all
  • issue this stty command twice:
 stty 0:4:18b2:8a00:0:0:7f:15:4:0:0:0:0:0:0:0:12:f:17:16:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0 -F /dev/ttySAC0
  • issue this fluid command:
 FLUID_PORT=/dev/ttySAC0 fluid.exe -oo -od13,13 -vvv -b115200 -f $HOME/filename.m0
  • in another ssh session, issue this command:
 echo 1 > /sys/bus/platform/devices/neo1973-pm-gsm.0/power_on

After this, the flashing proceeded as expected, and all seems alright. I'll have to push a new distro to it to be certain, but all looks good so far. Quinn Storm 22:39, 16 March 2009 (UTC)

Added note about battery removal. Mmontour 01:51, 17 March 2009 (UTC)

Flash using uSD card image worked!

I'm now able to use my "MobilePlus" (Mobistar network) SIM which failed to register previously. Thanks for this excellent tool!

--M8ram 15:16, 26 April 2009 (UTC)

Successful update here. Didn't fix unregistering SIM card under Android. I'll test few more things. --Mikeful 22:06, 18 June 2009 (UTC)

What is FLUID?

Please create a link to an explanation of what FLUID is when FLUID is first mentioned at the top of the page.

The name of the page

The name of this page is GSM/Flashing, which may be confused with Flashing_the_Neo_FreeRunner ? You could call it Firmware/Flashing (which breaks a lot of links .. and you need a stub.. )

--pike 00:07, 18 May 2009 (UTC)

Remove uSD - optional ?

At the bottom of par.3, it reads

>>You may can now remove bat and uSD

.. ("may"/"can") - "if you want to". I don't see a reason why you should ?

I did notice I couldn't get into the NoR menu without twiddling around with battery and sim; but not sure what was going on there.

--pike 00:07, 18 May 2009 (UTC)

===== Visibility of the final Messagge "D_O_N_E" =====

At the end of flashing process the final message "D_O_N_E" in green over black, it's not so readable. In general if yous see a green messagge, also if you cannot read it well, you can safely reboot, the Flashing process it's done. --Apertum 13:18, 18 May 2009 (UTC)

See http://pike.kw.nl/files/documents/pike/personal/photoos/2009/20090518/DSCN0644.JPG : i guess 'D_O_N_E' is more appropriately described 'when the console turns green'. --Pike 13:18, 18 May 2009 (UTC)

That's been the rationale of doing it this way ;-) /jOERG

Suggestion for uSD Instruction Steps

On the second step of the uSD Installation procedure with dd command, i suggest to add this text:

Before proceding make sure that the uSD memory is NOT already formatted. With simple GUI like Gparted o QParted, you can unmount the right uSD partitions, and remove all the partition to have a simple uSD not formatted (the right formatted partition will be automatically transferred with the next 'dd' image transfer command).

Because i've seen that if i have an already Ext2/3 formatted uSD (or any other partition), the 'dd' Command it's not working tranferring the image.--Apertum 21:03, 18 May 2009 (UTC)

The original istructions to dd to physical device will overwrite whatever filesystem may have been on uSD, incl. partition-table/MBR. If dd is not working, you encounter some different problem, maybe caused by not correctly unmounting all partitions, or by a typo in dd. The instructions cover these cases as well.

-- jOERG 2009-05-19 00:05

Suggestion: Add a big Note Sticky at the beginning of the page to avoid editing the page

Suggestion: add a very big Note Sticky at the beginning of the page to avoid editing the page by the community.

The beginnig phrase: "This is NO communtity driven page, please be reluctant and careful with edits. Thanks " must be a lot bigger to avoid errors, IMHO.--Apertum 21:11, 18 May 2009 (UTC)

--- seems there's no way to place a warning big enough for everybody anywhere on the page. Probably will lock eventually.

-- jOERG 2009-05-19 00:05

You can add a simple:

WARNING: This is NO communtity driven page, please be reluctant and careful with edits. Thanks


It's a lot more visibile and clear, IMHO. Anyway a lock it's safer, of course. --Apertum 22:34, 18 May 2009 (UTC)

Using scp from desktop

I don't have a card reader so I tried the scp command suggested. However, at the end it returns

scp: /dev/mmcblk0: truncate: Invalid argument

ALternatively, I mounted the desktop PC folder with the image using nfs and dd from there. -- User:fmartins 2009-08-15

I'm quite sure you're using a wrong command, what's your input?

usage of scp: scp IP:path_to_orig_file IP:path_to_to_dest_file

Dareus


Hi! I got the same error, this is what I did:

$ scp flash-moko11-2.image root@192.168.0.202:/dev/mmcblk0
root@192.168.0.202's password: 
flash-moko11-2.image                                    100%  270MB 293.2KB/s   15:43
scp: /dev/mmcblk0: truncate: Invalid argument
$

GTA02 now running MOKO11, but still having problems with SIMs

I updated my GTA02 to MOKO11, but 2 of my 3 SIM's (All from same carrier) still doesn't work.

SIM 1 works fine, with PIN and everything.
SIM 2 get's full GSM signal, but tells me "SOS Only" PIN Disabled
SIM 3 doesn't recieve a GSM signal at all, and GSM modem won't turm on. PIN Disabled.

All 3 SIMs works fine in my Nokia and HP phones.

I have tried with SHR and Android distros, but it's the same result.

Is there a MOKO12 on the way??

Personal tools

please refer to this very wikipage regarding -oo and flowcontrol Stephan_schmidt had exactly same issue and we fixed it yesterday, using these modifications


WARNING : Flash failed ! From Sleg on 2008/11/25 :


I had a problem during flashing my firmware ... I started again the module by typing 's3c24xx-gpio b7=1' as said in the wiki, and it started to flash the firmware. While it was flashing (I could see the progress ...) I failed by a 'Flash operation timeout'

The GSM module seems to not respond anymore :'(

If I retry, I get :

root@om-gta02:/usr/sbin# FLUID_PORT=/dev/ttySAC0 FLUID_FLOWCONTROL=h fluid.exe \
> -oO -b 115200 \
> -f $HOME/gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-moko10.m0
FLUID Revision 2.27, (23 Aug 2004). Copyright Texas Instruments, 2001-2004.
Reading image file: '/home/root/gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-moko10.m0' (2138kB) ok
Bootloader: 

But nothing append even if I start the module by typing in another terminal 's3c24xx-gpio b7=1'

Can somebody please help me ?? sleg AT tsleg -DOT- com


Thanks to Stefan Schmidt on the kernel mailing list My GSM went back !

here is what I did : (Without FLOWCONTROL and with -oo to choose the ROM bootloader)

root@om-gta02:~# opkg install http://people.openmoko.org/joerg/calypso_moko_FW/fluid_0.0+svn20070817-r2_armv4t_eabi.ipk
Downloading http://people.openmoko.org/joerg/calypso_moko_FW/fluid_0.0+svn20070817-r2_armv4t_eabi.ipk
Installing fluid (0.0+svn20070817-r2) to root...
Configuring fluid
root@om-gta02:~# opkg install http://people.openmoko.org/joerg/calypso_moko_FW/s3c24xx-gpio_1.0+svnr4130-r2.1_armv4t.ipk
Downloading http://people.openmoko.org/joerg/calypso_moko_FW/s3c24xx-gpio_1.0+svnr4130-r2.1_armv4t.ipk
Multiple packages (s3c24xx-gpio and s3c24xx-gpio) providing same name marked HOLD or PREFER.  Using latest.
Installing s3c24xx-gpio (1.0+svnr4130-r2.1) to root...
Configuring s3c24xx-gpio
root@om-gta02:~# wget http://people.openmoko.org/joerg/calypso_moko_FW/gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-moko10.m0
Connecting to 10.194.51.41:3128 (10.194.51.41:3128)
gsm_ac_gp_fd_pu_em_c 100% |**************************************************************************************************|  5419k 00:00:00 ETA
root@om-gta02:~# echo 0 >/sys/bus/platform/devices/neo1973-pm-gsm.0/power_on
root@om-gta02:~# echo 1 >/sys/bus/platform/devices/neo1973-pm-gsm.0/power_on
root@om-gta02:~# cd /usr/sbin
root@om-gta02:/usr/sbin# FLUID_PORT=/dev/ttySAC0 fluid.exe -oo -b 115200 -f $HOME/gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-moko10.m0
FLUID Revision 2.27, (23 Aug 2004). Copyright Texas Instruments, 2001-2004.
Reading image file: '/home/root/gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-moko10.m0' (2138kB) ok
Bootloader: (reset target) (ROM, version ?) ok
Checksumming (269 * 8kB = 2152kB):  ok
Flash Detect: (0xEC, 0x22A0) Samsung K5A3240CT ok
Program: (31 sectors, 243*8k=1944k) (******************) ok
root@om-gta02:/usr/sbin# 

And to wake up the GSM in another ssh window :

root@om-gta02:~# echo 0 >/sys/bus/platform/devices/neo1973-pm-gsm.0/power_on
root@om-gta02:~# echo 1 >/sys/bus/platform/devices/neo1973-pm-gsm.0/power_on



i recive instead of

"Program: (34 sectors, 267*8k=2136k) (*******************) ok"

this

"Program: (0 sectors, 0*8k=0k) () ok"

iam currently reflashing the old firmware, that seems to work.

iam using an non-us gsm-freerunner (recived yesterday so most likely the latest hardwar)

thakoman


[2008-11-19 04:46:39] <Wonka> DocScrutinizer: flashing to moko10-beta2 went though cleanly, i already had working ppp connects with the previously non-working SIM.

[2008-11-19 04:48:24] <Wonka> DocScrutinizer: but there are still problems... more often than not, the GSM chip does not answer. pppd opens the device, gets "AT command interpreter ready", utters "AT\n" and gets nothing. power off, power on, reset on, reset off, try gain... sometimes it works, but mostly not.


O2 UK prepay 3G SIM works with moko10-beta2, was previously not detected. T-mobile UK prepay SIM and old Orange UK contract SIM work with both old and new. Testing so far is cursory at best, but looks good. [quote: Alastair Johnson on devel-ML]

[2008-11-21] I flashed 6 out of our 8 Freerunner V.6 according to the GSM/Flashing- guide. I had no problems and the previously useless 3G- SIMs are working fine now. It seems like the 3G- SIM Issue, our beloved #666, is solved. You should point it out clearly. I heard a lot of users complain about this. The solution is simple and well hidden on the website. By the way, i have new 3G- SIM cards of the following german providers running without problems (O2, T- Mobile, E-Plus, Vodafone). Before the flashing procedure the Vodafone cards were not detected. Good work guys... thanks! Reiner

Works now with new gsm firmware moko10beta2 with O2 in Germany

Very great, I can make calls now after waiting for 5 month, big surprise :). Thanks a lot! --Kevin 15:18, 20 November 2008 (UTC)


I'm very happy to be able to report that the update went smoothly for me (without yielding any surplus "building materials") and that a new O2 SIM from http://freesim.o2.co.uk/ which never worked in my Freerunner before now seems to be working fine. Great work!

Tom

--

Thomas White Department of Materials Science and Metallurgy Electron Microscopy Group (PhD Student) University of Cambridge / Downing College




The flash worked without a hitch for me and now I am able to use a Vodafone prepaid SIM in my 850MHz unit while back in Europe. I am running Om2008.9 with the 20081023 FDOM modifications applied.

Great job!

-Jacob




Hello!

Replying under subject Success :) I've combined what Michael said (few echo 1 >> .... and echo 0 >> .... in the other terminal) and Joerg's suggestion (-oo instead of -oO) and it worked perfectly. The upgrade to moko10 was done.

So I can confirm the freerunner now works with Simobil's (Slovenian GSM operator) SIM.

Great job and thanks to all that took the time to do it.

Boštjan

State SD-image?

Any update on a SD-image for GSM flashing?


[joerg 2008-12-10 02:43:32]

We're busy on this. Follow wiki instructions, or come up with an automatism by yourself. Expect any update on january.

microSD size issue 4Gb KO, 1Gb Ok

I use a usd 4Gb that boots well with Qi, but don't with NOR, this kind of usd can't be used then for flashing. I nevertheless did the test and i confirm that it worked only when i used a smaller 1Gb usd.

[Philippelhardy 2009-06_27]

bug #1024

[Tebra 2009-01-13 07:45]

Hi. Are you working on moko11 to fix #1024 bug? Because of that bug I can't use android distribution.

German/Vodafone

Got a new Vodafone Prepaid SIM-Card. Didn't work with QTExtended nor with Android until I've used the procedure to upgrade the GSM-Firmware. Looks like it's not just "swiss sim cards". Regards, --Rtreffer 17:14, 25 January 2009 (UTC)

Broken GTA01bv4 GSM Modem Fix

I recently had to do a special process to recover my GTA01bv4 after breaking the gsm modem with a failed flash. The process is actually fairly simple.

  • Unplug USB and remove the battery for about 10s to ensure that the GSM chipset is powered off, then replace the battery and re-connect the USB
  • boot up from a distro that is neutered so that it does not access or turn on the gsm modem at all
  • issue this stty command twice:
 stty 0:4:18b2:8a00:0:0:7f:15:4:0:0:0:0:0:0:0:12:f:17:16:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0 -F /dev/ttySAC0
  • issue this fluid command:
 FLUID_PORT=/dev/ttySAC0 fluid.exe -oo -od13,13 -vvv -b115200 -f $HOME/filename.m0
  • in another ssh session, issue this command:
 echo 1 > /sys/bus/platform/devices/neo1973-pm-gsm.0/power_on

After this, the flashing proceeded as expected, and all seems alright. I'll have to push a new distro to it to be certain, but all looks good so far. Quinn Storm 22:39, 16 March 2009 (UTC)

Added note about battery removal. Mmontour 01:51, 17 March 2009 (UTC)

Flash using uSD card image worked!

I'm now able to use my "MobilePlus" (Mobistar network) SIM which failed to register previously. Thanks for this excellent tool!

--M8ram 15:16, 26 April 2009 (UTC)

Successful update here. Didn't fix unregistering SIM card under Android. I'll test few more things. --Mikeful 22:06, 18 June 2009 (UTC)

What is FLUID?

Please create a link to an explanation of what FLUID is when FLUID is first mentioned at the top of the page.

The name of the page

The name of this page is GSM/Flashing, which may be confused with Flashing_the_Neo_FreeRunner ? You could call it Firmware/Flashing (which breaks a lot of links .. and you need a stub.. )

--pike 00:07, 18 May 2009 (UTC)

Remove uSD - optional ?

At the bottom of par.3, it reads

>>You may can now remove bat and uSD

.. ("may"/"can") - "if you want to". I don't see a reason why you should ?

I did notice I couldn't get into the NoR menu without twiddling around with battery and sim; but not sure what was going on there.

--pike 00:07, 18 May 2009 (UTC)

===== Visibility of the final Messagge "D_O_N_E" =====

At the end of flashing process the final message "D_O_N_E" in green over black, it's not so readable. In general if yous see a green messagge, also if you cannot read it well, you can safely reboot, the Flashing process it's done. --Apertum 13:18, 18 May 2009 (UTC)

See http://pike.kw.nl/files/documents/pike/personal/photoos/2009/20090518/DSCN0644.JPG : i guess 'D_O_N_E' is more appropriately described 'when the console turns green'. --Pike 13:18, 18 May 2009 (UTC)

That's been the rationale of doing it this way ;-) /jOERG

Suggestion for uSD Instruction Steps

On the second step of the uSD Installation procedure with dd command, i suggest to add this text:

Before proceding make sure that the uSD memory is NOT already formatted. With simple GUI like Gparted o QParted, you can unmount the right uSD partitions, and remove all the partition to have a simple uSD not formatted (the right formatted partition will be automatically transferred with the next 'dd' image transfer command).

Because i've seen that if i have an already Ext2/3 formatted uSD (or any other partition), the 'dd' Command it's not working tranferring the image.--Apertum 21:03, 18 May 2009 (UTC)

The original istructions to dd to physical device will overwrite whatever filesystem may have been on uSD, incl. partition-table/MBR. If dd is not working, you encounter some different problem, maybe caused by not correctly unmounting all partitions, or by a typo in dd. The instructions cover these cases as well.

-- jOERG 2009-05-19 00:05

Suggestion: Add a big Note Sticky at the beginning of the page to avoid editing the page

Suggestion: add a very big Note Sticky at the beginning of the page to avoid editing the page by the community.

The beginnig phrase: "This is NO communtity driven page, please be reluctant and careful with edits. Thanks " must be a lot bigger to avoid errors, IMHO.--Apertum 21:11, 18 May 2009 (UTC)

--- seems there's no way to place a warning big enough for everybody anywhere on the page. Probably will lock eventually.

-- jOERG 2009-05-19 00:05

You can add a simple:

WARNING: This is NO communtity driven page, please be reluctant and careful with edits. Thanks


It's a lot more visibile and clear, IMHO. Anyway a lock it's safer, of course. --Apertum 22:34, 18 May 2009 (UTC)

Using scp from desktop

I don't have a card reader so I tried the scp command suggested. However, at the end it returns

scp: /dev/mmcblk0: truncate: Invalid argument

ALternatively, I mounted the desktop PC folder with the image using nfs and dd from there. -- User:fmartins 2009-08-15

I'm quite sure you're using a wrong command, what's your input?

usage of scp: scp IP:path_to_orig_file IP:path_to_to_dest_file

Dareus


Hi! I got the same error, this is what I did:

$ scp flash-moko11-2.image root@192.168.0.202:/dev/mmcblk0
root@192.168.0.202's password: 
flash-moko11-2.image                                    100%  270MB 293.2KB/s   15:43
scp: /dev/mmcblk0: truncate: Invalid argument
$

GTA02 now running MOKO11, but still having problems with SIMs

I updated my GTA02 to MOKO11, but 2 of my 3 SIM's (All from same carrier) still doesn't work.

SIM 1 works fine, with PIN and everything.
SIM 2 get's full GSM signal, but tells me "SOS Only" PIN Disabled
SIM 3 doesn't recieve a GSM signal at all, and GSM modem won't turm on. PIN Disabled.

All 3 SIMs works fine in my Nokia and HP phones.

I have tried with SHR and Android distros, but it's the same result.

Is there a MOKO12 on the way??