How to Disable Carrier IQ - General Questions and Answers

Hi Androider’s,
If Carrier IQ has bothered you like it bugged the heck out of me, I have a solution for you. This is not for new users to try. I may try and create an app for this!
1) Create a text file (ciq-off) on your Linux system using the provided code. Windows users should use Notepad++ .(Can’t have any pesky carriage return/line feeds in the file)
2) Use “adb push” to store it on your SD card of your phone. (If you don’t know what adb is, you should have someone help you.)
3) Give the file execute permissions then run the file. ( chmod 644 ciq-off)
4) Your phone should reboot and Carrier IQ will be disabled not to return, even after reboot. (Note: Your carrier can remotely start the app.)
In the future posting, I will attempt to remove the .so files that allows execution. This is a complicated process and the research seems to stretch far and wide at times. However, with enough people using their minds on this issue Carrier IQ will be defeated someday.
[ciq-off script]
HTML:
# Mount Filesytem Read/Write
grep " /system " /proc/mounts | awk '{system("mount -o rw,remount -t "$3" "$1" "$2)}'
#
# Enable Write to goldfish script
chmod 777 /system/etc/init.goldfish.sh
#
# Create append string for startup script
str=$(cat <<EOF
# Carrier IQ Disabler v1.0
su -c "setprop service.iq.active 0"
su -c "pm disable android/com.carrieriq.iqagent.service.IQService"
su -c "pm disable android/com.carrieriq.iqagent.service.receivers.BootCompletedReceiver"
su -c "pm disable android/com.carrieriq.iqagent.service.ui.DebugSettings"
su -c "pm disable android/com.carrieriq.iqagent.service.ui.ShowMessage"
su -c "pm disable android/com.carrieriq.iqagent.client.NativeClient"
su -c "pm disable android/com.carrieriq.iqagent.stdmetrics.survey.android.QuestionnaireLaunchActivity"
su -c "pm disable android/com.carrieriq.iqagent.stdmetrics.survey.android.QuestionnaireActivity"
EOF
)#
# Return script previous permissions
chmod 550 /system/etc/init.goldfish.sh
#
# Reboot Phone
reboot
References:
http://forum.xda-developers.com/showthread.php?t=1373394
http://android-tricks.blogspot.com/2009/01/mount-filesystem-read-write.html
Users:
dmanbuhnik
JoshMiers

Related

[TOOL] ModYourROM LITE (remove bloat & add apps after flashing)

