I just switched to CM 10.1.3 from stock 4.1.2 and found out that most directories (Data, System, etc...) are not readable in File Manager under BMM. File Manager shows 0 files for these directories.
This does not happen on stock 4.1.2. I'v also tried Safestrap 3.65, same thing.
Does anyone know how to fix this?
Also, I tried to use my own boot animation, but phone won't boot, it stuck on black screen.
No matter where bootanimation is located, neither /system/media nor /data/local.
I figured out myself
1. manually mount system/data in mount option before using file manager
2. the bootanimation.zip should be archived as save/store without compression
Related
Hello,
I had [JVT]Galaxydroid 2.0 but decided to go back to stock JVT. Now I'm having all kinds of trouble with copying a file to /system/etc.
I flashed stock JVT over Galaxydroid and rooted with speedmod kernel. Wiped caches and wiped user data. Then I installed su+busybox with speedmod's recovery option.
Titanium Backup didn't want to recognize su and busybox but after few tries it worked. Then I tried to copy spn-conf.xml to /system/etc (mounted /system as writeable with ES Root Explorer) and it seems like it copies succesfully, but the filesize is 0 bytes and the file is empty.
Then I tried adb, but it can't mount and doesn't even recognize cp or other commands. Where did I fail and how to fix this?
Thanks in advance
I had the GLaDOS kernel installed, but I changed to Eugene's, but the Aperture boot animation is still here... How do I reset it back to the normal stock ICS animation?
Or do I really have to flash my custom ROM again?
You can pull the bootanimation.zip from your ROM (I'm not sure where it's located for you, sorry). Once you have it on your SD card, copy it and then override the one currently there using Root Explorer. Just to be safe you can rename the current one to bootanimation.bak or whatever you'd like. Be sure to set permissions on the file to match the old one (mine are rwxrwxr-x, meaning everything is checked except write for "others", but yours could be different). With Root Explorer you can do so by long-pressing the file and selecting "permissions" from the menu. It should be similar for any other root file explorer.
You can reflash your ROM, but you'll lose any other mods you've made and will need to reflash your kernel if it's a custom one. To reflash without losing data, just wipe cache and dalvik then flash.
Supersonic Evo 4G | MIUI | Tapatalk
I have a Samsung galaxy s4 with build number I545VRUFNC5.(VZW) I have rooted the phone. I tried to manually fix the ability to write to sd card. In an attempt to swap the platform.xml file, I did not realize that the permissions would automatically change. The file is located here: device/system/etc/permissions/platform.xml. I am unable to fix the permissions to the file, even with root. As a result, the phone shows no files on the internal or external card. (no files are shown when connected to PC either)
I have tried to:
Factory data reset
Change file permissions using root/es file explorer (message: sorry, operations failed)
Change file permissions using terminal emulator (emulator error is "read only file system")
flash kit kat using odin (I flashed correctly, but I still could not change the permissions to the file)
Verizon wireless assistant (will not connect to phone)
Samsung Kies (It tells me that phone is not supported)
I can make calls/text, but cannot connect to internet. I there a way that I can change the file permissions from a computer? How can I go back to the original system settings?Please help.
Note: I also downloaded previous build for phone (I545VRUEMK2) I did not put this on the phone because I'm not sure if it is safe and I'm not sure that it will fix my problem.
Thank you
Fixed Problem
Just after posting this thread, I did a factory data reset. This followed the Kit Kat flash using odin. Everything seems to working normally now.
Thank You
I have been trying to use int2ext, however flashing or placing the script directly fails to work.
There are no errors when using cwm, but when looking in a file manager the script is 0kb, and empty.
Pasting the script using ES file explorer does the same, places a empty 0kb file, this is with system mounted as r/w.
Tried using the file manager that comes with CyanogenMod but it shows an error when pasting rather than placing anything.
Different attempt with Mounts2sd, it asks to update the Init.d, but it fails with the error 'the init.d startup script cannot be copied to the system partition'
Busy box also fails to configure.
I am using CyanogenMod 10.1 for the wildfire s.
Not sure what's going on, followed all instructions when installing cyanogen originally. I will flash again, but unfortunately away from home to restore contacts once I'd re-install (though not major issue) Will go ahead with it if its recommended.
Looking to see if there might be another issue and way to resolve it.
It is partitioned just seems an issue with permissions and access.
Be happy to see the end of this low memory.
Dear fellas,
I replaced my build.prop file to an another one and my phone is not booting up anymore.
I have a rooted Xiaomi Mi 5s Plus, with custom recovery.
Can anyone advise what to do without wiping the phone completely and flashing a new ROM?
What I've tried doing:
- I had the original build.prop that the phone had before it got stuck.
- I used the file explorer in custom recovery, copied that file to the system folder in root.
- Rebooted the device, still no luck!
- After rebooting, when I reopen the recovery, and navigate to the system folder again, I don't find the file I copied to the system folder!
Any thoughts on the matter please? Thanks in advance!
Have you tried writing original Rom to the phone. Don't have much experience with that kind best I can suggest
Sent from my SM-G930V using Tapatalk
black_hawk1990 said:
Dear fellas,
I replaced my build.prop file to an another one and my phone is not booting up anymore.
I have a rooted Xiaomi Mi 5s Plus, with custom recovery.
Can anyone advise what to do without wiping the phone completely and flashing a new ROM?
What I've tried doing:
- I had the original build.prop that the phone had before it got stuck.
- I used the file explorer in custom recovery, copied that file to the system folder in root.
- Rebooted the device, still no luck!
- After rebooting, when I reopen the recovery, and navigate to the system folder again, I don't find the file I copied to the system folder!
Any thoughts on the matter please? Thanks in advance!
Click to expand...
Click to collapse
Try mount system read/write first then copy og build prop file in system partition and reboot or use aroma file manager.