I moved an apk to the system folder but forgot to reset permissions now I have a bootloop, is there a way to access the system folder and remove this file with PC using adb or flashtool, LP 5.1 270 installed and rooted
is it possible to only flash the part of the ftf that overwrites the system folder using flash tool, I am downloading the FTF right now - would system.sin be the correct file to flash therefore keeping everything else as is
any help please
ok so I sorted this out myself and anyone in the same situation this may help
first as described above I moved an app to the system folder thinking it might fix something but it didn't and as it turns out the app developer has a bug they need to address, it was my favourite file manager that needs attention, I moved it to the system folder thinking it would solve all the issues I was facing with permissions etc but I conclude it is the app itself is buggy under LP, and as usual they are slow to sort this out and I paid for it......never mind
so the steps
updated to LP
rooted using kingroot (those that follow this path need to go to apps "kinguser" and force stop before running the script to swap out for supersu) then it works
so back to my problem (self inflicted)
because of my attempts to try and sort the app that wasn't working properly I thought if I made it a system app it would fix it, it didn't and not only that I forgot to change the permissions when I moved it to the system folder, when I rebooted the phone it went into a bootloop
so I wanted to avoid doing a complete factory reset or repair as I'm sure you all understand, lots of stuff gets lost
so I used xperifirm and downloaded the software that was updated LP 270
compiled an ftf using flashtool
ran flashtool and selected to update the firmware on my device
opted for the option - not to erase any user data
selected the absolute minimum of files to be updated
flashed phone
and now it is working, all settings as they were before - no data loss
I had to run kingroot again but that worked to perfection once I force stopped kinguser in settings / apps
hope this helps someone else
Related
recently rooted and running cyanogen 4.1.999, prior to that I ran each release from 4.04 on. at least from 4.11 on, i've noticed something strange happening to my system that I can't quite figure out the cause. Off a fresh install, package installer works for loading .apks from the card. Somewhere along the way though, it stops working; I'll try to install an app and it will keep looping, bringing me back repeatedly to the install screen where it shows permissions and asks to install or not.
I've checked and unchecked 3rd party install permission, no change. I also tried fix permissions and that doesn't help, Only a wipe gets it working again until the next time it fails. Installing an app from the market works just fine, just can't install independently unless I sneak the apk into my system backup folder and restore via system app backupper, but that is a limited option since the program then becomes uninstallable. No other issues i've noticed on these roms, just the installer. Anyone experience similar or have some input on the matter?
you should try and repair ext filesystems in recovery if you have apps2sd. please report back if it works
nope
ext filesystem repair does not fix the installer loop
this only happens on cyan 4.1 and greater?
is it with a specific app? also did you flash the single flash rom or did you install by cyanogens official install method
I tried posting this in the app and themes forum but had no luck, I have an issue with the Medscape app. I wasn't able to update the library so I uninstalled the app and manually deleted the library files from me Medscape folder, later I learned that the update problem was because of the adblock app. I solved that and tried to reinstall Medscape, so far so good. When I try to re install the library files, the app tells me theres no update available (???) and it shows the current files as if they are installed, but the folder is still deleted and when I try to look up something in the database, nothing comes up.
Is there a way to wipe completely the Medscape db registry so I can do clean install?
Thanks a lot
Sent from my GT-I9000 using XDA App
I had the exact same problem and I wasn't able to solve it... Only a factory reset did it...
I'm not root but if you are root go to /data folder and delete medscape info from that. I think it might work.
The problem is that you deleted the Mescape folder from your SD card but it contains a database file (maybe the index of articles) so anything you search returns nothing!
The solution would be to delete that old account information and data, and I think it resides in the /data folder but I can't confirm that because I'm not root.
Thanks for the suggestion, but it didn't work. Nothing related to medscape on the /data folder. I'll keep looking or I'll clean install when I flash Gingerbread
Sent from my GT-I9000 using XDA App
Having similar Medscape problem, this time I cannot delete Medscape pics/icons in my Gallery. Practically FC's whenever I try to open.
These are .PNG files - is there a trick to delete these?
===
UPDATE: I discovered that I could delete one of the PNG pics in the Gallery folder but not delete a second one - the Gallery app would freeze. It actually required a power ON/OFF to "reset" the gallery folder (whose ("number of files") did show that the pic was indeed deleted) and permit me to delete another image. For some reason, as I was fiddling with the FILES app, a Medscape folder popped up (it hadn't appeared before) and it had hundreds of low-kb files in it, including the PNGs. Luckily I was able to delete this Medscape folder without a hitch... other than the 2 minutes it took to actually delete. And wouldn't you know it: my Epic is running faster than ever. What is in that Medscape app I wonder...
===
cheers/dom
My issue is another,
I m using SG2 rooted, i removed my ad blocker and re install Medscape.
So i finaly managed to start instaling the resaurces .... the resaurces started from 1 of 24 ...and downloading ...
Is it logical to keep downloading ...after the 24 ... has been downloaded already?
for example 34 of 24 ...and keep going??
Hi!
I've a problem when trying to update my Medscape app. When I try to get ref updates, it suddently appears: "Not able to complete download at this time"
I've read this post , where they speak about ad blocking apps causing this problem, however I'm using cyanogenmod CM11 M12, without any apps of this kind, more over, I searched for Hosts file, and when I open it, there's only this line: "127.0.0.1 localhost". I don't know what else to do, I've tried unistalling the app, cleaning all data before so, In deed, I've also tried to do a clean install of CM11 M12, with no luck.
Wish you could help me!
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.
I have been trying to get "gsam root companion" to work on my htc one. I've rooted my device just so i could check out the features such as wake lock, etc.
The thing is, it keep saying "The Root Companion application is not installed correctly in /system/priv-app."
I tried manually installing it by copying the "com.gsamlabs.bbm.rootcomanion-1.apk" (whether or not if its the correct file) into the system/priv-app location. That restarted my device, and the file just disappeared from the priv-app location as well, and so the problem persist.
Am i doing everything wrong manually. Wish I could find a tutorial vid =/.
Thank you in advance
elfking7 said:
I have been trying to get "gsam root companion" to work on my htc one. I've rooted my device just so i could check out the features such as wake lock, etc.
The thing is, it keep saying "The Root Companion application is not installed correctly in /system/priv-app."
I tried manually installing it by copying the "com.gsamlabs.bbm.rootcomanion-1.apk" (whether or not if its the correct file) into the system/priv-app location. That restarted my device, and the file just disappeared from the priv-app location as well, and so the problem persist.
Am i doing everything wrong manually. Wish I could find a tutorial vid =/.
Thank you in advance
Click to expand...
Click to collapse
in order to write/modify/delete file in /system, you need an unsecured kernel (/system writeable), otherwise all changes made to /system will be reverted at reboot. I'm not using and never used gsam, maybe there is another option but the only one I know is to flash a custom kernel.
Kernel for the htc one (M7) are listed here
make sure to chose one that is compatible with your rom (sense/gpe based or AOSP based)
elfking7 said:
I have been trying to get "gsam root companion" to work on my htc one. I've rooted my device just so i could check out the features such as wake lock, etc.
The thing is, it keep saying "The Root Companion application is not installed correctly in /system/priv-app."
I tried manually installing it by copying the "com.gsamlabs.bbm.rootcomanion-1.apk" (whether or not if its the correct file) into the system/priv-app location. That restarted my device, and the file just disappeared from the priv-app location as well, and so the problem persist.
Am i doing everything wrong manually. Wish I could find a tutorial vid =/.
Thank you in advance
Click to expand...
Click to collapse
I just fiddled with this the other day, but didn't use the Root Companion app. It's not the Root Companion apk that's moved to /system/priv-app. It's the actual GSam Battery Monitor apk, com.gsamlabs.bbm.apk. The Root Companion app just does the move for you. If you have a file manager with root r/w permission, you should be able to do it yourself. Just move com.gsamlabs.bbm.apk from /data/app to /system/priv-app. Then restart your phone. I actually used an app called Link2SD to convert GSam Battery Monitor from a user app to system app and it accomplished the same thing.
alray said:
in order to write/modify/delete file in /system, you need an unsecured kernel (/system writeable), otherwise all changes made to /system will be reverted at reboot. I'm not using and never used gsam, maybe there is another option but the only one I know is to flash a custom kernel.
Kernel for the htc one (M7) are listed here
make sure to chose one that is compatible with your rom (sense/gpe based or AOSP based)
Click to expand...
Click to collapse
I'm running the stock AT&T 4.4.2 ROM rooted with the stock kernel and haven't had any issues with changes reverting back after a reboot. I use ES File Explorer & set it to have R/W permissions in that app's settings, but I assume that only applies to that app. Yet I've converted a few apps from user apps to system apps (3rd party launcher GSam Battery Monitor & SuperSU are the ones I remember off the top of my head) and never noticed them switching back to user apps. That is until I update them; then they become user apps. I don't know if this is because the apps I'm using to switch them have SU permissions or what, but none have changed back by simply rebooting. And as far as I know, I haven't done anything to modify the stock kernel from the OTA. Is it even possible to unsecure a stock kernel using apps?
alray said:
in order to write/modify/delete file in /system, you need an unsecured kernel (/system writeable), otherwise all changes made to /system will be reverted at reboot. I'm not using and never used gsam, maybe there is another option but the only one I know is to flash a custom kernel.
Kernel for the htc one (M7) are listed here
make sure to chose one that is compatible with your rom (sense/gpe based or AOSP based)
Click to expand...
Click to collapse
Thank you so much. I had this problem for days. Why isn't my unlocked phone writeable in the first place...
sharksfan7 said:
I just fiddled with this the other day, but didn't use the Root Companion app. It's not the Root Companion apk that's moved to /system/priv-app. It's the actual GSam Battery Monitor apk, com.gsamlabs.bbm.apk. The Root Companion app just does the move for you. If you have a file manager with root r/w permission, you should be able to do it yourself. Just move com.gsamlabs.bbm.apk from /data/app to /system/priv-app. Then restart your phone. I actually used an app called Link2SD to convert GSam Battery Monitor from a user app to system app and it accomplished the same thing.
I'm running the stock AT&T 4.4.2 ROM rooted with the stock kernel and haven't had any issues with changes reverting back after a reboot. I use ES File Explorer & set it to have R/W permissions in that app's settings, but I assume that only applies to that app. Yet I've converted a few apps from user apps to system apps (3rd party launcher GSam Battery Monitor & SuperSU are the ones I remember off the top of my head) and never noticed them switching back to user apps. That is until I update them; then they become user apps. I don't know if this is because the apps I'm using to switch them have SU permissions or what, but none have changed back by simply rebooting. And as far as I know, I haven't done anything to modify the stock kernel from the OTA. Is it even possible to unsecure a stock kernel using apps?
Click to expand...
Click to collapse
You just used your stock kernal 0.0
Why isn't mine like that. D=
elfking7 said:
You just used your stock kernal 0.0
Why isn't mine like that. D=
Click to expand...
Click to collapse
I have no idea. I didn't even know about needing an unsecure kernel to be able to write to /system. Nor do I know how the stock kernel became unsecure in the first place. All I've done is root the ROM as I normally would by flashing SuperSU. Then grant root permission to the apps that request it. If something in that process makes the stock kernel unsecured, then I don't know what it was.
You said in your OP that you tried manually moving the com.gsamlabs.bbm.rootcomanion-1.apk to /system/priv-app. First of all, that's the wrong apk. See my original reply for the apk you need to move. Do you even have GSam Battery Monitor installed? Battery Monitor & Root Companion are two separate apps. Battery Monitor needs to be installed before Root Companion will do its thing. At least I assume that's the case, b/c like I said before, I didn't use Root Companion to move Battery Monitor. But the description in Root Companion says all it does is move the Battery Monitor apk to /system/priv-app. Secondly, how did you move the apk? What app did you use?
Like I explained previously I originally used an app called Link2SD. That gives an option to convert user apps to system apps & vice versa. Just now I used it to convert GSam back to a user app. I wanted to test if moving the apk manually made a difference. After I converted it to a user app, I used ES File Explorer to cut & paste the GSam apk from /data/app to /system/priv-app. I then restarted my phone. The apk did not disappear and the app continues to work.
sharksfan7 said:
I have no idea. I didn't even know about needing an unsecure kernel to be able to write to /system. Nor do I know how the stock kernel became unsecure in the first place. All I've done is root the ROM as I normally would by flashing SuperSU. Then grant root permission to the apps that request it. If something in that process makes the stock kernel unsecured, then I don't know what it was.
You said in your OP that you tried manually moving the com.gsamlabs.bbm.rootcomanion-1.apk to /system/priv-app. First of all, that's the wrong apk. See my original reply for the apk you need to move. Do you even have GSam Battery Monitor installed? Battery Monitor & Root Companion are two separate apps. Battery Monitor needs to be installed before Root Companion will do its thing. At least I assume that's the case, b/c like I said before, I didn't use Root Companion to move Battery Monitor. But the description in Root Companion says all it does is move the Battery Monitor apk to /system/priv-app. Secondly, how did you move the apk? What app did you use?
Like I explained previously I originally used an app called Link2SD. That gives an option to convert user apps to system apps & vice versa. Just now I used it to convert GSam back to a user app. I wanted to test if moving the apk manually made a difference. After I converted it to a user app, I used ES File Explorer to cut & paste the GSam apk from /data/app to /system/priv-app. I then restarted my phone. The apk did not disappear and the app continues to work.
Click to expand...
Click to collapse
I followed alray's advice. I installed the elementalx kernel which made my system writeable, since my stock kernel wasn't originally. I then retry using the root companion (I installed gsam battery monitor since last week) which finally worked by using the automatic option that the root companion provided. I didn't notice much difference with the app, after giving the battery monitor privileged access to the system=/.
I know, I should have a backup, I'm an idiot. I manually deleted the Google App planning to just reinstall it with the store version so I could hibernate it with Greenify.
I reinstalled it and everything except Hotword detection from any screen works.
I still have a backup of the system files, but I don't know how to properly reinstall them.
Here's the files I backed up:
com.google.android.googlequicksearchbox.apk
com.google.android.googlequicksearchbox.odex
com.google.android.googlequicksearchbox.zip
extra_secondary_data.zip
info.txt
I've just done a factory reset, and the Google App was gone after resetting. This leads me to believe that the necessary files Android uses to restore Apps have been deleted.
General question: Where are these files stored and what do they look like? Would it be possible to manually move the necessary files back there (I still have the backups) and do another factory reset so they properly reinstall?
Could anyone with a Tab S2 maybe look for the necessary files and where they are located in the /system folder and maybe reupload them for me so I can place them back where they belong?
Help would be much appreciated.
Try copy them to a self named map in /system/app
Give proper permission and reboot
Thanks a lot for your help. Apparently I have lost my backup files. Do you or does anybody else have the correct files so I can put them back into the system folder? I'm so close to getting this thing to work.
In case anyone ever encounters a similar problem, I fixed it by downloading the stock-ROM from sammobile.com (you have to register to download but it's worth it) and flashing the md5 with ODIN (tried Flashify before, but somehow that didn't work).
Just follow this tutorial but use your stock ROM from Sammobile instead. http://www.theandroidsoul.com/samsung-galaxy-tab-s2-root-sm-t810-sm-t710-sm-t715-84217/
You'll lose root access but I guess you could just redo the tutorial with the autoroot file and you should be back to normal.
Thanks for your help everybody!