Develop Bugs

[Q] Kindle Fire 2 / Firmware - 10.2.4 (not rooted) / APK downloader

Greetings,
(Today is Monday, 07.01.2013 and this post describes my question about using Kindle Fire 2 with apk-downloader 1.4.0 + Google Chrome 24.)
I want to apologize if this is a well known question, but I could not find anything relevant between the loads of info about Kindle Fire 1 and Kindle Fire HD. The question is: is it possible to use the last version of APK downloader (1.4.0) with Chrome 24 or 23 to download apks from Google Play for Kindle Fire 2.
I tried to follow the steps, described on the author's page but ultimately I failed. Here's what I did.
1. I did clear install of Windows XP in Virtual PC (in case the software turned to be malware)
2. I installed the last version of Chrome (24.xxx).
3. ...downloaded apk-downloader 1.4.0 and dragged it onto the extensions page of chrome, which initiated installation of the extension. Went ok.
4. ...ensured that one of my two ancient Google accounts (from the time before phone registrations and etc...) is accessible with the proper username and password (no google wallet of whatsoever personal information in it).
5. Downloaded Redphx's Device ID application via friend's phone - and installed it on kindle with Easy Installer (found on amazon appstore).
This was the first glitch - the device id application failed to show any device id. So I went on to 6
6. I found AIDE on Amazon Appstore and wrote a small application to retrieve the value of Secure.ANDROID_ID. I did that, because I read in some post that TelephonyManager.getDeviceId(); returns null on tablets that do not have cellular connectivity.
7. Entered the account info and the AndroidID into the plugin and went on Google Play. Whenever I'm on an app download page, the plugin icon appears, but also in the webpage under the application name I get "You don't have any devices." Clicking the plugin button in urlbar fails with error 400 "Bad request"
I guess, that either the android_id is not what google wants or the whole thing with apk downloader is a scam. Do You have any ideas? Some clever algorithm to generate fake device ids maybe? My friend's phone (Samsung Galaxy II) seems to download apks that mostly work when installed on my kindle. But I hate to be obtrusive enough to ask for his device id.
Here is a secondary question. Everybody seems to hide their device_id. If someone has Your device_id can he do something nasty?
.

Your question can best be addressed in the proper forum http://forum.xda-developers.com/forumdisplay.php?f=1789 .

[GUIDE] New Fire Phone with FireOS and Google Apps - A Start-to-Finish Walkthrough