Hey! ^_^
I made a script to remove the bloat from ROMs, add some script functionality and replace some system APKs. It's simple, but really powerful. I use it everytime I get a new ROM because I like plain stock ROMs, with only the system apps. I dunno, I just like it that way .
So, here it is, ModYourROM LITE! ^^!. It’s intended to be used AFTER A ROM FLASH, INSIDE RECOVERY, AND BEFORE THE FIRST BOOT, but it can run afterwards with no issues, I guess.
ROM Compatibility? for now, it’s been tested only with GingerYoshi 1.1 and 1.2 (awesome ROM by the way ).
Now…
Very Important Notes, or V.I.N. for short. Yeah, like Vin Diesel, only that he’ll come and punch you right in your face if you don’t read AND follow them =P.
You need to have ADB in your PATH variable, or edit the script accordingly (!!!).
This script is made for Linux. If you’re on Windows, replace "#" by "REM" and remove the first line of the script.
Don’t just bluntly run it. READ what the script does before running it. It’s common-linux-sense.
You need to have busybox run-parts on your ROM for the startup-scripts functionality. GingerYoshi has it, I don't know which other ROMs have it. It's only needed if you want the startup scripts though.
This script creates a folder called “bak” in your SD card, in case you want to redo the changes. Be sure to have it inserted on the phone before running the script.
Last but not least: I’m not responsible if this breaks your phone, ROM, flying toaster or BORGizes your phone and assimilates you. This script has been working on my phone & setup without much modifications other than adding/removing a few APKs or scripts, so this is the only guarantee I give you. It hasn’t broken mine, but YDMV (Your Device May Vary). Still, you can PM me or post here and I'll try to help you fix something this script has made. However, I'm no expert so I may - or may not - fix what this script did on your phone.
Now, let’s get our hands dirty:
Create a folder somewhere (ie Destkop). I’ll call it “myr“.
Add your custom APKs into myr/apks. Rename them if needed so they have simple names with no spaces. Stuff like foo.bar.boo.hoo.apk sucks =P.
Add your startup scripts (if any) into myr/scripts (you can find some at the bottom of this post).
Add your boot animation replacement (if any) into myr/boot.
Add the latest busybox for ARM5 (in the case of HTC Magic, busybox-armv5l) into myr/busybox. You can find it HERE. Rename it as busy1184, WITH NO EXTENSION.
Put the following scripts in your myr folder:
myrLITE.sh
Code:
#!/bin/sh
# ================================================================================================================
# ModYourROM LITE v1.1 by DARKGuy (dark DOT guy DOT 2008 AT gmail DOT com)
# 6th Jun 2011
#
# WINDOWS USER: Replace # by REM and delete the first line. Be sure to have adb in your PATH environment variable.
# ================================================================================================================
# =====================================================================
# DO NOT REMOVE THIS ADB SEGMENT
# =====================================================================
echo "Mounting..."
adb -d shell mount /data
adb -d shell mount /system
adb -d shell mount /sdcard
adb -d shell mount /sd-ext
adb -d shell mkdir /sdcard/bak
# =====================================================================
# Remove this segment if you don't want to update busybox
# =====================================================================
adb -d push busybox/busybox1184 /sdcard/busy1184
adb -d shell dd if=/sdcard/busy1184 of=/system/bin/busybox
adb -d shell chmod 755 /system/bin/busybox
adb -d shell /system/bin/busybox --install /system/xbin
adb -d shell rm /sdcard/busy1184
# =====================================================================
# Remove these two segments if you don't want/have any startup scripts
# =====================================================================
echo "Adding startup script functionality..."
adb -d shell mkdir /data/local/scripts
adb -d push 90scripts.sh /system/etc/init.d/90scripts
adb -d shell chmod 0750 /system/etc/init.d/90scripts
adb -d shell chown 0:2000 /system/etc/init.d/90scripts
echo "Adding startup scripts..."
adb -d push scripts/noatime.sh /data/local/scripts/noatime.sh
adb -d push scripts/autokiller.sh /data/local/scripts/autokiller.sh
adb -d push scripts/non-rotational.sh /data/local/scripts/non-rotational.sh
adb -d shell chmod +x /data/local/scripts/noatime.sh
adb -d shell chmod +x /data/local/scripts/autokiller.sh
adb -d shell chmod +x /data/local/scripts/non-rotational.sh
# =====================================================================
# Take a look at what apps does this segment remove and delete the
# lines of apps you want to KEEP on your device.
# =====================================================================
echo "Removing apps..."
# Safe to remove
adb -d shell mv /system/app/Protips.apk /sdcard/bak
adb -d shell mv /system/app/PicoTts.apk /sdcard/bak
adb -d shell mv /system/app/TtsService.apk /sdcard/bak
adb -d shell mv /system/app/VoiceDialer.apk /sdcard/bak
adb -d shell mv /system/app/GoogleBackupTransport.apk /sdcard/bak
adb -d shell mv /system/app/GoogleFeedback.apk /sdcard/bak
adb -d shell mv /system/app/GooglePartnerSetup.apk /sdcard/bak
adb -d shell mv /system/app/OneTimeInitializer.apk /sdcard/bak
adb -d shell mv /system/app/ApplicationsProvider.apk /sdcard/bak
adb -d shell mv /system/app/Development.apk /sdcard/bak
adb -d shell mv /system/app/Stk.apk /sdcard/bak
# Bloat
adb -d shell mv /data/app/YouTube.apk /sdcard/bak
adb -d shell mv /data/app/DSPManager.apk /sdcard/bak
adb -d shell mv /system/app/Maxthon.apk /sdcard/bak
adb -d shell mv /system/app/GoogleQuickSearchBox.apk /sdcard/bak
adb -d shell mv /system/app/ThemeChooser.apk /sdcard/bak
adb -d shell mv /system/app/ThemeManager.apk /sdcard/bak
adb -d shell mv /system/app/lindamanager.apk /sdcard/bak
# Core app (I don't use GTalk. Delete if you do).
adb -d shell mv /system/app/Talk.apk /sdcard/bak
# Core app (I don't use the News Reader. Delete if you do).
adb -d shell mv /system/app/GenieWidget.apk /sdcard/bak
# Core app (I don't use the Email app. Delete if you do).
adb -d shell mv /system/app/Email.apk /sdcard/bak
# To be replaced afterwards (READ NOTE IN NEXT SEGMENT)
adb -d shell mv /system/app/DeskClock.apk /sdcard/bak
adb -d shell mv /system/app/Gallery3D.apk /sdcard/bak
# Remove launchers, so we add our own later (READ NOTE IN NEXT SEGMENT)
adb -d shell mv /system/app/Launcher2.apk /sdcard/bak
adb -d shell mv /system/app/ZeamLauncher.apk /sdcard/bak
# =====================================================================
# Remove this segment if you don't want/have any bootanimation.zip
# =====================================================================
echo "Changing boot animation..."
adb -d shell rm -f /system/media/bootanimation.zip
adb -d push boot/bootanimation.zip /system/media/bootanimation.zip
# =====================================================================
# Remove this segment if you don't want/have any replacement apps.
#
# BE SURE TO HAVE A REPLACEMENT APP HERE IN CASE YOU REMOVE CORE APPS,
# like the Clock, News Reader (GenieWidget), Email, Launcher and Gallery3D (which are
# removed above if you didn't look carefully enough - and as for Gallery, I replace it with a
# faster, maybe-not-so-eyecandy-er 2D one).
# =====================================================================
echo "Adding replacement apps..."
adb -d push apks/AlarmClockPlus.apk /system/app/AlarmClockPlus.apk
adb -d push apks/Gallery.apk /system/app/Gallery.apk
adb -d push apks/LauncherPro.apk /system/app/LauncherPro.apk
# =====================================================================
# Don't delete this, it's safe to keep it. Your next boot will be a bit
# slower because it's regenerating the odex files.
# =====================================================================
echo "Cleaning dalvik-cache..."
adb -d shell rm -f /data/dalvik-cache/*
adb -d shell rm -f /sd-ext/dalvik-cache/*
adb -d shell busybox sync
echo "."
echo "Done! Enjoy your new LITE ROM :)"
echo "Script by DARKGuy"
echo "http://www.drakkengard.com/blog/"
echo "."
90scripts
Code:
#!/system/bin/sh
sList=`ls /data/local/scripts/*.sh`
for myScript in $sList
do
sh $myScript
done
Now, EDIT ACCORDINGLY BEFORE RUNNING the myrLITE script.
You should end up with something like this:
{
"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"
}
Now, if you’re on Linux, run this first:
Code:
chmod +x myrLITE.sh
Then run the script:
Code:
./myrLITE.sh
If you’re on Windows, just name it myrLITE.bat and run it from a command prompt.
Now just plain enjoy your new LITE’d ROM .
Credits and references:
* GingerYoshi by Yoshi Team ( here ).
* SD Tweakz by Ungaze ( here and here ).
* Some theory on removing some APKs and autokiller script by tom0769 ( here ).
* Barebones CM Wiki page by CyanogenMod ( here ).
Comments & suggestions welcome!
If you like my work and want to motivate me to keep working on this (and more stuff for the community) make a donation! any amount is greatly appreciated
=========
CHANGELOG
=========
1.2 (09/06/11)
* Removed the annoying beginner's tips widget
1.1 (06/06/11)
* Added busybox updating
* Added Email.apk and GenieWidget.apk to the core app APK removing section.
* Fixed 90scripts.sh
1.0 (05/25/11)
* Initial release
Great! very usefull
I would also like to find some lightweight replacemments for some apps:
gtalk
- gibberbot (gtalk mod with encryption)
- imo (multiprotocol)
...
Skype
- fring (this can also replace message, phone calling and contacts apps?)
- Sipdroid
- Linphone
- Redphone (has encryption but it is not opensource?)
...
gmail
- K-9 + APG Seems faster and has more features, but I am not sure why it has to be running all the time. I would preffer to open it and check when I want to. Is it me or gmail seems more lightweight in resources?
Maps
- Can we get rid of them working all the time?
devrruti said:
Great! very usefull
I would also like to find some lightweight replacemments for some apps:
gtalk
- gibberbot (gtalk mod with encryption)
- imo (multiprotocol)
...
Skype
- fring (this can also replace message, phone calling and contacts apps?)
- Sipdroid
- Linphone
- Redphone (has encryption but it is not opensource?)
...
gmail
- K-9 + APG Seems faster and has more features, but I am not sure why it has to be running all the time. I would preffer to open it and check when I want to. Is it me or gmail seems more lightweight in resources?
Maps
- Can we get rid of them working all the time?
Click to expand...
Click to collapse
Thanks! glad you like it
Well, for GTalk I've been using eBuddy, and so far it's the best one out there .
I don't use voice calls Skype-style, so I don't know which one to use... Fring seems like a good alternative. I tried to use it as a replacement for eBuddy but I kept going back to it, so its only use (to me) would be a Skype replacement app :/
You may be right about GMail being more lightweight than K-9. I've been testing K-9 for a while now and while I haven't tested it through, it seems waaaaaay faster . I also found this little app which claims to stop the data sync, so it kinda does what you need?
https://market.android.com/details?id=org.r3pek.k9datakiller
Thanks for the feedback =) this little script will keep improving, so stay tuned! ^^.
Hey, great work!
Will try this next week to setup a gb rom (don't know which actually)
I'm quite content with laszlo's froyo the last weeks.
Just out of curiosity (don't want to miss maybe something great new) I'll try ezGingerbread, COS-DS or Yoshi's.
tom0769 said:
Hey, great work!
Will try this next week to setup a gb rom (don't know which actually)
I'm quite content with laszlo's froyo the last weeks.
Just out of curiosity (don't want to miss maybe something great new) I'll try ezGingerbread, COS-DS or Yoshi's.
Click to expand...
Click to collapse
^_^ Thanks! did you try it with the ROMs?
I just updated the script to 1.1 ^^ to comply with GY 1.2 update
greate work , going to try this in the evening when i have some time !

What is wrong with my script - going crazy

so I'm new to scripting, and I have a TON of lg optimus S's to root for work. So I figured I'd write a script to make life easy. I know all the shell commands are correct as if I manually type everything in it works. What happens is it gets through gingerbreak exploit and when the prompt returns # - everything seems to go to hell.
Here is my script I am using. I'm using Kubuntu 11.04 writing it in Kate, name of my script is Script2 and I'm executing it in bash via $sh Script2
echo "removing TMP directory";adb shell rm -r /data/local/tmp
echo "creating TMP directory";adb shell mkdir /data/local/tmp
echo "pushing gingerbreak";adb push gingerbreak /data/local/tmp/gingerbreak
echo "CD TMP";adb shell cd /data/local/tmp
echo "CHMOD TMP";adb shell chmod 777 /data/local/tmp/*
echo "running gingerbreak";adb shell /data/local/tmp/gingerbreak &
sleep 32
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
adb shell cat /sdcard/flash_image > /system/bin/flash_image
adb shell chmod 755 /system/bin/flash_image
adb shell mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
adb shell flash_image recovery /sdcard/xionia_cwma_12518.6.img
adb shell reboot recovery
I've tried with out sleep command and also with out "&" at the end of gingerbreak, and when I do that and it returns # it seems like no commands will work, even if I type them in it returns just a blank line with out #.
With that current script after sleep 32, it returns #, few seconds later it tries to mount and I get (including the end of gingerbreak exploit).
[!] dance forever my only one
# mount: Operation not permitted
Script2: 9: cannot create /system/bin/flash_image: Directory nonexistent
Unable to chmod /system/bin/flash_image Read-only file system
mount -o: permission denied
reboot: Operation not permitted
then it returns me to bash$
Thanks!
So something interesting, I've been playing with this for awhile, and I took everything out past the
adb shell /data/local/tmp/gingerbreak
it seems if I run it as
bash$ adb shell /data/local/tmp/gingerbreak
vs
bash$ adb shell
$ cd /data/local/tmp
$ ./gingerbreak
when # is returned, the first option won't take any commands its like it hangs, if I type out the next command it will just return a blank line with out $ or #, I have to forcibly end the process by CTRL+C and it will return me to bash, if I do the second option it works and I can enter the next command in and it takes and returns me to #. Anyone know why this is? I'm pretty sure this is the problem.
I would happily use the second option, but I'm not sure how to get the script to take any android shell commands without a "adb shell" infront. If anyone knows how to get around this, that would be awesome =)

[Q] Disable proximity sensor via terminal emulator

Hi @ all,
I have that following problem: My phones display turns off automatically while im receiving or doing a call. My proximity sensor is broken and i would like disable it and i found a good solution here in this formus:
http://forum.xda-developers.com/showthread.php?t=925814&page=5
# cd /data/local
# touch userinit.sh
# echo "#!/system/bin/sh" > userinit.sh
# echo "#" >> userinit.sh
# echo "chmod 0000 /dev/cm3602" >> userinit.sh
# echo "chmod 000 /dev/cm3602" >> userinit.sh
# chmod 777 userinit.sh
But there's a little problem. I'm not well in programming - now my question is: can someone cange the code that it fit's to my phone. It's a Desire S with CyanogenMod 10 Beta.
Would be very thankful!
our phone has a /dev/cm3602 as well, so it probably uses the same chip.
note: the following is untested
Code:
cat>/etc/init.d/98-disable-sensor<<EOF
#`which sh`
chmod 000 /dev/cm3602
EOF
run that through adb shell and if your kernel has init.d support it will automatically disable your proximity sensor every boot. disable the sensor for your current session by running a simple 'chmod 000 /dev/cm3602' through adb shell.
THX! I will try it out soon.
Sent from my Desire S using xda app-developers app
I've just figured out that those commands won't work as is -- I stupidly forgot you need to remount system r/w and make the file executable for it to run. This should work (still didn't test it) -- run it all in an adb shell:
Code:
mount -o remount,rw /system
cat>/etc/init.d/98-disable-sensor<<EOF
#!`which sh`
chmod 000 /dev/cm3602
EOF
chmod 755 /etc/init.d/98-disable-sensor
mount -o remount,ro /system
i just tried it out and it says
[email protected]:/ # mount -o remount,rw /system
mount -o remount,rw /system
[email protected]:/ # cat>/etc/init.d/98-disable-sensor<<EOF
cat>/etc/init.d/98-disable-sensor<<EOF
> #!'which sh'
#!'which sh'
> chmod 000 /dev/cm3602
chmod 000 /dev/cm3602
> EOF
EOF
sh: can't create temporary file /sqlite_stmt_journals/mksh.vXIer13043: No such file or directory
but simply 'chmod 000 /dev/cm3602' works fine for one session! thanks!
Ooh, joy, it's that bug in the android shell that I'd forgotten about.
Try this instead:
In an adb shell, run 'which sh'. Note the path it returns.
On your computer, copy the following to a text file named '98-disable-sensor'. Be sure to use an editor (e.g. Notepad++) that can save with LF newline bytes and make sure you tell it to do that! (Under Windows, a newline is marked by the bytes \r\n, which is wrong for Linux - it should be just \n. Save the file as 'Unix text file' or something like that when asked.)
Code:
#!/path/to/sh/you/wrote/down/earlier
chmod 000 /dev/cm3602
Push it to your device: 'adb remount' + 'adb push 98-disable-sensor /etc/init.d/'
Make it executable: 'adb shell chmod 755 /etc/init.d/98-disable-sensor'
Remount system r/o again: 'adb shell mount -o remount,ro /system'
Aquous said:
Ooh, joy, it's that bug in the android shell that I'd forgotten about.
Try this instead:
In an adb shell, run 'which sh'. Note the path it returns.
On your computer, copy the following to a text file named '98-disable-sensor'. Be sure to use an editor (e.g. Notepad++) that can save with LF newline bytes and make sure you tell it to do that! (Under Windows, a newline is marked by the bytes \r\n, which is wrong for Linux - it should be just \n. Save the file as 'Unix text file' or something like that when asked.)
Code:
#!/path/to/sh/you/wrote/down/earlier
chmod 000 /dev/cm3602
Push it to your device: 'adb remount' + 'adb push 98-disable-sensor /etc/init.d/'
Make it executable: 'adb shell chmod 755 /etc/init.d/98-disable-sensor'
Remount system r/o again: 'adb shell mount -o remount,ro /system'
Click to expand...
Click to collapse
Hi
Do you know what is the command to turn off all sensors ?
i want to execute the command when screen is off (by xposed edge)
and turn on again when screen is on
loopypalm said:
Hi
Do you know what is the command to turn off all sensors ?
i want to execute the command when screen is off (by xposed edge)
and turn on again when screen is on
Click to expand...
Click to collapse
I use the below command on low battery trigger via Tasker
Code:
cmd statusbar click-tile com.android.settings/.development.qstile.DevelopmentTiles\$SensorsOff
varunpilankar said:
I use the below command on low battery trigger via Tasker
Code:
cmd statusbar click-tile com.android.settings/.development.qstile.DevelopmentTiles\$SensorsOff
Click to expand...
Click to collapse
Thx but i don't want to use tasker or any extra app
loopypalm said:
Thx but i don't want to use tasker or any extra app
Click to expand...
Click to collapse
Us can use the via adb or shell script event trigger.
varunpilankar said:
Us can use the via adb or shell script event trigger.
Click to expand...
Click to collapse
what is the adb comand ?
loopypalm said:
what is the adb comand ?
Click to expand...
Click to collapse
Code:
adb shell cmd statusbar click-tile com.android.settings/.development.qstile.DevelopmentTiles\$SensorsOff
varunpilankar said:
Code:
adb shell cmd statusbar click-tile com.android.settings/.development.qstile.DevelopmentTiles\$SensorsOff
Click to expand...
Click to collapse
it work on PC but no luck in terminal/xposed edge
Edit : i found a way !
replace "adb shell" with "#!/bin/sh" work
If you have root then you can use Su directly
varunpilankar said:
If you have root then you can use Su directly
Click to expand...
Click to collapse
and the comand is ?
terminal - type
su
cmd statusbar click-tile com.android.settings/.development.qstile.DevelopmentTiles\$SensorsOff

busybox ls --color and many other commands "Working"

have you got bored of your one Text colored terminal ?
when you look at the results you always are confused ?
well .. you came into the right thread
I'm here today to show you how to make every busybox command fully functional
I was trying to make this command work but no success
Code:
#ls --color=always
then i ended up making busybox fully functional
Note: you must have rooted device and custom recovery and SDK tools " incase you don't have adb.rar "and your phone developer mode and USB debugging checked .
go to your SDK tools press sheft and right mouse click and open cmd here
________________________________________________________________________
now .. lets get to it shall we ?
1 - reboot into recovery and connect your device in your PC
2 - type in these commands in your PC command prompt you opened in order :
Code:
# adb shell
# mount system
# cp /system/bin/sh /sdcard/Download/sh
#adb reboot
3 - reboot your device
4 - download this busybox app and start it
jrummy.busybox.installer
5 - you'll see in the app's INSTALLER icon a location /system/xbin
change it to /system/bin
6 - open app's settings "upper right corner beside the three dot's" and check all what's in the installer settings
7 - press back and click install " your phone will boot into recovery and install the busybox "
8 - after finishing the process your device will reboot normally but wait a minute !!! SU is not working anymore :crying:
9 - reboot your device again into recovery !! " I'll try to fix it for you "
10 - type in these commands in order :
Code:
#adb shell
#mount system
#cp /sdcard/Download/sh /system/bin/sh
#chmod 755 /system/bin/sh
#adb reboot
and we are done
look at the attachment below this is how your terminal will look like and error free
I'm sorry about this post
apparently I was kinda mistaken
I think what happens that lead to this is
when you write down the applet's name in terminal the device start to search inside bin file first .. if the applet was not found in bin .
the device will start to search on xbin file and maybe the whole storage for that command
so .. since there are some applets in bin are the same one in busybox and I was able to locate them "took me like an hour to do so"
and these applets are :
Code:
[COLOR="blue"]blkid
brctl
cat
chmod
chown
clear
cmp
cp
date
dd
df
dmesg
du
grep
gzip
hd
id
ifconfig
insmod
ionice
ip
kill
ln
ls
lsmod
lsof
mkdir
mke2fs
mknod
mkswap
mount
mv
netstat
nohup
ping
ping6
printenv
ps
readlink
reboot
renice
rm
rmdir
rmmod
route
sh
sleep
swapoff
swapon
sync
top
touch
tune2fs
umount
uptime[/COLOR]
there are a lot of difference in results between the factory applets and the busybox applets
if you want to see the difference install busybox in /system/xbin and in terminal type one of these applets above like this :
for busybox applets result :
Code:
busybox [I][COLOR="blue"]applet[/COLOR][/I]
for system applets result :
Code:
[I][COLOR="Blue"]applet[/COLOR][/I]
it might not be a new thing but for me it is
I just wanted to share that info for the ones who doesn't know
Edit : there is also one applet in system/xbin which is " nc "
thanks .

[ROOT] [Magisk/Tasker] [Andromeda] Start Andromeda directly on boot from your phone

Hi,
You need to be rooted. Why to use Andromeda if you are rooted, you might wonder. Well, it runs miles better, there is no difference in speed between a themed and a not themed app. With a root Substratum, the difference is quite noticeable, for the worst.
Plus, I used magisk, although it should also be runnable from within Tasker, Auto Tools, or something alike, or simply with /system/etc/init.d support, which my P20 Pro lacks. The init.d injector magisk module didn't work either.
Hence I've modified the official linux adb script to be run at init directly on the phone. Due to the missing init.d support on many phones, like mine, I placed the script on /magisk/.core/service.d since I already had magisk installed
I also
Code:
ln -s /magisk/.core/service.d /system/etc/init.d
to make it easier to remember and have init.d support
The sleep timer might need to be increased, I tried to wait for projekt.substratum to be running but it was not enough, so unless someone can shed light on what other process to wait for, the sleep will do.
So download the script, rename it to start_andromeda-android.sh, and
Code:
adb push start_andromeda-android.sh /magisk/.core/service.d/
adb shell
su
chown 0:0 /magisk/.core/service.d/start_andromeda-android.sh
chmod 0755 /magisk/.core/service.d/start_andromeda-android.sh
#### optional, if your phone lacks /system/etc/init.d support, and you want to simulate it with magisk
# mount -o remount,rw /system
## if /system/etc/init.d exists and is not functional, like on my P20 Pro, just do
# rm -fr /system/etc/init.d
# ln -s /magisk/.core/service.d /system/etc/init.d
# mount -o remount,ro /system
# start_andromeda-android.sh
Code:
#!/system/bin/sh
sleep 15
# Let's first grab the location where Andromeda is installed
pkg=$(pm path projekt.andromeda)
# Due to the way the output is formatted, we have to strip 10 chars at the start
pkg=$(echo $pkg | cut -d : -f 2 | sed s/\\r//g)
# Now let's kill the running Andromeda services on the mobile device
kill=$(pidof andromeda)
# Check if we need to kill the existing pids, then kill them if need be
if [ -z "$kill" ]; then[INDENT]am force-stop projekt.substratum
appops set projekt.andromeda RUN_IN_BACKGROUND allow
appops set projekt.substratum RUN_IN_BACKGROUND allow
CLASSPATH=$pkg app_process /system/bin --nice-name=andromeda projekt.andromeda.Andromeda &
[/INDENT]
else
[INDENT]am force-stop projekt.substratum
kill -9 $kill
appops set projekt.andromeda RUN_IN_BACKGROUND allow
appops set projekt.substratum RUN_IN_BACKGROUND allow
CLASSPATH=$pkg app_process /system/bin --nice-name=andromeda projekt.andromeda.Andromeda &
[/INDENT]
fi

Categories

Resources