Develop Bugs

[Q] How to delete files/folders from /sdcard?

After rooting my Galaxy Nexus with Wug's Root Toolkit and sim unlocking with the Docomo hack, and then restoring my apps/data (can't recall if I restored from GN Toolkit or Root Toolkit), my camera app was messed up--could snap pix but they didn't save; and video always fc'ed. The solution turns out to be to rename or delete the DCIM folder. I couldn't delete--so I renamed. Now I am trying to delete that DCIM.old folder and contents (eating up 1+G on my storage), but cannot delete either individual files or the folder. I'm sure there is a simple solution, but I can't find it. Help (even with a condescending attitude ) much appreciated!
zzcat

If you use a file explorer, that has it's standard directory at / then all you need to do is navigate to /mnt/sdcard/ then make sure it's mounted as R/W and not R/O, if all that is the way I said it, you shouldn't have problems deleting anything, if so, use the ADB and type:
Code:
adb shell rm /mnt/sdcard/<Folder>
That should then do the trick

You could also try the following Apps:
- Rootexplorer (paid)
- Astro File Manager

familyguy59 said:
If you use a file explorer, that has it's standard directory at / then all you need to do is navigate to /mnt/sdcard/ then make sure it's mounted as R/W and not R/O, if all that is the way I said it, you shouldn't have problems deleting anything, if so, use the ADB and type:
Code:
adb shell rm /mnt/sdcard/<Folder>
That should then do the trick
Click to expand...
Click to collapse
FamilyGuy, thanks for the suggestion, the problem seems to be bad permissions and I can't figure out how to fix them. Tried the "fix permissions" from recovery, as well as when booted, to no avail.
Typing
adb shell rm -rf /[directory]
gives me "permission denied"
So tried
chmod 666 /sdcard/.../*
but get an "operation not permitted" message.
So I'm really stuck here...

familyguy59 said:
If you use a file explorer, that has it's standard directory at / then all you need to do is navigate to /mnt/sdcard/ then make sure it's mounted as R/W and not R/O, if all that is the way I said it, you shouldn't have problems deleting anything, if so, use the ADB and type:
Code:
adb shell rm /mnt/sdcard/<Folder>
That should then do the trick
Click to expand...
Click to collapse
Update: solved
boot into recovery mode
mount /data
adb shell
rm, rmdir etc. all work as expected from here, no need to chown or chmod anything
zz

I see you've solved this, but i thought i would throw this in anyway...
The easy way is to delete the files from /data/media
The sdcard directory is a symlink, so go to the true folder and you should have more success...

Sometimes the file ownerships get messed up after a cycle of recovering the OS and restoring files.
http://forum.xda-developers.com/showthread.php?t=1515291&page=2
If you have any other directories/files that you can't modify or delete, then boot into CWM recovery, plug in the USB cable, go into adb shell. Also make sure that /data is mounted in the CWM mounts menu. Then:
cd /data/media
chown -R media_rw.media_rw *
This fixed it for me and others.

cmstlist said:
Sometimes the file ownerships get messed up after a cycle of recovering the OS and restoring files.
http://forum.xda-developers.com/showthread.php?t=1515291&page=2
If you have any other directories/files that you can't modify or delete, then boot into CWM recovery, plug in the USB cable, go into adb shell. Also make sure that /data is mounted in the CWM mounts menu. Then:
cd /data/media
chown -R media_rw.media_rw *
This fixed it for me and others.
Click to expand...
Click to collapse
Thanks for this and other suggestions--my solution was trial and error, thrashing around in the dark (my unix command line chops are really, really rusty), and these are far more elegant. It's good to understand the underlying problem, your wisdom is appreciated.
Yes, permissions were messed up after rooting and applying a sim unlock hack, wiping and restoring from pre-unlock backup set. I see it so clearly now...

Problem can somebody help me?
Hello. I have a problem with my motorola defy+ running on gb 2.3.6 and is not ROOTED. Still he has an annoyng problem. After installing an aplication (not from the market) i saw that it didn't save data on the sd card. I uninstalled it and after a data factory reset i install apps such as temple run and Brother in Arms 2. At temple run it gave me this mesage
"File Access Problem Caution, unable to write files. This means your game progress can't be saved! Reason: Access to the path "/mnt/sdcard/Android/data/com.imangi.templerun/files/spaceholder.dat" is denied."
Also at Brother in Arms 2 the game didn't save. I rest the phone abouat 7-8 times.I changed the sd card. Note that the card was a 16 gb kingmax class 6 and put the 2 gb card that came with the phone. It all work smoothly. So what is the problem the sd card or the phone's software. Please answer i'm desparate and tired of wasting time.

This thread is about the Samsung Galaxy Nexus which has no external SD and uses a very different storage structure. I'm afraid we can't really help you here. Try the Defy forum.
Sent from my Galaxy Nexus using Tapatalk 2

zzcat said:
FamilyGuy, thanks for the suggestion, the problem seems to be bad permissions and I can't figure out how to fix them. Tried the "fix permissions" from recovery, as well as when booted, to no avail.
Typing
adb shell rm -rf /[directory]
gives me "permission denied"
So tried
chmod 666 /sdcard/.../*
but get an "operation not permitted" message.
So I'm really stuck here...
Click to expand...
Click to collapse
Before chmod the folder, you needed to be root by entering 'su' after 'adb shell' .
It worked from cwm, because cwm gives root access.
Linux/Android are all about permissions.
Sent from my i9250

cmstlist said:
Sometimes the file ownerships get messed up after a cycle of recovering the OS and restoring files.
http://forum.xda-developers.com/showthread.php?t=1515291&page=2
If you have any other directories/files that you can't modify or delete, then boot into CWM recovery, plug in the USB cable, go into adb shell. Also make sure that /data is mounted in the CWM mounts menu. Then:
cd /data/media
chown -R media_rw.media_rw *
This fixed it for me and others.
Click to expand...
Click to collapse
I tried your theory, and it didn't work, still get the message" unable to change ownership permission denied, in recovery mode.
we are still trying to find a solution, here is the discussion: http://www.slatedroid.com/topic/32434-i-got-my-smartq-t20/page__st__260 on Post # 277

rocketero said:
I tried your theory, and it didn't work, still get the message" unable to change ownership permission denied, in recovery mode.
we are still trying to find a solution, here is the discussion: http://www.slatedroid.com/topic/32434-i-got-my-smartq-t20/page__st__260 on Post # 277
Click to expand...
Click to collapse
Sorry to hear that. It sounds like the problem you are having is with a completely different device, so I can't really say why this may be occurring - I don't know how your device's file system is structured. This advice is specifically for the Galaxy Nexus. If a version of CWM exists for your smartQme device, I can't speak to whether it works properly and interprets commands the same way ours does.

cmstlist said:
Sorry to hear that. It sounds like the problem you are having is with a completely different device, so I can't really say why this may be occurring - I don't know how your device's file system is structured. This advice is specifically for the Galaxy Nexus. If a version of CWM exists for your smartQme device, I can't speak to whether it works properly and interprets commands the same way ours does.
Click to expand...
Click to collapse
it's a 9.8 inches tablet branded named called "LePanII'. it has ICS now, before we had Honeycomb 3.2.1.
The manufacture of this tablet did such a bad partitioning that the /system partition was left only with merely 4MB of free space in it.

rocketero said:
it's a 9.8 inches tablet branded named called "LePanII'. it has ICS now, before we had Honeycomb 3.2.1.
The manufacture of this tablet did such a bad partitioning that the /system partition was left only with merely 4MB of free space in it.
Click to expand...
Click to collapse
Good luck with your issue. I doubt it's related to the one we were having on the GNex though.

cmstlist said:
Sometimes the file ownerships get messed up after a cycle of recovering the OS and restoring files.
http://forum.xda-developers.com/showthread.php?t=1515291&page=2
If you have any other directories/files that you can't modify or delete, then boot into CWM recovery, plug in the USB cable, go into adb shell. Also make sure that /data is mounted in the CWM mounts menu. Then:
cd /data/media
chown -R media_rw.media_rw *
This fixed it for me and others.
Click to expand...
Click to collapse
Sorry if my question is dumb.
Does this command solve the problem for all the folders and sub-folders in sdcard? Thank you for your help!
Sent from my Galaxy Nexus

/data/media # chown -R media_rw.media_rw*
BusyBox v1.20.2-jb static (2012-10-25 21:29 +0100) multi-call binary.
Usage: chown [-RhLHP]... OWNER[<.|:>[GROUP]] FILE...
Change the owner and/or group of each FILE to OWNER and/or GROUP
-R Recurse
-h Affect symlinks instead of symlink targets
-L Traverse all symlinks to directories
-H Traverse symlinks on command line only
-P Don't traverse symlinks (default)
I got this after giving the commands from recovery in adb shell.
What does that mean?

Jar3112 said:
/data/media # chown -R media_rw.media_rw*
BusyBox v1.20.2-jb static (2012-10-25 21:29 +0100) multi-call binary.
Usage: chown [-RhLHP]... OWNER[<.|:>[GROUP]] FILE...
Change the owner and/or group of each FILE to OWNER and/or GROUP
-RRecurse
-hAffect symlinks instead of symlink targets
-LTraverse all symlinks to directories
-HTraverse symlinks on command line only
-PDon't traverse symlinks (default)
I got this after giving the commands from recovery in adb shell.
What does that mean?
Click to expand...
Click to collapse
OK solved, I forgot the space before the *!
Worked like a charm!!
Sent from my Galaxy Nexus

[RECOVERY] CWM 6.x - i9505 Ex#4

Hey, I bring to you, Clockworkmod Recovery or commonly known as CWM for your beloved i9505 (S4). Giving your device the ability to flash your favourite custom ROMs, Kernels, Mods in the future. Thankyou to 'as i9000' for giving me the stock recovery. Note: This thread will be moved to the i9505 section once its created.
This has not been tested by me and is still experimental. I hold no responsibility
for any problems caused. YOU! Are trying this at your own risk. Don't blame me that I wasted your $700.
Put a scare in you didn't I?
I have provided the stock recovery if you encounter any issues, you can always flash back. It is Odin flashable.
Downloads:
CWM Experimental #4: http://d-h.st/ZOk
Stock Recovery: http://d-h.st/LqC
Changelog:
Code:
[I][U]Experimental #4[/U][/I]
Display fixes
recovery.fstab fix
[I][U]Experimental #3[/U][/I]
Working (everything) [B]- revert[/B]
[I][U]Experimental #2[/U][/I]
Skipped
[I][U]Experimental #1[/U][/I]
Public release

emwno said:
Hey, I bring to you, Clockworkmod Recovery or commonly known as CWM for your beloved i9505 (S4). Giving your device the ability to flash your favourite custom ROMs, Kernels, Mods in the future. Thankyou to 'as i9000' for giving me the stock recovery. Note: This thread will be moved to the i9505 section once its created.
This has not been tested by me and is still experimental. I hold no responsibility
for any problems caused. YOU! Are trying this at your own risk. Don't blame me that I wasted your $700.
Put a scare in you didn't I?
I have provided the stock recovery if you encounter any issues, you can always flash back. It is Odin flashable.
Downloads:
CWM Experimental #1: http://d-h.st/khT
Stock Recovery: http://d-h.st/LqC
Changelog:
Code:
[I][U]Experimental #1[/U][/I]
Public release
Click to expand...
Click to collapse
It does not work (it doesnt boot)...

samovog said:
It does not work (it doesnt boot)...
Click to expand...
Click to collapse
adb pull /tmp/recovery.log

emwno said:
adb pull /tmp/recovery.log
Click to expand...
Click to collapse
Cannot. Flashed Chainfires root package, now the phone reboots itself...
Does anyone have a link to a stock odin firmware so i can reflash the phone and send you that file ?

samovog said:
Cannot. Flashed Chainfires root package, now the phone reboots itself...
Does anyone have a link to a stock odin firmware so i can reflash the phone and send you that file ?
Click to expand...
Click to collapse
This: http://www.orpheusdroid.com/xda/ credit to vijai2011. Flash that, then my provided stock recovery. (if still not working, ill provide the bootloader and boot.img)

emwno said:
This: http://www.orpheusdroid.com/xda/ credit to vijai2011. Flash that, then my provided stock recovery. (if still not working, ill provide the bootloader and boot.img)
Click to expand...
Click to collapse
It does not let me flash! It says:
Unsupported dev_type
i can flash other files (recovery, ...).

samovog said:
It does not work (it doesnt boot)...
Click to expand...
Click to collapse
do not work

[email protected] said:
do not work
Click to expand...
Click to collapse
adb pull /tmp/recovery.log

I tried to pull the log:
C:\Old stuff\I9300\Odin>adb pull /tmp/recovery.log
remote object '/tmp/recovery.log' does not exist
C:\Old stuff\I9300\Odin>adb shell
[email protected]:/ $ cd /tmp
cd /tmp
/system/bin/sh: cd: /tmp: No such file or directory
2|[email protected]:/ $
Is there another path in which I could look for the log you want?
/primpa

primpa said:
I tried to pull the log:
C:\Old stuff\I9300\Odin>adb pull /tmp/recovery.log
remote object '/tmp/recovery.log' does not exist
C:\Old stuff\I9300\Odin>adb shell
[email protected]:/ $ cd /tmp
cd /tmp
/system/bin/sh: cd: /tmp: No such file or directory
2|[email protected]:/ $
Is there another path in which I could look for the log you want?
/primpa
Click to expand...
Click to collapse
Code:
adb pull /cache/recovery/last_log
Code:
adb pull /cache/recovery/log

I'll be working with ewmno to try and get a working version out. (I'm only tester :highfive: )

Annie the Eagle said:
I'll be working with ewmno to try and get a working version out. (I'm only tester :highfive: )
Click to expand...
Click to collapse
Sweet. Let me know if you guys want me to try something =)
/p
---------- Post added at 11:44 PM ---------- Previous post was at 11:27 PM ----------
emwno said:
Code:
adb pull /cache/recovery/last_log
Code:
adb pull /cache/recovery/log
Click to expand...
Click to collapse
Unfortunately it won't work either:
Code:
[email protected]:/ # cd /cache/
[email protected]:/cache # ls -l
-rwx------ system system 8 2013-04-27 23:43 hidden_volume.txt
drwxrwx--- root root 1970-01-01 01:00 lost+found
[email protected]:/cache #

I guess im gonna have to start fresh, blindly

emwno said:
I guess im gonna have to start fresh, blindly
Click to expand...
Click to collapse
Just let me know if you need me to do something to help you out with this. I'm not a programmer, but I can try stuff =)
/p

I created my own CWM using the fstab.qcom and stock recovery. Here's the last_log file....

The-Kevster said:
I created my own CWM using the fstab.qcom and stock recovery. Here's the last_log file....
Click to expand...
Click to collapse
Whats wrong with it? need to know what im looking for..

Ok. The Samsung screen loads and there's text in the top left saying "loading recovery..." this is normal on stock recovery.
The screen then goes black and the device reboots. Nothing displayed on screen. Either it fails and reboots the device or there's instructions missing so with nothing left to do it reboots.
Sent from my GT-I9505 using Tapatalk 2

The-Kevster said:
Ok. The Samsung screen loads and there's text in the top left saying "loading recovery..." this is normal on stock recovery.
The screen then goes black and the device reboots. Nothing displayed on screen. Either it fails and reboots the device or there's instructions missing so with nothing left to do it reboots.
Sent from my GT-I9505 using Tapatalk 2
Click to expand...
Click to collapse
Check your recovery.fstab and what did you use to compile CWM?

Just builder.clockworkmod. The behavior is the same as your cwm.
Anything else I can do to help?
Sent from my GT-I9505 using Tapatalk 2

The-Kevster said:
Just builder.clockworkmod. The behavior is the same as your cwm.
Anything else I can do to help?
Sent from my GT-I9505 using Tapatalk 2
Click to expand...
Click to collapse
No not yet, still figuring it out. Will post a new version, i got an idea of what may have gone wrong.

[Q] URGENT: Lock Screen stuck with Game Keyboard

Hi all,
I have gotten myself into a bit of a dilemma here - I was playing GTA III with the input method set to "Game Keyboard", and then accidentally pressed the power button on my HOX. Now my phone is stuck with a lock screen (with pin code to unlock), but I cannot enter the pin as the damn game keyboard is set as the input method.
Is there any way to uninstall the game keyboard app from recovery, or a way to change the input method before the unlock screen.
I am running out of ideas, and my last resort is to restore a nandroid backup from a week ago ( I really dont want to do this as this means losing all changes since a week ago).
Any urgent help appreciated.
HTC One X
ARHD 21.0
CWM touch recovery

When you reboot it's still there? Try wiping the dalvik in recovery

Try this...
Code:
adb remount
adb shell
rm /data/app/xxxx.apk
XXX=name of app.apk

is there a way to list the contents of /data/app is adb as I dont know what the name of the apk is

carbon5000 said:
is there a way to list the contents of /data/app is adb as I dont know what the name of the apk is
Click to expand...
Click to collapse
I don't remember the command to mount it to PC via recovery... may b someone else can help you with it... Tried remembering, can't recollect...
Or you can give me the link of the app your using? I can install it and tell you the apk file name! :good:
---------- Post added at 02:38 PM ---------- Previous post was at 02:36 PM ----------
Or you can flash this recovery: http://d-h.st/HiV
It has aroma file manager by which you can take a look...

vin4yak said:
I don't remember the command to mount it to PC via recovery... may b someone else can help you with it... Tried remembering, can't recollect...
Or you can give me the link of the app your using? I can install it and tell you the apk file name! :good:
---------- Post added at 02:38 PM ---------- Previous post was at 02:36 PM ----------
Or you can flash this recovery: http://d-h.st/HiV
It has aroma file manager by which you can take a look...
Click to expand...
Click to collapse
Just realised I have the app installed on my tablet as well, so got the apk name from that - but after running the commands you suggested, I got the following error:
C:\Android\SDK\platform-tools>adb devices
List of devices attached
HT266W104018 recovery
C:\Android\SDK\platform-tools>adb remount
remount failed: Success
C:\Android\SDK\platform-tools>adb shell
~ # rm /data/app/com.locnet.gamekeyboard-1.apk
rm: can't remove '/data/app/com.locnet.gamekeyboard-1.apk': No such file or directory
~ #
am i missing something?

carbon5000 said:
Just realised I have the app installed on my tablet as well, so got the apk name from that - but after running the commands you suggested, I got the following error:
C:\Android\SDK\platform-tools>adb devices
List of devices attached
HT266W104018 recovery
C:\Android\SDK\platform-tools>adb remount
remount failed: Success
C:\Android\SDK\platform-tools>adb shell
~ # rm /data/app/com.locnet.gamekeyboard-1.apk
rm: can't remove '/data/app/com.locnet.gamekeyboard-1.apk': No such file or directory
~ #
am i missing something?
Click to expand...
Click to collapse
Everything seems OK...
Maybe try from the recovery....
Sent from my HTC One X using xda app-developers app

Is it a system app? if so then use this directory:
/system/apps
Also if it doesn't work then put a -r after rm... mostly it's in /data/app

SOLVED: just needed to mount the partitions in recovery before doing the adb commands.
Thanks for your help!!!!

Moto 360 5.0.1 update file

http://android.clients.google.com/p...ned-metallica-LWX48P-from-KNX01S.98cdf4ca.zip
to update:
Go into a shell on the watch with su and...
mount -o rw,remount /dev/block/mmcblk0p15 /cache
mv /sdcard/98cdf4ca90c4693edd379d67cdcf86e283058b81.signed-metallica-LWX48P-from-KNX01S.98cdf4ca.zip /cache/98cdf4ca90c4693edd379d67cdcf86e283058b81.signed-metallica-LWX48P-from-KNX01S.98cdf4ca.zip
echo 'boot-recovery ' > /cache/recovery/command
echo '--update_package=/cache/98cdf4ca90c4693edd379d67cdcf86e283058b81.signed-metallica-LWX48P-from-KNX01S.98cdf4ca.zip' >> /cache/recovery/command
echo '--wipe_cache' >> /cache/recovery/command
echo 'reboot' >> /cache/recovery/command
reboot recovery

Nice ty

See above

abuttino said:
See above
Click to expand...
Click to collapse
I was trying to do it thought ADB I'm just new to this and I ended up re posting in the wrong thread.
Im Not new to flashing via recover on phones but on adb through commands I always feel sketchy about it.

I keep getting permission denied
Ive ran root a few times I have the drivers install right for sure not sure what im doing wrong

NUGZZ420 said:
I keep getting permission denied
Ive ran root a few times I have the drivers install right for sure not sure what im doing wrong
Click to expand...
Click to collapse
Throw an "su" command in the shell before anything else. It will only work if you're rooted.

I don't really get it how to connect via shell to my watch. Is it the same as installing apk's over adb bluetooth debugging bridge?
Could you provide further instructions how to install the update manually?
Thanks!

Kamekazegoldi said:
I don't really get it how to connect via shell to my watch. Is it the same as installing apk's over adb bluetooth debugging bridge?
Could you provide further instructions how to install the update manually?
Thanks!
Click to expand...
Click to collapse
Is your watch rooted? If not, you can't do it

No further questions thanks!

abuttino said:
http://android.clients.google.com/p...ned-metallica-LWX48P-from-KNX01S.98cdf4ca.zip
to update:
Go into a shell on the watch with su and...
mount -o rw,remount /dev/block/mmcblk0p15 /cache
mv /sdcard/98cdf4ca90c4693edd379d67cdcf86e283058b81.signed-metallica-LWX48P-from-KNX01S.98cdf4ca.zip /cache/98cdf4ca90c4693edd379d67cdcf86e283058b81.signed-metallica-LWX48P-from-KNX01S.98cdf4ca.zip
echo 'boot-recovery ' > /cache/recovery/command
echo '--update_package=/cache/98cdf4ca90c4693edd379d67cdcf86e283058b81.signed-metallica-LWX48P-from-KNX01S.98cdf4ca.zip' >> /cache/recovery/command
echo '--wipe_cache' >> /cache/recovery/command
echo 'reboot' >> /cache/recovery/command
reboot recovery
Click to expand...
Click to collapse
Worked (almost) perfect! Except, the "mv" command caused it to error out with "Invalid Arguement:Cross-Device Link" (Due to the implementation of blocked cross device linking with the mv command, bypassable by just cp'ing) Just replaced it with "cp" and the problem was solved.
Though this has already been said, the 4.4w1 insecure boot.img no longer roots 5.0.1. Probably due to incompatibilliuies, I'll work up a new rooted boot.img this weekend. Sadly looks like its going to require flashing the boot.img, not just booting it.

How do you go on a shell on your watch?

You have to have the bootloader unlocked and rooted hooked up via Modded USB cable. Then use the super tool script iin the dev section to install drivers for fastboot. Then back out to that folder make sure you not clicked on anything right click anywhere I think but I right click on the fastboot file while holding the SHIFT key and open in command window the type adb devices to make sure you hooked up right and you have accepted it on your phone Witch you must click accept the adb on your phone to accept the computer access. Once you know your hooked up right type adb shell and boom there you go.

having some trouble.
I've got shell, and then su, i've got a prompt with #
Tried the mv command, and like that other guy, got a cross link error. So i tried cp instead of mv, and now get no such file or directory...
I should mention I'm doing this from adb on Windows. Am I missing something??

Prfndhatrdofman said:
having some trouble.
I've got shell, and then su, i've got a prompt with #
Tried the mv command, and like that other guy, got a cross link error. So i tried cp instead of mv, and now get no such file or directory...
I should mention I'm doing this from adb on Windows. Am I missing something??
Click to expand...
Click to collapse
Try this its what worked for me
coming from KNX01S, but I keep running into "Status 7" with the stock recovery and "Error executing updater script" with TWRP. Anybody have any better luck flashing this?
SOLVED!: I removed the get prop lines in the beginning of the update script and sideloaded in TWRP!
If anybody would like the modified package it can be found here: https://dl.dropboxusercontent.com/u/...360/update.zip
This was not my fix only copied and pasted

NUGZZ420 said:
Try this its what worked for me
coming from KNX01S, but I keep running into "Status 7" with the stock recovery and "Error executing updater script" with TWRP. Anybody have any better luck flashing this?
SOLVED!: I removed the get prop lines in the beginning of the update script and sideloaded in TWRP!
If anybody would like the modified package it can be found here: https://dl.dropboxusercontent.com/u/...360/update.zip
This was not my fix only copied and pasted
Click to expand...
Click to collapse
That Dropbox link seems to be down, do you still have that modified TWRP zip?
Found the original post, here's the original link: https://dl.dropboxusercontent.com/u/9407677/Moto 360/update.zip
Looks like the link text got shortened when copying/pasting, but it's all good now! Thanks for sharing!

Prfndhatrdofman said:
having some trouble.
I've got shell, and then su, i've got a prompt with #
Tried the mv command, and like that other guy, got a cross link error. So i tried cp instead of mv, and now get no such file or directory...
I should mention I'm doing this from adb on Windows. Am I missing something??
Click to expand...
Click to collapse
Make sure your using "/cache" instead of "/cache/"

nissanskylinebam said:
That Dropbox link seems to be down, do you still have that modified TWRP zip?
Found the original post, here's the original link: https://dl.dropboxusercontent.com/u/9407677/Moto 360/update.zip
Looks like the link text got shortened when copying/pasting, but it's all good now! Thanks for sharing!
Click to expand...
Click to collapse
Sorry I had been running all day and beat here my own just in case it helps same zip just my own link
5.0.1 update zip Mirror https://www.dropbox.com/s/naliirhnblh6ihg/update.zip?dl=0

npjohnson said:
Worked (almost) perfect! Except, the "mv" command caused it to error out with "Invalid Arguement:Cross-Device Link" (Due to the implementation of blocked cross device linking with the mv command, bypassable by just cp'ing) Just replaced it with "cp" and the problem was solved.
Though this has already been said, the 4.4w1 insecure boot.img no longer roots 5.0.1. Probably due to incompatibilliuies, I'll work up a new rooted boot.img this weekend. Sadly looks like its going to require flashing the boot.img, not just booting it.
Click to expand...
Click to collapse
Look forward to flashing the Rooted boot.img.
Thank you for doing it.

Update Today
In past day i have update to 5.0.1 LWX48P release. Today i have received automatic update on my watch to 5.0.1 LWX48T release. I don't know what is change but in past day I noticed a problem centering of my display; after update now the display is centered

http://shabbypenguin.com/?developer=Tools&folder=Superuser
flash that in TWRP to get root
latest update: https://mega.co.nz/#!dNBnyT7Q!qtPkmgOV-jrajJAAKDLE6cQWVHyDGi3OsEwmTq5jfOU LWX48T-from-LWX48P follow OP's instructions but change teh file names

How to Modify System files in OOS 10?

Hi,
I want to modify system files in OOS 10 but every method just fails.
Root File manager are shows that they delete the app, but it comes back after reboot.
I can delete app in TWRP but when boot up the OS, the app is back there. If I go in TWRP again to that directory the app doesn't exist but OS has the app there when booted up again. So TWRP is also failing me.
Debloater from magisk seem to work and is able to delete the apps but my main problem is that I want to modify build.prop but I can't as of yet. Nothing is able to save changes and it back to original state after reboot.
Has anyone manage to get proper access to be able to modify to system files via file manager or TWRP?

To edit build prop in oos 10 install magisk hide props config and busy box. Then open terminal and type props and choose options to add remove or change lines. Will keep researching and add a working way to change any system file but if it's anything getting put into the system twrp and magisk modules work but removing files and editing by removing bits doesn't seem to work through twrp.
---------- Post added at 02:20 PM ---------- Previous post was at 02:00 PM ----------
Appears you can mount in ADB to edit files and replace bits etc. Using the command " mount -o rw,remount / " without brackets and spaces beginning and end. Not to strong of a user with ADB but if I use the command to move an app to system combined with the mentioned command it lets me make a folder on system and puts the app into system.
So surely you can extract any file from system with ADB and then re insert it while mounted. It's long winded compared to root explorers but with Android 10 system being read only we may have to wait for a new method through root to do this again if ever possible at all.
This doesn't effect the ability to edit any part of the system for the purposes of custom ROMs but makes it near impossible to edit a running/installed ROM in Android 10 (atleast in stock os)

1. adb definitely works for uninstalling system apps. All you need to do is open an adb shell and run the following command,
Code:
pm list packages
pm uninstall --user 0 <package_name>
The list packages command will give you the appropriate package name
I use this myself and can confirm it works. I am running OOS 10 Open Beta 2.
2. I think you should be able to edit build.prop through adb shell. In case you run into /system mounting issues, reboot into recovery, manually mount system and run adb in recovery itself.
I haven't done this myself, so please tell me if it works!