There's a really simple way to prevent CyanogenMod from overwriting your custom /system changes during an update. Create the file '/system/etc/custom_backup_list.txt' with a list of files within /system that you don't want to be overwritten.
For example, to prevent CM from wiping out Swype, open adb shell and type this:
Code:
mount -o remount,rw /system
cd /system/etc
echo lib/libSwypeCore.so >custom_backup_list.txt
echo app/Swype.apk >>custom_backup_list.txt
cd /
mount -o remount,ro /system
If you use teferi's custom keymap, do this:
Code:
mount -o remount,rw /system
cd /system/etc
echo lib/libSwypeCore.so >custom_backup_list.txt
echo app/Swype.apk >>custom_backup_list.txt
echo usr/keylayout/vision-keypad.kl >>custom_backup_list.txt
echo usr/keychars/vision-keypad.kcm.bin >>custom_backup_list.txt
cd /
mount -o remount,ro /system
Then the next time you flash CM, your changes to /system will still be there. If you want to see why this works, take a look at /system/bin/backuptool.sh
Hope this helps
Thanks! This is great; now I can easily keep my Email.apk that doesn't require me to enter a alphanumeric password every time I want to use the phone.
CM probably needs to overwrite build.prop but I've been changing the LCD density in this file. Is there a way to use a seperate file to override the lcd density so that i can let CM overwrite build.prop but still maintain lcd density after a flash?
Whatever commands you put in /data/local/userinit.sh will run at boot. So in adb shell, type this for a density of 215:
Code:
cd /data/local
echo setprop qemu.sf.lcd_density 215 >userinit.sh
awesome! thank you!
Don't suppose you would know how to get the CM update to not install/auto delete after installation apks like ADWLauncher and wifi calling?
Thank you!
This may be the long lost solution to my Swype and Cyan Problems. The new Release Candidates are destroying my swype and not liking it's return after installing the new Cyan. So, if this can basically help me update without losing much, it's a god send. Especially the LCD density.
You're a genius.
Thank you.
Hmm, seems the issue is still persistent. Thanks though.
Should userinit.sh and custom_backup_list.txt survive the upgrade or should they both be included in the backup list file?
Sent from my HTC Vision using XDA App
If you look at the actual script, it seems that it ignores the backuptool if .installscript exists, and in practice, I've noticed that nothing gets saved when flashing via ROM Manager. Is this, in fact, what's happening, and is there a way around it?
sundar2012 said:
awesome! thank you!
Don't suppose you would know how to get the CM update to not install/auto delete after installation apks like ADWLauncher and wifi calling?
Click to expand...
Click to collapse
You can put the following in /data/local/userinit.sh:
mount -o rw,remount /system
for apk in ADWLauncher.apk MS-HTCVISION-KNT20-02.apk
do
rm -f /system/app/$apk
done
for package in com.android.launcher
do
pm uninstall $package
done
mount -o ro,remount /system
exit 0
Click to expand...
Click to collapse
I haven't tried this for removing the Wifi Calling app, so ymmv. I remove a much larger set of apps myself (facebook, email, live wallpapers, amazon mp3 store, DSPManager, FileManager, Browser). http://wiki.cyanogenmod.com/index.php?title=Barebones has a list of apps that can be removed safely.
@cparekh -- what e-mail app is that? Or did you just use the pre-OTA's Email.apk app?
Rc4 has the trackpad wake fm radio and speaker led fixed its workng very smooth better than rc3
Sent from my HTC Vision using XDA App
sundar2012 said:
awesome! thank you!
Don't suppose you would know how to get the CM update to not install/auto delete after installation apks like ADWLauncher and wifi calling?
Click to expand...
Click to collapse
Just delete them from the cmupdate.zip before flashing. Cwm recovery doesn't require sig so u don't have to worry about resigning it.
OP: nice find, I'm sure ill use it at some point.
This is driving me crazy because I know I have used this command before but i cannot get it to work now... What is the deal?
Code:
$ mount -o remount,rw /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Rooted using gfree on this phone. On my previous phone I used wpthis and did not have a problem. Anyone know what I need to do to mount rw?
cparekh said:
Thanks! This is great; now I can easily keep my Email.apk that doesn't require me to enter a alphanumeric password every time I want to use the phone.
Click to expand...
Click to collapse
I need that apk
Sent from my HTC Vision using XDA App
Used this method to when going from stock to CM 6.1.1 and could not get it to work. I had to push/install manually from ADB.
Anyone had any luck? I did what the OP said then flashed. Was I supposed to do anything after flashing wiping and then flashing (CM & gapps)?
rraxda said:
This is driving me crazy because I know I have used this command before but i cannot get it to work now... What is the deal?
Code:
$ mount -o remount,rw /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Rooted using gfree on this phone. On my previous phone I used wpthis and did not have a problem. Anyone know what I need to do to mount rw?
Click to expand...
Click to collapse
Make sure you have root in the shell by typing su.
cparekh said:
Thanks! This is great; now I can easily keep my Email.apk that doesn't require me to enter a alphanumeric password every time I want to use the phone.
Click to expand...
Click to collapse
IConrad01 said:
@cparekh -- what e-mail app is that? Or did you just use the pre-OTA's Email.apk app?
Click to expand...
Click to collapse
chubb16 said:
I need that apk
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
I am also interested in that apk
How can I backup progress on Angry Birds? Drives me nuts starting back over when I reflash CM
Titanium backup. You can use it to restore the app and the data. Usually i just restore the data to a fresh install.
Related
I've recently rooted my Desire Z and flashed Virtuous G-lite on it. One thing I really miss is an FM Radio app like the one of HTC Sense. I'm really searching for an app that receives FM, and not streams it over the internet.
I've searched the market but I haven't found anything, XDA forums had lots of hits but nothing that resolved my issue.Then I got a suggestion someone might be able to make an APK out of the Sense FM Radio.
So basically my question: Is there an app which alows me to receive FM Radio in the market? Or could anyone please wrap up an .apk from stock HTC Sense so I could try that out?
take a look at Spirit FM Radio
here is the fm.apk from cyanogen. I assume it works on other aosp roms, but I've been wrong (many a time) before.
mprost said:
take a look at Spirit FM Radio
Click to expand...
Click to collapse
Awesome, I like this radio more the CM's.
Sent from my T-Mobile G2 using XDA Premium App
pmcqueen said:
here is the fm.apk from cyanogen. I assume it works on other aosp roms, but I've been wrong (many a time) before.
Click to expand...
Click to collapse
Thanks for posting! Installing works fine, but the app FC's on launch, even after reboot, might need some work before it works on G-lite
mprost said:
take a look at Spirit FM Radio
Click to expand...
Click to collapse
Thanks for the heads up, app installs and launches, but after selecting an FM frequency there is no sound or any sign of receving anything.
Puffballofdoom said:
Thanks for posting! Installing works fine, but the app FC's on launch, even after reboot, might need some work before it works on G-lite
Thanks for the heads up, app installs and launches, but after selecting an FM frequency there is no sound or any sign of receving anything.
Click to expand...
Click to collapse
poo. make sure permissions are correct.
I don't ever use the FM radio so I'm not really familiar with how it works or if it relies on files outside of the apk to work. I do know that it requires bluetooth & headphones (headphones are used as antenna).
let me do some digging and I'll post back if I find anything.
I haven't got Root Explorer, but ROM Manager had a button Fix Permissions that should fix it too. After that I rebooted (ROM Manager suggested that), I enabled bluetooth, plugged in my headphones and still get instant FC when launching the app.
I will get back to it tomorrow, thanks for helping!
Puffballofdoom said:
I haven't got Root Explorer, but ROM Manager had a button Fix Permissions that should fix it too. After that I rebooted (ROM Manager suggested that), I enabled bluetooth, plugged in my headphones and still get instant FC when launching the app.
I will get back to it tomorrow, thanks for helping!
Click to expand...
Click to collapse
yes, rom mgr fix permissions works as well. I just hate using it because most of the time I only need to fix permissions for one or two apps at a time, and in that case it's easier to just know the chmod command (see below).
how did you "install" the app? did you place it on your sdcard and install it that way? or did you push it to /system/app (or /data/app)?
here's what I would do with it (I will test with g-lite when I get home tonight and let you know if it worked for me):
I would take the FM.apk attached and place it on my sdcard, then run the following commands from command prompt (you can do this from terminal emulator as well, just skip "adb shell"):
adb shell
su
mount -o rw,remount /system/app
mv /sdcard/FM.apk /system/app/
chmod 644 /system/app/FM.apk
reboot
Click to expand...
Click to collapse
in your case, my first step would be to find wherever FM.apk put itself (probably /data/app depending on what you did to install it), delete it, and start from scratch.
Why don't you just use tune in radio? It gets a ridiculous amount of stations and doesn't need headphones for an antenna. Try it!
Sent from my HTC Vision using XDA App
Tune In streams from internet, since I have a 1GB/month datalimit I really need FM to keep my data usage under 1GB/month.
Pmcqueen: I will try that first thing in the morning!
Sent from my T-Mobile G2 using XDA App
pmcqueen said:
yes, rom mgr fix permissions works as well. I just hate using it because most of the time I only need to fix permissions for one or two apps at a time, and in that case it's easier to just know the chmod command (see below).
how did you "install" the app? did you place it on your sdcard and install it that way? or did you push it to /system/app (or /data/app)?
here's what I would do with it (I will test with g-lite when I get home tonight and let you know if it worked for me):
I would take the FM.apk attached and place it on my sdcard, then run the following commands from command prompt (you can do this from terminal emulator as well, just skip "adb shell"):
in your case, my first step would be to find wherever FM.apk put itself (probably /data/app depending on what you did to install it), delete it, and start from scratch.
Click to expand...
Click to collapse
If I try mount -o rw,remount /system/app I just get feedback Usage: mount [-r] [-w] [-o] [-t] device directory. As far as I can tell the comma shouldn't be in the command, but what the command should be then I don't know
(My terminal has Superuser rights)
Puffballofdoom said:
If I try mount -o rw,remount /system/app I just get feedback Usage: mount [-r] [-w] [-o] [-t] device directory. As far as I can tell the comma shouldn't be in the command, but what the command should be then I don't know
(My terminal has Superuser rights)
Click to expand...
Click to collapse
try just
mount -o rw,remount /system
(no /app, but since it is a subdirectory it will inherit the r/w access)
Still the same message, I know for sure the terminal has SU because the $ changes to # after I type 'SU'.
Thanks for helping once again
Puffballofdoom said:
Still the same message, I know for sure the terminal has SU because the $ changes to # after I type 'SU'.
Thanks for helping once again
Click to expand...
Click to collapse
well darn it.
mount -o remount,rw /dev/block/mtdblock3 /system
^^ should get system mounted as read/write.
if not, do you have root explorer? we can do it that way as well, it's just faster to use terminal emulator/adb if it's not being tempremental.
So back at home once again, I tried the same commands from CMD and I'm getting the same message. I really don't know what's going on, it seems like the command isn't correct because it returns the possible options. Google hasn't come up with any suggestions too..
EDIT: Lol you posted at the time I was making this post, I will try what you said. I don't have root explorer, yet, let's see if your suggestion works, else I will need to find myself a copy of that root explorer
# su
su
# mount -o remount,rw /dev/block/mtdblock3 /system
mount -o remount,rw /dev/block/mtdblock3 /system
# mv /sdcard/FM.apk /system/app/
mv /sdcard/FM.apk /system/app/
failed on '/sdcard/FM.apk' - Cross-device link
#
Seems like your suggestion worked, but then moving the FM.apk failed. Any hints on that? Google tells me something about unmounted devices, but I can't find any solutions..
try just copying it instead. I saw this come up once before and I know a [very lengthy] workaround, but since it doesn't hurt to have a backup on your sdcard in the first place, might as well just copy...
just replace "mv" in the command with "cp"
let me know if that works or not.
edit: also, try adding busybox to the beginning of your command... ie:
busybox cp /sdcard/FM.apk /system/app
or
busybox mv /sdcard/FM.apk /system/app
Thanks, the busybox command did the trick. All commands execute perfectly now, but the FM radio still ain't working. Instant FC on launch (Bluetooth turned on and headset plugged in)
i also flashed virtous g-lite, but psx4droid can not load game with this rom. so i have to back to cm now. do you use psx4droid? how about its performance? pls let me kown.thanks.
Well I got Root Explorer, it looks usefull and I have used it with pleasure already. But moving/copying the FM.apk, it still doesn't work.
Anyone any thoughts?
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
Hey, just in case anyone else shelled out the money for SE's new Android release, Chaos Rings and couldn't play due to being rooted...
All you need to do to be able to play is rename your SuperSU.apk/superuser.apk in the /system/app folder (I just added, ".bak" to the filename) and the force close will end. Of course, you will probably want to rename the apk back to normal once finished
EDIT:
Cooldoud has a script on post #5 which, with Script Manager, should offer a widgetable solution to quickly renaming the superuser/supersu apk
rmikulus said:
Hey, just in case anyone else shelled out the money for SE's new Android release, Chaos Rings and couldn't play due to being rooted...
All you need to do to be able to play is rename your SuperSU.apk/superuser.apk in the /system/app folder (I just added, ".bak" to the filename) and the force close will end. Of course, you will probably want to rename the apk back to normal once finished
Click to expand...
Click to collapse
Sounds like a job for a bash script and Anycut. Would hate to have to do that manually all of the time...
garwynn said:
Sounds like a job for a bash script and Anycut. Would hate to have to do that manually all of the time...
Click to expand...
Click to collapse
OOH how difficult is it to do? Would be nice to automate
rmikulus said:
OOH how difficult is it to do? Would be nice to automate
Click to expand...
Click to collapse
Renaming is easy - busybox mv <source> <dest>
It's calling the app that I'm not certain about.
Yep found that out too... Really can't figure out why they went through the hassle of implementing such a lame system... Anyway, I wrote the below script for my gnote, it will toggle supersu so you can use the same widget to enable and disable supers.
After that install script manager, and set the script to be executed as root. You can then just create a widget to easily access the script
Code:
mount -o remount,rw /system
if [ $? -ne 0 ]; then
echo "Failed to remount /system as rw"
exit
fi
if [ -f "/system/app/Superuser.apk" ]; then
echo "Disabling Superuser App..."
mv /system/app/Superuser.apk /system/app/Superuser.bak
mount -o remount,ro /system
echo "All Done"
else
echo "Enabling Superuser App..."
mv /system/app/Superuser.bak /system/app/Superuser.apk
mount -o remount,ro /system
echo "All Done"
fi
I tried making it into a .sh and running it on script manager but it didnt work. kept saying line errors.
Metalshadowx2 said:
I tried making it into a .sh and running it on script manager but it didnt work. kept saying line errors.
Click to expand...
Click to collapse
You must make sure you convert your newline characters to Unix format. Wondows-style newline will cause the error you're getting (well if we're talking about the same error )
You can use notepad++ or Google dos2unix for a command line tool.
Sent from my GT-N7000 using xda app-developers app
Shouldn't this be in the apps section?
Sent from my SPH-D710 using xda premium
Probably yes, might also want to take it out of the Epic 4G section and move it to general Android as this is going to affect all devices
That's what I was just thinking...
Sent from my SPH-D710 using xda premium
cooldoud said:
Yep found that out too... Really can't figure out why they went through the hassle of implementing such a lame system... Anyway, I wrote the below script for my gnote, it will toggle supersu so you can use the same widget to enable and disable supers.
After that install script manager, and set the script to be executed as root. You can then just create a widget to easily access the script
Code:
mount -o remount,rw /system
if [ $? -ne 0 ]; then
echo "Failed to remount /system as rw"
exit
fi
if [ -f "/system/app/Superuser.apk" ]; then
echo "Disabling Superuser App..."
mv /system/app/Superuser.apk /system/app/Superuser.bak
mount -o remount,ro /system
echo "All Done"
else
echo "Enabling Superuser App..."
mv /system/app/Superuser.bak /system/app/Superuser.apk
mount -o remount,ro /system
echo "All Done"
fi
Click to expand...
Click to collapse
Anyway, big ups to cooldaud, your script works great for me! Had to change "Superuser" to "SuperSU" but everything is great! SMWidget ftw as well
Well so ironic SE would punish rooted android users and not GAF on ffxi hackers still -.- Meh I only speed hack moderately anyway...have you tried traveling otherwise? Soooo slow >.<
Sent from my SPH-D710 using XDA
Hi, tried this script on galaxy note 10.1, all went well and tablet acts like non rooted, but still supersu app in the app drawer and the game crashes as usually
cooldoud said:
You must make sure you convert your newline characters to Unix format. Wondows-style newline will cause the error you're getting (well if we're talking about the same error )
You can use notepad++ or Google dos2unix for a command line tool.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
ok i did and now i get this error
Looks like you're not using the busybox binaries. Maybe try replacing "mount" by "busybox mount"? Problem is I don't know what shell you'd be using so that might still not be working. Are you using the international Note? What ROM?
Also double check whether you're using SuperSU.apk or Superuser.apk as your root configuration tool.
I have no idea how all these scripts work, so I just tried to change the name of my superuser.apk, but for the life of me I can't figure out how to do that. My phone insists that I have insufficient privileges to rename it...
It seems that they finally added "*This game cannot be played on rooted devices." to the app description, it was not there yesterday
Well, I went and researched scripts. Got this script to work. (Had to add "busybox" before "mount")
Checked that the app does get renamed to .bak, and yet I still get a force close when i press start. I guess I'll just have wait for SE's patch.
It's important to check that the application is not appearing in your app drawer anymore (if your launcher can detect the app, so can SE... ) . Go there and check, if the app is still appearing it means it is still accessible (not sure whether you then need a reboot for it to disappear or something?), if it's not there... it means SE is also checking some other stuff to determine whether you're rooted, but I have no idea what that would be.
Ah yes, that's it. It still shows in my app drawer. Reboot didn't help. Trying searching the issue, came up with nothing. I guess I'm not meant to play this game just yet lol. Thank for trying to help!
Hello everybody,
i noticed an issue this morning with google plus.
As i think you know, latitude is going to disappear and i activated the location share on google plus.
But when i go into local, i can see all my friends sharing their positions, but the map doesn't show... as a matter of fact, i see icons on a empty display.
I tried to reboot, to clear cache and dalvik, also to remove and re-install google plus app, but nothing changed... have you some idea? what kind of problem is this?
Thanks,
Claudio
Same problem here on my Nexus 4 with CM 10.1. Aso reboot, reinstall, etc. does not help.
Maybe somebody else knows how to resolve this issue.
Same here on my Nexus 4. CM 10.1.1.
This issue doesn't seem to be reported anywhere else. Hopefully we can get to the bottom of this.
Yeah, it's true.
I tried to google the problem, but i can't find any report
I will add this is also an issue on my nexus 7 with cm 10.1.1.
Sent from my Nexus 7 using XDA Premium HD app
Yes, confirming this on N4 with CM 10.1.1.
Weird
Solution, it seems.
A potential solution:
MAKE SURE YOU ARE COMFORTABLE WITH YOUR FILE EXPLORER
Claude Robinson on G+:
"Google plus needs to be a system app in order for locations to work. There is an adb method but I don't know how to do that so I did it manually with root explorer.
First you need to go to /data and move com.google.apps.plus-1.apk to /system/app then you have to go to /data/app-lib/com.google.apps.plus-1 move all the files out of that folder into /system/lib reboot and you're done. You should now have the locations feature with maps working. While you are moving Google plus it will force close on you. Just hit OK until you are done and can reboot."
If you have any issues try clicking on the .apk to install it while it is in system/app. I cleared my data, but I don't know if that is necessary. My maps are working again.
sjoshua270 said:
This should fix the issue, if I am not mistaken.
Click to expand...
Click to collapse
this, what?
djsnake81 said:
this, what?
Click to expand...
Click to collapse
Sorry, forgot the text there.
Thank you sjoshua270, your fix worked for me!
This is what I did:
Code:
[email protected] ~ $ adb shell
[email protected]:/ $ su
[email protected]:/ # mount -o rw,remount /system
[email protected]:/ # cp /data/app/com.google.android.apps.plus-2.apk /system/app/
[email protected]:/ # cp /data/app-lib/com.google.android.apps.plus-2/* /system/lib/
[email protected]:/ # rm /data/app/com.google.android.apps.plus-2.apk
[email protected]:/ # rm -R /data/app-lib/com.google.android.apps.plus-2
Mount system as read-write (not sure if needed)
Copy apk from /data/app to /system/app
Copy libs from /data/app-lib/.. to /system/lib/
Remove original APK
Remove original libs
Reboot phone
sjoshua270 said:
A potential solution:
MAKE SURE YOU ARE COMFORTABLE WITH YOUR FILE EXPLORER
Claude Robinson on G+:
"Google plus needs to be a system app in order for locations to work. There is an adb method but I don't know how to do that so I did it manually with root explorer.
First you need to go to /data and move com.google.apps.plus-1.apk to /system/app then you have to go to /data/app-lib/com.google.apps.plus-1 move all the files out of that folder into /system/lib reboot and you're done. You should now have the locations feature with maps working. While you are moving Google plus it will force close on you. Just hit OK until you are done and can reboot."
If you have any issues try clicking on the .apk to install it while it is in system/app. I cleared my data, but I don't know if that is necessary. My maps are working again.
Click to expand...
Click to collapse
Thanks sjoshua, this worked great to me too!!!:good:
I moved the files as explained but find that now G+ is not installed. When go to run the APK from the /system/app/ folder to install it I get a "Parse Error" and can't install the app.
Can anyone help? This is the first time I've tried moving an app to the system folder.
from http://productforums.google.com/forum/#!msg/google-plus-discuss/PC4OKKAdjPM/6_FD10neqL0J
Solution found!!!
https://productforums.google.com/d/msg/google-plus-discuss/a_BJvcTJvtE/WAXOWtU_TckJ
https://plus.google.com/109052420587654093130/posts/Rzg2aL4wpi5
Note that if you are a TitaniumBackup user, the "convert to system app" does not work for this. You must follow the steps outlined in the G+ post.
Click to expand...
Click to collapse
google plus, missing maps
the new google plus has the friends locations . but when i go to locate a friend it shows the name of friend but no map. just this bunch of little squares..
how do i make the map show up. ?? is there a fix for that?
im on CM 10.1
never mind guys i found this gapps that fix the issue.
Steve Jones is the man to thank.
http://goo.im/devs/trevd/gapps/gapps-jb-20130615-signed.zip
Lw00d said:
never mind guys i found this gapps that fix the issue.
Steve Jones is the man to thank.
http://goo.im/devs/trevd/gapps/gapps-jb-20130615-signed.zip
Click to expand...
Click to collapse
Found it through G+, actually, but thanks for dropping this here!
Reported thread for merging with http://forum.xda-developers.com/showthread.php?t=2359379 (older thread), as I believe its the same issue.
I realized that I have to move the app / reinstall it from system folder after each restart, or it keeps force closing on me :\
Is there any other, more reasonable workaround yet?
Abondhal said:
I realized that I have to move the app / reinstall it from system folder after each restart, or it keeps force closing on me :\
Is there any other, more reasonable workaround yet?
Click to expand...
Click to collapse
New gapps package
http://forum.xda-developers.com/showthread.php?t=2369403
Lw00d said:
never mind guys i found this gapps that fix the issue.
Steve Jones is the man to thank.
http://goo.im/devs/trevd/gapps/gapps-jb-20130615-signed.zip
Click to expand...
Click to collapse
Thanks, but this package also doesn't seem to include G+ as system app. So it's not force closing, but I'm back to no map tiles :-\
Sent from my Nexus 4 using xda app-developers app
Worked for me, but my apk had a "1" not "2"
Code:
[email protected] ~ $ adb shell
[email protected]:/ $ su
[email protected]:/ # mount -o rw,remount /system
[email protected]:/ # cp /data/app/com.google.android.apps.plus-1.apk /system/app/
[email protected]roid:/ # cp /data/app-lib/com.google.android.apps.plus-1/* /system/lib/
[email protected]:/ # rm /data/app/com.google.android.apps.plus-1.apk
[email protected]:/ # rm -R /data/app-lib/com.google.android.apps.plus-1
Abondhal said:
Thank you sjoshua270, your fix worked for me!
This is what I did:
Code:
[email protected] ~ $ adb shell
[email protected]:/ $ su
[email protected]:/ # mount -o rw,remount /system
[email protected]:/ # cp /data/app/com.google.android.apps.plus-2.apk /system/app/
[email protected]:/ # cp /data/app-lib/com.google.android.apps.plus-2/* /system/lib/
[email protected]:/ # rm /data/app/com.google.android.apps.plus-2.apk
[email protected]:/ # rm -R /data/app-lib/com.google.android.apps.plus-2
Mount system as read-write (not sure if needed)
Copy apk from /data/app to /system/app
Copy libs from /data/app-lib/.. to /system/lib/
Remove original APK
Remove original libs
Reboot phone
Click to expand...
Click to collapse
So i'm trying to create a profile in tasker to enable/disable airplane whenever i'm connected to Wifi and it seems SecureSettings isn't allowing root actions even though it has root privileges. Anyone know an app that works with tasker that can allow me to enable/disable airplane mode?
Thanks!
metpage said:
So i'm trying to create a profile in tasker to enable/disable airplane whenever i'm connected to Wifi and it seems SecureSettings isn't allowing root actions even though it has root privileges. Anyone know an app that works with tasker that can allow me to enable/disable airplane mode?
Thanks!
Click to expand...
Click to collapse
Is there any particular reason you are using systemless root?
Sent from my Nexus 5X using Tapatalk
Mainly for Android Pay to work but I'm not married to systemless root if system root makes this work. However I may have found a workaround using Locale instead.
Sent from my Nexus 5X using Tapatalk
In either a terminal on your phone, or via adb shell from the computer, enter these commands:
Code:
mount -o remount,rw /system
touch /sbin/su /system/bin/su /system/xbin/su
mount -o remount,ro /system
I can't remember if you need to reboot or not, but might as well, just in case. Afterward, run your task and allow Secure Settings root access.
After doing this, Tasker and Secure Settings works for me. If this doesn't fix your problem, I don't know.
Thanks I'll give this a shot if Locale doesn't work
Sent from my Nexus 5X using Tapatalk
lightningdude said:
In either a terminal on your phone, or via adb shell from the computer, enter these commands:
Code:
mount -o remount,rw /system
touch /sbin/su /system/bin/su /system/xbin/su
mount -o remount,ro /system
I can't remember if you need to reboot or not, but might as well, just in case. Afterward, run your task and allow Secure Settings root access.
After doing this, Tasker and Secure Settings works for me. If this doesn't fix your problem, I don't know.
Click to expand...
Click to collapse
I have the same problem, running CF-Autoroot on my S7 edge. I would like to try your trick but am not sure how to exactly . Could you please explain a little bit more in detail how this is done?
EDIT: nevermind, i solved it my self using THIS method.
Thanks in advance.
Works for Secure settings, but it's broken Titanium backup
When I try to implement this in adb I get the following:
mount: '/dev/block/platform/soc.0/f9824900.sdhci/by-name/system'->'/system': Device or resource busy
Can anyone help? Would greatly appreciate it. Thanks!
facted said:
When I try to implement this in adb I get the following:
mount: '/dev/block/platform/soc.0/f9824900.sdhci/by-name/system'->'/system': Device or resource busy
Can anyone help? Would greatly appreciate it. Thanks!
Click to expand...
Click to collapse
Try using this command instead:
mount -o rw,remount /system
It worked for me
PiousInquisitor said:
Is there any particular reason you are using systemless root?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
is there system root for 7.0 or is this thread about 6.0.1?
niklus101 said:
is there system root for 7.0 or is this thread about 6.0.1?
Click to expand...
Click to collapse
There are unofficial versions in in the super su section here.
LSI said:
Works for Secure settings, but it's broken Titanium backup
Click to expand...
Click to collapse
Yeh, unfortunately, it does, same with AdAway.
Does it have to do with Android N or is it about the fact that touch /sbun/su fails due to sbin being read only?
If someone knows a solution, that would be great.
LSI said:
Works for Secure settings, but it's broken Titanium backup
Click to expand...
Click to collapse
I have the same problem with this too. It would be great to have a solution, or at least knowing how to reverse it would be great.
lightningdude said:
In either a terminal on your phone, or via adb shell from the computer, enter these commands:
Code:
mount -o remount,rw /system
touch /sbin/su /system/bin/su /system/xbin/su
mount -o remount,ro /system
I can't remember if you need to reboot or not, but might as well, just in case. Afterward, run your task and allow Secure Settings root access.
After doing this, Tasker and Secure Settings works for me. If this doesn't fix your problem, I don't know.
Click to expand...
Click to collapse
Do you hit enter at each line?
I'm doing this exact thing with Tasker and Magisk. I just had to add a quick edit to my build.prop, and then Tasker could recognize root with Magisk, and it worked fine.
Fit some reason I'm getting this error when dropping the commands
That's because it's mount -o not -0.
I just got secure settings and tried these commands in terminal. However they don't work. I get device or resource busy.
I'm on PureNexus 7.1.1 root via supersu on my Nexus 5x IF that matters in any way.
Edit: never mind. Solved it by replacing 0 with o. *Facepalm*
I've encountered the same problem in Android 7.1.2 and the above solution didn't work out for me. Secure Settings system+ is unavailable.
Any other solutions?
The first command
mount -o remount,rw /system
gave me the following result:
mount: '/dev/block/platform/msm_sdcc.1/by-name/system' not user mountable in fstab
1|jfltexx:/ $
It seems like an error.
akran said:
I've encountered the same problem in Android 7.1.2 and the above solution didn't work out for me. Secure Settings system+ is unavailable.
Any other solutions?
The first command
mount -o remount,rw /system
gave me the following result:
mount: '/dev/block/platform/msm_sdcc.1/by-name/system' not user mountable in fstab
1|jfltexx:/ $
It seems like an error.
Click to expand...
Click to collapse
Try this:
Code:
mount -o rw,remount /system
touch /sbin/su /system/bin/su /system/xbin/su
mount -o ro,remount /system
I'll share how I fixed this problem, which might be a LOT easier for some people.
Install a file manager that has root access (ie Root Explorer).
Navigate to /system/bin
Click whatever button to mount /system as rw.
Create a directory (or file) and call it su
Reboot phone
Open Secure settings and enable root.
At this point (and with above solutions, Android Pay is broken. If you want it back.
Open file manager again.
navigate to /system/bin
mount rw
delete the su folder (or file) you created earlier.
reboot.
Secure Settings only checks for su file the first time. Once it's been granted access, it no longer looks for su, it just tells the system it needs root access. So it will work the way its supposed to, even though it no longer can find the su file in expected location.
Also, for those that don't know, "touch" creates a file. So if you want to pass SafetyNet still, go back and delete the 3 files created from the touch command. And note that you only need to do 1 of them, not all 3, for Secure Settings to work.