Related
I been performing this myself with great success, but you need ROOT access AND busybox installed. Create a folder on your phone's SD card called tmp. You'll need adb in order to adb shell, and gain root access. (in cmd, adb shell <enter> su <enter> confirm you are on a # prompt not the $ prompt)
Now copy and paste each line, press enter after each line pasted. Confirm the files copied after each line by running ls /mnt/sdcard/tmp/mmssms.db
Code:
cp /dbdata/databases/com.android.providers.contacts/contacts2.db /mnt/sdcard/tmp/contacts2.db
cp /dbdata/databases/com.android.providers.telephony/mmssms.db /mnt/sdcard/tmp/mmssms.db
cp /dbdata/databases/com.sec.android.provider.logsprovider/logs.db /mnt/sdcard/tmp/logs.db
cp /dbdata/databases/com.sec.android.app.memo/Memo.db /mnt/sdcard/tmp/Memo.db
cp /dbdata/databases/com.android.providers.calendar/calendar.db /mnt/sdcard/tmp/calendar.db
Once that is done, mount the phone to your computer and copy the TMP folder to your computer. When you flash the custom rom, you'll have to keep the SIM card out of the phone because you do not want new history items written to the log files.
Next ls -l /dbdata/databases/com.android.providers.contacts/contacts2.db (and the others) to see what permissions/owner they have, if you simply cp the files from /mnt/sdcard/tmp to their locations, you'll get force closes in the application (because it's not able to write log data).
Make note is the owner for each db file. Then back to adb shell, su, cd /mnt/sdcard/tmp (trust everyone knows to copy the tmp folder from PC onto your phone) cp contacts2.db /dbdata/databases/com.android.providers.contacts/contacts2.db (and the others!).
Once the files are copied back to their locations on the device, run the following:
Code:
chmod 660 /dbdata/databases/com.android.providers.contacts/contacts2.db
chown app_15.app_15 /dbdata/databases/com.android.providers.contacts/contacts2.db
Obviously you want to use the app_X.app_X you saw from running ls -l /path/filename before copying the backed up log file.
bravomail said:
This is quick comparative review.
Overall for KB1.
TiBu restore of system setting from JS32.2.1 or JS52.2.1 other than WiFi highly discouraged. I had uncurable Force Close for Browser and for MMS. Say g-bye to your messaging history, or find other ways of transferring it.
Click to expand...
Click to collapse
Original thread is here http://forum.xda-developers.com/showthread.php?t=969343
SMS Backup and Restore is a great app that does exactly what it's title indicates, without root.
https://market.android.com/details?id=com.riteshsahu.SMSBackupRestore
Call logs backup and restore also does exactly what it's title indicates, without root.
https://market.android.com/details?id=com.riteshsahu.CallLogBackupRestore
Both free and developed by the same guy, I've used both many times without a hitch.
I sync my contacts with gmail, so no problem there.
hauj0bb said:
SMS Backup and Restore is a great app that does exactly what it's title indicates, without root.
https://market.android.com/details?id=com.riteshsahu.SMSBackupRestore
Call logs backup and restore also does exactly what it's title indicates, without root.
https://market.android.com/details?id=com.riteshsahu.CallLogBackupRestore
Both free and developed by the same guy, I've used both many times without a hitch.
I sync my contacts with gmail, so no problem there.
Click to expand...
Click to collapse
+1
The manual method is pointless and extra work for nothing. These apps work flawlessly. I've used them many times as well.
I know there are apps which backup the same settings, my whole point for posting is I do not backup contacts with Google. So I kept trying different things until putting this together and I know it's a pain but all that really is done is copying and pasting lines into an SU adb shell.
askpcguy said:
I know there are apps which backup the same settings, my whole point for posting is I do not backup contacts with Google. So I kept trying different things until putting this together and I know it's a pain but all that really is done is copying and pasting lines into an SU adb shell.
Click to expand...
Click to collapse
You do not use google account or you just don't use it for backing up contacts...
I use a Google account but not to sync or backup contacts.
Sent from my SAMSUNG-SGH-I897 using XDA App
Thanks for good info!
Thanks for good info!
I personally don't care about my SMS history. Other people text a lot.
Another alternative is to use Google backup/synchronization. I never tried it. Anyone?
In my experience, backing up phone contacts using Gmail syncing is not 100%. Some fields in the on phone contact records are not properly carried into Gmail contact records and viceversa.
You'd think since Android is Google and Gmail is Google this would work flawlessly.
askpcguy said:
I been performing this myself with great success, but you need ROOT access AND busybox installed. Create a folder on your phone's SD card called tmp. You'll need adb in order to adb shell, and gain root access. (in cmd, adb shell <enter> su <enter> confirm you are on a # prompt not the $ prompt)
Now copy and paste each line, press enter after each line pasted. Confirm the files copied after each line by running ls /mnt/sdcard/tmp/mmssms.db
Code:
Next ls -l /dbdata/databases/com.android.providers.contacts/contacts2.db (and the others) to see what permissions/owner they have, if you simply cp the files from /mnt/sdcard/tmp to their locations, you'll get force closes in the application (because it's not able to write log data).
Make note is the owner for each db file. Then back to adb shell, su, cd /mnt/sdcard/tmp (trust everyone knows to copy the tmp folder from PC onto your phone) cp contacts2.db /dbdata/databases/com.android.providers.contacts/contacts2.db (and the others!).
Once the files are copied back to their locations on the device, run the following:
[CODE]chmod 660 /dbdata/databases/com.android.providers.contacts/contacts2.db
chown app_15.app_15 /dbdata/databases/com.android.providers.contacts/contacts2.db
Obviously you want to use the app_X.app_X you saw from running ls -l /path/filename before copying the backed up log file.
Click to expand...
Click to collapse
Are you doing all this above because
Code:
cp -p
failed to preserve attributes or something? Or do your fingers like the exercise...
Oh, I bet it's because it is that the attributes are getting scrubbed when they are copied off the device to your computer...
I only do this manual method because I want to retain my history and contacts between Roms.
Sent from my SAMSUNG-SGH-I897 using XDA App
I was asking specifically why you didn't use the "-p" preserve attributes flag when using the cp (copy) command. But I now realize your may be storing your backups in a way that blows away the info anyway. so you need to set ownership and permissions manually after restore..
Because I push the files to an external sd card which is copied to my computer.
Sent from my SAMSUNG-SGH-I897 using XDA App
TiBu does this, too. But thanks for the info. It's good too know how to do things manually, too.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
I don't think titanium backup will backup call history. It does get the contacts and calendar though.
Sent from my SAMSUNG-SGH-I897 using XDA App
I found this thread very useful for the restoration of all my recent messages!!
the backup i have done with smsbackup&restore is 12hour before the disaster
what happened? simply after a normal reboot my Desire HD was going to bootloop! i've tried several restore procedures but i find out that /data partition is somehow "bad", don't know why...
the only thing i can do is backup data partition with clockworldmod and unyaff it on a pc;
then i followed the instructions in the OP and i succedeed in making succesfully a backup of all my messages ;
the only difference is the different path in which mmssms.db is located in Desire HD:
i have in /data/data/com.android.providers.telephony/databases/
thank you again mate, very detailed guide
Glad someone found this useful! This is only compatible with Froyo roms, Gingerbread uses the /datadata folder and I haven't needed to manually backup the files because MIUI backup does it so amazingly well!
Well, this is pretty neat. I'm forever reflashing my phone and having to reload everything.
Which is a p-a-i-n..
One question though, is there anyway to do all this using "adb shell"? I'd love to incorporate this into a batch file I'm making, with the proper credits of course, and it'd be nice to press a button and have the PC do all the hard work.
askpcguy said:
I don't think titanium backup will backup call history. It does get the contacts and calendar though.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Super Backup from the Market does all 3:
https://market.android.com/details?id=com.idea.backup.smscontacts&feature=search_result
The apps in post #2 are great too.
Ticklefish said:
Well, this is pretty neat. I'm forever reflashing my phone and having to reload everything.
Which is a p-a-i-n..
One question though, is there anyway to do all this using "adb shell"? I'd love to incorporate this into a batch file I'm making, with the proper credits of course, and it'd be nice to press a button and have the PC do all the hard work.
Click to expand...
Click to collapse
I tried, I had sort of a working bash script but ran into problems trying to get the script root access to do the copying/restoring. Come to think of it, if you wanted to get fancy, you could make a clockwork mod flashable zip. One for backup and one for restore.
-Yes, I know there are apps which might do this however I wanted to learn on my own.
Well, yes, there are backup apps but you have to reinstall those apps and wait while they put your data back in bit by bit. Granted it may not take long but when you're reflashing what seems like once every five minutes, it can take forever!
The zip route seems like a good idea. That way, you can back up, install a rom and restore your details all from one screen. I'll have to have a look at it.
Sent from my U20i using XDA App
Alright guys....Need help. How do I unroot from Super OneClick. I have the official TMobile 2.2 ROM as OTA..however it's failing because its checking to see if its rooted. Pleasant. So If someone could point me in the right direction it would be appreciated.
you sure its 2.2? OTA?
Yup. 100% Sure. 112MB file download. File is called Blur_Version.3.6.360.MB525.T-Mobile.en.US.zip with a Blur_Version.3.6.360.MB525.T-Mobile.en.US.crc file as well. Build.prop indicates that it is 2.2.1 /3.4.2-107-JDN-9/34.4.9. Getting completely hung up on this Status 7 error though. It is picky as hell, and I don't have a out of the box backup I can use to try as stock. It is definitely checking files though. It's like christmas and staring at your presents knowing what it is, but you can't unwrap it. Uggh!!
Root can't be your problem. I've updated to that release; Android 2.2.1, Blur 34.4.9, Build # 3.4.2.107_IDN-9, while my system was rooted. My phone was quite customized (Go Launcher with some "foreign" widgets and no Blur apps/widgets except for the Email app to get at my work e-mail) and everything came up OK. I was rather surprized how smoothly it all went. All my data (seemed to be mostly e-mail) had to be re-synched (this happened automatically), and it took one reboot to clear a message about non-Moto battery that was displayed after the first boot. Basically it all is where it was, except, of course, for root (I tried the latest, 1.7, SuperOneClick but it's looping no matter what I do).
Good luck.
[Added]
Well, well. It turned out that even though it seemed that SuperOneClick was failing (looping at trying to mount a partition R/O) it actually it did it's job! I just fired up RootExplorer and lo and behold a confirmation from Superuser for root popped up, got accepted, and I can start renaming the bloatware again. Woo hoo!
For me it ended up being the root. I was able to unroot with Z4root, and as soon as I did no more issues. I ended up saying screw it and wiped my phone all the way back to factory. Figure it's just better to rebuild it all cleanly and be done with it. I'm just happy its an official rom now.
mind posting a nandroid back up please?
It's really insane to sanction against rooting a phone. I can't image a computer denying me administrator's rights.
runeblade said:
How do I unroot from Super OneClick.
Click to expand...
Click to collapse
You can simply do it manually using Root Explorer. delete followings AS ROOT USER and reboot. that's all!
1. /data/data/com.noshufou.android.su
2. /system/app/superuser.apk
3. /system/bin/su & busybox
Also, it can be done via adb connection.
adb shell
$ su
# mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
# rm -r /data/data/com.noshufou.android.su
# rm /system/app/superuser.apk
# rm /system/bin/su
# rm /system/bin/busybox
# reboot
I second this.
jboogie3 said:
mind posting a nandroid back up please?
Click to expand...
Click to collapse
New 100% reliable "temp root" for Titanium Backup (won't stop working until reboot!)
Hi all,
I grew frustrated by the annoyance of losing root access randomly, when modified files on /system suddenly become inaccessible because of the S-ON lock.
But here's some good news: I came up with a way to get a 100% reliable "temp root" for Titanium Backup.
Advantages:
You will not lose root access until next reboot!
100% reliable, does not modify /system at all.
Drawbacks:
Minimalistic approach with no BusyBox.
Will only work with select root apps.
Tested with Titanium Backup only (for now).
Requirements:
Original "out of the box" Sensation or EVO 3D (untested).
Android SDK tools ("adb" command) on a computer.
USB connection between computer and phone.
Installed Superuser app from the Market.
Initial (one-time) setup:
unzip better-temp-root.zip
adb push fre3vo /data/local/tmp/
adb shell "cd /data/local/tmp ; chmod 755 fre3vo ; ./fre3vo"
adb shell "mkdir /data/bin ; mv /data/local/tmp/fre3vo /data/bin/"
adb push su /data/bin/
adb push root.sh /data/bin/
adb shell "chmod 4555 /data/bin/su ; chmod 755 /data/bin/root.sh"
adb shell "/data/bin/root.sh"
After every reboot:
adb shell "/data/bin/fre3vo"
adb shell "/data/bin/root.sh"
The advantage of this method is that /system is not modified, therefore the rooting will be totally stable and will persist until the next reboot
Q&A:
Will it work with other root apps?
This is a minimalistic approach which installs no busybox and does not touch /system, in order to be perfectly reliable. The drawback of this is that it will work only with root apps that are able to find "su" at /data/bin/su, and that don't need a busybox in $PATH. Fortunately, Titanium Backup fulfills both of these criteria. If you know other apps that do, please post about them.
Status:
Titanium Backup (free & pro): works
Root Explorer: works
MyBackup pro: works?
SetCPU: FC
Wireless tether: needs system modification
Greetings go to #teamwin for the exploit, of course.
Have fun !
Great. Good job!
Now where is that test recovery?
If it works well, maybe you should try and pass the files onto agrabren for him to implement into Fre3vo^2 (apk that makes root better like your fix is aiming to).
That way things will move a LOT faster
Using this, I can get Titanium Backup to work, but not AdFree. Might just wait for Fre3vo^2.
Adfree is build to edit files on /system partition which is not possible with temp root
Set-Cpu is working?
possible to make a script that runs
Code:
adb shell "/data/bin/fre3vo"
adb shell "/data/bin/root.sh"
at each boot automatically?
Does barnacle or any WiFi tether apps work with this? Still at work.....
Sorry for the noob question but where do unzip it to, the computer or the phone?
Sent from my PG86100 using XDA App
madindehead said:
Using this, I can get Titanium Backup to work, but not AdFree. Might just wait for Fre3vo^2.
Click to expand...
Click to collapse
Thanks for your feedback. I hadn't tested AdFree, but I'm not surprised here. This solution is a willful compromise: we refrain from modifying /system, and thus we gain 100% reliability - but at the same time we lose compatibility with some root apps, because they often rely on BusyBox being in /system (or at least in $PATH).
I have contacted @agrabren on Twitter with a link to this thread. I haven't looked into it, but if #teamwin can come up with a way to execute adb commands locally on the phone, it could all be done automatically at boot. Hopefully they'll add a configuration choice such as:
Method 1: Full compatibility with root apps, system BusyBox, "ephemeral" root
Method 2: Compatibility with *some* root apps, no system BusyBox, 100% reliable root
Let's see how it goes... but I know which method I'd personally use
Tiffany84 said:
Sorry for the noob question but where do unzip it to, the computer or the phone?
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Unzip to the computer, you'll get 3 files. Go on from there
What about this:
Any difference to files/method from first post?
http://www.facebook.com/pages/S-Off-for-Sensation-and-Evo-3d-NOW/117107248377328?sk=wall&filter=1
joel.bourquard said:
Unzip to the computer, you'll get 3 files. Go on from there
Click to expand...
Click to collapse
Ok. So this is where I struggle with adb. So how does it know where the files are at? Do u have to tell it the location of the files or do u put it in the same directory with adb? Again, I apologize when it comes to being clueless with adb.
Sent from my PG86100 using XDA App
DomSim said:
possible to make a script that runs
Code:
adb shell "/data/bin/fre3vo"
adb shell "/data/bin/root.sh"
at each boot automatically?
Click to expand...
Click to collapse
That's the goal - but such a script would not work right now, because: (1) the 1st command terminates the current shell and (2) the 2nd command must be called through ADB.
As far as I see, the 1st command could be invoked automatically from an Android app at boot, but the 2nd one needs to be called through adb, which requires a separate computer right now.
I haven't looked into that - but I think @agrabren / #teamwin are aiming at this (ie: somehow doing the equivalent of running commands through "adb" from the device itself) with Fre3vo^2.
Thanks very much..
Sent from my HTC Sensation Z710e using XDA App
Tiffany84 said:
Ok. So this is where I struggle with adb. So how does it know where the files are at? Do u have to tell it the location of the files or do u put it in the same directory with adb? Again, I apologize when it comes to being clueless with adb.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Same directory
Tiffany84 said:
Ok. So this is where I struggle with adb. So how does it know where the files are at? Do u have to tell it the location of the files or do u put it in the same directory with adb? Again, I apologize when it comes to being clueless with adb.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
I run Linux personally, but I think if you just unzip the files into some empty folder, then stay in that same folder and run ADB by its absolute path, it should work fine. Something like:
"C:\Program Files\Android SDK\BIN\ADB.EXE" push xx yy
Maybe a Windows user could give you more precise advice here...
Why would you need barnacle when you have wireless tether built in?
Sent from my HTC Sensation 4G using XDA App
With this,only run fre3vo bat file and all will install
automatically:
Ganii said:
What about this:
Any difference to files/method from first post?
http://www.facebook.com/pages/S-Off-for-Sensation-and-Evo-3d-NOW/117107248377328?sk=wall&filter=1
Click to expand...
Click to collapse
Anyone tried SetCPU ? Which profile did you select, and does it work?
Pinepig said:
Same directory
Click to expand...
Click to collapse
Thanks.
Sent from my PG86100 using XDA App
Found this over at SDX Developers
It's so easy a caveman can do it.
http://forum.sdx-developers.com/index.php?topic=17172.0
Be aware that if you do this you have no control over what has root and what doesn't. The "gingerbreak" way, along with the Android SU, does.
couldn't a person just install superuser?
Intercepter said:
couldn't a person just install superuser?
Click to expand...
Click to collapse
yes you can.... ive tested all of the ways of rooting this phone and this one is the easiest! after you do it just install superuser from the market and your all good.
Hey that's my post lol! Yeah well the thing about malware and root access that no one hardly knows is that all these apps that use root exploits to cause harm, they never request su permissions because they use there own exploit to gain root. So superuser wouldn't prompt you on an exploit root being ran. Superuser just prompts when some app requests /system/bin/su or /system/xbin/su. If you want to keep your phone safe its a mater of knowing what you install on your phone. Even with superuser your not safe from root exploit attacks!
Me personally I like nit having to allow everytime I install a new root app. And I know what I install so I never worry about malware.
Sent from my MOTWX435KT using Tapatalk
I noticed that his fix is to basically link su to sudo, which allows "root" programs to run the included superuser applet.
So does this mean someone could just install the SuperUser app without going through the usual rooting process? Is Gingerbreaking unnecessary then?
what concerns me is that if these phones ship with sudo enabled and no root password, then any app can get root without any special effort. That means the Triump is VERY insecure. I'm wondering if we can safely remove sudo and solve that particular problem.
Maybe they did that to make fixing them easier, for when a phone got sent in they could gain root and do whatever they need in it, then turn it back off real quick. This is kinda like the tether menu being hidden but not removed on the OV. How stupid do they think people are?
I don't think it's a question of stupidity - it's more one of knowledge. They don't anticipate the run-of-the-mill user to be digging through the file structure of the phone for something they have no idea of what it does or how it works.
And I'd have to agree - the non-technical people have no desire to start digging through the phone, but rather, to use it as is.
Therefore......
So if this could be made a script. Then we could un-root just as easily for protection. I only need it for barnacle.
root
--------
sudo
ln -s /system/xbin/sudo /system/xbin/su
ln -s /system/xbin/sudo /system/bin/su
unroot
-------
sudo
rm /system/xbin/su
rm /system/bin/su
RIGHT?
Edit: the "shebang" line needs to be changed. Not sure to what. You may be better off just typing in the commands yourself.
Not tested, but this should work.
The root script:
Code:
#!/bin/sh
#filename: rootme
echo "Rooting Device"
sudo
ln -s /system/xbin/sudo /system/xbin/su
ln -s /system/xbin/sudo /system/bin/su
echo 'Root has been achieved'
The unroot script:
Code:
#!/bin/sh
#filename: unrootme
echo "Un-rooting Device"
sudo
rm /system/xbin/sudo /system/xbin/su
rm /system/xbin/sudo /system/bin/su
echo 'Un-root has been achieved'
Make these files somewhere and *cd* to that directory. Type either
Code:
./rootme
or
Code:
./unrootme
Hope this helps someone.
TomXP411 said:
I noticed that his fix is to basically link su to sudo, which allows "root" programs to run the included superuser applet.
So does this mean someone could just install the SuperUser app without going through the usual rooting process? Is Gingerbreaking unnecessary then?
what concerns me is that if these phones ship with sudo enabled and no root password, then any app can get root without any special effort. That means the Triump is VERY insecure. I'm wondering if we can safely remove sudo and solve that particular problem.
Click to expand...
Click to collapse
Yes, that is true that an app could very easily gain root access on the triumph. HOWEVER, as pointed out by b_randon14 above, practically all malware apps use a root exploit to gain root priveliges. This means that even an unrooted device is susceptible. As an example, take a stock samsung captivate. It has no root, and no way to gain root, without flashing a custom rom/kernel. However, if an app used the psneuter exploit, it could still gain root access. (Btw, that is how I originally rooted my captivate, using super one click with the psneauter exploit)
So really, the triumph is no less secure than any other android device. Plus, the triumph is the only android device, aside from dev phones such as the nexus one/nexus s that come pre-rooted. So a triumph specific malware app would have to be written.
Personaly, I like the su+superuser.apk method of rooting, but that is because it is the only method I have ever used. And remember, if you prefer to have su+superuser.apk, you either use gingerbreak, or just use this trick and then install superuser.apk.
Sent from my SAMSUNG-SGH-I897
Yeah and plus an app has to be designed to gain root its not like any old app can just up and decide to request root and start destroying! And stock without any root(I.e. my method or gingerbreak) an app doesn't call /system/xbin/sudo it would call /system/bin/su or /system/xbin/su. Plus I mean if you used gingerbreak you should realize that an app can get root without going through superusrr or calling on su. I mean how else do you think gingrrbreak app gets root in the first place to copy su and superuser? Through the gingerbreak root exploit!!
Sent from my OC'ed Triumph!
The concept of an app being able to gain root makes it just as dangerous as a malignant virus for Android. The only difference is, it's not a virus. It's a nice, helpful, and otherwise very good program. Lucky for us.
I'm working on a batch script that does the same thing as these instructions, anybody vaguely interested in using it (should it be put out)?
primetechv2 said:
The concept of an app being able to gain root makes it just as dangerous as a malignant virus for Android. The only difference is, it's not a virus. It's a nice, helpful, and otherwise very good program. Lucky for us.
I'm working on a batch script that does the same thing as these instructions, anybody vaguely interested in using it (should it be put out)?
Click to expand...
Click to collapse
I wrote one and posted on xda, I think, but the shebang line needs some adjustment to find sh. Hope that helps.
Sent from my rooted Moto Triumph
Why is this not working for me? I downloaded terminal emulator from the market, typed: "sudo" and get:
sudo: permission denied
$
tsac said:
Why is this not working for me? I downloaded terminal emulator from the market, typed: "sudo" and get:
sudo: permission denied
$
Click to expand...
Click to collapse
Did they patch it? These two lines of code run from ADB should "root" the device... and sudo is just there.
adb -d shell sudo ln ln -s /system/xbin/sudo /system/xbin/su
adb -d shell sudo ln ln -s /system/xbin/sudo /system/bin/su
Now you may not be able to run "sudo" alone, you may need to specify a command with it too? Unfortunately I can't try it again, because all of my phones are rooted now
In the event this didn't work, GingerBreak should work regardless.
I'll give it a try when my phone finishes charging.....Thank you
tsac said:
I'll give it a try when my phone finishes charging.....Thank you
Click to expand...
Click to collapse
Sure. although I would still recommend Gingerbreak instead...it's more complete and contains Superuser as an extra security measure.
Sent from my MOTWX435KT using Tapatalk
Never got to try anything....Phones screen is dead. You know how people describe the flashing screen when turned on and off? Well mine flashed once and it has not worked since... Hopefully virgin mobile will honor the 1 year factory warranty. I did absolutely nothing to this phone. It just took a crap. Removal of battery does nothing. Phone will receive calls but there is nothing but a backlight. Tried several different methods. Horrible phone....Should be recalled
Thanks for your trying to help me.
Sent from my reliable homebuilt gaming rig using FireFox
rooted my dad's triumph...question though...couldn't I flash clockworkmod via rom manager or do I have to go the long way?
edit: nvm, i see rom manager doesn't support the triumph
UPDATE: try this simpler method first: http://forum.xda-developers.com/galaxy-y/general/trick-how-to-disable-google-play-store-t2951378
BEFORE REPLYING: please know that I have tried all of the standard suggested solutions to prevent Market from updating, including freezing Market Updater, using pm disable on it, and turning off auto-updates for apps, and these do not work on Market versions >= 3.0.
On my Samsung Galaxy S2, the latest market app (3.4.4) randomly freezes my entire phone, causing me to have to hold the power button down to reboot. Happens nearly every time I browse for apps in that version. I can "uninstall updates" to get back to the version in /system, but it updates itself to 3.4.4 every time I run it. My goal: prevent the automatic updates.
Plenty of threads here and elsewhere have tips for preventing the updates. The problem is that none if them work for market versions beyond 3.0. I've discovered a method for preventing the updates even on more recent market versions.
Do "uninstall updates" on the market app (in "manage applications").
Open the terminal app.
Run "su" to become root.
Run: touch /data/app/com.android.vending-1.apk
Run: chattr +i /data/app/com.android.vending-1.apk
This will put a bogus APK file in the way of where Android wants to put the new version. The chattr command makes the file "immutable", so that even root can't remove it. Just setting it read only with chmod isn't enough.
This will pin your market to the version included in your ROM. This trick might work if you want to pin a version that's already in /data/app, if you skip the "uninstall updates" and the "touch" command... Haven't tested this.
I tried it, but it said "chattr: command not found".
lexelby said:
On my Samsung Galaxy S2, the latest market app (3.4.4) randomly freezes my entire phone, causing me to have to hold the power button down to reboot. Happens nearly every time I browse for apps in that version. I can "uninstall updates" to get back to the version in /system, but it updates itself to 3.4.4 every time I run it. My goal: prevent the automatic updates.
Plenty of threads here and elsewhere have tips for preventing the updates. The problem is that none if them work for market versions beyond 3.0. I've discovered a method for preventing the updates even on more recent market versions.
Do "uninstall updates" on the market app (in "manage applications").
Open the terminal app.
Run "su" to become root.
Run: touch /data/app/com.android.vending-1.apk
Run: chattr +i /data/app/com.android.vending-1.apk
This will put a bogus APK file in the way of where Android wants to put the new version. The chattr command makes the file "immutable", so that even root can't remove it. Just setting it read only with chmod isn't enough.
This will pin your market to the version included in your ROM. This trick might work if you want to pin a version that's already in /data/app, if you skip the "uninstall updates" and the "touch" command... Haven't tested this.
Click to expand...
Click to collapse
I've had the same problem and this looks quite promising, but I have the same problem w/ chattr not found. What terminal app are you running?
Oops, should have mentioned... You'll need busybox installed. It'll include the chattr command.
lexelby said:
On my Samsung Galaxy S2, the latest market app (3.4.4) randomly freezes my entire phone, causing me to have to hold the power button down to reboot. Happens nearly every time I browse for apps in that version. I can "uninstall updates" to get back to the version in /system, but it updates itself to 3.4.4 every time I run it. My goal: prevent the automatic updates.
Plenty of threads here and elsewhere have tips for preventing the updates. The problem is that none if them work for market versions beyond 3.0. I've discovered a method for preventing the updates even on more recent market versions.
Do "uninstall updates" on the market app (in "manage applications").
Open the terminal app.
Run "su" to become root.
Run: touch /data/app/com.android.vending-1.apk
Run: chattr +i /data/app/com.android.vending-1.apk
This will put a bogus APK file in the way of where Android wants to put the new version. The chattr command makes the file "immutable", so that even root can't remove it. Just setting it read only with chmod isn't enough.
This will pin your market to the version included in your ROM. This trick might work if you want to pin a version that's already in /data/app, if you skip the "uninstall updates" and the "touch" command... Haven't tested this.
Click to expand...
Click to collapse
Ok, I'm back to version 3.1.3. I really hope this works! This market freeze problem has been driving me nuts. This has been the first time I've become overly frustrated with Android. If a version of the market isn't working correctly on our phones, we should be able to run whatever version of the market we want without it automatically updating and forcing you to use the latest version.
Oh!! You have the freezing too? I searched all over but I couldn't find anyone else describing the same freezes. What device/ROM are you on?
lexelby said:
Oh!! You have the freezing too? I searched all over but I couldn't find anyone else describing the same freezes. What device/ROM are you on?
Click to expand...
Click to collapse
I'm currently on CM7 using the AT&T Galaxy S2. I try MIUI from time to time to see if the issue has been resolved, but it hasn't. I had my first market lockup on CM7 today. It's been frustrating the living hell out of me. I tried your suggestion and the market still updated. Hasn't locked up yet, but I haven't spent a lot of time on my phone either.
Any other alternatives? Did the proposed solution work for you?
Sounds like you and I have the exact same phone, carrier, and ROM. The fix did work for me... Hasn't updated since. Maybe try removing Market Updater with Titanium Backup too. Perhaps it falls back to that to update if the builtin mechanism fails... Not sure. You could also try the process again, but be super sure you close Market, "uninstall updates", and then do the touch and chattr. If all else fails you could take a screen video (can we do that on Android?) and I'll watch to see if maybe there's a step I missed.
Also, after going through the steps, run these and paste in the results:
ls -l /data/app/com.android.vending-1.apk
lsattr /data/app/com.android.vending-1.apk
Ok, I'm going to try all of this later today when I get a chance. Will post back with an update asap.
Also, do you remember the results that came up after running every command? I'm going to try to post everything that comes up so you can take a look for yourself.
How long have you been running the market without it updating? I know quite a few people that could benefit from this if it works consistsntly. We are not some rare group. This is a pretty widespread issue here.
Sent from my SGH-I777 using Tapatalk
My market's been on version 3.1.3 since the day before I posted this thread, and it hasn't updated at all. I really think we can get this working for you too... We just need to figure out if I forgot to include a step. The two commands both actually give no feedback at all, so the ls and lsattr will tell us whether things worked properly.
So this problem is widespread? My Google-fu fails me, apparently. Is it just sgh-i777 users on cm7?
Here are my results. Note, the first time I did this, after one of the steps, I got something "not found." I don't remember what it was. But anyways:
$ export PATH=/data/local/bin:$PATH
$ su
# touch /data/app/com.android.vending-1.apk
# chattr +1/data/app/com.android.vending-1.apk
BusyBox v1.19.3 (2011-11-22 01:37:10 MST) multi-call binary.
Usage: chattr [-R] [-+=AacDdijsStTu] [-v VERSION] [FILE]...
Change file attributes on an ext2 fs
Modifiers:
- Remove attributes
+ Add attributes
= Set attributes
Attributes:
A Don't track atime
a Append mode only
c Enable compress
D Write dir contents synchronously
d Don't backup with dump
i Cannot be modified (immutable)
j Write all data to journal first
s Zero disk storage when deleted
S Write file contents synchronously
t Disable tail-merging of partial blocks with other files
u Allow file to be undeleted
-R Recurse
-v Set the file's version/generation number
# ls -l/data/app/com.android.vending-1.apk
ls: invalid option -- /
BusyBox v1.19.3 (2011-11-22 01:37:10 MST) multi-call binary.
Usage: ls [-1AaCxdLHRFplinsehrSXvctu] [-w WIDTH] [FILE]...
List directory contents
-1 One column output
-a Include entries which start with .
-A Like -a, but exclude . and ..
-C List by columns
-x List by lines
-d List directory entries instead of contents
-L Follow symlinks
-H Follow symlinks on command line
-R Recurse
-p Append / to dir entries
-F Append indicator (one of */[email protected]|) to entries
-l Long listing format
-i List inode numbers
-n List numeric UIDs and GIDs instead of names
-s List allocated blocks
-e List full date and time
-h List sizes in human readable format (1K 243M 2G)
-r Sort in reverse order
-S Sort by size
-X Sort by extension
-v Sort by version
-c With -l: sort by ctime
-t With -l: sort by mtime
-u With -l: sort by atime
-w N Assume the terminal is N columns wide
--color[={always,never,auto}] Control coloring
# lsattr /data/app/com.android.vending-1.apk
--------A---- /data/app/com.android.vending-1.apk
#
I just looked at the options and it looks like I inserted an "L" instead of "I" to make the file immutible. Correct? Let me know if I did something wrong so I can go back and try again.
Aha! Now we're getting somewhere. The command should be... "chattr space plus lower-case I space /data/app/com.abdroid.vending-1.apk"... that's "vending dash one dot apk". The ls command is "ell ess space dash ell space /data/app/com.abdroid.vending-1.apk". Can you just copy/paste the commands from the OP?
lexelby said:
Aha! Now we're getting somewhere. The command should be... "chattr space plus lower-case I space /data/app/com.abdroid.vending-1.apk"... that's "vending dash one dot apk". The ls command is "ell ess space dash ell space /data/app/com.abdroid.vending-1.apk". Can you just copy/paste the commands from the OP?
Click to expand...
Click to collapse
Well I'll be damned! I'm going to give this a try.
Do avoid spelling android as "abdroid" like I did, though
lexelby said:
Do avoid spelling android as "abdroid" like I did, though
Click to expand...
Click to collapse
Lol.
Ok, I think I got it. Take a look.
$ export PATH=/data/local/bin:$PATH
$su
# a/app/com.android.vending-1.apk
# a/app/com.android.vending-1.apk
# ls -l data/app/com.android.vending-1.apk
-rw-rw-rw- 1 0 0 0 Jan 11 16:06 data/app/com.android.vending-1.apk
# lsattr data/app/com.android.vending-1.apk
-----i--A---- data/app/com.android.vending-1.apk
#
Don't know why some of it's cut off. I'm not a terminal emulator expert.
That looks right. Now run Market. It should be at 3.1.3, and if you close it, wait a minute, and reopen it, it should still be 3.1.3. If it's updated, then I guess we go back to the drawing board...
Ok ,I ran it and restarted it and it's still the same. Now keep in mind, I did this several times yesterday and about an hour later when I launched the market, it updated. Oh, while I have it in mind, let me freeze market updater, just to eliminate all possible causes. If this works, I owe you a beer! You just have no idea how frustrated I've been over the past month with this issue!
And for the record, type "android market freezes phone" in google search and see for yourself. We are NOT the only ones.
Oh trust me, I know just how frustrated you've been I was really starting to get pissed off at having to "uninstall updates" to safely use the market. I also think the freezes and resulting hard reboots caused the filesystem corruption that forced me to have to restore to factory and restore all of my apps from Titanium. That sucked.
i have another work around that might work. so far its sticking for me.
since the steps from OP is to prevent market from updating and staying at 3.1.3, i downloaded market 3.1.3.apk from here.
i went into root explorer and renamed 'vending.apk' to 'vending.apk.bak'. i didnt delete it incase if anything. just renamed as a backup.
i used tibu to freeze 'market updater'.
i copied market 3.1.3 apk into /system/app and set permission to rw-r-r.
reboot.
so far its working fine for me and its staying at 3.1.3. not sure for how long.