I installed an application that sent my phone into a bootloop. I identified the culprit via adb logcat, but obviously cannot get into the phone to delete it. I don't want to do a wipe - I have a lot of time spent customising things as is and data I don't want to lose in some apps. Is there a way from within the recovery console to delete the offending application directly to stop the bootloop?
EDIT: N/m... thought it was the app, looking closer at adb logcat, looks like it isn't... and I found a way to delete the app but the issue remains.
Going to switch ROMs, the one I'm using now is fast, but appears to be way too buggy.
lotherius said:
I installed an application that sent my phone into a bootloop. I identified the culprit via adb logcat, but obviously cannot get into the phone to delete it. I don't want to do a wipe - I have a lot of time spent customising things as is and data I don't want to lose in some apps. Is there a way from within the recovery console to delete the offending application directly to stop the bootlopp?
Click to expand...
Click to collapse
omgggggggggg
http://forum.xda-developers.com/showthread.php?p=4529707
if you have apps2sd
Code:
adb remount
adb shell
rm /system/sd/app/xxxx.apk (or if that doesn't work put -r after rm)
if you dont have apps to sd, i believe apps are in /data/app
B-man007 said:
omgggggggggg
http://forum.xda-developers.com/showthread.php?p=4529707
if you have apps2sd
Code:
adb remount
adb shell
rm /system/sd/app/xxxx.apk (or if that doesn't work put -r after rm)
if you dont have apps to sd, i believe apps are in /data/app
Click to expand...
Click to collapse
i think my crappy typed-at-work commands have been quoted lol. I need to start a whole series of typed at work commands.
Also @lotherius what rom were you using?
Enomther's Rogers. May not have been the ROM but I am a bit frustrated as I have had several problems with it, and just went back to Cyanogen 4.0.4 for now. Thanks for the info.
Hi lotherius,
I'm in the same situation; How did you delete the app within the recovery? I have a Cyanogenmod 10.1 (android 4.2.2) based custom ROM with TWRP recovery right now.
Thanks in advanced!
lotherius said:
I installed an application that sent my phone into a bootloop. I identified the culprit via adb logcat, but obviously cannot get into the phone to delete it. I don't want to do a wipe - I have a lot of time spent customising things as is and data I don't want to lose in some apps. Is there a way from within the recovery console to delete the offending application directly to stop the bootloop?
EDIT: N/m... thought it was the app, looking closer at adb logcat, looks like it isn't... and I found a way to delete the app but the issue remains.
Going to switch ROMs, the one I'm using now is fast, but appears to be way too buggy.
Click to expand...
Click to collapse
adb uninstall badapp.apk
Or if this won't work try
adb shell
adb rm /data/app/badapp.apk
Or system app or wherever it is (may be able to just delete the data of the app too
Sent from my Nexus 4 using xda premium
Wow, thread necromancy
I'm just a guy, not a techophobe so I have no idea how to get to the shell inorder to type those commands. My daughter's Macbook Pro just endlessly restarts itself unless I put it in Recovery mode or Safe mode. I suspect it is 3rd party apps causing this, but I can't delete apps from Rec. or Safe mode and no one here has put it in layman's terms.
I'm currently using Dwangs donut ROM.
For some strange reason my Terminal Emulator is "missing".
There is no icon for it in my app tray.
Market shows it as installed, but cannot open it nor uninstall it.
I have now installed Better Terminal Emulator Magic. What commands do I need to enter to completely remove Terminal Emulator from my system, so that I can try reinstalling it from the Market?
I hope I've made myself clear - if not please feel free to ask for clarification!
Look in the Development Tools or Spare Parts. I've seen a couple builds where it ends up in there.
qwerty3656 said:
Look in the Development Tools or Spare Parts. I've seen a couple builds where it ends up in there.
Click to expand...
Click to collapse
Just looked in Spare Parts - not there. Can't find Development Tools on my phone.
To remove it do this in the recovery console
mount system
rm /system/app/Term.apk (i think that is the name for it)
reboot
david1171 said:
To remove it do this in the recovery console
mount system
rm /system/app/Term.apk (i think that is the name for it)
reboot
Click to expand...
Click to collapse
Ah, now we're getting somewhere (sort of!)
I've done that, but get the response:
rm: cannot remove ' /system/app/Term.apk' : No such file or directory
that means its not there or its spelled wrong..
try using /system/sd instead of system
also, maybe clearing the market cache would work
B-man007 said:
that means its not there or its spelled wrong..
try using /system/sd instead of system
also, maybe clearing the market cache would work
Click to expand...
Click to collapse
Tried both of these - no joy :-(
1. Same response as before
2. Terminal Emulator still showing as installed (but Open & Uninstall buttons greyed out), even after clearing Market cache.
well if you dl one of cyanogens roms, you can pull the apk from there and push it to system
Yea or adb install -r
if it is not in /system/app then you can drop it in there with these commands, make sure that the .apk is in the root of your sdcard
Code:
mount sdcard
mount system
cp /sdcard/Term.apk /system/app/
reboot
I applied the latest CM-update, and upon reboot my Facebook application was not showing, not listed in settings (manage application) or application directory. but if you attempt to install from Market it shows as installed and Open & Uninstall are grayed out. does anyone have an idea how to resolve this ???
Did you try ADBing in, removing the app, then reinstalling?
Mi|enko said:
Did you try ADBing in, removing the app, then reinstalling?
Click to expand...
Click to collapse
Hmmm - ADBing (must research this and find the appropriate instructions) .. I have never attempted something like this, Just a simple flash ROM guy; but I do have a little technical experience..
Is it very complicated ???
Shouldn't be too hard. Download adb (from the tools folder from the Android SDK), first do "adb remount", then use "adb shell" once it's set up, then you should get the rest, at least if you know basic unix commands like cd and rm. I think it's in /system/app somewhere, btw. If you need any help, just ask
The Compiler said:
Shouldn't be too hard. Download adb (from the tools folder from the Android SDK), first do "adb remount", then use "adb shell" once it's set up, then you should get the rest, at least if you know basic unix commands like cd and rm. I think it's in /system/app somewhere, btw. If you need any help, just ask
Click to expand...
Click to collapse
All better now...Thanks you guys...
I am trying to get rid of Amazon mp3 and i cant get rid of it i tried using android commander and astro and free advanced task killer and it will not go away. Also does anyone have a better free task killer than what i am using. they updated free advanced task killer and now it sucks. any help would be appreciated.
Skippy
firestonetech32 said:
I am trying to get rid of Amazon mp3 and i cant get rid of it i tried using android commander and astro and free advanced task killer and it will not go away. Also does anyone have a better free task killer than what i am using. they updated free advanced task killer and now it sucks. any help would be appreciated.
Skippy
Click to expand...
Click to collapse
The phone is still nand locked. It is only unlocked in recovery. You will have to remove the apk's via adb in recovery. Also task killers are highly discouraged on Froyo roms.
bkmo said:
The phone is still nand locked. It is only unlocked in recovery. You will have to remove the apk's via adb in recovery. Also task killers are highly discouraged on Froyo roms.
Click to expand...
Click to collapse
i tried everything to remove it in recovery using adb and no luck any suggestions?
firestonetech32 said:
i tried everything to remove it in recovery using adb and no luck any suggestions?
Click to expand...
Click to collapse
If you have clockwork recovery installed, then goto partitions and mount /system.
Then you can ADB in and rm the .apks you don't want.
You also shouldn't boot into recovery with the USB plugged in. Boot into recovery THEN plug it in, or you'll get directory not empty errors.
i get the error (/sbin/sh: pm: not found) when i type in (adb uninstall com.amazon.mp3 or adb uninstall com.amazon.mp3.apk) and i rebooted into recovery without the usb plugged in and mounted the system file in partitions menu
firestonetech32 said:
i get the error (/sbin/sh: pm: not found) when i type in (adb uninstall com.amazon.mp3 or adb uninstall com.amazon.mp3.apk) and i rebooted into recovery without the usb plugged in and mounted the system file in partitions menu
Click to expand...
Click to collapse
Don't try to uninstall the apk's, just adb shell rm /system/app/apkname.apk, or navigate to /system/app and rm apkname.apk
i get the error (/sbin/sh: pm: not found) when i type in (adb uninstall com.amazon.mp3 or adb uninstall com.amazon.mp3.apk)
Click to expand...
Click to collapse
This is a problem with the path variable in the CM6 roms. See my thread here. http://forum.xda-developers.com/showthread.php?t=780860
Short story, change the path in init.rc in order to use uninstall or install or just use the rm command as stated above (probably the easiest). I corrected the path on my rom as it seems to me it should include /system/bin which is where the "pm" command is located.
if by any chance you downloaded the app from the market, you can uninstall it from the market app by going to the download page & choose uninstall.
Just download winzip open the gapps zip on your computer delete the Amazon API from within winzip then place on your sd card then flash the new gapps in clockwork
Sent from my Liberty using XDA App
I have installed Google Now launcher on the 5..1.1 firmware, I have root access as well and have pm hid and removed (just rm'ing the process folders from /system/priv-app) most of the bloatware. Whenever I try to hit the "home" button it just brings up a message saying " The requested action is not permitted. Check Parental Controls settings and retry". I also pm hid and attempted to remove com.amazon.parentalcontrols and it hasn't had any effect either.
If I reboot the device it does bring up the Now launcher, but as soon as I go to another application view and try to go "back" or use the home button I get the parental controls message.
KennBr said:
I have installed Google Now launcher on the 5..1.1 firmware, I have root access as well and have pm hid and removed (just rm'ing the process folders from /system/priv-app) most of the bloatware. Whenever I try to hit the "home" button it just brings up a message saying " The requested action is not permitted. Check Parental Controls settings and retry". I also pm hid and attempted to remove com.amazon.parentalcontrols and it hasn't had any effect either.
If I reboot the device it does bring up the Now launcher, but as soon as I go to another application view and try to go "back" or use the home button I get the parental controls message.
Click to expand...
Click to collapse
Well that's a new one, though have seen people say that now launcher is finicky and to have another launched installed as well.
I to have ota 5.1.1 with root and have tried to block the stock lauuncher got the same error i tried with 2 diff launchers, i havent tried to install both then disable the stock maybe it will trigger something to do with the default settings. in one of the settings menus for one of the launchers it says something about "set default launcher" and when i select it to set it to new launcher it just opens the stock one. does anyone know if there is a way to change what launcher the home button defaults to, either through adb shell or fastboot someway.
Have you tried su pm hide com.amazon.parentalcontrols
from a adb shell
jdeandeck said:
I to have ota 5.1.1 with root and have tried to block the stock lauuncher got the same error i tried with 2 diff launchers, i havent tried to install both then disable the stock maybe it will trigger something to do with the default settings. in one of the settings menus for one of the launchers it says something about "set default launcher" and when i select it to set it to new launcher it just opens the stock one. does anyone know if there is a way to change what launcher the home button defaults to, either through adb shell or fastboot someway.
Have you tried su pm hide com.amazon.parentalcontrols
from a adb shell
Click to expand...
Click to collapse
How did you try to block it?
Whilst the stock launcher is on and is a system app the Fire OS won't let any other launcher steal default.
Pond-life said:
How did you try to block it?
Whilst the stock launcher is on and is a system app the Fire OS won't let any other launcher steal default.
Click to expand...
Click to collapse
I used adb shell pm hide com.amazon.firelauncher -- adb reboot-- reboots to apex launcher but when i push home i get the error, do i need to actually uninstall it or can i install a rom management app and remove it from system app list and freeze it im trying not to do any of this stuff without confirmation on it working, my wife is worried ill ruin her fire. Do you know how hard is it to flash back to stock firmware from a bricked Fire?
i have flashed devices before roms and recovery so im not a noob but i would just hate to be wrong and try something and not be able to fix it.
jdeandeck said:
I used adb shell pm hide com.amazon.firelauncher -- adb reboot-- reboots to apex launcher but when i push home i get the error, do i need to actually uninstall it or can i install a rom management app and remove it from system app list and freeze it im trying not to do any of this stuff without confirmation on it working, my wife is worried ill ruin her fire. Do you know how hard is it to flash back to stock firmware from a bricked Fire?
i have flashed devices before roms and recovery so im not a noob but i would just hate to be wrong and try something and not be able to fix it.
Click to expand...
Click to collapse
Hmm I'm sure that hiding it has worked for others, maybe not on 5.1.1 though, I froze it in titanium backup. Widgets didn't work in Apex until I pushed it to system but it did work as main launcher. As did trebuchet and Nova.
If it's opening when you've hidden it then suggests that it's not hidden maybe needs root shell to do it on 5.1.1 as with hiding the ads and ota
Pond-life said:
Hmm I'm sure that hiding it has worked for others, maybe not on 5.1.1 though, I froze it in titanium backup. Widgets didn't work in Apex until I pushed it to system but it did work as main launcher. As did trebuchet and Nova.
If it's opening when you've hidden it then suggests that it's not hidden maybe needs root shell to do it on 5.1.1 as with hiding the ads and ota
Click to expand...
Click to collapse
it doesnt open but it gives me the parental control error, is it possible to rename the apex application maybe to com.amazon.firelauncher.apk and overwrite the current one, after backing up the original of course, to get rid of the parental error?
jdeandeck said:
it doesnt open but it gives me the parental control error, is it possible to rename the apex application maybe to com.amazon.firelauncher.apk and overwrite the current one, after backing up the original of course, to get rid of the parental error?
Click to expand...
Click to collapse
Pretty sure that wouldn't work. It'll likely expect Apex to be able to work in ways amazon launcher can but it can't.
If you've got a back up of the original you could try renaming it or just deleting it on the tablet, I don't think hide is working as it should.
Could try the supertool to switch the launcher to nova and then change launcher to Apex after. The tool does delete the amazon launcher, so backed up original handy.
http://forum.xda-developers.com/amazon-fire/development/amazon-fire-5th-gen-supertool-root-t3272695
Using pm hide com. amazon. firelauncher worked fine for me to disable the Fire launcher but I had to reboot before Google Now tried to launch. Which it did, but then trying to use the home or back buttons brings on the message.
Another weird thing, all the bloat thst I hid the same way deems to have come back overnight somehow. I did disable Ota updates so not sure how that is.
KennBr said:
Using pm hide com. amazon. firelauncher worked fine for me to disable the Fire launcher but I had to reboot before Google Now tried to launch. Which it did, but then trying to use the home or back buttons brings on the message.
Another weird thing, all the bloat thst I hid the same way deems to have come back overnight somehow. I did disable Ota updates so not sure how that is.
Click to expand...
Click to collapse
so if you have perm root than first download and install
HTML:
http://www.apkdrawer.com/rom-toolbox-pro-apk/
then install the google now launcher and run it and everything get it running then reboot
next through the Rom Toolbox make the Google Now a system app
then "adb shell pm hide com.amazon.launcher" then "adb reboot"
Just incase this factors in i used the script from the super tool, since i run linux and cant run the bat file, as a guide i was trying to get my laucher "adb push Apex-Launcher.apk" & "adb shell "cp /data/local/tmp/--Apex-Launcher.apk--(my preferred laucher) /system/apps/Apex-Launcher.apk" but it would not let me mount file system as RW, so before i tried the above solution, which worked for me, i ran (adb reboot-bootloader) and (fastboot oem append-cmdline "androidboot.unlocked_kernel=true") so you may or may not have to do this before you try to hide the launcher but after you install Rom Toolbox
KennBr said:
Using pm hide com. amazon. firelauncher worked fine for me to disable the Fire launcher but I had to reboot before Google Now tried to launch. Which it did, but then trying to use the home or back buttons brings on the message.
Another weird thing, all the bloat thst I hid the same way deems to have come back overnight somehow. I did disable Ota updates so not sure how that is.
Click to expand...
Click to collapse
Those are both symptoms of the hide command not working fine. It needs to be done in root as jdeandeck did.
If you disable the ota with a hide command too I'd rename the ota files or do that again in root.
jdeandeck said:
so if you have perm root than first download and install
HTML:
http://www.apkdrawer.com/rom-toolbox-pro-apk/
then install the google now launcher and run it and everything get it running then reboot
next through the Rom Toolbox make the Google Now a system app
then "adb shell pm hide com.amazon.launcher" then "adb reboot"
Just incase this factors in i used the script from the super tool, since i run linux and cant run the bat file, as a guide i was trying to get my laucher "adb push Apex-Launcher.apk" & "adb shell "cp /data/local/tmp/--Apex-Launcher.apk--(my preferred laucher) /system/apps/Apex-Launcher.apk" but it would not let me mount file system as RW, so before i tried the above solution, which worked for me, i ran (adb reboot-bootloader) and (fastboot oem append-cmdline "androidboot.unlocked_kernel=true") so you may or may not have to do this before you try to hide the launcher but after you install Rom Toolbox
Click to expand...
Click to collapse
I am using Linux as well, I got the persistent root going, Super SU installed as described in this thread: http://forum.xda-developers.com/amazon-fire/orig-development/root-t3272362/post64347634#post64347634 I tried intsalling the Now launcher just via the Play Store app. However, when I tried to remove the bloat from the /system/priv-apps/ directory I also noticed the filesystem was read-only so I remounted it like so (I am totally unsure if this is proper)
Code:
adb shell
su
mount -o rw,remount /system
That seemed to give me sufficiant read-write access with a root terminal.
Pond-life said:
Those are both symptoms of the hide command not working fine. It needs to be done in root as jdeandeck did.
If you disable the ota with a hide command too I'd rename the ota files or do that again in root.
Click to expand...
Click to collapse
As in a root terminal? I launched an adb shell and used su and mount as described above to get read-write access and a root terminal, then did...
Code:
cat /data/local/tmp/bloat_list | while read process ; do pm hide $process ; done
and
Code:
cat /data/local/tmp/bloat_list | while read process ; do rm -R $process ; done
It seemed to remove the directories associated with the given item on the "bloat_list" file which I compiled from the "safe to remove bloatware" threads and pushed to the /data/local/tmp directory using adb. I did this prior on 5.0.1 without breaking too much... Aside from not being able to open my account settings any longer.
Contents of my "bloat_list"
Code:
com.amazon.ags.app
com.audible.application.store
com.amazon.camera
com.amazon.client.metrics
com.android.contacts
com.amazon.csapp
com.amazon.device.backup
com.amazon.h2settingsfortablet
com.amazon.kindle
com.amazon.kindle.kso
com.amazon.kindle.otter
com.amazon.mp3
com.amazon.kindle.otter.oobe
com.amazon.kindle.otter.settings
com.amazon.kindle.personal_video
com.amazon.legalsettings
com.amazon.photos.importer
com.amazon.photos
com.amazon.platform
com.amazon.tahoe
com.amazon.venezia
com.amazon.whisperlink.core.android
com.amazon.windowshop
com.amazon.zico
com.andoid.contacts
com.android.calendar
com.android.email
com.audible.application.kindle
com.goodreads.kindle
com.nuance.edr.androidservice.service
com.amazon.webapp
amazon.jackson-19.apk
com.kingsoft.office.amz
com.amazon.kor.demo
com.amazon.ods.kindleconnect
com.amazon.accessorynotifier
com.amazon.cloud9
com.amazon.weather
com.amazon.calculator
So every item in that list would have been acted on with both pm hide and rm -R (just clarifying)
Yet somehow a good amount of the items on that list came back over night. I'm not really sure my method for removing the files really had the effect that I think it did, because everything still seemed to work as if I hadn't deleted it... Well except for the "My Account" section of the "Settings", so I don't think I should have done the "rm -R" part to delete the files because it seems to have had some kind of effect.
As for the launcher situation, I backed up the firelauncher first before trying to remove and hide it and that did seem to work, but given the parental controls message I had to restore the launcher to maintain functionality. I don't think that trying to delete the items on the bloat_list first might have "broken" something and caused the message though because I tried to change the launcher BEFORE the items on the bloat_list.
I tried installing the Apex Launcher and for whatever reason it's working even without hiding or deleting Firelauncher... Though I haven't rebooted yet so I'm doubting that will remain the case.
As for the Rom Toolbox app, what exactly does it do? Reboots the device into some kind of custom recovery where I can alter settings? I've never heard of it before.
KennBr said:
I am using Linux as well, I got the persistent root going, Super SU installed as described in this thread: http://forum.xda-developers.com/amazon-fire/orig-development/root-t3272362/post64347634#post64347634 I tried intsalling the Now launcher just via the Play Store app. However, when I tried to remove the bloat from the /system/priv-apps/ directory I also noticed the filesystem was read-only so I remounted it like so (I am totally unsure if this is proper)
Code:
adb shell
su
mount -o rw,remount /system
That seemed to give me sufficiant read-write access with a root terminal.
As in a root terminal? I launched an adb shell and used su and mount as described above to get read-write access and a root terminal, then did...
Code:
cat /data/local/tmp/bloat_list | while read process ; do pm hide $process ; done
and
Code:
cat /data/local/tmp/bloat_list | while read process ; do rm -R $process ; done
It seemed to remove the directories associated with the given item on the "bloat_list" file which I compiled from the "safe to remove bloatware" threads and pushed to the /data/local/tmp directory using adb. I did this prior on 5.0.1 without breaking too much... Aside from not being able to open my account settings any longer.
Contents of my "bloat_list"
Code:
com.amazon.ags.app
com.audible.application.store
com.amazon.camera
com.amazon.client.metrics
com.android.contacts
com.amazon.csapp
com.amazon.device.backup
com.amazon.h2settingsfortablet
com.amazon.kindle
com.amazon.kindle.kso
com.amazon.kindle.otter
com.amazon.mp3
com.amazon.kindle.otter.oobe
com.amazon.kindle.otter.settings
com.amazon.kindle.personal_video
com.amazon.legalsettings
com.amazon.photos.importer
com.amazon.photos
com.amazon.platform
com.amazon.tahoe
com.amazon.venezia
com.amazon.whisperlink.core.android
com.amazon.windowshop
com.amazon.zico
com.andoid.contacts
com.android.calendar
com.android.email
com.audible.application.kindle
com.goodreads.kindle
com.nuance.edr.androidservice.service
com.amazon.webapp
amazon.jackson-19.apk
com.kingsoft.office.amz
com.amazon.kor.demo
com.amazon.ods.kindleconnect
com.amazon.accessorynotifier
com.amazon.cloud9
com.amazon.weather
com.amazon.calculator
So every item in that list would have been acted on with both pm hide and rm -R (just clarifying)
Yet somehow a good amount of the items on that list came back over night. I'm not really sure my method for removing the files really had the effect that I think it did, because everything still seemed to work as if I hadn't deleted it... Well except for the "My Account" section of the "Settings", so I don't think I should have done the "rm -R" part to delete the files because it seems to have had some kind of effect.
As for the launcher situation, I backed up the firelauncher first before trying to remove and hide it and that did seem to work, but given the parental controls message I had to restore the launcher to maintain functionality. I don't think that trying to delete the items on the bloat_list first might have "broken" something and caused the message though because I tried to change the launcher BEFORE the items on the bloat_list.
I tried installing the Apex Launcher and for whatever reason it's working even without hiding or deleting Firelauncher... Though I haven't rebooted yet so I'm doubting that will remain the case.
As for the Rom Toolbox app, what exactly does it do? Reboots the device into some kind of custom recovery where I can alter settings? I've never heard of it before.
Click to expand...
Click to collapse
Once in terminal the commands are the same from whatever computer you are using aren't they? Doesn't rm need the full directory address as it's not through pm?
The rom toolbox I think he just used to make the Now launcher a system app, so not something you can't do in adb.
Rom Toolbox is my favorite app for everything. Here is a list of some of the features you will find:
ROM Management
Install ROM’s & themes from a growing list of ROM’s. KAPOK, Cyanogen Mod and other popular ROM’s included in ROM Toolbox Pro apk.
Create, manage & restore nandroid backups
Wipe data, cache, dalvik-cache, battery stats
Install multiple ROMs & ZIPs from your SD card
App Manager
Batch backup & restore apps and their data
Schedule backups to run at a certain time
Restore apps from nandroid backups
Backup/Restore text messages, bookmarks, accounts, etc.
Backup your apps to dropbox
Freeze/Defrost system & user apps
Backup/restore Android Market link
Task manager
Automated batch uninstaller
E-mail your apps to friends
Move any user app to the SD card
Clean up dalvik-cache
Zip align, fix permissions, wipe data & cache, force close any app
Root Explorer
Access the whole of android’s file system (including the elusive data folder!).
Batch copy/paste, zip, tar, delete, move any file or folder
Change file permissions and ownership
View, edit & share files with ROM Toolbox Pro apk
File manager with two panels for easier management
Script-er & Terminal Emulator
Create and run scripts as root
Set your scripts to run at-boot
Auto Start Manager
Enable/disable apps that run on start-up
Enable/disable any broadcast receiver, activity or service
Reboot er
Reboot recovery, powerdown, bootloader, restart status bar, etc.
Font Installer
Install custom fonts from a huge list or from your sdcard
Set fonts as favorites & send them to friends
Boot Animation Installer
Install custom boot animations from a huge collection or from your sdcard
Preview boot animations
Create a boot animation from a GIF file
Have a new random boot animation each time you boot-up!
Theme Manager & Status bar Icon Changer
Create and install full themes (Meta Morph compatible)
Customize your status bar by installing custom icons for wifi, signal, gps, etc.
Change your battery icons in the status bar to a custom one from a list of 200+
Boot Logo Changer
Change your boot logo for supported phones
Theme Chooser Themes
View a list of themes for the T Mobile Theme Chooser
Set CPU
Set CPU & scaling governor
CPU Profiles
Kernel tweaks to speed up performance
Build.prop Editor
Easily edit your build.prop
Change LCD density, improve battery life, increase performance
Auto Memory Manager
Set min free values & select from presets. Apply values at boot
SD Booster
Increase the speed of your SD card
Permissions
Contacts – Backup call log and sms
SMS – Backup call log and sms
Accounts – Backup and restore from Google Drive
As for the bloat problem the:
Code:
fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
Seems to be imoportant for my Special Offer "screensaver" hiding a.k.a. com.amazon.kso
but idk if this works i guess i could try myself but Rom Toolboxes App Manager feature, that is only available in the pro, can "freeze" the com.amazon.firelauncher....
ok the above seems to worked maybe having the app installed when i did it did something in the settings or i froze the launcher and just dont remember it, but when i froze the firelauncher and pushed the home button, without the apexlauncher installed, nothing happened, not even the parental control message. then i reinstalled the apex launcher, hint get the pro from the site i mentioned before, and adb reboot, it worked.
next i might try to freeze some bloatware and see what i can get rid of but still save amazon app store stuff like books, audio books+store, videos, Game circle-thats for me, music player, shop amazon, which as i type i realize i can do from the Rom Toolbox with root, i swear im not selling anything
Pond-life said:
Once in terminal the commands are the same from whatever computer you are using aren't they?
The rom toolbox I think he just used to make the Now launcher a system app, so not something you can't do in adb.
Click to expand...
Click to collapse
Yeah they are the same since it's basically a *nix shell, was just showing how I did it. I'm not sure if there's some nuance I'm not aware of thst would make it not work... It seemed like I had all the permissions I needed, and I have root set up persistently as described in the thread I linked to.
The rom toolbox app, how does it boot recoveries if fastboot can't? Sorry I'm so used to desktops, fiddling with Androids goes above my head.
And the commands are the same but the \ in windows commands are / in linux like android so scripts meant for windows wont work on linux, or that i have found and i cant get .bin to run but never tried to change to .sh and run as shell script but thats for another forum
jdeandeck said:
Rom Toolbox is my favorite app for everything.
As for the bloat problem the:
Code:
fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
Seems to be important for my Special Offer "screensaver" hiding a.k.a. com.amazon.kso
but idk if this works i guess i could try myself but Rom Toolboxes App Manager feature, that is only available in the pro, can "freeze" the com.amazon.firelauncher....
ok the above seems to worked maybe having the app installed when i did it did something in the settings or i froze the launcher and just dont remember it, but when i froze the firelauncher and pushed the home button, without the apexlauncher installed, nothing happened, not even the parental control message. then i reinstalled the apex launcher, hint get the pro from the site i mentioned before, and adb reboot, it worked.
next i might try to freeze some bloatware and see what i can get rid of but still save amazon app store stuff like books, audio books+store, videos, Game circle-thats for me, music player, shop amazon, which as i type i realize i can do from the Rom Toolbox with root, i swear im not selling anything
Click to expand...
Click to collapse
It does seem rather a flexible toolkit.
Once you've got permanent root the fastboot bit shouldn't be needed I don't think. Hmmm.
I did clear much of the apps out, though did put Shop Amazon back on as I think something I wanted to use wouldn't work. I can't recall what though.
KennBr said:
Yeah they are the same since it's basically a *nix shell, was just showing how I did it. I'm not sure if there's some nuance I'm not aware of thst would make it not work... It seemed like I had all the permissions I needed, and I have root set up persistently as described in the thread I linked to.
The rom toolbox app, how does it boot recoveries if fastboot can't? Sorry I'm so used to desktops, fiddling with Androids goes above my head.
Click to expand...
Click to collapse
I use it to mostly change build.prop and backup apks and terminal emulator other things that i feel comfortable doing nothing like flashing or whatever i only flash from terminal on my linux pc or there is a app for flashing lg phones nothing easier than that.
KennBr said:
Yeah they are the same since it's basically a *nix shell, was just showing how I did it. I'm not sure if there's some nuance I'm not aware of thst would make it not work... It seemed like I had all the permissions I needed, and I have root set up persistently as described in the thread I linked to.
The rom toolbox app, how does it boot recoveries if fastboot can't? Sorry I'm so used to desktops, fiddling with Androids goes above my head.
Click to expand...
Click to collapse
Ooops I edited that one while you were replying.
Unlike pm doesn't rm need to know where the file or directory is like in this from the supertool?
adb shell "rm /system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk"
so it'd need to know that those directories were in priv-app in system?
And it seems to make a different part writeable than you did, at least I think that's what the chmod does and uses disable rather than hide oh and the " " everywhere.
adb shell su -c "chmod 777 /cache"
adb shell su -c "pm disable com.amazon.otaverifier"
adb shell su -c "pm disable com.amazon.device.software.ota"
adb shell su -c "pm disable com.amazon.settings.systemupdates"
And the fastboot oem command followed by fastboot reboot, not fastboot continue, lets me adb remount fine then when im done doing whatever i use adb reboot then it will reboot and reconfigure apps and settings or something and works good.
---------- Post added at 02:36 AM ---------- Previous post was at 02:30 AM ----------
Pond-life said:
Ooops I edited that one while you were replying.
Unlike pm doesn't rm need to know where the file or directory is like in this from the supertool?
adb shell "rm /system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk"
so it'd need to know that those directories were in priv-app in system?
And it seems to make a different part writeable than you did, at least I think that's what the chmod does and uses disable rather than hide oh and the " " everywhere.
adb shell su -c "chmod 777 /cache"
adb shell su -c "pm disable com.amazon.otaverifier"
adb shell su -c "pm disable com.amazon.device.software.ota"
adb shell su -c "pm disable com.amazon.settings.systemupdates"
Click to expand...
Click to collapse
i edited what i read to what i needed and if it said adb shell i ran everything from the adb shell fro terminal instead of saying adb shell su every time i said adb shell then su then pm ...