Database Users

[FireOS 5.x + ROOT] Quickly switch to Amazon UI and back:

Update2: Updated and tested under Lollipop (Sept 2015 FireOS 5.0.1 version for Fire HD 7 2014 [5.2.2u2], and should work with Fire 7 2015)
Given that a Fire tablet with Amazon experience is a terrible thing to waste, these are scripts to switch from and to Amazon launcher both under FireOS 4.5.x and Lollipop. Along with the launcher this disables a lot of battery sucking Amazon apps (the enabling script revives all of this goodness back).
The key stuff in scripts is the launcher block/unblock. I block other apps too because some of them seem to wake up a lot ("Wakelock detector" tells me this), so why not make them less obnoxious when you are not running Amazon experience ...
Naturally, you do need ROOT (how to root FireOS is a subject of other guides).
I assume you have Nova Launcher or free Google Now Launcher (on Lollipop installed as a system app in order to have Widgets working). If your Amazon launcher apk file is renamed, rename it back (verify that you do have the proper /system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk ). Do make sure that you have an alternative launcher (besides the stock Amazon one !!!). Also, make sure that your adb is authorized in order to enable you to unblock the Amazon launcher in case you get the permanent Fire logo.
Go ahead install Gscript ( https://bitbucket.org/Equidamoid/gscript/downloads ). Copy either fire_on_off.zip (for FireOS 4.5.x), or fire_on_off_511b.zip (for FireOS 5.x - Lollipop) to /sdcard/gscript, and unzip scripts right in there. In "Gscript", tap the 3 dots at the bottom right corner, tap "Add script", tap "Load File", tap root required, first choose the disabling script, then repeat for the enabling script. All set.
In Nova, long tap on an empty area, it'll offer to create Shortcut. Choose Gscript/"Kindle block". Repeat for "Kindle unblock".
Then in "Nova", tap "Kindle unblock". It'll get you into Kindle Launcher, at which point you have 100% Amazon experience. Once you do your thing, and want to go back, launch/switch to "Nova", and tap "Kindle block". At this point you are back to more stock like Android.
To give proper credit, this approach was proposed by DoLooper ( http://forum.xda-developers.com/showpost.php?p=61089153&postcount=29 , and some good suggestions in a reply to this post) .

bibikalka said:
So why not switch quickly to and away from stock Amazon UI ?
Click to expand...
Click to collapse
Thanks for the post and the scripts! The shortcut makes it so easy to switch between launchers, and blocking the other packages is a great idea.
In case it's not obvious to casual reader, this lets you run any adb shell command(s) from a homescreen shortcut (and scripts that do other things, too, of course). Here are a few related tips:
Launcher: This works with any launcher that allows shortcuts on the homescreen
Gscript: I suggest using this Gscript app instead of getting it from play store. Play store version is older and less stable, and I don't think it closes after running the shortcut.
Adding the scripts (alternate method): Create a folder named "gscript" in sdcard and put bibikalka's scripts in there. Then in Gscript app, tap (3-dot) menu button, "Add script," "Load file" and the scripts will be listed.
Edit scripts from Gscript: Long press on the script name and choose Edit.
People using Freetime should edit the scripts and delete lines for amazon.kindle.kso and Tahoe. Blocking these causes bootloop.

I'm on 4.5.3 root with Google play, does it Worth upgrading ?

This works with any Fire OS; don't need 4.5.4, just have to be rooted. If you use the Amazon launcher occasionally, try this.

DoLooper said:
This works with any Fire OS; don't need 4.5.4, just have to be rooted. If you use the Amazon launcher occasionally, try this.
Click to expand...
Click to collapse
Has anyone made a version of this for Lollipop ???

bibikalka said:
Has anyone made a version of this for Lollipop ???
Click to expand...
Click to collapse
Not I. (Kinda puts the lie to that old post, eh?)
Commands for developers preview:
pm disable com.android.launcher
pm enable com.android.launcher
am start -n com.android.launcher/com.android.launcher2.Launcher
5.2.2u2 enable/disable = pm disable com.amazon.firelauncher
I can guess start is:
am start -n com.amazon.firelauncher/com.amazon.firelauncher.Launcher
. . . but I can't test cuz I don't have a custom launcher right now. Maybe someone else can test this ??? If not, I'll figure it out in next few days. (You're still on 4.5.5?!)

DoLooper said:
Not I. (Kinda puts the lie to that old post, eh?)
Commands for developers preview:
pm disable com.android.launcher
pm enable com.android.launcher
am start -n com.android.launcher/com.android.launcher2.Launcher
5.2.2u2 enable/disable = pm disable com.amazon.firelauncher
I can guess start is:
am start -n com.amazon.firelauncher/com.amazon.firelauncher.Launcher
. . . but I can't test cuz I don't have a custom launcher right now. Maybe someone else can test this ??? If not, I'll figure it out in next few days. (You're still on 4.5.5?!)
Click to expand...
Click to collapse
OK, thanks! I just got a 5th gen Fire 7 for a present, and will play with it to see how this blocking works on Lollipop.

