yashsingh1/xdaforums huggingface dataset:
[Fire General] BeeWall:
Not everyone on XDA is busy with this tablet. The brightest minds are probably using their skills at a job, or working on more popular devices, like flagships. No offense intended to people in this forum. Finding and figuring out how to use an exploit takes a long time, and can be quite difficult. And devs have real lives too. That's why we use KingRoot, or at least try to. The people who make it spend a lot of time trying to find exploits, and we have to hope that one works for this device. And unlocking the bootloader is even harder. A lot harder than making an app, or even making a ROM. Again, not to belittle or offend the people who do those things. That's still hard work, and very useful. We just have to try hard, hope a lot, and be happy with what we have. The Fire isn't a paperweight, even on stock unrooted (unless you brick it). With Google Play and LauncherHijack, it comes close to being a normal tablet, especially if you disable and hide as much bloat as you can. I hope we can unlock it too, but we must be patient. It took 3 years to get a universal unlock for (was it the hdx?), and some other devices haven't gotten any unlock after an even longer period of time. Some devices can't even be rooted on any version. And some devices have even worse stock roms than the Fire. At least we have what we do.
[Fire General] MisterX00:
Mine was a simple question requiring a simple answer. To make this acceptable tablet, you have a guide for the installation of google services and improved Launcher of the existing one? Thank you so much for the information and for the full answer. I'm sure the XDA guys are very busy and mine was not a criticism of their work. Since I do not mean I can not know the timing to develop Roma, app, or unlocking procedures, root etc. Anyway thank you all for the excellent work they do every day. Through the site I installed a ROM in a samsung Note 2. Thanks again, look if possible an answer regarding the installation of google services and Launcher alternative tablet. Good night
[Fire General] BeeWall:
I'm sorry, I misunderstood your question. Thank you for clarifying.

Nova Launcher:

https://xdaforums.com/amazon-fire/orig-development/app-root-launcherhijack-custom-launcher-t3409531

Any other launcher:

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

Google Play:

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

Your original question had been about unlocking it, or at least seemed to be. A better way to phrase your actual question would be "How do I get Google Play and custom launchers?" In the future, I would recommend making questions as clear as possible. A look through the forum is also useful, then ask questions that aren't answered or clear. All of these tutorials are in there.

I'm sorry if my original answer may have sounded rude or unnecessary. As I said, the phrasing of your question made it sound like it was about bootloader unlock. I'm personally not a dev, but your question still seemed very impatient and ignorant. I understand that was not the intent​, however, I was in an irritable mood already. You calling the tablet a "paperweight" also sounded ungrateful to devs that work on this tablet, as it seemed to disregard everything they have done. From now on, I would suggest not calling a working device a paperweight. Even if Google Play and launchers weren't available, the tablet would be usable. I'm sorry again if my response seemed uncalled-for, and I hope that you understand why I posted it.

I hope the tutorials help. Good night to you as well.
[Fire General] MisterX00:
He was not addressed to you, indeed you've been more than kind to devote some time to respond, but the important thing is to clarify. I asked you at the beginning of the release, but called paperweights a tablet is just a figure of speech, and does not mean to denigrate the work of XDA developers. For paperweight I mean it is quite cumbersome to use than a normal Android and all the publicity is really annoying. Anyway I use it anyway without problems, and it is clear that if you can improve so much the better. Thanks for the tutorial, I will get to work immediately. Good day.
[Fire General] Robdroid14:
5.3.2.1 waiting on root too

I actually bought 2 of the 7" 5th gen just to go android then i came across this thread, hoping we can have root or roll back on 5.3.2.1, fingers crossed
[Fire General] BeeWall:
Until then, you can use Google Play and LauncherHijack to get some things. You can also disable and pm hide a lot of bloat safely. Make sure to disable OTAs, otherwise when root is found for 5.3.2.1 you'll probably have already updated to fix whatever exploit is found.
[Fire General] chwiejak:
Hi,

