How can I remove WaveSecurity in MCR R5

[Guest BlackWhite]

I follow this instruction but failed,

http://android.modaco.com/content/htc-desi...adb-in-windows/

when I try to mount /system

adb shell mount /system

I got

mount: can't read /etc/fstab: No such file or directory

when list software it's much different with instruction

adb shell ls /system/app

[0;0mAccountSyncManager.apk[0m [0;0mLauncher2.apk[0m

[0;0mAccountSyncManager.odex[0m [0;0mLauncher2.odex[0m

[0;0mAppSharing.apk[0m [0;0mLiveWallpapers.apk[0m

[0;0mAppSharing.odex[0m [0;0mLiveWallpapers.odex[0m

[0;0mApplicationsProvider.apk[0m [0;0mLiveWallpapersPicker.apk[0m

[0;0mApplicationsProvider.odex[0m [0;0mLiveWallpapersPicker.odex[0

m

[0;0mBluetooth.apk[0m [0;0mMagicSmokeWallpapers.apk[0m

...

just past a part.

what's wrong and how to remove software in ROM?

[Guest gandalfmuaddib]

when list software it's much different with instruction

adb shell ls /system/app

[0;0mAccountSyncManager.apk[0m [0;0mLauncher2.apk[0m

[0;0mAccountSyncManager.odex[0m [0;0mLauncher2.odex[0m

[0;0mAppSharing.apk[0m [0;0mLiveWallpapers.apk[0m

[0;0mAppSharing.odex[0m [0;0mLiveWallpapers.odex[0m

[0;0mApplicationsProvider.apk[0m [0;0mLiveWallpapersPicker.apk[0m

[0;0mApplicationsProvider.odex[0m [0;0mLiveWallpapersPicker.odex[0

m

[0;0mBluetooth.apk[0m [0;0mMagicSmokeWallpapers.apk[0m

...

just past a part.

what's wrong and how to remove software in ROM?

Looks like you're trying to remove the files when the phone is power on normally. Are you doing this in recovery?

[Guest PaulW21781]

Download the update.zip file which they supply

http://www.wavesecure.com/installations/update.zip

Then just apply the update like you would any other ROM/patch/etc etc (just make sure to rename it from update.zip to something like WaveSecure.zip before you copy it to your SDCard otherwise if you are using FakeFlash, you will overwrite it!)

[Guest BlackWhite]

Looks like you're trying to remove the files when the phone is power on normally. Are you doing this in recovery?

yes, that's the point.

thanks a lot.

1. First get into recovery mode with the Green menu then close that command prompt and open a new one and cd to /r4-desire-root folder

[Guest ManOfSteal]

I'm having a problem removing it myself. I'd done it once before using adb commands, but after going from MCR r3.1 to r6 (with a wipe), nothing now happens after going into recovery mode and then plugging in the PC via USB. I'm getting a response that a device is detected, but nothing else seems to work as expected. I'm probably missing something really obvious here... :(

Before when I used it, I could go back to the menu, but it now just freezes on the phone with the red triangle image, the only way to reboot is to remove the battery :(

[Guest BlackWhite]

I'm having a problem removing it myself. I'd done it once before using adb commands, but after going from MCR r3.1 to r6 (with a wipe), nothing now happens after going into recovery mode and then plugging in the PC via USB. I'm getting a response that a device is detected, but nothing else seems to work as expected. I'm probably missing something really obvious here... :(

Before when I used it, I could go back to the menu, but it now just freezes on the phone with the red triangle image, the only way to reboot is to remove the battery :(

I am using ClockWorkMod included in unrevoked3 recovery reflash tool,

that's no problem,

are there anything wrong with the driver of your phone?

[Guest ManOfSteal]

are there anything wrong with the driver of your phone?

Firstly, oops, a typo on my part, I'm using MCR r5 :(

The PC driver for HTC Sync you mean? Not to my knowledge.

[Guest ManOfSteal]

To explain more, this is the response I get:

C:\Program Files\android-sdk-windows\tools>adb shell

- exec '/system/bin/sh' failed: No such file or directory (2) -

An old XDA post explains: "This means that in your recovery image, even though you might have installed busybox, the symlink to it is missing (/system/bin/sh should be either bash or a symlink to your busybox binary)" :(

[Guest Morsdyce]

To explain more, this is the response I get:

C:\Program Files\android-sdk-windows\tools>adb shell

- exec '/system/bin/sh' failed: No such file or directory (2) -

An old XDA post explains: "This means that in your recovery image, even though you might have installed busybox, the symlink to it is missing (/system/bin/sh should be either bash or a symlink to your busybox binary)" :(

I had that problem too, although it worked itself out when i connected my desire (powered on) and tried accessing adb shell while the desire screen is on.

I then received a super user request i allowed it and everything worked out fine after.

[Guest ManOfSteal]

Thanks, that didn't seem to change anything for me (it was working as expected with ADB commands when powered on as normal). On my third attempt today however it finally worked, even though I'm sure I did nothing different to previously :(