MMS and o2 - problems copying Mms.apk

[Guest ali40]

Hi,

Like many others I have been struggling to try and get MMS working for the Orange San Francisco on o2... I need to be able to receive MMS's (don't care about sending)

Phone is rooted with Androot (v.1.6.2 Beta 5). Using Stock Orange ROM.

Initially I tried to use handcent to spoof the phone type to o2 but the desired "Custom User Agent" is not in the menu.

Next I thought about copying the modified Mms.apk file (which gives options for various other phone types) so I downloaded a terminal and also the mount system app to make system r/w. I want to do this locally on the phone rather than installing the SDK and going the ADB route.

Flow used:-

- Run the mount system app to allow RW in system folder

- Change to supervisor mode with "su"

- Change to system/aps and chmod the Mms.apk to rw

- rename Mms.apk to Mms.apk.bak

So far so good... Next I wanted to copy the new Mms.apk from SD card into /system/app but discovered that the "cp" command seems to have been removed from San Francisco! I just get an error even when I type "cp" on it's own...

So - I then tried Astro but it doesn't let me copy the file. I am assuming it's not going in as root access as the files in the /app folder are shown as -r-

Kind of stumped! Any suggestions on how to copy a file from sdcard to system/app without ADB? I did see root ewxplorer in the apps store. Would this do the job?

Any other ideas?

Thanks,

Ali

[Guest feckineejit]

You could try android commander

[Guest cbrpaul]

i have been trying to to sort this out for ages , search under my name for my various posts here

I have got mms working o2 , but due to o2 ( and giffgaff, same company) donot recognise the blade you will receive mms at a default size of postage stamp , which is quite frankly usless !!!

I have tried all the Mms.apk ,using adb ( i work in IT ) and all sorts , but nope nothing works !!

Other android phones have had success by fooling the Useragent within the phone itself, , this is what tells o2 systems the type of phone you use, but as yet no-one can do it for the blade !! not sure why ???

oh we are not alone on this either !!

So good luck !!

Edited January 22, 2011 by cbrpaul

[Guest Phoenix Silver]

i have been trying to to sort this out for ages , search under my name for my various posts here

I have got mms working o2 , but due to o2 ( and giffgaff, same company) donot recognise the blade you will receive mms at a default size of postage stamp , which is quite frankly usless !!!

I have tried all the Mms.apk ,using adb ( i work in IT ) and all sorts , but nope nothing works !!

Other android phones have had success by fooling the Useragent within the phone itself, , this is what tells o2 systems the type of phone you use, but as yet no-one can do it for the blade !! not sure why ???

oh we are not alone on this either !!

So good luck !!

hummm is there nothing to edit in build.prop ?

[Guest cbrpaul]

hummm is there nothing to edit in build.prop ?

heres the file ,

What would be the suggested area to change ? and to what ?

I have highlighted what it could be in red below !!

# begin build properties

# autogenerated by buildinfo.sh

ro.build.id=ERE27

ro.build.display.id=Swedish Snow RLS1

ro.build.version.incremental=20101208.144833

ro.build.version.sdk=7

ro.build.version.codename=REL

ro.build.version.release=2.1-update1

ro.build.date=Wed Dec 8 14:50:08 CST 2010

ro.build.date.utc=xxxx

ro.build.type=user

ro.build.user=user

ro.build.host=localhost.localdomain

ro.build.tags=release-keys

ro.product.model=ZTE-BLADE

ro.product.brand=ZTE

ro.product.name=P729B_TSE

ro.product.device=blade

ro.product.board=blade

ro.product.cpu.abi=armeabi

ro.product.manufacturer=ZTE

ro.product.locale.language=en

ro.product.locale.region=GB

#ro.wifi.channels=14

ro.wifi.channels=

wifi.interface=wlan0

wifi.supplicant_scan_interval=15

#wlan.default.dns1=xxx

ro.board.platform=msm7k

# ro.build.product is obsolete; use ro.product.device

ro.build.product=blade

[u]# Do not try to parse ro.build.description or .fingerprint

