Disable Auto Update to Android11? - OnePlus Nord N10 5G Questions & Answers

I've had a few issues with Android 11. It actually temporarily bricked my device. There were certain root features I use that weren't working (mock location and such)... I used MSM to get back to 10, but now my device just auto updated to 11 even though I had auto updates disabled in the settings.
How do I completely block updates? I don't want 11 on this thing

KaptinBoxxi said:
I've had a few issues with Android 11. It actually temporarily bricked my device. There were certain root features I use that weren't working (mock location and such)... I used MSM to get back to 10, but now my device just auto updated to 11 even though I had auto updates disabled in the settings.
How do I completely block updates? I don't want 11 on this thing
Click to expand...
Click to collapse
I am in the same boat. Auto updated without any interaction from me, despite also freezing all system update related apps via debloater.
I am not opposed to updates, but I am opposed to FORCED updates that silently install without my permission or intervention.
I read somewhere that the updates are coming through Google Play SVCS. I am currently MSM'ing my phone back to 10 for the 5th day in a row and plan on immediately revoking all permissions and backround usage for Play SVCS - however, I am guessing this will severely limit the device.
Notes: Also unchecked Auto Updates in Dev options.
Anyone have any ideas to prevent and block these forced shenanigans?

Remove system updater apk from the system. Simple. Freezing alone doesn't work.

Mohamedkam000 said:
Remove system updater apk from the system. Simple. Freezing alone doesn't work.
Click to expand...
Click to collapse
Last time I removed any system priv-app apk, my device bricked lol and I think it was the updater.
I'll give that a shot. Right now, everything is working that wasn't before when I was 11, but If I go back, i'll do that

How do you have RW to the system? Every time I try I get errors via adb

asuhoops8628 said:
How do you have RW to the system? Every time I try I get errors via adb
Click to expand...
Click to collapse
Use a Root System App Uninstaller app. That should do it better than an adb uninstall

KaptinBoxxi said:
Use a Root System App Uninstaller app. That should do it better than an adb uninstall
Click to expand...
Click to collapse
It'll cause errors, too. Since the file system change in 10, and 11, I the System App Uninstaller is not compatible with R, it'll not work.
Use Root Explorer, I use it to manually erase what is not necessary. At least it's guaranteed.

so, it appears blocking redirector.gvt1.com in pihole and adaway prevents play svcs from resolving the DL links for the update.
All other solutions suggested here have not worked for me. I will update tomorrow morning if I am still on android 10 (my phone has been updating while I sleep from 12-3am every night).

Shoot, I too had auto update disabled, and my phone updated last night.
I lost root AND SafetyNet!

adb shell pm disable-user --user 0 com.oneplus.opbackup
I believe com.oneplus.opbackup is the package name for system updater apk.
and above command will disable, aka freeze it.
After that "system update" in settings->system will be grayed out.
This seems to work on many other 1+ phones per various xda/reddit posts,
so I hope it would be good for N10.

