Related
i have a Kindle Fire HD 7" with the system version of 7.2.1 and i wanted to ether put ICS or even Jelly bean on it so that i could have that Android Interface instead of the Amazon book self thing which im not very fond of and also have the Play Store. I spent all of yesterday, not exaggerating, all of yesterday trying to root my device. So i watched all the videos on you tube and read a ton of threads about it here at XDA and i just dont know what im doing wrong.
So first i download the Kindle Fire Utility (KFU) and installed the drivers(in device manager it showed my kindle fire and under it Android Composite ADB Interface), then plugging in my device i ran the "run" batch file. and the red command prompt pops up and it brings up the menu and at the bottom it says "ADB Status: Online, Boot Status Unknown" so i tried changing the boot mode to normal or fast boot,just changing it at all would have been nice but it always just stays as unknown. i tried hitting 1 to change to different boot mode but it would just reboot with no changes. then i tried entering 2 "installing permanant root with superuser" and twards the bottom of the screen its says rebooting device into fast boot mode, installing FFF, waiting for device. and it reboots and thats it, it doesnt go anywhere from there. so then i went to "6" extras and then "1" install google app / Go launcher which actually did work i have the Play store and Go Launcher (it says installed but its no where to be found on the device) and i also tried all the other options on the main menu, install TWRP, CLOCKWORKMOD and FFF and they all say missing directory and my kindle reboots and it says waiting for device and thats it nothing happens
SO i gave up with that method
so then i tried using the SDK -> ADB-> platform tool command prompt method and typed everything perfectly just like the threads and videos said to and still its like i got no where. i typed everything in just as shown and it seemed to be working but at the end it didnt work ether. i wish i had more specifics of what i typed in and what it said back in the command prompt but i did this yesterday so its gone now. i Dont know what im doing wrong and its very frustrating
(keep in mind im a noob and simple terms would be appreciated)
Zponds360 said:
i have a Kindle Fire HD 7" with the system version of 7.2.1 and i wanted to ether put ICS or even Jelly bean on it so that i could have that Android Interface instead of the Amazon book self thing which im not very fond of and also have the Play Store. I spent all of yesterday, not exaggerating, all of yesterday trying to root my device. So i watched all the videos on you tube and read a ton of threads about it here at XDA and i just dont know what im doing wrong.
So first i download the Kindle Fire Utility (KFU) and installed the drivers(in device manager it showed my kindle fire and under it Android Composite ADB Interface), then plugging in my device i ran the "run" batch file. and the red command prompt pops up and it brings up the menu and at the bottom it says "ADB Status: Online, Boot Status Unknown" so i tried changing the boot mode to normal or fast boot,just changing it at all would have been nice but it always just stays as unknown. i tried hitting 1 to change to different boot mode but it would just reboot with no changes. then i tried entering 2 "installing permanant root with superuser" and twards the bottom of the screen its says rebooting device into fast boot mode, installing FFF, waiting for device. and it reboots and thats it, it doesnt go anywhere from there. so then i went to "6" extras and then "1" install google app / Go launcher which actually did work i have the Play store and Go Launcher (it says installed but its no where to be found on the device) and i also tried all the other options on the main menu, install TWRP, CLOCKWORKMOD and FFF and they all say missing directory and my kindle reboots and it says waiting for device and thats it nothing happens
SO i gave up with that method
so then i tried using the SDK -> ADB-> platform tool command prompt method and typed everything perfectly just like the threads and videos said to and still its like i got no where. i typed everything in just as shown and it seemed to be working but at the end it didnt work ether. i wish i had more specifics of what i typed in and what it said back in the command prompt but i did this yesterday so its gone now. i Dont know what im doing wrong and its very frustrating
(keep in mind im a noob and simple terms would be appreciated)
Click to expand...
Click to collapse
WARNING!!
Firstly your Using a Kindle Fire HD. That is different to the Kindle fire. Even with root I dont think your gonna be running Jelly Bean just yet. You will probably brick the device if you use a standard Kindle Fire ROM!!!!!!!!!!!!!!!!!!!!!
Ok first download and Install the Android SDK. Put it where its easy to find. I use c:\ . Once thats done open SDK manager and tick next to Android SDK Platform-tools and click the box for Install packages.
Once thats done See this page: http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
This gives the most stable ADB I have found.
OK next see this thread. This is automated root. http://forum.xda-developers.com/showthread.php?t=1893838.
If that still doesnt work (It didnt for me and others). Watch this Video. http://youtu.be/CYDBoTtdvcE This is the manual method. For a bigger look at the code see this page: http://www.redmondpie.com/how-to-root-amazon-kindle-fire-hd-7-8.9-on-android-4.0.4-ics/
On this page the open quote looks like a tilde EDIT thats actually a grave accent...I always called it the tilde key. Its not just use the KB apostrophe ( ' ) wherever you see a quote!
Hope this helps and I hope I dont get into trouble for posting external Links. Just trying to help!
Could anyone kindly share the adb code to change the permissions of an apk and push it to system/app/ ?
Using adb from a PC.
Please and thanks. :fingers-crossed:
Krsmqn said:
Could anyone kindly share the adb code to change the permissions of an apk and push it to system/app/ ?
Using adb from a PC.
Please and thanks. :fingers-crossed:
Click to expand...
Click to collapse
You know you can set the permissions before you push it to /system/app
Windows right?
http://www.cyberciti.biz/tips/windows-change-access-permissions-from-the-command-line.html
Or after you push it to /system/app
Code:
adb shell chmod <permissions> <filename>
Thank you for the reply.
To push to system/app, do I have the code right?
adb push xxxxxx.apk /system/app/
?
I try that and I get the error "device not found"
adb devices shows my device... wth?
Can anyone help?
How to Push Application to /system/app
Krsmqn said:
Could anyone kindly share the adb code to change the permissions of an apk and push it to system/app/ ?
Using adb from a PC.
Please and thanks. :fingers-crossed:
Click to expand...
Click to collapse
Krsmqn,
The code was missing a little information, I am sorry. First you need to make sure adb is enabled on the Kindle by
pulling down the upper status bar where you see the time. After you pull it down select More+ the go into
Security make sure Enable ADB is turned On. Next click the <- Arrow Back, then choose Device. Make sure
Allow Installation of Applications is turned On. If all this is OK, then let's test ADB. Make sure the Kindle is
plugged into USB, next go into Windows Device Manager by Right Hand Mouse Click on "Computer", select
"Properties", next select "Device Manager". Do you see Android Composite ADB Interface under Kindle Fire?
If no, go back to our tutorial and reinstall the ADB Driver as outlined in this tutorial:
http://forum.xda-developers.com/showthread.php?t=2069117
Once ADB is functioning properly, then let's PUSH files!
First let's make sure adb is running and make sure adb see's the Kindle. Please run these commands:
Code:
adb kill-server
adb start-server
adb devices
The output after devices will be a serial number, if this looks good, move on. First you need to make
sure the apk you want to push is in the same directory as adb.exe - if you have moved the apk to
the adb.exe directory, then run the following:
Code:
[FONT=Verdana]adb remount
adb push file_name_comes.apk_here /system/app/
adb shell chmod 644 /system/app/file_name_comes_here.apk
adb reboot[/FONT]
Does this help?
prokennexusa said:
Krsmqn,
The code was missing a little information, I am sorry. First you need to make sure adb is enabled on the Kindle by
pulling down the upper status bar where you see the time. After you pull it down select More+ the go into
Security make sure Enable ADB is turned On. Next click the <- Arrow Back, then choose Device. Make sure
Allow Installation of Applications is turned On. If all this is OK, then let's test ADB. Make sure the Kindle is
plugged into USB, next go into Windows Device Manager by Right Hand Mouse Click on "Computer", select
"Properties", next select "Device Manager". Do you see Android Composite ADB Interface under Kindle Fire?
If no, go back to our tutorial and reinstall the ADB Driver as outlined in this tutorial:
http://forum.xda-developers.com/showthread.php?t=2069117
Once ADB is functioning properly, then let's PUSH files!
First let's make sure adb is running and make sure adb see's the Kindle. Please run these commands:
Code:
adb kill-server
adb start-server
adb devices
The output after devices will be a serial number, if this looks good, move on. First you need to make
sure the apk you want to push is in the same directory as adb.exe - if you have moved the apk to
the adb.exe directory, then run the following:
Code:
[FONT=Verdana]adb remount
adb push file_name_comes.apk_here /system/app/
adb shell chmod 644 /system/app/file_name_comes_here.apk
adb reboot[/FONT]
Does this help?
Click to expand...
Click to collapse
Thank you for the help. I am thoroughly confused. This is going to be as detailed as I can make it.
Ok.... here's what happens:
The device shows up on my computer in device manager as "kindle fire > android adb interface" ... good right? But when plugged in, the usual "usb connected interface with the turn on usb storage button" doesn't show up on my kindle. The notification drop down only says "connected to a low power charger" .. blah blah. I will get to the CMD stuff in a sec.
On the kindle:
Besides the above mentioned stuff, when I press More :
Settings > My Account> the menu closes. The entire menu, so now I am looking at my home screen.
Settings> Applications>Notification settings> results in going back to the "more" or settings menu.
Settings>Applications>Installed Applications> seems to work . Shows both lists. All & Running.
Settings>Applications>Sync Amazon Content> results in nothing. Below that, Amazon App list is empty.So... figures.
Settings>Parental Controls are grayed out.
Settings>Sounds&Display> Everything here works except for >Notification Sounds> Back to Settings.
Settings>Wireless>Connects fine (didn't try bluetooth)
Settings>Device>About>All info is there (update kindle is grayed out)
Settings>Device>Storage>Back to Settings
Settings>Device>Date&Time> Time grayed out. Date grayed out. Select time zone works. Use 24h works.
Settings>Device>Allow Install of Apps> Works (is turned on)
Settings>Device>Reset to Factory Defaults> Menu pops up (are you sure blah blah) but I already did that and it's why I have these problems.
Settings>Location-based Services> Enable location works..
Settings>Language&Keyboard>Device language works.
Settings>Language&Keyboard>Keyboards>Default is Japanese? Keyboard Settings>All options work. But Japanese is the only language option.
Settings>Security>Everything here works, adb is on. No device admins.
Settings>Legal & Compliance>Notices>Everything here is fine.
Settings>Legal & Compliance>Terms of use> Back to Settings menu
Settings>Legal & Compliance>Safety stuff> Works
Settings>Legal & Compliance>Privacy>Opens Chrome (see chrome problems)
So that's what's up with the settings.
App issues:
Chrome> "Critical functionality required to run chrome is missing; either your chrome installation is incompatible, or not compatible with this version" Click ok and chrome closes. Chrome is the only browser installed that I can see.
Terminal Emulator> "Terminal Emulator has stopped" error msg.
Google search works untill it opens chrome.
Navigation> won't load (hangs at waiting for location with location on and wifi connected)
Maps> works including search. and wiki until you try to open chrome.
Latitude> works except when chrome in involved.
Google Drive> "Google Drive has stopped"
Youtube> Works fine until chrome is opened.
Camera/Video player/Music player/Gallery> Work
94/7fm (Streaming music app)> works except chrome is opened
Calendar> Won't open, asks you to register> registration attempt just closes without action.
Gmail>works untill chrome is opened.
Kindle Docs> Opens but is empty>cloud service fails at sign in.
News&weather> works until chrome is opened.
Amazon Video> closes instantly.
A few "go launcher apps (appcenter, gamezone, themes ,etc...) open but try to open chrome and fail.
That's about it for apps.
ADB:
adb devices: shows device
Try to push es file explorer renamed to ES.apk, located with adb.exe:
Code:
[FONT=Verdana]
c:\SDK\platform-tools>adb remount
remount failed: Operation not permited
c:\SDK\platform-tools>adb push ES.apk /system/app/
failed to copy 'ES.apk' to ' /system/app/ /ES.apk' : Read-only file system
c:\SDK\platform-tools>adb shell chmod 644 /system/app/ES.apk
Unable to chmod /system/app/ES.apk; No such file or directory
c:\SDK\platform-tools>adb reboot
[/FONT]
Rebooted to no avail. Am I still rooted? Do I need to change the permissions before I move it?
I hope I gave enough info. I'll be checking back frequently, as I really want to get this fixed.
*Edit*
On my other thread (usb not working) You're info helped me to install es file explorer. Thank you! I will try to figure it out and keep you posted.
No sound - biggest issue
Ok, I figured that until I can get all this google stuff worked out, I'd just side load apks. No problem. Installed Dolphin Browser HD and some other apps. After downloading winamp and putting a bunch of music on my device, I realized that there's no sound from the external speakers. Headphones work fine. Any ideas?
EDIT* sound all the sudden started working.. weird.
Kindle Fire HD - Odd Issues
Krsmqn said:
Ok, I figured that until I can get all this google stuff worked out, I'd just side load apks. No problem. Installed Dolphin Browser HD and some other apps. After downloading winamp and putting a bunch of music on my device, I realized that there's no sound from the external speakers. Headphones work fine. Any ideas?
EDIT* sound all the sudden started working.. weird.
Click to expand...
Click to collapse
Krsmqn,
If you continue to have these oddities, I would recommend you to order a USB Factory Cable so you
can flash a fresh copy of the software back to your Kindle. We do sell the Factory USB Cables for $15
shipped. Just PM us if you would like to order one. The Factory USB Cable allows the Kindle to be
booted in Fastboot mode.
app can not run when push /system/app
Hi all,
When i push app in /system/app when reboot and click on icon app but app hang and not run.Please help me ? I install my app on sd card run very well
Hi. I have a rooted kindle fire 7" .3rd gen.
I bought this kindle off craigslist used. it cant be registered though because i found out it was reported lost/stolen from amazon when i called about my registration issue. So i just rooted it and change alot around with new launchers and all. I am having an issue now though. after messing with pimp my rom on the stock rom and not knowing what i was doing, it crashed and i had to do a factory reset. luckily the bootloader came too and allowed me to do so. i have removed too much from it honestly. but it still works great. i uninstalled something that i shouldnt of and when i go to the settings menu, i can not enable unknown sources installation. before it has been enabled. but now after crash if i click on applications in the settings it just exits to the main screen of launcher. I have been able to work around that by using adb install (packagename.apk) and that worked fine. but for some reason overnight and not messing with anything it must of caught itself since unknown sources wasnt enabled. because now i can not install anything at all to it. if i use adb install (packagename.apk) it says it already exist installation failed from linux terminal. i used adb install -r (packagename.apk) and this had SUCCESS. however the games and apps do not show up in the app drawer of ANY launcher out of 4 or so.
i am really needing help on gettings things to show up when force installed with adb install -r into the app drawer, if this is the way i have to install stuff now.
also if possible i need to know if i can work with terminal to somehow enable unknown sources on the kindle fire itself. that would fix it all.
thanks for your time. any help appreciated
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 ...
EDIT 09/23/16
I finally found a permanent solution to how to change fire launcher on the Amazon Fire without root. It works on any version (FireOS 5.3.1) on any tablet variant (7, HD 8, HD 10 etc...).
You can read the detailed tutorial at http://forum.xda-developers.com/ama...-remove-default-launcher-amazon-fire-t3288310 but basically you run one command, must be done after reboot currently via adb shell:
Noval Launcher on Amazon Fire no-root:
Code:
nohup logcat -c; logcat | grep --line-buffered 'flg=0x10200000 cmp=com.amazon.firelauncher/.Launcher' | while read line; do am start com.teslacoilsw.launcher/.NovaLauncher; done &
That's it. Once you paste that into your adb shell you're done; you now have a default launcher programmatically set via ADB.
Optionally, you can install the modded firelauncher.apk so you can finally delete it without root .
(this is optional, you wont have any launcher after doing this! backup your old APK!!)
Code:
adb install -r -d com.amazon.firelauncher.apk
... as you can now see this will -r reinstall and -d downgrade the launcher, causing it to crash and never open.
Thanks for your support guys, I love android!
EDIT:
I have updated with a new method that is much better, the only negative to this new method is when you hit the home button, for a brief moment you see the firelauncher. Performance, speed, and bugs are perfect.
Just paste this code in adb shell, I'm working on setting up nohup to work with it, when you close adb it will stop working.. Going to bed for now though.
Code:
#!/bin/bash
am monitor | while read -r line; do
if [[ $line == *"firelauncher"* ]]
then
am start [B]com.newlauncher.launcher[/B]
fi
done
I'm new to the whole Android scene, and recently I had acquired an Amazon Fire HD 8. The only complaint about this tablet is the lack of Google Play and the horrible firelauncher. There is currently no root options available for the Fire HD modles 8 & 10, so I have spent the time to develop a temporary workaround.
Please take a quick look at the developmental thread I previously created so we can collaborate to make a more efficient version of this:
http://forum.xda-developers.com/hd8...zon-fire-hd-8-10-remove-firelauncher-t3286646
Disclaimer:
If you plan on installing new applications/packages while this script is running you may have a hard time. Installing packages may take 2-10 minutes, or maybe not at all!
If you experience any problems you can undo everything by running the undo script attatched (unix), or by typing "adb shell ps | grep /system/bin/sh", you will see anywhere from 2-10 processes listed. For each type "adb shell kill -9 <pid>", pid would be the process ID, should be the first number you see on each line.
There is a small chance when you press the home button that it will load the regular firelauncher, do not fret, try again and it will go to whichever launcher you previously selected.
Performance may be slightly altered, if it becomes too bad to use try adjusting the script and change the interval at which it loops (set to 20 by default).
This is an alpha experiment, and I am a noob with Android so please bare with me
This is a noobish approach to disabling the firelauncher (com.amazon.firelauncher.apk), please do not judge it, this is also my first time releasing something for Android.
If you are using a unix operating system (like Linux or Mac), I have compiled a script that does the work for you! Windows users will have to wait and do it manually since I am unfamilar with batch (would someone like to help with this?)
Automatic Tool (easy, linux, mac only)
Step One:
Download the two script attachments:
remove_default_launcher.sh - disables amazon's firelauncher
re-endable_firelauncher(undo).sh - reverts the process, if you have any issues
Step Two:
Run the following commands to make the scripts executable:
Code:
chmod +x remove_default_launcher.sh
chmod +x re-endable_firelauncher(undo).sh
Run the tool to remove amazon's nasty launcher!
Code:
./remove_default_launcher.sh
Step Three:
The script should automatically do everything, when it's done, check your Fire. Keep pressing the home button and switching between applications until you get the "Change default launcher" dialogue, make sure you have an alternative launcher installed beforehand or else you won't have a launcher! When it's all working how it should be go to step four!
Step Four:
Simply exit out of your terminal window, do not type anything, just exit ADB. The script will continue running!
This is what a successful window looks like, whenever you have confirmed it is working, close out of the ADB window and end that process.
{
"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"
}
Manually (harder, windows)
Step One:
Open up a new ADB shell window and type
Code:
adb shell
Step Two:
Once you are in the shell window, simply copy and paste this line of code and press return. It is just a simple bash script that loops the command "install -r -d "/system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk"" which will reinstall the firelauncher repeatedly, which temporary uninstalls it.
Code:
#!/system/bin/sh
nohup
while :
do
kill $!
sleep 1 & pm install -r -d "/system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk" & sleep 20; kill $!
kill $!
done &
exit
#press enter now
After pressing enter, you can watch it go to work, or you can close out of the adb window and unplug your device, it will continue to run until you kill the shell processes or reboot the device. Make sure you have an alternative launcher already installed so it can easily be set as default. EDIT: Reboot may not reset it, which is cool but could be annoying. To turn off this wonderful feature open up adb shell and use "ls | grep shell" and kill using "kill <pid>" all releated processes to /bin/shell or whatever. It may take up to a minute to reset.
If you have any issues at all please comment and I will send you a private message with detailed instructions catered to your specific issue!
If you are a dev, take a look at my unix auto-install script, it may help you figure it out yourself as well. I need someone who understands batch to help me write a windows version .
I literally spent about 45 minutes working on this noobish approach, so if you find bugs or want to modify the script, simply post in the comments your version and why you think it is more efficient. If you want to help make a dedicated and more efficient approach to this, check out the development thread here (there are alternative methods here too):
http://forum.xda-developers.com/hd8...zon-fire-hd-8-10-remove-firelauncher-t3286646
This appears to be a very stable system actually, I recommend everyone does this to the Fire HD tablets!
I hope this helps someone, if this helps you please give me a thanks so I know it
Confused as to why you'd post this here after using the correct forum section for the HD8 and 10 already.
Pond-life said:
Confused as to why you'd post this here after using the correct forum section for the HD8 and 10 already.
Click to expand...
Click to collapse
I was not sure whether it was the correct forum actually, it is stable enough to use for all versions of Fire now, so I posted for users who do not want to root their device, but hate the launcher. If you think it is in the wrong place I will remove it promptly. I actually did post this in the wrong spot.. It is in development instead... At least there will not be any flaming here
I have also noticed 6x more downloads in 1/5 of the time this thread has been posted compared to the other.
I have updated with a new method that is much better, the only negative to this new method is when you hit the home button, for a brief moment you see the firelauncher. Performance, speed, and bugs are perfect.
Just paste this code in adb shell, I'm working on setting up nohup to work with it, when you close adb it will stop working.. Going to bed for now though.
Code:
#!/bin/bash
am monitor | while read -r line; do
if [[ $line == *"firelauncher"* ]]
then
am start [B]com.newlauncher.launcher[/B]
fi
done
Good job on this!
glitch3yf0x said:
Good job on this!
Click to expand...
Click to collapse
No problem, hopefully I will find some more time to work on this in the future .
I am glad you like it.
nyln said:
If you are using a unix operating system (like Linux or Mac), I have compiled a script that does the work for you! Windows users will have to wait and do it manually since I am unfamilar with batch (would someone like to help with this?)
Click to expand...
Click to collapse
If you're still in need, I'd be happy to help port it to windows!
as for me,on windows, worked simply:
adb shell
pm hide com.amazon.firelauncher
to enable the fire launcher again,
adb shell
pm unhide com.amazon.firelauncher
This is one of the best thread for Fire OS world! Can't wait for you to perfect this.
P.S: Plz, someone here port it to Windows.
Does it work on Fire 5.3.1 ?
Please message me if you want me to keep working on this. After the root I stopped.
working great. And how to restore in the laucher back?
I am in Win10
update: After reboot, it turns back to original FireOS launcher. Is there a way to make it auto applied?
ttcontributor said:
update: After reboot, it turns back to original FireOS launcher. Is there a way to make it auto applied?
Click to expand...
Click to collapse
I will do some work on it. I am not an android developer, so maybe i will write a python application.
nyln said:
I will do some work on it. I am not an android developer, so maybe i will write a python application.
Click to expand...
Click to collapse
It's great to hear you still have your hands on this
nerakkaren said:
as for me,on windows, worked simply:
adb shell
pm hide com.amazon.firelauncher
to enable the fire launcher again,
adb shell
pm unhide com.amazon.firelauncher
Click to expand...
Click to collapse
If I am not mistaken, this will only bennefit those who have a rooted device. Fire 7 and HD 8 got updated via OTA removing my root. I am now working on a better way right now .
Please PM or Thank me if you're interested in this, it'll come out faster if I know people are waiting
I finally found a permanent solution to how to change fire launcher on the Amazon Fire without root. It works on any version (FireOS 5.3.1) on any tablet variant (7, HD 8, HD 10 etc...).
You can read the detailed tutorial at http://forum.xda-developers.com/ama...-remove-default-launcher-amazon-fire-t3288310 but basically you run one command, must be done after reboot currently via adb shell:
Noval Launcher on Amazon Fire no-root:
Code:
nohup logcat -c; logcat | grep --line-buffered 'flg=0x10200000 cmp=com.amazon.firelauncher/.Launcher' | while read line; do am start com.teslacoilsw.launcher/.NovaLauncher; done &
That's it. Once you paste that into your adb shell you're done; you now have a default launcher programmatically set via ADB.
Optionally, you can install the modded firelauncher.apk so you can finally delete it without root .
Thanks for your support guys, I love android!
Here is a teaser of my application:
[email protected]:/ $ adb install -r -d com.amazon.firelauncher.apk
/system/bin/sh: adb: not found
im getting this error, so i still c the default launcher for a couple of seconds before it goes to nova launcher
ahac85 said:
[email protected]:/ $ adb install -r -d com.amazon.firelauncher.apk
/system/bin/sh: adb: not found
im getting this error, so i still c the default launcher for a couple of seconds before it goes to nova launcher
Click to expand...
Click to collapse
You are already inside adb shell, type exit then type it again silly