So I just flashed Axura 2.2.5.9 and have kernel version 2.6.32.9 and well I wanted to use visual voicemail from Tmobile, but it won't let me install the newest version. So I tried to uninstall the older version that came with the rom and it won't let me.
The uninstall button is grayed out.
When I try to download the newer version from the market it says, "duplicate provider authority."
Thanks
vahdyx said:
So I just flashed Axura 2.2.5.9 and have kernel version 2.6.32.9 and well I wanted to use visual voicemail from Tmobile, but it won't let me install the newest version. So I tried to uninstall the older version that came with the rom and it won't let me.
The uninstall button is grayed out.
When I try to download the newer version from the market it says, "duplicate provider authority."
Thanks
Click to expand...
Click to collapse
easiest way is through Root Explorer, simply delete the .apk file from /system/app
or, if you have ADB on your PC, access your device through adb, and type the following commands:
adb shell
su
mount -o rw,remount /system
cd /system/app
rm nameof.apk
reboot
hope this helps
Well, using the app "Super manager" as my root explorer didn't work, so I ended up purchasing "SystemApp Remover" from the market and it worked well. As for the other method you described above was above my tech level and knowledge so I figured I'd find an easier method with keeping that as a last case scenario.
I got rid of Voicemail notifier, google voice and visual voicemail. Worked like a charm.
vahdyx said:
Well, it didn't work, but I ended up purchasing "SystemApp Remover" from the market and it worked well.
I got rid of Voicemail notifier, google voice and visual voicemail. Worked like a charm.
Click to expand...
Click to collapse
yes thats a good app....but the above methods undoubtedly work. did you even try them? if they didnt work, which method did you try, and what part of it didnt work? they are two of the original ways of removing system apps, theyve been around almost as long as root access for Android was discovered....good things to know and learn
if someone is trying to help you, dont just say the methods dont work.......either admit that you didnt even try, or post what went wrong, cause it couldve been something you did...because if another person who has this same problem sees this thread, they will automatically think these things dont work and will lose solutions to their problem.
^^^this goes for any situation, not just this one
Okay my apologies,
I went to the market and tried to find a root explorer but couldn't find a free one so I downloaded "Super Manager" app
I went into system file and long pressed on the file and tapped delete, the file just sat there. I did it again and it wouldn't delete. I restated my phone and it still didn't work.
So it wasn't necessarily the above method that didn't work it was the app that didn't work. I'll correct the post above as well.
I had a problem with system app remover before as I think it didnt just delete the apk but core processes linked to the apk I had a unbelievable flurry of fc maybe that was just my experience but root explorer is indisputably the easiest way to delete apk's cause you don't need anything other than the phone to do so
Yeah, ditto that @wills, I would advise to just freeze the process in titanium and go from there. I wouldn't remove it.
Don't blame me, blame my keyboard's autocorrection algorithm.
I deleted about 10 apps from system/app using root explorer. Not sure why a lot of the bloat was left in/inluded in the latest axura... I wish apps that can be grabbed for free from the market could be left out. ESPECIALLY the bloat from samsung.
I mean, why include samsung widgets when you removed touchwiz?
Related
It's funny because I installed it once but yesterday I installed the alien Rom because I couldn't install the Camera.apk file so I just started from scratch installing a Rom with the camera.apk already install........so I went to the market and see it's the new one, I hate it.......so I went to applications and deleted market/ the update market file too........then place older version of android market in system/app (r/w) using supermanager and also selected the permission button. Then clicked install. "application not installed"!!!!!! Really so then I was without a Market app so I had to reinstall the Alien Rom. Things are so complicated with this device the Evo you could just replace the apk you're good to go. Deoxed
update: I got it. talk about head------ache. all I did was deleted the market app and replace with the "right" old market.apk file. then i had to delete the updater market.apk file because it kept updating the market app. so I did that and got a error type message which closed the market app down. so Then i went installed the update market.apk file again which didn't install so I said screw this deleted the update market.apk file went back to market app and it works now.... so I dunno
update2: I knew it was too good to be true. Yeah the market.apk installed right but it doesn't download apps. I also tried different market.apk version, then it force close again. Screw this i'm just going to find another Rom that hopefully let's you simply install a APK file. after googling, all this stuff about use ADB/android SDK to install a simple apk app this isn't for me. *sad face So yeah I'll just settle with the new android market forget customizing my phone yep.......
noob_2010 said:
It's funny because I installed it once but yesterday I installed the alien Rom because I couldn't install the Camera.apk file so I just started from scratch installing a Rom with the camera.apk already install........so I went to the market and see it's the new one, I hate it.......so I went to applications and deleted market/ the update market file too........then place older version of android market in system/app (r/w) using supermanager and also selected the permission button. Then clicked install. "application not installed"!!!!!! Really so then I was without a Market app so I had to reinstall the Alien Rom. Things are so complicated with this device the Evo you could just replace the apk you're good to go. Deoxed
Click to expand...
Click to collapse
Just push it to /system/app. You never have to click on install application
Sent from my MB855 using Tapatalk
darktranquility18 said:
Just push it to /system/app. You never have to click on install application
Sent from my MB855 using Tapatalk
Click to expand...
Click to collapse
just "push" it to system/app? I heard that term before but not really sure what you mean unless just drop the market.apk file off in system/app without installing it. Well right now I have the new android market installed with the update.apk file.
Push/Copy. Same thing really, you should just be able to delete out the app and copy the old market into /system/app. Might not hurt to delete the market in the davlik cache as well.
Cryp7os said:
Push/Copy. Same thing really, you should just be able to delete out the app and copy the old market into /system/app. Might not hurt to delete the market in the davlik cache as well.
Click to expand...
Click to collapse
10 posts? umm yea lol. well what I did was went to supermanager(explorer) then went to the old market.apk that's on my sd card click installed ----> "application not installed" maybe I have to install directely on the phone? Ok let's try that--------> "application not install" like does the photon require a "special" type of apk app that only works on the Photon. gosh. Like does your rom have to be doexed or something?
I'm running Alien1 rom......but can someone help because now I'm without android mark
update: wait I think I'm getting somewhere. I deleted the market.apk app then paste the "older" version. then hit run and boom the newer version installed. hmmmmm must not have the right "old" version.
Not exactly sure what my post count has to do with anything. However I'm glad you figured it out. Just an FYI though, when you update an app that comes preloaded on a rom it won't replace that app instead it'll append a "1" onto the new filename and use that instead hence why you needed to delete the updated file before it would recognize the old market that you pushed into the /system/app folder.
noob_2010 said:
10 posts? umm yea lol. well what I did was went to supermanager(explorer) then went to the old market.apk that's on my sd card click installed ----> "application not installed" maybe I have to install directely on the phone? Ok let's try that--------> "application not install" like does the photon require a "special" type of apk app that only works on the Photon. gosh. Like does your rom have to be doexed or something?
I'm running Alien1 rom......but can someone help because now I'm without android mark
update: wait I think I'm getting somewhere. I deleted the market.apk app then paste the "older" version. then hit run and boom the newer version installed. hmmmmm must not have the right "old" version.
Click to expand...
Click to collapse
10 posts or not, he seems to know more than you about this, and he is right.You take the apk file and move it to system/app in your phone memory. You can do this with adb push, or use root explorer to put it there. Don't assume that because someone has a low post count they don't know what they are talking about.
You can also uninstall updates from the application manager. It'll re-update to the latest release, though.
Pew! Pew! Pew! From my Mo-Pho!
http://android-gz.com
bricky23 said:
10 posts or not, he seems to know more than you about this, and he is right.You take the apk file and move it to system/app in your phone memory. You can do this with adb push, or use root explorer to put it there. Don't assume that because someone has a low post count they don't know what they are talking about.
Click to expand...
Click to collapse
I already knew this. That's why i went ahead and replace the files. My problem was why isn't the app working correctly. That seems to be a buggy phone issue because the apk file is in system/app
you can always uninstall the market update then use titanium backup to freeze market updater. When I did it on my Photon I installed the older version of Market (2.2something...) and then used terminal to run about 3 commands that disabled market updater. cant for the life of me find the instructions I followed, but then perhaps my post count isnt high enough for the OP either. Because you know in order to know ANYTHING you have to have a high post count.
schollianmj said:
you can always uninstall the market update then use titanium backup to freeze market updater. When I did it on my Photon I installed the older version of Market (2.2something...) and then used terminal to run about 3 commands that disabled market updater. cant for the life of me find the instructions I followed, but then perhaps my post count isnt high enough for the OP either. Because you know in order to know ANYTHING you have to troll someone over and over.
Click to expand...
Click to collapse
thanks you da man!
Un-rooted, microSD card, GoLauncher Ex, ES File Explorer, App Manager, AnyCut, Button Savior, Dolphin and probably anything else you wonderful people told me I needed to get for it.
There is an app called Ballero (it is in Android Market) this app is to sync up with a knitting and crocheting forum so it doesn't have a lot of people even knowing about it. I have gotten it from this site http://rav.cldellow.com/. Using stock browser. When I try to install I get told that the install has failed. (This has also happened with GoogleServicesFramework.apk, google-earth.apk, Google_Maps_v6.02.apk which I understood should be able to go on an un-rooted NT.) So with the Ballero I have tried to install, copy/paste the apk to systems/apps, unzip it into a folder called ballero and tried to copy/paste that into the systems/apps folder. I'm told that it cannot be done.
So am I missing something? Does this mean that those apps are not for this version? Any advice would be greatly appreciated.
Ballero doesn't show up in Market, so it's not listed as compatible wth the NT. However, I had no problem side-loading it from your link with the stock browser.
I'm pretty sure it requires the Google apps/services be installed as it links to Google Maps to retrieve yarn store data. I don't know about sideloading Google Services Framework, but I think you need this and Google Maps before you can install Ballero.
Maybe you're hesitant, but you really should just root the device. It makes things much more functional. If you follow Indirect's instructions closely (don't worry about the manual method, just use the script) on a PC that hasn't had any Android device drivers on it before, it's very easy and painless. Not that you should need to, but root can easily be undone and the NT restored to factory specs.
The root script should also have the option to install the Google apps and Market for you, which in turn opens a lot of functionality on the NT. (I have no knowledge of sideloading these because the root script did it for me).
I'm pretty sure you can't copy/paste anything to system/app without root permissions.
GreenFuzzer said:
Un-rooted, microSD card, GoLauncher Ex, ES File Explorer, App Manager, AnyCut, Button Savior, Dolphin and probably anything else you wonderful people told me I needed to get for it.
There is an app called Ballero (it is in Android Market) this app is to sync up with a knitting and crocheting forum so it doesn't have a lot of people even knowing about it. I have gotten it from this site http://rav.cldellow.com/. Using stock browser. When I try to install I get told that the install has failed. (This has also happened with GoogleServicesFramework.apk, google-earth.apk, Google_Maps_v6.02.apk which I understood should be able to go on an un-rooted NT.) So with the Ballero I have tried to install, copy/paste the apk to systems/apps, unzip it into a folder called ballero and tried to copy/paste that into the systems/apps folder. I'm told that it cannot be done.
So am I missing something? Does this mean that those apps are not for this version? Any advice would be greatly appreciated.
Click to expand...
Click to collapse
well did you mount the system folder as read and write? the system folder is read only by default, so you need to go into your es file explorer settings to change the permission from read only to read and write.
Thank you very much. You are right I am very nervous about rooting. The more I read here the more I'm learning and slowly getting more confident. Thanks again.
*As you can probably tell his is my first android device. If you know of a good book that teaches more about android os I would be interested in reading it. Thanks again.
I just saw this on the XDA home page. Its a new super user app. As we know, the SU app on CM7 is a little buggy and doesnt always give super user permissions. Maybe this app will work better for us. Im going to be trying it out soon.
http://forum.xda-developers.com/showthread.php?t=1538053
UPDATE: So I installed it and tested all my root apps. Seems to work well. I will give it a day or two and see if I have any of the apps fail to get root permissions. If this works and fixes the SU problems we have, then this is a great thing for us CM7 users.
jsgraphicart said:
I just saw this on the XDA home page. Its a new super user app. As we know, the SU app on CM7 is a little buggy and doesnt always give super user permissions. Maybe this app will work better for us. Im going to be trying it out soon.
http://forum.xda-developers.com/showthread.php?t=1538053
UPDATE: So I installed it and tested all my root apps. Seems to work well. I will give it a day or two and see if I have any of the apps fail to get root permissions. If this works and fixes the SU problems we have, then this is a great thing for us CM7 users.
Click to expand...
Click to collapse
Since I am very familiar with ADB and the command line, I tore apart the apk in the linked thread OP to make sure I understood what was happening during the install. I moved the original su binary and Superuser.apk to my emmc (internal memory card), manually pushed the new files out to my phone, and then rebooted.
Once CM7DX2 came all the way up, I started doing some testing and noticed the the original Superuser APK was still showing up in my app drawer. If DOESN'T appear to be conflicting with the new SuperSU APK, but I'm not sure. I have had a few times of the SuperSU app stop responding and asking to either force close or wait. After hitting wait a few times, I ended up just FCing the app.
Once everything smoothed out, the SuperSU seems to have worked, bu, I was still receiving "not responding" messages from the SuperSU app when apps were asking for Root access.
I am going to also cross-post this to the linked OP thread and see if Chainfire wants more digging into this.
Also, as a side note, I think the reason the CM7DX2 Superuser APK was still appearing is that it MAY be installed as part of 2nd-init. I'm not 100% sure about this.
So, in conclusion, for CM7DX2, I think this needs more digging in to and I will offer to work with Chainfire to see what we can do.
Ciao!
Moon Shadow - NM said:
Since I am very familiar with ADB and the command line, I tore apart the apk in the linked thread OP to make sure I understood what was happening during the install. I moved the original su binary and Superuser.apk to my emmc (internal memory card), manually pushed the new files out to my phone, and then rebooted.
Once CM7DX2 came all the way up, I started doing some testing and noticed the the original Superuser APK was still showing up in my app drawer. If DOESN'T appear to be conflicting with the new SuperSU APK, but I'm not sure. I have had a few times of the SuperSU app stop responding and asking to either force close or wait. After hitting wait a few times, I ended up just FCing the app.
Once everything smoothed out, the SuperSU seems to have worked, bu, I was still receiving "not responding" messages from the SuperSU app when apps were asking for Root access.
I am going to also cross-post this to the linked OP thread and see if Chainfire wants more digging into this.
Also, as a side note, I think the reason the CM7DX2 Superuser APK was still appearing is that it MAY be installed as part of 2nd-init. I'm not 100% sure about this.
So, in conclusion, for CM7DX2, I think this needs more digging in to and I will offer to work with Chainfire to see what we can do.
Ciao!
Click to expand...
Click to collapse
Thanks Moon Shadow. The only time I had it hang on "asking for root access" is with Titanium Backup. I think that had to do with the SuperSU app freezing though when trying to get into the settings tab in the app. It just freezes up when selecting that and I had to go into application seetings and manually force stop the app. After that, everything worked fine. I think its just that settings tab for some reason.
The way I installed it was installed SuperSU from the market, then uninstalled the old Super User through the market. I then opened SuperSU and it asked to update so I did. After that, I went through all my root apps and the new SuperSU prompt popped up for all and I granted access. I too see the old SU in the app drawer. Opening that though shows that the only thing that its granting root access to is the new SuperSU app. It doesnt seem to be conflicting with anything so far.
Moon Shadow - NM said:
Since I am very familiar with ADB and the command line, I tore apart the apk in the linked thread OP to make sure I understood what was happening during the install. I moved the original su binary and Superuser.apk to my emmc (internal memory card), manually pushed the new files out to my phone, and then rebooted.
Once CM7DX2 came all the way up, I started doing some testing and noticed the the original Superuser APK was still showing up in my app drawer. If DOESN'T appear to be conflicting with the new SuperSU APK, but I'm not sure. I have had a few times of the SuperSU app stop responding and asking to either force close or wait. After hitting wait a few times, I ended up just FCing the app.
Once everything smoothed out, the SuperSU seems to have worked, bu, I was still receiving "not responding" messages from the SuperSU app when apps were asking for Root access.
I am going to also cross-post this to the linked OP thread and see if Chainfire wants more digging into this.
Also, as a side note, I think the reason the CM7DX2 Superuser APK was still appearing is that it MAY be installed as part of 2nd-init. I'm not 100% sure about this.
So, in conclusion, for CM7DX2, I think this needs more digging in to and I will offer to work with Chainfire to see what we can do.
Ciao!
Click to expand...
Click to collapse
Kind of random but Moon, you are a goddamn machine. The moment something great releases you take it apart and make it better. Good **** man, good ****.
Just including my experience...
SuperSU is working like a champ, but had major issues until I removed Superuser completely.
Here's how I installed:
- Install SuperSU from market
- Uninstall Superuser from settings > applications
- Launch SuperSU and allow it to update it's binary
- Delete superuser.apk from system/apps (use root explorer, es file explorer, terminal, etc...)
- Reboot
Since changing over to SuperSU, I haven't seen a single hang while an app is requesting su permissions.
xawen said:
Just including my experience...
SuperSU is working like a champ, but had major issues until I removed Superuser completely.
Here's how I installed:
- Install SuperSU from market
- Uninstall Superuser from settings > applications
- Launch SuperSU and allow it to update it's binary
- Delete superuser.apk from system/apps (use root explorer, es file explorer, terminal, etc...)
- Reboot
Since changing over to SuperSU, I haven't seen a single hang while an app is requesting su permissions.
Click to expand...
Click to collapse
Same here. This new SU seems to fix the issue we had with the old one. The only problem is that damn settings tab. It freezes the app.
Sent from my MB870 using Tapatalk
i find this relevant to my interest any one else test
Xb0i said:
i find this relevant to my interest any one else test
Click to expand...
Click to collapse
Follow xawen's directions and you'll be fine. It works like a charm.
Sent from my MB870 using xda premium
cant uninstall superuser from settings- applications. doesnt give the option
Xb0i said:
cant uninstall superuser from settings- applications. doesnt give the option
Click to expand...
Click to collapse
Did you go Settings> Applications> Manage Applications and hit the app? If you dont see that option, go into Titanium Backup (an app you have no excuse not having) and uninstall it. Then go into Root explorer and follow the above directions to totally remove it. Then reboot. It may seem like it isnt totally gone cause you may see the icon somewhere, but it likely is gone and a reboot is needed in order to confirm.
yea got the tiBu. but i tried force stopping and clearing data and uninstall never popped up. thought about removing in TiBu buts thats not what it said in the instructions.
Xb0i said:
yea got the tiBu. but i tried force stopping and clearing data and uninstall never popped up. thought about removing in TiBu buts thats not what it said in the instructions.
Click to expand...
Click to collapse
Its what I did. Its a bit of a deviation but it got the job done and thats what matters, ya know?
wow pretty bizzare i cant find superuser in TiBu! whats goin on lol
Xb0i said:
wow pretty bizzare i cant find superuser in TiBu! whats goin on lol
Click to expand...
Click to collapse
Did it disappear after you rebooted? If you have root explorer, go into system/app and see if SU is still gone. If so, you're in good shape.
to clarify
before i even started i backed up original superuser.apk to a folder on sdcard from root explorer, then
i downloaded supersu from market.
went to settings-app-manage apps- etc no choice to uninstall. force stopped- cleared data, still no uninstall option.
went into titanium backup to uninstall from there and superuser wasnt even listed in the apps! (ok weird)
only option left is to just delete from root explorer then continue continue to launch supersu, update binaries and reboot but im holding off.
Lowend was supersuper listed in titanium for u? y isnt it showing up in my list. i find it odd
Xb0i said:
to clarify
before i even started i backed up original superuser.apk to a folder on sdcard from root explorer, then
i downloaded supersu from market.
went to settings-app-manage apps- etc no choice to uninstall. force stopped- cleared data, still no uninstall option.
went into titanium backup to uninstall from there and superuser wasnt even listed in the apps! (ok weird)
only option left is to just delete from root explorer then continue continue to launch supersu, update binaries and reboot but im holding off.
Lowend was supersuper listed in titanium for u? y isnt it showing up in my list. i find it odd
Click to expand...
Click to collapse
I can't find superuser in TB either... it is kind of weird...
i believe u cant delete superuser from tibu cus u need superuser for root access so its like a paradox. i dunno y instructions were as someone showed cus it seems the only way to get this to work properly is delete from root explorer. but im gunna hold off till someone confirms this more legit
I don't understand why you're holding off...if SuperSU is active, go for the reboot and see if the old superuser app clears.
Sent from my MB870 using xda premium
id rather not have a headache if it messes something up.
this thread however gives some detail on supersu
looks like sum apps look for the presence of superuser.apk in data/app and possibly system/app.
a dummy file looks like it can resolve issues. ill switch when more testing is done on CM7dx2.
forum.xda-developers.com/showthread.php?t=1538053
Xb0i said:
id rather not have a headache if it messes something up.
this thread however gives some detail on supersu
looks like sum apps look for the presence of superuser.apk in data/app and possibly system/app.
a dummy file looks like it can resolve issues. ill switch when more testing is done on CM7dx2.
forum.xda-developers.com/showthread.php?t=1538053
Click to expand...
Click to collapse
It's odd that you guys don't see the uninstall option for it... Do you see it in Market (err...Google Play, stupid name)? That's another way to get the uninstall done. If it doesn't show up there, you should be able to use root explorer and delete it from /data/apps and /system/apps.
When we installed CM7, the instructions had us update Superuser from market. That would have installed it in /data/apps, so it just needs to be yanked from there. Uninstall via market, tibu, settings>apps or manual through root explorer should all do the same thing. Then you can delete the built in one from system.
Also, if for some reason the whole process breaks down on you...there's a flashable version of the original Superuser that will probably get you going again. I haven't tried it on CM7 though...
jsgraphicart said:
Same here. This new SU seems to fix the issue we had with the old one. The only problem is that damn settings tab. It freezes the app.
Click to expand...
Click to collapse
The most recent update (pushed yesterday) fixed this for me.
Hello
I was wondering if anyone could help me. Im using awd lancher and installed an antteck app manager and froze a moto app by mistake, the phone got in to a force close loop which even a restart couldnt fix. I managed to uninstall the app by grabbing time between the forced closes.
Now it says " this is not a motoblur device" when I try to use the moto default home launcher.
I have reinstalled the antteck app which shows no frozen apps.
Would a reset to factory work? My concern is if there is no ADW launcher and motoblur is still not working my phone will not work.
Orange UK rooted on gingerbread stock
Thanks for any help
jonnym
Jonnym said:
I managed to uninstall the app by grabbing time between the forced closes.
Click to expand...
Click to collapse
Which app? The one you froze?
Jonnym said:
Would a reset to factory work?
Click to expand...
Click to collapse
No, a factory reset just wipes the data partition.
A possible solution
If you know how to use ADB, and know where to acquire the ADW.Launcher APK, then you could do this:
NOTE: You may need root to do this. I have no idea, actually.
Copy ADW.Launcher to your ADB folder and rename it to launcher.apk to make things easier later.
Open Command Prompt, and CD to your ADB folder.
Type "adb remount" to mount /system as writeable.
Type "adb push launcher.apk /system/app.
You could possibly get away with pushing it to /data/app, but I've never tried pushing to /data before.
The app I uninstalled was the antteck app manager used to freeze the app.
I cant remember exactly which app I froze. It was one from a list of apps safe to freeze I found on the XDA forum, it wasnt safe. It may well have been the moto home launcher as I was trying to free up ram for the webtop.
I get the problem when I use home switcher to try to launch the original home rather than ADW
I no longer see the moto home launcher in the app list on the app manager.
I could try flashing with the sbf, but being a noob im not ready to do that unless all else fails.
Any help gratefully received
Jonnym
I just renamed blurhome.apk_fro to blurhome.apk in the system/app folder using root explorer and all has been fixed. It would seem that although I reinstalled the antteck app manager it doesn't search for previous frozen items. It also didn't show up in titanium backup either that can be used to freeze apps, not a criticism just an observation.
Thanks for all the help
Jonnym
Jonnym said:
I just renamed blurhome.apk_fro to blurhome.apk in the system/app folder using root explorer and all has been fixed. It would seem that although I reinstalled the antteck app manager it doesn't search for previous frozen items. It also didn't show up in titanium backup either that can be used to freeze apps, not a criticism just an observation.
Thanks for all the help
Jonnym
Click to expand...
Click to collapse
Glad you learnt something new. =D
And you should find the "safe" list you referred to and tell them its actually NOT safe.
Ill look for the list later...although it might have been a of stupidity and not on the list at all, I tend to do these things late at night
I'm currently rooted and restoring my apps, however it seems like with each new version of Android the external SD gets trickier and trickier. A lot of apps these days use the round about method of having you choose the card to write to via the file manager, unfortunately not all apps do this and one of them looks to be the ever popular Tasker. am I missing the option or am I screwed and have to rewrite all my tasks to write to the internal storage?
another issue is with Secure Settings mainly used in conjunction with Tasker... when I start it up it fails to recognize su and never prompts me via SuperSU for permissions to grant. anyone have any workarounds or fix for this?
lastly, is BusyBox still usable under Marshmallow? i loaded it up and everything seemed fine, but after a reboot Google Play Services, Amazon, Youtube and some others kept crashing.
My observations:
MyProfiles Pro not able to turn data ON/OFF with ROOT permissions even if the root permission is there for the app.
One Power Guard battery app works, but cannot tweak the profiles, it says root needed. I seriously doubt if it really is working.
njaustin123 said:
My observations:
MyProfiles Pro not able to turn data ON/OFF with ROOT permissions even if the root permission is there for the app.
One Power Guard battery app works, but cannot tweak the profiles, it says root needed. I seriously doubt if it really is working.
Click to expand...
Click to collapse
what I've realized is that SuperSU is running in systemless mode, which is causing some issues for outdated apps that were hardcoded to find 'su' in /system. some workarounds are putting a dummy file named su in /system or getting SuperSU to run in /system.
dimm0k said:
I'm currently rooted and restoring my apps, however it seems like with each new version of Android the external SD gets trickier and trickier. A lot of apps these days use the round about method of having you choose the card to write to via the file manager, unfortunately not all apps do this and one of them looks to be the ever popular Tasker. am I missing the option or am I screwed and have to rewrite all my tasks to write to the internal storage?
another issue is with Secure Settings mainly used in conjunction with Tasker... when I start it up it fails to recognize su and never prompts me via SuperSU for permissions to grant. anyone have any workarounds or fix for this?
lastly, is BusyBox still usable under Marshmallow? i loaded it up and everything seemed fine, but after a reboot Google Play Services, Amazon, Youtube and some others kept crashing.
Click to expand...
Click to collapse
I learned this the hard way in updating from LP to MM; do NOT restore your apps from a backup under LP. I did that, and was having nothing but issue after issue. Best bet, backup everything not an app, go back to the google play store, and reinstall everything from there. Any apk's you had you installed, install them fresh. I was literally to the point of shipping the phone back to T-Mobile and going to an S7 it was such a pain in the neck. After I learned after the 4th factory reset from LG Bridge, I've never had any issues since.
chernabog88008 said:
I learned this the hard way in updating from LP to MM; do NOT restore your apps from a backup under LP. I did that, and was having nothing but issue after issue. Best bet, backup everything not an app, go back to the google play store, and reinstall everything from there. Any apk's you had you installed, install them fresh. I was literally to the point of shipping the phone back to T-Mobile and going to an S7 it was such a pain in the neck. After I learned after the 4th factory reset from LG Bridge, I've never had any issues since.
Click to expand...
Click to collapse
Whenever you do a clean fresh flash Rom at the setup most rooms let you restore all your previous apps from google, no need to go to the play store it does it automatic. If you made a backup just restore the data.
Sent from my LG-H901 using XDA-Developers mobile app
dimm0k said:
what I've realized is that SuperSU is running in systemless mode, which is causing some issues for outdated apps that were hardcoded to find 'su' in /system. some workarounds are putting a dummy file named su in /system or getting SuperSU to run in /system.
Click to expand...
Click to collapse
Thanks. But can you give me little bit more details on that. How can I get SuperSU to run in /system? I checked settings of SuperSU app, but could not find.
Also I tried to create a new file called su in /system with Root Browser of ROM Toolbox, but it says 'failed'
chernabog88008 said:
I learned this the hard way in updating from LP to MM; do NOT restore your apps from a backup under LP. I did that, and was having nothing but issue after issue. Best bet, backup everything not an app, go back to the google play store, and reinstall everything from there. Any apk's you had you installed, install them fresh. I was literally to the point of shipping the phone back to T-Mobile and going to an S7 it was such a pain in the neck. After I learned after the 4th factory reset from LG Bridge, I've never had any issues since.
Click to expand...
Click to collapse
I have witnessed this, mainly with Google apps. after restoring the app with data the app would randomly crash... removing the app and installing it from Google fixes it, but I have not experienced this with non-Google apps. I'll keep this in mind the next go around when restoring my stuff.
njaustin123 said:
Thanks. But can you give me little bit more details on that. How can I get SuperSU to run in /system? I checked settings of SuperSU app, but could not find.
Also I tried to create a new file called su in /system with Root Browser of ROM Toolbox, but it says 'failed'
Click to expand...
Click to collapse
you won't be able to change SuperSU to be in systemless mode within SuperSU... look here for the non-systemless root method that you'll need to flash in TWRP. realize that if you do this flash that it most likely will break Android Pay. not sure if you need to mount /system as rw in Root Browser before you can create files there or if Root Browser does it for you automatically?
I am having issues with the camera in manual mode it keeps force closing
Sent from my LG-H901 using XDA-Developers mobile app
after doing some research and from my understanding, the bad news is that it looks like it's up to devs to add the feature of writing to the external SD via the Storage Access Framework (SAF). unfortunately it doesn't look like an easy task, as the developer of Tasker mentioned that he won't be implementing this since the number of external SD users are far and few =( and would revisit it if that number changes.
the good news for those of us smart and brave enough to root our devices, this is solvable via editing packages.xml and adding in one line for each app you want to "fix". this is documented here
justice26 said:
I am having issues with the camera in manual mode it keeps force closing
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
works fine for me here... are you using stock ROM?
dimm0k said:
you won't be able to change SuperSU to be in systemless mode within SuperSU... look here for the non-systemless root method that you'll need to flash in TWRP. realize that if you do this flash that it most likely will break Android Pay. not sure if you need to mount /system as rw in Root Browser before you can create files there or if Root Browser does it for you automatically?
Click to expand...
Click to collapse
I don't want to break stuff like Android Pay though I am not using it right now.
And about putting the file, in ROM Toolbox it says rwxr-xr-x for /system. Doesn't that mean write is there?
njaustin123 said:
I don't want to break stuff like Android Pay though I am not using it right now.
And about putting the file, in ROM Toolbox it says rwxr-xr-x for /system. Doesn't that mean write is there?
Click to expand...
Click to collapse
I believe non-systemless root only breaks Android Pay because of the way Android Pay is designed, as I believe it needs /system to be "pure". just want you to know that I have not done anything and have left everything as is, systemless root. seems like the only app I had that needed root was Secure Settings, which doesn't look like it will ever be updated anytime soon so I'm trying to ween myself away from that and do everything via Tasker without that plugin. as for you, if you're lucky, write to the apps you're having issues with and have them update it for systemless root. the issue is that their apps were looking for root specifically in /system, but with systemless root the su binary is now in /su/bin. as for putting a dummy su file in /system, I'm not entirely sure that would make your apps work and if it would break Android Pay if you did so. regardless, it doesn't hurt to try as you can simply remove the dummy su file to revert back to systemless. I believe those permissions you've listed for /system does does mean it can be written to, however it has to also be mounted as rw. check that via a terminal by issuing "mount | grep /system". you will probably see a ro in parenthesis or simply try to put a file in there.
dimm0k said:
I believe non-systemless root only breaks Android Pay because of the way Android Pay is designed, as I believe it needs /system to be "pure". just want you to know that I have not done anything and have left everything as is, systemless root. seems like the only app I had that needed root was Secure Settings, which doesn't look like it will ever be updated anytime soon so I'm trying to ween myself away from that and do everything via Tasker without that plugin. as for you, if you're lucky, write to the apps you're having issues with and have them update it for systemless root. the issue is that their apps were looking for root specifically in /system, but with systemless root the su binary is now in /su/bin. as for putting a dummy su file in /system, I'm not entirely sure that would make your apps work and if it would break Android Pay if you did so. regardless, it doesn't hurt to try as you can simply remove the dummy su file to revert back to systemless. I believe those permissions you've listed for /system does does mean it can be written to, however it has to also be mounted as rw. check that via a terminal by issuing "mount | grep /system". you will probably see a ro in parenthesis or simply try to put a file in there.
Click to expand...
Click to collapse
OK, so here is it: I was able to mount /system as rw with the terminal emulator in ROM toolbox and then create a dummy file named su. Rebooted the phone, both the apps still fail. I will write to the developers. For the time being, I am OK turning data on/off manually along with using MyProfiles for other things. And for the One Power Guard, I believe freezing many of the T-Mobile and LG junk using Titanium and having SetCPU with a little bit under-clocking have already made the battery better. So I can wait. Am also evaluating Craig's Root Battery App instead of OPG. Thank you anyways.