Help Please!! - 7" Kindle Fire HD Q&A, Help & Troubleshooting

Hello and Thank you for viewing my post!
I am New to Android Devices and the "Rooting" Process. I am a regular Apple user and use a Jailbroken iPhone and Use a Mac as well but have Windows Mirroring Capabilities on my Mac.
I just bought the Kindle Fire HD 8 (6th Generation) (2016) and it came with os 5.1.1 installed but once i connected to wifi it automatically updated me to 5.3.1.1.
I do not like the OS it includes as there are too many annoyances present (Ads, Unwanted OEM Applications, Etc.) and would like to Root my device and Run a "Real" Android OS and in other words, convert my Kindle Fire HD 8 into a Android Tablet as many do but i am unable to root because i am on 5.3.1.1.
If someone could please help walk me through the steps i need to take to root and all the tools ill need to do so, as well as ways to avoid bricking the device in the process.
Thank you in advance!
-Elijah

ElijahJ777 said:
Hello and Thank you for viewing my post!
I am New to Android Devices and the "Rooting" Process. I am a regular Apple user and use a Jailbroken iPhone and Use a Mac as well but have Windows Mirroring Capabilities on my Mac.
I just bought the Kindle Fire HD 8 (6th Generation) (2016) and it came with os 5.1.1 installed but once i connected to wifi it automatically updated me to 5.3.1.1.
I do not like the OS it includes as there are too many annoyances present (Ads, Unwanted OEM Applications, Etc.) and would like to Root my device and Run a "Real" Android OS and in other words, convert my Kindle Fire HD 8 into a Android Tablet as many do but i am unable to root because i am on 5.3.1.1.
If someone could please help walk me through the steps i need to take to root and all the tools ill need to do so, as well as ways to avoid bricking the device in the process.
Thank you in advance!
-Elijah
Click to expand...
Click to collapse
You can flash an older stock version with fastboot. You may need a fastboot cable to do it though.
Sent from my SCH-I535 using Tapatalk

Droidriven said:
You can flash an older stock version with fastboot. You may need a fastboot cable to do it though.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Ive heard rollingback from 5.3.1.1. will brick the Tablet due to the Bootloader(s), Correct?

ElijahJ777 said:
Ive heard rollingback from 5.3.1.1. will brick the Tablet due to the Bootloader(s), Correct?
Click to expand...
Click to collapse
Downgrading bootloader on some devices can brick them, it depends on the software though, not the device. Some devices with locked bootloader that can't be downgraded can sometimes extract the bootloader from the newer locked firmware and replace it in the older firmware, this allows the older firmware to be flashed without downgrading the bootloader because it has been modified so that it has the same bootloader. Not all locked devices can do this though, and even the ones that can still can't flash anything custom because of the bootloader, it does allow for downgrading to use things that won't work in the newer firmware. Whether or not that can be done on this or that device is hit or miss though, some can and some can't, it just requires research and trial and error.
Sent from my SCH-I535 using Tapatalk

Droidriven said:
Downgrading bootloader on some devices can brick them, it depends on the software though, not the device. Some devices with locked bootloader that can't be downgraded can sometimes extract the bootloader from the newer locked firmware and replace it in the older firmware, this allows the older firmware to be flashed without downgrading the bootloader because it has been modified so that it has the same bootloader. Not all locked devices can do this though, and even the ones that can still can't flash anything custom because of the bootloader, it does allow for downgrading to use things that won't work in the newer firmware. Whether or not that can be done on this or that device is hit or miss though, some can and some can't, it just requires research and trail and error.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
My Kindle Fire HD 8 (2016) allows me to unlock the Boot loader (OEM Unlock) from the settings menu, Im no sure if this is a good thing? (Easy way to downgrade boot loader alongside OS?) or not but not exactly sure. Would you recommend any tactics with this in mind or to just wait for kingroot or someone to crack 5.3.1.1. and create a Root?
Thank you!

