I am posting this in the Developer forum, because it is still a little more than a In-experienced user can handle at the moment, and the potential to get into a bootloop is a little higher if you are not familiar with what you are doing here.
If you are at all new / uncomfortable with Android, UNIX/LINUX, this phone, or adb, then: PLEASE DON'T TRY THIS AT HOME.
If you get into a bootloop I am not responsible for this, nor is this the place to complain if that happens. You can ask for support here though if this process has caused that.
If you do get into a bootloop, then try and help me out, with providing as much info as possible with what happened (any output or screen prints are VERY helpful). I am also posting the original /system/etc/init.goldfish.sh file here AT THE BOTTOM OF THIS POST. That way if it does all go wrong it is here to grab. So don't go asking for it someplace else, or even asking here for it.
You have been warned!
Now with that out of the way, on to the good stuff.
1) Go grab some kind of bloat freeze program, from the market. I have used bloat freezer from the market with great success.
Just download and install it, don't run it just yet, if you already have, and frozen the "Device Health Application", then unfreeze it, and reboot, before doing the next step.
It is VERY important that it is done in EXACTLY this order. The reason is, if the Device Health program is frozen when you let the init script run, it will not work exactly as it should and these services will restart, since part of it is frozen when it first runs, and it all has to be disabled in the proper way, so that it can not be restarted remotely, or we will HAVE to use cron to run checks. Cron is an elaborate hack, I don't want to have to do, unless we HAVE to. If you do it in the exact order noted here, cron will not be needed and this will not restart.
2) Go get the init.goldfish.sh file from http://dl.dropbox.com/u/45576654/init.goldfish.sh.tar
push this tarball to your phone:
Code:
adb push init.goldfish.sh.tar /data/local/
End code
Now is the command line part of this hack.
Code:
adb shell
su
mount -o remount, rw /system
cd /data/local
tar -xvf init.goldfish.sh.tar
cp /system/etc/init.goldfish.sh /sdcard/init.goldfish.sh
cp ./init.goldfish.sh /system/etc/init.goldfish.sh
chown root /system/etc/init.goldfish.sh
chmod 550 /system/etc/init.goldfish.sh
mount -o remount, ro /system
reboot
End code
Now when your phone comes back up:
3) Open your bloat freezer program and freeze the "Device Health Application"
Your phone will freak out, and tell you that Device Health has stopped and it will keep asking you to FC, all you can do is pull the battery.
Put the battery back in the phone an boot it up.
Now CarrierIQ should be 100% disabled on your Atrix 2.
As promissed, here is the Original /system/etc/init.goldfish.sh file in a tarball, just use the same code above to put this back in place.
DON'T USE ROOT EXPLORER TO COPY THESE FILES INTO PLACE!!!
Original /system/etc/init.goldfish.sh file:
http://dl.dropbox.com/u/45576654/init.goldfish.sh-orig.tar
The Jedi Master strikes again!
The force is strong in this one. Seriously Jim you absolutely amaze me. You are the Linux guru.
Sent from my MB865
Train us, he will.
Sent from my MB865 using Tapatalk
LOL....
Hopefully I have not scared everyone from trying this.... I just want to let all the newbies who just got this as thier first android phone yesterday, and rooted it today, and now think that this is a good hack to try, that this is not the best thing for them just yet. It can and will bootloop the phone if you get too excited and don't follow the directions exactly... I got mine in a bootloop testing this all out, and finding the exact steps, but it was not hard to get out of, because it gets into android enough to let you adb in, if you screw up...
quick question: Why would rooting followed by freezing not work for that application? I think I did that when I got the phone. I don't see anything called Device Health in my running or installed applications.
Is carrierIQ still running on my phone? Have you got a string I can look for in the 'ps' output in the Terminal to confirm? There are 100000 processes running on these phones these days, most with cryptic names.... I miss the G1 days....
devsk said:
quick question: Why would rooting followed by freezing not work for that application? I think I did that when I got the phone. I don't see anything called Device Health in my running or installed applications.
Is carrierIQ still running on my phone? Have you got a string I can look for in the 'ps' output in the Terminal to confirm? There are 100000 processes running on these phones these days, most with cryptic names.... I miss the G1 days....
Click to expand...
Click to collapse
No just freezing the device health app just stops the collection process.
The part where you run the commands to stop the services in android are where the data can and will be sent to CIQ or AT&T, there are other things collected that att does not care much about (ATT only wants what is collected with the dev health app), and that goes straight to CIQ, so the services at the OS level are VERY important to stop. There is really not a way to see them running, but I have found that these can and will restart if my instructions are not followed 100%. To find out if CIQ is doing anything take a look on youtube there is a video that explains how to look at the system logs and see what is being collected if anything, and what is being sent out. After a lot of trial and error, I found this is the ONLY way to stop it 100%.
Hey Jim. sorry I've been out of the forums for so long on this. I was going to dig around my atrix2 and see what I could find wrt carrieriq. I got stuck on missing shell tools and you gave me some advice wrt paths and such. I was wondering if you could point me in the right direction for fixing up my env when I shell in? I also don't seem to have grep anywhere... odd.
YOu mentioned doing some of the destructive work in an emulator, and I would like to try the same thing, but I've no idea how to get the atrix2 ROM into an emulator. How did you accomplish this?
I followed the instructions above precisely and verified that my init.goldfish.sh is indeed modified correctly with the carrieriq stuff, and have suffered no ill effects. I have not, however, attempted to determine if carrieriq processes have stopped running. I did notice that after having frozen and unfrozen device.health.monitor a few times, it doesn't ever register as a running app... wonder what's up with that.
thanks for the help.
I was wondering....could this be made into a handy dandy flashable zip?
Then after flashing just freeze the app?
Sent from my MB865 using XDA App
tylercarter said:
I was wondering....could this be made into a handy dandy flashable zip?
Then after flashing just freeze the app?
Sent from my MB865 using XDA App
Click to expand...
Click to collapse
Yep, working on it, should have it up for download tomorrow.... It will also be in my rom.
Jim
Sent from my MB865 using xda premium
jimbridgman said:
Yep, working on it, should have it up for download tomorrow.... It will also be in my rom.
Jim
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Sent from my MB865 using xda premium
jimbridgman said:
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
NICE! you really are a jedi master!
Who wants to be the first to try this out? I have created a flashable zip to disable CIQ on every boot, all you have to do is grab the file below:
http://dl.dropbox.com/u/45576654/NoCIQ.zip
Then with CWM, flash it, don't wipe anything, except maybe dalvic cache, but nothing else. This will only flash one file to your phone.
You will still have to freeze the device health app as in the OP.
This is just a test right now, once someone other than me tests this, and reports back, that all is great, then I will update the OP, to this method.
jimbridgman said:
Who wants to be the first to try this out? I have created a flashable zip to disable CIQ on every boot, all you have to do is grab the file below:
http://dl.dropbox.com/u/45576654/NoCIQ.zip
Then with CWM, flash it, don't wipe anything, except maybe dalvic cache, but nothing else. This will only flash one file to your phone.
You will still have to freeze the device health app as in the OP.
This is just a test right now, once someone other than me tests this, and reports back, that all is great, then I will update the OP, to this method.
Click to expand...
Click to collapse
It said switch to edify scripting. Installation aborted. Something about gingerbread cwm 3. Not sure. Never see this before. I checked the zip and it has 2 updater scripts. One just has a ~ at the end. I know nothing of code but just trying to help.
Sent from my MB865 using XDA App
jimbridgman said:
Who wants to be the first to try this out? I have created a flashable zip to disable CIQ on every boot, all you have to do is grab the file below:
http://dl.dropbox.com/u/45576654/NoCIQ.zip
Then with CWM, flash it, don't wipe anything, except maybe dalvic cache, but nothing else. This will only flash one file to your phone.
You will still have to freeze the device health app as in the OP.
This is just a test right now, once someone other than me tests this, and reports back, that all is great, then I will update the OP, to this method.
Click to expand...
Click to collapse
Tried this. No go. Here is the error in CWM.
Installing Update...
Amend Scripting (update0script) is no longer supported.
Amend Scripting was deprecated by Google in Android 1.5.
It was necessary to remove it when upgrading to the ClockworkMod 3.0 Gingerbread based recover.
Please switch to Edify scripting (updater-script and update-binary) to create working update zip packages.
Installation Aborted.
There ya go. Hope this helps.
holeshot77 said:
Tried this. No go. Here is the error in CWM.
Installing Update...
Amend Scripting (update0script) is no longer supported.
Amend Scripting was deprecated by Google in Android 1.5.
It was necessary to remove it when upgrading to the ClockworkMod 3.0 Gingerbread based recover.
Please switch to Edify scripting (updater-script and update-binary) to create working update zip packages.
Installation Aborted.
There ya go. Hope this helps.
Click to expand...
Click to collapse
hes working on it. wont be much longer
Why not use the app by TrevE?
Sent from my MB865 using xda premium
1.18.12 said:
Why not use the app by TrevE?
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
That does not perform the hack, only detects if it is running. The voodoo ciq detection app works much better though.
Jim
Sent from my MB865 using xda premium
I just rooted my phone, applied the hack and used Titanium Backup to freeze the Device Health App but I didn't see any FC.
Although when I opened Ti Backup, it told me that my su right are wrong. They are 4755 instead of 6755 or something like that and TiBu told me that it will fix it. I fixed it then froze the app and no FC or nothing. Phone is running fine but not sure if it worked.
Is it really necessary for the app to FC in order to show that it worked?
Should I try it all over again?
Thank you.
noobsquared said:
I just rooted my phone, applied the hack and used Titanium Backup to freeze the Device Health App but I didn't see any FC.
Although when I opened Ti Backup, it told me that my su right are wrong. They are 4755 instead of 6755 or something like that and TiBu told me that it will fix it. I fixed it then froze the app and no FC or nothing. Phone is running fine but not sure if it worked.
Is it really necessary for the app to FC in order to show that it worked?
Should I try it all over again?
Thank you.
Click to expand...
Click to collapse
Go download and install this, and it will show you if it (CarrierIQ) is active or not.
https://market.android.com/details?id=org.projectvoodoo.simplecarrieriqdetector&hl=en
Related
I have been trolling the forums for awhile and I never post but this is something that I have not been able to come across. Why after I used the bootstrap app and load into the recovery menu that now every time I go to reboot my phone I automatically go into the recovery menu even after a successful boot? Hope I worded that right. Please help and thank you!!
just realized I am in the theme section. Can this be moved to the appropriate board. THANKS!!
That's the way it works, it hijacks the bootloader, trust me its a good thing. Bootloop, battery pull, recovery, restore backup. Several times I've been glad it works that way.
Sent from my DROIDX using XDA App
Wait. I have a normal reboot. Maybe mine is messed up?
Yeah I got that but I thought it was only if I pulled the battery after it bootlooped. It does it every reboot except after I flashed a "rom", but I didn't like the rom so I reverted back to stock. I mean its awesome to have the security blanket but it can also be a bad thing if my 14 yo cousin gets ahold of my phone then formats my system an then reboots. Thanks for the help by the way.
Sent from my DROIDX using XDA App
The recovery works by looking for a file : /data/.recovery_mode
If it's there, then it goes into recovery mode, if not, then it allows for a normal boot.
However, if doing normal boot, it actually places the /data/.recovery_mode file and then erases it once the system is fully booted. I know this is confusing, but this is how it knows to go back into recovery if you did a battery pull (ie, the file was created, but never erased since you didn't complete the boot process).
All of this is supposed to happen automagically, but I've heard of that file sometimes getting 'stuck' and not deleted. Thus, causing you to reboot into recovery every time.
There is nothing inside the file, just an empty marker. You may want to delete that file and reboot. Should help.
-Z
If you want to remove bootstrap, you can do SBF flash, which I did several times and it perfectly works.
Zaphod-Beeblebrox said:
The recovery works by looking for a file : /data/.recovery_mode
If it's there, then it goes into recovery mode, if not, then it allows for a normal boot.
However, if doing normal boot, it actually places the /data/.recovery_mode file and then erases it once the system is fully booted. I know this is confusing, but this is how it knows to go back into recovery if you did a battery pull (ie, the file was created, but never erased since you didn't complete the boot process).
All of this is supposed to happen automagically, but I've heard of that file sometimes getting 'stuck' and not deleted. Thus, causing you to reboot into recovery every time.
There is nothing inside the file, just an empty marker. You may want to delete that file and reboot. Should help.
-Z
Click to expand...
Click to collapse
Ok I understand completely I knew the process but did not quite understand. Now the last question, is the only way to remove it to flash or can I use a file manager to remove it?
Oh and thanks for the help by the way.
UPDATE:
So I think I found it.
Unroot and Remove Recovery Via RootExplorer
jkpair said:
Ok I understand completely I knew the process but did not quite understand. Now the last question, is the only way to remove it to flash or can I use a file manager to remove it?
Click to expand...
Click to collapse
You can just delete it with a file manager (I am not sure about the permissions though .. you may need rootexplorer?)
I generally just do things like that from adb shell.
I KNOW I can delete it that way
Zaphod-Beeblebrox said:
You can just delete it with a file manager (I am not sure about the permissions though .. you may need rootexplorer?)
I generally just do things like that from adb shell.
I KNOW I can delete it that way
Click to expand...
Click to collapse
so for adb shell it would be something like:
Code:
adb shell
cd /system/bin
rm -r hijack
If thats right I won't try unless I know for sure. I don't know why but I have just got into a habit of googling after I ask. Lol I think this is it: Easy way to remove Koush's recovery?
So the logwrapper is the main file that matters not the hijack file and the original logwrapper was renamed to logwrapper.bin so I just replace Koush's recovery logwrapper with the previous one by copying over it.
Once again thanks for the help. Seems the answer is always 42.
jkpair said:
so for adb shell it would be something like:
Code:
adb shell
cd /system/bin
rm -r hijack
If thats right I won't try unless I know for sure. I don't know why but I have just got into a habit of googling after I ask. Lol I think this is it: Easy way to remove Koush's recovery?
So the logwrapper is the main file that matters not the hijack file and the original logwrapper was renamed to logwrapper.bin so I just replace Koush's recovery logwrapper with the previous one by copying over it.
Once again thanks for the help. Seems the answer is always 42.
Click to expand...
Click to collapse
I'm sorry, I misunderstood you goal here. I thought you wanted to keep the recovery, just fix it so it didn't come up on each reboot. If you are looking to completely remove the recovery, then I yes, I would follow the directions in the post you referenced, not the code section.
If you are only looking to 'fix' your reboot issues, I would suggest looking to see if /data/.recovery_mode exists on your phone. If it does, delete it. That's likely what is causing you to reboot into recovery each time.
Zaphod-Beeblebrox said:
I'm sorry, I misunderstood you goal here. I thought you wanted to keep the recovery, just fix it so it didn't come up on each reboot. If you are looking to completely remove the recovery, then I yes, I would follow the directions in the post you referenced, not the code section.
If you are only looking to 'fix' your reboot issues, I would suggest looking to see if /data/.recovery_mode exists on your phone. If it does, delete it. That's likely what is causing you to reboot into recovery each time.
Click to expand...
Click to collapse
Oh wow now I feel dumb. I thought I got it. So this would allow me to reboot and keep the recovery without it going into recovery every time I reboot. I hate asking noob questions lol
jkpair said:
Oh wow now I feel dumb. I thought I got it. So this would allow me to reboot and keep the recovery without it going into recovery every time I reboot. I hate asking noob questions lol
Click to expand...
Click to collapse
Assuming that is the problem. There may be another reason that you are getting dumped into recovery each time, but I suspect this is it. I will say that it's not 'normal' for recovery to come up each time. It should only come up if you somehow stop the boot process mid-way (Battery pull, etc) or use the Bootstrap recovery program to set it to reboot in recovery (which basically just creates the data file in question).
I would suggest you work through fixing this problem rather than just getting rid of the recovery. It's quite a powerful tool.
Zaphod-Beeblebrox said:
Assuming that is the problem. There may be another reason that you are getting dumped into recovery each time, but I suspect this is it. I will say that it's not 'normal' for recovery to come up each time. It should only come up if you somehow stop the boot process mid-way (Battery pull, etc) or use the Bootstrap recovery program to set it to reboot in recovery (which basically just creates the data file in question).
I would suggest you work through fixing this problem rather than just getting rid of the recovery. It's quite a powerful tool.
Click to expand...
Click to collapse
Yeah I really don't want to rid myself of it. I do believe I have an understanding now I am going to give it a shot when I can leave work. I will come back and post results.
Awesome It worked like a charm. Deleted the .recovery_mode file and am now happy.
Thanks for replying so quickly before I decided to just go ahead and remove the recovery menu all together.
jkpair said:
Yeah I really don't want to rid myself of it. I do believe I have an understanding now I am going to give it a shot when I can leave work. I will come back and post results.
Awesome It worked like a charm. Deleted the .recovery_mode file and am now happy.
Thanks for replying so quickly before I decided to just go ahead and remove the recovery menu all together.
Click to expand...
Click to collapse
Where is this file located? Im having the same problem.
Sent from my DROIDX using XDA App
DrewDanger said:
Where is this file located? Im having the same problem.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
From my earlier post:
The recovery works by looking for a file : /data/.recovery_mode
If it's there, then it goes into recovery mode, if not, then it allows for a normal boot.
However, if doing normal boot, it actually places the /data/.recovery_mode file and then erases it once the system is fully booted. I know this is confusing, but this is how it knows to go back into recovery if you did a battery pull (ie, the file was created, but never erased since you didn't complete the boot process).
All of this is supposed to happen automagically, but I've heard of that file sometimes getting 'stuck' and not deleted. Thus, causing you to reboot into recovery every time.
There is nothing inside the file, just an empty marker. You may want to delete that file and reboot. Should help.
Click to expand...
Click to collapse
I went through Astro and searched "/data/.recovery_mode" but it didnt bring up that file. I guess Im just confused at what exactly Im supposed to be looking for...
Yeah I ended up using a root file manager to do this was really easy. Just go the root menu and browse to data find recovery_mode and delete then reboot.
Oh and astro will not show what is in the data folder you have to get a root explorer app I think the one I used was android mate.
Sent from my DROIDX using XDA App
Ok cool I'll check that out. When I use Astro and go under "system" and scroll down it has a "recovery from boot" folder. Any idea what that is? When I open it there is a bunch of code script in it
Ok I deleted that file and it fixed it. I think Im just gonna un-root it when I get off work. Im over all this, lol. I'll wait until the Droid has more development as far as root access and what you can do. Can I just do the un-root through the one -click-root I used?
DrewDanger said:
Ok I deleted that file and it fixed it. I think Im just gonna un-root it when I get off work. Im over all this, lol. I'll wait until the Droid has more development as far as root access and what you can do. Can I just do the un-root through the one -click-root I used?
Click to expand...
Click to collapse
Yeah it has an option to unroot, but I can't state whether or not this is the best method to remove the root. I acctually am keeping my root and bootloader. Yeah I will be glad when there is a true rom as well but progress is progress.
in your build.prop replace the current text with this: you can get things like tv.com back
Code:
ro.build.description=passion-user 2.2.1 FRG83 60505 release-keys
ro.build.fingerprint=google/passion/passion/mahimahi:2.2.1/FRG83/60505:user/release-keys
i would upload one for people to flash but as some many people are on diff roms/kernels it would just cause more issues then its worth best way to go about fixing it is pulling the file from your phone (or the zip from teh rom your on). swapping out the text and pushing it back to /system
all credit goes to Decad3nce for the fix
Didn't s work for me...
Sent from my SPH-D700 using XDA App
you may have to reboot
Worked for me! Thanks.
Sent from Froyo!
Thanks worked great!!
shabbypenguin said:
in your build.prop replace the current text with this:
Click to expand...
Click to collapse
Wouldn't you like to be more specific? Your current instructions technically mean to replace the entire file with just those three lines...
Sent from my SPH-D700 using XDA App
Please note that users of Quantum Rom already have this fix applied, since 1.3
(Used the epic 2.1 key in 1.3, 1.4+ use the nexus one key)
Thanks shabby xD
Sent from my SPH-D700 using Tapatalk
Here's what I did from my PC with adb. (I have adb in my PATH so adjust the commands for wherever you might have adb.exe)
adb pull /system/build.prop
Then I edited the 2 lines on my PC with notepad++ and saved. Then I put it on my sdcard, remounted /system readwrite and copied it over to /system/build.prop and then rebooted.
adb push build.prop /sdcard/build.prop
adb shell
su (if your ROM didn't already drop you in to root, and check your phone for the superuser popup)
mount -t rfs -o remount,rw /dev/block/stl9 /system
cat /sdcard/build.prop > /system/build.prop
reboot
Sent from Froyo!
didnt work for me. I been trying to get the PayPal 2.2 to show up on the market but its a no go.
Im using Froyo also.
anyway we could just get the paypal.apk??
This didn't work for me either. Trying to get Pocket Blu installed, but it isn't working. TV.com isn't showing either. FWIW I have the new Market app if that means anything.
Any ideas?
Milkman00 said:
This didn't work for me either. Trying to get Pocket Blu installed, but it isn't working. TV.com isn't showing either. FWIW I have the new Market app if that means anything.
Any ideas?
Click to expand...
Click to collapse
Did you reboot your phone?
yes, and after rebooting a rechecked my build.prop file to make sure it took, and it was correct
Nevermind, I got it to work...
The end of the second line was missing the s. Put the s in, and it works perfect.
Can I get some clarification on this? I am using Mammon 1.0.3.1 and cannot get my sprint football ap to work.
Would this be an example of what this would fix?
Could the MSID number in my phone being different from my phone number be the reason it doesn't think this is a SPrint phone?
Thanks for posting a fix but it also didn't seem to work for me. I have been trying to load a program called Laser Appraiser from maket with no avail. Can anyone find it in their market?
worldlyinquirer said:
Thanks for posting a fix but it also didn't seem to work for me. I have been trying to load a program called Laser Appraiser from maket with no avail. Can anyone find it in their market?
Click to expand...
Click to collapse
Laser Appraiser shows up for me.
Milkman00 said:
Laser Appraiser shows up for me.
Click to expand...
Click to collapse
Thanks, Hmm I think I'll just wait for the latest froyo release and see if that helps
I tried downloading it and saving it to my SD card, but it's a protected app. I use AppMonster, which backs up all the apps for when I do flashing, but it doesn't do protected ones. Sorry man, I tried.
sorry i havent replied, most of the roms out there SHOULD have this baked in... i know acs and quantum do and the cm rom should but ill ask noob just to be sure.
For reference. http://forum.xda-developers.com/showthread.php?t=561579
Advantages:
jubeh said:
...there are two latent benefits to having odexed apps; decreased usage of dalvik-cache (thus, more space in /data) and decreased first-boot time after a wipe.
Click to expand...
Click to collapse
Disadvantages:
jubeh said:
The disadvantage of odexed apps is that, unless the classes.dex is kept inside the .jar or .apk, the app and framework are bound to each other (though an odexed framework can still be used under a full set of non-odexed apks, but not the other way around). This removes mix-and match, and it was the reason why I was waiting for a more current hero-dump that didn't have all it's apps and frameworks odexed...
Click to expand...
Click to collapse
This is just something quick that I threw together after i was asked some questions regarding creating .odex files and the entire dexopt mechanism.
I searched for scripts that allowed me to do this quickly but I only found half assed ones that really didn't fit my needs.
So here's a rough preview of the script: http://pastebin.com/PKxvzMmR
How it works:
After you flash the update.zip below, you'll have both the d3xopt.sh script and the dexopt-wrapper binary. You'll then simply jump into shell
Code:
adb remount
adb shell
and type "d3xopt.sh" and it'll spout out a brief overview of the script:
Code:
Clearing dalvik-cache
Directions:
This script allows you to create .odex files
to optimize dalvik runtime
How to use:
FR - Framework
SA - System Apps
ALL - Framework/System Apps
WARNING! WARNING! WARNING!
DO NOT DEXOPT SYSTEM APPS THEN FRAMEWORK.
ALWAYS DEXOPT FRAMEWORKS THEN SYSTEM
APPLICATIONS.
WRONG ORDER WILL RESULT IN ANDROID
RUNTIME ERRORS.
WARNING! WARNING! WARNING!
Example: d3xopt.sh FR creates the .odex files for core.jar, ext.jar, framework.jar, android.policy.jar, and services.jar in boot order as to not create any problems with runtime. This follows the order set forth by Jubeh here.
I did put in a few 'checks' that will stop the script from running. Right now it's just rough. (checks for Phone.odex and core.odex before initializing, if present, it exits).
Make sure that you nandroid before you run this script, that way, when you get a spam of force closes, you don't have to cry yourself to sleep.
jubeh said:
Also, be sure that if you want to keep an app's ability to be upgraded, don't odex it (actually, don't even have it in /system, toss it to /data/app)
Click to expand...
Click to collapse
Download Here: http://www.4shared.com/file/gz0eJdeY/D3xopt.html
Gonna try it right now on jaybob's Dec17th BlackMod, Thanks Deca!
LOL @ Spam of FC's! I got them, about 30 of them, and they keep coming back! Did I do it wrong or what? It cleared Dalvik, then I tried entering cmd's but none worked, entered FR and got nothing????
OK I figured it out
d3xopt.sh FR
Looks like most if not all the Apps failed... Rebooting now
It did boot up but FC for everything Nandroiding back...
cordell12 said:
Gonna try it right now on jaybob's Dec17th BlackMod, Thanks Deca!
LOL @ Spam of FC's! I got them, about 30 of them, and they keep coming back! Did I do it wrong or what? It cleared Dalvik, then I tried entering cmd's but none worked, entered FR and got nothing????
OK I figured it out
d3xopt.sh FR
Looks like most if not all the Apps failed... Rebooting now
It did boot up but FC for everything Nandroiding back...
Click to expand...
Click to collapse
try odexing on a fresh install before installing anything, also the fc's after the script runs will happen atleast if its anything like the other odex script i used on the vogue, also clearing the dalvik cache AFTER the script runs wont do too much since the dalvik cache gets emptied by the odexing process
Also before you run the script make sure you have atleast 15% of system space left or bad things can happen, and like the Op said is more than a few words, once its odex'd you can never theme it
Sent from my HERO200 using XDA App
Yeah, I dont have much space due to fierats. The dalvik cleared first, I was just out of order on my posting I do to much with themes on phone for this. I didnt see that it wouldnt work, or cause themes in future from working. Boredom, see a new thing and I wanna try it! Anything that can help the Hero is worth a shot
Yea dzo posted a thread about it in the vogue forums, the OP here doesn't exactly say it here but its true and yea FR could cause a problem
Sent from my HERO200 using XDA App
When flashing the zip from recovery, the whole /system/bin/ directory is chmod to 0755 permissions. This causes problems with apps which need superuser permissions. It took me more than a day to figure this out...
Joskevic said:
When flashing the zip from recovery, the whole /system/bin/ directory is chmod to 0755 permissions. This causes problems with apps which need superuser permissions. It took me more than a day to figure this out...
Click to expand...
Click to collapse
herp derp, fail on my part. Took the lazy route and just recursively changed permissions on flash instead of just doing it for the individual files. My bad.
Decad3nce said:
herp derp, fail on my part. Took the lazy route and just recursively changed permissions on flash instead of just doing it for the individual files. My bad.
Click to expand...
Click to collapse
Think you can make an updated version of it to use on my nook? I think odexing one of the nightlies would be pretty awesome
Sent from my PC36100 using XDA App
thoughtlesskyle said:
Think you can make an updated version of it to use on my nook? I think odexing one of the nightlies would be pretty awesome
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I would love an update too, odexing aospCMod would be awesome.
thoughtlesskyle said:
Think you can make an updated version of it to use on my nook? I think odexing one of the nightlies would be pretty awesome
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
il Duce said:
I would love an update too, odexing aospCMod would be awesome.
Click to expand...
Click to collapse
Sure, just need to revise the odexing order for gingerbread. Stuck doing homework right now but I'll have some time later this week.
Decad3nce said:
Sure, just need to revise the odexing order for gingerbread. Stuck doing homework right now but I'll have some time later this week.
Click to expand...
Click to collapse
Also how would I run this via terminal, for some reason my nook isn't recognized via adb
Sent from my PC36100 using XDA App
thoughtlesskyle said:
Also how would I run this via terminal, for some reason my nook isn't recognized via adb
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I was just about to chip in with the same question, I've got a Flytouch 3, we also can't get into ADB via the usb port, if we could run this script as a stand alone working off a directory with the files on a PC it would be extremely useful
hey Deca, wondering if there is a way to use this for /data/app ? I have evo3D now, LOTS of apps, and it boots wicked slow :/
Hi did this ever get updated for GB ??
Very good idea, hope it can work on modded roms.
Thanks.
Dead Link?
Hi dead Link??! Need it for Dev purposes??
Decad3nce,
the link is dead, can you upload the script again ?
thanks
So I've used the sqlite vacuum/re-index feature of V6 SuperCharger blindly without knowing what it does getting a placebo effect sort of thing, and I started doing some research on it and realized that this feature has started getting stripped out of a lot of stock roms and what not on android devices and that basically it makes it wayyyy easier for the system to index and sort out system/app files a lot of it was over the top for me but I figured there could be no negative effects to this at all.
So long story short I downloaded SQLite Installer from the market
Restarted and everything on my phone has been quick and painless it's been up for 6 hours now since the restart and have yet to have any lag/problems.
here's my set up:
Tweaked 2.0
0504 PBJ Kernel
OC'd to 1.2ghz (SIO i/o and Interactive governor)
don't know if it is placebo affect once again and I'd love to get some more veteran knowledge on this but I LOVE MY PHONE NOW
As I am a new member here I cannot post links but go to my thread at rootzwiki[dot]com/topic/25072-sqlite3-phone-is-snappier-than-ever/ and read the instructions there and download the easily flashable .zip file with the included detailing script.
happy flashing
p2kmafia
I just flashed so ill report if results are the same for me
Sent from my SCH-I510 using XDA
good lookin. there were positive results in my rootzwiki thread.
RFS or EXT4?
and is this the app: https://play.google.com/store/apps/details?id=ptSoft.util.sqlite3forroot
It would be fairly easy to run before and after database benchmarks in an app such as AnTuTu Benchmark. That would show if there are any real gains to be had.
Looking at the script, it essentially just re-writes all of the databases on the phone (via a VACUUM/REINDEX combo). Logic would state that if you have badly fragmented databases, which would manifest as things like degredation of performance over time, then this should make your phone a bit snappier.
[edit: I ran before and after tests (average of 3 tests). There was no appreciable difference between the tests. Now, the test results may not reflect real world results for two reasons: 1. I have no idea how the database I/O test in AnTuTu actually tests (what database, etc) and 2. I received errors when the script was attempting to vacuum databases ("error: unable to open file"), though the re-indexing worked fine.
End result? The test essentially means nothing and all we can go off of is anecdotal evidence. However, whether it's a placebo effect or not, this process simply can't harmfully impact your phone. As such, results should be anything from no change in response to some response increase.
Yeah, I know. A whole lot of typing that essentially says nothing. Sorry!]
jco23 said:
RFS or EXT4?
and is this the app: play.google[DOT]com/store/apps/details?id=ptSoft.util.sqlite3forroot
Click to expand...
Click to collapse
yes that's the app but check out my rootzwiki thread the flashable zip file adds the detailing script to your sd card that you'll need if you feel your device slowing down.
Cilraaz: thanks for testing this out. the error opening files might have to do with a bad install. keep the detailing script and try the app in the playstore for the install or reflash the zip
p2kmafia said:
Cilraaz: thanks for testing this out. the error opening files might have to do with a bad install. keep the detailing script and try the app in the playstore for the install or reflash the zip
Click to expand...
Click to collapse
I re-installed from Play and have tested my copy of sqlite3. It is a working copy. I also didn't flash the zip. I downloaded the zip, extracted the shell script, and manually placed it on my SD card. I've run the vacuum command manually as well, and received the same error.
I don't know what to tell you. I just re-ran the detailing script and I don't receive those errors, but if you know it is installed correctly/is vacuuming it shouldn't be a problem. I wish I knew more about this software to help out. I just discovered it helps a lot haha.
Cilraaz said:
I re-installed from Play and have tested my copy of sqlite3. It is a working copy. I also didn't flash the zip. I downloaded the zip, extracted the shell script, and manually placed it on my SD card. I've run the vacuum command manually as well, and received the same error.
Click to expand...
Click to collapse
Are you using script manager to run the script? And if so are you running with root privileges?
Sent from my SCH-I510 using xda premium
Endless2232 said:
Are you using script manager to run the script? And if so are you running with root privileges?
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
Script manager as root. Command line as root. The entire script and individual manual vacuums. Same result on all. Maybe I'll boot into CWM and run a fix permissions to see if that does anything.
Check the permissions of sqlite3 in system/xbin using root explorer. Read and execute should have all three checkboxes checked and write should have owner checked.
Sent from my SCH-I510 using xda premium
Endless2232 said:
Check the permissions of sqlite3 in system/xbin using root explorer. Read and execute should have all three checkboxes checked and write should have owner checked.
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
hey endless I just checked my sqlite3 and it has all 9 checks across the board. should I change them as well even though i'm not experiencing any problems?
p2kmafia said:
hey endless I just checked my sqlite3 and it has all 9 checks across the board. should I change them as well even though i'm not experiencing any problems?
Click to expand...
Click to collapse
No, you're fine.
So i did everything in the instructions and i have one little question. Do i keep the script running in the background?
Sent from my SCH-I510 using xda premium
Crap7126 said:
So i did everything in the instructions and i have one little question. Do i keep the script running in the background?
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
No. Once you've flashed/installed SQLite3 it runs by itself it's not a script. the detailing script is a run once kind of thing that you run if you feel your phone slowing down/lagging. I usually run it anywhere from once every 2 days to once every 3 or 4.
I also have an auto cache clearing app that I use that helps with lag so you don't get the two mixed up.
p2kmafia said:
No. Once you've flashed/installed SQLite3 it runs by itself it's not a script. the detailing script is a run once kind of thing that you run if you feel your phone slowing down/lagging. I usually run it anywhere from once every 2 days to once every 3 or 4.
I also have an auto cache clearing app that I use that helps with lag so you don't get the two mixed up.
Click to expand...
Click to collapse
Failed for me.
Sent from my SCH-I510 using xda premium
deafptl4ever said:
Failed for me.
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
what failed for you? i'd love to help out but need a little more information
Endless2232 said:
Check the permissions of sqlite3 in system/xbin using root explorer. Read and execute should have all three checkboxes checked and write should have owner checked.
Click to expand...
Click to collapse
If this was in regard to my issue, it's of no consequence. The sqlite3 executable was running fine, as evidenced by the fact that there were no errors in executing sqlite3 (the REINDEX command ran without problem). The permission issue would be with the database files themselves, though root should have no permission issues on r/w partitions like data and dbdata, or wherever sqlite3 is trying to write the temporary database during the VACUUM process. The VACUUM process actually reads data out of the database file, stores it in a temporary file, and then overwrites the original file with data from the temporary file. This eliminates "blank" data and fragmentation within the database files, which is why you see a slight performance increase and smaller database footprint.
Does anyone know where that temporary db file is stored by sqlite3?
Cilraaz said:
Does anyone know where that temporary db file is stored by sqlite3?
Click to expand...
Click to collapse
Unfortunately my expertise stops at how it works/why it works I just found out that it helps my phone and that's it
This def made my phone much snappier. My only question is, when i run the script i get a constant error, "error mountind database". Not really sure whato do (if anything) since it has made the phone quicker regardless.
Sent from my SCH-I510 using XDA
So, I'm attempting to root a Charge that the volume keys do not work. Apparently, 1 and 2 year olds who have great throwing ability is something the Charge, well, anything really, doesn't exactly appreciate. Normally, I root by going into the download mode, and flashing CWM, then installing the ROM. Obviously, not happening here.
My question is, has someone with more knowledge than I figured out how to accomplish this? Its running stock FP5. I really don't want to send it in because of the contract timing and wasteful of money. I'm also willing to experiment replacing parts, if someone knows anything about it...
Thanks.
Sent from my SCH-I510 (Tweaked 3.0) using xda premium
Yep. There's a jig that will force the phone into dl mode. IIRC it's branded for the gnex but it's confirmed to work on the Charge as well. http://forum.xda-developers.com/showthread.php?p=27533069
Sent from my SCH-I535 using Tapatalk 2
Hey, I had a thought of using ADB to root, and somehow forcing CWM on it, then using an app to boot it into dl mode. I've never used and before and don't know if it's possible, although, from what I read, it seems plausible. Can you offer any insight on this idea?
Sent from my SCH-I510 using xda
edji-x said:
Hey, I had a thought of using ADB to root, and somehow forcing CWM on it, then using an app to boot it into dl mode. I've never used and before and don't know if it's possible, although, from what I read, it seems plausible. Can you offer any insight on this idea?
Sent from my SCH-I510 using xda
Click to expand...
Click to collapse
If you have adb all set up and it properly recognizes your phone (something comes up when putting in the adb devices command) you can boot into download mode with
adb reboot download
Actually it's something I looked into recently for another member. I'm not saying it's not possible but I don't think we have the right tools for it. Originally ginger root was used via adb to root the charge but that's not going to work with our version of gb (assuming you could still find it). I'm not sure the format of cwm will work either. I'm not really proficient with adb so someone with more expertise might be able to get you going.
Sent from my Nexus 7 using Tapatalk 2
Awesome. I don't have it installed yet, but it doesn't look like it takes much to make it work. Plus, I have nine that isn't screwed up, so I think I'll see what I can come up with later.
On a side note, I can't post a reply to your tweaked 3.1 thread, but I ran into somewhat of a problem... run tweaktools, did the tweaks thing, phone BARELY would run. I also couldn't get a shell to run to get back in to uninstall. What I ended up doing to fix was a reinstall of SuperSU and installing a bash shell off a different emulator to get back into tweaktools. This was after I played in /system/etc/init.d awhile trying my hand at fixing it. Thought you may want/need to knoknow.
Sent from my SCH-I510 using xda
By the way, thanks for the tip. I'll report one way or another in a day or 2.
Sent from my SCH-I510 using xda premium
edji-x said:
On a side note, I can't post a reply to your tweaked 3.1 thread
Click to expand...
Click to collapse
You need 10 posts minimum to post in the Dev forums, XDA's rules.
Sent from my Droid Charge running [email protected] 3.2a enhanced by dSlice's Scripts & Tweaks
edji-x said:
Awesome. I don't have it installed yet, but it doesn't look like it takes much to make it work. Plus, I have nine that isn't screwed up, so I think I'll see what I can come up with later.
On a side note, I can't post a reply to your tweaked 3.1 thread, but I ran into somewhat of a problem... run tweaktools, did the tweaks thing, phone BARELY would run. I also couldn't get a shell to run to get back in to uninstall. What I ended up doing to fix was a reinstall of SuperSU and installing a bash shell off a different emulator to get back into tweaktools. This was after I played in /system/etc/init.d awhile trying my hand at fixing it. Thought you may want/need to knoknow.
Sent from my SCH-I510 using xda
Click to expand...
Click to collapse
Sorry to hear of the troubles - not sure what would have caused the issue with tweaktools. You weren't able to su, or you weren't able to open terminal emulator? What were you messing with specifically in the tweaks?
dwitherell said:
If you have adb all set up and it properly recognizes your phone (something comes up when putting in the adb devices command) you can boot into download mode with
adb reboot download
Click to expand...
Click to collapse
:banghead:
Sigh, I don't know why I didn't think of that lol. And I was Ninja'd. Double whammy lol
Sent from my SCH-I535 using Tapatalk 2
Okay, Found it in ADB, and am able to reboot into download, so all is well, I think.
On the tweaktools issue, I kinda did something like this...One tweak does okay, so lets install ALL of them....after that, performed the reboot, and everything went very sloooow. So, I tried to get into a term emulator, and nothing happened, the shell wouldn't even start. Blank screen. So, I tried a different outside of ROM toolbox. Nothing. So, I played around with the settings here and there, and still nothing. I then went into root browser, and started trying to manually move the tweaks out, nothing different. So, I downloaded another term emulator, "Better Terminal Emulator" and got a bash shell to at least open, was able to get into tweaktools, erase all tweaks, clear downloads. But the shells still weren't operating right. They'd open and run, but nothing would show on screen. So, a erase/reinstall of SuperSU, everything good....LOL
Well, maybe it'll help, maybe not, but here's the path I used to do this:
Visit samsung's site for the ADB download and install to c:\android-sdk\ (default)
Put USB Debugging on in phone
Start up command line and Odin 1.82
issue following in command line (notably in the c:\android-sdk\platform-tools)
Code:
adb reboot download
Odin up some Tweaked 2.2 with recovery and kernel for root
once rebooted, issue the following in ADB shell:
Code:
adb shell
su (Checked phone to be sure root was granted)
cd /data
rm -R *
cd /cache
rm -R *
cd /dbdata rm -R *
reboot, then adb reboot download.
Flashed EP4 Stock, updated,
Updated to FP5E
Once again, USB debug, adb reboot download, and Odin Tweaked 3.1 with 0302,
follow above code again, reboot, and I think I have it right....
Since the volume keys don't work on here, is there a way to screw around in the recovery mode via ADB rather than only the keys? I see ADB sees the phone in recovery, and seems to want to connect with it....Second is, is there a way to play with this in the *nix enviroment? I also have been searching for the Gingerbreak, etc to root this thing on stock, but haven't been able to do it....and last, is there a way to do a data wipe other than what I did, and think i accomplished with ADB?
Thanks
With the CWM that I am using, you can use the hard buttons at the bottom of the phone to navigate.
Sent from my SCH-I510 using Xparent Red Tapatalk 2