Database Develop

Changed Build.prop and now apps are force-closing...

Alright, didn't find anything related to this elsewhere, so I'm putting it here:
My Bionic is running on 5.9.901, rooted, no issues. I changed the ro.product.manufacturer and ro.product.model values in my build.prop temporarily to test something. Rebooted and the following apps started force closing: Titanium Backup, Swype (latest beta, not built in), Wifi Tether (GoogleCode version, latest alpha), and Flikie Wallpapers HD.
I figure ok, change what I did back to stock and reboot. That should fix the problem.
Nope. These same apps are still force closing on my. Now, here's the twist; I've removed and reinstalled each one with the same results. Somehow, modifying those two variables in my build.prop has changed something that is keeping these apps (and ONLY these apps) from installing/running properly.
Checking the stack traces from the app crashes, Titanium Backup indicates it's unable to find a file located within /data/data/com.keramidas.TitaniumBackup/files. Upon inspection, the entire directory under /data/data for TB contains nothing, even after reinstall. Permissions for /data and /data/data are set to 771. This is as far as I've gotten and I don't know what direction to go next.
Any help is appreciated. Thanks.
EDIT: Forgot to put in here that I've already tried running fix permissions from the bootstrap and that didn't change anything.
EDIT 2: Update. Figured out why the apps are force-closing. For some reason, when they're being reinstalled, the lib files (with the .so extension) are not being created in /data/data. If I open up the APK and copy the .so files to their rightful places, the app will then work fine. If, however, I remove and reinstall again, same thing happens. Something has changed, but I'm unable to figure out what and nothing logical makes sense at this point. Now that TB is working, I might just try a factory reset.

how do you edit build.prop? i have a droid bionic and used rom toolbox to tweak the lcd density and i think it messed something up. i am unable to install pandora or aim as it says my device is not compatible.

Apps not requesting root

Hey all,
So I recently rooted a Kindle Fire 7" HD. The root itself seems to have been successful, and Superuser shows up in the app list. My main issue is that many apps that require root don't appear to be requesting root. For example, I also installed the Google Play store, and a lot of applications were crashing.
Typically my go-to first solution to such a problem is to fix permissions, so I downloaded ROM Manager and ran the fix permissions routine, but the dialog to approve/deny the superuser escalation never appeared. After a few reboots and futzing around with it I was able to get ES File Explorer, the terminal emulator, and the Busybox Installer to escalate permissions (which is how I got Google Play installed in the first place), but I haven't been successful in getting anything else to escalate to root.
Any suggestions? The tablet isn't mine (!), but when I get my hands on it tomorrow I will probably have the SuperUser app update SU and see if that helps. Any other suggestions? Thanks!

[Q] GoogleServicesFramework,apk - Application Not Installed

Here's the situation. :/ I have a Rooted Kindle Fire 2 (not HD) and am having been attempting to REadd the Google Play Store. I've already done it, but a recent(ish) update completly removed it from my device. I know how to do and I already have the required files. However, I've ran into a slight issue and didn't happen the first time. You see... the "GoogleServicesFramework.apk" file simply won't install presents me with the ever annoying "Application Not Installed" error. I REPEAT, my device is already rooted and I use ES File Manager. It's set-up for root and I know my way around the folders. I've disabled the ads, uninstalled a few system apps, and changed my default homescreen. As far as my problem is concerned, I've tried various things.
-Just installing it... FAIL
-Moving to system apps and installing... FAIL
-Moving, rebooting, and installing... FAIL
-Moving, rebooting, setting permissions, and installing... FAIL
-Moving, setting permissions, rebooting, and installing... FAIL
-Moving to system apps and not installing... FAIL
-Moving to system apps, setting permission, and not installing... FAIL
Nope, nada, nein.... nothing has worked. I've checked and its not running in the background with ANY method. I've tried adding the store and linking my Google account (that already my "Kindle%20Fire" on it) anyways and that, of course, has failed,Currently, I have none of the core google files installed or present other then the Download folder. I have tried files from various sources and they all seem to have to the same problem. Does anyone have a solution to this?

Have you installed superuser? Eliminated some the issues you described when I had them
Sent from my KF-HD7

Sound lame but I used the tool from here :
http://forum.xda-developers.com/showthread.php?t=1951254
It has the option to add the framework and all the other stuff too as well as launchers. It sure saved me a long time after I wiped. 20 minutes and I was good to go.

