Related
I've been using Haykuro's G build because H has never worked for me. But now with the market problem I'm needing to switch to H because there are a lot of apps I want to download.
When I flash over to the H build and try to setup apps to sd, I always get stuck in a boot loop and I can't seem to figure out why that is. I thought maybe it was an app I had on my sdcard so I formatted both partitions and it still doesn't work.
If anyone can help it'd be greatly appreciated. =)
1st: you are trying the apps to sd H build right(not just the normal H version)?
2nd: what steps are you doing to try apps to sd and are any reporting errors?
3rd: are you trying to move the app cache also(/data/data)? If so that might be your problem.
It's the apps to sd version and I was just following the steps on the wiki pg.
http://android-dls.com/wiki/index.php?title=Haykuro_Apps_to_SD
And no I wasn't trying to move cache.
Hmm try going into the recovery terminal and do the following:
Code:
mount data
cd data
ls -l
look for the app directory listing and tell me what it says on that line(it'll probably carry over to the next line as well)
If the app directory doesn't exist well... then there's your problem.
app -> /system/sd/app
is that what you needed?
xocassidychick15ox said:
app -> /system/sd/app
is that what you needed?
Click to expand...
Click to collapse
Hmm ya, that looks correct. Was there anything else with that "->" next to it? If not, something is wrong with the sd card setup. Either /system/sd/app doesn't exist or the partitions aren't set up correctly. As a temporary fix(if there's nothing else with a '->') you can do this:
Code:
rm /data/app
mkdir/data/app
The only thing else that has '->' is:
app-private-> /system/sd/app-private
Hmm not looking good... try the code segment I put before, it should at least let you get into your phone. From there you can look into the /system/sd directory and make sure everything is correct.
EDIT: by not looking good I meant all that is correct which means it's something that'll be harder to fix.
When I try to enter the code it says:
rm /data/app
rm: cannot remove '/data/app' : No such file or directory
mkdir/data/app
sh: mkdir/data/app: not found
And when I look in /system/sd all it shows is lost+found
When I tried the code in ADB the first part went through but it still said
mkdir/data/app: not found
wfirst: there's a space between mkdir and /data/app.
also: you didn't restart the phone or anything since typing in the "mount data" bit have you? If so you need to type that again before doing that code segment.
EDIT: PM me your answers, I'll try to solve this through pm.
This has been solved. Reflashing the ROM fixed it.
The same thing happened to me. Went from 5.01G apps to SD, to 5.01Hr3 apps to SD. After setting up and changing the references to have apps point to the SD card (note that I already had apps on the SD card), all my apps appeared after rebooting. When I tried to reboot again, that's when I saw the endless HTC logo loop.
I reflashed the phone and it seemed to fix it. However, the phone later locked on me and I had to reboot by removing the battery. When the phone started again, I got the HTC logo loop.
I ended up going to Dude's G release instead. Hope someone figures this out.
Don't mean to start too many threads, but this is meant to specifically discuss the above programs.
RE: Google maps
Completely uninstalling and then reinstalling from the market seems to address the force close that occurs when a search query is submitted.
Alternatively, you can move the google maps apk from the ext2 partition to the /system/app folder on the phone. This is the same fix as for the google voice search...
RE: Google voice search
I went about the rather cumbersome process of moving the apk from the ext2 partition (as automatically happens in the Modaco ROM) back to the /system/app folder on the phone. This has resolved all the voice search crashes that I have come across.
NB: I do not know the results if you were to fix google maps by uninstalling and reinstalling and fix google voice search by moving the apk. I.e. if you were to do a google voice search within google maps under this fixing method, Im not sure if the voice search will crash....I'm guessing not though.
Please bear in mind im a COMPLETE linux/andoird/adb/whatever noob. I can outline my method for moving the apks, but Im certain there are better ways to do it.
Sweet, that fixed my google voice issue (and a quick mv and reboot didn't seem so bad to me, but perhaps I just have a high pain tolerance lol)
that or i didn't know there was an mv command...like i said...complete noob
dom2114 said:
that or i didn't know there was an mv command...like i said...complete noob
Click to expand...
Click to collapse
No sweat, mv is a linux command that can be used to move (thus mv) or rename files.
Basic Syntax:
Code:
mv [source] [destination]
So what I did was
Code:
mv /data/app/com.google.android.voicesearch.apk /system/app
and then rebooted the phone. Worked like a champ!
thanks, worked perfectly
NOTE: be sure to issue this command before the move to not get the 'read-only file system' error
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Thanks a ton for this! I don't have A2SD running and my Google Voice Search was also not working, I didn't even notice until someone had pointed it out. Lucky for me, there was a solution almost as fast as the problem was discovered! We should probably point it out to Paul @ MoDaCo now!
tstack77 said:
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
Alternatively, the following command works on MoDaCo's ROM:
Code:
adb remount
It accomplishes the same thing and is waaaaay easier for my simple mind to remember.
thecodemonk said:
Code:
adb remount
It accomplishes the same thing and is waaaaay easier for my simple mind to remember.
Click to expand...
Click to collapse
haha, totally agree. Thanks for that bit o' knowledge
AWESOME, thank you. I've been saving all of these forum posts together, I'll make a super-post once I get everything running the way I want, very clearly detailed and it will feature all of these different commands that I have used to help me along the way!
ok, so help me out if you can.
I want to copy the apk's on the ext2 partition i.e. in /system/sd/app to my computer in case I decide to wipe the sdcard for some reason.
In adb im typing:
cp /system/sd/app /desktop
Ive tried cp with the -r, -f, -rf options, and everytime i get a cannot create error message or sometimes a cannot create symlink message
Any tips??
dom2114 said:
ok, so help me out if you can.
I want to copy the apk's on the ext2 partition i.e. in /system/sd/app to my computer in case I decide to wipe the sdcard for some reason.
In adb im typing:
cp /system/sd/app /desktop
Ive tried cp with the -r, -f, -rf options, and everytime i get a cannot create error message or sometimes a cannot create symlink message
Any tips??
Click to expand...
Click to collapse
Once you're inside the adb shell, you don't really have access back to your desktop. Your best bet would be to run (from the windows command prompt where you normally run adb):
Code:
adb pull /system/sd/app c:\mybackup
(Replace C:\mybackup with whatever the path is to your destination...if you're on *nix or Mac, it will probably be more like "./Desktop" or something)
jesus, i think i might put a fist through a wall...im such an idiot.
pulling instead of pushing for the last half hour...
cheers, codemonk
dom2114 said:
jesus, i think i might put a fist through a wall...im such an idiot.
pulling instead of pushing for the last half hour...
cheers, codemonk
Click to expand...
Click to collapse
No sweat, we all have those moments. All the commands are fresh in my head since I've been researching and digging into things since before we had root (at the time trying to get it)...that and I think I've become addicted to the xda forums. (HALP!)
just as quick update to all.
Ive got a feeling that google voice search was actually causing all the force close issues in google maps. I still have google maps on my sdcard and did not uninstall it (only updated it) - have google voice search on phone and all seems to be fine.
A quick question for codemonk (& anyone else out there). For apps in the /system/app folder, you've got the apk and corresponding odex file. Anyone have any idea where the corresponding odex files for apps installed on the sd are (if they exist at all)?
dom2114 said:
just as quick update to all.
Ive got a feeling that google voice search was actually causing all the force close issues in google maps. I still have google maps on my sdcard and did not uninstall it (only updated it) - have google voice search on phone and all seems to be fine.
A quick question for codemonk (& anyone else out there). For apps in the /system/app folder, you've got the apk and corresponding odex file. Anyone have any idea where the corresponding odex files for apps installed on the sd are (if they exist at all)?
Click to expand...
Click to collapse
Not sure on the odex...I noticed some of the apps I removed didn't appear to have them (or are in a location I'm not aware of).
I ended up just moving the google voice app to fix it. (There's another thread on the google maps/google voice thing that contains the fix)
Ha, guess my XDA navigation isn't quite up to par. Care to post the link out of interest?
dom2114 said:
Ha, guess my XDA navigation isn't quite up to par. Care to post the link out of interest?
Click to expand...
Click to collapse
Wow I'm out of it...I was looking around, then realized...this *is* that thread. >.<
hahaha...guess it was your turn for onea those mistakes....
ok i dont even have voice search after installing modaco rom. all i have is the basic google search. how do i get the apk or download it. i tried the move, but it says it doesnt exist. i am complete noob so details are really needed thanks
if you decided to format your sdcard (using the recovery console) using the ext2/fat32/swap option, then the modaco ROM automatically moves google voice search and google maps (and a few other apps like quickoffice) to the ext2 partition on the sdcard.
this partition is accessible in various ways, but most people do it manually using ADB. if you don't know how to use adb, there are a bunch of threads here that talk about it. But in a nutshell, it involves downloading the android SDK, extracting it to somewhere on your computer (no need to install anything), open a command prompt in windows (start -> run -> cmd), navigate to the folder containing the sdk and go to the tools folder inside there (e.g. cd\androidsdk\tools), then type 'adb shell'. If all worked, you should have access to the phone.
then its just a matter of navigating to the ext2 partition on the sdcard (this is where all apps you install will be installed too - this is apps2sd automatically at work). You navigate there by typing:
cd /data/app
you should see the google voice search apk in there + others
then just use the command that codemonk helped me out with:
mv /data/app/com.google.android.voicesearch.apk /system/app
this will move the apk from the data/app folder (this is your sdcard) to the phone.
Written this response very quickly. Ask any specific questions and Ill try to help more if needed.
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
all you need to do, is get the permission XML for from face camera device rom (used the one from VIVO), and push it system, via recovery.
adb reboot recovery; adb shell mount -a; adb push android.hardware.camera.front.xml /system/etc/permissions/; adb shell fix_permissions; adb reboot
done
....
PROFIT
PS: this is NOT a flashable zip. but anyone wants to make one, be my guest
thanks to Kali- for the tips
Pushed the xml to the permisions folder with no problems. Ran fix_permissions and rebooted, doesn't appear to have done anything. I can verify that the xml is in the correct folder but google + just doesnt want to do hangouts.
Nexus One running CM7
Any ideas?
EDIT: I was wrong, I thought I would be able to start a hangout but once I found an existing one I was able to join no problem. THANKS!
Qestion
Will it happen if you copy the "android.hardware.camera.front.xml" in folder "/ system / etc / permissions /" by Root Explorer, and then restart the phone?
jossna said:
Will it happen if you copy the "android.hardware.camera.front.xml" in folder "/ system / etc / permissions /" by Root Explorer, and then restart the phone?
Click to expand...
Click to collapse
Yes, you'll either need to manually change the permissions in root explorer to match all the other files in there, or run fix permissions as per the guide
Smtih said:
Yes, you'll either need to manually change the permissions in root explorer to match all the other files in there, or run fix permissions as per the guide
Click to expand...
Click to collapse
Thanks, I try it, but doesn't work
This is how I got mine to work
There were some permissions issues and my phone can't adb anymore for some reason (seems common with the Captivate), so I did the following from Terminal Emulator:
su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock2
# chmod 777 /system
# cp /mnt/sdcard/Downloads/android.hardware.camera.front.xml /system/etc/permissions/.
# chmod 644 /system/etc/permissions/android.hardware.camera.front.xml
[Restart into recovery mode]
[Advanced]
[Fix Permissions]
And it worked! You just can't create your own Hangouts from the phone. You can join others though using your back-facing camera!
Thanks OP!
Jason Schoenbrun
jason schoenbrun gmail
-------------------
Why does xda developers require we create user names? If there's anyone who knows this, please let me know as I'm curious.
I haven't created a non-email username since the days of AOL. Now I have to make a dumb-sounding faux name like "hotmama2385" all over again? I really wish I could use my e-mail address as my persona. If I can't, at least I'd like to know out of curiosity why the design decision was made to exclude that possibility. of course as a protection from spambots I'd want some of my e-mail address hidden behind a CAPTCHA.
I know some people are privacy focused and/or want to be able to troll anonymously. So why not allow a username which can take whatever form we chose - AOL-esque IDs or an e-mail address - as most login services allow?
As an aside, I have the same question for Twitter, which is the reason I haven't signed up for it. I pushed off signing up for XDA by a couple of years until I absolutely had to because of this, and rarely log in because I can't remember that stupid username. (I just started to a little more because of LastPass.)
Nice work... I'll try this one...
hello,
how to fix permission?
with a terminal
I'm not sure what command that is specifically from a terminal, but you can type adb reboot recovery and then fix permissions via menu option once in recovery.
yep, but the problem I haven t a recovery mode. I want to say no menu.
I have an HTC evo 4g with CM 7.2RC1.
I implemented this fix, and rebooted, but still, when trying to do a video call, it stays on "video initializing" and never seems to finish. I have the latest skype from market.
What to do?
just maybe
So I installed the sdk tools, and opened cmd, and then cd to where adb is. I then copy and pasted the entire string "adb reboot recovery; adb shell mount -a; adb push android.hardware.camera.front.xml /system/etc/permissions/; adb shell fix_permissions; adb reboot" and pasted that into cmd is that all I do. I tried dong just "adb reboot recover" and waiting till it entered recovery, but then I couldn't do anything. after I pasted the entire string, my phone rebooted, and took a sec then started back up normally it seemed. So I think I did it correctly.
Perfect!!! Thanks, works like a charm on my Nexus One
great on arc s for hangouts
It's working great on arc s to create hangouts, but it still does not enable video chat in google talk.
I really don't understand why front camera is a pre-requisite for it. I shall be able to see at least the other's video if he has a front cam, even if they don't see me. Any way to workaround this issue of googletalk? (either to trick it to use front cam or just to display an empty frame, but receive other end's video).
I tried the same to see if it would work for Talk on my Defy, but no success
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.