I just got a Fire Phone via the Ebay sale, and like many others, I wanted to set it up with Google Apps. I also wanted to keep the working camera and NFC, so I decided to stick with FireOS. Doing that took a lot of searching, and flipping through multiple threads. It can get a little confusing. So I've collected all the steps here to help others (and myself, in case I need to do this again in the future, when I inevitably break something while tinkering). I've written this from the perspective of someone who has purchased a brand new Fire Phone from a third-party seller.
PLEASE NOTE: Much of this is the work/discoveries of other forum members. I'll link out to the original posts whenever possible. Please thank those people accordingly!
1. When you first start up your phone, connect to WiFi, and let it go through the upgrade process to 4.6.4. Now is the time to register your phone with Amazon (by signing in with your Amazon account). You want that year of Prime, don't you?
2. SIM Unlock the phone (if you aren't using AT&T). It's easy!
a. Use a paperclip to pop out the SIM tray
b. Insert a non-AT&T nano-sized SIM card. (Mine came with an AT&T SIM in it. You can't use this card to SIM unlock)
c. A window should pop up, prompting you to enter the code that is on your box. Enter it.
d. Done!​
3. Open Settings>Applications & Parental Controls>Prevent non-Amazon app installation. Turn App Installation to ON
4. Make sure ADB is set up on your computer. (this is an easy guide to follow if you don't already have it: http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378 )
5. Download the following file to your desktop computer:
GSM Unlocked Firmware (this is a 1.2gb file) (http://forum.xda-developers.com/showpost.php?p=62768812&postcount=2). Rename this update.bin, and put it into the folder where ADB is installed.​Now we get our hands dirty:
6. If you are using Windows (I'm not), follow the directions that @Bingo Bronson posted here: http://forum.xda-developers.com/showpost.php?p=62768812&postcount=2. @DePingus also has an illustrated guide for ADB on Windows here: http://forum.xda-developers.com/showpost.php?p=62844581&postcount=14
6a. If you aren't using Windows, you can follow my steps (the same, just without all the Android SDK stuff, assuming you installed ADB in step #4)
a. Connect your phone to your PC & boot into recovery: When the phone is off, hold PWR + VOL. UP until the recovery screen appears
b. From the list, choose "Apply update from ADB"
c. In the command prompt, enter the following:
Code:
adb sideload path/to/update.bin
d. It should take a few minutes. When it's done, reboot your phone​
NOTE: If for some reason this isn't working for you, @jack9955 has posted steps on how to downgrade via Safestrap here.
7. Open Settings>Device>Get Info About Your Fire Phone. Your current version will be listed under Software Version, and it should now be 4.6.3
At this point, you may need to repeat step 3. I didn't, but it's worth checking.
8. Open the Amazon app store (one last time) and download ES File Explorer.
9. In the Silk Browser, open up the following links and download the files:
KingRoot (http://forum.xda-developers.com/fire-phone/help/root-4-6-3-t3173322)
Updated Google Play Store files: (http://forum.xda-developers.com/fire-phone/general/google-play-store-4-6-1-version-4-apks-t3098592)​
10. Open ES File Explorer, navigate to Download, and install KingRoot. Follow the directions to achieve root.
11a. At this point, some people like to remove KingRoot (out of security concerns) and replace it with SuperSu. I haven't done that yet, but you can follow the directions from @najoor here: http://forum.xda-developers.com/fire-phone/general/root-fire-phone-supersu-t3105546
12. Open ES File Explorer, navigate to Download, and unzip play.zip. Be sure to install the apks contained in the play.zip folder in the proper order (Thanks to @escape75 for these files)
1) Google Account Manager 4.4.2 (940549)
2) Google Services Framework 4.4.2 (940549)
3) Google Play Services 7.8.99 (2134222-036) - Updated
4) Google Play Store 5.8.8 - Updated​
13. After installing, I rebooted into recovery again, and wiped the cache partition. I don't know if you need to, but engaging in good housekeeping is never bad.
14. You should have a Play Store icon in your app drawer now. Click it to open, and holy crap!! It works. Plug in your google account details.
Now it's time to keep Amazon from wrecking all your hard work. Steps 15 or 15a will block OTA updates of the OS.
15. Go to Settings>Applications & Parental Controls>Manage Applications. Click Filter By and select All. Find each of the files listed below, click it, and then click the "Disable" button on the next screen. Repeat for the other three files. (thanks @Bingo Bronson)
Amazon Device Client
DCP Platform Contracts
System Update
System Update (yes, there are two different files named system update. Freeze/Disable both)​
15a. If you'd rather, you can do like I did, and use Titanium Backup Pro to freeze the above files.
16. Don't like the Launcher? Neither do I. I followed these directions to change out my launcher: http://spinyourfire.com/fire-phone-tips-and-tricks/fire-phone-launcher/ I use Home Switch from the Play Store. It will allow you to set your new launcher.
If you decide to use a new launcher, here's some info (courtesy @Bingo Bronson) which may help:
1. Settings>Display>Show Status Bar allows you to turn on the Status Bar at the top of the screen. This will help some launchers display properly.
2. Miss your NavBar / want some way other than Amazon gestures to navigate your phone? Try installing Ultimate Dynamic NavBar or Pie Controls.​
NOTE: The new launcher will disable Tilt Left/Right on your home screen. In Amazon apps, the gesture will still work.
17. To sync your contacts/calendars/etc, go to Settings>My Accounts>Manage Email Accounts and add your Google account info.
a. Select that account, check sync calendar and sync contacts.
b. Set Inbox Check Frequency to manual.
c. In Email Settings, set everything to off, then click email notification settings, and set all of those to off.​
BEWARE: HERE BE DRAGONS
Hi. Are you new to phone hacking? Then you should probably stop reading here. Following any of the links or info could (pretty easily) lead to bricking your phone. I won't even mess with most of this stuff, I'm just providing links for intrepid explorers who know what they are getting into, and are willing to risk it. SERIOUSLY, TURN AROUND HERE!
Seriously, you did all that work, and now you want to risk breaking it? Well yeah, me too. So let's cover our asses.
Backing Up with SafeStrap
First, let's back up what you've done. @ggow (to whom we all owe a debt of gratitude) has gifted us with SafeStrap, which allows us to boot into a version of TWRP recovery. From there, you can install his CM11 or SlimKat Roms, or use the backup feature, which is what we are about to do.
1. Install Safestrap from here http://forum.xda-developers.com/fire-phone/development/recovery-safestrap-v4-0-1-t3149888. In ggow's directions, it talks about 4.6.1, but I can confirm it works properly on 4.6.3.
2. Once you have booted into Safestrap, Click Backup and then back it up! (it took about ten minutes for me)
3. Of course, a backup won't do you any good if you don't have multiple redundancies. So plug your phone into your computer, open up a terminal/CMD prompt, and enter the following:
Code:
adb start-server
then
Code:
adb pull /sdcard/TWRP/ /path/to/your/backup/folder
after that runs for a while, you should see a message that says something along the lines of "12 files pulled. 0 files skipped"​
Good! Now we are backed up, and we can start breaking stuff.
Turn on USB Debugging
1. Go to Settings>Device>Get info about your Fire
2. Tap "Model Number" seven or eight times, until the "Developer Options" button appears at the bottom of the list
3. Tap "Developer Options" and enable USB debugging​Installing Xposed Framework
Xposed Framework allows you to install different modules that can change the look, feel and operation of your phone. Xposed works best on Vanilla Android, but we can definitely put it to good use here. Lifehacker has a great overview on Xposed. I'll just give you the basics here.
What you'll need: Root
1. On your phone, visit http://repo.xposed.info/module/de.robv.android.xposed.installer. Scroll down to the bottom of the page and click Show Older versions. You want the APK for version 2.6.1 (the most recent stable version)
2. After downloading, navigate to your Downloads folder and install the Xposed Apk.
3. Open Xposed and click Framework. It will show you that Xposed is currently inactive. Tap the install/update button.
4. Once installed, you must reboot your phone for Xposed to work.​Congrats! Now with Xposed, you can really start customizing your phone. Check the forums...there is tons to discover and lots of people who know far more than I about how to use it. Just remember that a lot of the cosmetic stuff might not work on a Fire Phone. The modules I use are: ACDisplay, Amplify (paid version), AppOppsXposed, GravityBox, Greenify (paid version), PowerNap.
Installing a custom Lock Screen
Many of us on Android are used to custom lock screens, and haven't been thrilled with the Amazon Lock Screen. Through some trial and error, I've discovered how to swap out the Amazon Lock Screen for my lock screen of choice, ACDisplay. I haven't tried this with other 3rd party lock screens. Try following (and contributing to) this lockscreen thread to see any developments on other lock screens.
What you need: Xposed, Root, ES File Explorer (or another file explorer with root access)
1. Install ACDisplay (I sideloaded the APK, but it seems to work from the Play Store)
2. Open ES File Explorer, tap the hamburger menu, scroll down to Tools, and turn on Root Explorer
3. find the installed apk (com.achep.acdisplay-1.apk) in /data/app
4. rename it LockScreen.apk and move it to /system/priv-app/
5. Reboot
6. Open up AC Display and grant it access to Accessibility Settings and Notifications
7. In ACDisplay>Settings>Lockscreen move the slider to On and make sure that "Enable when no notifications" is ticked
8. Open Xposed and activate the ACDisplay module.
9. Reboot
10. I don't know if you need to, but I went to Settings>Lock Screen> Turn on Notifications... and made sure that notifications were off.​
The Xposed integration seems to be the key. Now, when I reboot my phone, I'll get the original Amazon Lock Screen once (sometimes) and then ACDisplay pops up from that point on. Apparently, if you want a pin/password on the lock screen, you can still use the security features of the OS lockscreen.
Launchers with Widgets
One of the problems with custom launchers is that widgets don't seem to work on the Fire Phone. But @hmoobguy and @DePingus have figured out how to beat that in this thread. Just like with the lock screen, you'll have to move some files.
What you need: Root, ES File Explorer (or another file explorer with root access)
1. Install your launcher from the Play Store.
1a. If you haven't already, visit the Play Store on your desktop, look at the page for the launcher you just installed, and take note of what comes after 'id=' in the URL. That's the file name you'll search for.
2. Open ES File Explorer, tap the hamburger menu, scroll down to Tools, and turn on Root Explorer
3. find the installed apk for your launcher of choice in /data/app by searching for what came after 'id=' in step 1a.
4. move it to /system/priv-app/
5. Reboot​
Note: you can also use Titanium to convert your launcher of choice into a system app.
Other Stuff
@Bingo Bronson has a ridiculously extensive list of Fire OS apps that can be disabled/frozen or deleted. Use at your own risk: http://forum.xda-developers.com/fire-phone/general/complete-app-list-replace-remove-t3132008
Hopefully this is helpful to others. I can add information as I go if new info (and new annoyances) come to light. Please let me know if there is anything I missed!

Thanks man! That's a good list there!
I gathered much of the information you have posted there last night and I have it at 4.6.3 with Google Play and a custom launcher.
My next challenge is a single lock screen. I have yet to actually root it however.
Which seems it will be required to get any further with the lock screen deal based off what I've read thus far.
Cheers!
"curious what adds the extra slide lock, is it the adding of a different Launcher or Home Switch? Even when using the FirePhone launcher again it remains."

Natet2003 said:
"curious what adds the extra slide lock, is it the adding of a different Launcher or Home Switch? Even when using the FirePhone launcher again it remains."
Click to expand...
Click to collapse
I'm not quite sure what you mean here. I'm messing with the lock screen myself, haven't quite got it figured out yet. I use AC Display, and have been trying to freeze various apps listed in the App List post (at the bottom of the walkthrough under "HERE BE DRAGONS"). I can shut off the Amazon lock screen, but for some reason, my lock screen only works every other time. If I let it sit for a while and then unlock it, I just get the woven graphite background and nothing else. I have to turn off the screen, turn it back on again, and then my lock screen will work. I'm assuming it has something to do with the system putting the app to sleep.

Natet2003 said:
My next challenge is a single lock screen. I have yet to actually root it however.
Which seems it will be required to get any further with the lock screen deal based off what I've read thus far.
Click to expand...
Click to collapse
This thread has info on changing the lockscreen.
http://forum.xda-developers.com/fire-phone/help/fire-phone-lock-screen-t2982798/page5
You do need root. Install the new lockscreen (many people were using Next Lock Screen). Use a root file explorer to delete /system/priv-app/LockScreen.apk (make a backup first). Then move whatevernewlockscreen.apk from /data/app to /system/priv-app, rename it to LockScreen.apk and reboot.
I was having issues with the alarm clock and then I screwed up all the lockscreens. I gave up trying to fix my mess and just took the opportunity to install 4.6.3. That fixed all my issues and put me back to the stock crappy lockscreen, which I'm still running.

munkymack said:
I'm not quite sure what you mean here. I'm messing with the lock screen myself, haven't quite got it figured out yet. I use AC Display, and have been trying to freeze various apps listed in the App List post (at the bottom of the walkthrough under "HERE BE DRAGONS"). I can shut off the Amazon lock screen, but for some reason, my lock screen only works every other time. If I let it sit for a while and then unlock it, I just get the woven graphite background and nothing else. I have to turn off the screen, turn it back on again, and then my lock screen will work. I'm assuming it has something to do with the system putting the app to sleep.
Click to expand...
Click to collapse
I think I found what it was. I had "C Launcher" installed. It does an iPhone styled sliding lock screen that even when I swapped to another Launcher the lock screen kept activating. (So I had two screens to bypass) When I had experimented with GO Locker it added yet another screen to those so 3 screens!
So once I've removed CLauncher and GO Locker I've not just have a single screen, which is FireOS default lock screen.

Great instructions, well consolidated--thanks!!
Questions: 1. What's the reason you went through all the updates, all the way to 4.6.4 and then downgraded to 4.6.3. Could you just not have installed 4.6.3 from the beginning? 2. Also, why version 4.6.3? Is that the version on which google play works the best?--the reason I ask is because I too have read so many posts on this site and I have come to perceive that Google play still does not work perfectly on any of the versions!. Hopefully my perception is wrong and I can proceed with your consolidated instructions. Can you please post updates as the days go by on how its all working. Thanks.

dannyol said:
Questions: 1. What's the reason you went through all the updates, all the way to 4.6.4 and then downgraded to 4.6.3. Could you just not have installed 4.6.3 from the beginning? 2. Also, why version 4.6.3? Is that the version on which google play works the best?--the reason I ask is because I too have read so many posts on this site and I have come to perceive that Google play still does not work perfectly on any of the versions!
Click to expand...
Click to collapse
I went to 4.6.4 simply because my phone automatically updated from 3.5.0>4.6.1>4.6.4 when I connected it to wifi, and the directions I'd found showed how to downgrade from 4.6.4 (which is AT&T specific) to 4.6.3 (gsm unlocked).
The reason I chose to downgrade is because Play store doesn't work on 4.6.4...it keeps breaking. On 4.6.3, that's not the case (so far); Play Store (and even more important, Play Services, which is necessary for most Google apps) is working exactly like it should be. Might it break in the future? Yeah, probably. But if / when it does, I'll try and update the post (assuming that a fix gets found).

DePingus said:
This thread has info on changing the lockscreen.
http://forum.xda-developers.com/fire-phone/help/fire-phone-lock-screen-t2982798/page5
You do need root. Install the new lockscreen (many people were using Next Lock Screen). Use a root file explorer to delete /system/priv-app/LockScreen.apk (make a backup first). Then move whatevernewlockscreen.apk from /data/app to /system/priv-app, rename it to LockScreen.apk and reboot.
Click to expand...
Click to collapse
Just a heads up, DePingus and I have been discussing this on the linked thread, and the above instructions DO NOT work. LockScreen.apk does not exist in /system/priv-app/ on 4.6.3. At this point in time, there is not a way to completely replace the Amazon lock screen with a custom lock screen.

This is a good guide.
Just FYI, you don't have to enable USB debugging to root with KingRoot. And, more importantly, you don't have to be rooted or enable USB debugging to install 4.6.3, Google Play Services, or alternate launchers. Instead of adb push, you can just copy the apks over using your favorite method (USB, OneDrive, direct download) and then run to install. Come to think of it, you probably should move rooting and USB debugging into the "here be dragons" section.

Is it safe to update the play store when it asks?

MrPaulAR said:
Is it safe to update the play store when it asks?
Click to expand...
Click to collapse
Yes, as far as we know (for v. 4.6.3) Play Store can be updated and will still work, same with Play services.

New fire phone with version 3.5-rooted and now at a stand-still
Bingo Bronson said:
Yes, as far as we know (for v. 4.6.3) Play Store can be updated and will still work, same with Play services.
Click to expand...
Click to collapse
I too got my new fire phone on ebay. The fire phone has version 3.5. I read that it was a rootable version, so I proceeded to root the phone via towelroot . I have supersu installed also. I have verified root via an app and the phone is now successfully rooted. Now I am puzzled as to what I should do with the fire phone with version 3.5 and am at a stand-still!!.
Questions:
1. Can I update to version 4.6.3 from here without loosing root?
2. Will updating to version 4.6.3 in its present rooted condition cause any harm (i.e bricking) ?
4. If I need to remove root and supersu in-order to update the phone to version 4.6.3, how do I do that?
3. The reason for these questions is because I am assuming that I need to update to version 4.6.3 to install google apps.
Can you help me proceed along from this standstill that I find myself in!
Thanks

dannyol said:
I too got my new fire phone on ebay. The fire phone has version 3.5. I read that it was a rootable version, so I proceeded to root the phone via towelroot . I have supersu installed also. I have verified root via an app and the phone is now successfully rooted. Now I am puzzled as to what I should do with the fire phone with version 3.5 and am at a stand-still!!.
Questions:
1. Can I update to version 4.6.3 from here without loosing root?
2. Will updating to version 4.6.3 in its present rooted condition cause any harm (i.e bricking) ?
4. If I need to remove root and supersu in-order to update the phone to version 4.6.3, how do I do that?
3. The reason for these questions is because I am assuming that I need to update to version 4.6.3 to install google apps.
Can you help me proceed along from this standstill that I find myself in!
Thanks
Click to expand...
Click to collapse
I did the same thing when I first got mine, so I understand where you are coming from. After reading around on the forum, I saw that 4.6.3 could work with Play Store / Services, so I just did a straight up OS update. I didn't unroot or anything, and suffered no problems. My phone updated from 3.5 to 4.6.1, and then to 4.6.4. From that point, I downgraded to 4.6.3 and then proceeded with the steps in the guide.
As far as I can tell, you WILL lose root in the update, but you can use Kingroot to re-apply root.

Will this work on a Fire tablet? Would I just not run the GSM unlocked firmware part?
Thanks

jimbobalu said:
Will this work on a Fire tablet? Would I just not run the GSM unlocked firmware part?
Thanks
Click to expand...
Click to collapse
I have absolutely no idea. If it does work, let me know. I've got one of the new $50 fire tablets coming at the end of the month.

DePingus said:
Just FYI, you don't have to enable USB debugging to root with KingRoot. And, more importantly, you don't have to be rooted or enable USB debugging to install 4.6.3, Google Play Services, or alternate launchers. Instead of adb push, you can just copy the apks over using your favorite method (USB, OneDrive, direct download) and then run to install. Come to think of it, you probably should move rooting and USB debugging into the "here be dragons" section.
Click to expand...
Click to collapse
That's a good point. I've been doing this long enough that rooting is something I do without a second thought, but for beginners, it opens up the door to a host of problems. I'll do a reorganization next time it's slow around the office.

Thank you for the step-by-step guide. It was incredibly helpful and everything worked...expect for downgrading to 4.6.3. It may be because I'm on a Mac, but nothing I tried seemed to work. That is until I found this website that worked to perfection. Hopefully anyone else on a Mac finds it useful as well.
And apparently because I'm a new user, I can't post URL's, so here's the closest I can get you
seo-michael.co.uk/how-to-setup-adb-on-os-x

This phone is dirty cheap now.
i might grab one of these . here in Europe
cheers

Be sure and check the LTE bands before you do. You may not be able use high speed data there.
EDIT: I looked at the work in your signature. I'm pretty sure you know exactly what you are doing / getting yourself into if you do pick one up. I'm just trying to be super newbie friendly over here, hence my response.

Osufever said:
Thank you for the step-by-step guide. It was incredibly helpful and everything worked...expect for downgrading to 4.6.3. It may be because I'm on a Mac, but nothing I tried seemed to work. That is until I found this website that worked to perfection. Hopefully anyone else on a Mac finds it useful as well.
Click to expand...
Click to collapse
Yeah, ADB is different on every system, and can be a pain in the ass to set up. The Lifehacker article I linked should cover everything, but if Mac users want to delve a little deeper, then the link you followed is a good way to go. I'm glad you were able to get things working!

quickest way to load kodi/firestarter & backup?

What's the fastest way to install KODI & Firestarter? I'm using abdfire for everything, however, the whole process takes too long.
Any ideas? Also, is there a way to bypass the Amazon login portion.

If you take the time to figure out how to connect to the device via ADB, and put the files you want to install (eg kodi.apk, starter.apk) in the same directory as adb.exe, installing both can be done in about a minute. First on the FireTV > Settings > System > Developer Options, enable ADB Debugging and Apps from Unknown Sources.
Next start a command prompt in the adb.exe directory (Shift+right-click in the directory and select "Open command window here"). Execute commands:
Code:
adb connect 192.168.1.2
adb install -r kodi.apk
adb install -r starter.apk
Skip the -r if this is a fresh install rather than a re-install or update. To get your device's local IP address, go to Settings > System > About > Network and look at the first line
I don't know whether you can bypass logging into Amazon. What happens if you boot the device without internet access?

Patrick_445 said:
If you take the time to figure out how to connect to the device via ADB, and put the files you want to install (eg kodi.apk, starter.apk) in the same directory as adb.exe, installing both can be done in about a minute. First on the FireTV > Settings > System > Developer Options, enable ADB Debugging and Apps from Unknown Sources.
Next start a command prompt in the adb.exe directory (Shift+right-click in the directory and select "Open command window here"). Execute commands:
Code:
adb connect 192.168.1.2
adb install -r kodi.apk
adb install -r starter.apk
Skip the -r if this is a fresh install rather than a re-install or update. To get your device's local IP address, go to Settings > System > About > Network and look at the first line
I don't know whether you can bypass logging into Amazon. What happens if you boot the device without internet access?
Click to expand...
Click to collapse
Awesome, thanks! If I were to drop my backup folder into the same directory as adb.exe and run
adb install backup.folder
Do you think that would work? I'm at work & cant test it myself just yet.
Also, about the logging into Amazon part, I don't think you can bypass it because you need to enable ADB Debugging and Apps from Unknown Sources.
UNLESS, you can enable it somehow without logging in or correcting to the interest...

The backup folder would have to be pushed to the correct directory
Android\data\org.xbmc.kodi\files\
Sent from my iPhone using Tapatalk

Agk fire is another good tool that you can use...
Sent from my LGLS991 using Tapatalk

The adbfire GUI does this perfectly. I've got it down to a 15 min process from stock to modified inc add-ons etc. I'd recommend hardwiring the computer you run adbfire on, and have the firestick as close to the router as possible (or hardwire if it's a FTV.) If the add-ons arnt a big deal, you can have Kodi and Firestarter done within 10mins using the GUI. Anyway, restore process that works best for me is:
-Connect Firestick to WiFi, log in, enable adb debugging and unknown apps.
-Get IP from Settings>About>Network
(The rest can be done from a PC now.)
-Load adbfire GUI, connect using IP found above.
-Install APK (select the Kodi apk.)
-Install Firestarter using the button provided.
-Click 'Restore' and select backup taken using 'Backup' from a previously modded Firestick (with all the add-ons/build you prefer.)
-This can take between 15min and 1 hour depending on your connections to router (what I mentioned above about hard wire etc) and also the size of the backup. My build is over 1GB, hardwired PC with Firestick 3 feet from the router, it takes me 13min to restore.
Personally this took my install time down from ~2 hours to 15minutes, mainly because the build I prefer is so large and takes a lot of tweaking to get going (however once I had it sorted, taking a backup means newly-restored devices are 100% ready when the backup process is done.)
I've spent more time on this than I'd like to admit but I got sick of spending 2hours and headaches each and every time!

Lol. said:
Personally this took my install time down from ~2 hours to 15minutes, mainly because the build I prefer is so large and takes a lot of tweaking to get going (however once I had it sorted, taking a backup means newly-restored devices are 100% ready when the backup process is done.)
Click to expand...
Click to collapse
Why is your build so large? do you install other apps besides Kodi? Which addons do you use?
For those with a slow connection who are trying to build a FireTV (not the Stick), it might be faster to place the kodi backup on a microSD plugged into the device and move the directory from there to the Kodi userdata directory instead of trying to move it from a computer over Wifi.

The way i did it was...
1) Installed ES File Explorer
2) Installed Firestarter using ES File Explorer
3) Installed latest stable version of Kodi from FireStarter
4) Used Fusion/Wizard to install popular Add-ons (TVMC)
extremely easy