Hey guys! Thanks for replying, but this is no longer an issue. I did a factory reset a couple days ago and now everything works perfectly! ...all my other (unmentioned) issues were fixed as well.

[Q] System UI disappearance

Hi,
I just recently rooted my Xperia Z, I was in the process of installing a modification to the software buttons off of one the users on this site. Unfortunately superuser was denying superuser access to root explorer while I was trying to copy the file over to the system folder.I was unsuccessful at installing the UI modification.
I decided to turn it off and on again to see if that would work; upon turning on my phone I realized that I no longer had any software buttons at the bottom (no home button, no back button... nothing) While it looks nice, as soon as I enter an app I'm stuck as I can't "back-up" out of it.
I checked out my apps in setting.
1# System UI was showing as 0.00b. As in it's gone!
2# I checked root checker, and apparently my device is no longer rooted; also none of my rooted apps are working so I'm incline to believe it.
I have a back up of the System UI on my computer, but no way of putting it on the phone as I'm not rooted. I have tried to re-root using the same method as I have before but it's not working. (It's the "Easy Rooting Toolkit for Xperia Z SO-02E, and it just wont recognize the device; USB drivers are working fine as companion works and I can browse the device using explorer :?)
--
I'd really appreciate it if someone could suggest some solutions to get System UI back on there; even some way to reset the device if possibel!
Thansk

Checked it out again, the System UI is there it seems.
I had a look on Google Play at the application I was last using before my phone pulled a wobbly; I should have looked at the first review (1 star):
Root Browser Lite - JRUMMY APPS INC
"does not work properly on my sony"
"I can browse the file system. But then I tried to create a new folder which failed. It totally screwed up my phone. Now the whole phone is very slow and apps often crash"
- Jost Joller
So this app has obviously screwed up my system,.

ZXperia said:
So this app has obviously screwed up my system,.
Click to expand...
Click to collapse
Sound's like you didn't root properly, so flash a stock ftf and start from scratch.

Lost root and cant re-root

I had my phone rooted and all working fine on Nougat. I then tried installing secure settings for Tasker and since around this time, i've lost root and if i try flashing super su in TWRP, each time i boot and check i'm not rooted. If i open Super Su app it tells me that the framework needs to be updated and to reboot, i do this and it just keeps telling me the same.
The only thing i am thinking may have broken this is i found a guide to get Secure Settings working on nougat where someone suggested creating a folder with root file explorer called 'su' in system/bin. Now when i open up Titanium Backup it tells me it could not acquire root and say the attempt was made using the "/system/bin/su" command which im thinking means it's looking somewhere there is an empty folder?
I cant now of course delete the system/bin/su folder i created as i cant enable root in File Explorer so i'm pretty stuck and not sure what i can do. I've tried the cleanup and full unroot in the supersu app and then flashing supersu in twrp again but still says no root when i check
Any suggestions?

farquea said:
I had my phone rooted and all working fine on Nougat. I then tried installing secure settings for Tasker and since around this time, i've lost root and if i try flashing super su in TWRP, each time i boot and check i'm not rooted. If i open Super Su app it tells me that the framework needs to be updated and to reboot, i do this and it just keeps telling me the same.
The only thing i am thinking may have broken this is i found a guide to get Secure Settings working on nougat where someone suggested creating a folder with root file explorer called 'su' in system/bin. Now when i open up Titanium Backup it tells me it could not acquire root and say the attempt was made using the "/system/bin/su" command which im thinking means it's looking somewhere there is an empty folder?
I cant now of course delete the system/bin/su folder i created as i cant enable root in File Explorer so i'm pretty stuck and not sure what i can do. I've tried the cleanup and full unroot in the supersu app and then flashing supersu in twrp again but still says no root when i check
Any suggestions?
Click to expand...
Click to collapse
This post was a bit more informative than your "my device unrooted itself" post in the stable thread.
Dirty flash your system or use the file manager in TWRP to remove the offending folder.

I was thinking of trying that but fixed it a different way as I just posted in the SuperSU thread. But in case anyone else ever has this problem...
I fixed my issue. By disabling SuperSU and enabling again from the app settings and it gave me root. I then deleted a created su folder in system/bin that I manually created earlier when trying to get secure settings working.