Database Info

Deleted some Google Talk files on rooted G1 and messed it up!

I want to start off by first appologizing for posting this in the wrong area (if I did), as I understand it's important to place the post in as specific as a topic as possible.
Two days ago I went in and deleted a few .apk files that had to do with GTalk, not realizing all those apps talk to each other to do certain tasks. I have not been able to download from the market OR sign into Google Talk since.
I found a forum last night where somebody had the exact same problem. Some guy posted a link to the files to put back on the phone. But since I can't download apps, I can't get a file manager to install the .apk files I downloaded onto my PC. I've tried using SDK and it is SUPER confusing. Please help as I am so frusterated I want to cry and pull my hair out.
Thanks in advance.
I am using a windows 7 laptop
Rooted G1 with CyanogenMod

adb is not difficult, if you are rooted would be more simpler.
try this
http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=783901

Sorry for bringing back an old thread, but I have ran into a similar problem on a US a854 milestone, I just recovered my phone from a bad experience trying to flash to 2.2, anyway i rooted again this evening and used root explorer to delete bloatware, unfortunately i uninstalled gtalk(google talk) and now I cant download from market. I need to find a way to get gtalk back. I do not have a back up and if someone can tell me how to create a nandroid back up I would be greatly appreciative, but I need to get gtalk back first
thanks in advance
JB
UPDATE, I found some talk.apk files on this forum and got me squared away.....for the record there here http://forum.xda-developers.com/showthread.php?t=773272

uwlopservice ?

seems to be always running, process is com.sonyericsson.signatureapps.components
what is this and how could it be removed, could it be safely removed?

http://ccalonnec.fr/wiki/index.php?title=SE_Xperia_X10_:_list_of_default_apps_and_how_to_remove_them

Hey XperiaX10iUser,
Like your work. Helped me go from first time AT&T smartphone user 3 weeks ago, to unbranded-rooted 2.1 X10 A, now with sdk and adb capabilities. Still confused as @#$%, but learning more each day. This list is for 1.6, but updated in November...can it be used for 2.1?

agentJBM said:
Hey XperiaX10iUser,
Like your work. Helped me go from first time AT&T smartphone user 3 weeks ago, to unbranded-rooted 2.1 X10 A, now with sdk and adb capabilities. Still confused as @#$%, but learning more each day. This list is for 1.6, but updated in November...can it be used for 2.1?
Click to expand...
Click to collapse
Hi.
Glad to have helped. I would say so, it would obviously be better if it covered 2.1 but the descriptions of what does what and if it can be removed should apply to both. I'm still learning too btw, there's a lot happening for the X10 right now so it's opened up a whole new World so to speak.