bibikalka said:
OK, thanks! I just got a 5th gen Fire 7 for a present, and will play with it to see how this blocking works on Lollipop.
Click to expand...
Click to collapse
It works "interestingly." Played with it today to update the block sys app post. Start command:
am start -n com.amazon.firelauncher/.Launcher
Couple interesting (to me) things:
Disable:
- If you only have one alternate launcher, disabling firelauncher immediately takes you to alternate. (But maybe it did this before. I've always had multi alt launchers.)
Enable:
- You stay on alt launcher, but tapping Home icon takes you to Fire launcher (even with multi alt launchers installed).
- Enable and switch = same as before: run enable and then run start

Updated and tested for Lollipop. Thanks to DoLooper for the suggestions!

bibikalka said:
Updated and tested for Lollipop. Thanks to DoLooper for the suggestions!
Click to expand...
Click to collapse
I want to give this a try on my Fire HD7 and have only been using the Amazon launcher to this point. What is the preferred Android launcher most of you use and do you go with the free launcher or purchase a particular one? I see a couple varieties of Nova at the Play Store and have to assume the purchased one does not have ads, so thought I would ask your preferences before giving it a try. Thanks in advance for any advice you provide...

I enjoy the Nova Prime(paid app) no ads lots to customize

phfoneman said:
I want to give this a try on my Fire HD7 and have only been using the Amazon launcher to this point. What is the preferred Android launcher most of you use and do you go with the free launcher or purchase a particular one? I see a couple varieties of Nova at the Play Store and have to assume the purchased one does not have ads, so thought I would ask your preferences before giving it a try. Thanks in advance for any advice you provide...
Click to expand...
Click to collapse
What don't you try the free Google Now launcher ? Once you see how this works, perhaps you'll try Nova.
In case you overdo launcher switching and end up with no working launcher, just remember you can always save the day with these commands in adb (as long as keep the amazon launcher intact, and just block it via "pm disable" as the script above does it):
pm enable com.amazon.firelauncher
am start -n com.amazon.firelauncher/com.amazon.firelauncher.Launcher

Hi all, I have run kindle_block_5_1.sh and then reboot device. I am stack with "Fire" logo at the boot. I have access to ADB, but could not receive root access in adb shell. Can anyone advice me? How can I revert changes after that script back?
Thanks in advance

Yevgen.A said:
Hi all, I have run kindle_block_5_1.sh and then reboot device. I am stack with "Fire" logo at the boot. I have access to ADB, but could not receive root access in adb shell. Can anyone advice me? How can I revert changes after that script back?
Thanks in advance
Click to expand...
Click to collapse
No need to answer, easily fixed my problem by factory reset in recovery

Yevgen.A said:
Hi all, I have run kindle_block_5_1.sh and then reboot device. I am stack with "Fire" logo at the boot. I have access to ADB, but could not receive root access in adb shell. Can anyone advice me? How can I revert changes after that script back?
Thanks in advance
Click to expand...
Click to collapse
Yevgen.A said:
No need to answer, easily fixed my problem by factory reset in recovery
Click to expand...
Click to collapse
Rookie mistake No launcher present, no adb authorized ! But I've added some messages to the original post to mention this issue.

I can't get Nova to create a Gscript shortcut at all. I press the Gscript disable option and it dumps me back to the Amazon launcher.

UPDATED: [ROOT] How to Install the Google Play Store on Stock 4.5.5.1 -Thor

After this little adventure, I went into further testing. There is now a much simpler method of installing the Google Play Store. Fully functional. Two methods to be exact, and an experimental one.
Method 1) -Recommended if you have Safetrap 4.01
Make sure you have SuperUser (Not tested with Kingroot)
and you are running 4.5.5.1 (It'll probably work in earlier versions.)
Note: I have Superuser installed as a system app for safety.
My device is a Kindle Fire Hdx 7" (3rd gen) Thor.
-You need Safetrap (or head to method 2 for a non safe-trap procedure)
-You need to be rooted
-And you need to download from Open GApps (Platform: ARM Android: 4.4 Variant: Pico < Smallest package)
First, you must make space in System/Priv-app to flash this little package. (< There's no way around this)
I deleted [ moffice, weather, and the android.mail.apk ] (I do not need those. I actually do not need a lot of the amazon services except for books.)
Reboot into Safetrap and flash/Install the opengapps package.
Wipe Dalvik/Cache. Reboot
> If you get a "Failed" - It means you need to delete more apps.
Make sure the message reads "Insufficient space, etc" and not "incompatible,"
If you are successful, reboot.
Open the Google Play Store and simply sign in with your account. You are done.
I haven't experienced any crashing. nada.
Use Market helper for incompatible app (Although inbox by gmail isn't working for me, everything else is.)
Method 2) Recommended if you don't have Safe trap.
You might need to delete some apps from system/priv-app if you get "Insufficient space error" <For me, I didn't have to delete anything.>
You do not need Safetrap.
-You need Root and you need to follow the method described here, but with a little tweak:
Move all the apps mentioned in the guide to System/Priv-app > Account And Sync Settings, Google Services Framework, Google Login Service, and Vending.apk)
Install Google Play Services from your downloads (Normal Install) < I am using the latest ones I got off Google.>
Reboot.
Open the android market (in apps) and sign in. <
Download the latest Google Play Store (from the guide or Google)
I renamed it vending.apk for short.
Delete the vending.apk found in System/Priv-app and replace with the new one.
Reboot.
Google Play Store is functional and shouldn't crash.
--------------------------
(I highly recommend a Custom ROM. The quality and functionality can not be beaten..)
Update: Now that the kindle app on android supports exporting highlights from personal docs/side-loaded books, etc.. I've made the full switch to CM11
------
Not recommended.
The method below is now experimental. I couldn't get it to reproduce after replacing Kinguser With SuperSu.
This is a fully functional Playstore. You can search, download and update
Tested on:
Kindle Fire HDX 7" (3rd Gen) running 4.5.5.1 w/ Kingroot
* No one is more responsible for your device than you. With that in mind, back up, read carefully, don't go the extra mile just because, and be aware there is always a risk. On to the fun stuff~
You will need:
-Root
-Safetrap v4
-All 4 apks from here (Skip all the instructions there and scroll to where it says —Then install these apks—
You also need the Google Apps Minimal Edition from here.
----INSTRUCTIONS
-Move all 4 apks to sdcard/download and install each one.
-Move your Google Apps Minimal Edition.zip to sdcard/download and keep it there.
Reboot into Safetrap.
* Make sure you have a backup of your STOCK Rom !
Go to Install > Find your Google Apps Minimal Edition.zip and install it.
From the same screen once you are done wipe dalvik/cache
Reboot.
You might run into a gray screen ? Hit the home button. It is a one time thing.
Login to your existing Google account. You'll notice the App Store will crash after a minute.
Reboot. That's it. Playstore shouldn't crash anymore.
#If it works for other devices, versions, let me know. Thank you.
I tested it on my own device, and downloaded a couple of apps. If something changes I will update this.
Update: You can find the latest Google Play Store and Services here. Uninstalling both items is necessary to install the new version then you can use ccleaner to remove any Google app that says 'newer version installed'

I did method 2. This absolutely worked. I'm especially pleased, because I kept seeing that I would need Safestrap and a custom ROM in order to get the Play Store on my HDX 7. So, thanks for the instructions.

If I used Kingroot to root my device can I still use method 2?
Also can I use twrp instead of safestrap? I have no idea what each one does what.
I rooted my tablet (HDX 7 4.5.5.1) using Kingroot, and my ultimate goal is to use google services and youtube properly. And change the OS (Is Nexus rom a good idea?)
Thanks for any help guys.

talkslow4me said:
If I used Kingroot to root my device can I still use method 2?
Also can I use twrp instead of safestrap? I have no idea what each one does what.
I rooted my tablet (HDX 7 4.5.5.1) using Kingroot, and my ultimate goal is to use google services and youtube properly. And change the OS (Is Nexus rom a good idea?)
Thanks for any help guys.
Click to expand...
Click to collapse
- no twrp, only safestrap v4 (which limits roms to cm11 and HDX Nexus)
- Google Services does not play well with FireOS v4. Strongly encourage custom rom if Google/YouTube is the end game
- YouTube via browser is also an option. Opera works well (as do others). Need to sideload via Opera home page or Apkmirror.

Hello
I went through Method 2, but can't get google service running.
There's one step that I could not understand, moving the apk files to system/priv-ap, why do we have to do so?
Thank you

mohzean said:
Hello
I went through Method 2, but can't get google service running.
There's one step that I could not understand, moving the apk files to system/priv-ap, why do we have to do so?
Thank you
Click to expand...
Click to collapse
Google Play Services and FireOS v4 simply do not get along. This is just one of many threads that suggest an integration methodology that yields a suboptimal experience or (more commonly) a crippled device. Bite the bullet and go with Safestrap v4 and a compatible custom rom (cm11 or HDX Nexus).

Thanks Luxen!!! It works perfectly! Device: Kindle Fire HDX 7" gen 3.
I used method 1.
Installed Kingroot, SuperSU, Safestrap, removed several APKs (MOffice (WPS Office), Cannon, EPSON, HP, Weather) from System/Priv-app using Total Commander (ASTRO file manager does not work) to make spaces, applied Pico OpenGApps, wipe Dalvik/Cache, reboot.
Then boom, it just works, no errors, no nothing! Updated all google apps. Everything works!
Can't thank you enough, great jobs!
Best,

mxnerd said:
Thanks Luxen!!! It works perfectly! Device: Kindle Fire HDX 7" gen 3.
I used method 1.
Installed Kingroot, SuperSU, Safestrap, removed several APKs (MOffice (WPS Office), Cannon, EPSON, HP, Weather) from System/Priv-app using Total Commander (ASTRO file manager does not work) to make spaces, applied Pico OpenGApps, wipe Dalvik/Cache, reboot.
Then boom, it just works, no errors, no nothing! Updated all google apps. Everything works!
Can't thank you enough, great jobs!
Best,
Click to expand...
Click to collapse
I am glad it worked out for you. Believe it or not, since I did method 1, I am still running my custom rom since that very day. Stable and smooth sailing.

Vanb85 said:
I did method 2. This absolutely worked. I'm especially pleased, because I kept seeing that I would need Safestrap and a custom ROM in order to get the Play Store on my HDX 7. So, thanks for the instructions.
Click to expand...
Click to collapse
This is the reason I tried to experiment with several different methods. I knew there are some users that are not interested or are too intimidated by Safetrap/Custom Roms, so I am glad it worked for you! :good:

I was wondering if anyone could help me a little bit with option 2 in the op's post? I am not the most tech savvy person in the world, so I am struggling a little with it. I have Kindle HDX 7 (3rd gen). I have managed to root using Kingroot. I attempted installing Google store. Got all the files downloaded and I thought installed accurately, but it would never let me sign in. I uninstalled and was going to retry using method 2 above that says move the files to system/private app before installing. I can't figure out how to get them from download to there though. I have ES File Explorer, but downloaded the recommended WIFI Explorer Pro to see file structure on my computer. Tried dragging and dropping and that did not work. Any advice? The instructions for #2 have not been the easiest for me to follow.

leigh80 said:
I was wondering if anyone could help me a little bit with option 2 in the op's post? I am not the most tech savvy person in the world, so I am struggling a little with it. I have Kindle HDX 7 (3rd gen). I have managed to root using Kingroot. I attempted installing Google store. Got all the files downloaded and I thought installed accurately, but it would never let me sign in. I uninstalled and was going to retry using method 2 above that says move the files to system/private app before installing. I can't figure out how to get them from download to there though. I have ES File Explorer, but downloaded the recommended WIFI Explorer Pro to see file structure on my computer. Tried dragging and dropping and that did not work. Any advice? The instructions for #2 have not been the easiest for me to follow.
Click to expand...
Click to collapse
Several ways to copy/move files in ES File Explorer. Perhaps easiest is to long file and scan options that pop-up (varies by version and config) for 'copy', 'move', 'copy to', etc. If nothing obvious check in 3-dot menu. Then navigate to target folder and tap 'paste'. Multiple files can be selected and copied at once.
If the files reside on your computer you should be able to copy/move using the same technique. Or simply download the directly to your device using the built-in Silk browser then move to target folder using ES File Explorer.
Might want to consider a custom ROM which has the Play Store built-in. While Amazon and Google components get along better in FireOS 5.x it is never a happy marriage with occasional glitches as versions of both change over time.

Thank you Davey126. I will give that a try. I have debated installing a custom rom, but fear that may be a little beyond my capabilities. I am struggling enough just getting Google Play on it. I am use to Android, so it has been hard to adjust to how locked down the Kindle is. Maybe if I come across some instructions I can easily follow, I will finally give that a custom rom a try.

leigh80 said:
I was wondering if anyone could help me a little bit with option 2 in the op's post? I am not the most tech savvy person in the world, so I am struggling a little with it. I have Kindle HDX 7 (3rd gen). I have managed to root using Kingroot. I attempted installing Google store. Got all the files downloaded and I thought installed accurately, but it would never let me sign in. I uninstalled and was going to retry using method 2 above that says move the files to system/private app before installing. I can't figure out how to get them from download to there though. I have ES File Explorer, but downloaded the recommended WIFI Explorer Pro to see file structure on my computer. Tried dragging and dropping and that did not work. Any advice? The instructions for #2 have not been the easiest for me to follow.
Click to expand...
Click to collapse
Actually you need to turn ON the ROOT EXPLORER option from TOOLS on Es File Explorer. to do so... Tap on TOOLS > ROOT EXPLORER > MOUNT RW and then mark all 4 options on right side (under RW) and tap on OK. doing so you will be able to move, copy and delete files/apks from/to System folders.

Hi @Luxen and everyone! I have a Kindle Fire HD 7 3rd generation running Fire OS 4.5.5 (Aug. 2015) and want to install Google Play Store on it. After searching for several hours, I can't find any worked method since all threads I found are outdated and people reported they were no longer working. I'm wondering if the method in this thread can work with my Kindle? Thank you!

kyoceralover said:
Hi @Luxen and everyone! I have a Kindle Fire HD 7 3rd generation running Fire OS 4.5.5 (Aug. 2015) and want to install Google Play Store on it. After searching for several hours, I can't find any worked method since all threads I found are outdated and people reported they were no longer working. I'm wondering if the method in this thread can work with my Kindle? Thank you!
Click to expand...
Click to collapse
In general Amazon and Google components do not play well on FireOS v4.x. It can be made to work...sort of...but tends to be susceptible when Play components auto update which happens frequently. A more reliable approach is to install a custom rom (CM11 or Nexus) that natively supports Google Play Framework, Services and Store.
If you opt to go this route the following thread may be of interest: http://forum.xda-developers.com/kin...used-partially-fire-os-to-proper-rom-t3421623

Google Play Store for Kindle Fire HD 7 (2013) 3rd gen on Fire OS 4.5.5
Davey126 said:
In general Amazon and Google components do not play well on FireOS v4.x. It can be made to work...sort of...but tends to be susceptible when Play components auto update which happens frequently. A more reliable approach is to install a custom rom (CM11 or Nexus) that natively supports Google Play Framework, Services and Store.
If you opt to go this route the following thread may be of interest: http://forum.xda-developers.com/kin...used-partially-fire-os-to-proper-rom-t3421623
Click to expand...
Click to collapse
Great! Thank you very much! I'll try what sd_shadow suggest first
I believe that 4.5.5 can be rooted with kingroot
KingRoot thread
then see rootjunky's supersume video
https://www.youtube.com/watch?v=3O3DcpeS_Ic
or manually install supersu with a terminal emulator
http://www.w0lfdroid.com/2015/05/How...h-SuperSU.html
Click to expand...
Click to collapse
then flash mine to CM11/Nexus

New here
I have the Fire HDX 7" 3rd gen and was wanting to make it a true Android tablet due to Amazon not updating it further. I have read post after post and I am so confused as to where to even begin. I know it needs to be rooted and a custom ROM installed, I just wish there was one place I could find step by step instructions to do so. I'd rather have Fire OS than have an usable tablet. Maybe I just need to give up trying to do it.

mckev24 said:
I have the Fire HDX 7" 3rd gen and was wanting to make it a true Android tablet due to Amazon not updating it further. I have read post after post and I am so confused as to where to even begin. I know it needs to be rooted and a custom ROM installed, I just wish there was one place I could find step by step instructions to do so. I'd rather have Fire OS than have an usable tablet. Maybe I just need to give up trying to do it.
Click to expand...
Click to collapse
Take a peek at this thread to get a sense of what's involved. Not a step by step guide by any means but touches on the highlights. Post back with any immediate questions.
http://forum.xda-developers.com/kin...used-partially-fire-os-to-proper-rom-t3421623

Davey126 said:
Take a peek at this thread to get a sense of what's involved. Not a step by step guide by any means but touches on the highlights. Post back with any immediate questions.
http://forum.xda-developers.com/kin...used-partially-fire-os-to-proper-rom-t3421623
Click to expand...
Click to collapse
Can I download ES file explorer from the Amazonn app store or should it be downloaded elsewhere? I have downloaded and installed KingRoot, but I haven't ran it as of yet.
Also wanted to say thanks for pointing me in the right direction!

mckev24 said:
Can I download ES file explorer from the Amazonn app store or should it be downloaded elsewhere? I have downloaded and installed KingRoot, but I haven't ran it as of yet.
Also wanted to say thanks for pointing me in the right direction!
Click to expand...
Click to collapse
Not sure how current the version in the Amazon App store is. Best grab a copy from here.
Tip: If unsure post any questions you may have before acting. HDX is a touchy device; easy to brick and hard (often impossible) to recover if you stray too far off the trail. Several great folks monitor these forums and can help as needed.

[GUIDE] Root/Kernel+ViPER/Dolby+Theme/Mods

Intro
I decided to put together this all-in-one guild compiling all the research and testing I've done. I've seen a lot of the same questions and misunderstandings come up over and over in the various threads, most of which I had myself. I've spent lots of time, since I got my new Google Pixel 2 XL, searching XDA, following all the guides the fine folks here put together, flashing, restoring, testing, etc. I've been using Android since my Google Nexus One, so I've been messing around with all this for quite some time now. The Android community is amazing and I've learned a lot over the years, so it's my turn to hopefully help someone out.
I'll also share some of the caveats, issues and fixes I had to do with this setup. This was all done with a Google Pixel 2 XL on Project Fi with an eSIM & physical SIM, so this guide was written and tested with that, however it should work the same in theory with other carriers, but your results may vary.
NOTE: I am not a developer by any means. I've toyed with creating my own custom ROM, but I'm not a ROM or Kernel developer. I just got really good at using the stuff the other amazing smart people here developed and shared with the community.
NOTE 2: Following these steps WILL wipe your device, so make backups if needed!
Thanks
I would like to give thanks to the following folks for the guides, development and help; @topjohnwu, @nathanchance, @Dees_Troy, @luciusfox, @thedude420, @Quinny899, @airmaxx23, @matt1313, @sharkie405, @Tulsadiver, and @zachman1750. Please forgive me if I forgot to mention you directly as I've gone through many threads and guides at this point. I also thank the community for helping each other out and providing their experiences and testing as well.
Why Root?
I get the same question from everybody all the time, "why do you root your phone?" Well, many reasons, which I'll list a few below, but because I spent a lot of money on my phone and I feel I should have full access to it. If your phone is leased or company owned, I understand why you wouldn't, but if you own it outright, why not have full access to do what you want with it? I mean, how would you feel if you purchased a computer (I'll use Windows in this analogy) and it came with one user account that was only part of the "Users" group, no local Administrator or account part of the Administrators group and no way to grant your one user account Admin rights? I'd be upset as I wouldn't be able to do much with it including; remove bloatware, install my own applications, replace the stock AV/Malware software, upgrade my video driver or even start from scratch. I mean the first thing I do when I get a new computer is format the HDD lol. I know it might be a silly analogy, but I don't see how it's any different than having root access on my phone.
- Remove bloatware (system apps you don't want/need)
- Custom Kernels (though the stock kernel on this phone is amazing out to the box, custom gives us more access to manage wakelocks, color control, vibrations, among other kernel items) (EXKM and Kernel Adiutor are a couple great apps to tweak your custom kernel)
- Customer recovery (easy backup/recovery, easy flashing of Zips, etc...)
- Untethered system theming including; custom fonts, launcher tweaks, status/navbar tweaks, etc...)
- System wide ad blocking
- Full system backup/restore (Titanium Backup is amazing for full system backups and then upload to cloud storage of your choice)
- Terminal root access (every have horrible battery drain and can't figure out exactly why quick and easy? Drop to terminal, elevate using su, then run top and and see what app is hogging the CPU)
- Xposed modules for system customizations (I've used a lot over the years, but not on this phone yet. You will also FAIL SafetyNet if you use the Xposed Framework.)
- AUDIO MODS! I honestly don't know how I lived my life without apps like ViPER and Dolby on my phone
A/B Partitions
To hopefully help clear up some confusion here, I'll list some important points to take note of.
- The whole point of the dual partition setup is to make OTA updating easier, allowing for updating the OS in the background
- There are two system, two boot and two vendor partitions, but only one data partition
- Only one system and its corresponding boot partition are active at one time
- Whichever system/boot partition is active will use the one data partition
- Flashing a custom kernel, mod zip or Magisk will flash to the current active slot from recovery, however flashing the Google Image or a custom rom will flash to the inactive slot
- The recovery is part of the boot partition, meaning anytime you flash the stock or custom kernel, for example, you'll need to reflash your custom recovery again (unless you install a kernel zip created with AnyKernel2 by @osm0sis)
My Build
Sharing these details as if you are on a different image, kernel, carrier, etc... your results may vary.
Phone: Google Pixel XL 2 Black 128GB - purchased from Google Store / Hardware Version: rev_10
Carrier: Project Fi with eSIM & physical SIM
Android Version: Official 8.1.0 / Security Patch Level: February 5, 2018
Build Number: OPM1.171019.018
Kernel: 4.4.119-FlashKernel-Taimen-v2.20 (clang version 6.0.0)
Root: Magisk Manager 5.6.1(105) (patched dtbo NOT preserving "force encryption" or "AVB2.0/dm-verity") & Magisk 16.0(1600) / Modules: Busybox for Android NDK 1.28.1, Magisk Manager for Recovery Mode (mm) 2018.1.31, Single User Mod 1.4, ViPER4Android FX Materialized 1.5.1 (2.5.0.5)
Recovery: TWRP 3.2.1-0
APKs: SELinuxModeChanger v11.0, AdAway 3.2-60, Dolby, MinitBatteryResrouces
Convenient Play Store Apps: 3Minit Battery Settings, FiSwitch, Kernel Adiutor, Light Manager, Root Explorer, substratum (Swift Black), TiBu Pro (I do scheduled backups of my phone to my Google Drive) & Terminal Emulator (great to use Busybox commands like "traceroute" or "top" to find that app killing your battery!)
Android Platform Tools Install
1. Download the latest version for your computer OS (PC/Mac/Linux) from Google: https://developer.android.com/studio/releases/platform-tools.html
2. Unzip the downloaded file to your hard drive somewhere and:
- Windows: add to your PATH (google "add adb to path")
- Mac/Linux: From terminal of your choice "sudo install adb /usr/local/bin && sudo install fastboot /usr/local/bin" (run from within the extracted directory and enter your password when prompted)
- Windows 10 & macOS High Sierra detect the phone automatically, but older versions you may need Android Device Drivers. Just Google what you might need and how to do it if your phone is not detected automatically.
Unlocking
1. Turn your phone off.
2. Press and hold Volume Down, then press and hold Power.
3. Plug your phone into your computer.
4. From command prompt/terminal on your computer (run Command Prompt as Admin in Windows throughout this guide):
- fastboot flashing unlock
- fastboot flashing unlock_critical
NOTE: I've read a lot of back and forth on if we should unlock_critial or not. This is just my opinion, but if you're here to do all this stuff to your phone, want complete access to do whatever you want to it, just do it. It's better to be ready now for the future because every time you unlock or relock, it will factory reset your phone. I've been unlocked both regular and critical since the first boot when I took my phone out of the box. I'll also mention, I’m not entirely sure what steps will work or not work in this guide if you don't since I've never not been unlocked with critical.
5. Follow the instructions on the phone screen to do the factory reset.
Clean Start
1. Download the "taimen" for Pixel 2 XL factory image [8.1.0 (OPM1.171019.018, Feb 2018)]: https://developers.google.com/android/images
2. Turn your phone off.
3. Press and hold Volume Down, then press and hold Power.
4. Plug your phone into your computer.
5. Unzip the downloaded file to your hard drive somewhere and from the directory you extracted the files (CMD/Terminal):
- Windows: flash-all.bat
- Mac/Linux: ./flash-all.sh
- Unplug your phone from your computer
Initial Config/Prep
1. Go through the initial phone setup steps.
- Make sure you setup your Google account so you have access to the Play Store and you can activate your eSIM if that's what you're using.
NOTE: When setting up with only an eSIM, I ran into some bugs and caveats I had to figure out on my own as Google support couldn't figure it out let alone understand what I was trying to explain to them. I ordered a physical SIM and now have both an eSIM and a physical SIM installed and can switch between them.
Verizon SIM: As @jrbxx7 was kind enough to share below; if running a Verizon SIM, wait till after setup is complete before inserting it. That way the vzw apps don't get installed on google setup.
eSIM Caveat: If you have 2 Step Authentication turned on for your Google account and your phone is your only device with the Google Authenticator App or Google Prompt, you will have to use one of your backup codes to log back into your account as your phone will not be activated until it's completed in the Project Fi application.
eSIM Bug: After you go through the initial phone setup, let Play Store finish its updates and don't reboot yet. Open Play Store and search for "Project Fi", then click "Enable", but DON'T update it. Just open Project Fi, complete the activation then reboot your phone. You can update the Project Fi app after the activation is successful. I've tested this through three factory restores and the result is the same every time.
Physical SIM: No issues since your phone will just be activated after boot so you can receive SMS codes.
2. Enable Developer Mode: tap "Build number" under "About phone" 7 times.
3. Under "Developer options", enable "USB debugging".
4. Download necessary files:
- Magisk 16.0(1600): https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
- SELinuxModeChanger 11.0: https://f-droid.org/en/packages/com.mrbimc.selinux/
- AdAway 3.2-60: https://f-droid.org/en/packages/org.adaway/
- Dolby: https://forum.xda-developers.com/pixel-2-xl/how-to/viper-dd-atom-t3724096
- Kernel. I use @nathanchance Flash Kernel: https://forum.xda-developers.com/pixel-2-xl/development/taimen-flash-kernel-1-00-t3702057
NOTE: You can use whatever kernel you want, but I've only used/tested with Flash. Flash Kernel also has the proper drives to resolve the TWRP touch issues. I've read other custom kernels do as well.
- TWRP 3.2.1-0 (image & installer): https://forum.xda-developers.com/pixel-2-xl/development/twrp-alpha-pixel-2-xl-t3698148
5. Plug your phone into your computer.
- If prompted on your phone, save and allow USB Authorization for your computer.
6. Push downloaded files to your phone (CMD/Terminal):
- adb push <path_to_Magisk_file>.zip /sdcard/Download
- adb push <path_to_SELinuxModeChanger_file>.apk /sdcard/Download
- adb push <path_to_AdAway_file>.apk /sdcard/Download
- adb push <path_to_Dolby_file>.zip /sdcard/Download
- adb push <path_to_Kernel_zip_file>.zip /sdcard/Download
- adb push <path_to_TWRP_image_file>.img /sdcard/Download
- adb push <path_to_TWRP_installer_file>.zip /sdcard/Download
Install Kernel & TWRP
NOTE: As of the Google February security image release, TWRP will no longer decrypt. You have three options to flash in TWRP until it's fixed; disable security before booting to TWRP, use USB storage via your OTG adapter, or put the files you need in the /data partition.
1. adb reboot bootloader (CMD/Terminal while your phone is still plugged into your computer)
2. Flash TWRP:
- fastboot boot <path_to_TWRP_image_file>.img
- Once in TWRP, install the TWRP_installer.zip file
- Reboot into TWRP
- Install Kernel.zip file
- Install the Magisk_16.0(1600).zip file
- Reboot to System.
3. Configure Magisk:
- Open Magisk Manager
- (OPTIONAL) Patch dtbo by unchecking both "force encryption" and "AVB2.0/dm-verity", tap "Install", tap "Install", tap "Direct Install (Recommended), then reboot
NOTE: By patching dtbo, you will receive a message on every boot that says something along the lines of "There's an internal problem with your device". This is perfectly normal when patching the dtbo and can be ignored as nothing is broken. Now, to be honest, I patch dtbo as I can't get certain things to work properly without, like Dolby, and the message doesn't bother me as it's only on boot up. I know patching dtbo is necessary for some things. For example, I don't think you can do manual build.prop edits without editing dtbo, if I'm not mistaken. I have had a few others on other threads say they were able to get Dolby to work without patching dtbo and just using SELinux in "permissive" mode, but I couldn't. Up to you, hence the "optional" part. If you decide to patch dtbo and want to go back, just flash the stock dtbo image file in fastboot or TWRP.
- Open Magisk Manager
- Goto Settings and tap "Hide Magisk Manager"
- Reopen Magisk after it's done
- Goto Settings and make sure "Magisk Hide" and "Systemless hosts" are both enabled
- Gogo Magisk Hide and check the applications you need to hide from Root (banking apps, authenticators, etc...)
4. If Play Store is not showing as "Certified" under Play Store Settings, clear Data and Cache on the Play Store under Phone Settings. Your Play Store will now be "Certified" under the Play Store Settings.
Install/Configure SELinuxModeChanger and AdAway
NOTE: It's my understanding that SELinux does not need to be set to "permissive" for ViPER and Dolby to work, but I can't get them to work otherwise. My Dolby will FC without setting SELinux to "permissive", which is why I'm adding it to my guide in case someone else is having the same issue. You can use the Magisk Module script if you want, but I like the convenience of the App to turn on and off easily.
1. Open "Downloads" from the App Launcher on your phone.
2. Install both SELinuxModeChanger.apk and AdAway.apk.
3. Open SELinuxModeChanger:
- Tap "Permissive"
- Tap "Automatically start on boot"
4. Open AdAway:
- Open Preferences and make sure "Enable systemless mode" is enabled". It's normal to be Greyed out. This is verification from the Magisk Settings you set above.
- Tap "Download files and apply ad blocking"
5. Reboot phone.
Install & Configure Magisk Modules / Dolby
1. Open Magisk Manager and go to Downloads:
- Download "Busybox for Android NDK" (some root apps need this, but it's also nice to have these utilities)
- Download "Single User Mod" (needed for latest TWRP install to my understanding, but it worked for me without. I like this anyway because I don't share my phone)
- Download "ViPER4Android FX" (make sure to get the v1.5.1(2.5.0.5) version) / during install you will be asked what version and theme, chose the 2.5.0.5 driver version and the Materialized version (needed for Dolby).
- Reboot Phone
2. Open ViPER 4 Android FX application:
- Under Settings tap "Turn on developer mode" then tap "Disable SELinux"
3. Reboot Phone.
- After reboot, open ViPER 4 Android FX application and enable/configure the effects you want.
NOTE: Be patient after a phone reboot. It sometimes takes a minute for the Magisk modules to load.
4. Reboot to TWRP.
- Install Dolby.zip file
- Reboot into System
5. Open Dolby, and if it force closes, make sure your SELinux is "permissive" first and if you still have force closes, patch dtbo following instructions above.
Themes & Mods - Screenshots attached below!
I use substratum and Swift Black from the Play Store for my system wide theme. I use Light Manager from the Play Store for custom status lights for applications, etc... You can also get more customization of what icons to show or not show on your status bar by pulling down the notifications at the top of the phone and holding down the Settings gear icon until you feel a vibrate. You'll now have "System UI Tuner" under Settings->System. I'm also using the following Mods:
- SearchLess Launcher: https://forum.xda-developers.com/pixel-2-xl/themes/mod-pixel-2-xl-launcher-mods-8-1-0-dp1-t3701939
- Rosemary Font: https://forum.xda-developers.com/pixel-2-xl/themes/font-flashable-ubuntu-font-zip-pixel-2-t3710892
- Various Mods Aroma w/ 3Minit Battery: https://forum.xda-developers.com/pixel-2-xl/themes/various-mods-8-1-december-update-t3721741
- Substatum /w Swift Black (I dont theme System UI or System UI Navigation as part of my setup with the Various Mods Aroma)
- ViPER w/ Audiophile X profile & Dolby using Music profile (Volume Leveler / Surround Virtualizer / Intelligent EQ: Open)
Updating
I'm going to keep these steps kind of generic and provide the order in which things have to be done (order is important), however for the details just follow the steps for each part above. You shouldn’t have to do the setup for Magisk Modules again unless:
- You ran into issues and needed to do a clean start with Magisk using the Magisk Uninstaller
- You are doing a Google Image update
Magisk - Push the updated Magisk Zip to your /sdcard/Download folder, boot into TWRP, flash new Magisk Zip, reboot into System, go through Magisk setup steps again.
Kernel – Push the updated Kernel Zip file to your /sdcard/Download folder, make sure you have the Magisk Zip file in your /sdcard/Download folder as well. Reboot to TWRP, flash new Kernel, flash Magisk, boot System and setup Magisk again.
TWRP – Push the updated TWRP Zip to your /sdcard/Download folder, reboot to TWRP, flash new TWRP Zip, boot into TWRP to test, boot System.
Google -
1. Disable any screen security you have.
2. Disable and uninstall Substratum themes, if you have any.
3. Full backup of some sort recommended!
4. Boot to Bootloader and do a flash-all (without -w) of 8.1 factory image, boot to System and allow the update to finish.
5. Boot back to Bootloader, boot TWRP, install TWRP, reboot to TWRP, install Kernel Zip file, install Magisk Zip file, boot back to System.
6. Complete Magisk setup steps (Magisk hide, App hide, systemless, etc..), check SafetyNet.
7. Apply any mods and themes in Substratum.
Have fun!

Right on brother. My own journey is pretty much a mirror of your write up and I can't think of a single thing to add. Nice work. We have the same setup. Lol

CyberpodS2 said:
Right on brother. My own journey is pretty much a mirror of your write up and I can't think of a single thing to add. Nice work. We have the same setup. Lol
Click to expand...
Click to collapse
Thanks man! Yeah, this stuff has always been fun to me. I don't mind "breaking" my phone so I have to figure out how to fix it. lol I lost count how many times I wiped, flashed, etc to come up with my list.
I've also updated the guide to include "updating" stuff.

felosisman said:
Thanks man! Yeah, this stuff has always been fun to me. I don't mind "breaking" my phone so I have to figure out how to fix it. lol I lost count how many times I wiped, flashed, etc to come up with my list.
I've also updated the guide to include "updating" stuff.
Click to expand...
Click to collapse
Exactly, I got really quick at starting from scratch... Lol

Nice write up! One note if u feel like adding it, if running a verizon sim, wait till after setup is complete before inserting it. That way the vzw apps dont get installed on google setup.

jrbxx7 said:
Nice write up! One note if u feel like adding it, if running a verizon sim, wait till after setup is complete before inserting it. That way the vzw apps dont get installed on google setup.
Click to expand...
Click to collapse
Thanks for the addition, I"ll add it now! I don't have a VZW SIM so I would never have known lol.

This is the best guide on XDA now! I've been reading 10 different threads to do stuff, but someone who understands how it all works together can make it so much easier... Thanks again [emoji106]
Sent from my [device_name] using XDA-Developers Legacy app

slaydog said:
This is the best guide on XDA now! I've been reading 10 different threads to do stuff, but someone who understands how it all works together can make it so much easier... Thanks again [emoji106]
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
You're welcome! I'm happy to know this is helpful to folks.

Sticky?
Mods,
Is there any way to make this thread a sticky so it's easier for everybody to find?
Thanks!

jrbxx7 said:
Nice write up! One note if u feel like adding it, if running a verizon sim, wait till after setup is complete before inserting it. That way the vzw apps dont get installed on google setup.
Click to expand...
Click to collapse
What exactly is installed for Verizon apps? I didn't notice them on my install. Not saying they are not there, just didn't notice the changes.

felosisman said:
Mods,
Is there any way to make this thread a sticky so it's easier for everybody to find?
Thanks!
Click to expand...
Click to collapse
I think this thread is worth a sticky because it covers a lot of stuff that other guides don't, and covers them well. TWRP wasn't even a viable option when other guides were made, and it has made things much simpler...
Sent from my [device_name] using XDA-Developers Legacy app

Thank you for the guide. So I assume that if I were to brick the device I could use the factory images and fastboot to restore? Does anyone know what would happen if you tried to flash an older factory image street upgrading through OTA?
Sent from my Pixel 2 XL using Tapatalk

andrewjt19 said:
Thank you for the guide. So I assume that if I were to brick the device I could use the factory images and fastboot to restore? Does anyone know what would happen if you tried to flash an older factory image street upgrading through OTA?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
You should always be able to restore using the factory images from Google. In all the years I've been doing this, I've never once actually bricked a device to where is wouldn't work anymore. Just basically boot up to the bootloader and run the flash-all script. You can get the full Google images and instructions here: https://developers.google.com/android/images
As for downgrading, I've not personally done it. I know folks have gone from the 8.1 DPs back to 8.0, but if I'm not mistaken Google is making it hard to downgrade for security reasons. Once 8.1 is officially released, we may not be able to go back to 8.0, for example. I'll let others chime in with their experiences.
EDIT: After reading your post again, if you mean you took the November OTA you will be fine. The latest factory image from Google is the same as the Nov OTA.

please delete

felosisman said:
You should always be able to restore using the factory images from Google. In all the years I've been doing this, I've never once actually bricked a device to where is wouldn't work anymore. Just basically boot up to the bootloader and run the flash-all script. You can get the full Google images and instructions here: https://developers.google.com/android/images
As for downgrading, I've not personally done it. I know folks have gone from the 8.1 DPs back to 8.0, but if I'm not mistaken Google is making it hard to downgrade for security reasons. Once 8.1 is officially released, we may not be able to go back to 8.0, for example. I'll let others chime in with their experiences.
EDIT: After reading your post again, if you mean you took the November OTA you will be fine. The latest factory image from Google is the same as the Nov OTA.
Click to expand...
Click to collapse
Thanks buddy for the reply. That's what I figured but my personal policy had always been to "find" the fix before I tamper with anything. Once I unlock the bootloader I'm assuming I cannot take OTA's in typical fashion right? Also is relocking the bootloader the same as unlocking (obviously using the opposite command)? Thanks so much.
Sent from my Pixel 2 XL using Tapatalk

andrewjt19 said:
Thanks buddy for the reply. That's what I figured but my personal policy had always been to "find" the fix before I tamper with anything. Once I unlock the bootloader I'm assuming I cannot take OTA's in typical fashion right? Also is relocking the bootloader the same as unlocking (obviously using the opposite command)? Thanks so much.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
You're welcome! Absolutely, might as well be prepared just in case.
So, I've not tried it myself from "System Updates", but to my understanding you can still take OTA with the bootloader unlocked. I think the OTAs stop working when the System partition has been modified. But considering pretty much everything we do these days is Systemless, I think it'd be fine. I did manually install the November OTA from fastboot with my bootloader unlocked and it worked fine. To relock, yeah the command is pretty much just the opposite.
"fastboot flashing lock" would relock your device. Keep in mind though, every time you lock or relock it will wipe your device.

Sticky Request
I've done sone searching and can't figure it out, but does anybody know if there is an official way to request this to be a sticky?

felosisman said:
I've done sone searching and can't figure it out, but does anybody know if there is an official way to request this to be a sticky?
Click to expand...
Click to collapse
Your guide helped
Cheers ?
You using any other mods
Sent from my Google Pixel 2 XL using XDA Labs

Prattham said:
Your guide helped
Cheers
You using any other mods
Sent from my Google Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
Excellent, happy it was helpful!
No, I'm only using what I've got posted; ViPER, Single User and BusyBox.

I'll go ahead and ask this here since the Viper thread is so busy and I have seen a lot of answers and it's things that I've already tried over and over again. But, no matter which Viper version I download whether it be through magisk or a zip install via TWRP, I can never ever ever get the drivers to install. You got Viper in the title of your thread but I only seen one line of Viper in the op and that's to do with setting selinux to permissive, which I already have set to.
So does anybody have any out-of-the-box advice on what to do to get that Viper driver to install on a pixel 2 XL running 8.1 .0 DP2?
I'll spend all my 8 thanks for the day thanking somebody if they can help me figure this out.
Edit: I did just notice some more Viper instructions, my bad. I will try those out and report back
Edit 2: So I followed your instructions to the T, and the driver still won't install. Anyone got any ideas? It's not some sort of bug with the program is it where the driver has really been installed already but it's just saying that it's not?
Sent from my Pixel 2 XL using XDA Labs

[Release] OneClick Script for Amazon Fire v5.3.2.1...v5.4.0.0 (Fire 7 / 7th gen)

Based on @savvytechwinner's work, on Wicki's work (Mod Edit - NO links to competing Forums) and on some experimentation of my own, I put together a new script to further ease the setup of an out-of-the-package Amazon Fire 7 / 7th gen and to clean up more throughly. This is a derivative / remix / improvement rather than something new. Thanks go to all the people this work is based on.
I already announced this in savvytechwinner's thread, but I figured setting up it's own thread is warranted.
What it does:
OTA Updates are blocked
Lockscreen ads are removed
Functional Google Play Store and Google Go search are installed
Bloatware is removed from the tablet
Functional Nova Launcher, Adblocker (DNS66) and light Youtube Client (NewPipe) are installed
Out-of-the-package instructions:
Have adb and Amazon Fire USB drivers installed on your PC.
Power on your Fire tablet, do the initial setup. DO NOT CONNECT TO WIFI. Instead, select any password protected wifi, then cancel, and initial setup will let you continue without internet.
Enter Settings -> Device options -> click Serial 7 times. A new menu entrypoint called Developer options will pop up.
In Developer options, enable ADB, then connect your tablet to your computer. Confirm the fingerprint. If that didn't work, look here for troubleshooting.
Now, extract the contents of this package somewhere on your computer and double click FireOneClick.bat.
You can watch how Amazon's apps vanish, but it is recommended not to do anything else with your tablet while the script does its work.
After it's finished, enter Settings -> Accessibility -> "enable To detect home button press". Then, open the LauncherHijack app and select Nova Launcher.
Open the DNS66 app and start it. This will run in background (at low memory consumption) and block ads.
Download the One Click Script from here.
Full readme, including credits and more info is found in my GitHub repo.

Just a heads up, I used this script on a fire 7 I had literally just opened, and it was successful in loading GApps and Blocking ads, but it did not debloat the amazon apps and it also did not block OTA updates...I woke up to a fire 7 that auto updated to 5.6.0. I'm not complaining here, since Nova Launcher is still installed and ads are nonexistent, just letting you know!

hiphopsded said:
Just a heads up, I used this script on a fire 7 I had literally just opened, and it was successful in loading GApps and Blocking ads, but it did not debloat the amazon apps and it also did not block OTA updates...I woke up to a fire 7 that auto updated to 5.6.0. I'm not complaining here, since Nova Launcher is still installed and ads are nonexistent, just letting you know!
Click to expand...
Click to collapse
Dammit... what version did you start on? Assuming it was 5.4.0.1?

Hi my 7" is on 5.4.0.
Does this just block the download or the update itself? Because I accidentally downloaded the OTA update but the tablet doesn't updated jet.
Is there a way to delete the update without root?

VottelTheTroll said:
Hi my 7" is on 5.4.0.
Does this just block the download or the update itself? Because I accidentally downloaded the OTA update but the tablet doesn't updated jet.
Is there a way to delete the update without root?
Click to expand...
Click to collapse
It blocks the update itself by disabling all apps that would apply it. I still recommend turning Wifi off and doing a factory reset, so the update data is gone for sure.
Blocking the update / debloating most likely did not work for @hiphopsded cause he started from 5.4.0.1. Blocking updates / removing ads / debloating is onlypossible on v5.4.0.0 and below. I am somewhat surprised he doesn't have ads on the lockscreen, but I think that is due to the DNS66 adblocker doing it's work properly.
EDIT: @hiphopsded - maybe there is still hope, but you'll have to do the research yourself.
https://forum.xda-developers.com/showpost.php?p=75167286&postcount=437

@k8500 I was on v5.4.0.0
I opened it brand new from sealed packaging, canceled connecting to a WiFi I did not have the password to, and was brought into the device home screen without ever connecting to WiFi to verify that I was on v5.4.0.0 and proceeded with installing the one click script.
Everything worked except debloating the tablet and OTA Updates being blocked. Not sure what went wrong. But having the launcher, google apps, and no ads is fine enough.

Another confirmation of this working on 5.4.0.0
Just received an Amazon Fire 7 - 7th gen. It ships with 5.4.0.1
I was able to downgrade from 5.4.0.1 to 5.4.0.0, then use this batch file to clean up the tablet.
Thanks!

already (well) used 7gen currently on 5.6.0.1
any idea when this will be updated to work on 5.6.0.1?
and next question does it actually root the tablet?
thanks in advance

markbnj said:
any idea when this will be updated to work on 5.6.0.1?
and next question does it actually root the tablet?
thanks in advance
Click to expand...
Click to collapse
Does not root and will not be updated for 5.6.x.x as Amazon disabled the underlying commands that perform the magic.

5.6.x.x update question
Davey126 said:
Does not root and will not be updated for 5.6.x.x as Amazon disabled the underlying commands that perform the magic.
Click to expand...
Click to collapse
ok. So, bottom line, I can either wipe the unit, and start over; or
try and root the fire tablet to get rid of ads, and install other stuff...)
any other ideas?
I've rooted lots of android, and would actually prefer a more android, rather then amazon centric tablet....
thanks in advance...

markbnj said:
ok. So, bottom line, I can either wipe the unit, and start over; or
try and root the fire tablet to get rid of ads, and install other stuff...)
any other ideas?
I've rooted lots of android, and would actually prefer a more android, rather then amazon centric tablet....
thanks in advance...
Click to expand...
Click to collapse
Can't root 7th gen Fire at present. Period. Can't load a different ROM w/o root. Try sketchy rollback/debloat techniques at your own peril. Contact Amazon to dump annoying lock screen ads. Install a VPN based firewall like AdGuard to dispense with in-app advertising. Possibly install a different launcher using non-root techniques. Pretty much it.

Maybe I'm a little late in opening this thread up again, but let me ask this:
I just got a Kindle 7 (7th generation) in the mail, to replace our son's old one (5th generation, though unfortunately never rooted) that started messing up (so presumably the new one is refurbished). We don't like all the amazon bloat, etc., and would prefer the different launcher or anything more android-like we can get. I would love to block the OTA updates. So your tool sounds great.
I opened it and turned it on but haven't set up the device yet. I see it's version 5.3.3.0 Does this one click script of yours work on the 5.3.3.0 ? Are there any other suggestions on the best way to use my new device (taking out amazon bloat and more like google) considering it's *not* the newest OS that Amazon makes? I.e. are there any options I have available to me currently that I want to be sure I don't lose out on by accidentally updating or something? Thanks for any help you can provide!

madagascaradam said:
Maybe I'm a little late in opening this thread up again, but let me ask this:
I just got a Kindle 7 (7th generation) in the mail, to replace our son's old one (5th generation, though unfortunately never rooted) that started messing up (so presumably the new one is refurbished). We don't like all the amazon bloat, etc., and would prefer the different launcher or anything more android-like we can get. I would love to block the OTA updates. So your tool sounds great.
I opened it and turned it on but haven't set up the device yet. I see it's version 5.3.3.0 Does this one click script of yours work on the 5.3.3.0 ? Are there any other suggestions on the best way to use my new device (taking out amazon bloat and more like google) considering it's *not* the newest OS that Amazon makes? I.e. are there any options I have available to me currently that I want to be sure I don't lose out on by accidentally updating or something? Thanks for any help you can provide!
Click to expand...
Click to collapse
Yes, it works with fire OS 5.3.3.0

Rortiz2 said:
Yes, it works with fire OS 5.3.3.0
Click to expand...
Click to collapse
Thanks for letting me know, but maybe I'm doing something wrong because I can't get it to work at all. To start with, I had already opened my fire tablet but skipped setup (also skipped signing into wifi because I knew that could give me an auto-update). So maybe that's what screwed it up? Maybe I should reset to factory and try again?
I had installed the fire drivers too but my fire never showed up in "portable devices" in device manager (in fact, I never saw such a category - but it did show up in devices as "MTP device").
The adb worked fine as I was able to get it to "show devices". However, the one-click never did anything. Usually I use powershell, but then I tried running through normal command prompt, but still no luck. I tried putting it in my adb fastboot folder (is that my problem? does it need the full adb and adb fastboot isn't enough?) and it still didn't work. So, maybe my first step was the problem or maybe a subsequent one, I don't know, but I couldn't get any of it to work.

uninstall apps
cannot uninstall applications , i downgrade to 5.4.0 but applications are only hiding , they are still in the system .
PROOF : you can check your free space before and after uninstalling, you will gain nothing important.
but for removing ads or blocking update , its working for 5.4.0 !!!
---------- Post added at 12:19 AM ---------- Previous post was at 12:17 AM ----------
avatarma said:
cannot uninstall applications , i downgrade to 5.4.0 but applications are only hiding , they are still in the system .
PROOF : you can check your free space before and after uninstalling, you will gain nothing important.
but for removing ads or blocking update , its working for 5.4.0 !!!
Click to expand...
Click to collapse
but for rooted devices we can uninstall applications with root uninstaller pro or similare application.

FireTV-Settings 3.0 Mod Root works on Tank and Mantis without Amazon Launcher

!! deprecated !!

0815hoffi said:
FireTV-Settings 3.0 Mod Root works on Tank and Mantis without Amazon Launcher
based on https://github.com/rainman74/FireTV-Settings/releases
install as normal APK.
Root is needed.
NewSettingsGerRoot.apk = German
NewSettingsEngRoot.apk = English
FireTV-SettingsGer.zip = Android Studio Zip German
FireTV-SettingsEng.zip = Android Studio Zip English
Feel free to customize it for whatever works best for you! ...
Click to expand...
Click to collapse
Ok so the apk file is unnecessary with root since the zip is in charge of that correct? This is actually interesting considering that the Amazon Launcher being disabled with root therefore losing functionality to accessing settings unless you were to use adb commands.
Edit: the apk was supposed to be installed, works 100%

Skel40 said:
Ok so the apk file is unnecessary with root since the zip is in charge of that correct? This is actually interesting considering that the Amazon Launcher being disabled with root therefore losing functionality to accessing settings unless you were to use adb commands.
Edit: the apk was supposed to be installed, works 100%
Click to expand...
Click to collapse
Questions...
So does the Zip need to be flashed?
Then install the APK?
Is the Amazon launcher disable by doing this, or do I have to disable that myself?
Can you easily remove it?

The Zip file is for customize.
SourceCode for Android Studio.
You must disable it .

OK so disable
com.amazon.tv.launcher
?
1. install APK
2. Flash zip ( for customize if you want)
3. disable launcher
The zip, what does it modify and how do you go back?
Sorry for the questions, just want to know what to expect if i have an issue...

Install other Launcher.
For mantis maybe you need FTVLaunchX to start the alternate Launcher.
#adb shell pm disable com.amazon.tv.launcher
Install apk to access the settings without amazon Launcher.
The Zip the SourceCode to build apk.
I hope it is understandable now

Thanks bro, this works perfect with ATV Launcher 0.1.2 now i can access amazon built-in apps on 4k stick.

Thanks for this.
Couple of queries:
Lots of icons on my custom launcher. But all start off at sleep. Is this normal? If so why so many icons?
The command to disable the amazon launcher is not working and I do have root. Any ideas?
Edit: Not to worry about the above. I found a new version that gives me just the one icon
Also found the instructions to delete the amazon launcher so that is good.
Only problem that some might have is installing new apps from the amazon marketplace (or whatever they call it).
Any ideas about how to do this?

Use this Version.
https://forum.xda-developers.com/showpost.php?p=82368799&postcount=1
Amazon Market is not working.
You must sideload the apps.
Also you can push the apps over the Amazon Website to your Stick.
App Updates should be installed automatic.

0815hoffi said:
Use this Version.
https://forum.xda-developers.com/showpost.php?p=82368799&postcount=1
Click to expand...
Click to collapse
Thanks for that.
I manage a lot of these sticks. Most I know the Amazon accounts for so will use the web site to push to them if they request new apps.
I will ask for the other account details but if they wont provide them I will send them to the website to install themselves if they want new apps.
It seems Amazon pushed out a new prime Video app today (or I was told about it today) that asks it you want to install it.
Was told it no longer works with this setup if it is installed. Was fine yesterday and no prompt to update then.
Might be a problem with the Prime Video app in general and not this setup, but all my sticks are running these fixes now.
Just tested on one and it is true. Trying to open Prime Video does nothing. Tried both the icons for it (one never worked but now both do not).
Will see if I can roll it back (once I find the original apk).
Thanks for this. So nice not to see the Amazon Launcher at all now.