Related
I used to have superuser/root running fine on my Vibrant. Busybox, titanium backup, everything worked.
I went to install RyanZA's lag fix (specifically the update.zip pack with a new superuser app, different busybox, etc someone else made) and started having troubles. The superuser requests were not working.
Now, I tried to go back to the original update.zip on this thread. I have the original Ninja superuser icon, etc. Now, when programs request SU, I can click allow or deny, the program hangs, and then I get:
"Sorry!
The appication Superuser Permissions (process com.noshufou.android.su) has stopped unexpectedly. Please try again."
And my root access is denied.
I've restarted, used different superuser update.zips, all about 10 times each in different combinations. I can't get past this error.
Question: How can I erase all the root crap I have on my phone and start over fresh? I can't even terminal "SU" to enable superuser.
lag fix...? vibrant isnt fast enough for you?
sigeltek said:
lag fix...? vibrant isnt fast enough for you?
Click to expand...
Click to collapse
I like my Vibrant like my women...not slow.
shadow300z said:
I like my Vibrant like my women...not slow.
Click to expand...
Click to collapse
QUOTE OF THE DAY!!!
As for your issue, you may try contacting the person whose update.zip you used and ask what it modifies/any reported issues like yours, and how to fix it. That's your best bet I think.
Have you tried using Clockwork ROM Manager and restoring to a pre-lag fix state? This same problem happened to me when I tried to install the lagfix from an update.zip file that I tried to access by rebooting the phone while holding down the volume and power keys.
The only way I got the lagfix to install properly was to use Clockwork to restore using nandroid, then used the one-click method (connected to the pc, in debugging mode, etc.). Now everything is working perfectly.
BTW, I have read some folks posting that they can't tell the difference between stock and lagfixed... My experience is exactly the opposite. The Vibrant is *much* faster when lagfixed.
scpieps said:
Have you tried using Clockwork ROM Manager and restoring to a pre-lag fix state? This same problem happened to me when I tried to install the lagfix from an .apk.
The only way I got the lagfix to install properly was to use Clockwork to restore using nandroid, then used the one-click method (connected to the pc, in debugging mode, etc.). Now everything is working perfectly.
Click to expand...
Click to collapse
Clockwork was unable to work because superuser kept crashing. I couldn't do ANYTHING root related.
I did solve the problem though, so for anyone else that has the same issue with SU FCing:
Goto: Menu - Settings - Applications - Manage Applications - Menu button - Filter, Choose to show "all" - Find & choose Superuser Permissions in the list - CLEAR DATA.
This fixed the problem for me, hopefully this will help someone else!
shadow300z said:
Clockwork was unable to work because superuser kept crashing. I couldn't do ANYTHING root related.
I did solve the problem though, so for anyone else that has the same issue with SU FCing:
Goto: Menu - Settings - Applications - Manage Applications - Menu button - Filter, Choose to show "all" - Find & choose Superuser Permissions in the list - CLEAR DATA.
This fixed the problem for me, hopefully this will help someone else!
Click to expand...
Click to collapse
I had this same problem (Clockwork couldn't fix permissions because Superuser Permissions kept FC'ing, and lots of google searching resulted in no help until I found this. Saved me from losing a few days of important text messages because I'm an idiot and hadn't backed up prior to doing a cognition update that didn't go well the first time around. THANK YOU!
worked! you the man my gee
Thanks man..
It seems that it happened when I uninstalled some apps. after that I connected my rooted Desire Z to PC, typed "adb shell" and "su" and.... "permission denied" appeared!
Went through some other apps, and none of them had root access! After rebooting phone, Superuser app crashed, and it kept crashing...
I cleared application data for Superuser app, and - voila! I got my root back again!
Thanks!
Have the droid charge. Superuser stopped working. All my apps started failing with "the application superuser has stopped unexpectedly". Clearing the data didn't do anything. I finally cleared data, uninstalled the superuser app and reinstalled it. Back up and running. Thanks everyone!
Been having issues with the most recent few ARHD ROMs (HTC Sensation), superuser force closing, etc. cleared SU data and all is well again! thanks.
So I am trying to load a couple of apks I have and it's been no go. On my Epic I usually just dropbox, open, and install. I tried that and initially got the security message. That is already taken care of via nookcolor tools. So that isn't the issue. My issue is every time I go to install I go to Astro, open the file via the "open app manager," it takes me to the info install page...I click install and it loads into the package installer, excellent...and then it just stalls and the progress bar runs and runs but never progresses. This has happened with every apk I have now tried.
Okay...so I figured I'd just go the little more involved (very little, no need to be that lazy, right) route and adb install. Well carp. All goes well, I adb install blahblah.apk and it starts rolling..."570kb blah..etc pkg /blah/temp/blah"...and just hangs there...never to give me the gratifying "success" message. Again, I have tried this with different apks that I know work and the same results. I restored to stock and rerooted, just in case. Same
I am running stock rooted (manualnooter) at this point, just got the nook day before yesterday (one of the many who jumped at the refurbs). Market apps download fine. I'm a blue dot, if that makes any diff. Likely not but meh.
I have searched and googled and not found the answers...but I know I am missing something elementally simple. My luck I'll look like an idiot and it will be a "did you check to see if you had any gas?" broken down car scenario. I'm okay with that, as long as I'm running again. I'm pretty sure I checked all the out of gas scenarios but I likely missed one or two so... any help is much appreciated. Thanks a ton...
I should know better than trying to write before coffee
Well, My answer is not a "check gas" answer. It's pretty dang weird.
1. Download ES Explorer from the market.
2. Start ES Explorer, hit Menu>Settings. Goto Root Options (NEW) and tick both check boxes. Hit allow when it asks you to.
3. Go back twice, until you see your sd card contents. Find the APK on there and select and hold. Hit copy and then hit the 1st button on the row of buttons (it's an icon of an sd card OR a Home icon) If you see a data folder, go in to it. If not, hit the 1st button again.
3. Once in the data folder, go into the app folder. Pull up the little white tab on the bottom. Tap the APK you wanted to install. It will copy. Once you see the APK's icon in the folder, hit the home button and restart. That should have installed it but it is a slow method. Note that you can Multi-Select APK's by pressing the Multi-select button and pasting them all in the /data/app/ folder.
are you sure you have side loading checked
Settings > applications should be the top box.
fnordsnafu said:
So I am trying to load a couple of apks I have and it's been no go. On my Epic I usually just dropbox, open, and install. I tried that and initially got the security message. That is already taken care of via nookcolor tools. So that isn't the issue.
Click to expand...
Click to collapse
I think he already took care of that. And he is on stock, so there is no Applications setting.
ikingblack, thank you, thank you!
Not sure why but by doing this it somehow unsnafued the package installer as well (fingers crossed). I went through your instructions with a known good apk that would not install for anything before. And there it was after the copy, paste reboot etc. Not too much to ask for...still was confused as to the why of the normal package installer method not working. So I decided to give it (package inst) a go with another known working apk (I had just tested it on my epic) that previously wouldn't install, repeatedly, and now it installed just like it should. Scratching my head in wonder. It shouldn't be the reboot, as I have do so many times...the only difference is the install instructions and adding ES (I'm leaving astro behind I think). All I know is it is working and I am a happy camper (tent is in the back yard...) Thanks again! cheers!
Sure. Also, you can select all the APK's using the 2-file icon at the top and tapping the APKs, then press-and hold on one of the APk's and then go to data app, and keep tapping the APK's you wanna copy. And then reboot. Enjoy your Nook!
Thanks for this, it fixed it, but I don't know why.
I suffered this issue on my dell streak.
It was working fine a couple of days ago when I installed GetJar.
Suddenly today for no reason I can determine:
All APK's I tried the install button in the package installer was not grayed out, but it would not respond when pressed.
I've just been setting up my streak again and installing a lot of software. I'm guessing something must of gone wrong.
Someone on another post suggested JuiceDefender may have caused it but I've not installed that recently.
In my case I did:
(1) Installed esFileExplorer
(2) Copied an apk to the folder /data/app/ as described above
(3) restarted the phone
This did not install the app for me.
(4) Tried running the apk file again. Suddenly the Install button is clickable again?! The app then installed just fine.
(5) Tried a different apk (without copying to /data/app/)
Now that will install fine?!
This is really weird. I can't replicate the issue now (which is good!)
but I also can't tell which action fixed it.
As said above it may have been installing esfileexplorer and giving it root access.
It may have been the act of copying the file that reset something.
It wasn't the reboot, at lease not on its own as i'd already tried it.
Regardless, thanks for the info.
If anyone sees this issue again you might want to just try installing esfileexplorer and see if apk's will then install.
This might help us identify which bit of the process is creating the fix.
Just found another suggestion if anyone is interested:
Some suggests using the 'Fix permissions' option of Titanium Backup. I have no way to test this.
For those interested in getting the fingerprint scanner working on CM7, authentec's datadefender app gives you a temporary work around.
EDIT: I was not the source of the idea, this was based on a post by t0dbld (http://forum.xda-developers.com/showpost.php?p=17449229&postcount=8). My only contribution was to find the names of the data files and spell out the instructions.
Datadefender can't enroll new fingerprints under CM7, but you can use existing fingerprint data. Here is a quick overview of what you need to do to get DataDefender working on CM7.
This has been tested moving from stock AT&T Atrix to CM7 Beta.
Steps:
1. Setup Fingerprint Unlock
2. copy fingerprint data files to SD Card
(/data/am2data.db , /data/am2data.db.meta)
3. Install CM7
4. copy data files from SD Card back to /data directory
t.s.eliot said:
For those interested in getting the fingerprint scanner working on CM7, authentec's datadefender app gives you a temporary work around.
Datadefender can't enroll new fingerprints under CM7, but you can use existing fingerprint data. Here is a quick overview of what you need to do to get DataDefender working on CM7.
This has been tested moving from stock AT&T Atrix to CM7 Beta.
Steps:
1. Setup Fingerprint Unlock
2. copy fingerprint data files to SD Card
(/data/am2data.db , /data/am2data.db.meta)
3. Install CM7
4. copy data files from SD Card back to /data directory
Click to expand...
Click to collapse
This is a great find. Nice easy instructions. Great job, thank you.
CM7 Drugged
So we have to be in stock first right?
from the frenzy atrix
fRenZy-_- said:
So we have to be in stock first right?
from the frenzy atrix
Click to expand...
Click to collapse
Yes, or any build with the fingerprint scanner working. Then follow the instructions.
CM7 Drugged
What if I went from a build with the scanner working and setup my finger print do I still need to flash back or where can I get those files I already made before I flashed to cm7? ?
Sent from my MB860 using XDA App
nucentury08 said:
What if I went from a build with the scanner working and setup my finger print do I still need to flash back or where can I get those files I already made before I flashed to cm7? ?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
you did a /data wipe before installing CM7, so they are gone.
Gonna have to try this...awesome.
Sent from my MB860 using Tapatalk
Can we share the data file?
CyanogenMod7 Beta|FauxKernel 1.3ghz
raunamaxtor said:
Can we share the data file?
CyanogenMod7 Beta|FauxKernel 1.3ghz
Click to expand...
Click to collapse
The data file is according to our fingerprint so unless u want somebody else's print on your phone its best to use your own.
great idea. used it and had it lock go launcher so its as close to locking down initial use as possible.
Before I flash a new ROM, I'd like to know how this affects locking. Presumably CM7 doesn't have a fingerprint lock screen. This was the one feature preventing me from using CM7.
Okay I figured out that you have to use DataDefender. I installed it on stock to see how it works before I install CM7.
y2whisper said:
great idea. used it and had it lock go launcher so its as close to locking down initial use as possible.
Click to expand...
Click to collapse
I did the same thing but if you hit "cancel" on DataDefender's authentication screen, you can use Go Launcher for a few seconds before it locks again. In those few seconds you can launch any app. That isn't a DataDefender. That's a DataAccessMinorInconvenience. Am I doing something wrong or is there no way to secure the phone with a fingerprint?
yeahmann said:
Okay I figured out that you have to use DataDefender. I installed it on stock to see how it works before I install CM7.
I did the same thing but if you hit "cancel" on DataDefender's authentication screen, you can use Go Launcher for a few seconds before it locks again. In those few seconds you can launch any app. That isn't a DataDefender. That's a DataAccessMinorInconvenience. Am I doing something wrong or is there no way to secure the phone with a fingerprint?
Click to expand...
Click to collapse
you're not doing anything wrong, CM7 just doesn't have official fingerprint support yet. if you absolutely have to have it, then just be patient and use a different ROM, or deal with this workaround.
data defender wasn't designed to replace a lockscreen, it was designed to lock down individual applications. sorry for the inconvenience.
yeahmann said:
Okay I figured out that you have to use DataDefender. I installed it on stock to see how it works before I install CM7.
I did the same thing but if you hit "cancel" on DataDefender's authentication screen, you can use Go Launcher for a few seconds before it locks again. In those few seconds you can launch any app. That isn't a DataDefender. That's a DataAccessMinorInconvenience. Am I doing something wrong or is there no way to secure the phone with a fingerprint?
Click to expand...
Click to collapse
1. Yes, as the title indicates, this is a workaround. There is no fingerprint lock screen yet on CM7, but the devs are working it.
2. Yes, you can cancel out of Data Defender. That does give you a short window of time to launch other apps. However, if you have those apps protected with data defender as well, the potential for compromise is limited.
3. Data Defender is definitely a work around and not a replacement. It does have limitations. If you don't whitelist it with a task killer, you've lost a lot of your security. If you accidentally delete your fingerprint data files or they get corrupted, you have no way to restore them. I'm sure there are some other problems as well. However, until CM7 has the full fingerprint functionality, we'll have to make do with hacks and workarounds.
Thanks for this. Useful as a stopgap while the devs work on implementing it fully!
hmmm having issues moving my am2data files to /data in cm7... ive tried adb pushing them with filesystem remounted to rw, root explorer moving them, and the built in file manager moving them but none of them will make them show up in a file manager or in datadefender.
help? pretty pls? =/
EDIT: adb pushed each file like 50 times and works fine now lol idk y
Vicious Von said:
The data file is according to our fingerprint so unless u want somebody else's print on your phone its best to use your own.
Click to expand...
Click to collapse
No, I think the point is, if you wiped before CM7 you only need a friend with stock atrix to generate new data and then copy it over.
You should have done a backup of your stock ROM before you flashed CM7, so you can use unyaffs to extract the files from the backup .iso files. No need to reflash stock then reflash CM7.
Fighto3 said:
hmmm having issues moving my am2data files to /data in cm7... ive tried adb pushing them with filesystem remounted to rw, root explorer moving them, and the built in file manager moving them but none of them will make them show up in a file manager or in datadefender.
help? pretty pls? =/
EDIT: adb pushed each file like 50 times and works fine now lol idk y
Click to expand...
Click to collapse
I used Root Explorer to copy the files to SD and then back again. I didn't have any issues. The Root Explorer GUI also provides an easy way to verify the the permissions match (provided you've noted the correct permissions before copying the files).
I replaced my fingerprint file, in the directory, and installed DataDefender, and locked down my essential apps and it works for those apps, but when I charge my phone overnight, and try to use it the next morning, it doesn't work; meaning, when the screen comes up to scan my finger, it comes up and goes away and goes straight to verification failed. Only way to fix it is a reboot. Anyone else having that problem? Anyone has any suggestions?
I do not expect much because CM7 is in beta but you never know...
Hello everybody
I just updated my Nexus 4 to Lollipop 5.0.1 by wiping it and installing the factory image from Google
The most annoying bug I found is that when the UI prompts me a dialog, it doesn't work.
For example, when I try to install an APK file, this pops up (see Screenshot_2014-12-13-12-27-42.png in attachments), and I can only tap on "cancel". the "install" button doesn't work. Everything else seems to work fine, the navigation bar and scrolling the notification menu from the top of the screen give no problem whatsoever. This doesn't seem to depend on the APK file, nor on how do I send the command (I tried installing with ES file explorer, Dropbox, and an app called Easy Installer). I can't figure out a workaround, so I am unable to install APK's on the phone.
Another example are SuperSU requests (see Screenshot_2014-12-13-12-35-17.png ). Here the situation is worse: nothing in the dialog works, neither "deny", nor "grant", nor the box or the menu that read "ask again". Luckily there is an obvious workaround, as I can just open SuperSU and grant the permissions from there (the dialog in the SuperSU app seems to be proprietary and not from the Lollipop UI)
Probably useful info: I am using stock Android 5.0.1, rooted, with TWRP recovery and I installed Busybox (in /xbin).
I have no idea how to repair this. Can you give me some advice? If not, is there some workaround to the problem of installing APK's?
Thanks for the help and the attention.
P.S. This is my first post on this forum. I looked at the rules, but am new. So if I unknowingly broke some rules or posted offtopic I beg your pardon in advance. I also looked for other threads reporting the same problem, but found none.
I've read some posts where the user experienced the same or similar issues as yours. If I'm not mistaken, the issue was caused by some sort of a screen dimming software.
janedoesmith said:
I've read some posts where the user experienced the same or similar issues as yours. If I'm not mistaken, the issue was caused by some sort of a screen dimming software.
Click to expand...
Click to collapse
You were right. I was using an app called Lux 1.75 (sometimes called Lux Dash) that is an automatic screen dimmer. As soon as I stopped it, everything started working again.
Thanks a lot!
Lux Dash prevents Greenify to automate hibernate
ganileni said:
You were right. I was using an app called Lux 1.75 (sometimes called Lux Dash) that is an automatic screen dimmer. As soon as I stopped it, everything started working again.
Thanks a lot!
Click to expand...
Click to collapse
Yep- it was driving me crazy. Worked fine in KitKat but not Lollipop. Uninstalled Lux Dash and now hibernate works automatically after turning on Greenify in Accessibility.
thanks for the tip- prevented me from going crazy!!
steve
Well Hello there!
Everything was working fine but then that was the problem because devil was prying its eyes on my phone :laugh:
Now I can't click on install button when installing apps from apk file. Cancel button is working fine and also installing apps from app store have no issues as well. I have tried installing other apps and on some them install option is working and those are the apps which do not require any permissions. So the apps with any permission access have problem with Install button.
Everything was working fine but the I installed the last app named Network Monitor mini downloaded from other source and this app has a permission "Draw over other app and Modify system settings" maybe something fishy?! and also while I was typing here, Lg keyboard is not working properly like its automatically autocorrects on its own, turns caps, etc. I was hard time while typing here.
Any help? :crying:
Hi, have you tryed to uninstall "Network Monitor mini" or disable it (the background service) before installing something ?
or you can look at this thread : https://forum.xda-developers.com/showpost.php?p=73405029&postcount=5
jesusdoit said:
Hi, have you tryed to uninstall "Network Monitor mini" or disable it (the background service) before installing something ?
or you can look at this thread : https://forum.xda-developers.com/showpost.php?p=73405029&postcount=5
Click to expand...
Click to collapse
Tried but no luck :crying:
I've tried everything I could. Well there were some topics like this that were around 4 year old which caused due to some apps like lux, screen dimmer, etc. but I don't have anything like that and also this keyboard is causing problem a lot like auto typing, cursor jumping somewhere else, etc. Maybe factory reset is only thing left. Thanks anyway :good:
I had the same Problem a few weaks ago.
To fix it i first download the .apk file again. Then i opened a File Manager (for me it's Es File Explorer) went to the Download folder and clicked on the .apk file, the install Button didn't work. Now You have to click on the recent Apps Button in your navbar and switch to another App and directly switch back to the File Explorer, where the Installation windows is still open. Now i could press the install Button.
Hope this works.
jokuu said:
I had the same Problem a few weaks ago.
To fix it i first download the .apk file again. Then i opened a File Manager (for me it's Es File Explorer) went to the Download folder and clicked on the .apk file, the install Button didn't work. Now You have to click on the recent Apps Button in your navbar and switch to another App and directly switch back to the File Explorer, where the Installation windows is still open. Now i could press the install Button.
Hope this works.
Click to expand...
Click to collapse
Well I did factory reset and the problem was still the same because the first app I installed was ES file explorer and guess what this problem was only occurring in ES file explorer :laugh:
Everything is working fine when I open any apk file with default file manager. :good:
Thanks bro!
This is happening to me and it's the first time ever. I thought the phone was knackered again. I got into a boot loop when I flash the Magisk 17.0 zip from TWRP (the recommended option to install after DL was not visible). Could not get out of boot loop but was able to boot into TWRP so I just flashed Fulmics again (easiest option for me) and restored some backups and downloaded some APKs. Only one APK would install normally but if I pressed the power button and then woke the phone up again with the power button it would work and the "Install" option would no longer be greyed out.
Does anyone know why this is happening and if there is a permanent fix?