yashsingh1/xdaforums huggingface dataset:
[Fire Android Development] sd_shadow:
even with 5.0.X fastboot mode options were very limited

adb commands are Only for recovery and rom

---------- Post added at 12:53 PM ---------- Previous post was at 12:51 PM ----------

if you are sure firmware was 5.1.2 , that's fine, but downgrading the wrong version can brick the Fire
[Fire Android Development] cwhiatt:
I cannot seem to get this recognized as an adb device in order to sideload recovery.img or .bin file.

As I said, fastboot recognizes the device and I just ran fastboot reboot and the device rebooted so how limited the fastboot commands are I'm not sure.

Is there anything I can do with fastboot to either get recovery on this or get it operable?
[Fire Android Development] sd_shadow:
you are following my instructions in?

Unbrick 7in Fire 2015 5th Gen with ADB Sideload
[Fire Android Development] BeeWall:
You must enter sideload mode to be recognized. You can enter recovery with Power+Volume button on left(I think, otherwise try right) and use Volume and power to select update from ADB.
[Fire Android Development] cwhiatt:
Yes I know that. The issue is that when I adb sideload the zip file it comes up with device is null.

Update: I booted to recovery options and did a factory reset and the device did power up. Immediately thereafter I went to Dev Options and there is no update available so the device still has them turned off and also, ADB debugging is enabled.

The computer still is not recognizing it when connected via USB so I'm going to have to keep troubleshooting that so I can run some commands to get this thing back in order.
[Fire Android Development] BeeWall:
Maybe retry flashing, but be very sure you do everything like it says.
[Fire Android Development] cwhiatt:
Retry flashing how? I did a factory reset so the Flash Fire software app is not on the device nor is the CM12 zip file and I can't flash via adb because the device is not recognized.

I think I am going to have to go through the methodical step by step process to try to re-establish this device in the device manager. As of yet it has been a no go.
[Fire Android Development] BeeWall:
You can redownload. If you are still rooted, you could remove the OTA app. Then you can't update, if that is he concern. Or you could use a router to block the domains for updates. You can also delete the update bin, or restart regularly to keep it from finishing.
[Fire Android Development] cwhiatt:
It boots to the lock screen and I can swipe but there is no app drawer and I'm unable to launch any apps. It's weird.
[Fire Android Development] BeeWall:
Hmm. How did you get to settings? Maybe from there you can launch an app. Also, just realized you said updates are blocked already. So disregard my previous post.

EDIT: Go to Settings>Help and click on the words "Silk application" in the banner at top. It will launch silk. From there, download the ROM. After it's done, download the FlashFire apk, and install it. Then hit open. From there, it should work. Also, unless you want cm theme engine a lot, I'd suggest using fire Nexus. It's still being developed, and everything except cmte can be added with Xposed.
[Fire Android Development] cwhiatt:
When I go to settings > all apps I don't think I can launch an app from there. If I can't figure it out without wasting hours and days I may just get another one and then try to send this one back.
[Fire Android Development] BeeWall:
I just edited my previous post. It should help.
[Fire Android Development] cwhiatt:
That was a phenomenal suggestion [MENTION=7559542]PorygonZRocks[/MENTION] but unfortunately I'm so hosed up on the boot that the Silk browser banner is not even there. I'm going to tackle [MENTION=4267571]sd_shadow[/MENTION] step by step process to try and get it identified in device manager so I can equally get it recognized in adb.

To confirm [MENTION=4267571]sd_shadow[/MENTION], at present, if the device is off it does turn on once the usb cord is plugged into the computer so it seems to me that the computer and device have enough communication going between them to facilitate that. HOWEVER, at present it is not showing up in the device manager when it is plugged in nor is it recognized as adb device.

But you are saying if I go through the methodical process in your post I can crack that nut yes?
[Fire Android Development] sd_shadow:
the 2015 Fire will power on when connected to a power source, it's no indication of data connection

boot to recovery, select adb option, connect to pc

on pc open device manager