ro.build.description=P729B_TSE-user 2.1-update1 ERE27 20101208.144833 release-keys

ro.build.fingerprint=ZTE/P729B_TSE/blade/blade:2.1-update1/ERE27/20101208.144833:user/release-keys

usb.default.pid=0x1354# end build properties

#

# system.prop for surf

#

ro.setupwizard.mode=OPTIONAL

ro.build.baseband_version=TSE_P729VB01

ro.build.sw_internal_version=TSE_P729VV1.0.0B05

ro.product.board_name=blade

rild.libpath=/system/lib/libril-qc-1.so

rild.libargs=-d /dev/smd0

persist.rild.nitz_plmn=

persist.rild.nitz_long_ons_0=

persist.rild.nitz_long_ons_1=

persist.rild.nitz_long_ons_2=

persist.rild.nitz_long_ons_3=

persist.rild.nitz_short_ons_0=

persist.rild.nitz_short_ons_1=

persist.rild.nitz_short_ons_2=

persist.rild.nitz_short_ons_3=

DEVICE_PROVISIONED=1

debug.sf.hw=1

dalvik.vm.heapsize=24m

ro.config.ringtone=Terminated.ogg

ro.config.notification_sound=F1_New_SMS.ogg

persist.sys.timezone=Europe/London

ro.camera.sound.forced=0

#

# ADDITIONAL_BUILD_PROPERTIES

#

ro.com.google.gmsversion=2.1_r12

ro.sf.lcd_density=240

qemu.sf.lcd_density=240

ro.com.google.clientidbase=android-zte

ro.com.google.clientidbase.yt=android-zte

ro.com.google.clientidbase.am=android-zte

ro.com.google.clientidbase.vs=android-zte

ro.com.google.clientidbase.gmm=android-zte

net.bt.name=Android

ro.config.sync=yes

dalvik.vm.stack-trace-file=/data/anr/traces.txt

[Guest cbrpaul]

ps on other android phones , the file is in another place !!

[Guest Phoenix Silver]

it's beyond my knowledge but i'm sure someone here know :lol:

i don't use mms i use only gmail

perhaps compare with a different model phone which work

ho and for the second question you can use astro manager (free on market) it does the job

[Guest cbrpaul]

i have started a new thread regarding where and how the file could be on the blade here

but im not confident that an answer will be found

http://android.modaco.com/content/zte-blad...f-small-mms-o2/

Edited January 22, 2011 by cbrpaul

[Guest ali40]

You could try android commander

Yeah I looked at that yesterday but's it's just an ADB front end (still need busybox etc on phone as far as I can tell)

From description:

Phone Requirements:

- ROOT (only for Applications Manager and flashing options)

- BusyBox (required only for rooted phones; included to most ROMs)

- Settings->Applications->Development->USB debuging must be enabled

- USB cable

PC Requirements:

- Windows

- Instaled Android SDK *

- Instaled ADB USB Driver from SDK

- SDK/Tools set in System Path (program can set it for You )

[Guest ali40]

So back to my original question - apart from ADB and root explorer, does anyone know of a way to copy files from SD card to phone

(Note that I am trying to copy the modified Mms.apk from here which allows phone spoofing to be selected)

Summary to date:

Phone is rooted / system priviledges set to R/W by "mount system" app

None of the 3rd party messaging apps seem to have the spoofing options enabled (Hanscent and one aother that I can't recall name of)

Astro cannot set correct RW priviledges to allow file to be copied from SD

cp command has been removed from O/S

Maybe I just have to buy root explorer but want to ensure it would do the job 1st! Pity there isn't a trial version.

Thanks.

Ps - should probably elaborate... I run Win7 64 bit which is a PITA for ADB. I am trying to avoid downloading the SDK (needed in Android Commander) as it seems to want the full version of JAVA which killed my PC last time I installed it!

Edited January 22, 2011 by ali40

[Guest Phoenix Silver]

i use root explorer and it does the job if you want to buy it

[Guest ali40]

i use root explorer and it does the job if you want to buy it

Ok thanks for confirmation.