How to disable OTA?
[Fire General] BeeWall:
Use the SuperTool. It has an option to disable OTAs.
[Fire General] chwiejak:
It working without root?
[Fire General] DB126:
Nope - need root to effectively block future updates.
[Fire General] chwiejak:
This is thread about fireos 5.3.2.1 which can not be rooted till now:(
[Fire General] DB126:
Until a root vulnerability/exploit is found for FireOS 5.3.2.1 OTA updates can not be effectively blocked.
[Fire General] MisterX00:
I do not find Supertool for the 5.3.2.1 version, what I get up to 5.3.1, and in any case requires the root that we can not do on this release!

THX
[Fire General] megatruck:
Lifehack=Solved

First post sorry if it is not up to par...

I feel this is slightly unethical but justifiable and possibly won't work for most people but here is what i did:

Searched and searched to come to the conclusion there was no way to root 5.3.2.1 so I got on Amazon Chat and talked to a tech support agent long story short, 3 levels of agent escalation and 6 hours later they would not be able to do anything for me to downgrade or replace because the "new firmware froze my Fire" as I was far beyond the warranty period so after working on this root for 2 days and having to deal with the chat people (nice but have no authority) I was a little pissed it's my Fire and I want it the way I want it no restrictions so I emailed Jeff Bezos and one of his Email Monitors replied within 6 hours saying sorry about the issues and that as a one time exception he would send me a new one. I just received it and it had 5.1.3 on it so i'm in business.

Like I said not the most above board thing to do and it probably won't work for most people but XDA has been very valuable to me so I thought it would be rude to not share my success story.
[Fire General] BeeWall:
I thought it worked without root. Would pm hide work, or does it restart itself?
[Fire General] krsmit0:
I have attempted to block mine at the router. If I do an update check. It's says update check failed.
[Fire General] BeeWall:
Glad you figured it out. Did you use a server list, or figure it out on your own? If the former, could you link it to make it easier for others? And if the latter, could you list them?
[Fire General] krsmit0:
It's a guide for fire TV. I have a pihole server and blocked the domains through there.

http://www.aftvnews.com/how-to-block-software-updates-on-the-amazon-fire-tv-or-fire-tv-stick/

domains are listed under method 3
[Fire General] DB126:
- pm hide is easily reversible; I also heard rumor (but have not confirmed) Amazon restricted the pm hide command in later builds of FireOS v5

- domain blocking is effective until Amazon rotates servers or brings new domains online; that spoiled many an OTA block for 3rd gen HDXs owners (among others); recognize the potential risks if you go this path.
[Fire General] BeeWall:
Is there a way to record server checks, so that when a new domain is up you can find it when the fire checks it? Also, if it can't check for updates, how does it know to check a new server?
[Fire General] krsmit0:
I'm on 5.3.2.1 so no risks for me. Just an attempt to keep it from updating in case something comes along. And the hide command seemed to work for me and lockscreen ads. Has anyone attempted to use something like tasker to redisable lockscreen ads automatically?

---------- Post added at 10:51 PM ---------- Previous post was at 10:49 PM ----------

Pihole can list all DNS queries, but figuring out which one to disable is trial and error. It does a lot of calling home. Disable the wrong one and other desired features might not work. Tried some already and had to reverse it.
[Fire General] BeeWall:
I'm wondering the same thing. I'm guessing it's not that simple, or it would have been suggested by now.
[Fire General] krsmit0:
i have 2 ideas i would like to try to disable ads on the kindle itself but i need the ads to renable before i can test them. I figure someone smarter then me as already attempt this.
[Fire General] BeeWall:
pm unhide com.amazon.kindle.kso
reboot

Use either ADB shell or a terminal emulator.
[Fire General] krsmit0:
nothing worked, i didnt expect much.
[Fire General] BeeWall:
The command I gave was to unblock ads. To block them, replace the word "unhide" with "hide" in the command.
[Fire General] DB126:
Think response from [MENTION=4614628]krsmit0[/MENTION] indirectly answered question. Unless all communication is severed new parameters can be loaded at Amazon's descretion.
[Fire General] krsmit0:
my kindle fire hasnt done an update check since 2-27 with this guide. manual update checks error out.

http://www.aftvnews.com/how-to-block-software-updates-on-the-amazon-fire-tv-or-fire-tv-stick/

EDIT: block these domains. I used pihole.

amzdigital-a.akamaihd.net

amzdigitaldownloads.edgesuite.net

softwareupdates.amazon.com

updates.amazon.com

and now im testing blocking this domain with pihole to disable lockscreen ads.

d2ifcvdeb7ylq0.cloudfront.net

black list it with pihole then run "pm clear com.amazon.kindle.kso" and "reboot" in adb. ads dont instantly download so it seems to take time to figure out if it works long term.

both of these are only solutions for your home network.

i have done some looking into mobiwol. seems to block apps from accessing the internet on a non rooted device. block the special offers app and the ota app. i dont think it restarts correctly on reboot but tasker will launch it on reboot if it doesnt load.

if someone could test and report back, it would be nice to know what works and what doesnt

EDIT: blocking cloudfront domain did not stop the ad from updating.
[Fire General] Jrhotrod:
You know, I use Android kitchen. I'm wondering: would a modded ROM be possible if I converted 5.3.2.1 firmware to zip, rooted it with kitchen, and sideloaded it? Don't really want to brick trying, but if there is a possibility of it working I will take a risk.
[Fire General] BeeWall:
It needs to be signed with Amazon keys, so no.
[Fire General] Jrhotrod:
Hmm. That's disappointing; too bad we don't have a way to sign :p
[Fire General] Jrhotrod:
I've seen this suggested before, but shrugged it off as implausible. However, as we are desperate for a solution, would sideloading SuperSU from stock recovery work? After all, sideloading is synonymous to flashing.
[Fire General] crazyates:
If it were that simple, it would have been done before. The stock recovery won't load any firmware/zip unless it's signed by Amazon. Replacing the stock recovery won't work because it's a locked bootloader. If we could unlock the bootloader, a lot of these problems could be worked through, but we're stuck for now. The reality is, even with a locked bootloader, these have a heck of a lot more support than a lot of other devices.

If you're on the newest firmware, you're SOL... kinda. You can still sideload the Google Play store, replace the stock launcher (kinda), and be able to use it more like an android tablet, and less like an ereader.
[Fire General] Jrhotrod:
Yes, I figured as much. I already knew that the bootloader was locked, it was just kind of an idea to throw out there. Thanks for responding so quickly
[Fire General] Mr McBoatface:
I had modded a Fire OS 5.3.2.1 installation image and changed the system.new.dat file to the system.new.dat file of Fire OS 5.3.1. I modified the target.blocklist meta-inf with the sha-1 values of the changed system.new.dat file and created a mock upgrade build by modding the build.prop value and build date.

If placed on the internal storage of the tablet it's detected as a upgrade and if you try to install the "upgrade" it reboots and proceeds to about 40% of the progress bar before a triangle and exclamation mark come on screen. It reboots and doesn't install.

I was hoping that by downgrading the OS (sytem.new.dat) while keeping the 5.3.2.1 preloader and boot files a way to root could be found. I've pretty much given up on this avenue now. But maybe it's a route that could be looked at again but I doubt it would work.
[Fire General] Ayden7777:
Hey do the same thing but use 5.3.2.0 instead of 5.3.1 and tell me if it works

---------- Post added at 05:42 AM ---------- Previous post was at 05:35 AM ----------

Do the same thing but just use the 5.3.2.0 instead of 5.3.1 this time and that might work ?
[Fire General] Mr McBoatface:
Well fire OS 5.3.2.0 isnt rootable either do no point in trying that.

The problem might be that within the system.new.dat which is a compressed OS there is another prop.build file and a recovery creation script. From what i remember the recovery creation script checks for the sha-1 of the installed boot loader and preloaded files.

Because they don't match it could be causing it to fail or the miss matched prop.build file causing the same thing.

I believe if it was possible to edit the system.new.dat file to change these to expected values it would work IF you could create an amazon compatible signed binary check file.....

But if we could do that we would loading a custom OS not amazon.

Feel free to try yourself ☺
[Fire General] DB126:
Given what we know about the 5.3.x.x branch there is no indication this would be more successful and every indication it would not.
[Fire General] Ayden7777:
mhmm I see ya, but everything is worth a try

---------- Post added at 08:52 PM ---------- Previous post was at 08:50 PM ----------

Oh yes I was thinking cuz you can downgrade 5.3.2.0

---------- Post added at 08:54 PM ---------- Previous post was at 08:52 PM ----------

How did you get these files? system.new.dat

Edit nvm used 7zip to open it

GOOD LUCK EVERYONE!
[Fire General] Ayden7777:
Did your device brick after the triangle?
[Fire General] Mr McBoatface:
No it just rebooted. The boot loader and preloaded files didn't change to older incompatible ones that would cause a brick. It's the downgrade of those that causes problems.
[Fire General] Ayden7777:
Yes I tried that and moved the meta inf folder and mine failed at about 48 and I did not get a triangle I got an error msg and it said verification failed installation aborted

---------- Post added at 12:46 AM ---------- Previous post was at 12:40 AM ----------

If you are desperate enough edit the bootloader images to make it boot the 5.3.1 if possible

Also the signing by Amazon has to me something in the files, so if someone geeky enough found out it could open a wide range of doors to downgrading!
[Fire General] Mr McBoatface:
Sounds like you tried to ADB sideload it ? I placed it on the tablet storage and attempted the upgrade via the OS.

Same result either way
[Fire General] Ayden7777:
Welp maybe you could take the boot files in the 5.3.1 and delete them and then try to "update it"

maybe that'll work!
[Fire General] Mr McBoatface:
Lol not desperate at at .... it's just a little hobby, playing around with a spare cracked screen tablet. I've got my tablets rooted and on nexus rom. Bootloader files can't be edited as the anti-rollback measures check the sha-1 values of the files.

Don't think this is an avenue worth going down any further as it's very unlikely to work.

Waiting for root from kingroot or a new fire OS with a root vulnerability seems the only option.
[Fire General] Ayden7777:
Ok but saying I meant the boot files in the "5.3.1.bin" file would it still "update"
[Fire General] Mr McBoatface:
Unlikely as I said before from what i recall from my attempts the system.new.dat has a recovery creation script that check sha-1 values of the installed boot files. I suspect if they are not as expected it won't install . It's also got a build.prop file which i suspect if older than the installed system won't install. I think its impossible to edit these files in the system.new.dat without affecting a binary check the upgrade process runs as part of amazon signing the OS.

No way around it that I can see. I spent a bit of time looking at it and like I said just can't see it working
[Fire General] Ayden7777:
Yes Ok I see ugggh

Everyone is still stuck on 5.3.2.1 tho

darn.
[Fire General] DragonFire1024:
Question...Did all of the 5th generations come with 5.3.2.0 out of the box? If so, and you don't activate WiFi, and don't register the device can you then rollback to the previous version then root? Without going through the whole 14 pages...I got a 7in 5th generation tablet, but it wasn't new. I did a factory reset on it and registered it, before I discovered all this stuff.
[Fire General] ms372591:
They could come with many different firmware versions. If you have 5.3.2.0 you can rollback and root, but if it updated to 5.3.2.1 it cannot be rooted as of yet.
[Fire General] resinis:
****in dammit... bought this tablet for $40, was going to clean off the amazon crap and use it as my new car computer.

i turned it on, set it on the table, and forgot about it for awhile. it went through a ton of updates without me telling it to do anything. now its on 5.3.2.1

i already hate this thing
[Fire General] chwiejak:
Yes, this is sad true:(

Which applications you using with "car computer"?
[Fire General] DB126:
Return it for a full refund if within 30 days of purchase. Otherwise you're stuck with an Amazon appliance. Root for FireOS 5.3.2.1 and above appears to be a long shot.
[Fire General] resinis:
Nova launcher. It's the best. It allows me to customize how ever i want, so i just use widgets for xiia radio and pandora, and set icons on the home screens where i want them. it works wonderfully.

and i could care less about the operating system. but, of course, this ****ing kindle fire FORCES you to use their launcher, and you can't use nova. F THAT.

I think I'm returning it. It's really not any faster than my old ass hisense pro 7 anyway
[Fire General] DB126:
- you should be able to install Nova following guidance in this post even on an unrooted device

- the above workaround is not perfect as you will note from thread comments; also no widget support unless rooted (plus some additional steps)

- a 5th gen Fire 7 will run circles around a HiSense Pro 7 (which I own) when freed from FireOS; unfortunately, you can't install a custom ROM without root

- as root for 5.3.2.1/5.3.3.0 is unlikely in the immediate future you should return your device while that option still exists

- consider a pre-owned HDX 7 which can be rooted and unlocked; there are a half dozen custom ROMs for that device ranging from KitKat to Nougat
[Fire General] theNine1:
I would like to add that, I got rid of the lock-screen ads (I guess) permanently by blocking internet access to all the preinstalled bloatwares. This requires the following two steps:

1. Clear all existing screen lock ads by:

adb shell pm clear com.amazon.kindle.kso
adb shell reboot

2. Block Internet connection to all the bloatwares using Internet blocking tools like "NoRoot Firewall". Also, using this tool you can block all future OTA updates. Specially block the following apps:

Advertising ID: com.amazon.advertisingsettings
DeviceSoftwareOTA: com.amazon.device.software.ota
Forced OTA: com.amazon.kindle.otter.oobe.forced.ota
Special Offers: com.amazon.kindle.kso

I would recommend to only allow the apps you need and to block all other preinstall apps.
[Fire General] Ayden7777:
Sorry for my noobish act, but what app should I use to block these programs or whatever?.
[Fire General] theNine1:
"NoRoot Firewall" is a good app, using which you can block the bloated apps from accessing the internet.
[Fire General] resinis:
i just returned it. amazon is trying to be like apple. f that.

unaltered google is still the best. i know a lot of companies are trying to compete, but they simply fall short. what sucks is everyone stopped making 7" tablets... barns and noble is the only major release in 2016, but it only has 1GB ram. In fact, i think the only mainstream tablet that has 2GB ram at 7" is the 2013 nexus 7 tablet! I need 7" though, because thats the only size that will fit in my truck's dash.
[Fire General] DB126:
Strongly recommend considering a used HDX (3rd gen Fire) which can typically be found on auction sites for $50-75 USD, sometimes less. More powerful than a Nexus 7 with 2GB ram and a gorgeous screen. Bootloader can be easily unlocked allowing installation of a custom ROM; a half dozen quality choices are available. Downside is no SD card slot or OTG support. Everything must fit in internal storage which ranges from 16GB to 64GB (11-59GB usable). Bluetooth can be a bit dicey with some ROMs; no problem with WiFi. I'm penning this on a 7" HDX running CM 12.1 which is my daily driver. Also have copies running Nexus 6 (Marshmallow) and LineageOS 14.1 (Nougat). Food for thought.
[Fire General] resinis:
no sd card slot kills it. my sero 7 pro uses a 128GB drive right now to hold all my mp3's

I have also tried DLNA devices to access my music over wifi in my car, but its nowhere near as stable as built in sd slot.
[Fire General] DB126:
Ok - another option is to seek out a Fire 7 that has FireOS 5.3.1 or below which can be rooted an then replaced with a custom ROM. Likely find one on an auction site. Not trying to be an Amazon fanboy. If you can find a Nexus 7 or another Sero Pro go for it. Not much else competes in the 7-8" space unless you want to drop $200+. Good luck.
[Fire General] Ayden7777:
Well... I wonder if 5.3.3 can be downgraded to 5.1.1, Amazon might be hiding from us...
[Fire General] chwiejak:
I blocked those addresses but my device was just updated:-\

I suppose that 5.3.3.0 is even harder for root than 5.3.2.1..

:-\
[Fire General] DB126:
Guaranteed brick as we already know that 5.3.3->5.3.2 won't work and 5.3.x bootloader is different than 5.1.x bootloaders. This one requires no further speculation.
[Fire General] DB126:
Yes - I have warned against this technique in multiple previous posts. Seen it happen on other Amazon devices too (most notably 3rd gen HDX) where the outcome was a hard bricked $200+ USD paper weight. At least most 5th gen devices continue to function after an unwanted OTA. Count your blessings.
[Fire General] Ayden7777:
I bet that amazon has this version that can be downgraded and fixed rooted devices and stuff like that. I don't think Amazon just throws away bricked tablets that get sent to them! :mad:
[Fire General] chwiejak:
Which technique block updates in 100%?
[Fire General] DB126:
Root followed by renaming DeviceSoftwareOTA.apk. There are no 100% methods for unrooted devices aside from network isolation. Blocking IPs and domain names is effective until Amazon spins up a new provider. Inevitably happens.
[Fire General] DB126:
Likely not but suspect some percentage is simply written off (you might be surprised at what gets tossed in any high volume commodity​ business). They obviously have knowledge we lack along with tools/techniques for rewriting eprom. I don't think a team of busy-bees is downgrading and repackaging borked devices one at a time.
[Fire General] savvytechwinner:
I know! Lets ask them nicely!! But in all seriousness, they should let 3rd party devs downgrade their horrendous firmware, glad I don't have a firetab any more. Not like the new tablet is any better :( The screen is way to scratched up :(
[Fire General] DB126:
Well no (business 101) but there's little to be gained arguing the point.
[Fire General] chwiejak:
Hello,

Do you know that someone working on root fireos?

Unfortunatelly I have newest version:(
[Fire General] DragonFire1024:
Possibly. A user reports a possible major flaw in his tablet that allowed him to use Odin to flash SuperSu to root, and he has/had 5.3.3.0. I am Awaiting some assistance in that thread so I can attempt to try that method myself.