how is it listed in device manager?
[Fire Android Development] cwhiatt:
I didn't bring it to work with me today so I'll have to check it when I get home but my recollection from the trial and error session yesterday was that it wasn't showing up at all in device manager. I'll check it to confirm later tonight and report back. Thanks
[Fire Android Development] BeeWall:
Enable show hidden devices, and see if it is under Other.
[Fire Android Development] cwhiatt:
I plugged my S6 in and it shows up. I plugged in another Kindle Fire 5th Gen (an unrooted stock 5.3.2.1) and that shows up in device manager but when I go to plug my KF in I get nothing. [emoji45]

Both my S6 and the other working KF came up under portable devices.
[Fire Android Development] BeeWall:
Weird. Normally it would at least show up under Other as Unknown device. Maybe part of the USB port got damaged (just whatever part receives data?) I doubt it, but maybe. Just to be sure, after you put it in sideload mode, it does or does not show up under Other (show hidden devices must be enabled)? That could help figure out if it is hardware or software trouble.
[Fire Android Development] cwhiatt:
Does NOT show up. I think it is a bad USB port as it was plugged in all night and this morning only read 1%. I snagged a new Fire from Target just this morning. It's on 5.3.1 so if I do my work before connecting this thing to WiFi I should be all set.

I meant to ask [MENTION=7559542]PorygonZRocks[/MENTION], is it possible to get TWRP on 5.3.1 or do I need to use the Fire Flash to flash the Nexus rom?
[Fire Android Development] BeeWall:
FlashFire. TWRP is 5.0.x only.
[Fire Android Development] cwhiatt:
What is the success rate for 5.3.1?

I have tried maybe 4 times so far and it gets around the 65% and fails
[Fire Android Development] sd_shadow:
it can take a number of tries before it works

doesn't seem to be any Rhyme or Reason on

how Kingroot Works
[Fire Android Development] cwhiatt:
Usually all it takes is for someone to inqyire. ;-(

Rooted and OTA disabled.
[Fire Android Development] rviertel:
lost root after factory reset

Hi,

I was able to root the device, and follow all of the steps to install cyanogenmod, but after doing so I tried encrypting my device which turned out to be a mistake. It became unusably slow. To remove the device encryption I did a factory reset, but now I've lost root. Any advice on how to get it back? Can I still use the supertool to root the device?

Thanks,
[Fire Android Development] DB126:
Best course is to reload/sideload FireOS (same version as before) and start over. That's not a lazy or phosopical response. Best course IMO having lost root (hence no ability to flash a new ROM, SuperSU, GAaps, etc).
[Fire Android Development] rviertel:
Thanks for the response, not exactly what I wanted to do but I guess its not the worst scenario
[Fire Android Development] BeeWall:
Does enabling root in Developer Options work? Can you install SuperSu?
[Fire Android Development] rviertel:
Enabling it in developer options doesn't do anything. If I try to run su in a terminal emulator after activating it nothing happens. I can install the SuperSU app but its not able to update the binary.
[Fire Android Development] sd_shadow:
time to reflash stock firmware, and start over
[Fire Android Development] BeeWall:
Did you reboot after enabling? Did you try enabling for ADB only and seeing if that works?

What FireOS version did you have before CM? You can check here if you want to be sure. If it was 5.0.x, you can boot TWRP and flash the SuperSU zip.

If neither work, and you had 5.1.1 or higher, then Davey126 and sd_shadow are right, you have to reflash stock. Use the tutorial I linked to to find out what version to flash, and find the firmware here.
[Fire Android Development] rviertel:
The reboot did it! I didn't realize that part was necessary. Thanks all for your help
[Fire Android Development] BeeWall:
Rebooting is generally the first step in troubleshooting. Unless you deleted the system, it does no harm ?
[Fire Android Development] DB126:
Great! Jumped to conclusion device had rebooted having gone through an encrypt/decrypt cycle. Another example of never assume! :).
[Fire Android Development] rviertel:
It did go through a reboot both to encrypt and decrypt, but after the decryption root was turned off by default. I then turned it on in developer options but didn't reboot after turning it on, thinking that simply flipping the switch would be enough
[Fire Android Development] SweetyVolty:
Can I root and change rom in 5.3.2.1 with this method? Not quite sure about anything right now, Kingroot didn't worked out and if I can't root/rom it than I will kick this tablet out from window.
[Fire Android Development] BeeWall:
This uses kingroot. 5.3.2.1 currently has no known root method.
[Fire Android Development] SweetyVolty:
okay thank you. I have no idea what to do with this thing till a cure found. Its like I have a Lamborghini car but its engine is only 50HP. I just wanted to change the rom. :'(
[Fire Android Development] BeeWall:
https://xdaforums.com/amazon-fire/general/removing-lock-screen-ads-root-t3218946

