Related
Hi All,
Not a Dev as such but have rooted and installed SlimLP on my Fire tablets.
Having trouble using some apps as they are detecting the root. Have looked into Xposed package and using the root cloak to solve these issues but can't find any info on whether my setup is supported or not and don't want to brick my devices.
What I have:
Device - Amazon Fire 5th Gen
Model - KFFOWI
Android Version - 5.1.1
Slim Version - slim-5.1.1.build.2.2-csolanol-20151210
All I want is to end up with both my devices running custom ROMs with the root cloaked, doesn't have to be SlimLP if it's not possible.
Any help would be appreciated on this. As I say I am not a Dev so won't understand technical jargon.
Thanks in Advance
Did your device have FireOS 5.0.1 on it before you flashed a custom rom? Aka can you load twrp recovery via fastboot.
If you have a 5.0.1 device then you should almost always be able to recovery from any issues.
I had 5.1.1 OS installed prior to flashing. I used RootJunkys supertool to root and used Flashfire to flash the rom.
Does this make a difference?
Chrisbonner89 said:
I had 5.1.1 OS installed prior to flashing. I used RootJunkys supertool to root and used Flashfire to flash the rom.
Does this make a difference?
Click to expand...
Click to collapse
Does make a difference but is irrelevant to your concern. You can not effectively cloak root on any android rom. Yes, some techniques can obscure root from poorly coded apps but most are more intelligent and can easily detect if the device has 'elevated' permissions - including if usb debug is enabled. Savvy users can defeat some checks but it's a cat and mouse game at best.
Hi Guys,
So I recently got my hands on a kindle fire 5th gen (2015), running the latest OS 5.3.2.1.
I have read many things and many different opinions on what can and cannot be done, and ideally I am looking for a conclusive list i there is one available.
So I was searching and Root Junky has provided custom ROM's and a few other files, however, this is my understanding
CANNOT: root
CAN: downgrade to an older OS, which may allow root, but its likely it will brick it
CANNOT: unlock bootloader for custom ROM installation
CANNOT: install a custom flash zip file from the inbuilt android recovery interface
I dont know if they just happened to crash down and lockdown the fire recently, but pages such as this below, indicate it can (or at least could) be done.
https://www.thepolyglotdeveloper.com/2016/05/install-better-custom-rom-amazon-kindle-fire/
and this, indicates its probably too late since I connected it and downloaded 5.3.2.1.
http://android.stackexchange.com/qu...ot-and-install-cm-12-1-on-5th-gen-kindle-fire
So, is there a conclusive list, aside "using your tablet as out of the box" as to what you can and cannot do to modify the fire 5th gen?
I got mine right before bootloader lock running slim LP haven't updated since used flash fire on 5.1.1 to the best of my knowledge
Sent from my Robin using Tapatalk
FF51, so very lucky, I am really envious actually.
The fire, when not suffering pixel outages, and without a dire need for GPS, makes an excellent hardware base, and from my reading, installng a custom rom would really unlock the xperience of the tablet and give it a much more competitive edge.
Out of curiosity, did you jump straight into the slim build, or did you try others?
Also I have read you cannot install CM13+ due to the limitations of the bootloader, but can you install CM12 instead (I think thats based on lollipop isnt it?) and can you do that with the stock bootloader / recovery module?
jeebob said:
Also I have read you cannot install CM13+ due to the limitations of the bootloader, but can you install CM12 instead (I think thats based on lollipop isnt it?) and can you do that with the stock bootloader / recovery module?
Click to expand...
Click to collapse
- can not root (at present) or downgrade (ever) FireOS 5.3.2.1
- bootloader remains locked; no custom kernels or recoveries (eg: TWRP)
- rooted devices can only run Lollipop based ROMs due to kernel restrictions
- custom ROMs must be installed with FlashFire
- see forum index for further info: http://forum.xda-developers.com/amazon-fire/general/index-amazon-fire-2015-t3210485
Hi every one!
Tell me please, can I use FlashFire and install CM12.1 into my Kindle 7 with 5.3.2.1 without root device?
So I can`t downgrade 5.3.2.1?
My device isn`t rooted and locked. my only achievement was the google play store
Davey126 said:
- can not root (at present) or downgrade (ever) FireOS 5.3.2.1
- bootloader remains locked; no custom kernels or recoveries (eg: TWRP)
- rooted devices can only run Lollipop based ROMs due to kernel restrictions
- custom ROMs must be installed with FlashFire
- see forum index for further info: http://forum.xda-developers.com/amazon-fire/general/index-amazon-fire-2015-t3210485
Click to expand...
Click to collapse
Thanks Davey, a concise list which is great, now I just have to hope we can get the bootloader and root sorted on 5.3.2.1!
bojkoio said:
Hi every one!
Tell me please, can I use FlashFire and install CM12.1 into my Kindle 7 with 5.3.2.1 without root device?
Click to expand...
Click to collapse
It looks like the answer is not at this time, as from my reading, 5.3.2.1 cannot be rooted directly with current methods, only 5.3.1 onwards.
freaky2xd said:
So I can`t downgrade 5.3.2.1?
My device isn`t rooted and locked. my only achievement was the google play store
Click to expand...
Click to collapse
thats all I have managed to achieve so far, next I want to remove the adverts!
bojkoio said:
Hi every one!
Tell me please, can I use FlashFire and install CM12.1 into my Kindle 7 with 5.3.2.1 without root device?
Click to expand...
Click to collapse
Nope - no custom ROMs without root.
---------- Post added at 12:50 PM ---------- Previous post was at 12:49 PM ----------
freaky2xd said:
So I can`t downgrade 5.3.2.1?
My device isn`t rooted and locked. my only achievement was the google play store
Click to expand...
Click to collapse
No - nor likely ever. Best hope is for a root solution.
Well Sh*t
I got all 3 of my daughters a kindle fire 7" 5th gen for Christmas. I ran thru the updates and was going to install the google framework and all that goes with it to be able to install works of ahhh painting app. However, I have hit a roadblock since it seems even tho I have enabled unknown sources and rebooted each device (all running 5.3.2.1) I can download apks but when I attempt to install them, it's like the install button just doesn't register touch response no matter what direction you rotate the device. I'm not new to this, I got kindles because of how easy it was to customize a previous one my 7 year old had, and besides, $30 each was a pretty good deal. So maybe it's a software glitch in the new update, maybe it's that I just don't care enough to dig into it but that's where it stands here.
Edit: A simple reboot after allowing unknown sources fixed the problem and I completed the installation of Google play store
luck_shawn said:
I got all 3 of my daughters a kindle fire 7" 5th gen for Christmas. I ran thru the updates and was going to install the google framework and all that goes with it to be able to install works of ahhh painting app. However, I have hit a roadblock since it seems even tho I have enabled unknown sources and rebooted each device (all running 5.3.2.1) I can download apks but when I attempt to install them, it's like the install button just doesn't register touch response no matter what direction you rotate the device. I'm not new to this, I got kindles because of how easy it was to customize a previous one my 7 year old had, and besides, $30 each was a pretty good deal. So maybe it's a software glitch in the new update, maybe it's that I just don't care enough to dig into it but that's where it stands here.
Click to expand...
Click to collapse
On mine I downloaded the four apks needed installed them (in proper order) using apk permission remover and it worked for me. There's a thread in the fourms I folllwed
I just used the kindle supertool to install the google framework and APK's. once click and leave it to its own devices - a tool by superjunky I think?
Anyway, as for the rotation, I havent noticed any particular problems with it, but I havent done a lot of work with testing it, I will try take a look a bit later!
i have the same problem. I managed to install Google Play but trying to side load the Popcorntime apk fails with the next and install button not registering touch input, cancel button works fine.
oilyrag said:
i have the same problem. I managed to install Google Play but trying to side load the Popcorntime apk fails with the next and install button not registering touch input, cancel button works fine.
Click to expand...
Click to collapse
Have you enabled FireOS setting that allows installs from unknown sources and then rebooted device?
Davey126 said:
Have you enabled FireOS setting that allows installs from unknown sources and then rebooted device?
Click to expand...
Click to collapse
Thought I had rebooted device, done it again, now works. Many thanks
Sent from my SM-N9005 using Tapatalk
I bought two 7" fires on the Black Friday sale to use as home automation panels in the house (with SmartThings). I installed the Play Store but found the SmartThings app was still not compatible . But really I was waiting for the new ActionTiles (web client) to come out. The one Fire upgraded to 5.3.2.1 and I haven't opened the other yet. The Play Store will no longer launch on the 5.3.2.1 tablet either. My original thought was to probably flash a new rom that is not as restrictive but doesn't look like that will happen now. Have a few additional questions for the "can" and "can't" list with 5.3.2.1 please:
1) Can the lock screen be disabled/removed?
2) Can the device be woken up by screen touch?
3) Does the non-root Play Store hack still work? (maybe I just need to redo something after the upgrade?)
4) Are there any browsers I can have auto load the ActionTiles dashboard (web page) and always keep it up and full screen?
Thanks a lot!
Coods said:
1) Can the lock screen be disabled/removed?
2) Can the device be woken up by screen touch?
3) Does the non-root Play Store hack still work? (maybe I just need to redo something after the upgrade?)
4) Are there any browsers I can have auto load the ActionTiles dashboard (web page) and always keep it up and full screen?
Thanks a lot!
Click to expand...
Click to collapse
1) not completely that I have found, unless you keep the screen alive 24/7.
2) power button only however root could allow this but 5.3.2.1 doesn't support (or should I say have a method for) root at this time.
3) yes it does, I have uploaded it to about 6 different kindle recently all running 5.3.2.1
4) again root would help, however you can use automateit free or pro from plastered. It's very powerful and you should be able to achieve a lot with it. If it doesn't support it though, tasker is another powerful tool which might be worth exploring
Sent from my D6603 using Tapatalk
jeebob said:
2) power button only however root could allow this but 5.3.2.1 doesn't support (or should I say have a method for) root at this time.
Click to expand...
Click to collapse
No hardware support for this capability regardless of root (re: touch to wake).
Davey126 said:
No hardware support for this capability regardless of root (re: touch to wake).
Click to expand...
Click to collapse
Thanks for confirming davey!
Sent from my D6603 using Tapatalk
Thanks for the info guys, appreciate it! This helps me understand the direction I want to take with these as alarm panels
Hi! I have a 5th gen Fire tablet running 5.1.1, rooted with the Supertool, lock screen ads turned off.
I'd like to get Alexa. I understand that Alexa is available in firmware 5.3.2.
I see here that 5.3.2 can't be rooted but can be downgraded to 5.3.1, which can be rooted. So I think 5.3.2 is the version that I want, rather than 5.3.2.1, to preserve the option to root in the future.
What is the process to upgrade my tablet to 5.3.2? Based on experience with other devices, I would expect that I'd need to do some combination of unrooting, factory reset, clear data and cache, etc.
But I'm reading the instructions for restoring stock firmware here, it looks like all I need to do is an adb sideload in stock recovery. Is it really that simple? No need to do anything else?
I'm assuming the result of that will be a fresh install of 5.3.2 with Alexa, and then I'll want to use the Supertool to install the Play Store.
Can anyone just provide a quick confirmation that I have this right? Thanks for any help!
5.3.2 isnt rootable, OTA updates will probably be an issue unless you can block auto updates.
discman017 said:
Hi! I have a 5th gen Fire tablet running 5.1.1, rooted with the Supertool, lock screen ads turned off.
I'd like to get Alexa. I understand that Alexa is available in firmware 5.3.2.
:
I'm assuming the result of that will be a fresh install of 5.3.2 with Alexa, and then I'll want to use the Supertool to install the Play Store.
Can anyone just provide a quick confirmation that I have this right? Thanks for any help!
Click to expand...
Click to collapse
krsmit0 said:
5.3.2 isnt rootable, OTA updates will probably be an issue unless you can block auto updates.
Click to expand...
Click to collapse
Yep. You'll probably want to hold off if retaining root option (and ability to flash a custom ROM) is more important than Alexia. Might also consider grabbing a refurb Fire 7 from Amazon (<$30 USD) and running Alexia on that pup. Best of both worlds...albeit with additional cost and hassle of dealing with 2 devices.
Thanks for the heads up about OTA updates. I figured I could just ignore OTA updates and stay on 5.3.2. But is that not the case? Will Amazon automatically update 5.3.2 to 5.3.2.1 without my approval?
Sorry for the very basic questions. I've been happily running 5.1.1 (rooted, OTA updates disabled by Supertool), so I hadn't considered the problem of a forced update.
Or is there another way to get Alexa (custom ROM, for instance)?
Thanks again!
discman017 said:
Will Amazon automatically update 5.3.2 to 5.3.2.1 without my approval?
Click to expand...
Click to collapse
Yes, it will automatically update as soon as it can. And unfortunately, updates can't be disabled without root, so 5.3.1 is the newest you can safely obtain without locking into the terrible 5.3.2.1 situation we're in now.
I just bought a new Fire 7 (7th generation) tablet. But all I found so far were for root is for Fire 7 (5th generation). Any new 7th generation root method and custom rom? Or is it compatible between 5th and latest 7th generation? Thanks for the help guys.
nyknight77 said:
I just bought a new Fire 7 (7th generation) tablet. But all I found so far were for root is for Fire 7 (5th generation). Any new 7th generation root method and custom rom? Or is it compatible between 5th and latest 7th generation? Thanks for the help guys.
Click to expand...
Click to collapse
If the OS Version is 5.3.2.1, or 5.3.3.0, then no...not root yet.
nyknight77 said:
I just bought a new Fire 7 (7th generation) tablet. But all I found so far were for root is for Fire 7 (5th generation). Any new 7th generation root method and custom rom? Or is it compatible between 5th and latest 7th generation? Thanks for the help guys.
Click to expand...
Click to collapse
The stock version is 5.3.3.0 so, no root.
DragonFire1024 said:
If the OS Version is 5.3.2.1, or 5.3.3.0, then no...not root yet.
Click to expand...
Click to collapse
Thanks for your reply. I haven't received it yet to check the OS version but I'm hearing it will be OS Version 5.4
nyknight77 said:
Thanks for your reply. I haven't received it yet to check the OS version but I'm hearing it will be OS Version 5.4
Click to expand...
Click to collapse
Mine came with 5.3.3.0.
nyknight77 said:
I just bought a new Fire 7 (7th generation) tablet. But all I found so far were for root is for Fire 7 (5th generation). Any new 7th generation root method and custom rom? Or is it compatible between 5th and latest 7th generation? Thanks for the help guys.
Click to expand...
Click to collapse
In addition to other responses no assessment of custom rom compatibility on 7th gen devices can be conducted without root. IMO it is highly unlikely an exploitable vulnerability will be found in recent builds of FireOS or the device bootloader anytime soon given recent efforts to shore up all Android based ROMs.
I just got 4 Fire 7 gen 7s in the mail today; two with a red case, two with a yellow case.
The odd thing is that the yellow colored ones came with 5.4.0.0, while the red ones came with 5.3.3.0. The red ones must not be as popular and I was sent slightly older stock I assume.
Even worse is that the 5.4.0.0 yellow ones won't even let you bypass/skip the initial wifi setup and amazon account login. You MUST be connected to the internet and login with an Amazon account to setup the tablet.
AlwaysLucky said:
I just got 4 Fire 7 gen 7s in the mail today; two with a red case, two with a yellow case.
The odd thing is that the yellow colored ones came with 5.4.0.0, while the red ones came with 5.3.3.0. The red ones must not be as popular and I was sent slightly older stock I assume.
Even worse is that the 5.4.0.0 yellow ones won't even let you bypass/skip the initial wifi setup and amazon account login. You MUST be connected to the internet and login with an Amazon account to setup the tablet.
Click to expand...
Click to collapse
I would highly advise you not allow those to update, flash 5.3.2.1 (the oldest version you can safely revert to if you haven't yet hit 5.4.0.1), and then use the tool linked below to remove all of the Amazon bloatware and install the launcher of your choice. This will get you as close as possible to a stock Android experience.
https://forum.xda-developers.com/amazon-fire/general/amazon-fire-utility-tool-bloat-removal-t3641151
Technocian said:
This will get you as close as possible to a stock Android experience.
https://forum.xda-developers.com/amazon-fire/general/amazon-fire-utility-tool-bloat-removal-t3641151
Click to expand...
Click to collapse
I appreciate the link to the updated tool. The added features are nice indeed and I will try it out.
Technocian said:
I would highly advise you not allow those to update, flash 5.3.2.1 (the oldest version you can safely revert to if you haven't yet hit 5.4.0.1), and then use the tool linked below to remove all of the Amazon bloatware and install the launcher of your choice.
Click to expand...
Click to collapse
Unfortunately, these are the 7th generation Fire 7 tablets (not 5th gen 'ford'). AFAIK, the earliest initial firmware shipped with these gen 7s is the 5.3.3.0. Even worse, is that I've tried to adb sideload every firmware version since 5.3.2.1 (even tried 5.3.3.0), but I got the same error every time at 47% progress:
"whole-file signature verification failed"
"aborted"
On that note, do you or anyone know if there is a way to adb sideload older firmware versions to a gen7? I was using the Windows 10 built-in USB drivers and that seems to be working but I have read elsewhere that the newer Fire generations require the Amazon USB ADB drivers to communicate properly with the computer. So my next step is to try using the Amazon USB driver and try again.
AlwaysLucky said:
On that note, do you or anyone know if there is a way to adb sideload older firmware versions to a gen7? I was using the Windows 10 built-in USB drivers and that seems to be working but I have read elsewhere that the newer Fire generations require the Amazon USB ADB drivers to communicate properly with the computer. So my next step is to try using the Amazon USB driver and try again.
Click to expand...
Click to collapse
Bootloader is locked and anti rollback measures are in place. If you are on 5.4.0.0, the lowest you can downgrade to currently is 5.3.2.1. Trying to go lower will result in a hard bricked tablet. Look at it this way...if you want to experiment, knock yourself out. If you do brick it beyond repair, you have 30 days from date of purchase (or delivery? Not sure how that works) to return it for another. Just get a color you haven't gotten and who knows what those are on, if the event you described regarding colors is true.
EDIT: I am in no way encouraging you to brick your device or do any harm to it.
DragonFire1024 said:
Bootloader is locked and anti rollback measures are in place. If you are on 5.4.0.0, the lowest you can downgrade to currently is 5.3.2.1. Trying to go lower will result in a hard bricked tablet. Look at it this way...if you want to experiment, knock yourself out. If you do brick it beyond repair, you have 30 days from date of purchase (or delivery? Not sure how that works) to return it for another. Just get a color you haven't gotten and who knows what those are on, if the event you described regarding colors is true.
EDIT: I am in no way encouraging you to brick your device or do any harm to it.
Click to expand...
Click to collapse
haha, nice edit.
Well I read your previous post stating that downgrading to 5.3.2.1 was possible, but I get the same above error trying to sideload any version firmware file to it. I am assuming this is because I am on the gen 7 (aka austin), not the gen 5 (aka ford). I have done some extensive searching on xda but it seems not many people actually have a gen 7, so I think I'm pioneering this a little bit.
With that, I can say that the Amazon USB driver for ADB made no change. Any ideas?
AlwaysLucky said:
haha, nice edit.
Well I read your previous post stating that downgrading to 5.3.2.1 was possible, but I get the same above error trying to sideload any version firmware file to it. I am assuming this is because I am on the gen 7 (aka austin), not the gen 5 (aka ford). I have done some extensive searching on xda but it seems not many people actually have a gen 7, so I think I'm pioneering this a little bit.
With that, I can say that the Amazon USB driver for ADB made no change. Any ideas?
Click to expand...
Click to collapse
Debugging mode is on I presume (ADB Enabled)? Have you installed any Google Services (Play Store etc)? Go here and please and follow the installation steps for Total Commander and tell me the info for the 1st and 2nd lines on your device.
DragonFire1024 said:
Debugging mode is on I presume (ADB Enabled)?
Click to expand...
Click to collapse
I truly appreciate your time into this, however I do not think I am explaining myself well. The ultimate purpose of these 4 gen7 (austin) tablets is for all 4 to be rooted and use a custom ROM. On one of the 7gens (5.3.3.0), I have successfully removed bloat from the stock rom and installed the play store (using your guide and others :good: ). It's much better than stock, but still not applicable for my purposes.
This leaves me with one option; downgrade the firmware to a rootable version (ideally 5.3.1). To do this, I enter the recovery menu by holding the volume down button and power button when powering on the tablet. While in the recovery menu (yellow on black text), I attempt to sideload firmware (any version, with md5s matching) and get the same error every time on all 4 tablets at exactly 47% completion:
"E: failed to verify whole-file signature"
"E: signature verification failed"
"installation aborted."
This doesn't brick any of the tablets and they reboot just fine out of recovery into the stock firmware. It must have something to do with the 7th gen tablets. While connected via USB to the tablets while in sideload mode in recovery, the hardware ID for the USB connection shows up as "USB\VID_1949&PID_0001". After googling that a little bit, it kept coming back to HD8 drivers! Soooo maybe I need the HD8 version of the firmwares so I can downgrade? Hmmmmm.....
AlwaysLucky said:
I truly appreciate your time into this, however I do not think I am explaining myself well. The ultimate purpose of these 4 gen7 (austin) tablets is for all 4 to be rooted and use a custom ROM. On one of the 7gens (5.3.3.0), I have successfully removed bloat from the stock rom and installed the play store (using your guide and others :good: ). It's much better than stock, but still not applicable for my purposes.
This leaves me with one option; downgrade the firmware to a rootable version (ideally 5.3.1). To do this, I enter the recovery menu by holding the volume down button and power button when powering on the tablet. While in the recovery menu (yellow on black text), I attempt to sideload firmware (any version, with md5s matching) and get the same error every time on all 4 tablets at exactly 47% completion:
"Whole-file verification failed"
"Aborting installation"
This doesn't brick any of the tablets and they reboot just fine out of recovery into the stock firmware. It must have something to do with the 7th gen tablets. While connected via USB to the tablets while in sideload mode in recovery, the hardware ID for the USB connection shows up as "USB\VID_1949&PID_0001". After googling that a little bit, it kept coming back to HD8 drivers! Soooo maybe I need the HD8 version of the firmwares so I can downgrade? Hmmmmm.....
Click to expand...
Click to collapse
I have no idea. Regardless, you CANNOT downgrade to anything lower than FireOS 5.3.2.1 (which cannot be rooted). If your tablets are on 5.3.3.0 or 5.4.0.0, the lowest you can go is 5.3.2.1. If you are having ADB trouble, I would download Android Studio full version and make sure the SDK is up to date and start a new ADB folder from there. If your Kernel is of a later date than June 2017, you might not be able to rollback at all.
AlwaysLucky said:
I truly appreciate your time into this, however I do not think I am explaining myself well. The ultimate purpose of these 4 gen7 (austin) tablets is for all 4 to be rooted and use a custom ROM. On one of the 7gens (5.3.3.0), I have successfully removed bloat from the stock rom and installed the play store (using your guide and others :good: ). It's much better than stock, but still not applicable for my purposes.
This leaves me with one option; downgrade the firmware to a rootable version (ideally 5.3.1). To do this, I enter the recovery menu by holding the volume down button and power button when powering on the tablet. While in the recovery menu (yellow on black text), I attempt to sideload firmware (any version, with md5s matching) and get the same error every time on all 4 tablets at exactly 47% completion:
"Whole-file verification failed"
"Aborting installation"
This doesn't brick any of the tablets and they reboot just fine out of recovery into the stock firmware. It must have something to do with the 7th gen tablets. While connected via USB to the tablets while in sideload mode in recovery, the hardware ID for the USB connection shows up as "USB\VID_1949&PID_0001". After googling that a little bit, it kept coming back to HD8 drivers! Soooo maybe I need the HD8 version of the firmwares so I can downgrade? Hmmmmm.....
Click to expand...
Click to collapse
Have seen this before (crap out at 47%). Usually pops up when attempting to sideload an inappropriate '.bin' file. Likely the 5.3.1 build you are using is for 5th gen devices. Different mainboard/SOC than 7th gen. Be happy Amazon's firmware detects this and doesn't allow the device to brick.
DragonFire1024 said:
Regardless, you CANNOT downgrade to anything lower than FireOS 5.3.2.1 (which cannot be rooted).
Click to expand...
Click to collapse
Ohhh I understand, so even if downgrading to 5.3.2.1 actually worked, I can't even root on that firmware anyways. Ugh, well I will be patient. Thanks for the info and your time.
If your goal is to have these all ultimately rooted, I would return them and get your money back (if you still can). It's not likely a root method will be found.
This isn't a hot new device like the Pixel 2 where hoards of talent will be flocking to try and make it more usable. I got mine second hand for 25 bucks, this device from a monetary standpoint just isn't worth anyone's time.
The only realistic way I see root happening is if they release firmware based on a new version of Android or Kingroot find an Android exploit that would be compatible with our device.
AlwaysLucky said:
Ohhh I understand, so even if downgrading to 5.3.2.1 actually worked, I can't even root on that firmware anyways. Ugh, well I will be patient. Thanks for the info and your time.
Click to expand...
Click to collapse
Correct...but keep in mind, so far it seems anyone on 5.4.0.1 won't be be able to debloat anymore. So downgrading to 5.3.2.1 is a better option than being so close to the latest version.
I'm not looking to root (i am, but i understand its not possible right now)... So is there any possibility to install apps other than the amazon app store?
thygreyt said:
I'm not looking to root (i am, but i understand its not possible right now)... So is there any possibility to install apps other than the amazon app store?
Click to expand...
Click to collapse
Please see this thread.
I have had my Amazon fire 5th gen for a couple months now and I want to know if there is a way to root my tablet without a computer, anybody know?
ChompDroid126 said:
I have had my Amazon fire 5th gen for a couple months now and I want to know if there is a way to root my tablet without a computer, anybody know?
Click to expand...
Click to collapse
Neither without, nor with a computer. The last rootable firmware was 5.3.1, long ago.
Using Tapatalk on a Ford
I am in the same boat as the OP what can be done to downgrade the version and get this device rooted?
Nrocket3 said:
I am in the same boat as the OP what can be done to downgrade the version and get this device rooted?
Click to expand...
Click to collapse
You can't as a quick of the dozen+ threads on the same topic would reveal:
- no root on any build of FireOS above 5.3.1
- 5.6 can not be rolled back to a rootable build
Nrocket3 said:
I am in the same boat as the OP what can be done to downgrade the version and get this device rooted?
Click to expand...
Click to collapse
@Nrocket3 Downgrading will brick your device unfortunately
Still no fix?
my son reset the kindle fire i had already had it rooted and factory reset was done...... i forgot how to root it and so i went back online looking to day how to do it again and now it states that u cannot root 5.6.+ and i checked the kindle i have and its running 5.6+ now :0( just wanna know if there is any update to this yet or a way to root
FatGuy870 said:
my son reset the kindle fire i had already had it rooted and factory reset was done...... i forgot how to root it and so i went back online looking to day how to do it again and now it states that u cannot root 5.6.+ and i checked the kindle i have and its running 5.6+ now :0( just wanna know if there is any update to this yet or a way to root
Click to expand...
Click to collapse
Unfortunately, no root once FireOS has progressed beyond 5.3.2.0. Status quo for many months and is unlikely to change going forward. You can still install the Play Store and ask Amazon to remove lock screen ads. That's about it.
Davey126 said:
Unfortunately, no root once FireOS has progressed beyond 5.3.2.0. Status quo for many months and is unlikely to change going forward. You can still install the Play Store and ask Amazon to remove lock screen ads. That's about it.
Click to expand...
Click to collapse
You can root from FireOS 5.4.1.0 all the way to the current 5.6.0.1, on the Fire HD 10 only. At the moment no other current (2017) tablets can be rooted. I plan to reload FireOS on my HD 10 sometime soon to re-root and see if I can't get some logs of it and see what's going on. The closest to root any other Amazon tablet has, beyond 5.3.1.0, is disabling system apps on 5.4.0.0 and earlier versions.
DragonFire1024 said:
You can root from FireOS 5.4.1.0 all the way to the current 5.6.0.1, on the Fire HD 10 only. At the moment no other current (2017) tablets can be rooted. I plan to reload FireOS on my HD 10 sometime soon to re-root and see if I can't get some logs of it and see what's going on. The closest to root any other Amazon tablet has, beyond 5.3.1.0, is disabling system apps on 5.4.0.0 and earlier versions.
Click to expand...
Click to collapse
Seen this movie before. HD 10 uses a different architecture (64-bit) utilizing different binaries with different vulnerabilities. It is unlikely that any exploits from the HD 10 can be leveraged to FireOS builds for the Fire 7 and HD 8.
Davey126 said:
Seen this movie before. HD 10 uses a different architecture (64-bit) utilizing different binaries with different vulnerabilities. It is unlikely that any exploits from the HD 10 can be leveraged to FireOS builds for the Fire 7 and HD 8.
Click to expand...
Click to collapse
Agreed. Though to see what's going on, could be beneficial. Though I do giggle a little at the thought of Amazon "patching" the disabling of system apps, only to have their most expensive tablet rooted. I have been wondering if whatever they patched caused this.
I don't really know how kernels are patched. Example: when a kernel is patched to stop potential exploits, how is the data written? Like is it in rotation? As new patches are uploaded, does it push off the older data?