Related
This will officially not work for 1.1
What it does:
Enables ADB via uRamdisk
Installs su and Superuser.apk
Installs Busybox
Installs Button Savior
Installs Go Launcher
Installs NookColor Tools (To Enable Non-Market Installs)
Installs Gapps (Gmail, Market, Youtube, Others)
System Files that get Modified:
/system/build.prop - Enabling Google Check In
packages.xml - Allows Gapps to install properly.
framework.jar - Should allow a proper Android ID to generate.
Changes:
June 24, 2011 -
Removed: Multitouch Permission
Added: Modified framework.jar
June 22, 2011 - Fixed: Script not running at boot.
June 20, 2011 - Initial Release
Before you begin:
You must already have a registered Nook Simple Touch
You must have a Gmail/Youtube linked Account. IF you used a Gmail account for B&N Registration you should use that one for this process.
You must either have dd (Linux) or WinImage (Windows) software.
You must have an external microSDCard reader or this will not work. Do NOT use the Nook Simple Touch.
You must have enough intelligence to follow instructions.
Let's get started:
Download TouchNooter from here: touchnooter-1-6-24.zip
Linux: Unzip and use dd if=touchnooter-1-6-24.img of=/dev/sdcard
Windows: Unzip and use WinImage to "Restore Virtual Hard Disk Image" to your SDcard.
Windows Alternative: https://launchpad.net/win32-image-writer/+download
Power off your Nook Simple Touch.
Insert TouchNooter SDcard into your Nook Simple Touch.
Power on your Nook Simple Touch.
You should see the screen "Rooted Forever".
It will boot like normal and you should be asked to select a launcher now. (If not use Button Savior to go home. This will bring up the launcher chooser.)
That was the hard part, now to the simple stuff.
Upon boot unlock your screen.
At the Android Welcome Screen skip Sign In.
Enable Location Services when given the option.
Connect to Wifi and launch Youtube from Go Launcher's App Drawer (Or the App Drawer of your Choice).
Click the Menu button (The right one in the middle of the status bar).
Select "My Channel" and Login using your Gmail Account.
Exit Youtube and Launch Gmail from "Extras".
Sync your Gmail Account and Exit. (If it fails to sync that is fine.)
Open up Market and Accept Terms and Service.
If you made it this far your nook should be successfully Rooted. Go Download an App to make sure.
Enable Non-Market Installs by running the NookColor Tools App.
If your Youtube fails to launch Uninstall and Reinstall Youtube from /data/app
Go to Settings > Device Info > SdCard > UnMount > Format
Thanks To:
Arnold Snarb - modified framework.jar
nemith - helping me figure out getting it to run at boot.
JesusFreke - For getting root.
MrMuffin - For the original Market Hack that we're using.
Currently Working On: TouchNooter 1.11.x
I've probably screwed up, but perhaps not too badly. Tried to follow all the steps and got the system files copied to media, and then to replace the main system files, but there I got confused. I ended up rebooting without attempting to install the youtube app, which I didn't find in the download. Even now, a lot looks like it is working, but I can't even attempt to sign in to google cause I can't get a keyboard to come up to allow me to enter my user name and password. Is there any help for me, or am I a total dunce needing to start over? thanks!
EDIT: I see I am screwed -- no keyboard is coming up for me anywhere. I guess I can go through a major reset but if anyone has a suggestion to just get the keyboard back I will appreciate it.
EDIT2: Well I got past that, simply chose multitouch keyboard instead of Gingerbread in NookColor Tools.
EDIT3: But now I am stuck again as I can't sign in to a google account... says can't establish a reliable data connection to the server, even though my wifi is fine. But at least at the moment everything else is fine, though the keyboard isn't working very well (but it does work; lots of ghosting)
An .img file is being uploaded for TouchNooter 1.6.20 It'll do all the copy and edit stuff, the only thing it can't do is create an android ID.
In the "GappsAndMore" there was some keyboards which were from the NC it was just a raw pull from AN. This is more refined with things that could cause issues removed. (Like Keyboards, Framework.jars from the NC, etc.)
william1853 said:
I've probably screwed up, but perhaps not too badly. Tried to follow all the steps and got the system files copied to media, and then to replace the main system files, but there I got confused. I ended up rebooting without attempting to install the youtube app, which I didn't find in the download. Even now, a lot looks like it is working, but I can't even attempt to sign in to google cause I can't get a keyboard to come up to allow me to enter my user name and password. Is there any help for me, or am I a total dunce needing to start over? thanks!
EDIT: I see I am screwed -- no keyboard is coming up for me anywhere. I guess I can go through a major reset but if anyone has a suggestion to just get the keyboard back I will appreciate it.
EDIT2: Well I got past that, simply chose multitouch keyboard instead of Gingerbread in NookColor Tools.
EDIT3: But now I am stuck again as I can't sign in to a google account... says can't establish a reliable data connection to the server, even though my wifi is fine. But at least at the moment everything else is fine, though the keyboard isn't working very well (but it does work; lots of ghosting)
Click to expand...
Click to collapse
I'd suggest a wipe and running TouchNooter... GappsAndMore had Keyboards and stuff in it and removed the stock keyboard =\
is a wipe in the nook touch holding down the power for 20 seconds?
No you need to do a complete wipe by triggering recovery, but I don't know how to trigger recovery yet.
oh well the perils of early adoption. I'll follow the thread with anticipation!
william1853 said:
oh well the perils of early adoption. I'll follow the thread with anticipation!
Click to expand...
Click to collapse
You could try 8 failed boots. Basically you power it on and then power it off before it fully boots. Do that 8 times and it might trigger recovery.
Confirmed this works great. I'm going to find a fix for the calendar.
GabrialDestruir said:
You could try 8 failed boots. Basically you power it on and then power it off before it fully boots. Do that 8 times and it might trigger recovery.
Click to expand...
Click to collapse
Recovery is holding the power button for 20+ seconds it will trigger recovery
xboxexpert said:
Recovery is holding the power button for 20+ seconds it will trigger recovery
Click to expand...
Click to collapse
Really? Is that from when it's off?
GabrialDestruir said:
Really? Is that from when it's off?
Click to expand...
Click to collapse
Not sure I have yet to try it but someone in the other thread said he called BN and they told him that and he did it.
xboxexpert said:
Not sure I have yet to try it but someone in the other thread said he called BN and they told him that and he did it.
Click to expand...
Click to collapse
I tried it and all I could get was it turning on and off
TouchNooter 1.6.20
This doesn't seem to work for me at all... I tried restoring the backup image and starting from scratch and it still will not work. I tried enabling Google Apps manually and it won't work for me either.
I think I'm done, if the 7th time wasn't the charm then I'm giving up for now...
MystaWright said:
This doesn't seem to work for me at all... I tried restoring the backup image and starting from scratch and it still will not work. I tried enabling Google Apps manually and it won't work for me either.
I think I'm done, if the 7th time wasn't the charm then I'm giving up for now...
Click to expand...
Click to collapse
I ran this on my Nook Touch and it worked just fine. Are you getting the "Rooted Forever" boot screen?
GabrialDestruir said:
I tried it and all I could get was it turning on and off
Click to expand...
Click to collapse
Didn't work for me either. 8 interrupted boots did.
i'm getting the rooted forever screen and then it just goes to the default stock home
any thoughts?
GabrialDestruir said:
I ran this on my Nook Touch and it worked just fine. Are you getting the "Rooted Forever" boot screen?
Click to expand...
Click to collapse
Same problem here... tried to return EVERYTHING to stock too.
yugoliang said:
i'm getting the rooted forever screen and then it just goes to the default stock home
any thoughts?
Click to expand...
Click to collapse
I did a reset of the device back to the out of the box experience, registered with my BN account, shut down and followed the directions to the letter. I had no luck at all. It just shows the Rooted Forever screen, then boots normally is if nothing happened.
Sorry Guys and Gals. Entirely my fault. It seems a combination of my own forgetfulness and bad scripting (I forgot proper codes and methods used in AN) caused this just to do nothing. I'm uploading a version as I'm typing this and will remove "BROKEN" from the title when it's up.
Still broken. init.rc isn't running it's script properly.
Script can be ran manually with:
Code:
adb shell sh /sdcard/nooter/tmp/scripts/Nooter
Will be working on getting it to trigger properly
It seems that Google just rolled out version 7.3.28 of their Google Play Services last night, and my Kindle Fire HD 8.9 has been popping up annoying Play Services have Stopped boxes constantly. Edit - confirmed this also is happening with 7.3.29. Also confirmed that this problem and fix works with the 7" Kindle fire HD tablets.
After pulling all my hair out, restoring to factory settings 3 times, figuring out how to re-root version 8.5.1, and then re-installing my old Google apps (from previous downloaded files), I have confirmed that Google will very quickly notice the outdated version and update to 7.3.28. Then the annoying pop-ups start all over again.
1) To fix the problem, you need a working version of Google Play Services. Go into Settings->Applications->Installed Applications and look for Google Play Services. Look for the version number in parenthesis, paying attention to the last 3 digits after the suffix. If it's like my Kindle 8.9, it will be -034. I confirmed that my Kindle did work on the previous version of Play Services (7.0.99), so what you need is to download that version for your Kindle. For the -034 version, the link is at:
(edit: I apparently can't post links, so I've modified the following to make it not look like a link, please edit and paste into your browser).
h t t p : / / www (dot) apkmirror (dot) com/wp-content/themes/APKMirror/download (dot) php?id=7772
2) Once downloaded, turn OFF Wi-Fi. Then, use ES3 file explorer to re-install this version from wherever you downloaded it to, overwriting the current version.
3) Next, create a folder in /data/app with name "com.google.android.gms-2" (not with the quote marks). You may see the actual .apk file already there ending in -1. Change permissions for this folder to rw-r-r. This folder should block the Google automatic update.
NOTE: This assumes your play services app is installed in this folder as "com.google.android.gms-1.apk". If it's not, one fix is to uninstall play services, then repeat the install in step 2. That should make it be named with the -1 suffix.
4) Repeat step 1 to confirm you're still on version 7.0.99. Select Clear data just to be sure the cache is cleared.
5) It should be safe to turn Wi-Fi back on. Launch Google Play Store, do a few things and confirm it works!
Really grateful for this, basically had the same issues as you on a Kindle 7", as Amazon store had popped up a few times with a permissions update I figured I'd suffered a clash/glitch. It wasn't until I turned on a dormant 8.9" and got the same error that I realised it was a wider issue and searched for your post.
Seems to have fixed the 8.9 first time, now back to the 7 and hope I haven't screwed it up too much trying multiple solutions.
Just a couple of notes from a novice, it's files that are located in data/app not folders? (update - confirmed need to create a folder not a file)
And the permissions correspond to Owner - Read, Write / Group - Read / Others - Read, being ticked only.
Another thing to look out for, when you're creating the dummy folder, watch out for autocorrect renaming parts of it to something else, maybe try copying and pasting the name.
:good: It worked perfectly! Thanks a lot!
P.S. i used this procedure in a kindle fire hd 7" (Tate)
This mostly worked, except I needed to create "com.google.android.gms-2.apk" to stop the updates. Worked on a Kindle 7 HD as well.
bobdob123usa said:
This mostly worked, except I needed to create "com.google.android.gms-2.apk" to stop the updates. Worked on a Kindle 7 HD as well.
Click to expand...
Click to collapse
Hi
I have the same issue with Play Services stopping, I downloaded the 7.0.99 -034 version which is correct for my 7 inch Fire HD.
I turned off wifi and installed it (over the existing) using the ES file manager and now have a new error "the processcom.google.process.gapps has stopped".
I read elsewhere this could be associated with the Downloads app but the problem is I cannot navigate anywhere on the device as the error reappears within a second of dismissing it
Any suggestions welcomed as I have a brick at present
There was an occasion when I got the persistent gapps error too, can you persevere and dismiss it enough to get to More/Applications/Installed Applications/Google Play services and Force Stop?
You can then confirm whether the old (working 7.0.99) version installed correctly and see if the error stops?
kinoogle said:
There was an occasion when I got the persistent gapps error too, can you persevere and dismiss it enough to get to More/Applications/Installed Applications/Google Play services and Force Stop?
You can then confirm whether the old (working 7.0.99) version installed correctly and see if the error stops?
Click to expand...
Click to collapse
Hi
Thanks for the response ..... I manages to force stop the Google Play services, 7.0.99 was installed
I have uninstalled the Play Service and the tablet seems to work with no errors but I guess I need to reinstall it again ....... or do I?
VeeMax said:
Hi
Thanks for the response ..... I manages to force stop the Google Play services, 7.0.99 was installed
I have uninstalled the Play Service and the tablet seems to work with no errors but I guess I need to reinstall it again ....... or do I?
Click to expand...
Click to collapse
I guess you need it if you want to use the Google store/synch? Maybe if you did a fresh install using this method the error would go away as it was something to do with the cache?
I have tried to do this method but still not working. It stays on 7.0.99 version but won't even open. I can't get it to open long enough for me to sign in. Any suggestions
---------- Post added at 02:34 AM ---------- Previous post was at 02:30 AM ----------
what folder are you creating the new folder in as well?
frosty1218 said:
I have tried to do this method but still not working. It stays on 7.0.99 version but won't even open. I can't get it to open long enough for me to sign in. Any suggestions
---------- Post added at 02:34 AM ---------- Previous post was at 02:30 AM ----------
what folder are you creating the new folder in as well?
Click to expand...
Click to collapse
I've done this method on both my 8.9" tablet, as well as two 7" tablets. The folder you create is in /data/app (you need to be root). Make sure you clear cache on the 7.0.99 version or things may still be out of sync.
In general, you'll have to fight through the clicking of OK on the annoying pop-ups. It may help to reboot the Kindle (hold down the power button, etc) to see if timing works better, and it may give you a window to uninstall quickly.
I created the folder in the data/app folder but now I'm not so sure I put it on the correct one. Can you tell me what folder exactly it goes into please?
frosty1218 said:
I created the folder in the data/app folder but now I'm not so sure I put it on the correct one. Can you tell me what folder exactly it goes into please?
Click to expand...
Click to collapse
Use ES File explorer. Back up all the way to the "/" directory. Under that you should see a folder called "data". Inside that, you should see a folder called "app". That is the /data/app folder. You'll know you're in the right place, because there should be a lot of installed .apk files in there. If you sort alphabetically, you should be able to find "com.google.android.gms-1.apk" (which corresponds to your installed play services file).
To block updates, make dummy named folders, such as "com.google.android-gms-2", and as another user pointed out it may help to also create "com.google.android.gms-2.apk". See the original post about setting permissions. Also, be careful about the autocorrect trying to change your filename on you. Once you finish, scroll through and compare names versus the installed play services apk (it should be -1, and you should have just made folders that have the same name, only with the -2).
should I download the google apk files from the kindle from apkmirror website or download them on my computer then transfer them to my kindle fire?
Once again,I have done all the steps shown and still, the moment I tap on google play store, it shows stopped error and returns to home screen. Does all the apk files need to change? The google framework apk, vending apk, google login apk, and the play store apk.
Please help
I keep getting the google play services have stopped working message. I would appreciate if someone could give me like a dummy version of this because I don't fully understand. So please make a video and reply it to me. Or just type something just please reply and help me do this.
I have tried this fix on a 7" fire HD tablet and I cannot get the fix to persist. Once I roll back with the correct 7.0.99 version with both a "com.google.android.gms-2" folder set with the correct permissions and a "com.google.android.gms-2.apk" installed in the data/apps folder things work well until a reboot. After a reboot I get upgraded to the .29 version of the apk and have to reinstall the working version again. I have tried every combination of folder/apk possibilities I can think of and I am still stuck. Any ideas?
Is there any update on how to keep the 7.0.99 Play Services version from upgrading? As mentioned above, I can get the 7.0.99 version to work, but only for a couple of days. Has anyone found a permanent solution?
mach76 said:
I have tried this fix on a 7" fire HD tablet and I cannot get the fix to persist. Once I roll back with the correct 7.0.99 version with both a "com.google.android.gms-2" folder set with the correct permissions and a "com.google.android.gms-2.apk" installed in the data/apps folder things work well until a reboot. After a reboot I get upgraded to the .29 version of the apk and have to reinstall the working version again. I have tried every combination of folder/apk possibilities I can think of and I am still stuck. Any ideas?
Click to expand...
Click to collapse
Is your "com.google.android.gms-2.apk" also a folder, or a dummy file? I've had success through reboots with two dummy folders: "com.google.android.gms-2" and "com.google.android.gms-2.apk". Make sure you uninstalled play services and re-installed 7.0.99 so that it takes the -1 suffix.
frosty1218 said:
Once again,I have done all the steps shown and still, the moment I tap on google play store, it shows stopped error and returns to home screen. Does all the apk files need to change? The google framework apk, vending apk, google login apk, and the play store apk.
Click to expand...
Click to collapse
No. You should only need to uninstall the Google Play Services, and that apk is the only one that needs re-installing. If the other files had previously been installed and worked fine, then they should still be ok.
See the note above about the two folders - for some installs, the dual dummy folder names seem to work better, and survive reboots.
I had to use r--r--r-- perms on the dummy file and folder to stop the updates. Otherwise outstanding help, thamks wolverine, kindle has stopped its google play seizures.
UPDATE: I have since added r--r--r-- on the actual 7.0.99 file (the -1.apk file) in order to prevent the updates (it managed to sneak in a damned update without it), so:
- follow ALL wolverine's excellent directions for installation, including turning off wifi, etc, take NO shortcuts
- create the dummy folder AND the dummy file (-2.apk)
- apply r--r--r-- permissions on ALL 3 ITEMS (dummy folder, dummy -2 file, and actual -1 file)
- enjoy a fully functional google play shizznitz on your rooted Fire.
Kingroot 4.5 form here works perfectly on fire os 4.6.3 (and it's in English now). If you think knigroot permission manager is annoying, you can replace it with SuperSu following the instructions here.
Just out of curiosity, Does anyone know what exploit kingroot uses to gain root on fire phone? I know they use several exploits from here and there, but I'm not sure which one.
I keep getting a failure. Even restored settings and still fails... bummer. 4.6.3 auto installed and removed my root, etc...
---------- Post added at 11:27 PM ---------- Previous post was at 11:01 PM ----------
Took a few tries, but think I got the trick.
1. Restore to 4.6.3
2. Enable usb debugging from Settings
3. IMMEDIATELY load ES File Explorer (and register your Phone through the normal process, don't skip and then do it from the App Store app)
4. Load KingRoot to the Downloads folder
5. enable 3rd party application installs in preferences
6. Install kingroot
7. Reboot
8. Run Kingroot
Worked for me.
Well, I never registered with amazon, Just sideloaded Google play and installed everything trough there. Anyway, Kingroot worked every time I tried. Maybe some problem with your internet connection?
I updated mine from 3.5.1 to 4.6.3, rooted with KingRoot 4.5 and then installed Super-Sume, didn't even reboot after KingRoot....but it seems to be working....now just gotta get Google Play installed
This also worked great on 4.6.4!!!!!!!!!!!!!!!!!!!!!!!!! THANK YOU!!!!!!!!!!!!!
Where?
plympton said:
I keep getting a failure. Even restored settings and still fails... bummer. 4.6.3 auto installed and removed my root, etc...
---------- Post added at 11:27 PM ---------- Previous post was at 11:01 PM ----------
Took a few tries, but think I got the trick.
1. Restore to 4.6.3
2. Enable usb debugging from Settings
3. IMMEDIATELY load ES File Explorer (and register your Phone through the normal process, don't skip and then do it from the App Store app)
4. Load KingRoot to the Downloads folder
5. enable 3rd party application installs in preferences
6. Install kingroot
7. Reboot
8. Run Kingroot
Worked for me.
Click to expand...
Click to collapse
Where in Settings do I find Enable USB Debugging?
jude525 said:
Where in Settings do I find Enable USB Debugging?
Click to expand...
Click to collapse
About device. Press any of those option 5-10 times until dev options shows up.
absolutely working fine, no need to do any steps, i just install the app n run and with in 22% it says root status accomplish
Thank u for the info
Which apps can I remove and how can imake sure that my Google services always work and no headaches
I just got a Fire Phone via the Ebay sale, and like many others, I wanted to set it up with Google Apps. I also wanted to keep the working camera and NFC, so I decided to stick with FireOS. Doing that took a lot of searching, and flipping through multiple threads. It can get a little confusing. So I've collected all the steps here to help others (and myself, in case I need to do this again in the future, when I inevitably break something while tinkering). I've written this from the perspective of someone who has purchased a brand new Fire Phone from a third-party seller.
PLEASE NOTE: Much of this is the work/discoveries of other forum members. I'll link out to the original posts whenever possible. Please thank those people accordingly!
1. When you first start up your phone, connect to WiFi, and let it go through the upgrade process to 4.6.4. Now is the time to register your phone with Amazon (by signing in with your Amazon account). You want that year of Prime, don't you?
2. SIM Unlock the phone (if you aren't using AT&T). It's easy!
a. Use a paperclip to pop out the SIM tray
b. Insert a non-AT&T nano-sized SIM card. (Mine came with an AT&T SIM in it. You can't use this card to SIM unlock)
c. A window should pop up, prompting you to enter the code that is on your box. Enter it.
d. Done!
3. Open Settings>Applications & Parental Controls>Prevent non-Amazon app installation. Turn App Installation to ON
4. Make sure ADB is set up on your computer. (this is an easy guide to follow if you don't already have it: http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378 )
5. Download the following file to your desktop computer:
GSM Unlocked Firmware (this is a 1.2gb file) (http://forum.xda-developers.com/showpost.php?p=62768812&postcount=2). Rename this update.bin, and put it into the folder where ADB is installed.Now we get our hands dirty:
6. If you are using Windows (I'm not), follow the directions that @Bingo Bronson posted here: http://forum.xda-developers.com/showpost.php?p=62768812&postcount=2. @DePingus also has an illustrated guide for ADB on Windows here: http://forum.xda-developers.com/showpost.php?p=62844581&postcount=14
6a. If you aren't using Windows, you can follow my steps (the same, just without all the Android SDK stuff, assuming you installed ADB in step #4)
a. Connect your phone to your PC & boot into recovery: When the phone is off, hold PWR + VOL. UP until the recovery screen appears
b. From the list, choose "Apply update from ADB"
c. In the command prompt, enter the following:
Code:
adb sideload path/to/update.bin
d. It should take a few minutes. When it's done, reboot your phone
NOTE: If for some reason this isn't working for you, @jack9955 has posted steps on how to downgrade via Safestrap here.
7. Open Settings>Device>Get Info About Your Fire Phone. Your current version will be listed under Software Version, and it should now be 4.6.3
At this point, you may need to repeat step 3. I didn't, but it's worth checking.
8. Open the Amazon app store (one last time) and download ES File Explorer.
9. In the Silk Browser, open up the following links and download the files:
KingRoot (http://forum.xda-developers.com/fire-phone/help/root-4-6-3-t3173322)
Updated Google Play Store files: (http://forum.xda-developers.com/fire-phone/general/google-play-store-4-6-1-version-4-apks-t3098592)
10. Open ES File Explorer, navigate to Download, and install KingRoot. Follow the directions to achieve root.
11a. At this point, some people like to remove KingRoot (out of security concerns) and replace it with SuperSu. I haven't done that yet, but you can follow the directions from @najoor here: http://forum.xda-developers.com/fire-phone/general/root-fire-phone-supersu-t3105546
12. Open ES File Explorer, navigate to Download, and unzip play.zip. Be sure to install the apks contained in the play.zip folder in the proper order (Thanks to @escape75 for these files)
1) Google Account Manager 4.4.2 (940549)
2) Google Services Framework 4.4.2 (940549)
3) Google Play Services 7.8.99 (2134222-036) - Updated
4) Google Play Store 5.8.8 - Updated
13. After installing, I rebooted into recovery again, and wiped the cache partition. I don't know if you need to, but engaging in good housekeeping is never bad.
14. You should have a Play Store icon in your app drawer now. Click it to open, and holy crap!! It works. Plug in your google account details.
Now it's time to keep Amazon from wrecking all your hard work. Steps 15 or 15a will block OTA updates of the OS.
15. Go to Settings>Applications & Parental Controls>Manage Applications. Click Filter By and select All. Find each of the files listed below, click it, and then click the "Disable" button on the next screen. Repeat for the other three files. (thanks @Bingo Bronson)
Amazon Device Client
DCP Platform Contracts
System Update
System Update (yes, there are two different files named system update. Freeze/Disable both)
15a. If you'd rather, you can do like I did, and use Titanium Backup Pro to freeze the above files.
16. Don't like the Launcher? Neither do I. I followed these directions to change out my launcher: http://spinyourfire.com/fire-phone-tips-and-tricks/fire-phone-launcher/ I use Home Switch from the Play Store. It will allow you to set your new launcher.
If you decide to use a new launcher, here's some info (courtesy @Bingo Bronson) which may help:
1. Settings>Display>Show Status Bar allows you to turn on the Status Bar at the top of the screen. This will help some launchers display properly.
2. Miss your NavBar / want some way other than Amazon gestures to navigate your phone? Try installing Ultimate Dynamic NavBar or Pie Controls.
NOTE: The new launcher will disable Tilt Left/Right on your home screen. In Amazon apps, the gesture will still work.
17. To sync your contacts/calendars/etc, go to Settings>My Accounts>Manage Email Accounts and add your Google account info.
a. Select that account, check sync calendar and sync contacts.
b. Set Inbox Check Frequency to manual.
c. In Email Settings, set everything to off, then click email notification settings, and set all of those to off.
BEWARE: HERE BE DRAGONS
Hi. Are you new to phone hacking? Then you should probably stop reading here. Following any of the links or info could (pretty easily) lead to bricking your phone. I won't even mess with most of this stuff, I'm just providing links for intrepid explorers who know what they are getting into, and are willing to risk it. SERIOUSLY, TURN AROUND HERE!
Seriously, you did all that work, and now you want to risk breaking it? Well yeah, me too. So let's cover our asses.
Backing Up with SafeStrap
First, let's back up what you've done. @ggow (to whom we all owe a debt of gratitude) has gifted us with SafeStrap, which allows us to boot into a version of TWRP recovery. From there, you can install his CM11 or SlimKat Roms, or use the backup feature, which is what we are about to do.
1. Install Safestrap from here http://forum.xda-developers.com/fire-phone/development/recovery-safestrap-v4-0-1-t3149888. In ggow's directions, it talks about 4.6.1, but I can confirm it works properly on 4.6.3.
2. Once you have booted into Safestrap, Click Backup and then back it up! (it took about ten minutes for me)
3. Of course, a backup won't do you any good if you don't have multiple redundancies. So plug your phone into your computer, open up a terminal/CMD prompt, and enter the following:
Code:
adb start-server
then
Code:
adb pull /sdcard/TWRP/ /path/to/your/backup/folder
after that runs for a while, you should see a message that says something along the lines of "12 files pulled. 0 files skipped"
Good! Now we are backed up, and we can start breaking stuff.
Turn on USB Debugging
1. Go to Settings>Device>Get info about your Fire
2. Tap "Model Number" seven or eight times, until the "Developer Options" button appears at the bottom of the list
3. Tap "Developer Options" and enable USB debuggingInstalling Xposed Framework
Xposed Framework allows you to install different modules that can change the look, feel and operation of your phone. Xposed works best on Vanilla Android, but we can definitely put it to good use here. Lifehacker has a great overview on Xposed. I'll just give you the basics here.
What you'll need: Root
1. On your phone, visit http://repo.xposed.info/module/de.robv.android.xposed.installer. Scroll down to the bottom of the page and click Show Older versions. You want the APK for version 2.6.1 (the most recent stable version)
2. After downloading, navigate to your Downloads folder and install the Xposed Apk.
3. Open Xposed and click Framework. It will show you that Xposed is currently inactive. Tap the install/update button.
4. Once installed, you must reboot your phone for Xposed to work.Congrats! Now with Xposed, you can really start customizing your phone. Check the forums...there is tons to discover and lots of people who know far more than I about how to use it. Just remember that a lot of the cosmetic stuff might not work on a Fire Phone. The modules I use are: ACDisplay, Amplify (paid version), AppOppsXposed, GravityBox, Greenify (paid version), PowerNap.
Installing a custom Lock Screen
Many of us on Android are used to custom lock screens, and haven't been thrilled with the Amazon Lock Screen. Through some trial and error, I've discovered how to swap out the Amazon Lock Screen for my lock screen of choice, ACDisplay. I haven't tried this with other 3rd party lock screens. Try following (and contributing to) this lockscreen thread to see any developments on other lock screens.
What you need: Xposed, Root, ES File Explorer (or another file explorer with root access)
1. Install ACDisplay (I sideloaded the APK, but it seems to work from the Play Store)
2. Open ES File Explorer, tap the hamburger menu, scroll down to Tools, and turn on Root Explorer
3. find the installed apk (com.achep.acdisplay-1.apk) in /data/app
4. rename it LockScreen.apk and move it to /system/priv-app/
5. Reboot
6. Open up AC Display and grant it access to Accessibility Settings and Notifications
7. In ACDisplay>Settings>Lockscreen move the slider to On and make sure that "Enable when no notifications" is ticked
8. Open Xposed and activate the ACDisplay module.
9. Reboot
10. I don't know if you need to, but I went to Settings>Lock Screen> Turn on Notifications... and made sure that notifications were off.
The Xposed integration seems to be the key. Now, when I reboot my phone, I'll get the original Amazon Lock Screen once (sometimes) and then ACDisplay pops up from that point on. Apparently, if you want a pin/password on the lock screen, you can still use the security features of the OS lockscreen.
Launchers with Widgets
One of the problems with custom launchers is that widgets don't seem to work on the Fire Phone. But @hmoobguy and @DePingus have figured out how to beat that in this thread. Just like with the lock screen, you'll have to move some files.
What you need: Root, ES File Explorer (or another file explorer with root access)
1. Install your launcher from the Play Store.
1a. If you haven't already, visit the Play Store on your desktop, look at the page for the launcher you just installed, and take note of what comes after 'id=' in the URL. That's the file name you'll search for.
2. Open ES File Explorer, tap the hamburger menu, scroll down to Tools, and turn on Root Explorer
3. find the installed apk for your launcher of choice in /data/app by searching for what came after 'id=' in step 1a.
4. move it to /system/priv-app/
5. Reboot
Note: you can also use Titanium to convert your launcher of choice into a system app.
Other Stuff
@Bingo Bronson has a ridiculously extensive list of Fire OS apps that can be disabled/frozen or deleted. Use at your own risk: http://forum.xda-developers.com/fire-phone/general/complete-app-list-replace-remove-t3132008
Hopefully this is helpful to others. I can add information as I go if new info (and new annoyances) come to light. Please let me know if there is anything I missed!
Thanks man! That's a good list there!
I gathered much of the information you have posted there last night and I have it at 4.6.3 with Google Play and a custom launcher.
My next challenge is a single lock screen. I have yet to actually root it however.
Which seems it will be required to get any further with the lock screen deal based off what I've read thus far.
Cheers!
"curious what adds the extra slide lock, is it the adding of a different Launcher or Home Switch? Even when using the FirePhone launcher again it remains."
Natet2003 said:
"curious what adds the extra slide lock, is it the adding of a different Launcher or Home Switch? Even when using the FirePhone launcher again it remains."
Click to expand...
Click to collapse
I'm not quite sure what you mean here. I'm messing with the lock screen myself, haven't quite got it figured out yet. I use AC Display, and have been trying to freeze various apps listed in the App List post (at the bottom of the walkthrough under "HERE BE DRAGONS"). I can shut off the Amazon lock screen, but for some reason, my lock screen only works every other time. If I let it sit for a while and then unlock it, I just get the woven graphite background and nothing else. I have to turn off the screen, turn it back on again, and then my lock screen will work. I'm assuming it has something to do with the system putting the app to sleep.
Natet2003 said:
My next challenge is a single lock screen. I have yet to actually root it however.
Which seems it will be required to get any further with the lock screen deal based off what I've read thus far.
Click to expand...
Click to collapse
This thread has info on changing the lockscreen.
http://forum.xda-developers.com/fire-phone/help/fire-phone-lock-screen-t2982798/page5
You do need root. Install the new lockscreen (many people were using Next Lock Screen). Use a root file explorer to delete /system/priv-app/LockScreen.apk (make a backup first). Then move whatevernewlockscreen.apk from /data/app to /system/priv-app, rename it to LockScreen.apk and reboot.
I was having issues with the alarm clock and then I screwed up all the lockscreens. I gave up trying to fix my mess and just took the opportunity to install 4.6.3. That fixed all my issues and put me back to the stock crappy lockscreen, which I'm still running.
munkymack said:
I'm not quite sure what you mean here. I'm messing with the lock screen myself, haven't quite got it figured out yet. I use AC Display, and have been trying to freeze various apps listed in the App List post (at the bottom of the walkthrough under "HERE BE DRAGONS"). I can shut off the Amazon lock screen, but for some reason, my lock screen only works every other time. If I let it sit for a while and then unlock it, I just get the woven graphite background and nothing else. I have to turn off the screen, turn it back on again, and then my lock screen will work. I'm assuming it has something to do with the system putting the app to sleep.
Click to expand...
Click to collapse
I think I found what it was. I had "C Launcher" installed. It does an iPhone styled sliding lock screen that even when I swapped to another Launcher the lock screen kept activating. (So I had two screens to bypass) When I had experimented with GO Locker it added yet another screen to those so 3 screens!
So once I've removed CLauncher and GO Locker I've not just have a single screen, which is FireOS default lock screen.
Great instructions, well consolidated--thanks!!
Questions: 1. What's the reason you went through all the updates, all the way to 4.6.4 and then downgraded to 4.6.3. Could you just not have installed 4.6.3 from the beginning? 2. Also, why version 4.6.3? Is that the version on which google play works the best?--the reason I ask is because I too have read so many posts on this site and I have come to perceive that Google play still does not work perfectly on any of the versions!. Hopefully my perception is wrong and I can proceed with your consolidated instructions. Can you please post updates as the days go by on how its all working. Thanks.
dannyol said:
Questions: 1. What's the reason you went through all the updates, all the way to 4.6.4 and then downgraded to 4.6.3. Could you just not have installed 4.6.3 from the beginning? 2. Also, why version 4.6.3? Is that the version on which google play works the best?--the reason I ask is because I too have read so many posts on this site and I have come to perceive that Google play still does not work perfectly on any of the versions!
Click to expand...
Click to collapse
I went to 4.6.4 simply because my phone automatically updated from 3.5.0>4.6.1>4.6.4 when I connected it to wifi, and the directions I'd found showed how to downgrade from 4.6.4 (which is AT&T specific) to 4.6.3 (gsm unlocked).
The reason I chose to downgrade is because Play store doesn't work on 4.6.4...it keeps breaking. On 4.6.3, that's not the case (so far); Play Store (and even more important, Play Services, which is necessary for most Google apps) is working exactly like it should be. Might it break in the future? Yeah, probably. But if / when it does, I'll try and update the post (assuming that a fix gets found).
DePingus said:
This thread has info on changing the lockscreen.
http://forum.xda-developers.com/fire-phone/help/fire-phone-lock-screen-t2982798/page5
You do need root. Install the new lockscreen (many people were using Next Lock Screen). Use a root file explorer to delete /system/priv-app/LockScreen.apk (make a backup first). Then move whatevernewlockscreen.apk from /data/app to /system/priv-app, rename it to LockScreen.apk and reboot.
Click to expand...
Click to collapse
Just a heads up, DePingus and I have been discussing this on the linked thread, and the above instructions DO NOT work. LockScreen.apk does not exist in /system/priv-app/ on 4.6.3. At this point in time, there is not a way to completely replace the Amazon lock screen with a custom lock screen.
This is a good guide.
Just FYI, you don't have to enable USB debugging to root with KingRoot. And, more importantly, you don't have to be rooted or enable USB debugging to install 4.6.3, Google Play Services, or alternate launchers. Instead of adb push, you can just copy the apks over using your favorite method (USB, OneDrive, direct download) and then run to install. Come to think of it, you probably should move rooting and USB debugging into the "here be dragons" section.
Is it safe to update the play store when it asks?
MrPaulAR said:
Is it safe to update the play store when it asks?
Click to expand...
Click to collapse
Yes, as far as we know (for v. 4.6.3) Play Store can be updated and will still work, same with Play services.
New fire phone with version 3.5-rooted and now at a stand-still
Bingo Bronson said:
Yes, as far as we know (for v. 4.6.3) Play Store can be updated and will still work, same with Play services.
Click to expand...
Click to collapse
I too got my new fire phone on ebay. The fire phone has version 3.5. I read that it was a rootable version, so I proceeded to root the phone via towelroot . I have supersu installed also. I have verified root via an app and the phone is now successfully rooted. Now I am puzzled as to what I should do with the fire phone with version 3.5 and am at a stand-still!!.
Questions:
1. Can I update to version 4.6.3 from here without loosing root?
2. Will updating to version 4.6.3 in its present rooted condition cause any harm (i.e bricking) ?
4. If I need to remove root and supersu in-order to update the phone to version 4.6.3, how do I do that?
3. The reason for these questions is because I am assuming that I need to update to version 4.6.3 to install google apps.
Can you help me proceed along from this standstill that I find myself in!
Thanks
dannyol said:
I too got my new fire phone on ebay. The fire phone has version 3.5. I read that it was a rootable version, so I proceeded to root the phone via towelroot . I have supersu installed also. I have verified root via an app and the phone is now successfully rooted. Now I am puzzled as to what I should do with the fire phone with version 3.5 and am at a stand-still!!.
Questions:
1. Can I update to version 4.6.3 from here without loosing root?
2. Will updating to version 4.6.3 in its present rooted condition cause any harm (i.e bricking) ?
4. If I need to remove root and supersu in-order to update the phone to version 4.6.3, how do I do that?
3. The reason for these questions is because I am assuming that I need to update to version 4.6.3 to install google apps.
Can you help me proceed along from this standstill that I find myself in!
Thanks
Click to expand...
Click to collapse
I did the same thing when I first got mine, so I understand where you are coming from. After reading around on the forum, I saw that 4.6.3 could work with Play Store / Services, so I just did a straight up OS update. I didn't unroot or anything, and suffered no problems. My phone updated from 3.5 to 4.6.1, and then to 4.6.4. From that point, I downgraded to 4.6.3 and then proceeded with the steps in the guide.
As far as I can tell, you WILL lose root in the update, but you can use Kingroot to re-apply root.
Will this work on a Fire tablet? Would I just not run the GSM unlocked firmware part?
Thanks
jimbobalu said:
Will this work on a Fire tablet? Would I just not run the GSM unlocked firmware part?
Thanks
Click to expand...
Click to collapse
I have absolutely no idea. If it does work, let me know. I've got one of the new $50 fire tablets coming at the end of the month.
DePingus said:
Just FYI, you don't have to enable USB debugging to root with KingRoot. And, more importantly, you don't have to be rooted or enable USB debugging to install 4.6.3, Google Play Services, or alternate launchers. Instead of adb push, you can just copy the apks over using your favorite method (USB, OneDrive, direct download) and then run to install. Come to think of it, you probably should move rooting and USB debugging into the "here be dragons" section.
Click to expand...
Click to collapse
That's a good point. I've been doing this long enough that rooting is something I do without a second thought, but for beginners, it opens up the door to a host of problems. I'll do a reorganization next time it's slow around the office.
Thank you for the step-by-step guide. It was incredibly helpful and everything worked...expect for downgrading to 4.6.3. It may be because I'm on a Mac, but nothing I tried seemed to work. That is until I found this website that worked to perfection. Hopefully anyone else on a Mac finds it useful as well.
And apparently because I'm a new user, I can't post URL's, so here's the closest I can get you
seo-michael.co.uk/how-to-setup-adb-on-os-x
This phone is dirty cheap now.
i might grab one of these . here in Europe
cheers
Be sure and check the LTE bands before you do. You may not be able use high speed data there.
EDIT: I looked at the work in your signature. I'm pretty sure you know exactly what you are doing / getting yourself into if you do pick one up. I'm just trying to be super newbie friendly over here, hence my response.
Osufever said:
Thank you for the step-by-step guide. It was incredibly helpful and everything worked...expect for downgrading to 4.6.3. It may be because I'm on a Mac, but nothing I tried seemed to work. That is until I found this website that worked to perfection. Hopefully anyone else on a Mac finds it useful as well.
Click to expand...
Click to collapse
Yeah, ADB is different on every system, and can be a pain in the ass to set up. The Lifehacker article I linked should cover everything, but if Mac users want to delve a little deeper, then the link you followed is a good way to go. I'm glad you were able to get things working!
Please Read: I am making this post to help my fellow hd 8 & hd 10 kindle users out with things I have found working and useful to me that I got working with my kindle. Please remember that doing this stuff can be dangerous unless you know what you're doing. Enjoy my findings!
Ready to ROOT your device?!
Follow these step's and I'll try making this as simple as possible.
Step 1. First we're going to install adb and get shell command working. This youtube video is probably the best visual way of getting it done. Only watch 3 minutes and 37 seconds of it, Skip the rest of the video. Click HERE. (give him a thumbs up for making the video).
Now open up Command prompt and type
Code:
adb devices
It should show a 16 digit serial key with "device" to the right. SUCCESS!
Step 2. Now let's run RootJunky's script. Download and extract the files, Click HERE. Run "1-Install-Play-Store.bat" file and let it load. It should list your device serial key and load up to the main menu page. Follow the order on the menu from 1 to 4. Now this was made for the fire hd 7" tablets but some of it works and some might not, I had a problem with ads loading up on lockscreen but found another way to disable them which is under "Disabling Amazon Services" down below.
Step 3. Let's get ROOT! We are going to install KingRoot and run it, kingroot will also install purify which is a nice handy program but you can remove it if you want later on. Now once you run KingRoot its going to search for the best possible method to root your device, it may or may not find a way but there should be a second option to install root. Do it. Some people have found that you may have to try multiple times to root to get a success or try updating the google framework through the play store. (My google framework is V4.4.4-1227136)
I have attached the kingroot apk down below or you can download kingroot from there website. Click HERE. (If you have any problems please post it and we may be able to help.)
Now let's disable some thing's we may find useless..
Disable the lockscreen
Open up command prompt. Type in "adb shell", Then type in "su"
Then copy this into command prompt.
Code:
sqlite3 /data/system/locksettings.db "UPDATE locksettings SET value = '1' WHERE name = 'lockscreen.disabled'"
You will not get a confirmation, now type "exit", then type "reboot".
Let the device reboot and enjoy! Now install a new lockscreen.
Want it back?
Code:
sqlite3 /data/system/locksettings.db "UPDATE locksettings SET value = '0' WHERE name = 'lockscreen.disabled'"
*This is messing with the sqlite in the actual android system files, please becareful and don't go around changing values in system files.
Disable Amazon's FireLauncher and replace it with Google Now Launcher
Note:
Load up ES Explorer, make sure it has root enabled in settings.
Before you run this command please download a new launcher and either install it normally or you can copy the apk file into the "system/app" folder and chmod the app to "-rw -r -r" in properties. Once the apk file is in the "system/app" folder, you can either install it from that location or disable Fire Launcher, reboot, and the app should auto install and load.
*Installing Google Now Launcher requires Google app from marketplace(Link below). Now Launcher allows you to use widgets. If you use Google now launcher please keep a back up launcher like nova launcher just in case until you get now launcher working. Google now launcher is tricky.
Open Command Prompt.
Type in "adb shell". Then type in "su".
Then type into command prompt,
Code:
pm disable com.amazon.firelauncher
After reboot if you get no launcher don't worry. Just enable firelauncher and install a new launcher(IE nova launcher) and then disable firelauncher. (Try updating the google framework.)
*To Re-enable, replace disable with enable.
*Don't forget to type in "exit" into command prompt twice when you are done and or before unplugging your usb.
Disable Amazon's OTA(over the air) updates
Go in to ES Explorer(set root access).
Now in ES Explorer go to system/etc/security
locate "otacerts.zip" and I made a copy of it and renamed it to "otacerts.zip.backup" just in case i needed it.
AND..
Now in Command Prompt, type "adb shell", type "su".
Then type into command prompt,
Code:
Pm disable com.amazon.device.software.ota
Pm disable com.amazon.settings.systemupdates
Hopefully this disables all the updates! Enjoy!
Google Play Store not working?
Solution 1. (¿GotJazz?)
Open up Kingroot's Purify app.
Try putting Google Account Manager and Google Services Framework on the Purify Whitelist.
Solution 2.
Load up Command Prompt.
Then type in "adb shell". Then "su".
Code:
pm grant com.google.android.gms android.permission.INTERACT_ACROSS_USERS
You will not get a notification that it worked but it does.
Open Google Play or Reboot device. If that doesn't work, read on..
Solution 3.
Re-install Google applications
Go into system settings >> apps & games >> manage all applications
I then went into every google application(this will help remove any settings saved and email addresses) and cleared the data and cache of each app.
After that was done, I then uninstalled each of these apps,
"Google Account Manager, Google Play Services, Google Play Store, and Google Services Framework".
After uninstalling those, run the rootjunky's script(link located below) and install the play store which is option 2 I believe.
Also remember to turn off google play store auto updates!
Disabling Amazon Services
Start up Command Prompt.
Type in "adb shell". Then "su".
Then type into command prompt.
Code:
pm disable (app name(IE. com.amazon.ags.app))
*To Re-enable, replace disable with enable.
List of Amazon apps that are okay to remove.
Code:
com.amazon.ags.app
com.amazon.cloud9
com.amazon.cloud9.kids
com.amazon.dp.contacts
com.amazon.dp.fbcontacts
com.amazon.firelauncher
com.amazon.geo.client.maps
com.amazon.geo.mapsv2
com.amazon.geo.mapsv2.services
com.amazon.kcp.tutorial
com.amazon.kindle
com.amazon.kindle.kso
com.amazon.kor.demo
com.amazon.parentalcontrols
com.amazon.photos
com.amazon.photos.importer
com.amazon.tahoe
com.amazon.unifiedshare.actionchooser
com.amazon.unifiedsharefacebook
com.amazon.unifiedsharegoodreads
com.amazon.unifiedsharesinaweibo
com.amazon.unifiedsharetwitter
com.amazon.webapp
com.amazon.webview
com.amazon.windowshop
com.amazon.pm
com.amazon.recess
com.amazon.socialplatform
com.amazon.zico
com.audible.application.kindle
com.audible.application.store
com.goodreads.kindle
Optional
Don't have prime? Please continue + more.
Code:
com.amazon.mp3 -amazon music player
com.amazon.mw -removes the firefly cam app
com.amazon.mw.sdk -part of the firefly app?
com.amazon.avod -amazon video app, i don't have prime, useless to me..
com.amazon.kindle.personal_video -the amazon/system video app, I replaced this with mx player.
com.amazon.csapp -amazon help app
com.amazon.application.compatibility.enforcer -not sure what this does
com.amazon.android.marketplace -amazon marketplace
com.amazon.camera -stock camera app, install a new one from play store
com.amazon.dynamicupdationservice -not sure what this is or if this is part of amazon updates
com.amazon.platform.fdrw -part of amazon app & services?
com.android.contacts -remove, no reason for contacts, up to you
com.android.calendar -android calender
com.android.deskclock -remove if you don't need alarms/clocks/timers/etc
com.kingsoft.office.amz -not sure what this is yet but im sure its useless
com.nuance.swype.input -yup, unless you like swype
jp.co.omronsoft.iwnnime.mlaz -not sure what this does?
*Don't forget to type in "exit" into command prompt twice when you are done and or before unplugging your usb.
Links:
Changing the DPI(HERE).
Google App v5.9.27.19.arm(300600996)(HERE).
Replace KingRoot with SuperSU(HERE).
Rootjunky's install play store script(HERE).
Contributors:
madsc13n41s4, sd_shadow, Selexo
Downloaded kingroot apk, installed, tried root twice, confirmed via superuser from chainsDD, backed up special offers from titanium backup, uninstalled special offers, great fully rid of ads on my lockscreen.
madsc13n41s4 said:
Downloaded kingroot apk, installed, tried root twice, confirmed via superuser from chainsDD, backed up special offers from titanium backup, uninstalled special offers, great fully rid of ads on my lockscreen.
Click to expand...
Click to collapse
Does your wallpaper on the lockscreen change? I have yet to look into getting it changed, about to look in to a new lock screen as well. Also don't forget to stop ota updates from amazon.
EDITED MAIN POST. Will add more soon.
kanderson88 said:
Does your wallpaper on the lockscreen change? I have yet to look into getting it changed, about to look in to a new lock screen as well. Also don't forget to stop ota updates from amazon.
Click to expand...
Click to collapse
Yeah, its not the default wallpaper, and changes on its own with generic backgrounds. Did forget about ota, powering off until I have the time, I'm elbows deep in a Ford Probe project for the time being. Thanks so much for finding this, hopefully I get time to really contribute soon. Glad to confirm
madsc13n41s4 said:
Yeah, its not the default wallpaper, and changes on its own with generic backgrounds. Did forget about ota, powering off until I have the time, I'm elbows deep in a Ford Probe project for the time being. Thanks so much for finding this, hopefully I get time to really contribute soon. Glad to confirm
Click to expand...
Click to collapse
You're very welcome sir. So happy I found out that kingroot worked. I am currently looking into getting a new lock screen and once I post my findings I'll let y'all see as well as changing the lock screen wallpaper. As well for the fixing google play store I am still currently having problems after that adb command, it worked for a good minute longer than usual.
kanderson88 said:
You're very welcome sir. So happy I found out that kingroot worked(credit). Anyways I am currently looking into getting a new lock screen and once I post my findings I'll let y'all see as well as changing the lock screen wallpaper. As well for the fixing google play store I am still currently having problems after that adb command, it worked for a good minute longer than usual.
Click to expand...
Click to collapse
I would install an opengapps.org package with FlashFire (Arm, 5.1.1, nano or pico)
Flashfire will install Google framework and extra support files, that should allow playstore to work better.
should work fine, but no guarantees
How to Use FlashFire App
Sent from my KFFOWI using XDA Labs
sd_shadow said:
I would install an opengapps.org package with FlashFire (Arm, 5.1.1, nano or pico)
Flashfire will install Google framework and extra support files, that should allow playstore to work better.
should work fine, but no guarantees
How to Use FlashFire App
Sent from my KFFOWI using XDA Labs
Click to expand...
Click to collapse
Yeh I need to look into flashfire, I used rootjunky's script to install it. Thanks for the idea, I'm gonna check it out.
I don't think I am going to use flashfire. Seems really risky of bricking me device. I'm going to try installing the apps manually or through adb. I'll keep doing some research on flashfire though. Thanks
kanderson88 said:
You're very welcome sir. So happy I found out that kingroot worked(credit). Anyways I am currently looking into getting a new lock screen and once I post my findings I'll let y'all see as well as changing the lock screen wallpaper. As well for the fixing google play store I am still currently having problems after that adb command, it worked for a good minute longer than usual.
Click to expand...
Click to collapse
Yeah, I had to cobble together my own Play Store solution. The differences in the versions of the apks used together really matters it seems. Luckily, I haven't had any issues since I got it running. I would highly recommend turning off Play Store automatic updates as App Store versions of certain apps are intentionally out of date as per compatibility. Eg, Facebook.
Holy crap opening up TB I can not wait until someone comes up with a list of **** thats safe to freeze/remove, so much amazon crap on this thing!
madsc13n41s4 said:
Yeah, I had to cobble together my own Play Store solution. The differences in the versions of the apks used together really matters it seems. Luckily, I haven't had any issues since I got it running. I would highly recommend turning off Play Store automatic updates as App Store versions of certain apps are intentionally out of date as per compatibility. Eg, Facebook.
Click to expand...
Click to collapse
Thanks didnt think about stopping the auto updates.
Smart move. Thanks.
mikek9 said:
Holy crap opening up TB I can not wait until someone comes up with a list of **** thats safe to freeze/remove, so much amazon crap on this thing!
Click to expand...
Click to collapse
What a great Idea, I will make a list of some things. Give me a day. Bed time.:crying:
mikek9 said:
Holy crap opening up TB I can not wait until someone comes up with a list of **** thats safe to freeze/remove, so much amazon crap on this thing!
Click to expand...
Click to collapse
This is what I've safely removed so far, leaving Prime included services.
com.amazon.ags.app
com.amazon.cloud9
com.amazon.cloud9.kids
com.amazon.dp.contacts
com.amazon.dp.fbcontacts
com.amazon.firelauncher
com.amazon.geo.client.maps
com.amazon.geo.mapsv2
com.amazon.kcp.tutorial
com.amazon.kindle
com.amazon.kindle.kso
com.amazon.kor.demo
com.amazon.photos
com.amazon.photos.importer
com.amazon.tahoe
com.amazon.unifiedsharefacebook
com.amazon.unifiedsharegoodreads
com.amazon.unifiedsharesinaweibo
com.amazon.unifiedsharetwitter
com.amazon.webapp
com.android.contacts
com.audible.application.kindle
com.audible.application.store
com.goodreads.kindle
Google Now Launcher doesn't start with Fire Launcher enabled/installed, but takes right over when disabled/uninstalled.
madsc13n41s4 said:
This is what I've safely removed so far, leaving Prime included services.
com.amazon.ags.app
com.amazon.cloud9
com.amazon.cloud9.kids
com.amazon.dp.contacts
com.amazon.dp.fbcontacts
com.amazon.firelauncher
com.amazon.geo.client.maps
com.amazon.geo.mapsv2
com.amazon.kcp.tutorial
com.amazon.kindle
com.amazon.kindle.kso
com.amazon.kor.demo
com.amazon.photos
com.amazon.photos.importer
com.amazon.tahoe
com.amazon.unifiedsharefacebook
com.amazon.unifiedsharegoodreads
com.amazon.unifiedsharesinaweibo
com.amazon.unifiedsharetwitter
com.amazon.webapp
com.android.contacts
com.audible.application.kindle
com.audible.application.store
com.goodreads.kindle
Google Now Launcher doesn't start with Fire Launcher enabled/installed, but takes right over when disabled/uninstalled.
Click to expand...
Click to collapse
Thanks for this. I'll consider when and if i make a cleaned up ROM/Bin
Yeah you must hide fire launcher through adb in order to use any launcher. Thanks for the list. I've been trying to figure out how to disable the lock screen all day and it seems impossible. Idk but maybe someone someday will provide a modified settings app. Idk.
madsc13n41s4 said:
This is what I've safely removed so far, leaving Prime included services.
com.amazon.ags.app
com.amazon.cloud9
com.amazon.cloud9.kids
com.amazon.dp.contacts
com.amazon.dp.fbcontacts
com.amazon.firelauncher
com.amazon.geo.client.maps
com.amazon.geo.mapsv2
com.amazon.kcp.tutorial
com.amazon.kindle
com.amazon.kindle.kso
com.amazon.kor.demo
com.amazon.photos
com.amazon.photos.importer
com.amazon.tahoe
com.amazon.unifiedsharefacebook
com.amazon.unifiedsharegoodreads
com.amazon.unifiedsharesinaweibo
com.amazon.unifiedsharetwitter
com.amazon.webapp
com.android.contacts
com.audible.application.kindle
com.audible.application.store
com.goodreads.kindle
Google Now Launcher doesn't start with Fire Launcher enabled/installed, but takes right over when disabled/uninstalled.
Click to expand...
Click to collapse
Did this show any improvements on the operating system? IE faster loading, battery power, etc etc..
What I'd like is as near as pure android as possible. So the more input the better.
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
Try freezing apps like those listed. Report back
---------- Post added at 10:21 PM ---------- Previous post was at 10:19 PM ----------
None of those apps look crucial to me. Get rid of them, let me know here.
technope said:
What I'd like is as near as pure android as possible. So the more input the better.
Click to expand...
Click to collapse
I agree, I don't know if i want to completely get rid of the fire os just in case and possibility of bricking when booting up a new rom and plus no boot image yet.
None of those apps look crucial to me. Get rid of them, let me know here.
Click to expand...
Click to collapse
Will do
Don't forget
"com.amazon.mp3" and replace with different music app
"com.amazon.mw" removes the firefly cam app.
"com.amazon.avod" -amazon video app, i don't have prime, useless to me..
"com.amazon.kindle.personal_video" the amazon video app, i replaced this with mx player.
"com.amazon.csapp" amazon help app
I disabled them all, ill keep you updated if i see a performance boost or battery boost.
Freshened up the main post! Hope its more readable.
Also note, multiple user profiles seem to break with the disabled apps in my list, personally believe it to be Fire Launcher's fault, probably responsible for handling the switch over, but I don't know too much about 5.1.1
madsc13n41s4 said:
Also note, multiple user profiles seem to break with the disabled apps in my list, personally believe it to be Fire Launcher's fault, probably responsible for handling the switch over, but I don't know too much about 5.1.1
Click to expand...
Click to collapse
can you try disabling all those but leaving firelauncher enabled? lets see if it gives you error's, if it doesnt, instead of disabling firelauncher, use the hide command instead of disable and see if that works. I would like to know what app is in charge of multiprofiles..
Please look at section for disabling amazons ota updates, added more to it! Thanks.