https://xdaforums.com/amazon-fire/general/how-to-install-google-play-store-fire-t3486603

https://xdaforums.com/amazon-fire/general/launcher-root-launcher-hijack-v2-t3561026

None of these require root. Look through the forums and see what else you can find. With Play Store, you can install a bunch of other no root things like Navbar Apps.
[Fire Android Development] cwhiatt:
One thing I did notice on an unrooted stock one we have is that while I did install the Google Playstore on it, there are some apps (one of the temple run versions for example) that will not install because it says the device is not compatible.
[Fire Android Development] wil.e.coyote:
TechDad, is there a special way to give "full access via setting?" I went to settings menu for both apps but didn't see a way to give them any more access. Sorry if this is a dumb question but I'm trying to learn..... Thanks!
[Fire Android Development] BeeWall:
He was referring to Accessibility, I believe. I've tested, it does not help, or did not in my case.

---------- Post added at 02:42 AM ---------- Previous post was at 02:14 AM ----------

You can get the APK online. It may be showing up that way because play store was not intended to be on the device.
[Fire Android Development] cwhiatt:
Aren't the zip files you download from GAPPS project just container files with the 4 apk files within? I am pretty sure they are.
[Fire Android Development] DB126:
Poster noted some apps are marked "incompatible" and will not download when the Play Store is installed on this device. A common workaround is to grab a copy of app from another reputable source such as APKMirror and 'sideload'. Dont believe question has anything to do with installing the Play Store app itself.
[Fire Android Development] cwhiatt:
Maybe I am mot clear or misunderstood.

The one unrooted one we have I did sideload or flash GAPPS on it without issue.

I did notice that when attempting to download certain apps via play store, they would not download and would say they were incompatable with the device.

Are you saying a workaround would be to download those apps from playstore using another device (say my rooted KF 5th gen or my S6) and then copy those app apk to unrooted KF and install them that way?
[Fire Android Development] sd_shadow:
easier to just download blocked apps from

Apk mirror

http://www.apkmirror.com/
[Fire Android Development] BeeWall:
I'm not sure. I'm just guessing that maybe it's missing some framework or something. I think the zips have apks, yes. But they have a lot more than 4 ? I'm not sure how many are actually necessary though.
[Fire Android Development] DB126:
Perfectly clear. Play Store assesses the host device to determine if the target app is compatible with the underlying hardware/software and meets regional requirements. Probably some other criteria too that Google does not disclose. For whatever reason the algorithm has determined your rooted tablet doesn't meet 'specs' for certain apps. This is a common problem with custom ROMs and/or when Google properties are installed on uncertified devices. Common workaround is to grab the app from another trusted source like APKMirror.

I understand the unrooted device does not behave the same way. This is also common: two nearly identical devices/installs behave differently. You can try reloading the Play Store on one/both or consider a custom ROM (Fire Nexus) which typically have fewer issues with Google properties.

Good luck.

---------- Post added at 01:08 PM ---------- Previous post was at 01:03 PM ----------