This event has led an almost two-week-now jihad against forced updates for me. I've definitely killed it (the auto-update) but took out GS as well. Can't confirm exactly which it is, but I am happy to show my work:
First, get NetGuard: https://f-droid.org/en/packages/eu.faircode.netguard/ NO ROOT REQUIRED and you can filter apps that phone home.
If you are comfortable re-flashing, some trial and error will get it. This is my list (assumes you know how to do ADB shell and have root) (you could also delete rather than move to SDCard, but I had some I killed that bricked it and wanted to revert w/o reflash):
Bash:
su
mount -o rw,remount /
mount -o rw,remount /product
mkdir /storage/emulated/0/bye
mv /product/app/Account /storage/emulated/0/bye/
mv /product/app/CalendarGoogle /storage/emulated/0/bye/
mv /product/app/Chrome /storage/emulated/0/bye/
mv /product/app/Drive /storage/emulated/0/bye/
mv /product/app/Duo /storage/emulated/0/bye/
mv /product/app/DynamicDDSService /storage/emulated/0/bye/
mv /product/app/Gmail2 /storage/emulated/0/bye/
mv /product/app/GoogleContacts /storage/emulated/0/bye/
mv /product/app/GoogleContactsSyncAdapter /storage/emulated/0/bye/
mv /product/app/GoogleLocationHistory /storage/emulated/0/bye/
mv /product/app/GooglePay /storage/emulated/0/bye/
mv /product/app/GoogleTTS /storage/emulated/0/bye/
mv /product/app/Maps /storage/emulated/0/bye/
mv /product/app/Messages /storage/emulated/0/bye/
mv /product/app/Photos /storage/emulated/0/bye/
mv /product/app/Videos /storage/emulated/0/bye/
mv /product/app/YTMusic /storage/emulated/0/bye/
mv /product/app/YouTube /storage/emulated/0/bye/
mv /product/app/remoteSimLockAuthentication /storage/emulated/0/bye/
mv /product/app/remotesimlockservice /storage/emulated/0/bye/
mv /product/priv-app/AndroidAutoStub /storage/emulated/0/bye/
mv /product/priv-app/CarrierServices /storage/emulated/0/bye/
mv /product/priv-app/ConfigUpdater /storage/emulated/0/bye/
mv /product/priv-app/GoogleDialer /storage/emulated/0/bye/
mv /product/priv-app/GoogleFeedback /storage/emulated/0/bye/
mv /product/priv-app/GoogleOneTimeInitializer /storage/emulated/0/bye/
mv /product/priv-app/GooglePartnerSetup /storage/emulated/0/bye/
mv /product/priv-app/GoogleRestore /storage/emulated/0/bye/
mv /product/priv-app/HotwordEnrollmentOKGoogleHEXAGON /storage/emulated/0/bye/
mv /product/priv-app/HotwordEnrollmentXGoogleHEXAGON /storage/emulated/0/bye/
mv /product/priv-app/OPAppLocker /storage/emulated/0/bye/
mv /product/priv-app/SetupWizard /storage/emulated/0/bye/
mv /product/priv-app/Velvet /storage/emulated/0/bye/
mv /product/priv-app/Wellbeing /storage/emulated/0/bye/
mv /product/priv-app/OobConfig /storage/emulated/0/bye/
mv /product/priv-app/Turbo /storage/emulated/0/bye/
mv /product/priv-app/Phonesky /storage/emulated/0/bye/
mv /product/priv-app/GmsCore /storage/emulated/0/bye/
mv /system/app/BackupRestoreRemoteService /storage/emulated/0/bye/
mv /system/app/CompanionDeviceManager /storage/emulated/0/bye/
mv /system/app/OPLocalUpdate /storage/emulated/0/bye/
mv /system/app/GoogleAssistant /storage/emulated/0/bye/
mv /system/app/GooglePrintRecommendationService /storage/emulated/0/bye/
mv /system/app/NVBackupUI /storage/emulated/0/bye/
mv /system/app/OPAppUpgrader /storage/emulated/0/bye/
mv /system/app/OPOnlineConfig /storage/emulated/0/bye/
mv /system/app/OPPush /storage/emulated/0/bye/
mv /system/app/PlayAutoInstallConfig /storage/emulated/0/bye/
mv /system/app/TSDM /storage/emulated/0/bye/
mv /system/app/OPBreathMode /storage/emulated/0/bye/
mv /system/priv-app/DynamicSystemInstallationService /storage/emulated/0/bye/
mv /system/priv-app/OnePlusGallery /storage/emulated/0/bye/
mv /system/priv-app/OnePlusWizard /storage/emulated/0/bye/
mv /system/priv-app/AmazonMDIP /storage/emulated/0/bye/
mv /system/priv-app/TagGoogle /storage/emulated/0/bye/
mv /system/priv-app/OPDeviceManager /storage/emulated/0/bye/
mv /system/priv-app/OPDeviceManagerProvider /storage/emulated/0/bye/
mv /system/reserve/OPBackupRestore /storage/emulated/0/bye/
mv /system/reserve/OPForum /storage/emulated/0/bye/
mv /system/reserve/OPNote /storage/emulated/0/bye/
mv /system/reserve/OPSoundRecorder /storage/emulated/0/bye/
mv /system/reserve/OnePlusPods /storage/emulated/0/bye/
Now the reason this took so long is I have a bunch of (paid) apps that all link to GS and verify I bought it... so I need to find OSS replacements (F-droid et al) for a lot of them. Additionally, most of the custom roms come with AOSP apps for dialer, contacts, etc... the list above kills the OnePlus ones but does not replace them.
Hope the above helps someone!

