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...
After OTA update failed, I flashed stock 5.0.2 rom onto my 32GB nexus 10 using wugfresh NRT with /nowipe mode. After rooting with the same NRT, busybox install wasn't successful, and displaying 0.0 mb space left in /system partition. Something must be wrong. I don't believe the system rom takes exactly the whole system partition. But the system flashing didn't report errors, and the system seems fine except when I tried to change boot animation, I cannot copy the .zip file to /media folder using root browser. This is either caused by busybox not installed properly or /sys partition is full. I successfully changed boot animation using the same steps on my nexus 4.
I have tried factory reset, no luck.
I also tried deleting some system apps using System app remover. I removed google slides and sheets, which should release over 15 mb space. But after multiple reboot, it still says 0.0mb left.
Anyone else have this problem? What can I do?
BTW. I previously flashed stock 5.0.1 /nowipe using the same tools. My memory is 60% sure that each time I flashed, there's less free space left in /system partition.
UPDATE: Successfully deleted a few apps in system folder using 'root browser' and released some space.
fransky said:
After OTA update failed, I flashed stock 5.0.2 rom onto my 32GB nexus 10 using wugfresh NRT with /nowipe mode. After rooting with the same NRT, busybox install wasn't successful, and displaying 0.0 mb space left in /system partition. Something must be wrong. I don't believe the system rom takes exactly the whole system partition. But the system flashing didn't report errors, and the system seems fine except when I tried to change boot animation, I cannot copy the .zip file to /media folder using root browser. This is either caused by busybox not installed properly or /sys partition is full. I successfully changed boot animation using the same steps on my nexus 4.
I have tried factory reset, no luck.
I also tried deleting some system apps using System app remover. I removed google slides and sheets, which should release over 15 mb space. But after multiple reboot, it still says 0.0mb left.
Anyone else have this problem? What can I do?
BTW. I previously flashed stock 5.0.1 /nowipe using the same tools. My memory is 60% sure that each time I flashed, there's less free space left in /system partition.
Click to expand...
Click to collapse
Is there a reason why you don't use ADB/Fastboot? I have noticed this before too though. I tried changing the boot animation and finding that there was no more room on the system partition. But I have also noticed that the system partition is pretty small on my Nexus 5 too. So lollipop must have shrunk that. Maybe try wiping everything before you flash whatever you are flashing
jsgraphicart said:
Is there a reason why you don't use ADB/Fastboot? I have noticed this before too though. I tried changing the boot animation and finding that there was no more room on the system partition. But I have also noticed that the system partition is pretty small on my Nexus 5 too. So lollipop must have shrunk that. Maybe try wiping everything before you flash whatever you are flashing
Click to expand...
Click to collapse
Thanks jsgraphicart. I did try OTA through ADB, but it failed, too. I looked around and people say google messed up ota after lollipop. So I flashed rom instead.
I've never wiped anything before. Could you point me to some instructions?
fransky said:
Thanks jsgraphicart. I did try OTA through ADB, but it failed, too. I looked around and people say google messed up ota after lollipop. So I flashed rom instead.
I've never wiped anything before. Could you point me to some instructions?
Click to expand...
Click to collapse
When I got my Nexus 10, the first thing I did was use the factory images and ADB/Fastboot to clear out everything. They worked fine. So there is nothing wrong with the images. I'd suggest trying them again. Or maybe try out a ROM. I'm running CM12 right now.
I don't know if my issue is related to this but, I am unable to copy my Nexus 6 audio files to the system folder on the N10 using root explorer. However I am able to delete files from system. I too used NRT to go to 5.0.2.
You're not the only one falling victim to this issue. Here is some discussion in a M8 thread.
And my N10
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What I've been doing the past few updates is using fastboot and formatting /system, then flashing the /system partition from the factory (not update) image, then I remove the Newstand apk from the /system/app folder, opening up some free space. I chose Newstand because it's large enough to give me working space for Busybox and a big hosts file, etc and there is already a newer version in the playstore which won't live in the /system partition anyway.
My /system partition is always modified enough that an update won't work, and it takes less time and effort to just flash the stock /system partition from the factory image, and modify it (root, busybox, hosts, etc).
I have just flashed the factory image again, this time unchecking 'no-wipe mode'. Still got 0.0mb left.
update: uninstalling system apps failed using 'system app remover'. But successfully deleted a few apks in the system folder using 'root browser', and now there's finally enough space to properly install busybox.
Will upload latest twrp with resize2fs binary. It is not built in by default. It allows you to reclaim the whole free space of the partition
Sent from my Xiaomi MI2s
Edit: here you are : http://forum.xda-developers.com/nex...-partition-t3029605/post58816504#post58816504
Can this be flashed in tarp from INTERNAL SD card since the nexus 10 has no SD card or does this require me to use a pc?
I too have 0 free space in my system partition after rooting and installing twrp
xyourxhighnessx said:
Can this be flashed in tarp from INTERNAL SD card since the nexus 10 has no SD card or does this require me to use a pc?
I too have 0 free space in my system partition after rooting and installing twrp
Click to expand...
Click to collapse
Yes, you can keep it in your normal downloads folder and flash it from there. That's because this only modifies the system partition, and doesn't touch your user data.
It Works when you have 0.0mb free in /System folder
tvBilly said:
What I've been doing the past few updates is using fastboot and formatting /system, then flashing the /system partition from the factory (not update) image, then I remove the Newstand apk from the /system/app folder, opening up some free space. I chose Newstand because it's large enough to give me working space for Busybox and a big hosts file, etc and there is already a newer version in the playstore which won't live in the /system partition anyway.
My /system partition is always modified enough that an update won't work, and it takes less time and effort to just flash the stock /system partition from the factory image, and modify it (root, busybox, hosts, etc).
Click to expand...
Click to collapse
This worked a treat for me....thank you!
Just for people suffering for this and ending up in this thread.
You can download here a fix I have made.
Short explanation
Google has defined a size of 644 MB for system partition for an ext4 filesystem.
So even if your actual block device is 800 MB( by default) flashing your stock update will tell your FS that the partition is only 644 mb. My fix just resize ext4 fs 's size to the size of your device part that is allocated for system ( which is 800 MB)
Khaon said:
Just for people suffering for this and ending up in this thread.
You can download here a fix I have made.
Short explanation
Google has defined a size of 644 MB for system partition for an ext4 filesystem.
So even if your actual block device is 800 MB( by default) flashing your stock update will tell your FS that the partition is only 644 mb. My fix just resize ext4 fs 's size to the size of your device part that is allocated for system ( which is 800 MB)
Click to expand...
Click to collapse
I'm a happy user of your fix. It's worked for me every time I've flashed it with never a problem. It allows flashing a bigger GAPPS and making apps into system apps when there otherwise wouldn't be enough space. Thanks.
Question: do I need to reflash it every time I update a ROM to a new nightly? I have been.
And me too. I still use the same routine of updating the system partition from the factory installer (rather than dealing with the update version), but I now don't bother to delete anything and I just use Kahon's fix, which works fine, and really is a fix...
It depends on your OTA package. If it is just extracting files then you need to flash my fix once(or format).
However its flashing an image then you will have to reflash my fix.
Just open your archive and check content:good:
Hi.
First the symptom:
I installed the MMB29K to MMB29O OTA on my nexus 7 2013 and as per the thread title is lost done of the links on /storage/..
There's also a /storage/self that I've never seen before.
/storage/emulated/ is still there but doesn't go to sdcard (which still works and has all my data by the way).
The tablet reports space issues even though sdcard is available and has plenty of space
Now the background:
My only modification is chainfire rootless. I needed to delete the file level checksums and repack the zip to get OTA to install. The above approach worked fine on my nexus 5 but It did report a space issue while flashing on the nexus 7.
DF shows 4 meg free on /system
Before i flash the full factory image minus userdata img make it worse does anyone have any ideas? Has the new MMB29O grown too big?
Thank you
Chris
Update : Just flashed the full .img contents from Google-Factory images, minus the userdata folder and reapplied systemless root and all good. A little confused why I lost the mountpoints in /storage in the first place
I wonder if related to the modifications that systemless root makes to the boot image
Hi,
I would like to know if there is a way to integrate/push Apps into System Partition beside using flashable ZIP file? For a long time Link2SD, LP and Titanium Backup did the trick, but now they all don't work.
Pushing an update (for example Play Store App) to system will just add the APK and not replace old one, so you have the App twice.
Pushing an installed User App to system will make it disappear, while it is wasting space in system partition. It's just not recognized by Android.
Right now (MM/6.0.1 ROM), the only working method I know of doing it is flashing ZIP file in Recovery or Flashfire. Is there any other working method? Preferably a script or an App that is still working on G900F with MM Stock ROM?
Hello there !
I've rooted my phone a weeks ago, and i want to convert a gps app to system app, for pokemon go like you guess.
I root my Op 6t international edition with magisk and stock rom.
Link2SD say me i don't have enough place in /system.
How i can increase my /system place ? Thanks you !
I also can not convert to system
Bro, I too faced the same problem when I flashed the latest 9.0.15 rom first. I am rooted and wanted to chnage the hosts file, but total commander and other files managers like ES, EZ all gave an error that /system has not enough memory. Then I thought of reflashing the same rom again as I did earlier, and things worked out fine. I was able to edit the hosts file and save it. I was able to mount it. But still I just have 7 mb left of 2.71 GB. I don't know the exact reason for this :/
I got this problem after installed beta 14 hour ago . I just delete the preinstall youtube then reboot . Problem solved .
Goormeetsingh said:
Bro, I too faced the same problem when I flashed the latest 9.0.15 rom first. I am rooted and wanted to chnage the hosts file, but total commander and other files managers like ES, EZ all gave an error that /system has not enough memory. Then I thought of reflashing the same rom again as I did earlier, and things worked out fine. I was able to edit the hosts file and save it. I was able to mount it. But still I just have 7 mb left of 2.71 GB. I don't know the exact reason for this :/
Click to expand...
Click to collapse
If you have magisk ypu can enable systemless hosts.
I'm having the same issue lately and adaway says I have no space in root, 0 out of 2.71gb. I hope installing the latest rom will help.
Mersine said:
I'm having the same issue lately and adaway says I have no space in root, 0 out of 2.71gb. I hope installing the latest rom will help.
Click to expand...
Click to collapse
You can try Tomatot's debloater https://forum.xda-developers.com/on...ol-tomatot-debloater-basic-script-to-t3869427 , download for OOS Invisible script: https://forum.xda-developers.com/attachment.php?attachmentid=4772363&d=1559812962
Hello, I have very simple fix for your issue. For app coversion to system app use Lucky Patcher instead! I had a same problem, but with Lucky Patcher, worked absolutely fine.