A minimal 'Play Store' install on an unrooted device involves four packages; see: https://xdaforums.com/amazon-fire/g...-google-play-store-fire-t3486603/post69280990
[Fire Android Development] BeeWall:
I know. That's where the 4 in my statement came from. I didn't mean necessary necessary, I was referring to things like Google Play Games, and maybe other things that apps might "need" to run. At least GPG is necessary for "full" functionality.
[Fire Android Development] DB126:
I have never installed Google Play Games and never missed it. Obviously an critical component for some games. Otherwise adds unnecessary bulk and complexity. Full functionality is in the eyes of the beholder.
[Fire Android Development] BeeWall:
Like I said, I don't know what depends on what. By "full", I meant all possible functions. I know that it is otherwise an opinion. My thought was maybe there is another Google app that some things depend on, which is why it might be incompatible. Though APKmirror is the best solution to "incompatibility". I have a tendency to overthink things ?
[Fire Android Development] DB126:
Well...however you 'think' the product is hugely valuable to the 5th gen Fire community, self included. A sincere Thanks for everything you bring to the table. :) :)
[Fire Android Development] TechDad378:
The settings are under "accessibility". Good luck, I have yet to duplicate my results.

Someone mentioned not registering the tablet when first boot. This is a strong possibility for root if you skip registration on initial boot. Reason being the tablet will only update if registered.

If you do skip registration and verify the tablet is NOT on version 5.3.2.1, root should be achieved. Just a thought!

TD378
[Fire Android Development] DB126:
Most Amazon devices arrive pre-registered if purchased with a personal account and will auto-update during or shortly after initialization. Best course of action is to boot into recovery mode and perform a factory reset prior to the first 'normal' boot. This will deregister device will leaving the rest of the stock startup experience largely intact.
[Fire Android Development] TechDad378:
Seems in theory, this concept will also work if you do not connect to wifi on first boot, verify version, factory reset then root.

Possibly a decent work around for time being...
[Fire Android Development] DB126:
Yes, this is the 'standard' recommendation for any Amazon device. Trouble is many folks enable WiFi when prompted during initialization or (worse) run an open AP that permits uncredentialed connections.
[Fire Android Development] crazyates:
The problem that a lot of people are having is that Kingroot requires wifi to root. If I could factory reset and root the device without wifi ever even turning on, I will test it immediately.
[Fire Android Development] DB126:
Some have a conceptual concern with the wifi requirement but the number of sucessful OTAs (unwanted FireOS upgrades) while running Kingroot are few and largely due to poor radio and/or observational hygiene during the rooting process. Cycling wifi off after KingRoot has downloaded its payload is an effective strategy. One can also monitor FireOS download progress and kill wifi if close to completion; a reboot will then kill the partial download. Avoiding fast network connections can slow the pace of OTA downloads giving KingRoot time to do its thing. Plus several other mitigations, most of which have been discussed at length in this thread.
[Fire Android Development] crazyates:
I understand all of that, and I did exactly that last time I rooted my second Fire (turned on wifi real quick, started KR, turned it off again). Because of the conversation about a Fire communicating with Amazon even if it's not registered, I'm wondering about the possibility of Factory Resetting, and then rooting without touching wifi even once.
[Fire Android Development] DB126:
At present KingRoot is the only tool available; WiFi is required in the APK build regardless of whether the device has been 'factory reset' (which addresses a different issue). There is a (tethered) desktop varient of KingRoot that does not require an active data connection on the target device. Issue for some is the desktop UI has not been translated to English or the language of choice. Pretty easy to figure out the major functions and corresponding buttons.
[Fire Android Development] vip451:
Kindle Fire HDX 8.9 3rd Generation

Please advice me how to ROOT a Amazon Fire 3th gen 8.9":):):):):)

*************************************************************************
[Fire Android Development] jhedfors:
Please do not quote the OP - completely unnecessary, and a pain to scroll through.

Also - wrong forum.

Use the forum for your device. You can start here:

https://xdaforums.com/kindle-fire-hdx/general/index-kindle-fire-hdx-7-8-9-t3206703
[Fire Android Development] vip451:
Very sorry. Thanks
[Fire Android Development] TechDad378:
The whole thoery of root may work if the device is not already updated. Yes wifi is need for KingRoot but a workaround can be achieved.

Keeping the same concept stated before, verifying the OS version is not already @ 5.3.2.1, shut wifi off on the tablet and connect tablet to pc. Once connected to PC run the PC version of KingRoot.

This way KingRoot is still used yet the tablet will not proceed with updates. Seems PC version of KingRoot produces more success. Just an idea!

TD378
[Fire Android Development] saajjata13:
Have attempted to use RJ Supertool many times, no success. I'm going to list my steps and if someone could tell me what I'm doing incorrectly, please reply.

