[FIX] Market 3.0+ FC Fix! - Android Software Development

I'm not sure if I'm posting this in the right spot or doing this right so bear with me. And apologizes in advance!
For anyone who is having market FCs I found a fix. Not exactly sure if what I did or what parts were the actual fix.
MUST BE ROOTED THOUGH!
What I did:
1. Boot into clockwork recovery > advanced > fix permissions
2. Wipe dalvik cache and normal cache
3. Boot phone normally
4. Go to settings> applications> manage applications> scroll to market > wipe data/ defaults / cache
5. With astro, es file explorer, root explorer etc go to >root of the phone> system> app> scroll to the market apk > click it and install like a normal apk
BAM! Fixed!... At least for me. Lol
Sent from my SPH-D700 using xda premium

Related

Accidentally installed old market, how to replace with latest?

I accidentally installed an old android market (download917.mediafire.com/holh5mrm74gg/rest29bka7mm0ck/Vending.apk) to my kindle after rooting, I definitely want the latest one and have seen that it's possible in many different youtube video's. Can anybody help me with the removal of the old android market and provide me with a way to install the latest one?
Thank you very much!
1. Install Root Explorer from the market.
2. Deinstall the version you have using the by going to settings > more > Applications > All Applications > Market > Clear Data > Uninstall.
3. Copy attached market APK to your Downloads folder on the Fire.
4. Using Root Explorer, navigate to Downloads and copy market apk.
5. Using Root Explorer, navigate to System/App and click Mount R/W.
6. Paste market apk into folder.
7. Long press Market APK and change permissions to all permissions (or similar to your other system/app apks if you like).
8. Exit Root Explorer.
9. Shutdown and restart KF.
I didn't find "settings > more > Applications > All Applications > Market > Clear Data > Uninstall" under root explorer, but I used File Expert, where I did find something similar. After doing the necessary steps, I indeed managed to reinstall with the new market. Thank you so very much for the help!
ctgchaos said:
I didn't find "settings > more > Applications > All Applications > Market > Clear Data > Uninstall" under root explorer, but I used File Expert, where I did find something similar. After doing the necessary steps, I indeed managed to reinstall with the new market. Thank you so very much for the help!
Click to expand...
Click to collapse
You have to tap the top menu bar on the Fire (where you see the gear icon). You can then see the more (+) button when the menu drops down. The steps are then as I laid out. This is standard OOTB functionality to deinstall an app.
Glad you were able to remove the app via the alt method you found.
terracode said:
1. Install Root Explorer from the market.
2. Deinstall the version you have using the by going to settings > more > Applications > All Applications > Market > Clear Data > Uninstall.
3. Copy attached market APK to your Downloads folder on the Fire.
4. Using Root Explorer, navigate to Downloads and copy market apk.
5. Using Root Explorer, navigate to System/App and click Mount R/W.
6. Paste market apk into folder.
7. Long press Market APK and change permissions to all permissions (or similar to your other system/app apks if you like).
8. Exit Root Explorer.
9. Shutdown and restart KF.
Click to expand...
Click to collapse
dont work for me....
vmonsan said:
dont work for me....
Click to expand...
Click to collapse
You'll need to be more specific if you want help.
Hello,
I have similar problems but I the "uninstall" button is inactive for me. Any idea what to do?
Assuming you properly installed the old version of market just run the new version someone posted on this thread to install it. No need to do anything else. It's no different than any other system app that gets an update. The new version gets installed in /data/apps and gets run instead of the old version in /system.
Sent from my HTC Flyer P512 using Tapatalk

[Q] CyanogenMod file manager not able to switch to root access.

