Related
I fell into the 6.2.1 trap before I got Google Android Market installed. As a result of a partial market installation, I get periodic errors about the android market that pop up and need to be forced closed. I plan to do a factory reset and return the device to the store then buy a new one with the original OS. I need to know what to do so I can get it working with Android Market OTA.
Since the tablet has only 6+ GB to play with, I don't want to load it with too many hacking type tools or other OS. I am interested in seeing how Titanium Backup works but I don't know if I want to keep the KF permananently rooted. My main goal is to have Android Market available and working wirelessly. I am also trying do decide whether to block the the OTA update from Amazon permanently or just until I get my basic Google apps installed. So my plan is:
Get a new Kindle Fire with old OS
Leave WiFi off
Root with Super One Click
Install Google Android Market
Disable rerouting to Amazon Market
Am I right assuming that once installed, Google Android Market will continue to function once Amazon updates me to the latest version?
I also want to make sure that I have Google Mail and Google Maps and I don't know if 6.2.1 unrooted prevents installing those. I like the ability of the 6.2.1 to get rid of junk on the carousel and the scrolling speed seems a little better now. Of course videos are playable with unrooted KF.
Am I missing any steps or are there other recommendations?
You should be able to install Google maps and Gmail onto a regular 6.2.1 KF without any problems.
I don't think there's a known method to block the update while keeping full online functionality.
The best thing at the moment is to install a premodded 6.2.1 update with root access so you can install the Market Place etc.
In anycase if you return the unit for a new one there could (and probably will) be another update in a few weeks. So far there's been an update every couple of weeks since it came out. Each time you lose root and are back to square one.
I'm waiting for someone more clever than me to find a workaround to get root access back on a 6.2.1...
PS - 6GB is a lot of room for installing apps! I wouldn't worry about running out of room unless you're filling up your KF with downloaded media.
oh and PPS - Amazon updates can easily stop the market place from working. The 6.2.1 update has stopped mine from working (because I had it installed in /system/app which is one of the folders replaced in the last update.)
Got new 6.0 KF - Bootstrapping Catch 22
So I returned the 6.2.1 version and got a new one with 6.0 still installed. Now I find that I have no way of loading any apps with the stock unit. The directories that show up on the device through the USB connection are very limited. I copied the root explorer app to the documents directory but naturally it does not show up.
Without having a file explorer app, I don't know how to proceed. If I turn on and register the Kindle, I am liable to get updated immediately. If I can just get to the Amazon store and get a file explorer app and then quickly turn off wireless I may luck out. Are there any other ways to get an app installed without having an app like root explorer or similar without having to first go to Amazon market?
6.2.1? I'm still on 6.2. What's the deal? Why did i not get the update?
Update - I was able to quickly register and bring in the root explorer app. I then turned off WiFi and found I was still at 6.0. Now to try to root it...
Download the latest tools from the AFH link near end of post. It includes the changes in the attached "jobs" zip. You only need "jobs" if you downloaded the tools before May 11
EDIT May 29: Playstore is currently unreliable. Until updated, use the workaround here.
UPDATE May 17: Install Other Launcher and Install Kingroot tools may not complete if Windows username has spaces. I'll fix in next update. Until then, if your username has spaces, use this fix.
Here are tools for the 2014 Fire HD 6 and 7. A little late, I know, but some of you who still troll the forums may find them handy. Download the tools from AFH link, extract and run RUNME.bat.
IF YOU PLAN TO ROOT, TURN OFF WIFI NOW!
Tested working on OS 5.1.2.1 and below, except:
- Current Kingroot can't root 5.1.2.1. You need to downgrade. See "ROOT OS 5.1.2", below.
- OS 4: Only OTA blocking is implemented in the Block/Unblock jobs. [5/13/16 UPDATE: Also, Play Store isn't working on OS 4.
.. I probably won't fix it unless there's some demand. Try the video guide here. OS 4 users, also see post #11 for useful info about custom launchers.]
THE TOOLS
Install Play Store
Install Nova Launcher to /priv-app [root]
Install Other Launcher to /priv-app [root]
Uninstall priv-app Launchers [root]
Install Apps
Block/Unblock: OTA, ADS, AMAZON LAUNCHER, APPSTORE, AMAZON SEARCH [root]
Root Checker
Device Info
Root Tools
Install Kingroot ~ Root ~ Block OTA
Replace Kingroot with SuperSU [root]
DESCRIPTIONS
Before running a job, look here for any tips and instructions. This info is also in the readme.txt in the zip
INSTALL PLAY STORE - Like it says. Works on both rooted and unrooted OS 5. Not for OS 4. EDIT May 29: Playstore is currently unreliable. Until updated, use the workaround here.
INSTALL NOVA LAUNCHER - Installs Nova to /system/priv-app so widgets work. If you just rooted, make this your first custom launcher. You can replace it or add a different one later.
INSTALL OTHER LAUNCHER Installs the launcher app in user_launcher folder to priv-app. Get the apk for the launcher you want (from apkmirror.com for example) and put it into the folder and run the job. EDIT 5/16/2016: Filenames must end with ".apk" No spaces allowed; replace with "_". (The tool will find spaces and pause while while you fix.)
HOW TO INSTALL GOOGLE NOW (also in Readme.txt):
It's much easier to install Google Now if Amazon is blocked, and you need a custom launcher to do that.
1. If you don't have a custom launcher installed, use Install Nova tool (installs Nova and blocks Amazon)
If you have a custom launcher, block Amazon so your custom launcher is running.
2. Get Google Now (small) from apkmirror.com, e.g., put into user_launcher folder and run Install Other Launcher job.
You'll boot to your "other" launcher
3. Run Google Now in app drawer and:
If prompted to Update Google App (Get it from Google Play), do it.
If prompted that other launcher is default, tap link to go to Amazon Settings. In Apps & Games>Manage all Applications: Swipe to All, scroll to your other launcher, tap it and see if "Launch by Default" is on. If yes, Clear Defaults. If no, go to your launcher settings and see if you can turn off default there.
Some launchers don't give up their default easily. If pressing home key doesn't show "Select Home App" after doing the above, run Block/Unblock tool and switch to Amazon. Then block Amazon again. After restart, press home key and you'll get "Select Home App" and be able to choose Google Now.
UNINSTALL LAUNCHERS - Uninstalls and deletes everything associated with a launcher installed to /priv-app. If multiple, prompts you to choose the one to uninstall.
INSTALL APPS - Installs all the apps in the user_apps folder. Put the apks into the folder and run the job. Filenames must end with ".apk" No spaces allowed; replace with "_". (The tool will find spaces and pause while while you fix.) Don't install a launcher with this; use one of the launcher tools.
BLOCK/UNBLOCK - OTA, ADS, AMAZON LAUNCHER, APPSTORE, AMAZON SEARCH
Except for OTA, these work only on rooted OS 5. OTA does a soft block on unrooted OS 4, hard block on rooted.
OTA: Disables update packages and renames DeviceSoftwareOTA.apk for a "hard" block. Unblock reverses it.
ADS: Blocks/unblocks the lockscreen ads.
AMAZON LAUNCHER: Block disables the stock launcher (Amazon UI) and the Appstore, which forces the home key to use your custom launcher. Unblock switches you to Amazon. Checks for custom launcher before disabling Amazon. Black screen with multiple custom launchers: If you haven't set a default launcher, disabling Amazon will boot to black screen. (System doesn't know which launcher to use.) Press home key (circle at bottom) for launcher choices. TIP: To easily switch between your launcher and Amazon, use @bibikalka's guide here to set up "one-tap switching" from launcher home screen.
APPSTORE: Blocks the appstore so in-app links take you to the Play Store (instead of throwing that stupid Appstore prompt). Amazon complains bitterly if you run this from Amazon UI, so use it at your custom launcher or just use the Amazon launcher block.
AMAZON SEARCH: If you have Google Search installed, blocking Amazon Search makes your launcher search bar use Google instead of Amazon shopping.
DEVICE INFO - Just some specs that I find interesting. Lazy man's way to find out which tablet is plugged in, OS it's running, whether rooted . . .
INSTALL KINGROOT, ROOT, BLOCK OTA - Installs Kingroot, prompts you through rooting and blocks OTA updates.
- Installs kingroot v.4.8.5 by default.
- You can skip installation if Kingroot already installed
- You can install a later version if available: Check for new versions here: http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
ROOTING AND UPDATES: An update file can download while you're rooting. The Kingroot tool prevents it from installing as soon as you press Enter to tell the tool you're rooted. Then it looks for any downloaded file and if it finds one it tells you where it is and prompts you to delete.
Amazon says that updates install when the the device is not being used, but be aware that on OS 5 there's some risk. To minimize the risk, never leave the tablet idle while rooting. Just keep running Kingroot until root is successful and then press Enter to block installation of any download. (These instructions are in the tool.) To eliminate all risk, you can downgrade and root OS 4.5.3. On OS 4 the tool blocks update installation before rooting. (There's no way to do this on OS 5.) From OS 4.5.3, you upgrade with root in TWRP per bibikalka's root Tut.
True story: Kingroot once rebooted 5 times and told me "Root Failed" 3 times before finally succeeding. An update had downloaded to /cache, but the kingroot tool successfully blocked installation and found the file, which I deleted. So, although it's possible you could get upgraded, as long as you keep the tablet busy trying to root and then press Enter as soon as you're rooted, it's very unlikely.
REPLACE KINGROOT WITH SUPERSU - Installs W0lfDroid's sh script and prompts you through using it to replace Kingroot.
I reviewed and tested the script and it does (only) what it says: Removes all Kingroot (except Purify app, which tool uninstalls) and installs SuperSU. The tool uses SuperSU v. 2.4.6 for OS 5 (known working on OS 5.1.2) and SuperSU v. 2.4.9 for OS 4 (because 2.4.6 didn't seem to work).
FULL DISCLOSURE: I lost root one time after running this on OS 4. I think the problem was SuperSU 2.4.6 and that's why I changed it. I've tested many times and this only happened once, but you should know it happened. AFAIK W0lfDroid script is still the best free tool for the job.
ERRORS: Script was written to remove Kingroot from multiple android versions, so it tries to remove Kingroot files that don't exist on Lollipop. THIS PRODUCES LOTS OF ERRORS. THAT'S OK. I left in all commands so it will work on OS 4, too.
USE THIS SOON AFTER ROOTING. W0lfDroid's script should work fine even with root apps installed, but all I know for sure is it runs quick and easy on a "fresh" system.
ADB Sideload
There's an adb-sideload job in the jobs folder. I didn't put it on the menu because it uses commands that may not run on some systems. Also, if you know what you're doing, it's probably faster to manually sideload an update. If someone wants to try it, put the update bin file into adb_sideload folder and run sideload.bat.WINDOWS TESTING: Script was tested on English-language versions of Win 7 Pro and Home. Some testing on Win 10. (Thanks @SpaceBananas!) There's nothing that can hurt your tablet, but there may be kinks to work out based on Windows version. Hope a tester will work with me to help make the tools accessible to everyone. Thanks!
ADB DRIVERS REQUIRED: Try the guide in first link below. If problems, try the second.
Guide: http://forum.xda-developers.com/fir...ivers-fire-t3189000/post62561840#post62561840
Other options: http://forum.xda-developers.com/showpost.php?p=63072252&postcount=2
ROOT OS 5.1.2
IF YOU PLAN TO ROOT, TURN OFF WIFI NOW!
ROOT GUIDE: Follow this guide to use Kingroot and the root tools to set up your tablet.
At this time, Kingroot can only root OS 5.1.2 (February 2016) and below.
You can downgrade OS 5.1.2.1 (March 2016) to 5.1.2 and root, as explained in Root Guide, but this is an exception!
In general, never downgrade in order to use Kingroot. It's the fastest way to a brick!
You may be able to safely downgrade a higher OS to OS 4.5.3, root, and then upgrade in TWRP per @bibikalka's root Tut. Before trying this on an OS later than 5.1.2.1, make sure the tutorial says it's safe.
DOWNLOAD THE TOOLS FROM AFH ➔ . FireHD_TOOLS v 1.2
Update as of 5/11/16
➔ If you got the tools before the update, just replace the jobs folder in FIREHD_TOOLS with the one in attached "jobs_v1.x.zip"
Change Log
5/11/2016 - v1.2: Updated sideload.bat. (Missed the Find/Findstr fixes.)
5/10/2016 - v1.1: Fixed "No such file or directory" and "Permission denied" errors for users with *nix Find command installed
.
Nice Work!
@DoLooper - Magnum Opus, no less !
Why version 0.1 ??? The first release - solid 1.0 !!!
Updated. See OP.
Guys, I could use some feedback. Tools are getting downloaded a lot. Anybody using them? Are they helpful? Problems? Wishes? Anything? Thanks!
.
Updated again <sigh>. Sideload tool didn't get updated in v1.1. Apologies to those who downloaded the jobs zip.
DoLooper said:
Updated. See OP.
Guys, I could use some feedback. Tools are getting downloaded a lot. Anybody using them? Are they helpful? Problems? Wishes? Anything? Thanks!
.
Click to expand...
Click to collapse
Thanks DoLooper.
I tried these tools on my Fire HD 7 running 4.5.5.1 rooted with KingRoot.
I was able to use the script to successfully switch from KingRoot to SuperSU as well as to install Nova Launcher.
However, I had issues with the script elsewhere.
The play store seemed to install okay and it let me put in my google account info. After that, things went down hill. I was able to open the Play Store app without it crashing, but I just kept getting the "Error retrieving information from server. [RH-01]" message . I tried numerous things to correct this, but nothing seemed to work. In the end, I downgraded to 4.5.5, wiped data, cache and dalvik, and then flashed gapps via TWRP. This worked out, so all is good now.
I also had trouble with blocking the default launcher. Nova seemed to install okay, but the default launcher still worked and was a constant nag with each press of the home button. I fixed this by freezing the default launcher via Titanium Backup.
I don't know if these issues are particular to 4.5.5.1, or if I'm just unlucky. Regardless, I still appreciate your effort for putting this together. :good:
I'm currently trying to get wallpapers and widgets to work on the Nova launcher with no success. I tried the fixes intended for earlier Kindle models and (not surprisingly), they didn't work. Specifically, I tried Stunt's Wallpaper Fix and Kindlefree from the app store.
Any ideas where I should look for guidance on making Wallpapers and Widgets work?
Thanks again!
notorious.dds said:
Thanks DoLooper.
I tried these tools on my Fire HD 7 running 4.5.5.1 rooted with KingRoot.
I was able to use the script to successfully switch from KingRoot to SuperSU as well as to install Nova Launcher.
However, I had issues with the script elsewhere.
The play store seemed to install okay and it let me put in my google account info. After that, things went down hill. I was able to open the Play Store app without it crashing, but I just kept getting the "Error retrieving information from server. [RH-01]" message . I tried numerous things to correct this, but nothing seemed to work. In the end, I downgraded to 4.5.5, wiped data, cache and dalvik, and then flashed gapps via TWRP. This worked out, so all is good now.
I also had trouble with blocking the default launcher. Nova seemed to install okay, but the default launcher still worked and was a constant nag with each press of the home button. I fixed this by freezing the default launcher via Titanium Backup.
I don't know if these issues are particular to 4.5.5.1, or if I'm just unlucky. Regardless, I still appreciate your effort for putting this together. :good:
I'm currently trying to get wallpapers and widgets to work on the Nova launcher with no success. I tried the fixes intended for earlier Kindle models and (not surprisingly), they didn't work. Specifically, I tried Stunt's Wallpaper Fix and Kindlefree from the app store.
Any ideas where I should look for guidance on making Wallpapers and Widgets work?
Click to expand...
Click to collapse
Thanks for feedback. Tools apparently need work for OS 4.5.5.1. I tested pretty well on 4.5.3 and 4.5.5, but not 4.5.5.1. There may be some peculiarity there.
- The play store error has been reported on some 2015 Fires (using a different tool, but same method to install). It's unclear why it happens on some devices and not others, and they haven't found a fix, but it may be an OS 4 issue on the Fire HDs. I'll look into it.
- Nova & stock launchers: The block on stock launcher didn't work because it isn't implemented for OS 4. As mentioned at top of OP, only OTA block is available for OS 4. I'll need to add it in an update. Hadn't thought about need for it when using the Nova tool.
Would you please look in /system/priv-app folder and see if com.teslacoil.launcher.apk is at the bottom of directory? If so, are perms set to rw- r-- r--? Let me know and we'll proceed from there to get you widgets. Thanks.
DoLooper said:
Thanks for feedback. Tools apparently need work for OS 4.5.5.1. I tested pretty well on 4.5.3 and 4.5.5, but not 4.5.5.1. There may be some peculiarity there.
- The play store error has been reported on some 2015 Fires (using a different tool, but same method to install). It's unclear why it happens on some devices and not others, and they haven't found a fix, but it may be an OS 4 issue on the Fire HDs. I'll look into it.
- Nova & stock launchers: The block on stock launcher didn't work because it isn't implemented for OS 4. As mentioned at top of OP, only OTA block is available for OS 4. I'll need to add it in an update. Hadn't thought about need for it when using the Nova tool.
Would you please look in /system/priv-app folder and see if com.teslacoil.launcher.apk is at the bottom of directory? If so, are perms set to rw- r-- r--? Let me know and we'll proceed from there to get you widgets. Thanks.
Click to expand...
Click to collapse
Thanks for the help!
I found the com.teslacoilsw.launcher-1.apk file, but it's in my /data/app folder... and it is chmod'ed to 644.
Also, I did successfully install the AppWidgetPicker.apk and LiveWallpapersPicker.apk files to /system/app using the "kindlefree" app, but I think that about all the app did. These files are also chmod'ed to 644.
notorious.dds said:
Thanks for the help!
I found the com.teslacoilsw.launcher-1.apk file, but it's in my /data/app folder... and it is chmod'ed to 644.
Also, I did successfully install the AppWidgetPicker.apk and LiveWallpapersPicker.apk files to /system/app using the "kindlefree" app, but I think that about all the app did. These files are also chmod'ed to 644.
Click to expand...
Click to collapse
I've been using OS 5 for too long! Forgot you can't get wallpaper on OS 4 without fussing. It's unclear from your post: Did the pickers get wallpaper to work? This is the way we did it back when we always booted twrp and installed xposed: http://forum.xda-developers.com/fire-hd/general/how-to-wallpaper-custom-launcher-t3123009
As to widgets: What I meant is, you should have /system/priv-app/com.teslacoil.launcher_4.2.2.apk. Do you? I just retested this on 4.5.3. Nova (com.teslacoil.launcher_4.2.2.apk) got copied there and chmod'ed to 644 as it should and widgets are working fine.
No wallpaper is a bad problem, though, and no tool can fix it--unless that LiveWallpapersPicker DID work. Let me know. And let me know about /system/priv-app/com.teslacoil.launcher_4.2.2.apk.
BTW, how come you want to stay on OS 4?
DoLooper said:
I've been using OS 5 for too long! Forgot you can't get wallpaper on OS 4 without fussing. It's unclear from your post: Did the pickers get wallpaper to work?
Click to expand...
Click to collapse
Nope.
DoLooper said:
This is the way we did it back when we always booted twrp and installed xposed: http://forum.xda-developers.com/fire-hd/general/how-to-wallpaper-custom-launcher-t3123009
Click to expand...
Click to collapse
I think I tried that to no avail, but I can't remember exactly which module I used.
DoLooper said:
As to widgets: What I meant is, you should have /system/priv-app/com.teslacoil.launcher_4.2.2.apk. Do you? I just retested this on 4.5.3. Nova (com.teslacoil.launcher_4.2.2.apk) got copied there and chmod'ed to 644 as it should and widgets are working fine.
Click to expand...
Click to collapse
I think I ended up installing Nova via the app store so that's why it wasn't on the system partition. However, my widgets seemed to work when I checked again. I have no idea why they wouldn't work when I first tried them. I did end up creating two simple scripts via the "Scripter" app that would enable and disable the stock launcher. I put them as widgets on the nova desktop allowing for single click toggling of the stock launcher.
DoLooper said:
No wallpaper is a bad problem, though, and no tool can fix it--unless that LiveWallpapersPicker DID work. Let me know. And let me know about /system/priv-app/com.teslacoil.launcher_4.2.2.apk.
Click to expand...
Click to collapse
No, nothing seemed to fix the wallpaper... always black. Am understanding this correctly that the wallpaper works on this thing if I load Lollipop?
DoLooper said:
BTW, how come you want to stay on OS 4?
Click to expand...
Click to collapse
I didn't want to fiddle around with change the bootloaders every time I wanted into TWRP. At this point, it doesn't matter anyway... I hard bricked the device by flashing the 5.2.0 stock recovery last night
The post about using this to revert to stock should be edited or removed. It's bad.
The only reason I was trying to revert to stock was that I ended up getting into a situation where the stock launcher would continue looping back to the Welcome/select language screen. I wiped cache, data, and dalvik and reflashed the 4.5.5 rom which didn't fix it. I even tried that same approach including a wipe of system... same result. I was quite surprised to see the problem continue even after wiping everything. At that point I figured I go back to full stock and start over... BAD IDEA.
Anyway, I ordered a new one and it should be here tomorrow. I'm now curious if it's possible to recover the bricked device via the UART port on the motherboard. We'll see.:fingers-crossed::fingers-crossed:
notorious.dds said:
. . .
I think I ended up installing Nova via the app store so that's why it wasn't on the system partition. However, my widgets seemed to work when I checked again. I have no idea why they wouldn't work when I first tried them. I did end up creating two simple scripts via the "Scripter" app that would enable and disable the stock launcher. I put them as widgets on the nova desktop allowing for single click toggling of the stock launcher.
No, nothing seemed to fix the wallpaper... always black. Am understanding this correctly that the wallpaper works on this thing if I load Lollipop?
I didn't want to fiddle around with change the bootloaders every time I wanted into TWRP. At this point, it doesn't matter anyway... I hard bricked the device by flashing the 5.2.0 stock recovery last night
The post about using this to revert to stock should be edited or removed. It's bad.
The only reason I was trying to revert to stock was that I ended up getting into a situation where the stock launcher would continue looping back to the Welcome/select language screen. I wiped cache, data, and dalvik and reflashed the 4.5.5 rom which didn't fix it. I even tried that same approach including a wipe of system... same result. I was quite surprised to see the problem continue even after wiping everything. At that point I figured I go back to full stock and start over... BAD IDEA.
Anyway, I ordered a new one and it should be here tomorrow. I'm now curious if it's possible to recover the bricked device via the UART port on the motherboard. We'll see.:fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
Sorry to hear about the brick. Good thing Amazon is patient with us.
Yes, wallpaper works fine on OS 5. [For others who read this, on OS 4 the only way to get wallpaper is with Xposed (installed in TWRP) and the kindleBG module in the link I posted above. And BTW, although the tools don't block OS 4 Amazon launcher ATM, it can be done manually. Commands are here.]
Thanks for your input. Play store didn't work for me either this time, despite earlier success. Everything else except the launcher block (and other non-OTA blocks) does work, so for now I'm just going to edit post and see if there's any other interest in play store on OS 4. (I trust you'll get OS 5 on replacement or will want to update to it.)
As to TWRP: Once tablet is set up, booting TWRP isn't needed much except for upgrading. and bibikalka gives us lots of options for doing it.
Let us know if anything comes of UART port tests. You'd be the hero of the community!
Workaround for Windows username with spaces
The Install Other Launcher and Install Kingroot jobs may not complete if your Windows username has spaces in it. I'll fix this in next update. Meanwhile here's the workaround:
1. Right-click RUNME.bat and choose Edit. [file opens in Notepad]
2. Add a blank line under :: Set paths and run menu.
3. Type: SET "username=abc"
4. Make sure this section of RUNME looks like below and then save and close Notepad
Code:
:: Set paths and run menu.
SET "username=abc"
SET "main=%CD%\"
SET "jobsdir=%main%jobs\"
[remaining code]
This changes the username only for the tools. The rest of Windows continues to use the real username.
I'm getting ready to update. Please let me know if you found any problems.
Used the tool on my Fire HD 6 (4th Gen) running a Rooted OS 5.1.2.1 to install a new launcher and block OTA's, ads, fire launcher, appstore, and Amazon search. Everything worked without issue! Thanks for the awesome and simple to use tool! Tablet is now almost pure Android. Great work!!!
Sidenote: Used bibikalka's TUT (http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950) on my Fire HD 6 that was currently running Fire OS 4.5.3 with TWRP Recovery to obtain a Rooted Fire OS 5.1.2.1..
I adb'd the 5.1.2 upgrade to my slab this way.
$ adb push update-kindle-20.5.4.2_user_542168620.bin /sdcard/
3047 KB/s (663908627 bytes in 212.722s)
My OS is FIRE OS 5.1.2 Build Date March 31, 2016 1:37 AM.
I tried and got an error to the effect, "cannot upgrade because the upgrade you are trying is older than the one you have".
So I'm probably running an even later version of 5.1.2 where they blocked that loophole.
I'm just going to by a cheap Chinese slab and root that.
wallywallywally said:
I adb'd the 5.1.2 upgrade to my slab this way.
$ adb push update-kindle-20.5.4.2_user_542168620.bin /sdcard/
3047 KB/s (663908627 bytes in 212.722s)
My OS is FIRE OS 5.1.2 Build Date March 31, 2016 1:37 AM.
I tried and got an error to the effect, "cannot upgrade because the upgrade you are trying is older than the one you have".
So I'm probably running an even later version of 5.1.2 where they blocked that loophole.
I'm just going to by a cheap Chinese slab and root that.
Click to expand...
Click to collapse
use adb sideload in Stock recovery
Sent from my KFFOWI using XDA Labs
sd_shadow said:
use adb sideload in Stock recovery
Sent from my KFFOWI using XDA Labs
Click to expand...
Click to collapse
Yuh, I used sideload AND IT WORKED!!
I also have a fire 5th generation. Does the same procedure work for that, assuming I use the proper 5.1.2 for that device: https://kindle-fire-updates.s3.amaz...ate-kindle-global-37.5.4.2_user_542168620.bin
wallywallywally said:
Yuh, I used sideload AND IT WORKED!!
I also have a fire 5th generation. Does the same procedure work for that, assuming I use the proper 5.1.2 for that device: https://kindle-fire-updates.s3.amaz...ate-kindle-global-37.5.4.2_user_542168620.bin
Click to expand...
Click to collapse
yes
Sent from my KFFOWI using XDA Labs
Confirmed, this procedure worked for Fire (5th generation), however the amazon update file is different (see a few posts back)
I just got a fire HD 6 (4th Gen) with the 4.5.2 OS.
Everything I see talks about 4.5.3 and later. I have not turned on wifi, so basically in a holding pattern for now. I want to root/twrp and maybe a custom rom.
Can some give me advice on the best path to take? Should I upgrade then root? Or root then upgrade? Any advice is appreciated.
Hello. When I open Google Play on my Huawei watch 2, I can see a list of apps installed on my phone w/ the option to install them on the watch. One of those applications is "Messages" which is really Android Messages (https://play.google.com/store/apps/details?id=com.google.android.apps.messaging), but whenever I try to install it, the watch shows installing but never installs it. I even reset the watch and very first thing I did was try to install it again but it's still not working.
I could've sworn I had this installed on a past watch. Thoughts?
Yeah, I’m having the same issue since I reset my watch to pair with my note 8. What I’m thinking is there was an update but instead of just fixing, it broke something...as it’s been a trend on android wear. I did the reset on the 9th of Sept.
As much as I like android wear, because of all of these constant issues, I might jump ships and go to the Samsung gear s 3 classic...
Same issue. Came from Note Edge, had to Factory Reset watch to migrate it to my new Note8, which I think is dumb. Now I can't re-install Messages, which I was getting a TON of use out of for the last month or so since I found it. I want it back!
Slightly off topic, but I just found this yesterday and was able to pair my watch to a new phone without resetting or losing anything.
https://www.xda-developers.com/pair-android-wear-without-factory-reset/
ExodiusTSD said:
Same issue. Came from Note Edge, had to Factory Reset watch to migrate it to my new Note8, which I think is dumb. Now I can't re-install Messages, which I was getting a TON of use out of for the last month or so since I found it. I want it back!
Click to expand...
Click to collapse
Update! Specifically for the Huawei Watch (Original, not 2) Since you can plug the Huawei watch directly into the computer and use ADB to install apps directly onto it, I used this tutorial (Search Sideload Apps to Android Wear Smart Watch on Youtube, uploaded by Dave Bennett) to install this most recent version of the Android Messages apk, which I got from APKMirror (https:// www . apkmirror. com /apk/google-inc/android-messages-android-wear/android-messages-android-wear-2-1-167-release/) and it worked like a charm!
From the Tutorial, all I had to do was download the ADB files, then the apk, and put the apk in with the adb files. Follow the parts of the Tutorial that show you how to enable ADB on the Watch. The only command I ended up needing was ".\adb -d install (appname).apk" in Windows Powershell, which I launched by holding Shift and right-clicking in the folder with the adb files and the apk. Super straightforward. If you have any issues with it, let me know, and I'll try to clarify what I did a little better! Good luck! Sorry for the spaces in the Links, I'm too new to post links directly yet!
ExodiusTSD said:
Update! Specifically for the Huawei Watch (Original, not 2) Since you can plug the Huawei watch directly into the computer and use ADB to install apps directly onto it, I used this tutorial (Search Sideload Apps to Android Wear Smart Watch on Youtube, uploaded by Dave Bennett) to install this most recent version of the Android Messages apk, which I got from APKMirror (https:// www . apkmirror. com /apk/google-inc/android-messages-android-wear/android-messages-android-wear-2-1-167-release/) and it worked like a charm!
From the Tutorial, all I had to do was download the ADB files, then the apk, and put the apk in with the adb files. Follow the parts of the Tutorial that show you how to enable ADB on the Watch. The only command I ended up needing was ".\adb -d install (appname).apk" in Windows Powershell, which I launched by holding Shift and right-clicking in the folder with the adb files and the apk. Super straightforward. If you have any issues with it, let me know, and I'll try to clarify what I did a little better! Good luck! Sorry for the spaces in the Links, I'm too new to post links directly yet!
Click to expand...
Click to collapse
Perfect. I downloaded the apk, copy and pasted the install adb instruction, it installed and then updated. Great. Thnx!
Awesome, my first "Tutorial" post has a 100% success rate! (So far) Just glad I got it working for myself, and glad to have helped others with what I found. Can't imagine what Google managed to screw up that's preventing us from installing it directly, since it worked great before, and still works without any issues at all installed from this method.
ExodiusTSD said:
Update! Specifically for the Huawei Watch (Original, not 2) Since you can plug the Huawei watch directly into the computer and use ADB to install apps directly onto it, I used this tutorial (Search Sideload Apps to Android Wear Smart Watch on Youtube, uploaded by Dave Bennett) to install this most recent version of the Android Messages apk, which I got from APKMirror (https:// www . apkmirror. com /apk/google-inc/android-messages-android-wear/android-messages-android-wear-2-1-167-release/) and it worked like a charm!
From the Tutorial, all I had to do was download the ADB files, then the apk, and put the apk in with the adb files. Follow the parts of the Tutorial that show you how to enable ADB on the Watch. The only command I ended up needing was ".\adb -d install (appname).apk" in Windows Powershell, which I launched by holding Shift and right-clicking in the folder with the adb files and the apk. Super straightforward. If you have any issues with it, let me know, and I'll try to clarify what I did a little better! Good luck! Sorry for the spaces in the Links, I'm too new to post links directly yet!
Click to expand...
Click to collapse
This worked on my brand new HW 2 as well. I got it setup with my pixel, immediately downloaded the august security patch, rebooted and could NOT install the android messages app. Followed your instructions and it worked like a charm. So happy Thank you!!
OMG LOOK AT ME I'M SO AWESOME AND HELPFUL AND GETTING STUFF DONE but seriously, It's good to know I helped out a bit.
It would appear that they finally fixed the issue, finally just got it to install on my Huawei Watch paired with my Pixel XL. Last night I just clicked the card on my watch that says it failed, next it opened the Play Store, then I clicked install, afterwards it actually showed it downloading a nearly 5MB file and installed in about a minute total to complete.
I've been using a fire tv stick remote with my NP since pretty well day one. It has a few more buttons that I find makes life much easier. Since the November update using the on screen keyboard doesn't work. It looks like the NP/GBoard is registering the enter button as a right arrow. The remote still works perfectly everywhere else. I've tried the basics, reboot, unplug, clear cache, deleting GBoard updates, and repairing the remote. None of that has worked. I've been using the remote from the play store which works, but I'd rather not have to do that. Also, I can't find the original remote anymore, of course. I can find the remote for a DVD player I bought 17 years ago, but I can't find the remote for the nexus player. Any idea how to fix this?
I use the Fire TV remote as well because it doesn't have the same disconnect problems as the original remote. And I had the same issue with Oreo.
To fix it, I extracted the Leanback keyboard from the Nougat ROM and installed that. Then I went into Settings > Applications and disabled Gboard. The keyboard now works with the Fire TV remote within apps like the Play Store, but it still doesn't work in the search box in the launcher. But I don't really use search from the launcher since it can't even search Netflix, and I don't like the new launcher anyway. I figure I'll give it a little bit of time to see if they fix the issue (doubtful since apparently the Nexus Player won't be getting any more updates), and then I'll flash the old launcher too.
The Nougat keyboard (LeanbackIme.apk) is here. Since the Oreo update evidently removed it, it isn't replacing anything and so it can be installed just like any other APK:
https://androidfilehost.com/?fid=817906626617955164
The Nougat launcher (LeanbackLauncher.apk) is here. Since it replaces the Oreo launcher, it will probably need to be installed via root or custom recovery:
https://androidfilehost.com/?fid=889964283620774815
SenorChang said:
I use the Fire TV remote as well because it doesn't have the same disconnect problems as the original remote. And I had the same issue with Oreo.
To fix it, I extracted the Leanback keyboard from the Nougat ROM and installed that. Then I went into Settings > Applications and disabled Gboard. The keyboard now works with the Fire TV remote within apps like the Play Store, but it still doesn't work in the search box in the launcher. But I don't really use search from the launcher since it can't even search Netflix, and I don't like the new launcher anyway. I figure I'll give it a little bit of time to see if they fix the issue (doubtful since apparently the Nexus Player won't be getting any more updates), and then I'll flash the old launcher too.
The Nougat keyboard (LeanbackIme.apk) is here. Since the Oreo update evidently removed it, it isn't replacing anything and so it can be installed just like any other APK:
https://androidfilehost.com/?fid=817906626617955164
The Nougat launcher (LeanbackLauncher.apk) is here. Since it replaces the Oreo launcher, it will probably need to be installed via root or custom recovery:
https://androidfilehost.com/?fid=889964283620774815
Click to expand...
Click to collapse
Thanks dude,
The remote actually works fine for everything other than the search. The main reason I'd like that to work is for use with TerrariumTV. I'll give the leanback keyboard and see if it helps, but I have my doubts. I don't have my NP rooted so I wont be able to try the launcher.
the problem is that any code for touchscreen is not recognized.... i use a usb remote with a physical keyboard in the back and a fly mouse option. with that i can cover any kind of keyboard requirement by the app..... then use the other remote to watch tv .....
I install leankey keyboard from Play store then go to settings and change keyboard to leankey. Haven't found anything it doesn't work on.
Calum 2 said:
Thanks dude,
The remote actually works fine for everything other than the search. The main reason I'd like that to work is for use with TerrariumTV. I'll give the leanback keyboard and see if it helps, but I have my doubts. I don't have my NP rooted so I wont be able to try the launcher.
Click to expand...
Click to collapse
I guess it depends what search you're trying to get working. If you're talking about the search within a particular app, installing the Nougat keyboard should be enough, since the Nougat keyboard works fine with the Fire TV stick remote.
If you're talking about the search box at the top of the launcher, however, that's different. I suspected flashing the Nougat launcher would fix that, but I just tried it and it didn't work. So maybe it's a different app altogether. But I don't really use that search feature myself and I mostly just wanted the old launcher back, so I'm happy. For what it's worth, you don't need root to flash the Nougat launcher, just an unlocked bootloader.
In case anyone cares, here are the steps to flash the Nougat launcher without root
Prerequisite: your Nexus Player bootloader must be unlocked
Download the Nougat launcher from here: https://androidfilehost.com/?fid=889964283620774815
Download the latest TWRP for the Nexus Player from here: https://dl.twrp.me/fugu/
Reboot your Nexus Player to the bootloader
Code:
sudo adb reboot bootloader
Boot TWRP
Code:
sudo fastboot boot twrp-3.2.1-0-fugu.img
Once you're in TWRP, flash the Nougat launcher and reboot
Code:
mount /system
adb push LeanbackLauncher.apk /system/priv-app/LeanbackLauncher/LeanbackLauncher.apk
reboot
If you want to undo it, just reinstall the Oreo launcher by following the same steps with this file: https://www.androidfilehost.com/?fid=889964283620774817
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.