Re: Help with locked phone
On Monday 22 August 2011 16:04:59 Dan Rossi wrote: > sudo flasher -F ARM.bin -f -R > flasher 3.11.5 (May 17 2011) Harmattan > > USB device found at bus 253, device address 4. > Device serial number is > Sending request 0x01 failed: Operation timed out > NOLO_REQ_GET_STATUS: Operation timed out > ERROR: Device status query failed The USB connectivity can be pretty unreliable. Some suggestions: Unplug all other USB stuff, and plug the N900 cable directly into the PC, without a hub in the way. If you are using windows (I know you aren't from your command line, but...), reboot (without the N900 connected), and try the process again. If you can, try a different PC -- the reliability is very different on my different PCs. If you can, try a different OS (windows vs. linux). Try slight differences in the process (which order you plug things in, when you start flasher, etc). Persevere -- in my experience you will get it to work eventually. Graham ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Re: Help with locked phone
On Mon, Aug 22, 2011 at 10:04 AM, Dan Rossi wrote: > Hi, this is my first post here, so bare with me. I'm a bit saddened by the > unmaintained state of the maemo operating system after for so long being > excited about a real linux phone. I am asking for help in regards to > reflashing > the firmware to get back into a "locked" phone. My girlfriend accidently hit > the > "lock screen and keys" button instead of the offline mode button which is > insanely placed between the secure device and lock screen and keys buttons. > This is a really bad place to be putting this for starters. The default lock > code > 12345 does not work so we're stuck for solutions. I've done the same thing, and I agree about the placement. Luckily I never changed my code away from the default. Just for encouragement: flashing should let you into the phone again. It doesn't reset the code, but once you're back into your device, you can try to recover the lock code using this program: http://talk.maemo.org/showthread.php?t=37808 > Trying to reflash the phone I get this error > > sudo flasher -F ARM.bin -f -R > flasher 3.11.5 (May 17 2011) Harmattan > > USB device found at bus 253, device address 4. > Device serial number is > Sending request 0x01 failed: Operation timed out > NOLO_REQ_GET_STATUS: Operation timed out > ERROR: Device status query failed > > I press the U button while plugging in the usb cable. > > Any ideas ? It looks like you're doing everything correctly. Be sure to run flasher before plugging in the N900. It will wait for you to plug it in. Normally, when everything is working, pressing U is not necessary, as N900 will detect flasher's commands and just start going. (Pressing U certainly doesn't hurt, though.) You might try enabling or disabling R&D mode with the flasher, and then trying to flash again after that. I've read reports in the past where people having flashing trouble were able to get it going again after issuing those commands. There is also the "cold flashing" technique, to replace the boot loader. (I have not personally tried it.) http://wiki.maemo.org/Updating_the_firmware/Cold_Flashing Good luck! ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Help with locked phone
Hi, this is my first post here, so bare with me. I'm a bit saddened by the unmaintained state of the maemo operating system after for so long being excited about a real linux phone. I am asking for help in regards to reflashing the firmware to get back into a "locked" phone. My girlfriend accidently hit the "lock screen and keys" button instead of the offline mode button which is insanely placed between the secure device and lock screen and keys buttons. This is a really bad place to be putting this for starters. The default lock code 12345 does not work so we're stuck for solutions. Trying to reflash the phone I get this error sudo flasher -F ARM.bin -f -R flasher 3.11.5 (May 17 2011) Harmattan USB device found at bus 253, device address 4. Device serial number is Sending request 0x01 failed: Operation timed out NOLO_REQ_GET_STATUS: Operation timed out ERROR: Device status query failed I press the U button while plugging in the usb cable. Any ideas ? If we can't get in, we might have to get a new phone possibly an android phone instead and recycle it because its useless right now. Let me know thanks. Daniel ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Re: Meego Summer Release
On Mon, 2011-08-22 at 16:28 +0200, Andre Klapper wrote: > On Wed, 2011-06-22 at 09:06 -0300, João Olavo Baião de Vasconcelos > wrote: > > Does anyone know whether the Meego Summer Release [1] (released today) > > Rather: released seven weeks ago. Oops, next time I should check first the date of emails before answering them. Sorry. :) andre -- Andre Klapper (maemo.org bugmaster | MeeGo QA) http://blogs.gnome.org/aklapper/ | http://www.openismus.com ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Re: Meego Summer Release
On Wed, 2011-06-22 at 09:06 -0300, João Olavo Baião de Vasconcelos wrote: > Does anyone know whether the Meego Summer Release [1] (released today) Rather: released seven weeks ago. > has the same user interface that is showed on N9? "MeeGo CE" (which is the summer release) is fully open-source. "MeeGo 1.2 Harmattan" on the N9 is not. So there are differences. > What about the same apps and features? There are differences. andre -- Andre Klapper (maemo.org bugmaster | MeeGo QA) http://blogs.gnome.org/aklapper/ | http://www.openismus.com ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
n900: usb keyb and h-e-n
Hi, I can't get my Lenovo SK8855 usb keybd working on my n900. http://www.notebookreview.com/default.asp?newsID=5387 I have such usb usb connector http://www.dealextreme.com/p/usb-cable-coupler-extension-connector-2646 Then I start h-e-n First message: 'stopping BME' Then I choose: > low speed hostmode >VBUS boost on > enumerate >> connect usb-keybd to n900 > mount But nothing is happening ... when I try to type in a xterm. I can't turn on Capslock. Also mouse does nothing. When I connect and mount a usb stick, it says 'unable to connect, no file system available' System information, see below. Thanks in advance! Dirk [code] sudo fdisk-l (in ubuntu) Device Boot Start End Blocks Id System /dev/sdb1 1 449 3606561b W95 FAT32 /dev/sdb2 450 487 305235b W95 FAT32[/code] [code]# apt-cache policy kernel-power-bootimg kernel-power-bootimg: Installed: 1:2.6.28-10power47 # apt-cache policy kernel-power kernel-power: Installed: 1:2.6.28-10power47 # apt-cache policy hostmode-gui hostmode-gui: Installed: 0.3 [/code] [code]# lsusb -v Bus 001 Device 001: ID 1d6b:0002 Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 0 Full speed hub bMaxPacketSize064 idVendor 0x1d6b idProduct 0x0002 bcdDevice2.06 iManufacturer 3 Linux 2.6.28.10-power47 musb-hcd iProduct2 MUSB HDRC host driver iSerial 1 musb_hdrc bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 12 Hub Descriptor: bLength 9 bDescriptorType 41 nNbrPorts 1 wHubCharacteristic 0x0011 Per-port power switching No overcurrent protection bPwrOn2PwrGood5 * 2 milli seconds bHubContrCurrent 0 milli Ampere DeviceRemovable0x02 PortPwrCtrlMask0xff Hub Port Status: Port 1: 0002.0301 C_ENABLE lowspeed power connect Device Status: 0x0003 Self Powered Remote Wakeup Enabled[/code] [code]# dmesg mBi, 2300 mBm) [ 1194.606079] (5735000 KHz - 5835000 KHz @ 4 KHz), (600 mBi, 3000 mBm) [ 1195.821289] wl1251: down [ 1199.649200] wl1251: 151 tx blocks at 0x3b788, 35 rx blocks at 0x3a780 [ 1199.664825] wl1251: firmware booted (Rev 4.0.4.3.7) [ 1199.725463] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 1200.317230] wlan0: authenticate with AP 00:23:69:15:11:c7 [ 1200.320617] wlan0: authenticated [ 1200.320678] wlan0: associate with AP 00:23:69:15:11:c7 [ 1200.324340] wlan0: RX AssocResp from 00:23:69:15:11:c7 (capab=0x411 status=0 aid=2) [ 1200.324371] wlan0: associated [ 1200.376251] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 1210.813354] wlan0: no IPv6 routers present [ 1626.887573] twl4030_usb twl4030_usb: HW_CONDITIONS 0xd0/208; link 2 [ 1627.426116] Forced hostmode error: no device attached [ 1627.426208] usb usb1: usb resume [ 1627.446166] hub 1-0:1.0: hub_resume [ 1627.446228] hub 1-0:1.0: port 1: status 0301 change 0001 [ 1627.555389] hub 1-0:1.0: state 7 ports 1 chg 0002 evt [ 1627.555450] hub 1-0:1.0: port 1, status 0301, change , 1.5 Mb/s [ 1627.680450] usb 1-1: new low speed USB device using musb_hdrc and address 18 [ 1632.672790] twl4030_usb twl4030_usb: HW_CONDITIONS 0x50/80; link 1 [ 1632.680419] usb 1-1: khubd timed out on ep0in len=0/64 [ 1637.680419] usb 1-1: khubd timed out on ep0in len=0/64 [ 1642.680328] usb 1-1: khubd timed out on ep0in len=0/64 [ 1642.805358] usb 1-1: device descriptor read/64, error -110 [ 1647.914916] usb 1-1: khubd timed out on ep0in len=0/64 [ 1652.914764] usb 1-1: khubd timed out on ep0in len=0/64 [ 1657.914794] usb 1-1: khubd timed out on ep0in len=0/64 [ 1658.039886] usb 1-1: device descriptor read/64, error -110 [ 1658.274261] usb 1-1: new low speed USB device using musb_hdrc and address 19 [ 1663.274169] usb 1-1:
