[Q] 5.0.1 Problem with free system space...root and busybox - Nexus 10 Q&A, Help & Troubleshooting

Hi all, i have a strange problem with 5.0.1 factory image...
After root with wug toolkit it cannot open the busybox installer app.
Supersu seems to be installed...device seems to be rooted...
Manually reinstall busybox installer seems to work...after deleting system apps to generate free space in /system...
But if i reboot android dysplays: actualising apps.....
And after that again the busybox installer app cannot be opened...
Anyone else have seen this strange behaviour??
Greets knorst

Hello.
I have no problems with bb or free space.
But I have deleted YouTube and maps from priv-app folder from system partition to free space and also try setting selinux to permissive. It might denials some things.

Well...the problem is, that you have to root first before you are able to remove system apps...i also removed some apps..free space 60 mb....but nevertheless the above described behaviour occured...

Related

Fix for installing busybox on m

Hey guys, some of you seem to be having troubles installing busybox on the new marshmallow. Busybox claims there's only about 16 MB left on the system, but you need more before it will successfully install. Well, if you go into twrp and go to wipe, select system and hit repair, you have to option to resize. It'll set your system at 32 MB. This should be enough to install busybox. After you install it you'll be back down to 0 mb but you can do the process over again and gain another 32 MB.
A better solution would be to just use TB to remove a bunch of Google Apps, then just reinstall from the play store.
I cleared about 500mb doing that, without fussing with formatting.
or just flash this
http://downloads.codefi.re/networkingpro/BusyBox-Android_M.zip
in twrp
funny, i installed stericsons busybox app, then it installed busybox without any issue.
Busybox on Rails worked for me.
The M BusyBox wouldn't install for me so I tried Busybox on Rails. It says it can't write to /system/xbin. Is that also due to the 16MB size of /system?
LeoRex said:
A better solution would be to just use TB to remove a bunch of Google Apps, then just reinstall from the play store.
I cleared about 500mb doing that, without fussing with formatting.
Click to expand...
Click to collapse
You don't have to format, you just resize the partition. I moved some apps but it still said I had 16 MB in system.
abogrhen said:
or just flash this
http://downloads.codefi.re/networkingpro/BusyBox-Android_M.zip
in twrp
Click to expand...
Click to collapse
I installed this version but don't see the Busybox app. However, I see files under /system/xbin that look like it's installed. Does that should normal?
JimSmith94 said:
The M BusyBox wouldn't install for me so I tried Busybox on Rails. It says it can't write to /system/xbin. Is that also due to the 16MB size of /system?
Click to expand...
Click to collapse
Busybox on rails gave me the same error when I ran it using the "Normal" option. The "Recovery" option booted to TWRP to install but I noticed two red text errors. Something about Busybox not installing, but my device reboots before I can get the exact errors. Oddly, Busybox IS installed after the reboot, the app is there and I confirmed through terminal.
Worked For Me
I'm on a Nexus 6 with fresh install of latest Marshmallow build. I used NRT this morning to do a fresh install, root and install TWRP. Busybox did not install properly and using a Terminal Emulator and entering the command "busybox" would show "not found". After using donjuro's fix at the top of this thread and then flashing the Busybox-Android_M supplied by user abogrhen (also in this thread) I was able to properly install Busybox. Using the Terminal Emulator and typing "busybox" now shows me a list of commands. Thanks for your help.
donjuro said:
Hey guys, some of you seem to be having troubles installing busybox on the new marshmallow. Busybox claims there's only about 16 MB left on the system, but you need more before it will successfully install. Well, if you go into twrp and go to wipe, select system and hit repair, you have to option to resize. It'll set your system at 32 MB. This should be enough to install busybox. After you install it you'll be back down to 0 mb but you can do the process over again and gain another 32 MB.
Click to expand...
Click to collapse
Just copy the busybox binary to the data partition, something like /data/bin/
Then in your terminal program, add /data/bin/ to the PATH variable (start command).
There is no need to mess with the system partition for this.

"Busybox" didn't load successfully in system/xbin then what or how? (2012 7 wifi)

"Busybox" didn't load successfully in system/xbin then what or how? (2012 7 wifi)
I used Wug's all in one root. All went well. It also included the busybox app. I did the installation using the default choice of system/xbin, which appeared in a "how-to" video as well. In the video it showed that it loaded successfully. Mine did not load successfully. It specifically said that there was a conflict with the location. I tried system/bin and it basically said the same.
My main question is. 1. What does busybox do that I will need on this device, and 2. How then do I load it, as in, what options should I choose for location? Or delete altogether and reload it? and that question is asked because I want to make sure that deleting the app will not mess up my root/rom/twrp or anything else.
Thank you in advance.
busybox provides a set of linux commands needes especially when you want to run scripts e.g. in init.d
What version of Android do you have installed? Most likely there is no space left on /system and so installation of busybox failed. If you are on a custom rom, you can try to flash micro / pico gapps instead of the normal ones to leave some space left on /system for busybox, or you need to root your device "systemless" and you can install busybox on the partition provided by SuperSU ...

AdAway on stock nougat- copying of host file failed

hello im getting the following message everytime i try and download the lists "copying of host file failed! please read help for more information"
ive just updated to the android 7.0 through the developer program, twrp custom recovery installed with root access build number NRD90M
just wondering what could be causing this and if i can do anything to try and fix it thanks
Is your /system set to read only, or read/write? If read only, adaway will not be able to update /system/etc/hosts
dratsablive said:
Is your /system set to read only, or read/write? If read only, adaway will not be able to update /system/etc/hosts
Click to expand...
Click to collapse
i have it set to read write im gonna try to flash the systemless hosts right now ill update how it goes
flashing the AdAway_systemless_hosts_v2.zip in the recovery, then unistalling and reinstalling the app seems to have worked
you can also use Magisk now to enable complete systemless root and then the hosts file /system/etc will be forwarded to the systemless version
I didn't even install Adaway, I just downloaded a host file and replaced it in /etc/
Works good enough for me and one less app running...
kennehh said:
hello im getting the following message everytime i try and download the lists "copying of host file failed! please read help for more information"
ive just updated to the android 7.0 through the developer program, twrp custom recovery installed with root access build number NRD90M
just wondering what could be causing this and if i can do anything to try and fix it thanks
Click to expand...
Click to collapse
In the exact same boat. Frustrating. Tried Adfree, to no avail. Adaway, to no avail. Tried the adaway bind zip file, making hosts writable, and even System to writable. Nothing.
treoo0_1 said:
In the exact same boat. Frustrating. Tried Adfree, to no avail. Adaway, to no avail. Tried the adaway bind zip file, making hosts writable, and even System to writable. Nothing.
Click to expand...
Click to collapse
i have fixed this by converting adaway from user apps to system apps using Link2SD, reboot and adaway working properly again
Very old thread, but I've had exactly the same problem installing AdAway on the last 3 or 4 phones -- all but one running Nougat 7.0, the other on Oreo 8.1. This was when trying to install AdAway versions 3.1 and 3.3.something.
I finally got it to write hosts file updates using one of the following, not sure which was the key:
-- Installed version 3.2 which had been running problem-free on an old phone for years. The biggest difference is this older phone is running Resurrection Remix 5.8.3 (Nougat 7.1.2).
-- Before trying to update the hosts file on this fresh install, I went straight to AdAway preferences and set "Check for updates daily", "Enable webserver", and "Start webserver on boot". After making those settings I tapped Download Files and Apply Ad Blocking, and it successfully wrote to the hosts file.
Again I don't know which was the fix. It seems weird that version 3.2 would work when a version just before and after it didn't work for me. But of course it is possible that the version is the difference. It seems even more weird that those 3 little preference settings make any difference at all . . . unless it's just the act of writing changes to the AdAway app itself.
Before installing 3.2, using Root Explorer I checked permissions on the working phone and one non-working phone, for the systems and etc folders, and for the hosts file itself. (In all cases AdAway is/was set to use /systems/etc/hosts.) I also checked Android permissions in the Apps list. All permissions were exactly the same on both phones: 0755 for system, 0755 for etc, and 0644 for hosts. No permissions assigned via Android.
Hoping this bump will also get fresh attention from somebody who might know the details of a real answer.
@Moondroid
Why the hell you trying to make some really old ass version of it work instead of installing the newest version? Lol
I've been using 4.2.7 and though its kind of weird on a fresh install I need to update and apply the hosts twice before searching for newer hosts comes back its up to date. But at least it works.

could not remount /system

Guys, i am on stock os, 7.0 , recently flashed magisk for systemless root and when i tried to use app mover to move some apps to system, i get error as could not remount/system. Tried supersu root as well but same result, im a newbie here. please help Used both Vegito and Ex kernel too. but i get the error everytime. But root checker shows i have root.
You could try the Magisk module named "App Systemizer". It can convert user apps to system apps, but systemlessly.
thorin0815 said:
You could try the Magisk module named "App Systemizer". It can convert user apps to system apps, but systemlessly.
Click to expand...
Click to collapse
Thanks, Is there a way to edit system files , like modifying host file ? It seems i have been using system root all these days. Is it still available ?

How to uninstall Google Apps on ROOTED Oneplus 5 mit OxygenOS 10.0.0

I have had the Oneplus 5 for many years. After each update of OxygenOS I uninstalled some system apps (Chrome Google Photos, Gmail, Google Movies etc) in Solid Explorer (with root access).
But, since the update to OxygenOS 10.0.0 with Android 10 this does not work anymore. Solid Explorer says that the app has been deleted, but after a reboot it is still there.
When I try to uninstall one of the apps with Titanium Backup, the message "Cannot remove system app. Failed to locate the apk file."
Does anyone have an idea how to permanently uninstall and delete system apps?
Thanks!
Berta Paneslowski said:
I have had the Oneplus 5 for many years. After each update of OxygenOS I uninstalled some system apps (Chrome Google Photos, Gmail, Google Movies etc) in Solid Explorer (with root access).
But, since the update to OxygenOS 10.0.0 with Android 10 this does not work anymore. Solid Explorer says that the app has been deleted, but after a reboot it is still there.
When I try to uninstall one of the apps with Titanium Backup, the message "Cannot remove system app. Failed to locate the apk file."
Does anyone have an idea how to permanently uninstall and delete system apps?
Thanks!
Click to expand...
Click to collapse
On Android 10 it's not possible anymore to delete system apps directly from OS, even with root access. You must use Titanium for show the path of apps you want deleted, system apps are located on :
system/system/app
system/system/priv-app
Go in recovery TWRP
> mount Cache, System, Vendor, Persist, Data, Firmware partitions
> Advanced > File Manager > system/system/priv-app/Gmail > "Folder" button on right bottom > Delete
Do the same thing for all apps that you want deleted.
Actually,it does get deleted from a root explorer, however, few apps have symlinks as well, or few apps have stubs as well. Hence those may invoke reinstallation automatically. Those are the ones which need to be deleted permanently from recovery (especially).
As you have discovered, several apk files are system linked and so every reboot will bring them back. To counter this I use the xXx debloat script. The module is flashed in Magisk and allows one to select which apps and services you want removed. Here is a link to the module on xda: https://forum.xda-developers.com/showpost.php?p=82391573&postcount=2.
You can flash the module with stock settings or make a custom profile as I did.
I have a question or two...
1) Is it ok to convert Chrome and Google Maps from system to user apps in android 10?
2) Will first deleting the app using TWRP, then install it from Playstore convert the app from a system to a user app?

Categories

Resources