@arda99 Definitely can confirm that having system updates greyed out does NOT prevent this upgrade! This is with the SIM out of the phone (but WiFi connected), so can't be a carrier push.
Google Services was giving me update nags, but they could be ignored (nothing forced successfully until the A11 reflash).

SomeRandomGuy said:
@arda99 Definitely can confirm that having system updates greyed out does NOT prevent this upgrade! This is with the SIM out of the phone (but WiFi connected), so can't be a carrier push.
Google Services was giving me update nags, but they could be ignored (nothing forced successfully until the A11 reflash).
Click to expand...
Click to collapse
You're right...my phone upgraded to 11 few days ago when on charger. Did another MSM back to 10 and this time I uninstalled the package instead of disable.

Frustrating, isn't it, @arda99 ? I turned it into a game. Wasted almost two weeks of calendar time, but i just sped up the inevitable... a nearly 100% FOSS fone now, free from forced upgrades for the moment. I'd still bet it is a GS thing.
Now I just need to figure out how carriers can push stuff (like how APNs get set automatically after plugging in a different SIM... what else can they set, modify, or disable?)

Got update notice again...Found another update service in Google Play Service. Need root to disable it.
Code:
adb shell
su
pm disable com.google.android.gms/com.google.android.gms.update.SystemUpdateActivity

But see, here's the thing that terrifies me. If you have a fully functional, logged in (to Google) running phone, you can go to the play store online, and push something to your phone. Think about that. Poof, a minute later, there is code on your phone without any confirmation needed.
So what is stopping OTHER stuff from coming down that way? The kind hearts and souls keeping integrity at our dear billionaire company ?
I'm loving that MicroG lets you un-register applications from getting messages. Still tweaking my install - some of the OnePlus stuff seems to be miles ahead of the f-droid options (like dialer... damn, does no one that writes dialer software ever get a spam call and have a blocklist? Ditto for messages... QKSMS is nice but blacklist blacklist blacklist.... sigh)... but I will get there.
Lets all be thankful for an actual OSS community, and that we still have options for sideloading unlike that OTHER phone ecosystem with no freedom at all...

arda99 said:
Got update notice again...Found another update service in Google Play Service. Need root to disable it.
Code:
adb shell
su
pm disable com.google.android.gms/com.google.android.gms.update.SystemUpdateActivity
Click to expand...
Click to collapse
My phone auto-updated itself to Android 11 at the beginning of August. Went through and disabled what I could right then and thought that was the end of it.
Today I saw another one of those white "Your system is out of date" prompts and sat right down to do some more digging.
Just disabled this service and the com.oneplus.opbackup you mentioned higher in the thread via ADB. Hopefully this time I got it all.

thanks everyone for the answers. I've disabled everything here and haven't had a popup in awhile
Although I might be switching to a OP7 Plus 5G GM1925 if I can get it rooted... everything I flash to it freezes it and bricks it. I gotta figure out why

Related

[SCRIPT] Remove Cell Standby Service (No Effect on Battery Life!)

