Permenantly Disable CarrierIQ WIP
What is CarrierIQ - In a nutshell CarrierIQ is OEM Sanctioned SpyWare
IQ Agent is software, typically pre-installed on mobile devices by handset manufacturers or network operators, designed to gather, store and forward diagnostic measurements on their behalf. Data available can include metrics on the device itself (e.g., firmware, battery levels, application performance, web performance) and performance data on voice and data connectivity between the device and radio towers. The mobile device manufacturers or network operators determine which of these metrics are actually collected, according to a set of criteria known as a "profile."[6] The IQ Agent software runs in the background, and the user is not usually aware of its presence unless the implementation includes an on-off switch
Click to expand...
Click to collapse
How do I get rid of it?
There are several different schools of thought in regards to "How do I get rid of it" One is just delete (De-Bloat) the carrier branded files from your ROM or use a custom ROM, unfortunately the only custom ROM gaurenteed not to have CIQ is either AOKP, AOSP, or CM outside of those there is no 100% garauntee that CIQ isn't lurking around in some obscure apk or service within your ROM.
Click to expand...
Click to collapse
Why this guide then if I can't garauntee its gone?
For two reasons, one so we can hopefully get multiple developers involved in researching exactly what is needed in order to completely once and for all remove CIQ. Two, since we can't be 100% sure it's gone we can at least minimize it's impact on our device.
Click to expand...
Click to collapse
There are already tools to remove CIQ on the PlayStore why not use those?
That's the easiest answer of all, none of them work NONE OF THEM. The most predomanent one wants you to purchase the full version for .99cents in order to remove CIQ and even then it doesn't remove it, it can't remove it for one very simple reason, CIQ is intrenched in multiple applications, services and frameworks requiring very careful expert coding to remove, miss one thing and your device no longer boots. Want proof? try this but make a backup first because your device won't boot anymore afterwords. With a root explorer browse to your /system/lib folder and delete these two files libiq_client.so and libiq_service.so. even if your rom is completely debloated with no carrier branded apks at all now reboot. Whoops stuck at the bootanimation? Yep because those modules are called from not only within the framework but several other apks and also the kernel ramdisk.
Click to expand...
Click to collapse
The nuts and bolts of this MOD (Remember it's a W.I.P.)
Phase 1: - /system/framework/ext.jar
I'm not going to go into how to decompile or edit smali thats for a different
thread, If you don't know how then stop here, go learn and then come back.
Click to expand...
Click to collapse
1. adb pull /system/framework/ext.jar
2. Decompile the jar file (I recomend Virtuous Ten Studio)
3. browse to /smali/com/carrieriq/client
4. Locate IQClient.smali
5. search for the word "submit" there are three submit .methods we are going to change each one.
REPLACE: (The entire method)
Code:
.method public shouldSubmitMetric(I)Z
WITH:
Code:
.method public shouldSubmitMetric(I)Z
.locals 2
const/4 v0, 0x0
return v0
.end method
REPLACE: (The entire method)
Code:
.method public submitMetric(IJ[BII)I
WITH:
Code:
.method public submitMetric(IJ[BII)I
.locals 7
const/4 v0, 0x0
return v0
.end method
REPLACE: (The entire method)
Code:
.method public submitMetric(Lcom/carrieriq/iqagent/client/Metric;)I
WITH:
Code:
.method public submitMetric(Lcom/carrieriq/iqagent/client/Metric;)I
.locals 9
const/4 v0, 0x0
return v0
.end method
6. Re-Compile ext.jar
7. Reboot to recovery (and mount system)
8. abd push ext.jar /system/framework/ext.jar
9. chmod 0644 ext.jar
10. wipe cache and dalvik cache
11. reboot
Ok, What did we just do?
Phase 1: Is complete, at this point even tho CIQ still has it's fingers in our device at least now it is hobbled as to exactly what it can do with the information it gathers, keystrokes, pictures, web urls, apps downloaded etc. There is a lot more to do yet but for now Phase 1 will give you a small amount of relief from CIQ. Stay tuned and visit this thread often for discussion, updates and general info regarding CIQ.
Click to expand...
Click to collapse
NOTES:
Ok so further research also shows IP connection information being obtained through the services.jar however, if we replace the submit methods in services.jar the device will reboot while trying to verify the stability of your network connection. So obviously there is more CIQ fingers stuck in the OS somewhere else. In comparison to an international S5 Rom which appears to have little to no carrier branding there is a significant difference in the services.jar. Hmmmm more research ahead I think.
Click to expand...
Click to collapse
Phase 2: - /system/framework/services.jar
1.adb pull /system/framework/services.jar
2. Decompile the jar file (I recomend Virtuous Ten Studio)
3. We are going to replace an entire smali fragment.
4. Browse to \smali\com\android\server\ciq
5. Open "IPConnectivityCIQ.smali"
6. Replace the entire contents of the file with the code below.
Code:
.class public Lcom/android/server/ciq/IPConnectivityCIQ;
.super Ljava/lang/Object;
.source "IPConnectivityCIQ.java"
# direct methods
.method public constructor <init>()V
.locals 0
invoke-direct {p0}, Ljava/lang/Object;-><init>()V
return-void
.end method
# virtual methods
.method public connectivityChanged()V
.locals 0
return-void
.end method
7. Re-Compile services.jar
8. Reboot to recovery (and mount system)
9. abd push services.jar /system/framework/services.jar
10. chmod 0644 services.jar
11. wipe cache and dalvik cache
12. reboot
Ok, What did we just do?
Phase 2: Is complete, At this point we have now removed the ability for CIQ to submit not only specific keystokes and user collected data but, we have also remove the ability for CIQ to track our location, network stability, cell strength and many more Network statistics. We aren't done yet there will be more and as I locate code and test i will be adding it to this guide.
Click to expand...
Click to collapse
Phase 3: - /system/framework/framework-res.apk
1. adb pull /system/framework/framework-res.apk
2. De-Compile the apk
3. We will be working with AndroidManifest.xml
4. Locate all instances of "carrieriq" either comment out or delete the corresponding xml sections
5. Remember to also comment out or delete any permissions xml segments for carrieriq
6. Re-Compile the apk and reboot your device to recovery
7. Mount system partition
8. adb push framework-res.apk /system/framework/framework-res.apk
Ok, What did we just do?
Phase 3: Is complete, At this point we have now removed the ability for the system to start any CIQ services and disabled all permissions associated with those services. We aren't done yet there will be more and as I locate code and test i will be adding it to this guide.
Click to expand...
Click to collapse
!!!NOTICE!!!
DEVS are free to use this code as a basis for their own work, also free to include in your own ROM or mods,
the only requirements are that you must give mention in your OP to my work. Check back here often for code
additions and changes as well as for any needed downloads if they become a part of this MOD.
Click to expand...
Click to collapse
Reserved
REserved
Why not simply post the recompiled JAR file here?
For one this is a work in progress, for two that's not what this thread is about. As the title says it's a [GUIDE][MOD] Which means it's HOW to do it.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
make a zip for SS Recovery and apply odex and deodexed roms, but I see you are busy with other projects.
jm2k7 said:
make a zip for SS Recovery and apply odex and deodexed roms, but I see you are busy with other projects.
Click to expand...
Click to collapse
the point of this whole website is to learn, educate, and share.
none of that occurs when all a user does is flash other peoples mods.
just sayin
Twiddler said:
Why not simply post the recompiled JAR file here?
Click to expand...
Click to collapse
Because how to is for everybody and for any build.
Enviado do meu SM-G900F
Hmm this is interesting. Is this the equivalence of using something like carrier iq detector to find out what's triggering the ciq to start then using something like android tuner to disable those receivers from starting up carrier iq? What I did was found as many of the receivers that kick up ciq in the system disabled them and this allowed me to stop libiq (renaming to .bak) from running without getting stuck in boot loop. If this is a better way I'll definitely follow this.
Sent from my LG-D850 using XDA Premium 4 mobile app
Well, I followed the guide. But when I install carrier iq detector, there still appears carrier iq.
tell me if this is normal, it is disabled even if it is detected?
jm2k7 said:
Well, I followed the guide. But when I install carrier iq detector, there still appears carrier iq.
tell me if this is normal, it is disabled even if it is detected?
Click to expand...
Click to collapse
What mine picked up was the files I had renamed to .bak and the apk that I had frozen. If you never deleted the lib files which I wouldn't recommend without disabling all ciq receivers then they are what the detector is picking up. Like the op said. His guide is a work in progress. Maybe his guide along with freezing/deleting any apps and deleting or renaming libs with disabling receivers could optimize killing ciq.
Sent from my LG-D850 using XDA Premium 4 mobile app
jm2k7 said:
Well, I followed the guide. But when I install carrier iq detector, there still appears carrier iq.
tell me if this is normal, it is disabled even if it is detected?
Click to expand...
Click to collapse
This is a work in progress, if you follow the current instructions it effectively disables the ability to send data, ciq detectors are unreliable since we can't yet get rid of the libs it will still detect ciq as present.
as I get time and determine more code changes this will improve
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Hey guys, I would love to do his if it was flashable. Any chance that could happen? Also, using a firewall blacks the communication from happening but doesn't stop it from trying right?
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
kalans said:
Hey guys, I would love to do his if it was flashable. Any chance that could happen? Also, using a firewall blacks the communication from happening but doesn't stop it from trying right?
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
considering the ongoing nature of this mod im not going to build a flashable zip as of yet, i have been running the modifications on my S5 for about a week or so and am still researching other methods to modify.
Firewalls do block the communication (provided you know exactly what ports and services to block) at this point the mod just returns null results for any attempt to gather data from keystrokes, cell tower location, wifi stats and network connectivity stats.
The guide definitely works. Not for the faint of heart, but it's a sure-fire way to stop CIQ's spying eyes.
I would be willing to post the recompiled ext.jar but honestly it's not that hard to do yourself. The downsides to using someone else's ext.jar should be apparent (security, for one) but I think if people really want it, they should be able to download it. As a CISSP, I promise to exercise the ethical responsibilities that I vowed to uphold. But, decompile it yourself and check my work if you don't trust it. That's probably the best way to verify - but then, why not just do the work yourself?
To deploy these jars without requiring a non-stock recovery, place them somewhere usable (for me, /sdcard/Download) and execute the following as root:
Code:
cat /sdcard/Download/ext.jar > /system/framework/ext.jar
cat /sdcard/Download/services.jar > /system/framework/services.jar
DO NOT USE THE `mv` COMMAND. In android, it does not work the way you expect GNU mv to work. Use cat.
Also you will want to wipe /data/dalvik and /data/dalvik-cache, then reboot!
Below is a large-ish image that shows my SGS5 with CIQ disabled. I have not tripped my knox counter and I have not installed a third-party bootloader. I wiped cache manually.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MonarchX said:
Does CarrierIQ slow down my phone or its connection in any manner or form?
Click to expand...
Click to collapse
Good question. I haven't run any performance metrics before or after the modification so I cannot answer with certainty. However, CIQ is designed to monitor LOTS of activity in the background (location, phone status, "diagnostic information") and upload it without your knowledge. Also, the data can be manually fetched by the carrier/authorities.
It stands to reason that disabling these threads and background processes would free up some of the phone's resources to do other things; however, these are pretty beastly devices that can handle simple stuff like CIQ spying with ease.
For more information about CIQ and what it does http://en.wikipedia.org/wiki/Carrier_IQ
deduction said:
Good question. I haven't run any performance metrics before or after the modification so I cannot answer with certainty. However, CIQ is designed to monitor LOTS of activity in the background (location, phone status, "diagnostic information") and upload it without your knowledge. Also, the data can be manually fetched by the carrier/authorities.
It stands to reason that disabling these threads and background processes would free up some of the phone's resources to do other things; however, these are pretty beastly devices that can handle simple stuff like CIQ spying with ease.
For more information about CIQ and what it does http://en.wikipedia.org/wiki/Carrier_IQ
Click to expand...
Click to collapse
Very well put, I didn't do any metrics either prior to the mod so can't speak to the performance either. but in theory it could given the correct circumstances. there is more to this that i have not posted yet as an addition to init.d by stopping some other background services but im still trying to determine if that portion is even needed. i have browsed thru the several more frameworks and found additional CIQ componenets but as of yet have not been able to successfuly remove them without causing compile errors or FC's within the framework itself. I am still actively working on this so continue to check back
deduction said:
The guide definitely works. Not for the faint of heart, but it's a sure-fire way to stop CIQ's spying eyes.
I would be willing to post the recompiled ext.jar but honestly it's not that hard to do yourself. The downsides to using someone else's ext.jar should be apparent (security, for one) but I think if people really want it, they should be able to download it. As a CISSP, I promise to exercise the ethical responsibilities that I vowed to uphold. But, decompile it yourself and check my work if you don't trust it. That's probably the best way to verify - but then, why not just do the work yourself?
To deploy these jars without requiring a non-stock recovery, place them somewhere usable (for me, /sdcard/Download) and execute the following as root:
Code:
cat /sdcard/Download/ext.jar > /system/framework/ext.jar
cat /sdcard/Download/services.jar > /system/framework/services.jar
DO NOT USE THE `mv` COMMAND. In android, it does not work the way you expect GNU mv to work. Use cat.
Also you will want to wipe /data/dalvik and /data/dalvik-cache, then reboot!
Below is a large-ish image that shows my SGS5 with CIQ disabled. I have not tripped my knox counter and I have not installed a third-party bootloader. I wiped cache manually.
Click to expand...
Click to collapse
which is the firmware it was pulled from?
juancollado2003 said:
which is the firmware it was pulled from?
Click to expand...
Click to collapse
This was from NCE, however should be valid with minor adjustments for other firmware as well
Sent from my Unity Powered Spaceship
Just wanted to say thanks for posting this.
Googled around a bit and it's really not hard to do. I learned something new so that's cool. Thanks was given in your first post. Now I have peace of mind that CIQ is no longer spying on me and collecting all my data.
deduction said:
The guide definitely works. Not for the faint of heart, but it's a sure-fire way to stop CIQ's spying eyes.
I would be willing to post the recompiled ext.jar but honestly it's not that hard to do yourself. The downsides to using someone else's ext.jar should be apparent (security, for one) but I think if people really want it, they should be able to download it. As a CISSP, I promise to exercise the ethical responsibilities that I vowed to uphold. But, decompile it yourself and check my work if you don't trust it. That's probably the best way to verify - but then, why not just do the work yourself?
To deploy these jars without requiring a non-stock recovery, place them somewhere usable (for me, /sdcard/Download) and execute the following as root:
Code:
cat /sdcard/Download/ext.jar > /system/framework/ext.jar
cat /sdcard/Download/services.jar > /system/framework/services.jar
DO NOT USE THE `mv` COMMAND. In android, it does not work the way you expect GNU mv to work. Use cat.
Also you will want to wipe /data/dalvik and /data/dalvik-cache, then reboot!
Below is a large-ish image that shows my SGS5 with CIQ disabled. I have not tripped my knox counter and I have not installed a third-party bootloader. I wiped cache manually.
Click to expand...
Click to collapse
I tried this files on ng3 but system never boot up, it looks are not compatible
Related
I thought I'd offer my solution to disabling the hard key vibrations on the Atrix since other people might find this useful. This method differs from the other solutions in that it doesn't tamper with your Silent Mode vibrations (like StreakVibrations does) and it's code based, so it shouldn't tamper with any themes you have installed (like the framework-res.apk method). It is firmware dependent though since it's a code modification.
You'll need an android.policy.jar modified for your firmware.
What I'm doing is I'm modifying the method called performHapticFeedbackLw, and telling it to skip triggering the vibrate pattern for all effects (there are 5) except for keyboard taps. Long press vibe, virtual key vibe, safe mode disabled vibe, and safe mode enabled vibe will no longer trigger... Incidentally, does anyone know what safe mode on this phone refers to?
To use the file, you need to be on Bell, Telstra, GingerBlur, Gladiatrix or stock ATT 1.8.3 firmware, and be deodexed. Can you copy the file to your phone without being deodexed? I don't know. I'm a programmer, but an Android newbie so just to be safe it's best if you're deodexed.
Before you try anything, obviously make sure you are backed up. At least copy your existing android.policy.jar so that you can restore it if necessary.
All you need to do is either:
a) Run the novibes.bat script packaged in the zip. There are a couple prerequisites:
1. Make sure to set your USB connection to "None" on your phone.
2. On your phone, go to Settings > Applications > Development and make sure USB debugging is turned on.
3. Plug your phone into your PC and let it install any necessary drivers.
4. Then you can run novibes.bat.
or
b) Follow the steps outlined below to do it manually:
1. Replace /system/framework/android.policy.jar with the one that I've attached.
2. Make sure the permissions of the file are set to rw-r--r-- (thanks for reminding me, Meloy and for correcting, natboy!). The easiest way is to use Root Explorer, long press the file, choose permissions, and set owner: read/write, group:read, others:read. Otherwise, use Terminal and type "chmod 644 /system/framework/android.policy.jar" without the quotations.
3. Reboot.
For those not on stock Bell, I'd be willing to modify your android.policy.jar and post it here if you provide somewhere for me to download it, and specify what firmware it comes from. It's quite quick to do once you're set up so I don't mind. Alternatively, make the change yourself:
1. Download baksmali and smali (both .jars and scripts, total 4 files).
2. Copy /system/framework/ from your phone to your computer.
3. Copy all the files from step 1 to the framework directory from step 2 on your computer.
4. Unzip android.policy.jar and copy its classes.dex file to the framework directory on your computer.
5. From the command line, navigate to the framework directory and run "./baksmali classes.dex". It will create a directory named "out".
6. Open "out/com/android/internal/policy/impl/PhoneWindowManager.smali" in a text editor.
7. Search for a method called "performHapticFeedbackLw". Go to near the bottom of that method, and you will see the Dalvik bytecode representation of a switch statement:
Code:
.sparse-switch
0x0 -> :sswitch_27 #This is for long press vibe
0x1 -> :sswitch_35 #This is for virtual key vibe
0x3 -> :sswitch_38 #This is for keyboard tap vibe
0x2710 -> :sswitch_3b #This is for safemode disabled vibe
0x2711 -> :sswitch_3e #This is for safemode enabled vibe
.end sparse-switch
8. Here's an example of how you might want it to change. Basically you want to replace the original goto labels with one that causes the method to step out without triggering a vibe, and that notifies the calling method there was no vibe by returning false. The label to use is called ":cond_1d":
Code:
.sparse-switch
0x0 -> :cond_1d #This is for long press vibe
0x1 -> :cond_1d #This is for virtual key vibe
0x3 -> :sswitch_38 #This is for keyboard tap vibe
0x2710 -> :cond_1d #This is for safemode disabled vibe
0x2711 -> :cond_1d #This is for safemode enabled vibe
.end sparse-switch
9. From the command line in the framework directory, run "./smali -o classes.dex out". You now have a new classes.dex that has your modification.
10. Zip up the classes.dex with the META-INF directory from your original android.policy.jar. Rename the zip to android.policy.jar.
11. Copy the new file to your phone and reboot.
12. At this point you should be done.
Will this be possible on the AT&T atrix? I currently use the streak vibe method but I'd like this much better.
Sent from my MB860 using XDA App
n1ckr0th said:
Will this be possible on the AT&T atrix? I currently use the streak vibe method but I'd like this much better.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1079873&page=3
Check out that thread over in general. The info for how to edit framework.res is there, but there is a flashable .zip that will disable the vibrations in either stock/rooted 1.83 or Gingerblur 3.5 for you.
bearsfan172 said:
http://forum.xda-developers.com/showthread.php?t=1079873&page=3
Check out that thread over in general. The info for how to edit framework.res is there, but there is a flashable .zip that will disable the vibrations in either stock/rooted 1.83 or Gingerblur 3.5 for you.
Click to expand...
Click to collapse
thank you, but i wonder if this specific method is possible on the atrix as to retain themes and such.
interesting that its in general, development may be a better home for it.
n1ckr0th said:
thank you, but i wonder if this specific method is possible on the atrix as to retain themes and such.
interesting that its in general, development may be a better home for it.
Click to expand...
Click to collapse
Yes, this would work perfectly fine on ATT. You can either follow the instructions I provided, or if you like you can post /system/framework/android.policy.jar from your phone somewhere and pm me the link so I can download it and I'll do it for you. Also mention what firmware you're on. I just don't want to download hundreds of MB of firmwares which is why I didn't set one up for all the ATT firmwares.
That other method requires editing a file that is guaranteed to change with any theme you install. That means anytime you change themes you'll need to edit that .apk yourself, or wait for someone to bring the change over. android.policy.jar is unlikely to change for themes.
Ok, I've posted a version for ATT 1.8.3 that was given to me by n1ckr0th.
n1ckr0th, let me know whether it works fine or not. There should be no problem, it looked just like the other 2 versions I modified.
Incidentally, he's using GingerBlur 3.5 so anyone on stock be careful (ie. copy your original file to somewhere else on your phone). It shouldn't matter at all because from what I see, there aren't any resources to modify in android.policy.jar so GingerBlur's should be the same as stock. At any rate, it won't brick your phone if you put the wrong one on. I put Telstra's on my phone by accident and it just messed up the the graphics on screen (maybe because the addresses were all wrong for my phone). You can still use adb, or sshdroid to copy and replace with your original android.policy.jar.
please delete
meloy said:
Don't use this on AT&T 1.83!
After the replace and reboot my phone was really laggy and some applications doesn't start anymore (camera, contacs for example). After i have replaced it with the original file i have still the same problem.
My phone config:
- SBF 1.83
- rooted (GingerBreak 1.20)
- sideloading enabled (GladEnabler)
- GladiAtrix 3 b0.2 ROM
- LauncherPRO
- GingerBread Theme only
Click to expand...
Click to collapse
What? That can't be right, if you still have the same problem after copying the original file, that means that you must have done something wrong. It's a single file change, provided you returned the file to the original, it will be back to the way it was. How did you copy the file? And also, are you deodexed? As mentioned in the original post, you have to be deodexed, because I don't know the results of using it on a non-deodexed system. Your posted config makes it sound like you might not be.
Sorry, my mistake. It is deodexed, I have just forgot to set the permissions to rw-r-r, you should maybe mention this in your start post. It's all working fine now. Thanks for the good work.
By the way, your mod (android.policy.att_1.8.3.zip) has added an "reboot" function to my phone, it is working well too.
meloy said:
Sorry, my mistake. It is deodexed, I have just forgot to set the permissions to rw-r-r, you should maybe mention this in your start post. It's all working fine now. Thanks for the good work.
By the way, your mod (android.policy.att_1.8.3.zip) has added an "reboot" function to my phone, it is working well too.
Click to expand...
Click to collapse
Haha, that's good. Had me scared for a moment, I didn't want to break anyone's phone!
Thanks for the tip, I'll mention that in the original post. Oh, and what do you mean by the reboot function...? Where did you access that? I certainly didn't add it, so it might be a mod added to GingerBlur?
maledyris said:
Oh, and what do you mean by the reboot function...? Where did you access that? I certainly didn't add it, so it might be a mod added to GingerBlur?
Click to expand...
Click to collapse
When i go to the phone options i have now these selection:
- Silent Mode
- Airplane Mode
- Power off
- Reboot
Yes, i think it is a GingerBlur mod. But it doesn't bother me, it is a good feature.
meloy said:
When i go to the phone options i have now these selection:
- Silent Mode
- Airplane Mode
- Power off
- Reboot
Yes, i think it is a GingerBlur mod. But it doesn't bother me, it is a good feature.
Click to expand...
Click to collapse
Interesting, that never occurred to me. I usually go into terminal and type in reboot to reboot my phone. I think I'll add that to my phone too...
maledyris said:
Haha, that's good. Had me scared for a moment, I didn't want to break anyone's phone!
Thanks for the tip, I'll mention that in the original post. Oh, and what do you mean by the reboot function...? Where did you access that? I certainly didn't add it, so it might be a mod added to GingerBlur?
Click to expand...
Click to collapse
the reboot function is cooked into GingerBlur. for some reason my phone wouldnt boot after i replaced the file? i used root explorer and set the permissions to whats specified.
n1ckr0th said:
the reboot function is cooked into GingerBlur. for some reason my phone wouldnt boot after i replaced the file? i used root explorer and set the permissions to whats specified.
Click to expand...
Click to collapse
Hmm, how far does it get? Do you at least get to the boot animation? I notice that it may sit at the boot animation for a really long time after changing a file sometimes. Probably updating the cache or something. It's odd that it wouldn't work for you considering it's your file and it worked for meloy. How did you copy the file over?
If you try again, delete the original file, so you can be sure it's no longer there, then try the copy again.
I'm on AT&T 1.8.3. I followed instructions just as in OP (yes, including the proper setting of permissions), but I soon found a significant problem. Everytime I held down my power button in order to invoke the power options menu, instead of the menu popping up, my phone just freaked out (the screen quickly FADED to black and the phone rebooted). I did this about four times, and each time it happened exactly the same. So I brought back the original framework file, and now everything works fine.
Any ideas?
I have no problems with this mod. It works all fine.
Been waiting on this mod. Streakvibrations has me missing my notification vibes. Thank you
It gave me a red light on boot, stuck at Motorola logo for infinity. I booted into recovery and reflashed gb 3.5 to fix it. Ill try your idea of deleting it then moving the new one.
Sent from my MB860 using XDA App
EDIT: still didnt boot, had to flash again..
I'm getting the flashing red light and rebooting as well. I can't get into CWM though, going to have to flash a SBF. Only think I can think of is maybe the Dalvik cache needs to be wiped before rebooting?
Edit: I'm on an AT&T phone and used GB to deodex as well.. maybe it's not catching all the files..
lurchbyrep said:
I'm on AT&T 1.8.3. I followed instructions just as in OP (yes, including the proper setting of permissions), but I soon found a significant problem. Everytime I held down my power button in order to invoke the power options menu, instead of the menu popping up, my phone just freaked out (the screen quickly FADED to black and the phone rebooted). I did this about four times, and each time it happened exactly the same. So I brought back the original framework file, and now everything works fine.
Any ideas?
Click to expand...
Click to collapse
Are you on stock 1.83? Now that we know that android.policy.jar has some mods built into it for Gingerblur pseudo rom, the att 1.83 file I posted probably isn't ideal for stock users.
If you're on stock, maybe you could post your android.policy.jar somewhere and pm me the link to download. Then I could put together a pure stock att one when I get home.
Sent from my MB860 using XDA App
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Designed and developed around sino8r's method amongst other knock offs of the same.
See Post 2 for important info on DTR's and my advice on using them. See Post 3 for DTR downloads. See Post 4 for the Instructions and tools you need to make your own DTR!
Click to expand...
Click to collapse
CHANGE LOG:
Code:
[B]15Oct2011:[/B]
Added DTR for CM Nightly 226
[B]11Oct2011:[/B]
Added CM 7.1, Inc GB OTA, Hybrid Speed, Base 3D, Desired Inc and OMGB
[B]29Sep2011:[/B]
Added instructions and files for creating a DTR
Bunker Buster DTR Info
Please note that this method will break Mobile Networks in the settings menu. You will still be able to kill Data with a widget or other method though. There is a supposed fix for this and I'll try to research it and implement an update as soon as I can. Maybe, lol
Click to expand...
Click to collapse
1. What does this do?
This modifies the services.jar file located in system/framework, that allows you to have an un-throttled data access. You don't have to worry about modifying anything yourself.
2. Will this make my Data faster?
In some cases, YES. This has NO effect on actual phone signal. This only takes the throttle off, so you can download, or play games and not have to worry about it hitting a certain peak and lagging from that point on.
3. If I flash this, will it break my phone?
Sort-of. This will cause Force Closes when you try to select Mobile Network in Settings. Thats the only thing you should notice. I'm working on a work around for this. For now you can still kill Data with a widget or any other sort-of alternative way you want to. This should not physically harm your phone though.
4. Will this work on any ROM?
Yes. This is not based off a particular ROM, and can be used with ANY HTC Droid Incredible ROM. ALTHOUGH If you're Dev has made changes to the services.jar file, this could wipe those changes out. If you are unsure, ask your dev. In any case you may send me your services.jar and I will look at it for you.
5. Do I have to be rooted?
Yes. In order to be able to flash this, you are going to need to have root with CWM3.X Recovery. This uses edify scripting.
6. Does this effect data cap?
No, this mod only effects throttling. You may still be charged data cap overage even if your using this mod.
7. My personal favorite: Does it work or is it placebo?
I have used this several times. For me it does seem to work. I do not have internet at my house and so I have to tether with my phone. I use about 4-12GB of Data a month. Netflix, Xbox Live, Roming, music and everything else. While using this my Data moves as normal. Without this mod my Data usually only crawls. So if you ask me Yes it does work.
IMPORTANT ADVICE ON USING A DTR
Through my own personal use of DTR's, I have found that the best time to flash a DTR is right after you do a fresh install of your Rom.
Here is what I normally do:
1. Place my Rom on my SD Card along with my DTR.
2. Reboot into CWM Recovery.
3. Wipe everything that is supposed to be wiped.
4. Flash my Rom.
5. REBOOT THE PHONE.
6. QUICKLY set up my phone.
This part is important!!!
7. Go into Settings/Wireless & networks/Mobile Networks.
8. I usually set my data to always connected and data roaming on. You can do whatever you need to right here. But keep in mind once you flash the DTR you will not be able to access this menu! Thats why its important to do it now!
9. Reboot into CWM Recovery.
10. Flash the DTR and reboot the phone.
Rule of thumb is to do all of this as quickly as possible. The reason why is because as soon as you boot your phone, your phone will start syncing. Its syncing your contacts and other stuff as well. Some of that other stuff also includes where you are on your usage of your data plan. If it detects that you are over limit it will then activate the throttle process. A little more on this. This DTR does not actually REMOVE the throttle per say. It simply removes the files that the phone system uses to BUILD the throttle. Without the needed throttle files the phone won't be able to set up the throttle which in turn means you will be running at full network data speed. Now do you see why this is important to do this quickly?
So basically lets say, if you've been running a Rom for a few days and then you decide to flash a DTR...expecially if you've noticed your data slowing down, it's already to late. You might as well do a FULL wipe and follow my instructions above. Its the only way to regain your full Data speed again.
Hopefully this sheds a little light on how the phone side throttle works as well as the DTR.
NOTE: As much as I hate to say it, a DTR can never be able to stop a network side throttle. A DTR is only good for stopping the phone side throttle!
Bunker Buster DTR Downloads
-CyanogenMod-
CM 7.1 Download Here
Click to expand...
Click to collapse
CM NIghtly 226 Download Here
Click to expand...
Click to collapse
-Incredible GB OTA based Roms-
Official Incredible GB OTA Download Here
Click to expand...
Click to collapse
-Stang Roms-
Hybrid Speed V7 Download Here
Bass 3D Download Here
Desired Inc HD 3D Download Here
Click to expand...
Click to collapse
-R2DoesInc Roms-
OMGB 1.2.2: Download Here
Click to expand...
Click to collapse
Bunker Buster DTR DIY
Hey guys, I made a complete package of everything you need to make your own DTR's. This one zip that I provide below contains everything that you need for both Windows and Linux. This way you don't have to go looking for everything you need everywhere.
First, download this zip and place it on your Desktop for now:
Bunker_Buster_DTR.zip
Next lets make sure your computer is set up and ready to make the DTR.
Unzip the Bunker_Buster_DTR.zip and have a look at its contents. You should see four folders and one zip file.
The names of the four folders and the one zip file are:
Linux smali 1.2.7
Linux smali 1.2.8
Windows smali 1.2.7
Windows smali 1.2.8
wildstang83_DTR_Flasher.zip
Do you see all of these? Good, lets continue with setting up your computer!
First decide what version you want to use. smali 1.2.7 is obviously older but I've never had an issue with it, so I would recommend using it. The smali 1.2.8 is newer and you shouldn't have issues making a DTR with it, but as a Dev I have personally ran into situations doing other things building Roms where it didn't work properly for me so I had to fall back on 1.2.7. Just tossing that out there...
Obviously if your on Windows you'll want to use the Windows version and visa versa for Linux.
Once you made your choice, open up your C:\ Drive. On Linux you would use your Home folder.
Open the folder of whatever version of smali you will be using. Inside that folder you will see two folders. One called smali and the other called baksmali. Drag those two folders into your C:\ Drive for Windows or home folder for Linux.
There, set up complete. Wasn't that easy?
Your now ready to make DTR's!
Next, find the Rom you want to make a DTR for.
NOTE: I use 7Zip for everything I do so I'll use it for the following instructions. For Linux, the default zip application is fine. It doesn't hurt to have the 7Zip add on for it though
Once you have the Rom just place it on your Desktop. Right click it and choose 7Zip/Open Archive. Linux: Just double click the Rom. I suppose you could do the same in Windows if 7Zip is set as your default .zip program
You will see a folder called system. Open that folder and you will see another folder called framework. Open that folder as well. Look for a file called services.jar. Just simply drag and drop that file to your Desktop. You can go ahead and close that Rom zip.
Now, do the same thing for that services.jar file. Just open archive it and look for a file called classes.dex. Is your C:\ Drive still open? Good! open that baksmali folder. Drag and drop that classes.dex file into the baksmali folder. Do you see that file in the baksmali folder called Decompile? Good, double click that.
NOTE: In the Linux version only, you may have to right click that Decompile file and set the permissions to allow to run as a program!
In the event that my Decompile file isn't working for you, you can manually run these commands;
For Windows:
Code:
cd C:\baksmali [Press the enter/return key]
java -Xmx512M -jar baksmali.jar -o classes/ classes.dex [Press the enter/return key]
For Linux:
Code:
cd ~/baksmali [Press the enter/return key]
java -Xmx512M -jar baksmali.jar -o classes/ classes.dex [Press the enter/return key]
If all has went well, there will be a new folder in the baksmali folder called classes. Open that folder all the way up like this: classes\com\android\server. Inside that server folder scroll all the way down and look for the 7 files that start with Throttle. Delete those 7 files. MAKE SURE YOU ONLY DELETE THOSE SEVEN THROTTLE FILES! Next back all the way out to that baksmali folder again. Now drag that classes folder into the smali folder. This is where we recompile the classes folder into the new classes.dex. So guess what we do now! Thats right, double click that Compile file!
NOTE: In Linux you may have to right click that Compile file and set the permissions to allow to run as a program!
In the event that my Compile file isn't working for you, you can manually run these commands;
For Windows:
Code:
cd C:\smali [Press the enter/return key]
java -Xmx512M -jar smali.jar -o classes.dex classes/ [Press the enter/return key]
For Linux:
Code:
cd ~/smali [Press the enter/return key]
java -Xmx512M -jar smali.jar -o classes.dex classes/ [Press the enter/return key]
If all has went well, there will be a new file in that smali folder called classes.dex. Is your services.jar still open? Cool just drag and drop the new classes.dex into your services.jar, over writing the old classes.dex.
Good job! All the hard stuff is done. Now all that is left to do is get your new throttle remover onto your phone. That's where that super awesome wildstang83_DTR_Flasher.zip comes in. Just open that zip up to system/framework and drop in your new services.jar. Drop that flasher zip on your SD Card, reboot into Clockwork Mod Recovery and flash just like a Rom. Reboot your phone when that's done. Enjoy your new found ability of avoiding that mean throttle!
wildstang83 said:
★BUNKER BUSTER REVERSER★
Coming Soon!
Click to expand...
Click to collapse
Cool thanks, wow did you reset your page? was going to check and see response on a DTR removel to stock and everything is gone.lol
rlacrossjr said:
Cool thanks, wow did you reset your page? was going to check and see response on a DTR removel to stock and everything is gone.lol
Click to expand...
Click to collapse
Yea, I'm trying to get geared up for the dtr removers, so I kinda had to expand. The only way that I could do that was to move to a new thread and capture a couple of replies after so I could.
Once I get my post situated I'll start getting up the removers.
Don't know if this will help you with CM Nightly DTR/removal. I used from this site until I went to gingersense/MIUI. http://driphter.com/index.php?topic=3736.0
Also not to big of a deal but wanted to download your DTR for MIUI, but the way they are listed the XDA app will not let you click and download.
rlacrossjr said:
Don't know if this will help you with CM Nightly DTR/removal. I used from this site until I went to gingersense/MIUI. http://driphter.com/index.php?topic=3736.0
Also not to big of a deal but wanted to download your DTR for MIUI, but the way they are listed the XDA app will not let you click and download.
Click to expand...
Click to collapse
Um... I don't know about that. I just tested it and works for me on xda premium.
Sent from my ADR6300 using XDA Premium App
EDIT: just tested it again. Heres what i had to do to get it to download. Click DOWNLOAD HERE on my thread, it opens the browser, then use the optical joystick to click the link. I couldnt get it to work by pressing it with my finger. Hope that makes since.
Also I am familiar with thebroken. he is one of my inspirations for this project as well.
Must be cause I'm on free version.did hold press oj control nothing
Sent from my ADR6300 using XDA App
rlacrossjr said:
Must be cause I'm on free version.did hold press oj control nothing
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Oh wow it is. I just tested again and in the free version it does block links. That's crazy.
Sent from my Optimized Inc using XDA App
Any chance of getting the latest MIUI DTR out? Going to sit on that update until I can get your patch
Thanks!
grimez said:
Any chance of getting the latest MIUI DTR out? Going to sit on that update until I can get your patch
Thanks!
Click to expand...
Click to collapse
MIUI 1.6.17 is ready!
Hey people, I may be slowing down just a little on ★BUNKER BUSTER DTR★
I'll still be pushing out updates so don't worry though. I'm just picking up on a new project with a friend of mine, newtoroot. If my new project goes well and I'm sure it will... I want to say a HUUUUGE thank you to newtoroot for taking the time to work with me and to break down the instructions I need Barney style, lol. Seriously people, this guy is awesome. The best. Go check his stuff out when you get a chance.
Hey Wild whats going on bro, cant wait to play with your new joint venture!! In the mean time quick question... Does the new Uber kingdom RLS0.5 use the same DTR as all the others or am i going to have to wait for a release of a new one ?
Thanks
o0 DIDDY 0o said:
Hey Wild whats going on bro, cant wait to play with your new joint venture!! In the mean time quick question... Does the new Uber kingdom RLS0.5 use the same DTR as all the others or am i going to have to wait for a release of a new one ?
Thanks
Click to expand...
Click to collapse
Hey Diddy, were still good on uber.
Yea can't wait to see the damn thing boot myself. Working with newtoroot and joelz to get the issues fixed. So I'm sure with there help my new "v i s i o n" will be great. Those guys have been awesome with helping me out so far.
wildstang83 said:
Hey Diddy, were still good on uber.
Yea can't wait to see the damn thing boot myself. Working with newtoroot and joelz to get the issues fixed. So I'm sure with there help my new "v i s i o n" will be great. Those guys have been awesome with helping me out so far.
Click to expand...
Click to collapse
Thats awesome! Its those 2 I keep switching between. Top notch work in my opinion, you couldn't find better teachers. Good luck, let me know if there is anything i can help you out with!
o0 DIDDY 0o said:
Thats awesome! Its those 2 I keep switching between. Top notch work in my opinion, you couldn't find better teachers. Good luck, let me know if there is anything i can help you out with!
Click to expand...
Click to collapse
Might let you test if you want. I finally got boot this morning at 1:47am. I have a couple more issues to get worked out before that though.
wildstang83 said:
Might let you test if you want. I finally got boot this morning at 1:47am. I have a couple more issues to get worked out before that though.
Click to expand...
Click to collapse
Yea, no problem. I could give it a test drive for ya and report back any issues i may encounter. lmk
SkyRaider4.1 added!
Upgraded to 1.6.17 last night, I'll upgrade this tonight.
Hi,
When I got my Droid, I couldn't believe all the stuff that came preinstalled with the phone, so I started deleting everything that seemed unnecessary. Given the fact that I already reflashed the phone 20 times in the last week, I made a little script to help me out. I thought I would share it with you in case it comes handy to someone.
BIG NOTE 0: There's a system part that Motorola uses to get stuff from your phone. It's called Data Collector. Whenever any app crashes, it makes quite a big dump, with your network carrier, signal level, applications installed, applications running and a lot of stuff that isn't opt-in. In fact, one of the scripts (/system/bin/bugtogo.sh) can take screenshots of your phone. I don't like being spied, so I tried to remove it all. Cannot be certain though, but I would recommend you to remove, if you like your privacy, at least, the DataCollector apks, and to empty the bugtogo.sh script from /system/bin
BIG NOTE 1: I don't use this phone in the US, so I don't know if I'm breaking part of the CDMA support. It still shows up in every settings and I don't have any reason to think it won't work, but since I can't test it in anything except GSM/UMTS, I can't know it for sure.
BIG NOTE 2: The script will install Apollo (Music Player), Nova Launcher (homescreen replacement), and Cyanogenmod's Gallery app. If you don't want them and want to keep Blur and the default gallery (the script doesn't remove the music player just in case it's needed by some other app), then don't use this script, or modify it as you wish.
BIG NOTE 3: I am not responsible for anything if this causes a mess. Worst case scenario you'll need to flash back the system partition (fastboot flash system system.img), and then reroot your phone. You have been warned.
This is what it removes:
Code:
/system/app/DataCollection.apk
/system/app/DataCollection.odex
/system/app/DataCollectorProvider.apk
/system/app/DataCollectorProvider.odex
/system/app/DataCollectorService.apk
/system/app/DataCollectorService.odex
/system/app/blur-services.apk
/system/app/blur-services.odex
/system/app/blur_facebook.apk
/system/app/blur_facebook.odex
/system/app/blur_flickr.apk
/system/app/blur_flickr.odex
/system/app/blur_kaixin001.apk
/system/app/blur_kaixin001.odex
/system/app/blur_lastfm.apk
/system/app/blur_lastfm.odex
/system/app/blur_orkut.apk
/system/app/blur_orkut.odex
/system/app/blur_photobucket.apk
/system/app/blur_photobucket.odex
/system/app/blur_picasa.apk
/system/app/blur_picasa.odex
/system/app/blur_youtube.apk
/system/app/blur_youtube.odex
/system/app/vzw_vnav_DROID4.apk
/system/app/vzwapnpermission.apk
/system/app/MyVerizon.apk
/system/app/VerizonSSOEngine.apk
/system/app/MotoVzwAtCmdPlugin.apk
/system/app/MotoVzwAtCmdPlugin.odex
/system/app/VzwController.apk
/system/app/VzwController.odex
/system/app/VzwDeviceSetup.apk
/system/app/VzwDeviceSetup.odex
/system/app/VzwEntitlementService.apk
/system/app/VzwEntitlementService.odex
/system/app/VzwPhoneService.apk
/system/app/VzwPhoneService.odex
/system/app/VCast.apk
/system/app/VCastStub.apk
/system/app/VCastTones.apk
/system/app/VCASTVideo.apk
/system/app/VmmGallery.apk
/system/app/com.motorola.android.server.ims.apk
/system/app/com.motorola.android.server.ims.odex
/system/app/com.motorola.android.settings.aplogd.apk
/system/app/com.motorola.android.settings.aplogd.odex
/system/app/VmmBackupManager.apk
/system/app/VmmBackupManager.odex
/system/app/VmmGallery.odex
/system/app/SmartActionFW.apk
/system/app/SmartActionFW.odex
/system/app/SmartActions.apk
/system/app/SmartCarDock.apk
/system/app/SmartDock.apk
/system/app/ZumoService.odex
/system/app/ZumoService.apk
/system/app/WelcomeWebtop.odex
/system/app/WelcomeWebtop.apk
/system/app/WeatherWidget.apk
/system/app/VZWInstaller.apk
/system/app/Vvm.odex
/system/app/Vvm.apk
/system/app/VSuiteApp.apk
/system/app/VRDClient.apk
/system/app/VMMServiceInterface.odex
/system/app/VMMServiceInterface.apk
/system/app/VideoSurf.apk
/system/app/Videos.apk
/system/app/VideoCalling.apk
/system/app/Swype.apk
/system/app/SocialShare.odex
/system/app/SlingBox.apk
/system/app/SocialShare.apk
/system/app/SlackerRadio.apk
/system/app/RichLocationVzW.apk
/system/app/Protips.odex
/system/app/Protips.apk
/system/app/PlusOne.apk
/system/app/PhotoEditor.odex
/system/app/PhotoEditor.apk
/system/app/OnlineAlbum.odex
/system/app/OnlineAlbum.apk
/system/app/NflMobile.apk
/system/app/Netflix.apk
/system/app/MusicStore.apk
/system/app/MotorolaAccountSetup.apk
/system/app/MotorolaAccountSetup.odex
/system/app/MotoEmailConfig.apk
/system/app/MotoDockHelperService.odex
/system/app/MotoDockHelperService.apk
/system/app/MotoConnect.odex
/system/app/MotoConnect.apk
/system/app/MotoCastDashboard.odex
/system/app/MotoCastDashboard.apk
/system/app/motoactv.apk
/system/app/MotMusic.apk
/system/app/MotGallery.apk
/system/app/MCDownloadManager.odex
/system/app/MCDownloadManager.apk
/system/app/Kindle.apk
/system/app/JunosPulsePlaceholder.apk
/system/app/IlsVzW.apk
/system/app/HuxVmmSetting.odex
/system/app/HuxVmmSetting.apk
/system/app/HuxSnCClient.odex
/system/app/HuxSnCClient.apk
/system/app/GuidedTours.apk
/system/app/GuidedTours.odex
/system/app/HelpCenter.apk
/system/app/FileManager.apk
/system/app/FileManager.odex
/system/app/Facebook.apk
/system/app/DockService.odex
/system/app/DockService.apk
/system/app/DlnaSystemService.odex
/system/app/DlnaSystemService.apk
/system/app/DLNA.odex
/system/app/DLNA.apk
/system/app/DemoMode.odex
/system/app/DemoMode.apk
/system/app/ContactIce.odex
/system/app/ContactIce.apk
/system/app/Cmas.odex
/system/app/Cmas.apk
/system/app/BuaContactAdapter.odex
/system/app/BuaContactAdapter.apk
/system/app/BlurUpdater_VZW.odex
/system/app/BlurUpdater_VZW.apk
/system/app/BlurChooser.odex
/system/app/BlurChooser.apk
/system/app/BackupRestoreConfirmation.odex
/system/app/BackupRestoreConfirmation.apk
/system/app/BackupAssistanceClient.odex
/system/app/BackupAssistanceClient.apk
/system/app/ArcVideoEditorLite.apk
/system/app/android-syncservice-app.apk
/system/app/OutOfBox.odex
/system/app/OutOfBox.apk
/system/app/FriendFeed.apk
/system/app/FriendFeed.odex
/system/framework/com.motorola.MCDownloadLibrary.services_lib.jar
/system/framework/com.motorola.MCDownloadLibrary.services_lib.odex
/system/framework/com.motorola.motoconnect_lib.jar
/system/framework/com.motorola.motoconnect_lib.odex
/system/framework/com.motorola.vzw.vmm.helper.jar
/system/framework/com.motorola.vzw.vmm.helper.odex
/system/framework/com.motorola.vzw.vmm.util.jar
/system/framework/com.motorola.vzw.vmm.util.odex
/system/framework/com.scalado.android.photoeditor.jar
/system/framework/com.scalado.caps.jar
/system/framework/com.verizon.phone.jar
/system/framework/com.verizon.phone.odex
/system/framework/com.vzw.android.gex.jar
/system/framework/com.vzw.android.gex.odex
/system/framework/com.vzw.android.hux.jar
/system/framework/com.vzw.android.hux.odex
/system/framework/com.vzw.android.jar
/system/framework/com.vzw.android.odex
/system/framework/com.vzw.android.smart.jar
/system/framework/com.vzw.android.smart.odex
Instructions:
1. Root your phone if you haven't already
2. Install Busybox from Google Play if you haven't already
2. Uncompress the zip into your internal sdcard. You should get this:
Code:
/sdcard/removecrap/Apollo.apk
/sdcard/removecrap/Gallery2.apk
/sdcard/removecrap/com.teslacoilsw.launcher-1.apk
/sdcard/removecrap/remover.sh
3. Run from a terminal on the phone, or from adb (always as root)
sh /sdcard/removecrap/remover.sh
4. Wait until the phone reboots
5. 200 extra Mb of system and a lot more free ram for your apps. Oh, and Motorola won't get another bug report from you
EDIT: Ooops, Reupdated the zip file, it was deleting one extra file (motosignature inside the framework folder)
EDIT2: Didn't catch Carrier IQ's qer binary on /xbin. Unfortunately we can't touch those binaries since they're in the randisk, so I updated the script so it removes the logfile qe generates and replaces it with a folder so it can never write the scan results again (thank you bofh.bug for the links!)
That's great, but you'll probably have trouble installing whatever official update comes next, since the updates generally expect certain apps to exist (with correct checksums too) so that they can be updated.
Sent from my DROID4 using Tapatalk
highlandsun said:
That's great, but you'll probably have trouble installing whatever official update comes next, since the updates generally expect certain apps to exist (with correct checksums too) so that they can be updated.
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
Probably OTAs will fail after running the script, but fixing it is as easy as reinstalling the system partition with fastboot and then applying the OTA
Sent from my DROID4 using xda app-developers app
This does disable all data connectivity (3G/4G) for CDMA users, you can still receive texts and calls, but will not be able to get data services.
When I have time I will make update this script to work with CDMA users.
arleslie said:
This does disable all data connectivity (3G/4G) for CDMA users, you can still receive texts and calls, but will not be able to get data services.
When I have time I will make update this script to work with CDMA users.
Click to expand...
Click to collapse
Were you able to fix the script so it works for CDMA users? Or, do you know what apps breaks it?
Very nice script, thanks. Easy way to run it by using Root Browser: open as script. But as for me QuickPick is better than ICS Galerry
Sent from my DROID4 using xda app-developers app
Hi biktor_gj , could you make a similar script for Android 4.1.2? Very grateful in advance
Tanzior said:
Hi biktor_gj , could you make a similar script for Android 4.1.2? Very grateful in advance
Click to expand...
Click to collapse
I did again the script for the jelly bean update. This time it removes less crap, since it seems Motorola left a bit less than on previous versions. This will remove the annoying "Foreign card" warning when you boot the phone with some non-verizon sim, the acoustic warning when you turn up the volume, smart actions and so on.
IT WON'T REMOVE THE APPS. It will leave them here:
Apps: /system/app/oldapps
system binaries: /system/bin/oldbin
Framework: /system/framework/oldframework
If you encounter any problem, you can simply move back the files through adb and the phone will be like before applying the script.
NOTE: Only tested on GSM. Probably won't work on CMDA since it's missing most of the Verizon stuff. If you can identify which apps are needed for CDMA to wokr again tell me and I'll update the script accordingly.
I run the script from ADB and worked like a charm. Been using it for 24hours and no problems so far, but you never know, so use at your own risk
Code:
[email protected]:~/Documents# adb push removecrap2.sh /sdcard/removecrap2.sh
[email protected]:~/Documents# adb shell
[email protected]_maserati:/ $ su
[email protected]_maserati:/ # sh /sdcard/removecrap2.sh
It works great, thank you. Good work.
Sent from my DROID4 using xda app-developers app
Hi to all, i found two app : ModemPanicReporter.apk and ModemStatsService.apk. What they are doing ? Maybe it is necessary to remove they too ? Removing these applications will improve battery life.
Sent from my DROID4 using xda app-developers app
i have tired the security bypass in xposed but it didnt work. does anyone know of one that does work. im on an att x
looking for this as well
Interested in this also. Anybody found anything?
It will probably take some time before someone takes the securities out of the stock app. Until then you can use a 3rd party mail app from the market like MailDroid to access your exchange email without a screen lock.
We are working on the same thing over here...
http://forum.xda-developers.com/showthread.php?p=45776460#post45776460
A Dev just posted some instructions for one of the guys who says he partially knew how to do it. So we shall see if anything comes of it.
Ya I edited my last email app similar to those instructions and just replace the security check with 1 or 0 or whatever it was that made it think it ran the check already. If I get bored I'll work on the Verizon apk this weekend. I haven't touched the stuff in a while so I might not but I'll post the apk if I get around to it. Drinking can inhibit the process though.
Edit: if someone is already doing it and I just missed that info let me know in the chance I do decide to do it this weekend.
Sent from my XT1060 using xda app-developers app
verizon moto x
I am currently working on the email.apk. there is also the exchange2.apk that i believe will need to be edited as well.
When I edited the email apk a couple of years ago I just went to these lines and returned true and false. These lines check to see if the policies are enabled I believe.
Code:
.method public isActive(Lcom/android/emailcommon/provider/Policy;)Z
.registers 1
.parameter "policy"
.prologue
const/4 v0, 0x1
return v0
.end method
.method public isActiveAdmin()Z
.registers 1
.prologue
const/4 v0, 0x0
return v0
.end method
I then tried to recompile it and i got an error stating that two registers were required for one of the two changes. I haven't looked at which line yet because I know I don't know enough to figure out why it needs to registers. Here is the error.
Code:
c:\MotoX>java -Xmx512M -jar smali.jar out -o classes.dex
out\com\android\email\SecurityPolicy.smali[1659,4] This method requires at least
2 registers, for the method parameters
so this is where i am and this is what im stuck on. Ill attach the entire smali file so anyone that can help can take a look at the entire code. Ill also attach the security admin smali in case that matters.
Ill also begin working on the exchange apk, but this apk didn't exist the last time i did this so I'm not sure what I'm going to do with it. Like I said, Im not good at this stuff I just really want an exchange security bypass for my Moto X.
i have been messing with that ExchangeNoPIN-v6.0 found in here
i am have a dev edition, rooted, on the 4.4.4 ota. i believe on 4.4.2 i had it working simply by flashing the zip on twrp but this was not the case with 4.4.4. i tried a bunch of different things by trial and error... eventually what i ended up doing the following get this to work (not sure which step was the key).
you have to make sure to clear data and cache in both email and exchange service apps first
i copied email.apk and exchange2.apk from the zip in the aforementioned thread into my phone.
interesting bit on 4.4.4 is that email.apk is in /system/priv-app and exchange2.apk is in /system/app
i took manually copied both apks into /system/app and /system/priv-app using root explorer, and set 0644 permissions for each, rebooted, didnt work, so then i simply manually installed both of them by clicking on the apks (from the original directory, before they were copied to the system folders). this installed them as an "update."
after I did this, everything was working.
Use a program Nine is is an awesome Exchange client and has either device or application support. Keeps me from locking down my device with the stock exchange client.
Sent from my XT1053 using Tapatalk
Simple question. I want to start my own service from my package with the same permissions as the package i am hooking. Does anybody know how i could do this? I know if i use android:sharedUserId="android.uid.systemui" in the manifest, but it prevents it based off of signature mismatch. Could i use xposed to grant my app the sharedUserId?
Simple question. I want to start my own service from my package with the same permissions as the package i am hooking.
Click to expand...
Click to collapse
I don't think that is possible. I haven't worked with services yet, but as far as I understood, you have to declare them in your manifest (in contrast to BroadcastReceivers, which can also be registered at runtime). Theoretically again, you could try to modify the manifest parsing and try to inject additional entries there.
elesbb said:
Could i use xposed to grant my app the sharedUserId?
Click to expand...
Click to collapse
Theoretically, I think yes, you could hook the package manager to ignore the signature mismatch etc. But I think it will be quite fragile.
What do you want to achieve with this?
rovo89 said:
I don't think that is possible. I haven't worked with services yet, but as far as I understood, you have to declare them in your manifest (in contrast to BroadcastReceivers, which can also be registered at runtime). Theoretically again, you could try to modify the manifest parsing and try to inject additional entries there.
Theoretically, I think yes, you could hook the package manager to ignore the signature mismatch etc. But I think it will be quite fragile.
What do you want to achieve with this?
Click to expand...
Click to collapse
I hate how Samsung removed widgets from the lockscreen. So i figured i'll create my own lockscreen and have it loaded by the system. I might just skip the whole service thing (which would make my lockscreen easier to write by having classes that extend things like FrameLayout as the stock lockscreen does) but i found where the lockscreen is actually shown. i may just inflate my own xml of the lockscreen using xposed resources and then adding it with windowmanager. Then the inflated view will follow the same permissions as the stock lockscreen and allow me to handle key presses and still preserve the security behind it.
Thanks rovo for the reply!
@rovo89
If i am inflating my own view inside a hooked method, how can i get the ids of my layout? I tried XModuleResources myRes; myRes.getIdentifier() but it returned null.
Be careful, Resources.getIdentifier() expects the arguments in a different order than Xposed, like getIdentifier("mystring", "string", "my.package.name").
Apart from that, simply use R.layout.my_layout.