Patrick_445 said:
Why is your build so large? do you install other apps besides Kodi? Which addons do you use?
For those with a slow connection who are trying to build a FireTV (not the Stick), it might be faster to place the kodi backup on a microSD plugged into the device and move the directory from there to the Kodi userdata directory instead of trying to move it from a computer over Wifi.
Click to expand...
Click to collapse
Andy's build v7 - it's impressive - but a pain in the ass to get working (i4atv updated last week causing major headaches.) The latter is what led me down the backup/restore route.

Lol. said:
The adbfire GUI does this perfectly. I've got it down to a 15 min process from stock to modified inc add-ons etc. I'd recommend hardwiring the computer you run adbfire on, and have the firestick as close to the router as possible (or hardwire if it's a FTV.) If the add-ons arnt a big deal, you can have Kodi and Firestarter done within 10mins using the GUI. Anyway, restore process that works best for me is:
-Connect Firestick to WiFi, log in, enable adb debugging and unknown apps.
-Get IP from Settings>About>Network
(The rest can be done from a PC now.)
-Load adbfire GUI, connect using IP found above.
-Install APK (select the Kodi apk.)
-Install Firestarter using the button provided.
-Click 'Restore' and select backup taken using 'Backup' from a previously modded Firestick (with all the add-ons/build you prefer.)
-This can take between 15min and 1 hour depending on your connections to router (what I mentioned above about hard wire etc) and also the size of the backup. My build is over 1GB, hardwired PC with Firestick 3 feet from the router, it takes me 13min to restore.
Personally this took my install time down from ~2 hours to 15minutes, mainly because the build I prefer is so large and takes a lot of tweaking to get going (however once I had it sorted, taking a backup means newly-restored devices are 100% ready when the backup process is done.)
I've spent more time on this than I'd like to admit but I got sick of spending 2hours and headaches each and every time!
Click to expand...
Click to collapse
If I start jailbreaking these and selling them on Craigslist, should I be worried about Amazon suspending my email / account for using the same IP or email too many times?

vurze said:
If I start jailbreaking these and selling them on Craigslist, should I be worried about Amazon suspending my email / account for using the same IP or email too many times?
Click to expand...
Click to collapse
Well for a start, jailbreaking is not the right term here, lets leave that to iOS
Secondly, I'm not in the best position to advise, I don't sell these, I simply have a few and didn't want to spend hours sorting them all out once an update or a different build is released. I would suggest you do NOT use your personal Amazon account if you plan to do this though, it's not worth the risk. Perhaps look into creating a different one...

vurze said:
If I start jailbreaking these and selling them on Craigslist, should I be worried about Amazon suspending my email / account for using the same IP or email too many times?
Click to expand...
Click to collapse
gee.. how did I know the OP question was for this reason....

As stated in a previous post, I avoid adb all together and use ES Explorer to download Kodi apk and FireStarter Apk and then use Fusion Config Wizard for most popular add-ons.. I can get this all done under 10 minutes a stick.. On Black Friday and Cyber Monday I purchased 100 Firesticks for $2500 ($25/piece sale) (purchased in Delaware to avoid sale tax) and have been selling them side loaded with Kodi for $80-$100. Let's just say it's going to be a good Christmas. The market is saturated with these (Craigslist, eBay) I usually sell by word of mouth and I even have a few store owners who bought 5 at a discount.

[WINDOWS/LINUX][TOOL]Fire Toolbox V31.0

Fire Toolbox V31.0
All-In-One Toolbox for Fire Tablets!​
​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The Fire Toolbox is a collection of useful ADB (Android Debug Bridge) tweaks that can be applied to Amazon's Fire Tablets. The Toolbox project aims to help users fully customize and unlock the full potential of their tablets by putting all the power into their hands.​​The Toolbox doesn't touch the system partition meaning all changes made can be reversed either through the tools/subtools themselves or through a factory reset. This means the Toolbox does NOT void your warranty.​
View attachment 5469557
IMPORTANT INFORMATION REGARDING FIREOS 7.3.2.2+ AND THE TOOLBOX (PLEASE READ)
If your tablet is running FireOS 7.3.2.2 or above please note that some functions of the Toolbox may not work due to new restrictions in the new firmware. The following tools either do not work or have limited functionality:
• OTA Updates - OTAs can no longer be disabled.
• Manage Amazon Apps - Some system apps can no longer be disabled.
We're looking into workarounds to the issues detailed above. Please keep an eye on the forum for further development.
Click to expand...
Click to collapse
Device Name:Generation:​Amazon Fire 7 (2022)12​Amazon Fire 10/10+ (2021)11​Amazon Fire 8/8+ (2020)10​Amazon Fire 10 (2019)9​Amazon Fire 7 (2019)9​Amazon Fire 8 (2018)8​Amazon Fire 10 (2017)7​Amazon Fire 8 (2017)7​Amazon Fire 7 (2017)7​Amazon Fire HD8 (2016)6​Amazon Fire HD10 (2015)5​Amazon Fire HD8 (2015)5​Amazon Fire HD7 (2015)5​Amazon Fire HD7 (2014)4​Amazon Fire HD6 (2014)4​
In this forum, you may hear the word "generation" being used when talking about Fire Tablets. Just know that "generation" effectively means the same as "what year was the tablet manufactured?". This may seem confusing and as a result a reference table has been provided for you below.​
​
Getting the Toolbox up and running with your tablet is surprisingly a very easy procedure. The only thing required is for you to enable Developer Options and ADB on your tablet. So, without further ado, let's get started.​
At this point, please read the section below, and make sure to follow the correct guide that is made for your tablet on how to set up the device so it works with the Toolbox.​
FIRE HD 7, 8, 10 (2018 - 2022) Guide:​
Spoiler: Show Guide
​Before purchasing the tablet:​
Make sure you uncheck the "Link device to your Amazon account to simplify setup" box before Adding to Cart. (See this screenshot, credits go to @ancientrael)
if the box remains checked, your tablet will automatically update to the latest version of FireOS the second it auto-connects to your wifi.
Booting the tablet for the first time:​
Wait for your tablet to fully boot up for the first time (may take a few seconds to minutes).
When it boots, it will ask you for the language you'd like the OS to use. Select your prefered language.
Tapping the blue arrow at the bottom of the screen, you'll be asked to connect to a WIFI network.
Select ANY network from the list (even if you don't know the password).
Once it asks for the password, tap the "Cancel" button and it will take you to the previous screen with the Wifi networks.
At the bottom of the screen, you should now see a "Skip Setup" button, go ahead and tap that.
It will now ask if you're sure you want to skip fire setup. Just tap "Skip" once more.
You should immeditely be thrown into Fire Launcher. You're now ready to enable USB/ADB Debugging.
Enabling USB Debugging:​
Turn on your tablet and go to Settings > Device Options > About Fire Tablet and tap on the Serial Number until you unlock Developer Options.
Press the back button and find the new Developer Options and toggle it on.
Scroll down till you find USB Debugging and enable it.
Setting up the drivers:​​If you are on Windows 10 or Windows 11 you do NOT need to following this guide because Windows will setup the needed drivers by default automatically. All you need to do is plug your tablet in and Windows will take care of the rest. Please wait until these drivers are fully installed before laucnhing the Toolbox for the first time. ​
Download the latest version of the Toolbox from the Downloads section of this page and install it onto your PC.
Plug your tablet into the computer, and Windows will start installing the MTP drivers. It will also attempt to install the ADB driver but will fail. (This is normal and to be expected)
Launch the Toolbox, and it should detect your Windows version and inform you that further driver setup is required. It will then ask you if you'd like the Toolbox to download and install the drivers.
Click the "Yes" button, wait for the download to finish and follow the driver setup. If this for some reason doesn't work, please follow this guide to manually install the drivers.
At this point, If drivers are setup properly... the Toolbox will inform you that the "device isn't authorized. Please authorize your device now."
On your tablet, you should see a new prompt asking if you want to Allow USB Debugging and should show the computer's RSA key fingerprint. Tick the box that says "Always allow from the computer" and hit ok.
​That's it, the Toolbox should recognize your tablet and will take you to the main menu. Enjoy!​​
​
FIRE HD 6, 7, 8, 10 (2014 - 2017) Guide:​
Spoiler: Show Guide
Before purchasing the tablet:​
Make sure you uncheck the "Link device to your Amazon account to simplify setup" box before Adding to Cart. (See this screenshot, credits go to @ancientrael)
if the box remains checked, your tablet will automatically update to the latest version of FireOS the second it auto-connects to your wifi.
Booting the tablet for the first time:​
Wait for your tablet to fully boot up for the first time (may take a few seconds to minutes).
When it boots, it will ask you for the language you'd like the OS to use. Select your prefered language.
Tapping the blue arrow at the bottom of the screen, you'll be asked to connect to a WIFI network.
Select ANY network from the list (even if you don't know the password).
Once it asks for the password, tap the "Cancel" button and it will take you to the previous screen with the Wifi networks.
At the bottom of the screen, you should now see a "Skip Setup" button, go ahead and tap that.
It will now ask if you're sure you want to skip fire setup. Just tap "Skip" once more.
You should immeditely be thrown into Fire Launcher. You're now ready to enable ADB Debugging.
Enabling ADB Debugging:​
Turn on your tablet and go to Settings > Device Options and tap on the Serial Number until you unlock Developer Options.
Find the new Developer Options and toggle it on.
Scroll down till you find ADB Debugging and enable it.
Setting up the drivers:​​If you are on Windows 10 or Windows 11 you do NOT need to following this guide because Windows will setup the needed drivers by default automatically. All you need to do is plug your tablet in and Windows will take care of the rest. Please wait until these drivers are fully installed before laucnhing the Toolbox for the first time. ​
Download the latest version of the Toolbox from the Downloads section of this page and install it onto your PC.
Plug your tablet into the computer, and Windows will start installing the MTP drivers. It will also attempt to install the ADB driver but will fail. (This is normal and to be expected)
Launch the Toolbox, and it should detect your Windows version and inform you that further driver setup is required. It will then ask you if you'd like the Toolbox to download and install the drivers.
Click the "Yes" button, wait for the download to finish and follow the driver setup. If this for some reason doesn't work, please follow this guide to manually install the drivers.
At this point, If drivers are setup properly... the Toolbox will inform you that the "device isn't authorized. Please authorize your device now."
On your tablet, you should see a new prompt asking if you want to Allow USB Debugging and should show the computer's RSA key fingerprint. Tick the box that says "Always allow from the computer" and hit ok.
​That's it, the Toolbox should recognize your tablet and will take you to the main menu. Enjoy!​​
• ADB Shell - Spawn a Unix shell that can be used to communicate with the device and execute commands.​• Custom Launcher - Replace Fire Launcher with a custom launcher.​• Enable Widget Support - Enable widgets on supported launchers.​• Custom Sounds - Set custom sounds for notifications, lock/unlock events, low battery, and more!​• Density Modifier - Change the value of pixels per inch to either decrease or increase resolution.​​
Spoiler: Expand
• Restore Default Density - Restore the factory default density.​• Google Assistant - Replace Amazon Alexa with Google Assistant.​• Google Services - Install Google Services and the Play Store.​• Google Services (Manage)​• Add/Remove Google Accounts​• Clear Data/Cache for Play Services​• Uninstall Play Services​• Hybrid Apps - Sideload Amazon Appstore apps without having the Appstore enabled.​• Keyboard and Input - Manage other input methods and install custom keyboards.​• Lockscreen Wallpaper - Replace the lockscreen's wallpaper with a custom one. ​• Manage Amazon Apps - Manage the Amazon apps installed on your tablet.​• Hide/disable Amazon Apps - Hide and Disable Amazon apps through presets or manually select apps.​• Restore Amazon Apps - Completely restore every Amazon app or manually select apps to restore.​• Modify System Settings - ​• Power Options - Reboot, shutdown, reboot into recovery, or reboot the tablet into bootloader mode.​• Parental Controls Hide - Installs a service that auto-dismisses messages from Parental Controls.​• Privacy Controls - Disable telemetry collection of app usage data, interest based ads, etc. ​• Push and Pull​• Push - Transfer files from your computer to your tablet.​• Pull - Retrieve files from your tablet and transfer them to your computer.​• Remove Lockscreen Ads - Remove ads from the lockscreen.​• Screen Capturing - Record the device's screen, or capture a screenshot.​• Sideload Apps - Install APKs from sources outside of the Amazon Appstore.​• System Backup ​• Backup - Create a backup of the current system configuration.​• Restore - Restore system configuration from a previously created backup.​• User Management (8th gen and above)​• Create a User - Create a new user.​• Delete a User - Delete a toolbox created user.​• Switch Users - Switch the current user to a different Toolbox created user.​• YouTube Clients - Install third-party Youtube clients. ​​
Windows:
Version​Installer (.exe)​Portable (.zip)​Update Post​VirusTotal​V31.0​Download​Download​Post​Link​
Spoiler: Previous Versions
Version​Installer (.exe)​Portable (.zip)​Update Post​VirusTotal​V30.2​Download​Download​Post​Link​V30.1​Download​Download​Post​Link​V30.0​Download​Download​Post​Link​V29.0​Download​Download​Post​Link​V28.9​Download​Download​Post​Link​V27.0​Download​Download​Post​Link​V26.1​Download​Download​Post​Link​V25.2​Download​Download​Post​Link​V24.0​Download​Download​Post​Link​*Halloween Edition​Download​Download​*Bug Fix​Link​V23.0​Download​Download​Post​Link​V22.0​Download​Download​Post​Link​V21.0​Download​Download​Post​Link​V20.0​Download​Download​Post​Link​V19.0​Download​Download​Post​Link​V18.0​Download​Download​Post​Link​V17.0​Download​Download​Post​Link​V16.0​Download​Download​Post​Link​v15.0​Download​Download​Post​Link​V13.0​Download​Download​Post​Link​V12.0​Download​Download​Post​Link​V11.1​Download​Download​Post​Link​V11.0​Download​Download​Post​Link​V10.2​Download​Download​Post​Link​V10.1​Download​Download​Post​Link​V10.0​Download​Download​Post​Link​V9.2​Download​Download​Post​Link​V9.1​Download​Download​Post​Link​V9.0​Download​Download​Post​Link​V8.2​Download​Download​Post​Link​V8.1​Download​Download​Post​Link​V7.2.1​Download​Download​Post​Link​V7.1​Download​Download​Post​Link​V7.0​Download​Download​Post​Link​V6.56​Download​Download​Post​Link​V6.55​Download​Download​Post​Link​V6.54​Download​Download​Post​Link​
*Linux:
Version​Installer​Portable (.zip)​Update Post​VirusTotal​V2.0 (Beta)​Download​N/A​Post​Link​
Spoiler: Previous Versions
Version​Installer​Portable (.zip)​Update Post​VirusTotal​V1.0 (Beta)​Download​N/A​Post​Link​
* While in Beta, I'd like to heavy push the installer so that we can get it to stable along with the Toolbox. So, for now, the only download option will be the installer. Once the Toolbox and the Installer are both stable a portable option will be available. However, if you really need a portable version please PM me and I'll send you the link.​​
Other Downloads:
Resource​Resource Link​Applicable Tools​Custom Navigation Bar Icons​Google Drive Folder​Navigation Bar Modifier​Toolbox Changelogs​Google Drive Folder​N/A​
​
​If you like my work and would like to support me feel free to Donate. Thank you!

My Home Button isn't working after using the Custom Launcher Tool?​​Due to the way the process works, it alters your navigation bar's home key to send a key event that can be picked up by Automate. Once Automate reads this event, it launches your custom launcher automatically. ​​However, if the flow in Automate isn't running, the navbar key will not work, and nothing will happen when it's tapped. To fix this, either open Automate and start the "Launcher Invoker" flow again, or execute the Custom Launcher tool in the Toolbox, click the ":" icon (upper-right) to show the Tool Options panel, and click the "Restore Navigation Bar" button to restore the stock layout. ​
Click to expand...
Click to collapse
​Google Family Link won't work on my tablet?​​Unfortuently, no matter how hard we try, we still haven't been able to get Family Link to work correctly on the tablets. The Family Link app fails to install, and the Child account refuses to login. No matter what we tried, we couldn't get a Child account to work on the tablets.​​We believe this has to do with missing dependecies, and the tablets not being certified through Google's Play Protect platform. We're still activly looking into getting the issue resolved. Until then, it's recommended that you use an alternative such as Amazon's FreeTime, Eyezy, or another third-party family managing software.​
Click to expand...
Click to collapse
How can I remove a Google Account from my tablet?​​Because of the missing accounts section in the Settings app it will be a little more difficult to remove Google Accounts directly from the tablet. The easiest way that I've found is to visit this page: https://myaccount.google.com/security, sign-in to your Google Account, scroll down to "Your Devices" and click the "Manage devices" button. From the list of devices find your tablet and in the upper right-corner click the 3-dot icon and from the list select "Sign out". ​
Click to expand...
Click to collapse
​Can the Toolbox be used to root my tablet?​​Primarly, rooting a Fire Tablet requires the user to open the back of the device and short out a certain point on the motherboard. The Toolbox has been designed for folks who'd rather not bark down this alley. It uses the power of ADB to make changes, and is meant to be an alternative to rooting. In summery, the Toolbox isn't designed to root.​
Click to expand...
Click to collapse
​The Toolbox is being marked as a virus?​​This is likely because the Toolbox (and it's installer) aren't signed with a software license. This freaks Windows out because it sees that there is no publisher, and as a result it displays a warning (smartscreen). In addition, some anti-viruses might also flag the Toolbox as a virus simply because the build is relatively new and there is no record of it in the anti-viruses database, resulting in a false positve.​​As always, I take your security and privacy VERY seriously! If you do not feel safe with installing the Toolbox due to virus concerns, I respect and support your decision. It is always up to the user and their judgment! ​
Click to expand...
Click to collapse

2018 HD 8, did the remove lockscreen ads. went through its process. said sucess. nothing changed, and nothing in the downloads folder

Mx43Racing said:
2018 HD 8, did the remove lockscreen ads. went through its process. said sucess. nothing changed, and nothing in the downloads folder
Click to expand...
Click to collapse
This tool is designed to install Automate, push Amazon Lockscreen Ads Remover V4.5 to tablet, and install all permissions required to run the script. Now, to get it all set up and working you need to enter Automate and open the settings. From here you are looking for an option that's titled "Run on system startup" make sure you enable this option. Now, for installing the adblocker you can import it into Automate (Flow is found on your internal storage or sdcard) Or you can download the script from the automate community. Refer to this forum if you need assistance (skip steps 1-5 because they have already been done automatically by the toolbox). Sorry I can't write up a detailed post, I'm at a family gathering at the moment. Just let me know if you need further assistance.

Great tool! However, after "removing everything Amazon", it seems to have also removed parental controls which screws up some things. I get "the requested action is not permitted. Check parental controls settings and retry" when I try to download offline translation functionality in Google Translate. When I go to the the tablets settings>parental controls, it won't open. Also seems to not allow install of Amazon related apps like kindle and prime video.

newfires said:
Great tool! However, after "removing everything Amazon", it seems to have also removed parental controls which screws up some things. I get "the requested action is not permitted. Check parental controls settings and retry" when I try to download offline translation functionality in Google Translate. When I go to the the tablets settings>parental controls, it won't open. Also seems to not allow install of Amazon related apps like kindle and prime video.
Click to expand...
Click to collapse
It's kind of annoying right? So, whats happening is Its coded to remove Parental Controls but I've just discovered it isn't able to because Parental Controls is a Device Administrator which you can't uninstall even with ADB without deactivating it first. As a result, I will update the tool so it doesn't remove anything related to parental controls until we can find a way to disable it. However, chances are kind of slim. I don't think its possible without root but we will see. I'm also thinking about a restore option for the "Remove Everything Amazon" tool that returns the amazon system apps so you don't have to do a factory reset.

Datastream33 said:
It's kind of annoying right? So, whats happening is Its coded to remove Parental Controls but I've just discovered it isn't able to because Parental Controls is a Device Administrator which you can't uninstall even with ADB without deactivating it first. As a result, I will update the tool so it doesn't remove anything related to parental controls until we can find a way to disable it. However, chances are kind of slim. I don't think its possible without root but we will see. I'm also thinking about a restore option for the "Remove Everything Amazon" tool that returns the amazon system apps so you don't have to do a factory reset.
Click to expand...
Click to collapse
Pls let us know when it's updated I would love to remove amazon bloat and free up some space

Thanks for this tool! It worked a treat

question, if i remove everything amazon-related, can i still install kindle app from play store,? i tried this with a previous tool and had no succes, it would fail to install kindle from play store, i had to factory reset back.

jjta said:
Pls let us know when it's updated I would love to remove amazon bloat and free up some space
Click to expand...
Click to collapse
Of course
I'm not sure how long its going to take. Hopefully, its pretty quick! But, we will see!

ashaman25 said:
Thanks for this tool! It worked a treat
Click to expand...
Click to collapse
AWESOME! So happy everything was satisfactory!
That makes me extremely happy to hear!

Sertralina said:
question, if i remove everything amazon-related, can i still install kindle app from play store,? i tried this with a previous tool and had no succes, it would fail to install kindle from play store, i had to factory reset back.
Click to expand...
Click to collapse
Hmmm, I'm not sure about this. I can test it at home and let you know how it goes if you would like. However, it would be a few hours from now if your interested.

Will this work on a Kindle Fire 10" Gen 5 version? I've already hacked my wife's 2017 using another more complex path to doing so, but a friend just asked me to hack his Gen 5 10" and I'd love to do it as easily as this. However, a bit nervous if this doesn't allow it.

I think I answered my own question. Using a windows 10 computer, I connected the 10" Fire Gen 5... ran the program... and it continually crashed after initially finding the kindle. I never got the menu with the options. And where does this program unpack itself to once the EXE zip is run?

Quick question, is there already a new version around?

shonkin said:
I think I answered my own question. Using a windows 10 computer, I connected the 10" Fire Gen 5... ran the program... and it continually crashed after initially finding the kindle. I never got the menu with the options. And where does this program unpack itself to once the EXE zip is run?
Click to expand...
Click to collapse
I believe this may be a bug in the tablet detect section of the code. I know it can read Hd10 (2017), hd8 (2017), and hd (2018) without error. I'm not sure what's going on but I will look into it. Oh and also, a new version of the tool is coming soon!

klausb65 said:
Quick question, is there already a new version around?
Click to expand...
Click to collapse
I'm currently working on V2.0 as we speak. More information on that soon! Thanks!

Wow! Very nice! I will try it!
Thanks

Rortiz2 said:
Wow! Very nice! I will try it!
Thanks
Click to expand...
Click to collapse
hope you like it! let me know how it goes! thanks, Rortiz!

Thanks!
This is exactly what I was looking for, great work! can't wait for step "Remove Everything Amazon" on 8th gen

FIX YOUR APP SYNC! Smartwatch 3 is not dead yet!

OK guys your watch will still work with many Wear OS apps but apps won't sync up with your phone any more. The problem is that the version of Google Play Services on your watch is way out of date.
The solution is you need to sideload a newer version of google play services and then like magic all your apps that can still work with Wear OS 1.5 will work again.
You need to download and install adb fastboot on your PC, and the USB drivers for your particular model of phone. Then go to apkmirror and download the latest version of "Google Play Services (Wear OS)" as an APK.
Now put your Smartwatch into developer mode by going to settings --> about --> build number (click it 7 times, congrats you are now a developer)
Now go to Settings --> Developer Options --> ADB Debugging (enable) and Bluetooth debugging (enable)
Back on your phone, Wear OS App --> Advanced Settings --> Debugging over bluetooth (enable)
Enable Developer options on your phone as well through settings --> About --> Software info --> Build number seven times. Enable USB debugging.
Plug phone into PC with usb and open a command prompt in the directory where you've installed the adb files
Code:
ADB devices
should show your phone unauthorized. Authorize it on the phone popup prompt. Now the command should show your phone as "device"
Code:
adb forward tcp:6666 localabstract:/adb-hub
adb connect localhost:6666
On your watch, authorize the connection
On your phone, Wear OS app, Advanced settings, you should see Host: connected and Target:connected
If you get into trouble, run
Code:
adb kill-server
and try again.
Now you can install the apk
Code:
adb -e install -r (path to apk)
it will take a long while and may appear to hang. Give it time, at least 15 minutes. Go do something else. Wait for the command prompt to come back.
Now reboot your watch and revel in the magic as your apps suddenly reappear.
You also try sideloading other apps your mileage may vary. On APK mirror you can sometimes find older verions of Wear OS apps, look for ones that require Android 6.0+ Instead of 7.1.+

FYI I've tried sideloading several apps, and while many don't work properly, I was able to get Maps working by sideloading
com.google.android.apps.maps_10.35.2-1035250000_minAPI23(nodpi)_apkmirror.com.apk

Hi,
Thanks for this =)
Is there a reason to push the app through the phone instead of directly to watch?
EDIT: just do the same but directly connect the watch through USB worked well for me, including installing more apps like GMaps and Messages.
EDIT2: Just did this, so people could find this workaround faster =) https://support.google.com/wearos/thread/55427445

stormPremier said:
EDIT2: Just did this, so people could find this workaround faster =) https://support.google.com/wearos/thread/55427445
Click to expand...
Click to collapse
Sorry, this page can't be found. Do you have another link?

i5510 said:
Sorry, this page can't be found. Do you have another link?
Click to expand...
Click to collapse
Weird, I can't access this page using Private Navigation, you may need to be connected to your google account to access it ?
Also, it may not be published yet.

stormPremier said:
Weird, I can't access this page using Private Navigation, you may need to be connected to your google account to access it ?
Also, it may not be published yet.
Click to expand...
Click to collapse
Unfortunately, I don't use an account by Google. Would you mind quoting your solution here?

Hey first of all, thank you to bring me a light to follow,
I can confirm that if you use usb is more quickly, just I have:
1: installed "15 seconnds adb installer v1.4.3" found on this forum
2: Plug my smartwatch 3 on my pc (windows 10)
3: downloaded the most recent google play services (wear os) from apk mirror
4: rename the downloaded apk with a shorter name
5: placed the apk on C: and then open a power shell window in that location (****f+right click)
6: put this command adb install -r -g aplicationname.apk
7: wait 5 minutes
8: enjoy
by: Alexai Medina

i5510 said:
Would you mind quoting your solution here?
Click to expand...
Click to collapse
Hi people,
I own a sony smartwatch 3, got some problems about sync multiple times. I always found simples workarounds but some days ago, Google dropped support for wear 1.5 devices.
I consider this as an official announcement:
https://support.google.com/wearos/thread/5538033?hl=en
Therefore, we have a "workaround" for those that need more time to buy another smartwatch or else.
Inspired from this: https://forum.xda-developers.com/smartwatch/smartwatch-3/fix-app-sync-smartwatch-3-dead-t4121409
# Download the latest GService for Wear OS
Using apkmirror website you can find the latest apk for "Google Play Services (Wear OS)",
This link will give you the page of GService v20.21.17 which is the latest available on 2020-06-25.
You must ensure 2 things:
- Is it the latest version
- Is it compatible with Android 6.0+ (as it's the wear android version, 7.0+ and above will not work)
You can also download other apks to install, see the "More" section at the bottom of this post.
Soon or later, Google will definitely drop android 6.0. When this will happen, the latest version will not be available anymore for android 6.0+, therefore it will be the end.
# Download/Install adb debugging tools on your computer
There are multiple ways to install the adb debugging tool, I recommend following the steps you'll find on XDA website: https://www.xda-developers.com/install-adb-windows-macos-linux/
Available for Windows, Linux, and macOS.
# Enable ADB Debugging options on your watch
Enable developer mode by going to
Settings --> about --> build number (click it 7 times, congrats you are now a developer)
Now go to Settings --> Developer Options --> ADB Debugging (enable)
Then open and keep the command line window (aka "terminal")
# Connect your watch to your computer
Then using the terminal, type "adb devices", after a moment, you should get a prompt asking for debugging permission on your watch: accept.
In the terminal, you should now see something like "14452D11F536B52 device" when typing "adb devices" again.
If you see "unauthorized" or else, you're not ready for the next step, go back and try again.
If you struggle at this step, you may need specific drivers or else for your watch, google will be your best friend at this point.
# Send the app to your watch
In the terminal, type "adb install -r path_to_the_apk_file", replace path_to_the_apk_file by the path to the file you download from apkmirror earlier.
Then wait, the installation can take several minutes. Once it's done, restart your watch and you should see the apps beginning to synchronize themself =)
----
If you're new to the command-line tool (aka "terminal"), I'll assume you're a window user.
So you may need to type something like "adb install -r C:/Users/Robert/Downloads/file_downloaded.apk", again, you'll have to replace Robert by your windows username and file_downloaded.apk by the name of the file you downloaded earlier.
The best way to get this line right: open the file explorer, click "This computer" in the sidebar, then click on your main hard drive, then the folder "Users". Here you should see a folder with your username, click on it, then go through folders & files until you see the downloaded file. Once it's done, you should be able to get the full pathname by click in the explorer address bar (didn't understand ? See https://winaero.com/blog/show-full-path-address-bar-windows-10-file-explorer/ ) then at this point you should know how to execute the last command by reading again the last step "Send the app to your watch"
----
# More
You can follow this step and install any apk you want, but I don't recommend installing apk not made for Wear OS even if it works
More apps installable this way on your watch if you don't want to wait for app sync:
- Google Messages (SMS), latest is v6.1.095 on 2020-06-25
- Google Maps, latest is v10.35.2 (android 6.0+) on 2020-06-25
The GMaps is a good example about obsolete versions: on 2020-06-25, the real latest available is v10.43.2, but it's android 7.0+ only, so don't expect GMaps to work indefinitely for your watch, it will stop working soon or later.
# Say thanks
Please, if you can click upvote or post an answer: it will help people with the same problem find this

Thanks for posting a simplified process.
I only used Bluetooth because I have other Wear OS watches that don't work over cable connect, so it's the way I am familiar with. I like to use different watches depending upon activity and mood. The Smartwatch 3 is a great watch for outdoor activities because it is sleek, waterproof, and very sunlight visible.

stormPremier said:
Hi people,
I own a sony smartwatch 3, got some problems about sync multiple times. I always found simples workarounds but some days ago, Google dropped support for wear 1.5 devices.
I consider this as an official announcement:
https://support.google.com/wearos/thread/5538033?hl=en
Therefore, we have a "workaround" for those that need more time to buy another smartwatch or else.
Inspired from this: https://forum.xda-developers.com/smartwatch/smartwatch-3/fix-app-sync-smartwatch-3-dead-t4121409
# Download the latest GService for Wear OS
Using apkmirror website you can find the latest apk for "Google Play Services (Wear OS)",
This link will give you the page of GService v20.21.17 which is the latest available on 2020-06-25.
You must ensure 2 things:
- Is it the latest version
- Is it compatible with Android 6.0+ (as it's the wear android version, 7.0+ and above will not work)
You can also download other apks to install, see the "More" section at the bottom of this post.
Soon or later, Google will definitely drop android 6.0. When this will happen, the latest version will not be available anymore for android 6.0+, therefore it will be the end.
# Download/Install adb debugging tools on your computer
There are multiple ways to install the adb debugging tool, I recommend following the steps you'll find on XDA website: https://www.xda-developers.com/install-adb-windows-macos-linux/
Available for Windows, Linux, and macOS.
# Enable ADB Debugging options on your watch
Enable developer mode by going to
Settings --> about --> build number (click it 7 times, congrats you are now a developer)
Now go to Settings --> Developer Options --> ADB Debugging (enable)
Then open and keep the command line window (aka "terminal")
# Connect your watch to your computer
Then using the terminal, type "adb devices", after a moment, you should get a prompt asking for debugging permission on your watch: accept.
In the terminal, you should now see something like "14452D11F536B52 device" when typing "adb devices" again.
If you see "unauthorized" or else, you're not ready for the next step, go back and try again.
If you struggle at this step, you may need specific drivers or else for your watch, google will be your best friend at this point.
# Send the app to your watch
In the terminal, type "adb install -r path_to_the_apk_file", replace path_to_the_apk_file by the path to the file you download from apkmirror earlier.
Then wait, the installation can take several minutes. Once it's done, restart your watch and you should see the apps beginning to synchronize themself =)
----
If you're new to the command-line tool (aka "terminal"), I'll assume you're a window user.
So you may need to type something like "adb install -r C:/Users/Robert/Downloads/file_downloaded.apk", again, you'll have to replace Robert by your windows username and file_downloaded.apk by the name of the file you downloaded earlier.
The best way to get this line right: open the file explorer, click "This computer" in the sidebar, then click on your main hard drive, then the folder "Users". Here you should see a folder with your username, click on it, then go through folders & files until you see the downloaded file. Once it's done, you should be able to get the full pathname by click in the explorer address bar (didn't understand ? See https://winaero.com/blog/show-full-path-address-bar-windows-10-file-explorer/ ) then at this point you should know how to execute the last command by reading again the last step "Send the app to your watch"
----
# More
You can follow this step and install any apk you want, but I don't recommend installing apk not made for Wear OS even if it works
More apps installable this way on your watch if you don't want to wait for app sync:
- Google Messages (SMS), latest is v6.1.095 on 2020-06-25
- Google Maps, latest is v10.35.2 (android 6.0+) on 2020-06-25
The GMaps is a good example about obsolete versions: on 2020-06-25, the real latest available is v10.43.2, but it's android 7.0+ only, so don't expect GMaps to work indefinitely for your watch, it will stop working soon or later.
# Say thanks
Please, if you can click upvote or post an answer: it will help people with the same problem find this
Click to expand...
Click to collapse
Thank you very much!!!!
You saved my watch!

Hi. In the link to install the adb debugging tool, I can only get as far step 6 connecting my phone. When i type 'adb devices' in the command prompt it says -
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
Nothing appear on my phone as per the step 7 "On your phone’s screen, you should see a prompt to allow or deny USB Debugging access"
Can anyone help?

@MrFleas
1) go again on EVERY.SINGLE.STEP this may feel dumb to do but it could help
2) if it does not work, try googling for swr50 USB drivers, you may need to download Android SDK and drivers - then reboot - then start again at step one
3) come back here to thanks or asking for more help
Envoyé de mon ONEPLUS A6003 en utilisant Tapatalk