WARNING: I've added this to my script and for some reason it has an adverse effect on the "n" button and Lock Screen if used BEFORE you complete the SetupWizard !!!
WARNING: Again BE WARNED if you do this mod before you finish the setup wizard you will loose the functionality of your "n" button and Lock Screen !!!
I have a feeling poster before me copied and pasted this from somewhere because notice how in his first sentence he says "Phone.apk and TelephonyProvider.apk" but then his script says "Mms.apk"....what happened to Phone.apk because there is no Mms.apk in the system folder on any Nook I have. So below is the corrected script and also this entire process in done in dos instead of in adb;
Code:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb shell mv /system/app/Phone.apk /system/app/Phone.OLD
adb shell mv /system/app/TelephonyProvider.apk /system/app/TelephonyProvider.OLD
adb reboot
There is no adverse effect from doing this & it's confirmed after while in NookTools there is no Cell Standy service running.
Download [REMOVAL]
Want to undo this process?
Code:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb shell mv /system/app/Phone.OLD /system/app/Phone.apk
adb shell mv /system/app/TelephonyProvider.OLD /system/app/TelephonyProvider.apk
adb reboot
Download [UNDO REMOVAL]
thanks, just got my NC yesterday, and already updated/rooted + done this hack
xmas_spirit said:
thanks, just got my NC yesterday, and already updated/rooted + done this hack
Click to expand...
Click to collapse
Run my script too from the other post?
xboxexpert said:
Run my script too from the other post?
Click to expand...
Click to collapse
No, I just manually entered commands in adb shell
xboxexpert said:
I have a feeling poster before me copied and pasted this from somewhere because notice how in his first sentence he says "Phone.apk and TelephonyProvider.apk" but then his script says "Mms.apk"....what happened to Phone.apk because there is no Mms.apk in the system folder
Click to expand...
Click to collapse
90% of the internet are sites posting info from other sites. Be glad he didn't slap on some ads.
I'm new here, but trying to learn.
Your code is:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb shell mv /system/app/Phone.apk /system/app/Phone.OLD
adb shell mv /system/app/TelephonyProvider.apk /system/app/TelephonyProvider.OLD
adb reboot
would it make sense to add:
adb shell mount -o remount,ro /dev/block/mmcblk0p5 /system
before the reboot? Or does that get done automatically upon reboot? I assume it is bad to leave it rw and not reset it to ro?
Thanks for this, I ran 'most' of your other script.
Auto-nooter, your script, adw launcher and it is coming along nicely. Still debating remapping the volume keys to back/menu...
DC_Rob said:
I'm new here, but trying to learn.
Your code is:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb shell mv /system/app/Phone.apk /system/app/Phone.OLD
adb shell mv /system/app/TelephonyProvider.apk /system/app/TelephonyProvider.OLD
adb reboot
would it make sense to add:
adb shell mount -o remount,ro /dev/block/mmcblk0p5 /system
before the reboot? Or does that get done automatically upon reboot? I assume it is bad to leave it rw and not reset it to ro?
Thanks for this, I ran 'most' of your other script.
Auto-nooter, your script, adw launcher and it is coming along nicely. Still debating remapping the volume keys to back/menu...
Click to expand...
Click to collapse
yes, the system partition goes back to RO after a reboot
Can this be done using terminal emulator
Sent from my PC36100 using XDA App
Ben74 said:
yes, the system partition goes back to RO after a reboot
Click to expand...
Click to collapse
Great, now I know. I write code for a living so, I try to be tidy....
Thanks
worked perfectly, thanks.......
midnightmaraude said:
Can this be done using terminal emulator
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Just use Root Explorer; rename those two files to anything else and reboot. Really, you could just remove them, renaming is just a precaution.
Thanks for this, makes the nook even better!
Mike
sent from my nookcolor using the xda app
Just to play devil's advocate, does anyone know if it's really improving battery life, rather than just no longer reporting cell standby under battery use details?
wvcachi said:
Just to play devil's advocate, does anyone know if it's really improving battery life, rather than just no longer reporting cell standby under battery use details?
Click to expand...
Click to collapse
I wondered that, but I also have no reason to run unused services so it can't hurt.
wvcachi said:
Just to play devil's advocate, does anyone know if it's really improving battery life, rather than just no longer reporting cell standby under battery use details?
Click to expand...
Click to collapse
I've been playing angry birds for 30 minutes and only lost 4% battery life. Seems to be awesome.
ummmmmm where is the script
ADB commands are only in OP lol
Therefore you need adb
No such file or directory?
I keep getting an error message stating the following:
"failed on '/system/app/phone.apk' - No such file or directory"
If I navigate to that file using Astro File Manager I can see the files, so I can't figure out what I'm missing here.
Salt72 said:
I keep getting an error message stating the following:
"failed on '/system/app/phone.apk' - No such file or directory"
If I navigate to that file using Astro File Manager I can see the files, so I can't figure out what I'm missing here.
Click to expand...
Click to collapse
Try capitalizing the file names.
Not to beat a dead horse, but this can easily be done in Root Explorer. All you're doing is renaming two files.
Not to be a cheapskate, but is there a free version of Root Explorer or a similar app that will do the same?
No
try Astro or Linda, thats free but ads supported

[GUIDE] Have Webtop over HDMI and want to OTA update?

