Related
Im using the Root Explorer v2.10.2(which is the latest) to delete some unwanted system apks in system/apk folder, and im pretty sure i have already deleted those apks, but when i go into Settings->applications->manage applications, i still can find those deleted apks. Altho they are like 0 bite in memory, but still looks very annoying to me. Is there any way to get rid of those things in 'manage applications'? I have tried to search keywords in RootExplorer, and deleted the apk folders under data/data, and reboot my phone, and they are still there..
Also, if i click on any of those apks, "settings" will FC.
tzf123 said:
Im using the Root Explorer v2.10.2(which is the latest) to delete some unwanted system apks in system/apk folder, and im pretty sure i have already deleted those apks, but when i go into Settings->applications->manage applications, i still can find those deleted apks. Altho they are like 0 bite in memory, but still looks very annoying to me. Is there any way to get rid of those things in 'manage applications'? I have tried to search keywords in RootExplorer, and deleted the apk folders under data/data, and reboot my phone, and they are still there..
Also, if i click on any of those apks, "settings" will FC.
Click to expand...
Click to collapse
Did you try running fix_permissions?
Binary100100 said:
Did you try running fix_permissions?
Click to expand...
Click to collapse
hmm.. what is fix_permissions?
i searched on google and it says:
From a running ROM
To execute the fix_permissions script on your phone:
Open the "Terminal" app from the application drawer.
Type
su
fix_permissions
when i type fix_permissions in terminal, it indicates fix_permissions not found, i also tried fix_permissions.sh, still not found
tzf123 said:
hmm.. what is fix_permissions?
i searched on google and it says:
From a running ROM
To execute the fix_permissions script on your phone:
Open the "Terminal" app from the application drawer.
Type
su
fix_permissions
when i type fix_permissions in terminal, it indicates fix_permissions not found, i also tried fix_permissions.sh, still not found
Click to expand...
Click to collapse
what rom and recovery are you using?
Binary100100 said:
what rom and recovery are you using?
Click to expand...
Click to collapse
SMOKI 0.6.3, RA-hero-v1.6.2
it seems like the fix_permissions command can be used in CM ROMS..
tzf123 said:
SMOKI 0.6.3, RA-hero-v1.6.2
it seems like the fix_permissions command can be used in CM ROMS..
Click to expand...
Click to collapse
Try running fix_permissions from recovery.
its not working... those apks still stay in 'manage applications'.. altho recovery said its successful
Binary100100 said:
Try running fix_permissions from recovery.
Click to expand...
Click to collapse
LOL, problem solved, by editing the packages.xml under data/system, somehow the apk details are recorded in that file, so i just delete the corresponding codes and reboot my phone, walllllaaaaaaaaaa
AND, thanks a lot for your guide, LOL
tzf123 said:
LOL, problem solved, by editing the packages.xml under data/system, somehow the apk details are recorded in that file, so i just delete the corresponding codes and reboot my phone, walllllaaaaaaaaaa
AND, thanks a lot for your guide, LOL
Click to expand...
Click to collapse
Glad that you got it solved.
Also I hope that you don't mind by I edited your title because your problem wasn't specifically related to the Root Explorer app. This problem would occur if you had used any other means of removing the system app. By editing the title it'll make it easier for those that need assistance with a similar issue post their problems and find solutions. Adding [Solved] is effective to let them know that a resolution is available within the thread.
And it's not my guide, it's a reference for others that can't find the answer with the apparently evasive search feature.
Greetings,
Okay, so I endeavoured to root my phone last night and was successful. I ran into trouble when the clockwork recovery and superuser permissions kept getting removed each time I rebooted the phone. This morning, I tried to restore the superuser permissions by following the steps I found here on xda but after running the terminal script I rebooted my phone and when my phone wouldn't boot beyond the Google screen.
Now, I'm at the Google splash screen with no way to move forward. I'm a mac user and I don't really get the adb thing. Got adb to work with mac from a youtube video, but still not sure what commands to run.
I can't access clockwork recovery from the bootloader.
What I've done so far:
- wiped cache
- wiped/factory data reset
- retraced my steps by using terminal to setup superuser permission from this post (http://forum.xda-developers.com/showthread.php?t=927838)
What I think:
- maybe in all of my clicks I removed the ROM, so the phone doesn't have a ROM to work with.
This maybe a really infantile conclusion, but I know there's a solution (had a rooted G1 that I flashed all the time and thought I bricked once but was able to get it back to stock).
Eagerly waiting for a reply... no cell phone if this can't be fixed.
Tamaratee
__________________
Phone: Nexus
Rooted with problems
This post might help:
http://forum.xda-developers.com/showthread.php?p=9866675
It has the adb commands on how to replace the existing boot loader with cwm and all.
Hope it helps.
EDIT: If all else fails, you can try flashing a nandroid backup (2.3.3). This post would guide you:
http://forum.xda-developers.com/showthread.php?t=979851
Greetings Cygnum,
Thanks for the suggestion. I have a question: will these commands work on a Mac?
Thank you to AllGamer for suggesting that I post this question here and for the following suggestion:
AllGamer said:
please post the same question in QA or General, then we can all help you
PM is not the best place to ask for help.
The first thing to do is to download the full set of Android SDK 2.3+ for MAC
then we'll continue from there.
Click to expand...
Click to collapse
How do I proceed AllGamer? I downloaded the mac SDK from here (http://developer.android.com/sdk/index.html).
Follow steps 1-7 from here to get back Clockwork Recovery.
http://forum.xda-developers.com/showthread.php?t=878446
If your bootloader is already unlocked, you can skip those steps.
Do steps 8-9 to copy this file over to your USB drive.
http://devsforandroid.com/ip.board/index.php?/files/file/94-stock-deodexed-233-voodoo-rooted/
This rom is Master's Stock 2.3.3 ROM that is already rooted which should get you up and running.
Unmount, go back. Wipe system data, wipe cache. Go to advanced, Wipe Dalvik-cache.
Go back, choose to install zip from SD card. Locate Master's stock ROM. Flash that.
In the end, you'll have a stock deodexed rom that is rooted. Keep in mind that you will lose all your data, but that at least puts you back on track.
Also wanted to mention if you didn't already know, mac scripts are run with a "./" in front of them. So to use the adb command you would do something like, "./adb reboot bootloader" after you have changed your directory to the folder that contains the sdk files.
peeturr said:
Also wanted to mention if you didn't already know, mac scripts are run with a "./" in front of them. So to use the adb command you would do something like, "./adb reboot bootloader" after you have changed your directory to the folder that contains the sdk files.
Click to expand...
Click to collapse
I feel bad for being a stickler here, but this is only true if he has not added the location of the binaries to the PATH. ./ just specifies to start in the local directory rather than look to the PATH to search for the file, it's not a requirement for running a script.
krohnjw said:
I feel bad for being a stickler here, but this is only true if he has not added the location of the binaries to the PATH. ./ just specifies to start in the local directory rather than look to the PATH to search for the file, it's not a requirement for running a script.
Click to expand...
Click to collapse
Yeah my bad. Just whatever had worked for me. Pretty new to mac myself.
Sent from my Nexus S using XDA App
krohnjw said:
I feel bad for being a stickler here, but this is only true if he has not added the location of the binaries to the PATH. ./ just specifies to start in the local directory rather than look to the PATH to search for the file, it's not a requirement for running a script.
Click to expand...
Click to collapse
Doesn't ~/ do the same as well?
Sent from my MattedBlues CM7 Nexus S from the XDA Premium app.
kenvan19 said:
Doesn't ~/ do the same as well?
Sent from my MattedBlues CM7 Nexus S from the XDA Premium app.
Click to expand...
Click to collapse
No. ~/ specifies your home directory
Thanks Everyone
Thanks for all the suggestions and help I received. I PM'd KenVan and he provided me with the script and my Nexus S is up and running.
I just had this problem on the weekend I could not get past the lockscreen so I flashed cyanogen nightly and bam booted fine
Sent from my Nexus S using XDA App
Problem Solved Over the Weekend
Thanks for the help everyone. I posted this in a couple places, so I forgot to update this thread.
I fixed the problem with detailed steps from KenVan. Thanks again though to all of you for your suggestions.
ANNOUNCEMENT:
If you have a new Nook HD/HD+ and want to root and get the GAPPS running, you should follow the guide at the All-in-One thread instead. That said, I won't copy all the information here to there, so you should continue to read on.
Proof:
https://www.youtube.com/watch?v=MssQ25bnZnk
Okay this one is more interesting than the root I created. I don't think there will be a simple batch file for this one. I barely get this working and I'm going to try to write instruction for the people. I guess let me start off with the same disclaimer.
Disclaimer:
If something gone wrong, it's all your fault. I take ZERO responsibility for what happen to your device, your life, your wife/husband, your kids, your unborn child and etc. You get the idea.
Background:
I basically taking the installation process from the Kindle Fire HD and apply it it here. The original instruction which I "borrow" from is here. For the most part, the process is the same, but we have to be extra careful for writing into /system partition or we are toast.
What I found:
Well, since we didn't have "UNKNOWN SOURCE" option, we have to adapt and fix that first. You can thanks skyhawk21 for coming up with that idea. Since then, there have been other way to enable Unknown Source. LeapinLar have wrote an excellent here. And I have make it even simpler here. Also, I have found that trying to install Google Play store after some other stuff already installed is kinda pain and brought some error. So I would strongly start this fresh. I mean factory reset and apply root. If you don't know how to gain root on the Nook HD+, I wrote an excellent piece for it here.
Hugh big caution
I did all my stuff based off my root method. I also noticed that verygreen updated his root. While there are some similarlity in our methods, THERE ARE SOME DIFFERENCE ALSO. For example his root doesn't have a working superuser or he have busybox installed and symbolicly linked for all sub command. This mean the instruction I have may not work if you used his method to root.
Addendum 1: 11/19/[email protected]:50PM Pacific
I have been told that the first set of instruction is no longer necessary by leapinlar. This mean that if you only want the ability to install app via Google Play, you can do the first set of instruction and be done with it. But this means you won't be able to utilize the rest of Google's services. On the other hand, you can skip the first instruction and purely do 2nd instruction and get most of the stuff working. Well I say most because it doesn't include Google Maps and Chrome.
Addendum 2: 11/19/[email protected] Pacific
I have added Google Map below so you can download separately But Chrome Browser is like 20MB and over the filesize limit of the xda forum. Since most people don't use it, and there are many good alternative browser already, I won't bother. You can also look up both apk online if you want. they both should work on Nook. You don't have to make symbolic link on these two, but you can't have it on /system either. Either try install it via "adb install" command or open it using your favorite file browser. I forgot which method I use, probably the first.
Addendum 3: 11/30/[email protected]:25AM Pacific
I rewrite and hide unnecessary stuff and streamline the guide.
Addendum 4: 12/01/[email protected]:25PM Pacific
Adding gapps-ics-inst.sh.img which should be compatible for both my and verygreen root method.
Addendum 5: 12/02/[email protected] Pacific
Adding troubleshooting tips
Addendum 6: 12/04/[email protected]:45PM Pacific
Update with brand new easy to follow instruction.
Addendum 7: 12/07/[email protected] Pacific
The Google Map will no longer install as part of the script. I think Maps may not function properly if google framework weren't installed correctly first.
So, you will just have to install it manually after the Google Play updated.
EXTREMELY OUTDATED NOT FULLY WORKING Instruction is hidden since it's no longer necessary.
Instruction:
Optional, factory reset it. Seriously I cannot say this will work unless you start from scratch. If you already have rooted earlier, then install something like titanium backup and backup your porn(I mean data).
Gain root access. Follow this guide.
Follow my instruction here to enable "UNKNOWN SOURCE".
Upload 3 files to /data/su/ using "adb push" command
GoogleServicesFramework.apk - mediafire.com/?zaumfwhraxcifqf
Vending.apk - mediafire.com/?31bn3e258jjpj8d
Play.apk - mediafire.com/?wwcqrlfwt8o1gnv
If you have problem downloading this Play.apk I suggest try using this Vending_v3.9.17.apk instead. Be sure not to confuse with the earlier Vending.apk file, or better yet, rename it to something like Play3917.apk
adb install $your_choice_of_file_manager(must support root), I prefer ES File manager
using your file manager and browse to /data/su and install GoogleServicesFramework.apk (I'm not sure if you can just do adb install GoogleServicesFramework.apk from your PC, but since I didn't do it that way and this is a known result, so I recommend doing it this way)
adb shell
su
mount -o remount,rw /system
mv /data/su/Vending.apk /system/app/Vending.apk
chmod 644 /system/app/Vending.apk
chown 0.0 /system/app/Vending.apk
mount -o remount,ro /system (not sure if this is necessary, but I better safe than sorry)
using your file manager and navigate to /system/app and install Vending.apk
mount -o remount,rw /system (only if you did step 11)
rm /system/app/Vending.apk
mount -o remount,ro /system
using your file manager and go to /data/su and install Play.apk or Play3917.apk depending on what you download
now you can delete both GoogleServiceFramework.apk and Play.apk in the /data/su folder.
That's all, your Google Play Store should now be working.
Login and have fun. I manage to install some stuff through that.
Click the "THANKS" button below.
OK, now to get a more complete gapps. The below steps are to be only after you have Google Play Store, meaning all the above steps are done. The instruction below will let your other app sync and use google account. Meaning stuff like RSS reader sync with google reader or Youtube app access your personal account. Well, atleast those are the two I have tried and seem to be working.
OUTDATED Instruction:
Instructions:
Download these two files. gapps-ics-inst.sh.img and gapps-ics-system.zip (if you use verygreen root method use this gapps-ics-inst.sh.img , the one embedded on this post instead. This one should work universally but untested. I re-wrote it to adapt for verygreen root method also. If it works I'll rewrite this part of instruction again to use the new version of the shell script.)
adb push gapps-ics-inst.sh.img /data/su/gapps-ics-inst.sh
adb push gapps-ics-system.zip /data/su/
This step might take some time
adb shell
su
cd /data/su
chmod 755 gapps-ics-inst.sh
./gapps-ics-inst.sh
This step could take some time too, once it return to shell, then go to next step
(optional delete installation file to save space) rm gapps-ics-system.zip
(optional delete installation file to save space) rm gapps-ics-inst.sh
exit
exit
(you should be back to your OS by now, if not keep exiting until you are out of adb)
adb reboot
once your nook is rebooted, the screen may say updating some files, this is normal.
enjoy, everything should work now.
If you didn't hit that "THANKS" button, you better do now. If you did, do it again?
Thanks leapinlar for catching the typo, I have reupload the shell script file now. And thanks to him for hosting the gapps-system.zip
There have been some errors on my initial instruction. Certain things have been point out. I have updated the instruction accordingly. leapinlar have also fixed gapps files and the shell script for that in post #34. So big kudo to him. I haven't have much time to toy with this lately, but since people report that his script work. So here are the new instruction.
If you were using verygreen version of root, try running this first.
Code:
adb shell su -c "/data/su/busybox chown shell.shell /data/su"
FAQ:
Q: I don't see the Google Play Market on the list of apps.
A: If you use the "Skip OOBE" aka Test mode, then (reboot first or go into shell and kill the app launcher and then) you have to hold down the Vol-Up key and tap the word Apps on the top to see them. After that I recommend installing other launcher, then they can see all the apps.
Q: Some people are saying after they install an adblock app, after reboot it get into bootloop and wipe everything.
A: The way most adblock apps work is that they modify the hosts file which usually located at /system/etc/hosts Well, as we have discussed before this is not a good idea to make change directly to /system folder(directory). The only adblock I know of that work is AdAway with a specific setting.
When installed, first you have to go to menu > preferences > target hosts file > /data/data/hosts, it will then ask to create symbolic link, say yes and then you can reboot.
Troubleshooting Tips:
I had a little problem today, unrelated to the GAPPS install mod here. But the problem involved Google Play not working correctly. I kept getting Google Play error pop up. So, I use Titanium Backup ROOT to wipe the data and then uninstall all the apps which names start with Google. I'm not sure if this is enough, it might but I didn't want to take any chance. This maybe unnecessary but I did it anyway; I delete all the files that I created in the /data/su/system that have anything to do with google. Basically anything that was unzip there. Rebooted, then re-apply the same google mod here. And problem solved. I did have to re-login again, but yes I clear up that Google Play error.
Pre-Requisite:
ADB + ROOT + Enable Unknown Source.
1. ADB: leapinlar wrote a post to help you getting ADB to work here.
2. ROOT: I wrote a guide on how to get root the easy way here.
3. Enable Unknown Source: Again, I make an easy little tool for you here.
Brand New and Improve Instructions:
Download these three files. New.zip GoogleMaps.apk and gapps-ics-system.zip
Unzip New.zip (don't unzip gapps-ics-system.zip)
run install.bat
PS: Now I know how hard it's to write a guide in xda. Prop to all those dev that have been there b4 and after, especially the one I have use their works.
That's it, I'm going out to buy one ASAP. Thanks for your hard work!
thanks for you Howto
after that is it possible to use Youtube and Google Maps apps?
Youtube can be install from Play Store but you have to sideload the Google Maps since it's not available for download in Play Store. GMail works, but the authentication through google account on other apps still aren't working. I guess this problem may be beyond my current level of tinkering knowledge.
great job on getting google market somewhat working!!!! We need the manual nooter developer or author to make what we need for the Nook HD AND HD+. Anyhow I belwive you need more framework files to get google authentication working and unfortunately they need to be installed within root folders like the /system folders and sub folders... Also Barness and noble included frameworks for google authentication, probably just not working with google apps installed manually.... gotta figure it out...
---------- Post added at 05:49 PM ---------- Previous post was at 05:47 PM ----------
By the way youtube app works installed older version from my Motorola Droid 3 manually through es file explorer and it works and does HD fine
I have been thinking about that and wonder if we can put those lib files on diff folder and sym link them? I still afraid it might reset the thing.
someone0 said:
Instruction:
[*]Optional, factory reset it. Seriously I cannot say this will work unless you start from scratch. If you already have rooted earlier, then install something like titanium backup and backup your porn(I mean data).
Click to expand...
Click to collapse
I was able to do this with root explorer after rooting with no problem.
Thanks for this (and your rooting zip - both are super!)
issue was fixed, removed obnoxiously long quote
smatticus said:
still have the issue where i can't get the nookcolortools to run properly from /system/app. it just crashes. i googled this and it says that i need to reboot the nook to apply the system/app move BUT that supposedly creates the bootloop. i REALLY don't want to do that so can someone help me out here?
Click to expand...
Click to collapse
You probably shouldn't quote anything that big unless you very need to. As far as getting nook color tool to run, did you set the file to have proper permission, eg: chmod and chown the file? Your other option is factory reset and start from scratch. Sometime getting a clean slate to start with make things easiler to follow.
Thank you for the Google Play Store. It works great for me. I want to install Google Voice. Before I installed your framework apk, I was not able to get the credentials to come up. Now since installing that, it comes up with my Google credentials and tries to authenticate them. But immediately Android System force closes and the sign in screen just sits there. Any ideas on this one? This is the last thing I need to make this my everyday device.
Sent from my Nook HD+ using Tapatalk
someone0 said:
As far as getting nook color tool to run, did you set the file to have proper permission, eg: chmod and chown the file? Your other option is factory reset and start from scratch. Sometime getting a clean slate to start with make things easiler to follow.
Click to expand...
Click to collapse
turns out i wasn't supposed to install the app via adb. my fault for not following instructions. thanks for your hard work
Nice, I think I am getting the Nook HD+.. Hope there is custom ROM soon.. thanks man
leapinlar said:
Thank you for the Google Play Store. It works great for me. I want to install Google Voice. Before I installed your framework apk, I was not able to get the credentials to come up. Now since installing that, it comes up with my Google credentials and tries to authenticate them. But immediately Android System force closes and the sign in screen just sits there. Any ideas on this one? This is the last thing I need to make this my everyday device.
Sent from my Nook HD+ using Tapatalk
Click to expand...
Click to collapse
I'm thinking about that right now but as I suggested, putting the google lib in other place and make symbolic link in the appropriate /system sub. I won't be able to test that theory of mine until I get home later tonight. I will have to research where all the files suppose to go and their permission. Unless you want to do it, you are welcome to.
I agree, getting authentication would be tha last missing link to make this device fully enjoyable as day-to-day usage. And the we can wait for custom ROM from real developers. That is definitely out of my knowledge.
works without full reset
figured i'd put it out there that i DID NOT do a full factory reset (partly to be a guinea pig, partly because i'm lazy) and this method DOES WORK without it. It took 2 tries (it loaded up the first time, then crashed a few minutes later.) the second time it worked like a charm. One note: the chown command gave me an "operation not permitted" notice, but the market IS working, i grabbed a TON of apps and thankfully got updates to the ones i purchased through the nook shop that hadn't seen an update since they first launched (i'm looking at you, machinarium).
Thanks!
Thanks so much for your work on this! I can access the Google Play Store along with the Amazon App Store now and have loaded up my new Nook with my favorite apps. My only disappointment is that I still can't get Amazon Instant Video or Google Play Movies to work...once these work I'll be in heaven!
leapinlar said:
Thank you for the Google Play Store. It works great for me. I want to install Google Voice. Before I installed your framework apk, I was not able to get the credentials to come up. Now since installing that, it comes up with my Google credentials and tries to authenticate them. But immediately Android System force closes and the sign in screen just sits there. Any ideas on this one? This is the last thing I need to make this my everyday device.
Sent from my Nook HD+ using Tapatalk
Click to expand...
Click to collapse
BTW, I got that working now, my theory works. Now only if I have a place to store 60+MB file. Then I can update this guide to include that. I was able to use Youtube app to access my account and so is my RSS reader to sync with google reader.
Access Denied
I'm getting an error when I try to execute ./gapps-inst.sh. It's saying cannot execute - Permission denied. I've rooted and followed the instructions to install Google Play and all worked fine...I'm on this last step and it won't work! Advice is much appreciated!! I also keep having permission denied issues with the adb push command...I can paste the files manually via ES File Explorer and rename to remove the .bin but I still can't install from adb shell.
I've also tried chmod 777 on the gapps-inst.sh prior to doing ./gapps-inst.sh but that produces a giant string of errors.
I'm at a loss!
someone0:
I just rehosted your files on my MediaFire account.
Removed links. New links on OP.
Alright, so I have no idea what Nook HD/HD+ thread to put this is in... so here i go.
1. Will these steps get the play store on the Nook HD as well?
2. Will the apps show up in the Nook app section, or do we still need a launcher. I have sideloaded all my apps, but have to use a launcher to get at them.
Thanks!
someone0:
There is are a couple of typos in your gapps-inst.sh file -
Code:
ln -s /data/su/system/usr/srec/en-US/google_hotword_clg /system/usr/en-US/google_hotword_clg
ln -s /data/su/system/usr/srec/en-US/google_hotword_logistic /system/usr/en-US/google_hotword_logistic
are missing the /srec in the second /system link.
Also it seems the real /system has these files so the symlinks fail.
Code:
ln -s /data/su/system/etc/permissions/com.google.widevine.software.drm.xml /system/etc/permissions/com.google.widevine.software.drm.xml
ln -s /data/su/system/framework/com.google.widevine.software.drm.jar /system/framework/com.google.widevine.software.drm.jar
ln -s /data/su/system/usr/srec/en-US/acoustic_model /system/usr/srec/en-US/acoustic_model
Dalvik cache cleaner is a shell script which clears the Dalvik cache that can be used with Android Terminal Emulator.
Root and busybox is required, if you don't know what root and/or busybox is then do NOT bother using the script.
Place the shell script in the main directory.
With Android Terminal Emulator type:
su
sh /sdcard/Dalvik_cache_cleaner.sh
The process should be close to instant depending on how much files you have in the directory.
Download: http://caftp.3owl.com/Shell_Scripts/Dalvik_cache_cleaner/Dalvik_cache_cleaner.sh
It worked
~~~~~~~~~~~~~~~~~~~~~
Samsung galaxy s2
Rom: Jedi knight 6
kernel: Jedi kernel 2
~~~~~~~~~~~~~~~~~~~~~
And you thought celebrities weren't smart! =P
Is this also intended to run on every boot, ie via init.d
thebrainkafka said:
Is this also intended to run on every boot, ie via init.d
Click to expand...
Click to collapse
No, that would also waste too much time on boot then on a normal boot due to rebuilding the cache everytime.
When you uninstall an application, usually a dalvik cache file is left over wasting space.
But if you want you can use ROM Toolbox from JRUMMY APPS INC. in the Play Store.
There is a Scripter in that application that you can use for such thing but the problem is that when I tryed using the su binary in the shell script, there is an issue where the su binary in the shell script will just cut off the other parts of the script and only the su binary so your answer would be fat chance unfortunately. :/
Sent from my Sony Tablet S using xda premium
Issue fixed.
Is this the same as wiping dv cache through recovery. Also what will be the script for wiping cache? Will it be rm /cache?
Thanx!
The-Droidster said:
Is this the same as wiping dv cache through recovery. Also what will be the script for wiping cache? Will it be rm /cache?
Thanx!
Click to expand...
Click to collapse
Yes and the code is:
#!/system/bin/sh
rm /data/dalvik-cache/*
reboot
Click to expand...
Click to collapse
I'm not sure if /cache/ is really dalvik cache, on devices with OTA update support the OTA zip's will be stored their with other stuff but if you want I can give you the code for that.
On linux (That also means android) use 'chmod 755' for the permissions for the shell script.
I have tried adding 'su' but that fails has the terminal only executes the su binary so the rest of the script does not get executed.
Using the 'echo' binary to say out what it is doing is a fail has the terminal does not go anywhere due to the echo binary getting executed but it will not display output in the terminal anyway making the script not being executable.
Sent from my Sony Tablet S using xda premium
Man I am full with ideas.
I can create a shell script to do:
[OTA]
Remove OTA Update zip in cache
Copy OTA Update zip from cache to SDCard
[Files and Folders]
Remove LOST.DIR (That is just a useless folder )
Wipe SD Card
Wipe Zip files (useful for custom roms on your SD which you don't want anymore)
Well soon I should get more ideas so the OTA shell scripts will not be possible unless I get a rootable device with OTA functionallity (I do have a Sony Tablet S but I forgot to root it but I went and installed the firmware update without noticing) so it would be the Nexus 4 I would test it on in March.
The thing is that more shell scripts I create more pages I have to add to my website to give information about it, how to use it and the download link which can take around 10 Minutes just by editing the code, make backup and then upload via FTP.
Sent from my Sony Tablet S using xda premium
New shell scripts available which should be available tomorrow and if not a few days.
They are:
Aptoide Cleaner - I found out that the xml files are adding numbers to their file extensions so I built a script which can remove that problem real fast.
Take Out Bin - Removes all or at least most useless directories like LOST.DIR and LazyList, they are just a few.
ExtSD and USB Cleaner - Same has 'Take Out Bin' but it does it on the external SD Card while on USB, LOST.DIR will be erased has that should not be there.
-OLDER PROJECTS-
Dalvik Cache Cleaner - Read the first post.
Andro.Shell.Crash - This is good for developers has this does crash/lag/freeze the OS which can help a root exploit get in, of course there is different effects depending on the hardware and software, if the device is fast and has good hardware then it is possible that it may just lag and/or freeze but for older devices with older hardware can just crash.
NOTICE: The older projects are already out and available to download on my website.
I will be creating a forum about these shell scripts but I am not sure about the Aptoide one for many reasons.
I know that I am not suppose to be talking about this on a thread which has a different purpose but yeah, just an update.
EDIT: I uploaded and programmed the webpages from my tablet using WM FTP Client and DroidEdit Pro so that was a bit too early but all well, new thread(s) should come in tomorrow depending what will happen tomorrow (It is 03:30AM so it would count has today anyway).
Anyone can please guide me how to remove this script???
Thank you in advance
romelcool said:
Anyone can please guide me how to remove this script???
Thank you in advance
Click to expand...
Click to collapse
You just delete the shell script, you only use it in the Terminal Emulator so once you run it, it will wipe the dalvik cache so it will not do such thing in every boot.
Sent from my Nexus 4
Man I think you should create a script which are:
Auto clean of cache || Optimize App || Kill Media Process
If it's possible to you to create script with the list below that will be awesome ! ..
what is the code for auto cleaning cache every 30 minutes ? ..
and also auto optimize application every 24 hours ? ..
kill media process ?
I hope you could help me with this .. Thanks !
CoolApps said:
Download: http://caftp.3owl.com/Shell_Scripts/Dalvik_cache_cleaner/Dalvik_cache_cleaner.sh
Click to expand...
Click to collapse
Gone!
jidanni said:
Gone!
Click to expand...
Click to collapse
That's because I switched sites between 2012 - 2015. This thread was very inactive so I missed it out and didn't update the link with the new one.
The current server I use for it has some files that I'm aware of that are more often downloaded by users which means I ended up removing the shell scripts along with others that don't need to be there. I made a backup of everything before, by the way.
I don't feel that there's a need restore the file and plus, this thread's old.
Because of the sudden bumps of a thread that currently serves no purpose, something should be done about it to avoid further confusions.
Sent from my Nexus 4 using Tapatalk
Can you please tell me what your script did.
I made my own script that does
su -c 'find /data/data/*/cache/* -delete'
This one line saved me from installing multi-megabyte apps that do the same thing.
Is there anything more I should add to my script?
Now I can finally have enough room so Google Play can update apps again!
Thread closed at OP's request.
DISCLAIMER: YOU AGREE TO TAKE FULL RESPONSIBILITY FOR YOUR DEVICE IF YOU PROCEED.
The original thread (http://forum.xda-developers.com/moto-g/general/mod-save-data-space-cache-partition-t2942765) was getting to cluttered up with development and testing so I decided to start a new thread with the "finished" product. The original thread will be renamed to Q&A/Development. We might even ask for the old thread to be closed down. (up to @Bert98, the thread's creator.)
Moto G's internal eMMC card has a ~600Mb partition called /cache, which is not used since the apps' cache is stored in /data, so the latter fills up and the first one stays empty.
Owning a 8Gb model, having 600Mb not available for storage really bugged me, because my phone's memory (/data partition) was always full because it's a 5.7Gb space shared between apps and microSD files.
Now, it may not work for you if:
a) you have A LOT of apps installed.
And by "a lot", I mean more than 90-100 apps, but if you have a 8Gb model, you probably don't
b) you're running ART (this is default in lollipop and newer)
Since ART uses a lot more space than dalvik, the space in the /cache partition probably won't be enough. When I was running ART, it used 1Gb more than dalvik.
Original post by @Bert98
Click to expand...
Click to collapse
This was tested on my moto g 16GB which is running RetailUS_4.4.4 kitkat with CWM recovery. The custom ROM procedure was tested on the same phone but with cm11 Nightly installed.
Prerequisites:
1. You must have "adb root" functioning. If you don't head to this thread: http://forum.xda-developers.com/showthread.php?t=1687590 and there is a free download link at the bottom of the post.
Download and install the apk on your phone. Open up adbd insecure (the new app) and grant it superuser rights PERMANENTLY. Check the box that says "enable insecure binary" and make sure to check the box
that says "enable at boot."
2. You must have a recovery that can accept adb shell commands.
3. Root Access Duh?!
4. A windows machine capable of running batch files.
5. A decent text editor, notepad will work but notepad++ is strongly recommended. (Only needed if you are using STOCK ROM procedure)
Please, please make a nandroid backup before you continue!!!!
Stock ROM procedure:
Read the directions very carefully and then read them again, before continuing.
1. Download the cachemover_v1.3.zip from: LINK REMOVED DUE TO SCRIPT ISSUES.
2. Extract the contents.
3. Connect device to PC and navigate to the extracted folder.
4. Double click/Run the cachemover_Stock.bat
5. Follow the onscreen instructions until you get to the part where it says to edit a file.
6. About halfway through the script it will pull a file called "init.qcom.post_boot.sh" to the folder.
7. Open it with a TEXT editor and navigate to about line 487 (Might be different for 8gb model). Look here for a better understanding: https://www.dropbox.com/s/jr5lyl5s5i2jtpg/where to paste code.PNG?dl=0
8. Start a new line and paste this code in the file: (Refer to the image above for help)
Code:
chmod 655 /cache
chmod 655 /cache/dalvik-cache
chmod 655 /cache/dalvik-cache/*
9. Make sure to save the file in the same folder as the cachemover_Stock.bat
10. Press any key to continue on the script and let it do its thing.
11. It will reboot several times and land you on the home screen/lock screen.
12. If the script hangs after a reboot, you need to unlock the device to reestablish a connection with your computer.
13. There might be one or two force closes but once you close the notifications they will not come back.
Custom ROM procedure:
USE THIS FOR ROMS THAT DO NOT REMOUNT OR CHANGE PERMISSIONS OF /CACHE ON BOOT
1. Download the cachemover_v1.3.zip from: https://www.dropbox.com/s/bzj34g4q1s61ojz/cachemover_v1.3.zip?dl=0
2. Extract the contents.
3. Connect device to PC and navigate to the extracted folder.
4. Double click/Run the cachemover.bat
5. Follow the onscreen instructions.
If anything goes wrong:
Go to recovery, wipe cache, then wipe dalvik-cache and reboot. This should get your device back to how it was.
(If you used STOCK ROM procedure)
The script made a backup of the "init.qcom.post_boot.sh" file to /sdcard/init_backup
You can restore the shell script to /system/etc/ via shell commands or by using a root browser. To restore permissions:
Code:
chmod 740 /system/etc/init.qcom.post_boot.sh
chown root:root /system/etc/init.qcom.post_boot.sh
Custom ROM procedure already has a restore script!
I am currently working on an auto restore script for stock and that will be relased soon, hopefully! :good:
Changelog:
v1.0 - First stable release. Does not work on STOCK ROM.
v1.1 - Added a restore script.
v1.3 - Added support for STOCK ROM. There are still a few bugs.
How it works?!?!
Coming soon...
Huge thanks to @Bert98 and @dd043
Hit the thanks button if it worked! I went through about 50 factory resets, and reflashed the ROM about 25 times, and put about 10 hours of work into this script! Really motivates me for future projects. :laugh:
Thanks for your help man and effort.
I encountered a problem, everything works up until my device boots in CWM to fix permissions, then just sits there doing not alot I don't even see the option in my CWM.
Any ideas? cheers
Sent from my XT1032 using XDA Free mobile app
When it reboots to cwm unplug the cable and replug it, if it hangs just type these commands manually from a command window.
chmod 655 /cache
chmod 655 /cache/dalvik-cache
chmod 655 /cache/dalvik-cache/*
reboot
If this does not work you may ned to go into mounts & storage in the cwm menu and click mount /cache. Then try the commands again.
I'm having some issues on stock.
I thought 0655 fixed everything but no, I can't install any app after moving the dalvik-cache to /cache. I tried chmoding 0777 on the new cache folder, on /cache itself, to no avail.
Code:
E/dexopt cannot open '/data/dalvik-cache/[email protected]' for output
Anyone can confirm it's not only my device? And/or can help find a fix?
Also does someone knows how to execute commands on a particular init step? Real init.rc scripts can do:
Code:
on post-fs-data
mount -o bind /cache/dalvik /data/dalvik-cache
It there was a way to achieve the same from post_boot/init.d we could mount -o bind /cache/dalvik /data/dalvik-cache and all permissions issues would disappear as well as the need for symlink.
You have a typo in the threads title. Just a heads up.
Vuciz said:
You have a typo in the threads title. Just a heads up.
Click to expand...
Click to collapse
Thanks for letting me know!
dd043 said:
I'm having some issues on stock.
I thought 0655 fixed everything but no, I can't install any app after moving the dalvik-cache to /cache. I tried chmoding 0777 on the new cache folder, on /cache itself, to no avail.
Code:
E/dexopt cannot open '/data/dalvik-cache/[email protected]' for output
Anyone can confirm it's not only my device? And/or can help find a fix?
Also does someone knows how to execute commands on a particular init step? Real init.rc scripts can do:
Code:
on post-fs-data
mount -o bind /cache/dalvik /data/dalvik-cache
It there was a way to achieve the same from post_boot/init.d we could mount -o bind /cache/dalvik /data/dalvik-cache and all permissions issues would disappear as well as the need for symlink.
Click to expand...
Click to collapse
Let me try and do that right now... Ill get back to you if it does!
My script works on stock btw... But the mount way seems a bit easier and might cause less errors than my way.
Try it please.
skyguy126 said:
Let me try and do that right now... Ill get back to you if it does!
My script works on stock btw... But the mount way seems a bit easier and might cause less errors than my way.
Try it please.
Click to expand...
Click to collapse
Yes I've tried your script, all went well but the result is the same. The script itself works nicely btw
Applications present before moving cache work perfectly, but I can't install anything new. I suspect it might be my device but before wiping everything I'd prefer feedback from others :fingers-crossed:.
I cannot install new apps as well. The mount command you showed me has the same effect too. I honestly don't know anymore, the sym link did not allow the install of new apps nor did the mount command you sent me. Correct me if I am wrong.
Edit: Going through all the init files on my phone to see which one remounts /cache at boot.
Why does the init.rc get overwritten at boot. Is it because the kernel (boot.img) is the one that copies it over? I have found by changing the perms/locations in this file and init.target.rc you can achieve what this mod is trying to acomplish.
I don't see the mount cache command in CWM strange
I've managed to get back to normal, thanks for everyone's help though, I will keep and eye on the thread
Sent from my XT1032 using XDA Free mobile app
non-windows version?
Thanks for this tool. It's a great idea and our Motos really need it.
However, I have a problem - I do not own a windows license (os x and ubuntu user) and I would prefer not to spend $120 just to use it for this script. Pirating is out of the question for me.
I was wondering if there is any chance of having this script written for linux and/or mac. If impossible, is there a LEGAL way of running windows in a virtual machine? Something like a trial or similar?
If you know how just convert it to shell script for osx and Linux. I give you permission to do this but you may not take credit or rehost your creation.
Ok so I have the kernel extracted and we could modify and flash that, but I believe that it's not really necessary. There are a lot of risks to flashing kernels and I am not willing to take it. So is there a way we can modify dalvik so it creates it's cache in /cache instead.
skyguy126 said:
Why does the init.rc get overwritten at boot. Is it because the kernel (boot.img) is the one that copies it over? I have found by changing the perms/locations in this file and init.target.rc you can achieve what this mod is trying to acomplish.
Click to expand...
Click to collapse
Yes the init.rc is in the boot ramdisk. I don't think it would be worth the trouble to rebuild a boot.img. The moto g is fairly unbrickable but it's quite a lot of work to setup an environment to rebuild an image :/.
Too bad for the mount command, I was sure it was working but maybe I had changed something else and don't quite remember the steps to reproduce
We could possibly implement a shell script toggler for when we need to install new apps, but I'm afraid it'd become annoying fairly quickly: I noticed the issue initially because google play services decided to update itself, failed, and broke all google apps. As far as I know this autoupate can't be disabled.
Thanks for trying!
dd043 said:
Yes the init.rc is in the boot ramdisk. I don't think it would be worth the trouble to rebuild a boot.img. The moto g is fairly unbrickable but it's quite a lot of work to setup an environment to rebuild an image :/.
Too bad for the mount command, I was sure it was working but maybe I had changed something else and don't quite remember the steps to reproduce
We could possibly implement a shell script toggler for when we need to install new apps, but I'm afraid it'd become annoying fairly quickly: I noticed the issue initially because google play services decided to update itself, failed, and broke all google apps. As far as I know this autoupate can't be disabled.
Thanks for trying!
Click to expand...
Click to collapse
How about making a simple apk that toggles this feature. Something like when you click the icon it doesn't even open but gives a little notification of success. Something like that. I myself am not experienced with apks but I can put together a shell script for the apk.
skyguy126 said:
Ok so I have the kernel extracted and we could modify and flash that, but I believe that it's not really necessary. There are a lot of risks to flashing kernels and I am not willing to take it. So is there a way we can modify dalvik so it creates it's cache in /cache instead.
Click to expand...
Click to collapse
Patching dalvik itself sounds promising. It can probably be done with in a batch script with a command line hex editor.
The path is defined in frameworks/base/cmds/installd/installd.h
Code:
#define DALVIK_CACHE_PREFIX "/data/dalvik-cache/"
Not sure if there is another mention in the source tree.
But there's nothing to say we wouldn't face the same issue, the error message in the logcat is pretty generic
dd043 said:
Patching dalvik itself sounds promising. It can probably be done with in a batch script with a command line hex editor.
The path is defined in frameworks/base/cmds/installd/installd.h
Code:
#define DALVIK_CACHE_PREFIX "/data/dalvik-cache/"
Not sure if there is another mention in the source tree.
But there's nothing to say we wouldn't face the same issue, the error message in the logcat is pretty generic
Click to expand...
Click to collapse
Ill try it. I don't mind doing a bunch of resets because I am using my moto g as a test bench anyway. My daily driver is the OnePlus One
dd043 said:
Patching dalvik itself sounds promising. It can probably be done with in a batch script with a command line hex editor.
The path is defined in frameworks/base/cmds/installd/installd.h
Code:
#define DALVIK_CACHE_PREFIX "/data/dalvik-cache/"
Not sure if there is another mention in the source tree.
But there's nothing to say we wouldn't face the same issue, the error message in the logcat is pretty generic
Click to expand...
Click to collapse
EDIT: Unfortunately it didn't work. I don't know if I modified the installd file correctly. The program I used is HxD.
Is there a way we can force dalvik to start after the directories are created. And change dalvik to create it in /cache.