Hi people, just realized we can also download the sony app to our phones (directly from phone or by using adb like on watch) so we can edit stock watch faces again =)
Here's the app to download to the phone: https://www.apkmirror.com/apk/sony-...ditor-2-0-0-20-android-apk-download/download/
Once installed, to edit watch faces, go to wear app, the edit watch faces =)

Seems like the same issue...
My hardly used smart watch is ALIVE again!
Thanks a lot guys!

I have latest but sync not working :/ i have a question is possibile install app with higher api or change apk API level ?

check the play service on your phone and install exactly the same version of the wear app
then it works

Cheers for doing this! Got my old smartwatch working cause of that. If anyone else reading this has issues at the' ADB device' point, and is using a linux based system, remember to use sudo on the commands -as otherwise i found that it would not enable the prompt to let me 'authorise' the device in order to send the apk to the watch.
Question- given that google have disabled the onboard step counter function on wear 1.5 devices (like this one), can we sideload a fitness apk via adb with this method that will then sync to our phones?

skwal83 said:
check the play service on your phone and install exactly the same version of the wear app
then it works
Click to expand...
Click to collapse
Hi, I've got the same issue. I had to change my phone. I've installed the same version of google play services on the watch with the description in this threat. But the phone is still not syncing the apps to the watch. Is there anything more I can do to trigger the sync (already triggered 'resync all app in Wear OS' without effect).

You might try to go Settings-Permissions on the watch and set the Permissions for your app. Sometimes I have got this to make the app work, when it is already installed on the watch but not working.

It works! I first downloaded this version of Wear OS for my phone:
Wear 2.43, the newest one somehow broke the sync for me.
By using ADB with " ADB install -r "I installed the last working Google Play Services for my Watch and also the last available version of Google Fit for Android 6.
Play Services : Play Services Wear OS - 20.45.16
Google fit : Google Fit - 2.10.36