Okay, we discovered that having the Webtop over HDMI breaks the OTA update.
So to update you're going to have to undo that mod, and possibly any others.
If you backed up your original files great, go restore them, clear the dalvik-cache and you're fine.
Otherwise, use the attached files and these steps to recover:
Credit: _unknown for the original posted instructions I'm using as a template
Please let me know if there are any adjustments that need to be made to the code, as I'm pulling this from memory and had stored the backups on my phone and was restoring from there.
Requirements:
Be rooted
Be able to work with adb
First, unpack the attached zip-file.
Go into the correct directory for your version.
Now run (in a terminal)
Code:
# I use /data/tmp as the storage location, you can also use /sdcard/
adb push DockService.apk /data/tmp
adb push PortalApp.apk /data/tmp
adb push DockService.odex /data/tmp
adb push PortalApp.odex /data/tmp
adb shell
# you are now in the phone shell
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
# you could mv these files to backups if you intend on doing the mod
# again after the update
rm /system/app/DockService.*
rm /system/app/PortalApp.*
rm /data/dalvik-cache/*DockService* /data/dalvik-cache/*PortalApp*
# move the files from /data/tmp to /system/app
mv /data/tmp/DockService.* /system/app/
mv /data/tmp/PortalApp.* /system/app/
reboot
NOTE: This zip will not in any way help you to obtain root! You must be rooted prior to attempting to apply this patch, or it will not work!
pksublime said:
Okay, we discovered that having the Webtop over HDMI breaks the OTA update.
So to update you're going to have to undo that mod, and possibly any others.
If you backed up your original files great, go restore them, clear the dalvik-cache and you're fine.
Otherwise, use the attached files and these steps to recover:
Credit: _unknown for the original posted instructions I'm using as a template
Please let me know if there are any adjustments that need to be made to the code, as I'm pulling this from memory and had stored the backups on my phone and was restoring from there.
Requirements:
Be rooted
Be able to work with adb
First, unpack the attached zip-file.
Go into the correct directory for your version.
Now run (in a terminal)
Code:
# I use /data/tmp as the storage location, you can also use /sdcard/
adb push DockService.apk /data/tmp
adb push PortalApp.apk /data/tmp
adb push DockService.odex /data/tmp
adb push PortalApp.odex /data/tmp
adb shell
# you are now in the phone shell
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
# you could mv these files to backups if you intend on doing the mod
# again after the update
rm /system/app/DockService.*
rm /system/app/PortalApp.*
rm /data/dalvik-cache/*DockService* /data/dalvik-cache/*PortalApp*
# move the files from /data/tmp to /system/app
mv /data/tmp/DockService.* /system/app/
mv /data/tmp/PortalApp.* /system/app/
reboot
NOTE: This zip will not in any way help you to obtain root! You must be rooted prior to attempting to apply this patch, or it will not work!
Click to expand...
Click to collapse
mv /data/tmp/PortalApp.* /system/app/
# mv /data/tmp/DockService.* /system/app/
mv /data/tmp/DockService.* /system/app/
failed on '/data/tmp/DockService.apk' - Cross-device lin
# mv /data/tmp/PortalApp.* /system/app/
mv /data/tmp/PortalApp.* /system/app/
failed on '/data/tmp/PortalApp.apk' - Cross-device link
Okay working on it...
try using cp instead of mv
Thank you. Will do this tonight
cp worked instead of mv
was able to update, thankyou.
lcpl said:
cp worked instead of mv
Click to expand...
Click to collapse
thanks, i updated the instructions
at least the important part was getting the files up for people, most can figure it out from there
Has anyone that has updated to the newer OTA version been able to re-hack the Webtop / HDMI output using the original method?
Thanks!
alohajeff said:
Has anyone that has updated to the newer OTA version been able to re-hack the Webtop / HDMI output using the original method?
Thanks!
Click to expand...
Click to collapse
You rave to re-root after the update, but yeah, it's the same thing.
Haven't got that far yet, I'm just starting.
Give me a bit and I'll tell you how it went.
Update 1:
Installed the update with out a hitch, save for a line of code
"rm /data/dalvik-cache/*DockService* /data/dalvik-cache/*PortalApp*"
I had to change to
"rm /data/dalvik-cache/*.*"
The dalvik chache is rebuilt at the next reboot, so there isn't much harm wiping the whole thing.
And Yeah, i had to change that the "mv" to"cp"
Update 2:
Rooted just fine using :/showthread.php?t=1217416
Update 3:
Followed : /showthread.php?t=1199443
But as of again, I changed
"rm /data/dalvik-cache/*DockService* /data/dalvik-cache/*PortalApp*"
to
"rm /data/dalvik-cache/*.*"
and
"mv" to"cp"
Works just as well as before. Even with 9/12's update
I had some trouble before, but It looks like I just had to re apply the hack one again. It's all good now. Dockless webtop on the latest OTA.
It's not working for me for the 10/12 update. Any ideas? Do the odex files have to be renamed to .bak?
Airwolf79 said:
It's not working for me for the 10/12 update. Any ideas? Do the odex files have to be renamed to .bak?
Click to expand...
Click to collapse
Yes.
Sent from my MB855 using Tapatalk
John Kotches said:
Yes.
Sent from my MB855 using Tapatalk
Click to expand...
Click to collapse
So what is the easiest way to go about this? Do I have to rename them before I push, or once they're installed?

[Tweak] Foliomod 1.4 Display Wake Up - How to FIX -

I've found this solution in a nopy's post in CM7 here http://forum.xda-developers.com/showpost.php?p=18818844&postcount=659
To fix the unwanted wakeup on latest build
Code:
adb remount
adb shell
# cd /system/usr/keylayout
# mv gpio-keys.kl ../keychars
# mv nvec_keyboard.kl ../keychars
# mv tegra-kbc.kl ../keychars
# mv usb_keyboard_102_en_us.kl ../keychars
# exit
adb reboot
Do this only if you understand what your doing.
Click to expand...
Click to collapse
But this work in foliomod too.
Battery consumption is about 1% at hour in standby mode, without any wakeup.
Only one issues: like CM7, you need to press two times the power button to wake up your device.
I hope help you.
Bye.
Nice, i'll try, but i've question.
I'll need to boot my Folio into fastbot mode? (3 press power & +) ?
and commands should equals "#" ?
You don't have to. Do that with booted tablet.
Sent from my IDEOS S7 Slim using XDA App

Vpndialogs.term error 3 {fix}

Okie doke so lets saying you are happily trying too root your tab executing this http://forum.xda-developers.com/showthread.php?t=1887447 script.
everything goes as planned until you reboot and try to start the terminal and nothing appears. One method is to inject a VpnFaker you have signed using Zipsigner2 if that doesn't work you can rollback using this code
adb shell
cd /data
mv system system3
mv system- system
mv app app3
mv app- app
If nothing works then here is a way I found to fix it. once you get to code TZ=0 under it will say rw-rw-rw which means the VpnFaker will disappear once you reboot.
type in /data/app/VpnFaker.apk it will say permission denied that means it is indeed there. so to fix it we type:
chmod 644 /data/app
this worked for me on ICS no revision when trying to root!! hope it does for you if you are on ICS with revision do
chmod 644 /data/app/VpnFaker.apk
otherwise you will have to reupdate because doing it the other way will cause you to lose adb.

[Q] Structuria for better structure of android folders. Easy to open !books !music

Hello! Sorry me English, I'm Russian.
I tired of android structure: A lot of .* folder, a lot of program's rabbish. It's bad for PC, but in phone with little screen it's much more worse.
So, I have an indea, how can we fix it.
The first move is mv all of folder like books, downloads etc to !books, !downloads!
Then, we need to mkdir books, downloads etc
The we should mount -o bind !books to books - we need to do it on a startup
Somebody say that you can just rename folder and sune some program, but it's veeery boring.
As for me, I can not realize that because I am noob and have some glitches with my computer, phone... So, can anybody make this?
My script did not work, i tried make it different, but it was nothing
#!/system/bin/sh
mkdir huu
busybox mv /mnt/sdcard/hu /mnt/sdcard/huui
mv /mnt/sdcard/Books /mnt/sdcard/!Books
mv /mnt/sdcard/Download /mnt/sdcard/!DownLoad
mv /mnt/sdcard/Music /mnt/sdcard/!Music
mv /mnt/sdcard/Movies /mnt/sdcard/!Movies
mv /mnt/sdcard/Pictures /sdcard/!Pictures
mv / mnt/sdcard/DCIM /mnt/sdcard/!DCIM
I tried cd /mnt/sdcard but it said me that folder's is not exist, even if I make it with y hands!
For mount folder I tried something like
#!/system/bin/sh
mount -o bind /mnt/sdcard/!Books /mnt/sdcard/Books
I hope that you will help me, and I beelive it helps to many people improve efficiency of android using.

Categories

Resources