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.
Related
Hi,
I've crosscompiled a couple of useful command line applications (including binutils, gcc, make) to Android -- they work fine if I just move all the files to an Android device, or run them from an SD card etc.
Now I'm wondering what the best way to package them is -- last time I checked, an APK couldn't contain files in /system/bin or the likes, so if I want stuff installed in standard locations, that rules out using an APK (obviously that could be worked around by creating an empty app and just including all related files in the data storage area, and live with the fact that the files aren't where they ideally belong, as long as PATH is set correctly, shouldn't matter too much -- or do any devices mount the data area with the "noexec" bit?).
The other possibility I've considered is just making it a zip file to be installed through custom recoveries - unfortunately I'm running into problems there: trying to use ClockworkMod Recovery 6.0.1.0 on a Galaxy Nexus to install the zip file results in "Installing update..." immediately followed by "Installation aborted." -- that's despite the fact that signature verification works fine when enabled (I've used signing-tools to sign the zip file. Other than the META-INF directory created by signing-tools, the zip file contains system/bin/gcc, system/bin/make and friends). Am I doing anything wrong there?
And, of course, is there a third, even better, way to package command line tools that I'm missing?
I am having trouble using Android File Transfer after I tested out ShoStock for a couple of days and was wondering if anyone could offer some help. The trouble is that when I connect my phone to my computer (Macbook Pro running 10.8.3), Android File Transfer starts up and I can transfer files fine to the internal sdcard (usually), but I can't transfer files to the external sdcard. I switch over to the external sdcard view, drag a file over, and then get an error message from AFT telling me I need to restart my phone.
More information:
I did not have any problems with this until after I tested out ShoStock (just curious about it). I ran it for two days and then decided to return to Carbon Rom (very nice rom, btw. It's my DD). When I went back to Carbon, I did all the wipes, ran a kernel cleaning script, formatted system, then flashed. I had some problems related to MTP after that wipe - MTP would not set in the kernel (using STweaks) or in the rom settings. So, I did another full wipe etc. MTP sticks, but it still won't work with the external sdcard. I can use adb to move files to my sdcard, but I rely on MTP for syncing itunes with my phone so I need it work!
I have tried enabling/disabling adb, by the way. Doesn't work.
Also, when I tested out ShoStock, I just used the included kernel. For Carbon, I use AJK v1.49.
Thanks!
---------
PROBLEM SOLVED!
In case anyone encounters this issue, here's what I did:
Using ES File Explorer (or a similar file explorer with root privileges), mount your system as r/w (that means mount "/" as r/w)
Navigate to root and open default.prop in a suitable text editor (I like the ES editor)
Modify this line: persist.sys.usb.config=
To look like this: persist.sys.usb.config=mtp,adb
You might also check that ro.secure is ro.secure=0 (mine was inexplicably set to 1, which is probably why STweaks thought that I didn't have root)
I came across this because I was actually looking for vold.fstab. I couldn't remember where it was, but noticed the default.prop and thought I'd have a look. It was actually set to usb_mount_storage (or something of the like).
Unhappy [Q] Problems with deleting files and replacing sounds
HI all! New use here.
I superuser'd my phone, routed my phone, installed CM11 and all is well. It was my understanding that with apps like RootBrowser and or SuperManager i could browse to files change permissions and delete and remove them or replace them.
I am unable to change my lock sound or boot animation.
Ive granted the permissions to the apps and am operating the root browsers in Root mode. (sorry if my terminology is wrong but im new to this) When i try to replace the files in system/media or system/media/audio/ui they simply dont work, "operation failed". I am able to change the permissions on the replacement files going into these directories to match those im overwriting but its still fails.
Ive even successfully deleted the default lock sound but when i paste the new one into the folder it fails and says stuff like "out of space" or "no room" and then when i shut app and go back in the original file is back!
Can anyone help with this as my lovely rooted phone is being very difficult.
Your partition is mounted as read-only, that`s why you get "operation failed".
Mount it as read / write and should be ok.
ngl_ro said:
Your partition is mounted as read-only, that`s why you get "operation failed".
Mount it as read / write and should be ok.
Click to expand...
Click to collapse
Thank you. I now know what to do but not how to do it? Are you able to help or link me to a post on how to do that?
Many thanks
ngl_ro said:
Your partition is mounted as read-only, that`s why you get "operation failed".
Mount it as read / write and should be ok.
Click to expand...
Click to collapse
When i use the app SuperManager to browse the file system to "system" folder it asks me "If you want to modify the file in teh system, you have to mount the system image first. Please choose access mode: System IMage: R/O"
then
"Do nothing Read only R/W" so i chose R/W but that does not fix the problem?
My errors i get are "not enough free space" well there is plenty of that!
So confused....
Any thoughts
Just ignore the "not enough free space".
Cant help you with RootBrowser or SuperManager because I never used them. I use ES File Explorer, and mounting partitions with it always solved my problems with not being able to delete / modify system files / apps.
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
A little background first. Flashed stock recovery and my original first backup in order to take OTA for Marshmallow. OTA wouldn't take so I downloaded / installed MM update successfully. Currently at 6.0, 3.38.502.12. Then, re-unlocked bootloader (S-ON) and flashed TWRP 3.0.2.0. I then immediately created a full backup successfully before rooting.
Since that point, I've been unable to create another backup. I've also had countless problems trying to flash anything at all like custom ROMs and such. Keep having to revert to my unrooted backup post-MM update. The problem had to occur somewhere after my first successful TWRP backup post-MM update and now. Puzzling part is that I restored this same successful backup then without leaving TWRP, I immediately tried to do another backup and it fails the exact same way.
Recovery.log shows:
* MD5 Created.
Backing up System...
Error opening: '/system/app/Ds' (Not a directory)
I:Error in Generate_TarList!
Error creating backup.
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
I've tracked this down and it does indeed appear to be a directory "Ds". Inside as a sub-directory called 'oat' with Ds.apk inside of that, which is the Dolby Audio service.
I'm completly stumped. Any ideas?
Update, in the /system/app/ (list of apps) it looks like there is an oat subdirectory followed by arm64 then filename.odex:
/system/app/BasicDreams/oat/arm64/BasicDreams.odex
However, when I browse to the problem app "Ds"... oat does not appear as a directory.
This could be a simple fix then?? Coudn't I just obtain root again, somehow change that oat to a directory and hope I see the rest of the subdirectories and files there?
OR... could I find Ds.odex somewhere and re-create the file structure?
Better yet! Would someone out there be able to give me or post a link for Ds.odex? Would it be as easy as me making a sub-directory called oat/arm64 and placing this Ds.odex file in there??
Any help would be much appreciated.
sirvalence said:
Update, in the /system/app/ (list of apps) it looks like there is an oat subdirectory followed by arm64 then filename.odex:
/system/app/BasicDreams/oat/arm64/BasicDreams.odex
However, when I browse to the problem app "Ds"... oat does not appear as a directory.
This could be a simple fix then?? Coudn't I just obtain root again, somehow change that oat to a directory and hope I see the rest of the subdirectories and files there?
OR... could I find Ds.odex somewhere and re-create the file structure?
Better yet! Would someone out there be able to give me or post a link for Ds.odex? Would it be as easy as me making a sub-directory called oat/arm64 and placing this Ds.odex file in there??
Any help would be much appreciated.
Click to expand...
Click to collapse
I don't have any oat directories under /system/app/(app name)/oat/ARM64/...
Only thing that is in the app directory (for me) is the .apk, and at times, a lib subdirectory (webviewgoogle is like that, which has an arm and arm64 directory under that).
I'm running VenomRom which may handle this differently.. it's prerooted and whatnot.
I also disabled boomsound which I think also disabled the Dolby sound system app from running. Viper is better [emoji2]
Id back up your internal storage again, ruu, flash twrp 3.0.0-2, boot into recovery, let it make system writable, reboot into recovery again, and see what happens.
Or flash a pre-rooted sense rom instead of stock.
I honestly couldn't get this stupid AT&T varient working correctly until I s-off'd, updated Sid to developer, then run dev ruu. Works great now.
Sent from my HTC One M9 using XDA-Developers mobile app
grandpajiver said:
I don't have any oat directories under /system/app/(app name)/oat/ARM64/...
Only thing that is in the app directory (for me) is the .apk, and at times, a lib subdirectory (webviewgoogle is like that, which has an arm and arm64 directory under that).
I'm running VenomRom which may handle this differently.. it's prerooted and whatnot.
I also disabled boomsound which I think also disabled the Dolby sound system app from running. Viper is better [emoji2]
Id back up your internal storage again, ruu, flash twrp 3.0.0-2, boot into recovery, let it make system writable, reboot into recovery again, and see what happens.
Or flash a pre-rooted sense rom instead of stock.
I honestly couldn't get this stupid AT&T varient working correctly until I s-off'd, updated Sid to developer, then run dev ruu. Works great now.
Sent from my HTC One M9 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks, yeah I'm having nothing but trouble since moving to MM. Each time, I can RUU back to stock ATT US and everything is fine. Not sure if it happens during my first TWRP pre-root backup, or the restore process. I looked at the recovery.log of said backup and nothing looked different regarding the /system/apps. I've since tried a few times and it just seems to throw a few /system/apps into another directory altogether, no rhyme or reason. Last try, there wasn't even a Ds directory as it disappeared. A Ds 0 byte file then appeared at /system level. This happened with 10 or so other random system apps. WEIRD! Maybe I should just S-OFF. I've never done that or changed my MID or SID for that matter. I'm still fairly new to this.
sirvalence said:
Thanks, yeah I'm having nothing but trouble since moving to MM. Each time, I can RUU back to stock ATT US and everything is fine. Not sure if it happens during my first TWRP pre-root backup, or the restore process. I looked at the recovery.log of said backup and nothing looked different regarding the /system/apps. I've since tried a few times and it just seems to throw a few /system/apps into another directory altogether, no rhyme or reason. Last try, there wasn't even a Ds directory as it disappeared. A Ds 0 byte file then appeared at /system level. This happened with 10 or so other random system apps. WEIRD! Maybe I should just S-OFF. I've never done that or changed my MID or SID for that matter. I'm still fairly new to this.
Click to expand...
Click to collapse
So worth the 25 dollars. But you need your system up and rooted for that to work.
But yeah, the dev edition SID 01 worked for me.
Made it way easier to work with and taking that ruu was magic.
Oh, also, do you have an sdcard? There is always the rom.zip method... placing the appropriate 0PJAIMG.ZIP in the root of the sdcard then rebooting into download mode works nicely.
Sent from my HTC One M9 using XDA-Developers mobile app