Hey,
I can't access the system partition of my Nexus 5 with Solid Explorer, Super SU 2.64 and Marshmallow 6.0.1
I want to push the Motorola Gallery APK to /system/app and the according /lib files into the /system/lib folder.
Both doesn't work, but I can copy stuff into the /system partition.....
Titanium Backup also fails when trying to push backup files to the system partition.
Is this a known bug or what else can I do?
Solid Explorer works with a modified boot.img (tried for mra58k though) and Super SU 2.52. Titanium Backup still fails (wont got over 0% progress)
Related
I have a T-Mobile HTC M7 converted to GPE, recently flashed to Lollipop from KK 4.4.4. I use Tasker and OpenRecoveryScript to automate Nandroid backups through TWRP, then use FolderSync to upload said backup to my server over WiFi. My method worked perfectly until I flashed to Lollipop.
Since flashing to Lollipop, whether through Tasker or manually, I get an error in FolderSync saying the Nandroid files can't be read or copied. If I use TWRP's file manager, I can view the Nandroid folders/files, but those same files are not viewable using ES File Explorer in Lollipop. When I navigate to TWRP\BACKUPS\{Serial Number} folder in ES File Explorer, the {Serial Number} folder (where the TWRP backups are) is listed as a 0k(zero) file that can't be read or copied. When I try to create a new folder (in the BACKUPS folder) using ES File Explorer I get an error saying the operation failed.
Just this morning I restored a Nandroid backup using TWRP, and now in ES File Explorer my entire SDcard folder is blank (not true, as all my apps still function), but in TWRP file manager the SDcard folder is fine. At first I thought the problem was with ES File Explorer, but I tried a few different file explorers with the same result (FX File Explorer tells me 'Access was Denied' when trying to view the sdcard folder. ) All file managers I've tried have root access.
I thought Lollipop fixed the sdcard problems from KK, but this is a whole new one for me. Is there an issue with Lollipop not being able to read files that are written through recovery/TWRP? Any help would be greatly appreciated.
In a terminal app type
Su
restorecon -FR /data/media/0
Ajxx16 said:
In a terminal app type
Su
restorecon -FR /data/media/0
Click to expand...
Click to collapse
Thanks for the help Ajxx16. Tried your suggestion and get: tmp-mksh: restorecon: not found
You have root correct?
Ajxx16 said:
You have root correct?
Click to expand...
Click to collapse
Yes. Rooted running SuperSu 2.37 and TWRP 2.8.1.0. I also tried applying the restorecon patch through TWRP's terminal. It seems like it did something, but again when I boot back into the system, sdcard folder listed as empty. I just flashed a Nandroid backup I had of 4.4.4 and no sdcard issue. I'm going to update back to 5.01 (slowly, monitoring each step) to see if I can troubleshoot when the issue starts again, if at all (which wouldn't bother me if it didn't, really).
So I updated from 4.4.4 and ran into the same issue. It turns out the ROM I was updating from somehow did not have restorecon in the system/bin folder. I was able to find a 5.01 GPE RUU, flashed that, applied restorecon fix, and issue is resolved. Thanks for the help Ajxx16!
I tried to change the boot animation, running M Preview 3, and despite the fact that the flash claims to have performed successfully, it did not. I'm trying to flash the Marvel boot from the Themes and Apps section, and I know the flashable file worked on 5.1.1. It didn't overwrite the bootanimation.zip in /system/media. At one point, I was able to manually move the file there myselfusing Root Explorer, but I did not realize that the /system partiton did not have enough space to hold the entire zip file, so it was a corrupted zip at that point, and now my boot animation is just "android" in gray lettering. I cleared up enough space to hold the entire zip file of the marvel boot, but now I cannot move the file there, ES File Explorer and Root Explorer simply say it failed to copy.
I just tried to use adb to push the zip file from my computer, but it fails because /system is a read-only file system. So, I tried to remount with a shell as read-write, after some initial issues with apparently /system/xbin/mount not working properly, it did remount as read-write when using /system/bin/mount. But, adb push still fails because /system is a read-only file system.
Code:
mount | grep system
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 rw,seclabel,relatime,data=ordered 0 0
But, as you can see, it's mounted as read-write.
I, also, just tried to move the file as root in an adb shell, with no luck. A bootanimation.zip shows up in /system/media, but apparently it is corrupt because I cannot open it with root explorer, or in Windows when I pull it. When I try to move the boot animation that I want, the shell reports that there is not sufficient space, which is true now. The bootanimation.zip takes up 40MB of the 55MB of free space in the /system partition. Any time I try to delete the zip, it is automatically recreated before I have a chance to move anything in it's place, even when I do:
Code:
rm /system/media/bootanimation.zip | mv /storage/emulated/0/Download/marvelboot/system/media/bootanimation.zip /system/media/bootanimation.zip
So, what am I missing? Is it even possible to change the boot animation on Android M? Am I doing something wrong, or not doing something I need to?
why flash it? its a boot animation.. extract it from the zip, then pkace the bootanimation.zip into /system/media/ then just reboot. thats all it takes.
edit.. i didnt read ypur whole post and realuze that yoh have other issues.
Yeah, I wish it was just as easy as flashing or moving the zip file to /system/media/... Normally it is, but with Android M there seems to be a problem?
cappiez said:
Yeah, I wish it was just as easy as flashing or moving the zip file to /system/media/... Normally it is, but with Android M there seems to be a problem?
Click to expand...
Click to collapse
no, no problem here. do you have full root? i mean do you have the ability to edit anything in /system/?
Everything seems fine according to root checker. And, if I make small changes to my build.prop (Just editing build.id), the changes stick after a reboot. Soooo.. Yes?
cappiez said:
Everything seems fine according to root checker. And, if I make small changes to my build.prop (Just editing build.id), the changes stick after a reboot. Soooo.. Yes?
Click to expand...
Click to collapse
so you fo have full root. i use root explorer to put animations into /system/meda/, havent had any issues. does that animation work on a n6?
It worked on 5.1.1. Since I moved to the M Preview 3 builds, it appears to have stopped working.
cappiez said:
It worked on 5.1.1. Since I moved to the M Preview 3 builds, it appears to have stopped working.
Click to expand...
Click to collapse
nope. im on m preview 3, and it works fine here.
I've updated my device today to 6.0.1 and rooted, however I can't seem to change the boot animation (yes, I have searched for answers and tried quite a few fixes).
Root Explorer tells me I have renamed the old file and copied the new file, however once I leave the directory and go back the old file is still there.
I have used the file explorer in TWRP and managed to delete the stock boot animation, but get a FAILED message when I try to copy the new file.
I used the terminal in TWRP and tried to copy the file manually, and receive a "No space left on device" message.
I've also tried mounting the /system as rw in adb. I can delete the bootanimation.zip file from there, and df -h shows 3mb free. Shouldn't the system partition have more space available than that?
Am I missing something, or has something changed with the new android versions?
Google has filled the system partition up to the brim. Also you can't remount system as rw while Android is running.
But the direction is right, go to TWRP, mount system, delete the old bootanimation. If the new one is not that much bigger then you could just copy it there, set permissions to rw-r--r--. But if the new animation is significantly bigger, you'll have to delete some bloatware first.
Thanks for that. The odd thing is, when I run DF in the terminal, it shows I have 20mb free. The boot animation file I am trying to copy is 6mb.
I'll keep poking around. If it doesn't work, it doesn't. It's not hugely important
Hi all,
I'm having issues installing system apps on my rooted htc one m7. I am using root explorer to copy the apk from my downloads to system/app but either one of two things happens -
1 - As soon as I press copy the phone crashes, upon rebooting the apk is nowhere to be seen in system/app
2- The copy works, I set the correct permissions but as soon as r/o is remounted the apk is deleted (leave and re-enter the folder and it's gone) if I reboot the phone without remounting r/o the apk is deleted as well
I have rooted with SuperSU v2.71 and am using team win recovery project v3.0.0. The android version is up-to-date (5.0.2) and busybox is correctly installed. I have also tried using the terminal emulator, but once again it seems to delete the apk upon remounting r/o. Of course I have also tried different apk's, all with the same results.
adamrob1511 said:
Hi all,
I'm having issues installing system apps on my rooted htc one m7. I am using root explorer to copy the apk from my downloads to system/app but either one of two things happens -
1 - As soon as I press copy the phone crashes, upon rebooting the apk is nowhere to be seen in system/app
2- The copy works, I set the correct permissions but as soon as r/o is remounted the apk is deleted (leave and re-enter the folder and it's gone) if I reboot the phone without remounting r/o the apk is deleted as well
I have rooted with SuperSU v2.71 and am using team win recovery project v3.0.0. The android version is up-to-date (5.0.2) and busybox is correctly installed. I have also tried using the terminal emulator, but once again it seems to delete the apk upon remounting r/o. Of course I have also tried different apk's, all with the same results.
Click to expand...
Click to collapse
/system is write protected by the kernel. You Ned a custom kernel or you must work from a custom recovery.
Sent from my HTC One using XDA Labs
I have come across an issue with the latest SuperSU and Nougat for the OnePlus 3 with those apps not seeing root and to fix...
u will have to get the su file from the lastest SuperSU zip in the arm64 folder and use twrp's file manager to copy file to system/bin folder, make sure u mount system in Advanced 1st.
Thanks to @matze19999