Database Develop

Native IM application working with 3G + patch for GTalk losing messages [Feb 03 2010]

I was bothered by the fact that Google Talk didn't show some of the messages I received. Johan de Koning submitted a patch that wasn't accepted by Google but works well. I applied this patch for personal use, but I thought that you might be interested as well.
Also, I had a look at the IM application and I modified it to allow login instead of having the "phone number cannot be read from your SIM" error. This might or might not work. It works for me, but users in the US have reported that it still fails.
UPDATE 16th Jun 2010:
Added version 1.1.2 from Cliq.
UPDATE 3rd Feb 2010:
New eclair version for IM.apk, completely untested. Might or might not work.
Patched ImProvider is no longer useful for Android versions >= 2.
Also, I removed the cupcake IM.apk because I just noticed it is broken and won't work. No-one should be still running a rooted cupcake anyway.
Notes
This is for donut. I tested it on cm 4.2.2 and 4.3.2.1, but it should work with any donut rom. As far as I know, it doesn't use sms at all. It still needs the tmo plugins to login, but no sms are sent. Other than that, it does exactly the same as when you login on wifi.
Installation
Some of these steps will fail depending on the rom (the dalvik-cache and odex part). These errors can be safely ignored.
First reboot into recovery, then, on your computer :
Code:
adb shell
mount /system
mount /sdcard
cp /system/app/IM.apk /sdcard/IM.apk
cp /system/app/ImProvider.apk /sdcard/ImProvider.apk
exit
adb push ImProvider.zip /system/app/ImProvider.apk
adb push IM.zip /system/app/IM.apk
adb shell
mount /system/sd
rm /system/sd/dalvik-cache/*
rm /system/app/ImProvider.odex
rm /system/app/IM.odex
umount /system/sd
umount /system
umount /sdcard
reboot
Of course, I'm not responsible if anything breaks.
More information about the sources is available in this post.

which roms are these for? cupcake? donut? hero? haha. i pushed them to my hero rom and they do not show up in my app tray or in applicantion manager.

Tested them on cm 4.2.2 and it works. Does this use ip traffic or sms?

ok cool, probably for donut. i tried on Hero cupcake and it fails, just keep getting ForceCloses. owell, i dont use it anyways but just thought it be fun =)

Bavilo said:
Tested them on cm 4.2.2 and it works. Does this use ip traffic or sms?
Click to expand...
Click to collapse
You can try removing TmoImPlugin.apk and see if it still works.
edit:
I asked him in another thread earlier and this is his response
Zappletoo said:
Data only hopefully.. I've not been charged for any sms so far.
Click to expand...
Click to collapse
I'm going to push it into Cyan's build and remove TmoImPlugin.apk and see if it still works.

Well, it doesn't work without tmoimplugin, and with that, I know it uses sms.

Sorry for the lack of details.. I updated the first post to make it clearer. It doesn't send sms afaik, becaus my plan doesn't have unlimited sms and I wasn't charged for any sms since I patched the IM app.
Also, this is for donut only, because the IM subsystem changed a bit since cupcake.

can you somehow modify im.apk so that it would stay in memory?

seems to work fine *tries out this im comparison to ebuddy, seems much faster ^^*
not sure if it uses sms, but dont think so.. ah well got unlimited anyway ^^

Do you have the source patches for these?

I'd like to have more feedback.. Does it work properly for everyone ? Any bugs or FC ?
cyanogen said:
Do you have the source patches for these?
Click to expand...
Click to collapse
The patch from ImProvider is here : http://code.google.com/p/cyanogenmod/issues/detail?id=597
but I couldn't recompile it from source without breaking everything.. I had to patch the apk directly. Maybe you'll do better.
The patch for the IM application is attached, the edited file is in packages/apps/IM/src/com/android/im/service
DOHCtor said:
can you somehow modify im.apk so that it would stay in memory?
Click to expand...
Click to collapse
I don't know how to do that, sorry. But it seems the app already stays in memory for a while. Are you sure it doesn't stay already, if it's not killed by an application manager ?

Sorry if I'm being a noob, but how exactly does one install this? I did
adb push /path/IM.apk /system/app
adb push /path/ImProvider.apk /system/app
and rebooted, and I still get SIM card cannot be read errors. I feel like I'm probably missing a step like installing.

enderx1 said:
Sorry if I'm being a noob, but how exactly does one install this? I did
adb push /path/IM.apk /system/app
adb push /path/ImProvider.apk /system/app
and rebooted, and I still get SIM card cannot be read errors. I feel like I'm probably missing a step like installing.
Click to expand...
Click to collapse
Yea, same here. I guess it doesn't work for users in the States. However, it does work on wifi but once I turn off wifi, it disconnects.

Try installing it from recovery if you didn't, and clear dalvik cache (rm /system/sd/dalvik-cache/* on cm with apps2sd, not sure about others).

i'm tryin using it on CM ROM 4.0.4 but when i try push it, i can't use the IM, is there anyone already can used that IM in CM ROM 4.0.4 ?? thanks before

I hate when my messages are loosed, and run loose around the intarwebs.
Additionally, I don't like to be LOSING messages. =9

Thanks! Works perfect on enomther 2.1.1

kamikaze2311 said:
i'm tryin using it on CM ROM 4.0.4 but when i try push it, i can't use the IM, is there anyone already can used that IM in CM ROM 4.0.4 ?? thanks before
Click to expand...
Click to collapse
It doesn't work on cupcake, donut only (cm >= 4.2).
danguyf said:
I hate when my messages are loosed, and run loose around the intarwebs.
Additionally, I don't like to be LOSING messages. =9
Click to expand...
Click to collapse
You can never have enough o's.

Did anyone else lose use of the market doing this?

ZeroGDarius said:
Did anyone else lose use of the market doing this?
Click to expand...
Click to collapse
Are you sure this is related ? I don't really see how the IM application could affect the market..

OPEN VPN

Has anyone managed to get Open VPN working on a Galaxy S? I have a SPICA on which it is working but I cant find a TUN.KO that works on the Galaxy S. Thanks

Also trying to find a proper TUN.KO for the Galaxy S.
No luck so far.

Read here: http://android.modaco.com/content-page/291919/openvpn-on-android/page/20/

None of the methods described for other phones worked for Samsung Galaxy S. I tried with several tun.ko and all where giving me "format errors" as the kernel was not matching.
Last resort, I compile it myself from Samsung I9000 kernel sources.
Tested it and worked. I know have OpenVPN in Galaxy S (I9000)!
I attach the tun.ko file. I hope other guys out there with I9000 can use it.

Excellent. Will give it a go. Which ROM are you running?

I'm currently running I9000BGF1, I will be soon upgrading to new Firmware.
Kernel Version: 2.6.29 [email protected] #2

Hi Chafw,
Can you talk me through where you put the tun.ko, and where you put your OpenVPN files in the directories? I'm getting no where fast on this!
Thanks
SA

Hi mittu1,
I believe you are already root and busybox/openvpn installed.
I used the same link that tids2k wrote above to setup the whole thing up.
I used openvpn-settings application for starting up openvpn configurations.
In openvpn-settings you can define where the tun.ko driver is located.
Anyway, the simplest thing to do firdst to test whether the tun.ko works for you is to
load it by hand using a root shell:
insmod <path to tun.ko>
I have it installed in /system/lib/modules/tun.ko.
Hope this helps.

The tun.ko is ok, it loads nicely. Many many many thanks !!!
In the "OpenVpn Settings" app, my connection ask me for a password, I see "auth", then nothing, I fall back in front of the "select to turn on OpenVPN tunnel" button.
I have tried with stock libcrypto.so and libssl.so, and then with those from openvpn-binary.zip at hxxp://sourceforge.net/projects/tunneldroid/files/
The OpenVPN app still don't want to establish the connection... In no ways... And no log message in dmesg at all (neither for tun)
So it's enough for this night, but if someone have an idea, you are (really) welcome !!!

Does the module have to match the kernel version exactly? Running european JM2,
kernel is 2.6.29 [email protected]3#2
PS. 1st Post

Do you copy tun.ko in the /lib/modules folder ? or in a new freshly created folder /system/lib/modules (as said on modaco guide) ?
On my system (XXJF3 / XXJF3 / XAJF3), I have no /system/lib/modules folder, and every time a mount in rw my /, then write tun.ko to /lib/modules, then remount in readonly, and then reboot the phone, the tun.ko file disappear...
Do I miss something ? Does the / mount point isn't a real partition ???
thnks in advance

@ Anduru:
No, don't think that is necessary but I'm also quite new to Android.
@raphman:
I created a new folder /system/lib/modules. I didn't have the directory either.
Anyway the OpenVpn-settings applications allow to define the location of the tun.ko. Haven't tried but I believe you could put it anywhere in the system.
Also, make sure the ifconfig and route commands are available and properly linked.

@chafw
thanks for your reply
meanwhile i just tried my luck and it worked.

Guys,
I'm glad it's working but I haven't managed it yet!!
I'm using the I9000XWJM2 rom, rooted! I've downloaded the tun.ko file, the open VPN Setting file off the market, and Open VPN installer. I've got the certs and config files.
Can some one please guide me through installation to get it up and running OR did people use the following link instructions
http://android.modaco.com/content/software/291919/openvpn-on-android/
Would really appreciate someone's help here.

Chaf, many thanks, but in fact, my installation was ok, it was a password problem... Arrrrgggggg !!!!!!!
So now I connect fine to my OpenVpn server, but I cannot reach any server withour using the "Fix DNS" problem.... Strange, because using the connection on my pc automacillay get the DNS given by the vpn....
Many thanks !!!

@raphman:
The DNS is a known issue in Android as OpenVPN uses update-resolv
hook scripts to update the resolv.conf configuration with the passed DNS parameters.
However, this does not work yet with in Android and Openvpn-settings.
You can either use fix-dns or add your hosts in the /etc/hosts file if they are
a limited number.
@mittu1:
Yes, that's the guide.

liblzo
I have got to the stage where my openvpn connection is started but no traffic is being passed through the tunnel. Checking around it seems that I am missing the liblzo.so file that handles compression. Can any of you guys post a working liblzo.so or confirm that your configuration does/doesn't use this file? Thanks.

mittu1 said:
I have got to the stage where my openvpn connection is started but no traffic is being passed through the tunnel. Checking around it seems that I am missing the liblzo.so file that handles compression. Can any of you guys post a working liblzo.so or confirm that your configuration does/doesn't use this file? Thanks.
Click to expand...
Click to collapse
take it here and 1st step is SAVE your old files somewhere !!!
hxxp://sourceforge.net/projects/tunneldroid/files/openvpn-binary.zip/download
then cp in /system/lib and chmod 755. That's ok on my i9000.

hi,
It didn't work! Still same problem. Any other suggestions?

chafw said:
None of the methods described for other phones worked for Samsung Galaxy S. I tried with several tun.ko and all where giving me "format errors" as the kernel was not matching.
Last resort, I compile it myself from Samsung I9000 kernel sources.
Tested it and worked. I know have OpenVPN in Galaxy S (I9000)!
I attach the tun.ko file. I hope other guys out there with I9000 can use it.
Click to expand...
Click to collapse
I tried the tun.ko and it works! Unfortunately my (Endian) firewall can only use a tap device, and apparently both ends have to match. I get the connection, but the the device and IP are never setup. Any chance you can either compile the tap device like you did the tun, or give me the steps so I can do it myself ?

[FIX] For 2.2 Market issues, use this mod - *Updated* with Stock Build.prop

For those of you having trouble seeing protected apps, I modified our fingerprint in the build.prop. What this does is spoofs the market into thinking its seeing a Droid 2 (with Froyo) It worked for me, let me know if it does for you.
1. Put build.prop into your AndroidSDK\TOOLS folder
2. Connect via USB.
3. CD (Navigate) in CMD to your tools folder
Mount your /system (adb remount) works for me
Copy and paste this
4. adb remount
5. adb push build.prop /system/build.prop
6. adb reboot
To test if you need this before you push the build.prop fix, search the market for Us Bank. If only 2 or 3 show up, you are not getting the full market. After this fix, you should see 10 items listed when you search for Us Bank.
Hope this helps.
2.2 Market Fix Build.Prop -- WITH STAGEFRIGHT=TRUE
This can also be done via Root Explorer.
Edit: Here is a "clean" build.prop for those of you who do not want the stagefright fix (which breaks video playback) Sorry, I was not aware it did that. Thank you.
Non Stagefright Build.prop -- WITH STAGEFRIGHT=FALSE
For everyone flipping out about Birdmans tweet and you want the stock build.prop, here ya go
Stock Build.prop -- WITH NOTHING! STOCK!
You only need the stock one if you ever plan on doing a factory reset. But, you also cant do a factory reset if you have removed or renamed apps so I feel that should be mentioned. If you've done any modding and you are planning on upgrading, your best bet is to always use the SBF anyway. I dont think birdman realizes the panic he sets in with one little tweet. Factory resets suck anyway. But then again... "you decide..."
Thanks to Jcase for giving me the original idea way back when. I just basically applied his Eris Market Fix to work with our phones.

This created several problems for me.
First, the build.prop file is a read-only system file and doing a push did not work for me.
I had to copy it to my sdcard and then in shell:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/build.prop /system/build.prop
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
This created some really fubar'd effects on my network as I couldn't access the market from 3g. It more or less disabled my 3g network.
When I activated wi-fi, it worked fine, and did let me into the market.
I'm trying to put my original build.prop file back on, but I still have no 3g connectivity.
Update:
restored my build.prop and still no go.
update2:
tried clearing the 'cache' from reboot mode and even did a factory reset ... still no go.
I'm starting over with SBF, update, FROYO, etc.
I don't know for certain that this file hosed me, but I had not yet done any other system file issues. Either way, I would not recommend you follow my above instructions

Found a fix
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.

Zaphod-Beeblebrox said:
This created several problems for me.
First, the build.prop file is a read-only system file and doing a push did not work for me.
I had to copy it to my sdcard and then in shell:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/build.prop /system/build.prop
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
This created some really fubar'd effects on my network as I couldn't access the market from 3g. It more or less disabled my 3g network.
When I activated wi-fi, it worked fine, and did let me into the market.
I'm trying to put my original build.prop file back on, but I still have no 3g connectivity.
Update:
restored my build.prop and still no go.
update2:
tried clearing the 'cache' from reboot mode and even did a factory reset ... still no go.
I'm starting over with SBF, update, FROYO, etc.
I don't know for certain that this file hosed me, but I had not yet done any other system file issues. Either way, I would not recommend you follow my above instructions
Click to expand...
Click to collapse
Firstly, I figured ppl would know how to use adb.
if you cant push the file, use "adb remount" and it will work.
Secondly,
Hmm... Sorry to hear that but I HIGHLY doubt it was the build.prop that did this.
I posted over at another thread, and it worked for everyone.
Check it.
http://www.droidxforums.com/forum/droid-x-hacks/4318-2-2-market-issues-use-mod.html

elkniwcire said:
i must say i take no responsibility if this causes problems but this worked for me. Do a search in the market for "eris market fix." it was designed for the eris but works just fine on my droid x. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but i assume most everyone on froyo already is rooted.
Click to expand...
Click to collapse
yes this worked for me aswell thank you

Yes this method definitely works. I have market working now and can search for protected apps etc.

elkniwcire said:
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Click to expand...
Click to collapse
I would not recommend this. I have talked to 2 people so far who said their phone have gone in to bootloops using the Eris Market Fix. After all, it is for an Eris. Read the comments on the app in market. Lots of people are using it on the wrong phone and having problems.
Do yourself a favor and just use the build.prop in this post as it has already been tested in numerous forums with no problems whatsoever, if done correctly.

he was just explaining where the idea comes from i think... You'd have to be crazy to use the eris market fix app on a droidx, just simply edit the build.prop fingerprint line.

I just used the root explorer meathod and now it wont boot.
I downloaded the file.
renamed my build.prob to build.prob/bak
placed the new build.prob in the system folder
rebooted and now after the M screen it just goes to a black screen with the backlight lit. Wont boot up. Im learning adb so this may be a noob question but can I access adb if the phone wont boot all the way up. That way I could change the build.prob back
Edit Delete Post: Im just retarted haha .prop not .prob :/

Could you plz give us some details on doing this with root explorer. Thanks
Prolly simple but I did try moving current build file then renaming and pasting yours without success doing us bank search. Also rebooted cleared cache and market history prior to search. Appreciate any help with doing this via root explorer.

LexusBrian400 said:
Firstly, I figured ppl would know how to use adb.
if you cant push the file, use "adb remount" and it will work.
Secondly,
Hmm... Sorry to hear that but I HIGHLY doubt it was the build.prop that did this.
I posted over at another thread, and it worked for everyone.
Check it.
http://www.droidxforums.com/forum/droid-x-hacks/4318-2-2-market-issues-use-mod.html
Click to expand...
Click to collapse
LexusBrian400 said:
I would not recommend this. I have talked to 2 people so far who said their phone have gone in to bootloops using the Eris Market Fix. After all, it is for an Eris. Read the comments on the app in market. Lots of people are using it on the wrong phone and having problems.
Do yourself a favor and just use the build.prop in this post as it has already been tested in numerous forums with no problems whatsoever, if done correctly.
Click to expand...
Click to collapse
I took a brief look at each file and I really don't understand how I got into trouble. As I said, I had not yet started doing any mods, just trying to install a few apps.
While I'm no computer or phone neophyte, I don't profess to be up to speed on Android yet. I do typically read through instructions pretty well, and search out multiple sources/explanations so I have a better 'understanding' of what I'm doing, rather than just "parrotting" the steps.
Having said that, I would like to know the difference between using 'adb remount' and the instructions I used in my first post. Is that just the difference in doing this via a shell command and not? ie, they perform the same action, just from a different starting point?
As for the Eris file, I did download that and all seems to be OK right now.

Sorry ahead of time for a possibly stupid question but I just wanted to be sure. Do you have to be rooted to do this fix?

Yes, it requires an edit to a file that you can only be edited when rooted

elkniwcire said:
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Click to expand...
Click to collapse
This works for me...thanks!

OP has been updated with original build.prop

Silly question but is the Non Stagefright file edit like the first one so the Market is fixed if you use either of the first 2 posted files. I realize the last file is just the stock build.prop but am a little confused on wah tis in the first 2 files. Obviously the first fixes the Market issue, so I guess I'm more question wha tis in the non stagefright file. TIA for any help/input

will2live said:
Silly question but is the Non Stagefright file edit like the first one so the Market is fixed if you use either of the first 2 posted files. I realize the last file is just the stock build.prop but am a little confused on wah tis in the first 2 files. Obviously the first fixes the Market issue, so I guess I'm more question wha tis in the non stagefright file. TIA for any help/input
Click to expand...
Click to collapse
Just use the non-stagefright one.
Just like the post says, stagefright breaks HD video playback for SOME people. However some people dont care and just want higher quadrant scores, so they use the stagefright=true build.prop
Use the =false version for better stability.

Thanks for the reply.

2.2.1 Update error

hey boys
so I finally gave it and did the whole adb rooting thing... lots of command lines and so on but finally it works so I got rid of Universal Androot..
so now my problem is still there though...
I run the update.zip and I get this:
assert failed: apply_patch_check(“system/app/GenieWidget.apk”,”(insert tons of digits here″,”(insert tons of digits here)″)
“E: Error /sdcard/update.zip
(Status 7)
Installation aborted.”
Anybody got a solution?
My phone and its changes:
Stock Nexus One 2.2
Rooted word-per-word via http://forum.xda-developers.com/showthread.php?t=736271
Uninstalled Amazon MP3 and "News & Weather" (genie widget?)
I figure maybe reinstalling News & Weather would fix it ... but Titanium backup does not recover it even if I did back it up first... (useless??)
I downloaded the APK and instaled it, but still the same thing.
What else what else...
thanks

I'm only posting this here because I, too, have an error and am in no way trying to thread-jack. I got the 2.2.1 OTA the other day and went ahead to update. Unfortunately, I use AndRoot also and when I got halfway through the OTA, I got an error during installation. I pulled the battery, rebooted, and I was still 2.2 rooted. I unrooted with AndRoot and now seemingly have no way of acquiring the update OTA. Any advice, OP?

OTA seems absolutely random to me ... so I would download the update (found in this very forum) and rename it to update.zip and put it in the root of your sd card and run the update as prescribed on many sites...
as for my problem... damnit damnit damnit is all I can say. I know 2.2.1 is generally useless, but I want to be sure I can install Gingerbread when it comes out!!

damn so I tried 2 different versions of GenieWidget installations (it's news and weather)
seems I get the same error everytime.
I know the "simplest" thing is to run a full reinstall of my phone (recover console?) but I don't want to redo all my apps/settings... can't there be a way to recover 1 or 2 components only? in this case, amazon mp3 and geniewidget, just so that the 2.2.1 update works...?

I had the same issue with com.amazon.mp3.apk not being found (I remember deleting it as soon as I got root)... well I had to put it back under /system/app/ (meaning you can't do it via the market - only manually)
Note: the exact version that was shipped with froyo has to be installed. You can check that you have the right apk by computing its sha1 sum (that's the second "insert tons of digits here" MitchRapp refers to)

*UPDATE*
oh snap.
my friend has the same nexus one as me ... so I copied his GenieWidget.apk and .odex into my /system/app and so far so good... i got another error (com.amazon.mp3) so I'm going to copy that too
update to follow...

hey it worked!
after a (seemingly) endless "X" animation bootup... 2.2.1 is there.
now I lost the root access I just made with adb shell something something.... that's normal I guess, so I'll redo it

Uh oh, I removed amazon mp3 too...;(

toss the .apk back in /system/app and reboot and update... it worked!
now for re-rooting... that wont work damnit.
I'm doing the rageagainstthecage thing word-for-word and the thing is, when I try
./busybox cp busybox etc...
it says file already exists
and the chmod commands only give me a "read-only" error
cuz I already rooted earlier using the .freenexus style .......
what can I do for this?

Anyone happen to have the2.2 Amazon apk and willing to share?
Sent from my Nexus One using XDA App

I do, what's your email
anyone know how to re-root 2.2.1 using the rageagainstthecage without it telling me everytime that busybox file exists and is in read-only... i followed the steps to the letter...

bennettm89 said:
Anyone happen to have the2.2 Amazon apk and willing to share?
Click to expand...
Click to collapse
Sure.
sha1sum is c3b285c13db4b7f8fcfb72372d77b388157bf6cd

MitchRapp said:
I do, what's your email
anyone know how to re-root 2.2.1 using the rageagainstthecage without it telling me everytime that busybox file exists and is in read-only... i followed the steps to the letter...
Click to expand...
Click to collapse
I used superboot (1.1-FRF91-nexusone-superboot) - worked like a charm.

I had an issue with settings.apk , had used universal androot and metamorph to make changes to the battery meter.
After getting the ota , the installation was aborted due to changes in settings.apk . i downgraded to android 2.1 erd79 ( had the passimg.zip file from few months ago).
Once downgraded never got OTA for further updates ( eg ere27 , frf91 etc).
had to manually update to frg83.

Jony, Thank you.
OP, thank you anyway, I got it from Jony. Now to find the update.zip...

God bless it. Went to go install from SD, I don't have twitter. I hate twitter. Anyone have it...

MitchRapp said:
anyone know how to re-root 2.2.1 using the rageagainstthecage without it telling me everytime that busybox file exists and is in read-only... i followed the steps to the letter...
Click to expand...
Click to collapse
The rageagainstthecage step-by-step is missing a couple steps that will cause it to give the errors you're seeing. I ran into this and posted the solution, with follow-up and confirmation by others, later in the thread. Check out
http://forum.xda-developers.com/showthread.php?t=792016
In a nutshell, the /system partition needs to be mounted for both read and write in order to set permissions on the Superuser.apk and su files. Also, if you already were rooted and have Superuser.apk, su, and busybox installed, you don't have to copy them back to the phone--you can just set the permissions on the existing files.

Ohhhh jony! Can you post the twitter APK pl0x

bennettm89 said:
Now to find the update.zip...
Click to expand...
Click to collapse
There it is: http :// android.clients.google.com/packages/passion/signed-passion-FRG83-from-FRF91.c8847c98.zip
bennettm89 said:
Ohhhh jony! Can you post the twitter APK pl0x
Click to expand...
Click to collapse
Hre you go - sha1sum is 2acade940a14e65abcb93ff7fc68b0a95b733113

jony22 said:
There it is: http :// android.clients.google.com/packages/passion/signed-passion-FRG83-from-FRF91.c8847c98.zip
Hre you go - sha1sum is 2acade940a14e65abcb93ff7fc68b0a95b733113
Click to expand...
Click to collapse
Thanks buddy, I appreciate it.
I'm not really happy with the update. Lost root ( I knew I would ) but the most upsetting thing is that I removed my work email from my phone. I had to update security settings to authorize the remote administration of my device through my exchange server at our HQ which is not happening. I know it doesn't have to be done but I was getting increasingly angry just looking at it in the notification bar 24/7.

Anolog clock resets o reboot

Hi all,
Was not really sure where to put this apologies if its the wrong place.
I recently created my own analog clock, I'm using CM7 RC0, I simply replaced the clock background .png in the original desktopclock.apk, renamed it, signed it and then installed it through filemanager.
Now, it works fine! I was very happy, until I rebooted my phone today, got back onto the desktop and it had reset to the original anolog clock! Tried it again and sure enough everytime I reboot I have to reinstall the .apk!
Anybody have any idea why on earth this would happen?
Many thanks,
Sean

This was originally brought to my attention with the HTC_IME mod by Jonasl. I installed a themed version over the top of the one already installed by default in /system/app and on reboot the original (quite frankly ugly) keyboard was back...
for some reason I do not know, you have to manually un-install the previous version. Don't know why...
use this http://forum.xda-developers.com/showthread.php?t=644909
to un-install the original apk for the clock, then push your app into /system/app using adb. reboot and it should all be sorted... I hope.

Great stuff, thank you for your help. Now I wonder how to do this using linux, I will look into it, at least I know what the problem is

wiiija said:
Great stuff, thank you for your help. Now I wonder how to do this using linux, I will look into it, at least I know what the problem is
Click to expand...
Click to collapse
I'm on linux right now, and I did this to remove my stock messaging app not 3 hours ago...
Just open up your terminal and use adb, assuming you have the androidsdk on your computer...
If you don't it's going to be a little harder, you're going to have to find a root exploring file manager and delete the analog clock app from /system/app and then you're going to have to put the new one there AFTER rebooting.
If you want adb just ask and I'll tell you how to get it.
1. download the android sdk from http://dl.google.com/android/android-sdk_r12-linux_x86.tgz
2. open up the .tgz and extract it to /home/-your_user_name/androidsdk
3. open up terminal and type
su
PATH=$PATH:/home/-your_user_name/androidsdk/tools
adb
adb devices <-------(make sure your device is connected and in debug mode. If that fails just boot into recovery)
qiuness said:
adb shell
su
cd /system/app
mount -o rw,remount /system
rm -r analogclock.apk
Click to expand...
Click to collapse
4. install your new, themed app
abd push /path/to/your/app.apk /system/app
5. reboot.

Brilliant guys thank you very much, its all sorted, easy once you know how