I wanted to try and use Droid Explorer and abd method for my first time(thanks to ABD for Noobs). Once I got all the sdk tools saved and DE recognized my phone, I did a > select all > copy > paste > of my entire internal drive including sdcard and made a copy in a new folder on my desktop. It seemed to copy all the files, but when I accidentally deleted some of the 2.1 Sync apps and part of Goggle .gapps (I don't remember the entire file names) and went to use abd to push an app back on to the phone I opened the file it was completely empty. What did I do wrong? What folders of the drive do I need to copy and how do I save them, so I can use them individually to push apps back on the phone?
I had to to re-flash using SEUS to get a complete ROM. After I reflashed I realized the phone needed to be rooted in order to use Droid Explorer. Z4root was saved in my sd card, but was unable to figure out how to install them from my PC. I ended up setting up wifi and google account to use the Market to install a file explorer, and opened z4root that way. How do you install apks in a phone that has not been rooted from a computer?

[Q] late night phone spaghetti. x10 mini pro help please!

Hi everyone,
I'm looking for some pointers on the path to 2.1 on my x10 Mini Pro, and hoping the wealth of knowledge between you all can set some things straight for me?
I'll apologise in advance if I ramble at all or don't make much sense... I've been browsing forums for hours and am suffering from mild cross-eyedness and slight brainfreeze.
The scenario;
I have an x10 mini pro, running 1.6, on Vodafone UK. Yes, the ONLY network that have not yet provided the 2.1 update for x10mp users. The phone was rooted with universal androot and also had astro file manager and titanium installed. For about three months I have had the 'starting download' hang problem in Market which I have not been able to fix. I hadn't really wasted much time on it as it was of little importance at the time however I now want to update some things and can't. Today I got annoyed and did a factory reset, hoping to resolve the problem. It didn't, and now I have a blank canvas of a phone.
I didn't back up before doing the reset as call logs and txts are of less importance that the files on my sd card, which remain untouched. I don't really have any other 'important' stuff on the phone right now.
I realised shortly after that I had a backup from December which I ran, as a last ditch attempt, this did not restore my lost applications, but did restore some user data. I noted that my root privileges and titanium were gone too
B*gger it, I thought, since I've lost all my data I may as well go for a generic NON-Vodafone installation of Android 2.1, and hopefully that will also fix the Market issue.
I've had a look on forums here and would like to run the 2.0.2.a.0.24 firmware posted by shivenjuneja.
I've downloaded this via pc, and understand I need to also install the flashtool and xrecovery, both of which I have downloaded and saved in a folder on my laptop.
Now remember, market was not an option so I've downloaded universal androot via pc too and have saved this to the root of the SD card.
With my primitive blank phone, I am unable to browse to it without a file manager, so now I need to download Astro File Manager again.
I decide to have a probably fruitless attempt of doing this via the market (because saving it on the SD card is pointless as I need it installed in order to browse to it!) and much to my amazement, it's worked!! Woohoo Market is working again! But hell, I've still lost everything on my phone so I'll perservere with my android update, thank you very much.
Ok, now while waiting for Astro to download, I remember that I've also read on the forum that the upgrade to 2.1 is likely to be stuck in a booting loop if I upgrade with user data on the phone. If I do a factory restore I will lose my file manager and root privileges that I will shortly be installing, right?
So now, at this hour, I'm wondering exactly what order I need to do everything in to get 2.1 on my phone.
To install 2.1 I need to install the flash tool and xrecovery. To install those I need root, to root I need Astro and before doing any of this I need a phone that has no user data on it.
D4mn you Vodafone.
Could anyone advise the best method to do all of the above i.e in what order to do it all, or point out if there is anything obvious I haven't accounted for.
I don't usually have a problem with this sort of thing, hopefully it will look clearer tomorrow!
Thanks in advance
K

Also, does registering your google login to use the Market count as 'user data' when you upgrade? I ask as I may need to download and install Astro again from the market, if it's still working after another reset?

A lot of view and no replies? I could really use your advice guys if anyone could oblige...
From further reading I understand that I need busybox to install xrecovery and that I also need to be on 2.1 054 as xrecovery won't install on 1.6?
Is this correct?
It sounded so simple initially to flash from 1.6 to the latest version of 2.1, whereas now I need this to install that, need to be on the later version to install the app I need to use to flash to the next version up, and have to have a bunch of other apps and tools installed in order to the able to run anything!
All I want is a rooted 2.1 with all the network and SE bundled crap removed, so I can start putting my phone back to how I bl00dy want it with the apps I choose!
I hate you Vodafone. IhateyouIhateyouIhaveyouIhateyou

[Q] "Lost root" after busybox upgrade - Cannot r/w to / !

[Hopefully I didn't miss this being covered somewhere else, as I am much the same as many of you and get beyond irritated with endless repeat questions. I searched using the best keywords I could think of for the issue, but to no avail. Apologies in advance if this has been covered!]
Alrighty. I've got a TF101, rooted it myself (thank you XDA), running 8.6.5.1.9 i believe, stock rom just with root. Used nvflash and Razorclaw. Worked like a charm.
It's been fine for the last 6 months, no issues. However, I decided to update busybox using its internal updater as I have before with no problems. I noticed I accidentally told it to install to /system/bin instead of /system/xbin, and the only reason I even knew about that was due to having to configure an app to find busybox in /xbin instead of /bin.
Now there's a problem. I can still access the internal virtual sd card, but that's about it. The device can't seem to read or write to the main directory (although it can deal with going DIRECTLY to /mnt/sdcard). Ghost commander can't view the main directory, but ESFile explorer _can_, although root browsing in ESFile Explorer is UNchecked. It shouldn't be able to do what it's doing, and it's only doing it in one of two apps.
As a result, I've got no access to any root apps obviousy, but the wifi is having issues as well, it tries connecting but it can't complete the connection.
I'm toying with just wiping and flashing a new rom entirely, but figured I'd ask before I jump in the deep end of things. I keep backups of stuff, but it's still such a pain in the ass reinstalling things.
Any suggestions? I have a feeling it's something "simple", a link file or ... something which linux gurus would know about and I would not, not being a guru or disciple myself.
Thanks in advance!

If only you have working CWM installed. You could just flash this Superuser3.0.7.

Ah, but the plot thickens. I had superuser on there. I even uninstalled and reinstalled it. No dice.
Update: I said fuggit and did a factory reset. However, my wifi is still not fully connecting to my network although it has no problem finding it. I don't have a recovery image on the external SD and unless i get the network working, will have to wait until tomorrow to get a working microsd->usb adapter to put it on there.
I CAN still get into CWM, thank god.
Current rom is stock 8.6.6.19
Razorclaw gives an error when trying to root.
Also, when trying to moust USB from the recovery menu. it fails, saying "E:unable to upen ums lunfile (no such file or directory).
I am hoping this will magically get fixed after re-installing stock from the SD card ... and that my device isn't somehow crippled.
Sorry for the massive details, but more data = better.

It will magically get fixed
I recommend you flash any Totally stock ota. Then upgrade to the latest OTA, then use my tool PERI (or another) to install recovery and root. Then you should be all fixed up.

Well, it looks like I did get things back on track, but oddly enough, neither of the standard OR modified for root stock ROMs would work. One just wouldn't install, another failed halfway through. MD5s checked out and everything. I had put Revolver 4 beta on there sort of as a "just in case", and that one installed fine (and I was pleased when it displayed "installing Busybox symlinks").
Phew. CLose close call. Now to deal with the bull**** of setting stuff back up again.
However, the question remains: I'm assuming this whole thing happened because of the busybox update and me accidentally installing it to /bin instead of /xbin, and I think it "cleaned up" its own symlinks or something.
I'm not saying don't update your busybox, although I'm sticking with what works and **** upgrading anymore, just be careful...
Thanks for the help!

Recently I used the busybox installer to update my busybox version and it went through great... but after reboot it reverted back to the old version.. And I never touch it since.. don't want to take the hassle further..

There are certain 'plague' versions of busybox that simply don't work. I'd find that list of working BBs and STICK with one that's good. I'm still on 1.63 or someat like that.

Mangraa said:
[Hopefully I didn't miss this being covered somewhere else, as I am much the same as many of you and get beyond irritated with endless repeat questions. I searched using the best keywords I could think of for the issue, but to no avail. Apologies in advance if this has been covered!]
Alrighty. I've got a TF101, rooted it myself (thank you XDA), running 8.6.5.1.9 i believe, stock rom just with root. Used nvflash and Razorclaw. Worked like a charm.
It's been fine for the last 6 months, no issues. However, I decided to update busybox using its internal updater as I have before with no problems. I noticed I accidentally told it to install to /system/bin instead of /system/xbin, and the only reason I even knew about that was due to having to configure an app to find busybox in /xbin instead of /bin.
Now there's a problem. I can still access the internal virtual sd card, but that's about it. The device can't seem to read or write to the main directory (although it can deal with going DIRECTLY to /mnt/sdcard). Ghost commander can't view the main directory, but ESFile explorer _can_, although root browsing in ESFile Explorer is UNchecked. It shouldn't be able to do what it's doing, and it's only doing it in one of two apps.
As a result, I've got no access to any root apps obviousy, but the wifi is having issues as well, it tries connecting but it can't complete the connection.
I'm toying with just wiping and flashing a new rom entirely, but figured I'd ask before I jump in the deep end of things. I keep backups of stuff, but it's still such a pain in the ass reinstalling things.
Any suggestions? I have a feeling it's something "simple", a link file or ... something which linux gurus would know about and I would not, not being a guru or disciple myself.
Thanks in advance!
Click to expand...
Click to collapse
You may have been hit with a bug I introduced.
There was a bug with version 8.0 of my application.
There is not an issue with Busybox V1.20.1.
I apologize for this bug, the application symlinked all applets to Busybox and on some devices there are applets which are unique to the device and should not be replaced by those offered by Busybox.
A simple way to fix this is to simply reflash your rom. You do not need to wipe or clear any data. This will fix the issue and you can update Busybox normally with my application as long as it is version 8.1 or higher.
I apologize for the frustration I have caused, please let me know if I can do anything to help you further. I am trying to find people who were affected to see if I can help rectify the situation.

yeah me too
I guess I should have done a more recent backup. I tell you, there is a reason i have 38 updates waiting, everytime I start going through them, boom blows up in my face

[Q] Sidekick 4G Woes

Argh! Pulling my hair out over this one. I've been flashing custom ROMs and rooting my phones for years now, since my old HTC G1. Even had KitKat running on my HTC Desire 4G!
... but this Sidekick is proving another matter. I've been through forum after forum, all saying the same things on how to root/flash this thing, but I haven't managed to get anything to work! So, here's step-by-step of what I just did and the result I get every single time, no matter the initial method:
1: Fired up ODIN3.
2: Wiped the user data and cache from the stock recovery (Android System Recovery (3e)).
3: Connect USB cable, reboot phone into download mode (using the battery-pull method).
4: Successfully flash to stock ROM, reboot.
5: Sign in with Google, enable WiFi.
6: Run SuperOneClick, reboot.
7: Grab ES File Explorer from the Market, after it updates.
8: Attempt to replace "recovery" in /system/bin with custom
... and here's where things break. Doesn't matter what version of SuperOneClick I use (and I've tried from 1.9.1 through 2.2.3), nor does it matter what exploit I select. What happens? Well... aside from everything on-screen claiming to be okay, and everything claiming it's working, once the rooting is "successful", I reboot like it says, see that SuperUser is in the applications, it shows me an su binary version...
... but anything that tries to run super-user (ES File Explorer included) that gets added to the super-user list simply does not work. I can't over-write the recovery, can't delete or muddle with anything that requires elevated privileges, and the ROM Manager for sure won't work because I can't get CWR installed.
I love my phones with keyboards. I really do. I'd love to keep this thing, but the stock firmware is driving me up a wall (especially that stupid media scanner). So if anyone has any ideas to throw at me, care to offer some? Haven't a clue at this point what I'm doing wrong.

Hey buddy!
I feel your pain, this is one of the last nicely built hardware keyboard phones, first time rooting it is a bit strange
See post #27 (or so) here
http://forum.xda-developers.com/showthread.php?t=2221030
I ran through the manual steps there and have links for needed files
If you get stuck let me know, I'll be around

demkantor said:
Hey buddy!
I feel your pain, this is one of the last nicely built hardware keyboard phones, first time rooting it is a bit strange
See post #27 (or so) here
http://forum.xda-developers.com/showthread.php?t=2221030
I ran through the manual steps there and have links for needed files
If you get stuck let me know, I'll be around
Click to expand...
Click to collapse
Awesome! I'll give this a go once I'm all done with today's activities and see if it works.
Well, apparently I have root access for the moment, but it is denying my replacing of /system/bin/recovery - in adb shell, it states "Filesystem is read-only", so I re-mounted /system -rw and no dice. Going to attempt to try again in a moment, after a reboot.

Okay, so since there's a problem with all of this, I'm going to try that second ROM (KD2 I think it was) - but as I recall, it was on a very slow server. Plus I have a load of things to do tomorrow, so it probably won't be until tomorrow evening sometime when I'll be able to flash it. Once I've used Odin to re-flash, I'll get back to you.

Well, I had to dissect "t839-Sidekick4G-UVKG2-One-Click.jar" and remove the xml file from within it, but I acquired the necessary package to upgrade to KG2 from KD1 through Odin3. Took a while to figure out just how to deal with it, and I was successful in flashing... and I even replaced the recovery file after rooting it again!
... however, now it just sits there at the "T Mobile Sidekick 4G" start-up screen when I attempt to boot into recovery, so now I'm preparing to re-flash it again to recover the stock recovery. So... still more on this, later.
EDIT: Also, I named the tar file "KG2OdinHeimdall.tar", since I basically ripped it right off the "HeimdallPackage.tar" file from the Heimdall one-click thing. Turns out, it apparently works just fine if you remove the .xml file from the original tar.

Finally!
I ended up having to use my own method to get the KG2 update installed because the one-click program kept crashing on me when selecting "Show all devices", and I opted to use AntTek Explorer (all you have to do is go into the program's options and it'll attempt to acquire admin privileges, if the device is rooted) to copy the recovery file to /system/bin - but your post worked for everything else, once I got past not being able to copy the recovery file.
I opted for the CM6 package and it's quite fast! Thank you loads, demkantor!

Nice! I'm glad all worked out well for you!
If you get a chance try out the one gingerbread ROM, its cool to see it running but there are still driver issues so keyboard is borked, really makes it pointless to have on this phone...
But there are a few nice froyo ROMs ready to be played with, someday development will hopefully pick up again
Until then, happy flashing!