418 replies to this topic

[chrisbeaumont]

ciwrl, on 17 January 2011 - 05:38 AM, said:

P.S RM version != CWM version

RM may indeed be 3.0.0.7; but you still need to get and apply the ClockworkMod (which btw, is the name of the recovery not the app) 3.x.

See the difference?



Here, ill help

http://postkreative....cwm-3.0.0.5.img

I feel like I'm being very stupid, but what do I do with this img file?  I've tried running it from file manager, but that doesn't work.  I don't know what to do with it

Thanks in advance.

[RD1945]

chrisbeaumont, on 18 January 2011 - 12:34 PM, said:

I feel like I'm being very stupid, but what do I do with this img file?  I've tried running it from file manager, but that doesn't work.  I don't know what to do with it

Thanks in advance.

you have to flash it with fastboot (fastboot flash recovery recovery.img).

[chrisbeaumont]

RD1945, on 18 January 2011 - 12:48 PM, said:

you have to flash it with fastboot (fastboot flash recovery recovery.img).

Thank you!

However, now having some other weirdness - when I try to fastboot flash recovery, i get the following error:

sudo ./fastboot-mac flash recovery recovery.img
sending 'recovery' (3982 KB)... OKAY
writing 'recovery'... FAILED (remote: not allowed)

I've got the phone connected in FASTBOOT USB bootloader mode, but it's still not working.

I also tried to flash the radio but got the same error:

sudo ./fastboot-mac flash radio radio.img 
sending 'radio' (24832 KB)... OKAY
writing 'radio'... FAILED (remote: not allowed)

Anybody got any idea what's going on?

EDIT: I should also say that i've already installed the latest CM7 nightly ROM using the incorrect version of ClockworkMod Recovery (2.5.1.3) - just in case that's got anything to do with this fastboot weirdness.

I've now gone back to my backed up 6.1.3 stable CM ROM, but wondered if installing CM7 using the wrong version of CMR might have caused something odd to happen to the bootloader that's causing this problem with fastboot.

Edited by chrisbeaumont, 18 January 2011 - 03:19 PM.

[PatricF]

chrisbeaumont, on 18 January 2011 - 02:54 PM, said:

Thank you!

However, now having some other weirdness - when I try to fastboot flash recovery, i get the following error:

sudo ./fastboot-mac flash recovery recovery.img
sending 'recovery' (3982 KB)... OKAY
writing 'recovery'... FAILED (remote: not allowed)

I've got the phone connected in FASTBOOT USB bootloader mode, but it's still not working.

I also tried to flash the radio but got the same error:

sudo ./fastboot-mac flash radio radio.img 
sending 'radio' (24832 KB)... OKAY
writing 'radio'... FAILED (remote: not allowed)

Anybody got any idea what's going on?

EDIT: I should also say that i've already installed the latest CM7 nightly ROM using the incorrect version of ClockworkMod Recovery (2.5.1.3) - just in case that's got anything to do with this fastboot weirdness.

I've now gone back to my backed up 6.1.3 stable CM ROM, but wondered if installing CM7 using the wrong version of CMR might have caused something odd to happen to the bootloader that's causing this problem with fastboot.

Did you boot into the bootloader when you tried to flash it?

[chrisbeaumont]

PatricF, on 18 January 2011 - 07:37 PM, said:

Did you boot into the bootloader when you tried to flash it?

Yep, had it in bootloader, ./fastboot devices reported the device a present.

[PatricF]

I just installed the latest nigthly and it looks like it works great except for one thing, the WiFi doesn't seem to work.
If I turn it on it will take a couple of seconds until it turns on but I can't see my network and then the WiFi will just turn it self off.

Anyone else have the same problem?

I updated the radio just before I installed CM7 so I never had a chance to test it out on CM6.1

EDIT:

This is what I get:

01-18 22:11:10.159: ERROR/WifiHW(1315): Unable to open connection to supplicant on "eth0": No such file or directory
01-18 22:11:10.239: INFO/GPSButton(1511): Update State
01-18 22:11:10.279: DEBUG/WifiService(1315): acquireWifiLockLocked: WifiLock{NetworkLocationProvider type=2 binder=android.os.BinderProxy@408e42a0}
01-18 22:11:10.319: DEBUG/WifiStateTracker(1315): Reset connections and stopping DHCP
01-18 22:11:10.419: DEBUG/SettingsAppWidgetProvider(1799): Call buildUpdate for widget:14
01-18 22:11:10.449: DEBUG/SettingsAppWidgetProvider(1799): buildUpdate done for widget:14
01-18 22:11:11.321: INFO/wpa_supplicant(5748): CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00
01-18 22:11:11.329: DEBUG/WifiStateTracker(1315): Disabling interface
01-18 22:11:11.349: INFO//system/bin/wpa_supplicant(5746): l2_packet_receive - recvfrom: Network is down
01-18 22:11:11.809: INFO/wpa_supplicant(5748): CTRL-EVENT-STATE-CHANGE id=-1 state=1 BSSID=00:00:00:00:00:00
01-18 22:11:15.166: ERROR/WifiHW(1315): Unable to open connection to supplicant on "eth0": No such file or directory
01-18 22:11:15.369: DEBUG/WifiService(1315): releaseWifiLockLocked: WifiLock{NetworkLocationProvider type=2 binder=android.os.BinderProxy@408e42a0}
01-18 22:11:20.163: ERROR/WifiHW(1315): Unable to open connection to supplicant on "eth0": No such file or directory
01-18 22:11:24.039: INFO/WindowManager(1315): Setting rotation to 3, animFlags=0
01-18 22:11:24.059: INFO/ActivityManager(1315): Config changed: { scale=1.0 imsi=240/8 loc=en_US touch=3 keys=1/1/2 nav=1/1 orien=2 layout=34 uiMode=17 seq=28}
01-18 22:11:24.179: INFO/GPSButton(1511): Update State
01-18 22:11:24.279: INFO/dalvikvm(5530): Jit: resizing JitTable from 4096 to 8192
01-18 22:11:24.689: INFO/WindowManager(1315): Setting rotation to 0, animFlags=0
01-18 22:11:24.689: INFO/ActivityManager(1315): Config changed: { scale=1.0 imsi=240/8 loc=en_US touch=3 keys=1/1/2 nav=1/1 orien=1 layout=34 uiMode=17 seq=29}
01-18 22:11:24.779: INFO/GPSButton(1511): Update State
01-18 22:11:25.168: ERROR/WifiHW(1315): Unable to open connection to supplicant on "eth0": No such file or directory
01-18 22:11:25.168: VERBOSE/WifiStateTracker(1315): Supplicant died unexpectedly
01-18 22:11:25.168: DEBUG/WifiStateTracker(1315): Reset connections and stopping DHCP
01-18 22:11:26.169: DEBUG/WifiStateTracker(1315): Disabling interface
01-18 22:11:26.169: INFO/wpa_supplicant(5748): CTRL-EVENT-TERMINATING - signal 15 received
01-18 22:11:26.169: INFO/wpa_supplicant(5748): CTRL-EVENT-TERMINATING - signal 0 received
01-18 22:11:26.169: INFO/wpa_supplicant(5748): CTRL-EVENT-STATE-CHANGE id=-1 state=0 BSSID=00:00:00:00:00:00
01-18 22:11:26.179: INFO/GPSButton(1511): Update State
01-18 22:11:26.179: DEBUG/WifiStateTracker(1315): Reset connections and stopping DHCP
01-18 22:11:26.319: DEBUG/SettingsAppWidgetProvider(1799): Call buildUpdate for widget:14
01-18 22:11:26.329: DEBUG/SettingsAppWidgetProvider(1799): buildUpdate done for widget:14
01-18 22:11:27.039: DEBUG/dalvikvm(1315): GC_EXPLICIT freed 678K, 53% free 6119K/12871K, external 6173K/7709K, paused 196ms
01-18 22:11:27.200: DEBUG/WifiStateTracker(1315): Disabling interface
01-18 22:11:27.209: ERROR/Tethering(1315): attempting to remove unknown iface (eth0), ignoring
01-18 22:11:27.739: INFO/GPSButton(1511): Update State
01-18 22:11:27.952: DEBUG/SettingsAppWidgetProvider(1799): Call buildUpdate for widget:14
01-18 22:11:27.979: DEBUG/SettingsAppWidgetProvider(1799): buildUpdate done for widget:14

I guess

01-18 22:11:10.159: ERROR/WifiHW(1315): Unable to open connection to supplicant on "eth0": No such file or directory

has something to do with it, it can't seem to find the WiFi-interface..


EDIT2:

# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue 
	link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
	inet 127.0.0.1/8 scope host lo
	inet6 ::1/128 scope host 
	   valid_lft forever preferred_lft forever
2: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop 
	link/ether fa:a5:bf:9e:fb:05 brd ff:ff:ff:ff:ff:ff
3: rmnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
	link/ether 72:ca:a0:52:33:85 brd ff:ff:ff:ff:ff:ff
	inet 79.102.215.38/30 brd 79.102.215.39 scope global rmnet0
	inet6 fe80::70ca:a0ff:fe52:3385/64 scope link 
	   valid_lft forever preferred_lft forever
4: rmnet1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
	link/ether 8e:d1:a3:02:48:63 brd ff:ff:ff:ff:ff:ff
5: rmnet2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
	link/ether 12:be:66:e5:f8:95 brd ff:ff:ff:ff:ff:ff
6: usb0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
	link/ether be:80:5d:9c:dc:44 brd ff:ff:ff:ff:ff:ff
7: sit0: <NOARP> mtu 1480 qdisc noop 
	link/sit 0.0.0.0 brd 0.0.0.0
8: ip6tnl0: <NOARP> mtu 1460 qdisc noop 
	link/tunnel6 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 brd 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00

[chrisbeaumont]

chrisbeaumont, on 18 January 2011 - 08:49 PM, said:

Yep, had it in bootloader, ./fastboot devices reported the device a present.

Sorted this - I used this method to install 3.0.0.5 http://forum.xda-dev...ad.php?t=900460

[chrisbeaumont]

PatricF, on 18 January 2011 - 08:52 PM, said:

I just installed the latest nigthly and it looks like it works great except for one thing, the WiFi doesn't seem to work.
If I turn it on it will take a couple of seconds until it turns on but I can't see my network and then the WiFi will just turn it self off.

Anyone else have the same problem?

I have the same problem - WiFi turns on, won't recognise any networks, then after a few seconds it turns itself off.

[chrisbeaumont]

Another minor thing - when I open up the gallery, the 'loading new albums' overlay notice appears, but then never disappears, even when leaving gallery.  Stays there regardless, can't figure out how to get rid of it apart from rebooting.

[El Nino]

PatricF, on 18 January 2011 - 07:37 PM, said:

Did you boot into the bootloader when you tried to flash it?

should ask the user if they have the engineering bootloader or are they s-off?

anyways my question, what am i doing wrong :S
it just doesn't boot CM at all. constantly stuck on htc white screen when ever i try install gingerbread roms. i mean it just stays there for an hour until i pull the battery out.

steps i take:

1)transfer rom onto SD CARD, safely remove after completion on the computer then remove from the phone.
2) adb reboot bootloader
3) as you need to do a full wipe and i am radio s-off and have engineering spl i do, fastboot erase system -w and also fastboot erase boot
4)flash new CWM 3.0.xx
5)navigate to recovery from the phone
6)install rom
7)reboot and run adb logcat

so why have i never been able to run gingerbread?just always freezes
i followed instructions of kali

ok update:

i did the exact same thing on which i've been trying 28 times before this. and it works. yes 28 tries to get it to work i love it tho LOL

Edited by El Nino, 19 January 2011 - 12:12 AM.

[PatricF]

chrisbeaumont, on 18 January 2011 - 09:46 PM, said:

I have the same problem - WiFi turns on, won't recognise any networks, then after a few seconds it turns itself off.

It's fixed in build #5 so it works now

[sfixic]

chrisbeaumont, on 18 January 2011 - 12:34 PM, said:

I feel like I'm being very stupid, but what do I do with this img file?  I've tried running it from file manager, but that doesn't work.  I don't know what to do with it

Thanks in advance.

There's also another way to do it. Put the cwm recovery image in the sdcard root folder.
Enter the terminal then write

Su
flash_image recovery /sdcard/filename.img

Then reboot, start rom manager, then reboot into recovery and you'r all set.

Edited by sfixic, 19 January 2011 - 08:47 AM.

[PatricF]

sfixic, on 19 January 2011 - 08:46 AM, said:

There's also another way to do it. Put the cwm recovery image in the sdcard root folder.
Enter the terminal then write

Su
flash_image recovery /sdcard/filename.img

Then reboot, start rom manager, then reboot into recovery and you'r all set.

Cool, I didn't know you could do that from the phone, thanks for the tip!

[chrisbeaumont]

PatricF, on 19 January 2011 - 07:07 AM, said:

It's fixed in build #5 so it works now

Wunderbar - all working for me now also.

[downloaderen]

What radio is best...by the way i love the cm7 everything works perfekt...

[joshua03]

Hallo,

with nightly #5 I have an Proximity sensor issue. During a call the display turns off und doesn't wake up anymore.
So, I have to take off the battery to make an restart.

[AdrianM]

downloaderen, on 19 January 2011 - 11:24 AM, said:

What radio is best...by the way i love the cm7 everything works perfekt...

I'm using Radio_12.28e.60.140f_26.04.02.17_M2_SF ,  and I have great battery life, and no problem. (i haven't tested gps)

Edited by MafiotuL, 19 January 2011 - 12:40 PM.

[joshua03]

MafiotuL, on 19 January 2011 - 12:40 PM, said:

I'm using Radio_12.28e.60.140f_26.04.02.17_M2_SF ,  and I have great battery life, and no problem. (i haven't tested gps)

I can confirm this. It's working perfectly.
GPS is also working.

Edited by joshua03, 19 January 2011 - 12:51 PM.

[PatricF]

joshua03, on 19 January 2011 - 12:50 PM, said:

I can confirm this. It's working perfect.

Same here, been using it for a while now and it works great.

joshua03, on 19 January 2011 - 12:39 PM, said:

Hallo,

with nightly #5 I have an Proximity sensor issue. During a call the display turns off und doesn't wake up anymore.
So, I have to take off the battery to make an restart.

I'm running build #5 and I don't have any problem with the proximity sensor at all.

[joshua03]

PatricF, on 19 January 2011 - 12:53 PM, said:

Same here, been using it for a while now and it works great.



I'm running build #5 and I don't have any problem with the proximity sensor at all.

I think, your DHD is an new generation model.
  
My DHD is an first generation model (October 2010) and had this problem from beginning, until the issue was fixed with ROM 1.32.405.6.

And now with the CM7 ROMs this issue again.