First, yes it is OS 5.3.1

Second, I have verified ADB and Fastboot are working correctly.

a) Start Supertool

b) Select #6 - Root your Amazon Fire 5th GEN

c) select #3 - Root Fire OS 5.1.2 or 5.3.1

d) Install Kingroot

e) Open Kingroot - message "Network Error-Unable to get root strategy from cloud"

f) close and open Kingroot 4 times

g) power off

h) Open Kingroot - receive same error

i) close and open Kingroot 1 more time, clears error

j) Kingroot home screen (Android Symbol) - message "root access not available"

k) Press "get now"

l) Error message at bottom of screen "loading root failed"

m) pressed multiple times, error will not clear

I would appreciate any help
[Fire Android Development] DB126:
WiFi must be on the first time Kingroot runs; can be disabled after device reboots.
[Fire Android Development] saajjata13:
If the WiFi is on, won't an update start and download 5.3.2.1 making the tablet un-rootable?
[Fire Android Development] sd_shadow:
yes, but rooting should be done long before the update is downloaded
[Fire Android Development] cwhiatt:
The other thing also is that while it could download the update, I don't think it will install unless you press to install it.
[Fire Android Development] q4q9x:
Does WiFi have to be on before installing the Google Play Store? I installed the store without any connection, and enabled the WiFi connection after rebooting, but when I try to sign in the store app claims, "Couldn't sign in. There was a problem communicating with Google servers. Try again later."

[EDIT: This is on a device runing Fire OS 5.3.2.1. I did not root; did not think it was necessary to do so before installing the Play Store from the SuperTool.]
[Fire Android Development] DB126:
- WiFi must be enabled for Play Store to connect to your Google account and display app catalog

- don't know of the Play Store build included in the SuperTool works w/5.3.2.1 and/or on unrooted devices

- this one does (still needs WiFi): https://xdaforums.com/amazon-fire/general/how-to-install-google-play-store-fire-t3486603
[Fire Android Development] fayraz:
I have tried rooting my device using KingRoot and this is the 4th attempt now and now it just says Verify Root Status and been like that for about 10 mins now?

Shall I give it a reboot? - Done reboot and ran KingRoot again and still stuck on Verify Root Status.
[Fire Android Development] BeeWall:
See my reply in the Fire Nexus thread.
[Fire Android Development] saajjata13:
After connecting the WiFi and turning off anti-virus, root worked.

Thanks for everyone's help.

TA
[Fire Android Development] Canon7:
Hello,

I have a Fire 7 Tablet 5. Generation with FireOS 5.3.2.1.

Now I want to install a Android Version, but I dont know, is that possible?

I can not look through it anymore.

Can someone please tell exactly how I must proceed there and which files I need?

A step by step guide would be wonderful.

Thank you very much.

Greetings....
[Fire Android Development] Pond-life:
The ones the supertool disables? yeah if the system can't see those files it can't run them.
[Fire Android Development] FrankieChen:
I've not had any success with option 5 " Boot device to TWRP Recovery". It starts off:

< waiting for device >

downloading 'boot.img'....

OKAY [ 0.267s]

booting....

OKAY [ 0.060s]

finished. total time: 0.347s]

--------

[*] TWRP Recovery is booting please wait....

Press any key to continue...

and then nothing happens after I press a key.

I think the problem might be on the tablet reboot, the device is failing to be recognised. I noticed that when I connect the Fire to the computer initially, I get a device icon in the right hand bottom taskbar. Once the tablet reboots using rootjuny's script (and this happens also when I test the drivers in option 1, and also (I think) when I try option 7 to root), the device is no longer recognised. I've tried 4 different USB ports and it's the same on all of them.

Any thoughts?
[Fire Android Development] mattzildjian:
Without Root? Can you walk me through that?

How about blocking the update server on my router? If somebody knows how to do this I would be very grateful for help on this!

I really need to disable OTA without rooting.

Thanks!

Would this guide work for blocking OTA on my network?

http://www.aftvnews.com/how-to-block-amazon-fire-tv-update-to-ensure-rooting/