Hello, folks,
I have a problem with my Nexus 5X (Android 7.1.2). I had rooted it with TWRP and Magisk, until last no problems. After an update to Magisk v18 two days ago, I found the problems.
I had an app that I installed as a system map. It was deleted after the update. If I now want to reinstall it (as in this manual), it won't work. I can create a folder in "system/app" and "system/priv-app" (or copy the APK there), but I can't do anything else. No renaming, no changing of permissions. Also it often happens that I cannot copy the file there because of missing permissions. This only works once after a restart. After a restart the copied file or folder will be deleted again and again.
I tried Solid Explorer, Root Explorer and ES File Manager. Link2SD also fails and cannot create the system app. SU permissions are on for all tested apps.
Does anyone have an idea what I should do? :-/
Regards
XOXO
XOXO1 said:
Hello, folks,
I have a problem with my Nexus 5X (Android 7.1.2). I had rooted it with TWRP and Magisk, until last no problems. After an update to Magisk v18 two days ago, I found the problems.
I had an app that I installed as a system map. It was deleted after the update. If I now want to reinstall it (as in this manual), it won't work. I can create a folder in "system/app" and "system/priv-app" (or copy the APK there), but I can't do anything else. No renaming, no changing of permissions. Also it often happens that I cannot copy the file there because of missing permissions. This only works once after a restart. After a restart the copied file or folder will be deleted again and again.
I tried Solid Explorer, Root Explorer and ES File Manager. Link2SD also fails and cannot create the system app. SU permissions are on for all tested apps.
Does anyone have an idea what I should do? :-/
Regards
XOXO
Click to expand...
Click to collapse
This is a normal problem for Magisk. To fix it do the following. Open Magisk manager's settings and turn on core only mode then reboot. Do your system stuff add/remove apps, set permissions, etc. Then turn off core only mode (or modules won't work) and reboot once more.
Spaceminer said:
This is a normal problem for Magisk. To fix it do the following. Open Magisk manager's settings and turn on core only mode then reboot. Do your system stuff add/remove apps, set permissions, etc. Then turn off core only mode (or modules won't work) and reboot once more.
Click to expand...
Click to collapse
Thanks, that helps.
Related
Hello guys, after much of my research on getting old market back on ICSunday ROM by jusada, I finally figured out how to do so.
So let's start.
1. Download Vending.apk (Attached) onto your phone and save it to your SDCard.
2. Get/Open Root Explorer and navigate to "/sdcard" copy "Vending.apk" from there.
3. Mount R/W in "/system/app/" and paste "Vending.apk" in there.
4. In "/system/app/" folder there would be a file called "8007005.apk" rename it to "8007005.apk.abc" (I don't prefer deleting system files, so I just rename them so as to get a backup in case anything goes wrong).
5. Rename your "Vending.apk" (the one you just copied) to "8007005.apk".
6. Change permissions of your "8007005.apk" to "rw-r--r--" and Change owner to Owner: 0-root and Group: 0-root.
7. Rename "MarketUpdater.apk" in "/system/app" to "MarketUpdater.apk.abc".
8. Navigate to "/data/data/" and delete folders called "com.android.vending" and "com.android.vending.update".
9. Reboot your mobile.
10. Finally if you don't see your market downgraded just head over to Root Explorer and navigate to "/system/app/", tap "8007005.apk", when the popup shows up tap "Install" and let it install like a normal apk file.
Voila you have successfully downgraded your market!
Post your queries here if you are facing any problems or need help with something.
On Cyanogenmod, i uninstalled the Updates from Market under Settings/Apps and deleted MarketUpdater.apk.
There is a better way for those roms fixed on the new market. It's automated: search oldmarket on xda it's a free root app.
how to stop market updating itself? i revert to the old one then it update it self once again.
ketah23 said:
how to stop market updating itself? i revert to the old one then it update it self once again.
Click to expand...
Click to collapse
Use titanium backup or any other app that can freeze apps, to freeze market-updater.apk
downloadonlyaccount said:
On Cyanogenmod, i uninstalled the Updates from Market under Settings/Apps and deleted MarketUpdater.apk.
Click to expand...
Click to collapse
ICS ROM already comes with updated 3.3.1, so if I uninstalled updates, the market still remained the same.
consegregate said:
There is a better way for those roms fixed on the new market. It's automated: search oldmarket on xda it's a free root app.
Click to expand...
Click to collapse
Used that, gave me FC's when I opened market.
ketah23 said:
how to stop market updating itself? i revert to the old one then it update it self once again.
Click to expand...
Click to collapse
Grab yourself a copy of Root Explorer (Root needed), head over to "/system/app/", mount R/W and rename file called "MarketUpdater.apk" to "MarketUpdater.apk.abc", finally uninstall updates of market and it would stop upgrading itself.
5pace said:
Grab yourself a copy of Root Explorer (Root needed), head over to "/system/app/", mount R/W and rename file called "MarketUpdater.apk" to "MarketUpdater.apk.abc", finally uninstall updates of market and it would stop upgrading itself.
Click to expand...
Click to collapse
if you have root explorer [or any other] then you just can remove all read write permission of marketupdater.apk and uninstall current updates
I have two separate issues which I believe are caused by the same thing.
1. When I try to alter platform.xml in the /system/etc/permissions folder via ES File Explorer to enable 3rd party apps to have write capability to the SD card, the edit is unsuccessful and my phone reboots. When I pull a copy of the file to my PC, alter it, and then try to push it via ADB, the same thing happens. I previously used the ADB pull/push method to edit my hosts file and had success with that after doing it while in Recovery, but this time around both ways (in recovery and with the device booted up) result in my device rebooting. For the SD card fix, I've also tried the app that does it for you and encounter the same issue.
2. When attempting to update the SuperSU binary, the update fails my device reboots. This happens with either update method - normal and recovery.
So both issues seem to have the same root cause... my phone will not allow any editing of system files. Anyone have any suggestions?
For reference I'm on a Galaxy Note 4 (model SM-N910T) on T-Mobile.
Baseband version N910TUVU1ANJ7
Android version 4.4.4 (stock ROM)
Kernel version 3.10.0-2796035
Build number KTU84P.N910TUVU1ANJ7
I'm also running Wanam Xposed - not sure if that has anything to do with anything but just fyi.
Thanks
bump... anyone have any ideas?
replace the altered xml with a original/stock one..
If u have a backup
abhinavp649 said:
replace the altered xml with a original/stock one..
If u have a backup
Click to expand...
Click to collapse
I have the stock .xml in there right now... my problem is that I want to replace it, but I can't because my phone reboots every time I try.
Gakuseinozen said:
I have the stock .xml in there right now... my problem is that I want to replace it, but I can't because my phone reboots every time I try.
Click to expand...
Click to collapse
Is your Phone is rooted? If yes:
place the altered .xml somewhere in your sd card.
1. Install an app called Total Commander.
2. Navigate to the location where your stock file is located.(delete it)
3. Now goto sd card where you placed your altered file.
4. Tap on Icon of the .xml file, You will see a green tick mark on it.
5. When your file is selected. Tap on Copy/Move to Icon.( u will see two files one on one with a blue arrow)
6. Now Click on '>>' button to browse the location where you have to Copy/Move the File.
7. Now Tap Copy if You want a backup placed in sd card of the file or move if you just want one file to be there.
(Through all the Process I am assuming that your phone is rooted and you Have Granted SuperUser permissions to Total Commander)
abhinavp649 said:
Is your Phone is rooted? If yes:
place the altered .xml somewhere in your sd card.
1. Install an app called Total Commander.
2. Navigate to the location where your stock file is located.(delete it)
3. Now goto sd card where you placed your altered file.
4. Tap on Icon of the .xml file, You will see a green tick mark on it.
5. When your file is selected. Tap on Copy/Move to Icon.( u will see two files one on one with a blue arrow)
6. Now Click on '>>' button to browse the location where you have to Copy/Move the File.
7. Now Tap Copy if You want a backup placed in sd card of the file or move if you just want one file to be there.
(Through all the Process I am assuming that your phone is rooted and you Have Granted SuperUser permissions to Total Commander)
Click to expand...
Click to collapse
I'm assuming this will end with the same result as when I try it through ES File Explorer. ES has the same capability and I have given it root access already. Something is causing all attempts to alter system files to fail, regardless of root access.
Gakuseinozen said:
I'm assuming this will end with the same result as when I try it through ES File Explorer. ES has the same capability and I have given it root access already. Something is causing all attempts to alter system files to fail, regardless of root access.
Click to expand...
Click to collapse
This was not successful. Anyone else have any ideas? I tried posting logs in the SuperSU update failure thread, with the logic that if I get that issue fixed my other issue will be resolved also, but Chainfire hasn't responded to any of the requests in a while.
After root I deleted DefaultContainerService.apk by mistake but one good thing is I had copied terminal, linuxforandroid and ROOT Explorer to the system/app folder.
Bad thing is these 3 apps are not installed by default even though it is in system/app folder. (Other pre existing apps are installed) when the reset happens.
I am not able to install any apps now without DefaultContainerService :crying:
Even after format I am having root format.
When you move apps to /system, they must have permissions set to 0644 then reboot to have it take affect. If you can find a stock based rom, you should be able to extract that apk and move it to system, set permissions, reboot and good to go.
Partial
The solution is great. i used adb and changed the permission and reset the phone.
I can see the app installed but when i open it it tells failed.
I found temp solution of pushing DefaultcontentProvider through adb but still I want it to be in default app list. Do not want to push after every reset.
Android 5.1.1 "optimizing apps" on every boot - no .odex files on the phone!
Dear all,
Today I installed Android 5.1.1 on my Nexus 4 after doing a complete wipe and rooted it.
The system runs, but each time I reboot, it takes about 20 minutes "optimizing apps" - each and every one out of 135.
I tried wiping the cache partition, but it didn't help.
I did some research and found people telling that they solved the problem by changing the file permissions of the .odex files to 666.
Then, I was surprised to find that there are no .odex files on my phone (except for a few ones which aren't those I'm looking for). I used the find command with root permissions to find the files.
According to various sources, the .odex files should be in /data/app and /system/app. But they're not there. For example, my directory /data/app/com.whatsapp-1 contains only the file base.apk and a lib directory. Is this normal?
Thanks!
For anyone with the same issue: I found out that the problem occurs exactly after installing SuperSU (via TWRP). Only then will Android optimize all apps at each boot. I didn't try other root apps. Instead, I moved to Android 7.1, which also works great and without that problem.
Hello friends, I bring good news.
Yes! It is possible to install Cerberus as a system app. (Even if it's rooted with Magisk)
Yes, Cerberus will survive a factory reset. And your device will be traceable after a factory reset.
Obviously the device will not be tracked if the system partition is deleted. Tested only on my Xiaomi Mi A3, Android 9 (Pie).
-
FOLLOW THE STEPS:
1. Download the RS File Manager app (To get root access, you must buy the premium version. Maybe in the future this function does not require purchase.); Alternatively, you can try the procedure with some other root file manager, I don't know if you will succeed;
2. Open the RS File Manager and find the option Root explorer. Tap on it and select Mount R/W;
3. Download the Cerberus app (Disguised version), after all you don't want the Cerberus app to be recognized by others, am I right?)
4. In RS File Manager navigate to the /System/priv-app folder and create a folder called Cerberus;
5. Now just paste the APK you downloaded in the Cerberus folder that you created;
6. Within the Cerberus folder, hold your finger on the APK file, then select more -> properties -> change permissions. Now change the permissions to rwx r-x r-x (I will attach a screenshot to help them - On your device it can be different, in this case just look at the permissions of the other folders in System/Priv-app. Then use the same permissions.);
7. Go to /data/dalvik-cache/ and delete all the content inside the dalvik-cache folder. DO NOT DELETE THE DALVIK-CACHE FOLDER.
8. Reboot your device;
After the device restarts, Cerberus will already be on your list of apps;
Enjoy it!
Hi @FredMontteiro
Did the App settings survive? Did the tracking actually work post factory reset?
The settings do not survive, but the device could be tracked perfectly.
FredMontteiro said:
The settings do not survive, but the device could be tracked perfectly.
Click to expand...
Click to collapse
I think this is only possible through the Cerebus portal using IMEI number or maybe hw device id preregistered with Cerebus.
Will this in any way break safety net?
OMG
my device is now stuck at boot animation!
please help
uvalml said:
my device is now stuck at boot animation!
please help
Click to expand...
Click to collapse
Well describing the steps leading up to your problem would help...
FredMontteiro said:
The settings do not survive, but the device could be tracked perfectly.
Click to expand...
Click to collapse
Can you explain HOW?.
because I tried the app and made it system app and after the factory reset the app data got wiped and I couldn't track my device
FredMontteiro said:
The settings do not survive, but the device could be tracked perfectly.
Click to expand...
Click to collapse
Can this way work in huawei y7 2019 ?
Ah for ****e sake, well this sucks ass. Follwed instructions perfectly and now I got a bootlop. Looks like Im not going to bed early tonight.
FredMontteiro said:
Hello friends, I bring good news.
Yes! It is possible to install Cerberus as a system app. (Even if it's rooted with Magisk)
Yes, Cerberus will survive a factory reset. And your device will be traceable after a factory reset.
Obviously the device will not be tracked if the system partition is deleted. Tested only on my Xiaomi Mi A3, Android 9 (Pie).
-
FOLLOW THE STEPS:
1. Download the RS File Manager app (To get root access, you must buy the premium version. Maybe in the future this function does not require purchase.); Alternatively, you can try the procedure with some other root file manager, I don't know if you will succeed;
2. Open the RS File Manager and find the option Root explorer. Tap on it and select Mount R/W;
3. Download the Cerberus app (Disguised version), after all you don't want the Cerberus app to be recognized by others, am I right?)
4. In RS File Manager navigate to the /System/priv-app folder and create a folder called Cerberus;
5. Now just paste the APK you downloaded in the Cerberus folder that you created;
6. Within the Cerberus folder, hold your finger on the APK file, then select more -> properties -> change permissions. Now change the permissions to rwx r-x r-x (I will attach a screenshot to help them - On your device it can be different, in this case just look at the permissions of the other folders in System/Priv-app. Then use the same permissions.);
7. Go to /data/dalvik-cache/ and delete all the content inside the dalvik-cache folder. DO NOT DELETE THE DALVIK-CACHE FOLDER.
8. Reboot your device;
After the device restarts, Cerberus will already be on your list of apps;
Enjoy it!
Click to expand...
Click to collapse
does this work on android 11 or on devices with dm-verity check ?