ElijahJ777 said:
My Kindle Fire HD 8 (2016) allows me to unlock the Boot loader (OEM Unlock) from the settings menu, Im no sure if this is a good thing? (Easy way to downgrade boot loader alongside OS?) or not but not exactly sure. Would you recommend any tactics with this in mind or to just wait for kingroot or someone to crack 5.3.1.1. and create a Root?
Thank you!
Click to expand...
Click to collapse
I would wait for root
I DO NOT GIVE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Droidriven said:
I would wait for root
I DO NOT GIVE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Alright, Appreciate the help!
Have a good day!
-Elijah

Related

blu advance 5.0 hd compatible?

Hey so do you think the blu advance 5.0 hd will be compatible with the work being done on the R1 hd? I would really like to jump on this hype train with my similar but slightly less powerful phone.
I am hoping that I will be able to install a custom rom like R1 users. I also want to root my phone to disable google services in the meantime.
xda123455 said:
Hey so do you think the blu advance 5.0 hd will be compatible with the work being done on the R1 hd? I would really like to jump on this hype train with my similar but slightly less powerful phone.
I am hoping that I will be able to install a custom rom like R1 users. I also want to root my phone to disable google services in the meantime.
Click to expand...
Click to collapse
That phone is based on the 6580 SoC, the R1 uses a 6735. There is a site that lists some roms for blu products that may help, I don't know how reliable they are, I have never used them, but if you want to check it out...
http://www.blu-dev.com
kal250 said:
That phone is based on the 6580 SoC, the R1 uses a 6735. There is a site that lists some roms for blu products that may help, I don't know how reliable they are, I have never used them, but if you want to check it out...
http://www.blu-dev.com
Click to expand...
Click to collapse
Thanks I checked out the site and it seems like there is no blue advance 5.0 roms and no forum activity =/
xda123455 said:
Thanks I checked out the site and it seems like there is no blue advance 5.0 roms and no forum activity =/
Click to expand...
Click to collapse
If your wanting to root it, I'm hearing Kingroot is working, never used it though, so I can't say if it works or if it's safe??
kal250 said:
If your wanting to root it, I'm hearing Kingroot is working, never used it though, so I can't say if it works or if it's safe??
Click to expand...
Click to collapse
I've tried Kingroot, Kingo Root and Frama root. All with no luck.
devanttrio said:
I've tried Kingroot, Kingo Root and Frama root. All with no luck.
Click to expand...
Click to collapse
Did you use the desktop versions? Those have higher success rates. I tried rooting an HTC that way and it worked flawlessly even when the apk didn't.
Autolounge said:
Did you use the desktop versions? Those have higher success rates. I tried rooting an HTC that way and it worked flawlessly even when the apk didn't.
Click to expand...
Click to collapse
I did.
I also tried the apps, of the ones that have apps.
devanttrio said:
I did.
I also tried the apps, of the ones that have apps.
Click to expand...
Click to collapse
You're going to have to do it manually.
no go on kingo
I'm in the same boat. I've got 20 of these BLU Advance 5.0 HD devices and I need to root them to gain access to the VirtualSensor app to emulate a gyroscope. I've tried Kingo and Mobogenie (barf-boo-hisssss). I'm wondering if kingo isn't working on these since they have Marshmallow. I read somewhere they originally shipped with Lollipop.
Did you get anywhere Devanttrio??
trc117 said:
I'm in the same boat. I've got 20 of these BLU Advance 5.0 HD devices and I need to root them to gain access to the VirtualSensor app to emulate a gyroscope. I've tried Kingo and Mobogenie (barf-boo-hisssss). I'm wondering if kingo isn't working on these since they have Marshmallow. I read somewhere they originally shipped with Lollipop.
Did you get anywhere Devanttrio??
Click to expand...
Click to collapse
consider yourself blessed my friend, i'd like to root mine just to get marshmallow.... i have lollipop and checked for updates and says i'm up to date, i can only install 1 app at a time because there is no room on the internal storage, i have to move every app to sd card and then clean cache for each and every app i want.. never recommending blu to anyone
trc117 said:
I'm in the same boat. I've got 20 of these BLU Advance 5.0 HD devices and I need to root them to gain access to the VirtualSensor app to emulate a gyroscope. I've tried Kingo and Mobogenie (barf-boo-hisssss). I'm wondering if kingo isn't working on these since they have Marshmallow. I read somewhere they originally shipped with Lollipop.
Did you get anywhere Devanttrio??
Click to expand...
Click to collapse
I was able to root mine successfully the long way.... had to obtain a dump of the boot.img / recovery.img using software that I'm not sure of the policy of discussion on here at XDA - compile TWRP - unlock bootloader - fastboot boot the compiled recovery - flash SuperSU to get patched boot.img (kitchen was being dumb and systemless root didn't want to work) - Flash SuperSU in system mode - Convert SuperSU.apk to system app so it doesn't get removed every reboot. I can post my compiled TWRP when I'm back at my office or grab it from my repository that I'm trying to establish - https://bluroms.info . Sorry for the design mess / lack of much there at moment haven't had much free time lately in process of cleaning up the device kernel sources to build from source... its sort of ... messy in there...... can post on github if anyone wants in
zjr8 said:
I was able to root mine successfully the long way.... had to obtain a dump of the boot.img / recovery.img using software that I'm not sure of the policy of discussion on here at XDA - compile TWRP - unlock bootloader - fastboot boot the compiled recovery - flash SuperSU to get patched boot.img (kitchen was being dumb and systemless root didn't want to work) - Flash SuperSU in system mode - Convert SuperSU.apk to system app so it doesn't get removed every reboot. I can post my compiled TWRP when I'm back at my office or grab it from my repository that I'm trying to establish - https://bluroms.info . Sorry for the design mess / lack of much there at moment haven't had much free time lately in process of cleaning up the device kernel sources to build from source... its sort of ... messy in there...... can post on github if anyone wants in
Click to expand...
Click to collapse
I've been trying to root a Blu Advance 5.0 HD for a while now and stumbled on this post. I visited your site but am not sure what a 'Scatter File' is, or in what order I need to do things in order to get root.
If you could provide a little more detailed info that would be very much appreciated.
Thanks!
rAy
EDIT: Sorry, to clarify I tried all of the other PC and APK rooting solutions but was able to unlock the bootloader using ADB. I guess I'm just looking for the proper way to root and add TWRP. Thanks!
ray2jerry said:
I've been trying to root a Blu Advance 5.0 HD for a while now and stumbled on this post. I visited your site but am not sure what a 'Scatter File' is, or in what order I need to do things in order to get root.
If you could provide a little more detailed info that would be very much appreciated.
Thanks!
rAy
EDIT: Sorry, to clarify I tried all of the other PC and APK rooting solutions but was able to unlock the bootloader using ADB. I guess I'm just looking for the proper way to root and add TWRP. Thanks!
Click to expand...
Click to collapse
I found a option in developer settings that is "Enable OEM unlocking" and it makes it so you can unlock the bootloader from fastboot, if you do adb reboot-bootloader and then fastboot unlock it should undo the bootloader for you
zjr8 said:
I was able to root mine successfully the long way.... had to obtain a dump of the boot.img / recovery.img using software that I'm not sure of the policy of discussion on here at XDA - compile TWRP - unlock bootloader - fastboot boot the compiled recovery - flash SuperSU to get patched boot.img (kitchen was being dumb and systemless root didn't want to work) - Flash SuperSU in system mode - Convert SuperSU.apk to system app so it doesn't get removed every reboot. I can post my compiled TWRP when I'm back at my office or grab it from my repository that I'm trying to establish - Sorry for the design mess / lack of much there at moment haven't had much free time lately in process of cleaning up the device kernel sources to build from source... its sort of ... messy in there...... can post on github if anyone wants in
Click to expand...
Click to collapse
Like the others said, I would really appreciate if you could give an explanation or tutorial on how to use these files that you uploaded to root the phone. I'm willing to donate some money if required. I only know basic technical stuff haha.
CreativiTimothy said:
Like the others said, I would really appreciate if you could give an explanation or tutorial on how to use these files that you uploaded to root the phone. I'm willing to donate some money if required. I only know basic technical stuff haha.
Click to expand...
Click to collapse
I too am trying to root this device, and am unclear on a few of the steps here. I actually found your site with the recovery and boot images independently, really appreciated! I am at the point where I just need to patch the boot image, though I am not sure how to do this. If you could help me out with this step I might be able to put together some sort of list of steps to get through the whole process if you don't have the time.
Any help would be appreciated, thanks!