CyanogenMod's file manager seems to be stuck in safe mode, even though I have a rooted device and even have a modified kernel. I've not been able to figure out exactly what's happening. It says that only the accessible file systems are the storage volumes.
Anyone else have this problem, or does anyone know how to fix it?
RogueSly said:
CyanogenMod's file manager seems to be stuck in safe mode, even though I have a rooted device and even have a modified kernel. I've not been able to figure out exactly what's happening. It says that only the accessible file systems are the storage volumes.
Anyone else have this problem, or does anyone know how to fix it?
Click to expand...
Click to collapse
The default for the CM file manager is for root access to be turned off. With the file manager open go into settings and allow root access. Once you exit settings you'll have full access.
Nut_House said:
The default for the CM file manager is for root access to be turned off. With the file manager open go into settings and allow root access. Once you exit settings you'll have full access.
Click to expand...
Click to collapse
That's the problem. It won't allow root access, even though the phone has root access. The menu for the access mode is disabled.
RogueSly said:
That's the problem. It won't allow root access, even though the phone has root access. The menu for the access mode is disabled.
Click to expand...
Click to collapse
Have you tried clearing cache and Dalvik and fixing permissions? The other thing to try, if you haven't already, is downloading the latest nightly and performing a clean install rather than dirty flashing. Good luck.
If you accidentally refused root access the first time you have to go into the SU app and clear out the File manager permission and start over.
Nut_House said:
Have you tried clearing cache and Dalvik and fixing permissions? The other thing to try, if you haven't already, is downloading the latest nightly and performing a clean install rather than dirty flashing. Good luck.
Click to expand...
Click to collapse
I've already tried installing the latest nightly version and ran a permission fix on it, but end up with the same result. I'll try clearing cache, dalvik, and then fixing again.
gharlane00 said:
If you accidentally refused root access the first time you have to go into the SU app and clear out the File manager permission and start over.
Click to expand...
Click to collapse
The file manager doesn't have any permissions in SuperSU and never asks for any since it's not in root access mode. :\
Nut_House said:
Have you tried clearing cache and Dalvik and fixing permissions? The other thing to try, if you haven't already, is downloading the latest nightly and performing a clean install rather than dirty flashing. Good luck.
Click to expand...
Click to collapse
Yeah, still the same result. Clearing dalvik and cache didn't work.
Just grab es file explorer.
Sent from my SPH-L720 using xda app-developers app
RogueSly said:
Yeah, still the same result. Clearing dalvik and cache didn't work.
Click to expand...
Click to collapse
same problem.
tried to install supersu, reinstall busy box on bin and xbin, fix permissions, no luck, option still greyed out.
file manager always worked for me as root, both on cm-based ROMs and aosp.
this time it is not working with the combo saberMod and matrix on N4.
(i think this is a device-independent issue)
---------- Post added at 08:20 PM ---------- Previous post was at 08:07 PM ----------
After a lot of tentatives I solved it.
I am not 100% sure of which change made it though
I think it was by using ES root manager and resetting system as R/W.
Sent from my Nexus 4 using xda app-developers app
Alternate fix
I also had the same issue and resolved it by tapping the menu button on the top left corner. when you do this, another menu button appears in the top right corner. Hit that, then settings, and choose root mode. Took me a while to figure out!!!
solved...
Installing busy box should resolve the issue...
Sorry for bumping, I have busybox and su installed, init.d support as well, but Cyanogen's File manager still cannot access root (option is grayed out). I'm on a stock Prestigio rom. It worked previously, but I reflashed firmware and now it doesn't work on this new firmware. Any thoughts?
Hi terirem and everybody,
I had this issue recently and I've managed to fix it. This is what You should do:
Short run:
Type in rooted phone terminal:
su
am start com.cyanogenmod.filemanager.ics
done
Long run:
1. Of course You need rooted phone, I've installed also BusyBox but I am not sure if it's necessary.
2. Install Terminal application
3. Install (if it's not installed yet) and run cyanogenmod file manager then minimize it by pressing home button (make sure You don't do anything else on Your phone to don't kill file manager process, it needs to be alive for 4th point)
4. I will make all commands bold for easier reading. run your terminal app and type: top -n 1 (this command will list all your running applications just once).
5. Find cyanogenmod in last "name" column, mine has name: com.cyanogenmod.filemanager.ics (if you can't find it you can try the one I had for 7th step, should probably work)
6. Type: su You will be asked to give superuser permissions to terminal, agree. Now instead of $ an # should appear, this means all commands from now on have root privilage.
7. Now we will finally rerun filemanager again with superuser permissions, type: am start com.cyanogenmod.filemanager.ics (if you had different name of filemanager just write the one you got after am start)
8. Go to cyanogenmod filemanager general settings and change access mode to root (it should be finally available, if not make sure again You typed am start with root permissions in terminal, if still doesn't work then forget about point 9).
9. Give me a beer, or actually simple thanks is enough, I need to stop drinking.
My SuperSU is kept auto-granting and system storage is kept read-written, also I cleared the every caches.
The CM file manager is still not shown a root mode to me.
I have J-rummy’s ROM toolbox as an alternative root explorer, but sometimes is less readable than CM file manager.
There is a guy forgetting to let the system storage read-written to remind him.
I did this with CM file manager - make sure you have root access not just safe mode in general settings. When you open filemanger it is granted super U access and then you can edit and save without issues
CM Dev Settings
In Dev options is Root access set to Apps and ADB?
For anyone else still having this problem, just erase the File Manager data (Settings | Apps | File Manager | Storage | Clear Data) with SU turned on in developer options. Then press the hamburger icon in the top-right of the app, press the settings icon on the bottom, click on General settings and you will see Access Mode
bsevcenk said:
For anyone else still having this problem, just erase the File Manager data (Settings | Apps | File Manager | Storage | Clear Data) with SU turned on in developer options. Then press the hamburger icon in the top-right of the app, press the settings icon on the bottom, click on General settings and you will see Access Mode
Click to expand...
Click to collapse
I am on CM13, now with SuperSU installed since I couldn't get the root option there to work well with some other apps for some reason.
File Manager now doesn't show any option for 'safe mode' or otherwise at all in settings. I cleared the data. I started it as in the earlier post. Nothing.
In the Developer options root is allowed, although only for ADB (the apps option has gone).
passtim said:
I am on CM13, now with SuperSU installed since I couldn't get the root option there to work well with some other apps for some reason.
File Manager now doesn't show any option for 'safe mode' or otherwise at all in settings. I cleared the data. I started it as in the earlier post. Nothing.
In the Developer options root is allowed, although only for ADB (the apps option has gone).
Click to expand...
Click to collapse
same here for me.
I'm working on a fix for now.
EDIT
If you're on a systemless SuperSU, use a terminal or ADB shell to input the following lines:
Code:
su
mount -o remount,rw /system
ln -s /su/bin/su /system/xbin/su
id74em8 said:
same here for me.
I'm working on a fix for now.
EDIT
If you're on a systemless SuperSU, use a terminal or ADB shell to input the following lines:
Code:
su
mount -o remount,rw /system
ln -s /su/bin/su /system/xbin/su
Click to expand...
Click to collapse
Apologies, but I'm no expert at these things. What is a 'systemless' SuperSU?
Is making a link as you suggest safe?

Play store error

How to solve error 492 on play store?
Try to clear data,cache from google services,store etc....from settings if not works,then wipe data and cache and dalvik cache from CWM.....
san122 said:
How to solve error 492 on play store?
Click to expand...
Click to collapse
Pls post SS to see ur problem
Sent from my GT-S5360 using xda app-developers app
san122 said:
How to solve error 492 on play store?
Click to expand...
Click to collapse
open phone settings
goto applications
mannage applications
select the all tab
you need to select the following apps and clear data and cache
google play services
google play store
google service framework
now with a file browser that can show hidden folders like root browser delete .android_secure from the root of your sd card (note the folder name starts with a dot)
go into cmw
wipe cache
wipe delvik cache
mount system (if on cm7 common kernel unmount system and mount it twice) data and cache
(if you get any errors in mounting anything you will have to flash stock rom via odin and start again)
flash the correct gapps for the android version you are on
restart
Best way reflash rom !
Sent from my GT-I9500 using Tapatalk
I had this problem for 5 days now, i even reflashed stock and formatted sd card, nothing changed
marcussmith2626 said:
open phone settings
goto applications
mannage applications
select the all tab
you need to select the following apps and clear data and cache
google play services
google play store
google service framework
now with a file browser that can show hidden folders like root browser delete .android_secure from the root of your sd card (note the folder name starts with a dot)
go into cmw
wipe cache
wipe delvik cache
mount system (if on cm7 common kernel unmount system and mount it twice) data and cache
(if you get any errors in mounting anything you will have to flash stock rom via odin and start again)
flash the correct gapps for the android version you are on
restart
Click to expand...
Click to collapse
Nice guide.
Sent from my GT-P3110 using XDA Premium 4 mobile app
If all else fails, use Cache Fixer, though you have to move the cache on each reboot.
reset Apn under setting
works in me
san122 said:
How to solve error 492 on play store?
Click to expand...
Click to collapse
Galaxy ace-i has a flashable zip, try to search.
Inviato dal mio Nexus 7 utilizzando Tapatalk
I fixed it...technically it fixed itself, I moved between 4 or 5 roms and finally i can download apps now

S-Browser (working zip)

When the Verizon S5 first got SS, there was a zip floating around on XDA with the stock browser for the S5. I've been looking and Googling(Googlin?) for it but all the ones I try give me constant fc's.
Anyone have a link or zip of a working version?
jayandare said:
When the Verizon S5 first got SS, there was a zip floating around on XDA with the stock browser for the S5. I've been looking and Googling(Googlin?) for it but all the ones I try give me constant fc's.
Anyone have a link or zip of a working version?
Click to expand...
Click to collapse
Your request is vague, leaving us without a clear idea of what you need. What is wrong with your existing S-browser? For that matter which S5 model and carrier is this for? Are you talking about the SM-G900V on Verizon?
What firmware version do you have? Is your phone rooted? What do you mean when you say "zip"? A zip file is simply a compressed file. Or did you actually mean a flashable zip file which is something different.
You didn't tell us how you tried to install the other S-browser versions.. but the forced closures are usually caused by people failing to wipe cache and data in the settings menu application manager, followed by wiping the phone cache from recovery mode.
.
A cursory Google search suggests that Verizon may not include the necessary S-browser libraries on their phones. Just one more thing that would cause the app to crash. Way to go Verizon. If you have a rooted, Verizon phone then you can install S-browser as follows (or alternate directions here):
Download these two files:
PORTED_S5SBROWSER.7z
libswev8.so
Extract the S-browser files (Sbrowser.apk and SbrowserTry.apk) from the zip to the /system/app/ directory
Confirm that permissions are set to 0644
The three library files (libsbrowser.so, libsbrowser_ext.so, libswev8.so) go to /system/lib/
They require 0644 permissions as well
After rebooting, S-browser will probably work fine for you. But it's good practice to clear the caches, particularly if you had a previous S-browser installation.
Go to the settings menu:
Settings > Applications > Application Manager > All > Internet > Force stop > Clear cache > Clear data > OK
Now go to recovery mode
Confirm that your device is off by removing the battery for a few seconds. Then replace the battery.
Press and hold the volume up, home and power keys at the same time until you see the phone enter recovery mode on the screen
Choose wipe cache from the menu and confirm.
Your phone will then reboot normally. You may see an "Android is updating applications message". This is routine and is just the OS doing a one-time update (rebuild) of your cache.
Enjoy your working S-browser.
.

Device Stock UPSM

My device Stock in USPM and no way that i can turn it off.
here is some ways i read in different threads.
charge 100%
use different launcher
wipe cache
wipe dalvik
and more i don't want to bored you with them.
here is solution i came up with and it solved my problem without lose anything
Requirement:
TWRP recovery
1. reboot to recovery (TWRP)
2. Advanced - File manager
-- look into system\app
-- and change every "emergency " Folder name or
-- or simply rename apk file and delete extension
3. reboot (this is how you get color and full setting)
4. setting - app manager - reset app preference (this is how your all apps working without losing any data (only if you disabled some apps this will enabled them again))
5. reboot to recovery
6. Restore apk files that renamed
7. reboot
8. disable UPSM
9. reboot
and it's done

Categories

Resources