Need computer-less rooting method please!

Hey everyone,
So I bought the Blu R1 HD 16gb/2gb on amazon for 60 bucks, super stoked with its performance and look (although who can complain for the price of a family meal?).
My only problem is that I've been unable to root it. I know that I can easily root it with a computer, but for whatever reason my computer is unable to install any drivers for anything! Does anyone know of a rooting app that is compatible with the phone, or a way to root it with out a computer?
Please don't respond telling me how to install drivers, as I've tried everything; short of upgrading windows, that is.
P.S. Tried a bunch of apps already, none have supported rooting the R1 HD yet. I've tried kingo, king, towel, z4, and a bunch of others.
Thanks in advance!
Dude really? there is no other computer you could use to do it? your brother/sister father/mother some friend anything?... so sad
onlykhaz said:
Dude really? there is no other computer you could use to do it? your brother/sister father/mother some friend anything?... so sad
Click to expand...
Click to collapse
Yeah, they're all mac users, and android doesn't connect to it correctly.
ActuallyAFrog said:
Yeah, they're all mac users, and android doesn't connect to it correctly.
Click to expand...
Click to collapse
i dont (haven't anyway) use mac but @ColtonDRG , who does alot on this forum, uses MACos, so i do beleive there is support for mac
ActuallyAFrog said:
Hey everyone,
So I bought the Blu R1 HD 16gb/2gb on amazon for 60 bucks, super stoked with its performance and look (although who can complain for the price of a family meal?).
My only problem is that I've been unable to root it. I know that I can easily root it with a computer, but for whatever reason my computer is unable to install any drivers for anything! Does anyone know of a rooting app that is compatible with the phone, or a way to root it with out a computer?
Please don't respond telling me how to install drivers, as I've tried everything; short of upgrading windows, that is.
P.S. Tried a bunch of apps already, none have supported rooting the R1 HD yet. I've tried kingo, king, towel, z4, and a bunch of others.
Thanks in advance!
Click to expand...
Click to collapse
You're doing it wrong. We don't use ****ty rooting apps to root, we do it the RIGHT way. You have to install TWRP and flash SuperSU. You can do this the original way using SPFT, or the (more recommended) way of converting to OEM non-Prime, unlocking the bootloader, and using fastboot to flash TWRP.
ActuallyAFrog said:
Yeah, they're all mac users, and android doesn't connect to it correctly.
Click to expand...
Click to collapse
No. No. You could not be more wrong. Android connects to macOS MORE correctly than it connects to Windows. It doesn't even need any drivers! At Google, they don't use Windows, they use macOS and Linux. That said, we don't have any SPFT for Mac, unfortunately, but that's MediaTek's fault, and there's no reason you couldn't use a Linux live USB to do it.
mrmazak said:
i dont (haven't anyway) use mac but @ColtonDRG , who does alot on this forum, uses MACos, so i do beleive there is support for mac
Click to expand...
Click to collapse
I use macOS sometimes, yes, but there is no SPFT for it. I use Linux mostly.
ColtonDRG said:
No. No. You could not be more wrong. Android connects to macOS MORE correctly than it connects to Windows. It doesn't even need any drivers! .
Click to expand...
Click to collapse
Well @ColtonDRG I wasn't really saying that it won't work, I was saying they don't like me fiddling with their computers, cause as a kid I messed up some of their stuff, and they really haven't gotten over it yet.
But say I could use one, those things would be all to root it? I would just get the necessary programs, convert OEM to non-prime, unlock the bootloader (assuming mine is locked), flash TWRP, and then Super SU? I'd be done with it in an hour or two?
ActuallyAFrog said:
Well @ColtonDRG I wasn't really saying that it won't work, I was saying they don't like me fiddling with their computers, cause as a kid I messed up some of their stuff, and they really haven't gotten over it yet.
But say I could use one, those things would be all to root it? I would just get the necessary programs, convert OEM to non-prime, unlock the bootloader (assuming mine is locked), flash TWRP, and then Super SU? I'd be done with it in an hour or two?
Click to expand...
Click to collapse
You might need to convert your phone to the OEM non-Prime version first, but yes. There is no version of SPFT for macOS, so you'll need to use Windows or Linux for that, but the rest can be done on any OS. The whole process only takes me about 10 minutes, but if you don't know what you're doing, it would be reasonable to assume that you could do it in about a half an hour.
EDIT: Also my comment was in direct response to you saying:
"Yeah, they're all mac users, and android doesn't connect to it correctly."
Which implies that Macs cannot manipulate Android devices, which is simply not true.
ColtonDRG said:
You might need to convert your phone to the OEM non-Prime version first, but yes. There is no version of SPFT for macOS, so you'll need to use Windows or Linux for that, but the rest can be done on any OS. The whole process only takes me about 10 minutes, but if you don't know what you're doing, it would be reasonable to assume that you could do it in about a half an hour.
Click to expand...
Click to collapse
So I'll be good using only Mac as long as I don't need to switch my OEM?
ActuallyAFrog said:
So I'll be good using only Mac as long as I don't need to switch my OEM?
Click to expand...
Click to collapse
No. The Prime version of the phone requires SPFT to root, so you will need it either way. You can use SPFT to covert to the OEM version and then root using fastboot, or you can use SPFT to root the Prime version. I personally highly recommend converting.
Niki Kidman said:
Considering you had already cost "big money" to buy the root software. Maybe it's better for you to make good use of it... Try to change a computer...
Click to expand...
Click to collapse
Try Linux, I just got phone yesterday, rooted, unlocked bootloader, removed amazon stuff and compiled kernel.
Sent from my R1 HD using Tapatalk
vampirefo said:
Try Linux, I just got phone yesterday, rooted, unlocked bootloader, removed amazon stuff and compiled kernel.
Sent from my R1 HD using Tapatalk
Click to expand...
Click to collapse
It's been a long time since I rooted any phone or played around with adb or my linux mint (14). Would it be possible for you to tell me which guide you may have used for linux. I am using a windows 10 computer and cannot follow noob friendly guide for the life of me. My computer won't recognize the phone at all and I have disabled driver verification. Any help would be awesome.
Thanks
sid0101 said:
It's been a long time since I rooted any phone or played around with adb or my linux mint (14). Would it be possible for you to tell me which guide you may have used for linux. I am using a windows 10 computer and cannot follow noob friendly guide for the life of me. My computer won't recognize the phone at all and I have disabled driver verification. Any help would be awesome.
Thanks
Click to expand...
Click to collapse
I explained how I rooted in below post.
http://forum.xda-developers.com/showthread.php?p=68477232
If you can't follow it, then you need to stick with Windows method.
Sent from my R1 HD using Tapatalk

5.3.2.1 - Complete "Can" and "Can't" list?

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

Any root/slim ROM method for Fire 7 (7th generation 2017)?

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.

fire os 5.6.2.0 root

hello all!!
i am new to the forums, but i have been looking around for a while to figure out how to root and rom my Amazon Fire 7 (5th generation; KFFOWI). i havent used it in a while and i just loaded it up and now it has an update to Fire OS 5.6.2.0. is there any root for this device? and if so, has anyone found a way to custom recovery the device or unlock the bootloader? if there is no way, i am quite interested in the method used on LG's devices on if that would work to get a custom recovery on here. we all know about how most of LG's devices has a locked bootloader and the only way to get the custom recovery on specific LG devices was with a Bumped version of TWRP. if there is any way to test and work on it for the Fire 5th generation the same way it has been done on an LG G3, it might work out in the long run for this device. yes, root may have to be achieved still. but if someone can work on a ROM dump and try to find a loophole or a backdoor the hard way, we might be able to achieve root. i personally haven't learned android SDK let alone android kitchen, but i have a lot of experience in rooting and romming devices. my device is basically useless to me as i have a macbook and another android mobile device (LG Stylo 4 *still trying to find root for that device as well*), so if anybody tries these methods and can at least bring this device back to speed, we might be able to get more development for this device and probably can get Nougat or even Oreo on this device. you'll never know unless we try to put forth the effort to getting this device resurrected and rid of this FireOS plague!
Thanks!
MajorFoulest
See here.

Categories

Resources