Related
Hey, I recently rooted my Kindle Fire HD and everything was working great, until I installed an Xposed tweak that caused my Kindle to start boot looping and then thereafter I went ahead and screwed it up even worse - by messing with various fastboot methods to get it working again. Yeah... I should have just left it as it was, I know...
I've read about how there are signature checks whenever the Kindle boots up which I'm assuming I don't have anymore. So, I'm curious if there is anyway to come back from this? From what I've read, if I had backed up the partitions, technically I should have been able to restore them - but unfortunately here we are.
I've also downloaded the latest update from Amazon 'update-kindle-11.3.1.0_user_310084920' and after converting it to a zip file, there is a 'boot.img' and a 'recovery.img' which I would assume would have the signatures already within them, but no system.img. Is there anyway for someone to create an exact backup of that file, or is that not possible right now without a second bootloader?
I'm honestly really unsure of what to do here, I've tried a myriad of different approaches and still it looks like this is a bad brick... However I do hope someone out there has a solution, I'd love to get this device working again.
Oh and what happens whenever I start it up, is that I just get the Amazon Kindle Fire Logo (Pure White), without any changes. It doesn't turn gold with the animation or anything.
Hyperiunn said:
Hey, I recently rooted my Kindle Fire HD and everything was working great, until I installed an Xposed tweak that caused my Kindle to start boot looping and then thereafter I went ahead and screwed it up even worse - by messing with various fastboot methods to get it working again. Yeah... I should have just left it as it was, I know...
I've read about how there are signature checks whenever the Kindle boots up which I'm assuming I don't have anymore. So, I'm curious if there is anyway to come back from this? From what I've read, if I had backed up the partitions, technically I should have been able to restore them - but unfortunately here we are.
I've also downloaded the latest update from Amazon 'update-kindle-11.3.1.0_user_310084920' and after converting it to a zip file, there is a 'boot.img' and a 'recovery.img' which I would assume would have the signatures already within them, but no system.img. Is there anyway for someone to create an exact backup of that file, or is that not possible right now without a second bootloader?
I'm honestly really unsure of what to do here, I've tried a myriad of different approaches and still it looks like this is a bad brick... However I do hope someone out there has a solution, I'd love to get this device working again.
Oh and what happens whenever I start it up, is that I just get the Amazon Kindle Fire Logo (Pure White), without any changes. It doesn't turn gold with the animation or anything.
Click to expand...
Click to collapse
The 2013 Kindle Fire HD is not setup for Xposed yet. There is no bootloader access yet therefore there is no way to recover yet. You have two options at this point. Wait until there is a bootloader exploit or contact Amazon for an exchange.
The only things available are root, remove OTA updates and remove lock screen ads. Even Google Play is only for window shopping at the moment.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
LinearEquation said:
The 2013 Kindle Fire HD is not setup for Xposed yet. There is no bootloader access yet therefore there is no way to recover yet. You have two options at this point. Wait until there is a bootloader exploit or contact Amazon for an exchange.
The only things available are root, remove OTA updates and remove lock screen ads. Even Google Play is only for window shopping at the moment.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
For anyone wondering, xposed actually works perfectly with a good number of modules, but don't install Xthemeengine, that'll cause the bootloop.
Fastboot
As long as you can boot into fastboot-mode nothing is lost. (if you can't -> buy a fastboot-cable. it is much cheaper than a new Kindle. They cost about 15$).
I used this useful tool. It just flashes the old system, boot and recovery on your Kindle. (all files are included in the downloadable zip file).
This tool was very useful for me and saved my Kindle very often (I am a real flashoholic...). Maybe there is something like this for the new 2013 KFHD too?
Gamingmayr said:
As long as you can boot into fastboot-mode nothing is lost. (if you can't -> buy a fastboot-cable. it is much cheaper than a new Kindle. They cost about 15$).
I used this useful tool. It just flashes the old system, boot and recovery on your Kindle. (all files are included in the downloadable zip file).
This tool was very useful for me and saved my Kindle very often (I am a real flashoholic...). Maybe there is something like this for the new 2013 KFHD too?
Click to expand...
Click to collapse
Nah nothing so far for the 2013 unfortunately. I don't think there's been much interest in this model as of yet.
Hyperiunn said:
Nah nothing so far for the 2013 unfortunately. I don't think there's been much interest in this model as of yet.
Click to expand...
Click to collapse
I've been interested. Unfortunately, my mother won't let me touch her new 2013 Fire HD. Still, if you can find someone who's rooted and not bricked, maybe they could backup their boot, system, and recovery .imgs for you and post them for you. And since they're already rooted, you would be too (someone correct me if I'm wrong). If I could get a temporary root or find a way to remove root later I would back them up for you.
The system restore tool for the 2012 Fire HD flashes the boot, recovery, and system partitions. Theoretically, the same tool would work, but only if you replaced the .img files with the ones for the 2013 Fire HD.
Gamingmayr said:
As long as you can boot into fastboot-mode nothing is lost. (if you can't -> buy a fastboot-cable. it is much cheaper than a new Kindle. They cost about 15$).
I used this useful tool. It just flashes the old system, boot and recovery on your Kindle. (all files are included in the downloadable zip file).
This tool was very useful for me and saved my Kindle very often (I am a real flashoholic...). Maybe there is something like this for the new 2013 KFHD too?
Click to expand...
Click to collapse
There is no confirmation that a fastboot cord even works with the 2013 model nor are the stock images available yet. The 2012 KFHD and the 2013 KFHD do not use the same images.
---------- Post added at 11:28 PM ---------- Previous post was at 11:26 PM ----------
Hyperiunn said:
For anyone wondering, xposed actually works perfectly with a good number of modules, but don't install Xthemeengine, that'll cause the bootloop.
Click to expand...
Click to collapse
It won't work on the 2013 Kindle fire HD yet though. Since that is the topic here I guess that narrows it down to this tablet not all the others don't it.
Fastboot cable works just fine with the one I have.
Ok, so I'm a noob when it comes to this stuff, but I have managed to root my Kindle Fire HD 7" and I installed the Google play store, so I was happy thus far. Yesterday I lost root and couldn't figure out why. Today I noticed that my Kindle had done an update from 7.4.6 to 7.4.8 and I'm wondering if this is why I lost root? If so, how can I fix this to get my Kindle back into root? Like I said, I'm a noob and don't want to screw up my Kindle messing around with stuff when I don't have a clue. Any advice would be of great help, thanks in advance.
Oh yeah, I should add this information: I get this pop up from Superuser, "There is no SU binary installed and Superuser can not install it. This is a problem"
Yea when it updates it clears the system partition where the su binary is stored, you need to reroot it. Never heard of a 7.4.8 update, but if it is a new one and you can reroot it then you can just downgrade it with kindle fire first aid by sticking it into fastboot with a simple "adb reboot bootloader", think kffa will do it for you though.
Sent from my Amazon Kindle Fire HD using Tapatalk
masterndentske
stunts513 said:
Yea when it updates it clears the system partition where the su binary is stored, you need to reroot it. Never heard of a 7.4.8 update, but if it is a new one and you can reroot it then you can just downgrade it with kindle fire first aid by sticking it into fastboot with a simple "adb reboot bootloader", think kffa will do it for you though.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
" Never heard of a 7.4.8 update, but if it is a new one and you can reroot it " Hmmmm, the way you worded that makes me feel like I might be stepping into uncharted territory if I try to root it again and I don't like the thought of that. I'll think about it and maybe give it a try tomorrow after I get some sleep and my head is clear. Thanks for the advice, I really appreciate it.
cautiousone said:
" Never heard of a 7.4.8 update, but if it is a new one and you can reroot it " Hmmmm, the way you worded that makes me feel like I might be stepping into uncharted territory if I try to root it again and I don't like the thought of that. I'll think about it and maybe give it a try tomorrow after I get some sleep and my head is clear. Thanks for the advice, I really appreciate it.
Click to expand...
Click to collapse
I had the same problem starting yesterday. My Kindle upgraded to 7.4.8 and any app requiring root stopped working, namely Google Play Store, SuperUser, ... I used KFFirstAide to re-root the Kindle and all is working so far.
blackeyeX2 said:
I had the same problem starting yesterday. My Kindle upgraded to 7.4.8 and any app requiring root stopped working, namely Google Play Store, SuperUser, ... I used KFFirstAide to re-root the Kindle and all is working so far.
Click to expand...
Click to collapse
:good: Awesome, thanks for passing that on to me, I'm going to give it a go and see what happens. I'll post a status update later today after I've had a chance to thoroughly test it.
:victory: Well I got it to root again and reinstalled google play with no issues to report, all went well. So is there a way to stop Amazon from updating my Kindle in the future? Now, the next task is to get a second boot loader on it, although I don't have a fastboot cable, so I'm kinda chicken, hahaha. But I'm feeling confident now, so maybe I'll give it a shot tonight. Wish me luck... A big thanks for the help, I guess I just needed some reassurance on re-rooting the thing and I'm happy.
Just make sure you downgrade the bootloader first, if you don't use the fireflash method then I recommend making sure to check the md5sum of the bootloader before downgrading it so you don't end up with a paperweight.
Sent from my Amazon Kindle Fire HD using Tapatalk
I'm having this issue also. Same update, same loss of SU + Play store.
I can't get my kindle to root like before though. It says it was successful but my fire becomes extremely laggy, no icons appear, where the navigation swipe is there are slightly darker vertical lines and the only way I've fixed it is by factory restore.
How are you rerooting???
I can't remember how I rooted in the first place, I only remember that I had massive issues getting GP store on and used this KFFA which is what I'm now using to reroot.
http://forum.xda-developers.com/showthread.php?t=2069329
Any suggestions would be massively appreciated
kindle fire hd 7.4.8
same thing happen to me so I tried getting adb to work witch it didn't that well, so I downloaded the update .bin file from amazon and edited it useing winRAR just added SuperSU to /system/app then changed a few things in kindle first aid then used a fastboot cable to upload the custom update so my kindle is running v7.4.9 witch I changed it to because it didn't work any other way. i'll make a video
dEADwEIRD said:
I'm having this issue also. Same update, same loss of SU + Play store.
I can't get my kindle to root like before though. It says it was successful but my fire becomes extremely laggy, no icons appear, where the navigation swipe is there are slightly darker vertical lines and the only way I've fixed it is by factory restore.
How are you rerooting???
I can't remember how I rooted in the first place, I only remember that I had massive issues getting GP store on and used this KFFA which is what I'm now using to reroot.
http://forum.xda-developers.com/showthread.php?t=2069329
Any suggestions would be massively appreciated
Click to expand...
Click to collapse
I just followed the same steps as I did the first time I rooted it, I used KFFA. But this time around some of the actions described didn't happen, like Superuser didn't ask for permission as it did the first go around and a few other little things, but I just took it slow and easy and it came out working fine. Also I used KFFA to install GP, it also skipped a few actions, but I just have it a little extra time to do its thing and it works perfectly. I saw a fix for the laggy screen and icons issue somewhere, I think it's in KFFA? I would have to double check that when I get home to be certain.
stunts513 said:
Just make sure you downgrade the bootloader first, if you don't use the fireflash method then I recommend making sure to check the md5sum of the bootloader before downgrading it so you don't end up with a paperweight.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Thanks for the heads up on that, I've held off on doing it until I have more time to research it. I like to feel somewhat comfortable going into it and not totally freaked out. Thanks again, you guys are great around here.
Sorted.
I rooted using The Bin4ry Method and using KFFA to bring all the other systems back on line.
is anyone having problems with ADB and fastboot on 7.4.8?
Because I tried rooting using KFFA that didn't work I kept getting errors so I tried using fastboot to flash the recovery using this code
Code:
fastboot flash recovery recovery.img
I get "device not found" or when it dose work i get "failed to flash" (something like that) but i have the adb drivers installed would there be different ones for 7.4.8? When I type
Code:
fastboot device
it finds the device it just dosn't work when I want to flash
and only half the adb commands work
You have to have it with a special parameter telling it what the kindles vendor id is so it should look like this...:
Code:
fastboot -i 0x1949 flash recovery recovery.IMG
Try that.
Sent from my Amazon Kindle Fire HD using Tapatalk
"... I used KFFirstAide to re-root the Kindle and all is working so far."
I tried using bin4ry's root, which is how I originally rooted my kindle, but it did not work.
I am pleased to say that KFFirstAide was able to restore root.
Thank you xda for pointing me in the right direction!
stunts513 said:
You have to have it with a special parameter telling it what the kindles vendor id is so it should look like this...:
Code:
fastboot -i 0x1949 flash recovery recovery.IMG
Try that.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Thank you!!! i got root access by flashing with twrp recovery witch you can get more info at
http://forum.xda-developers.com/showthread.php?t=2128848
on my other kindle i used Bin4ry root witch work but i had to turn off adb/usb debugging and turn it back on during the process because it wouldn't find the device if i didn't
you can download Bin4ry here
http://forum.xda-developers.com/showthread.php?t=1886460
gregcavaretta said:
on my other kindle i used Bin4ry root witch work but i had to turn off adb/usb debugging and turn it back on during the process because it wouldn't find the device if i didn't
Click to expand...
Click to collapse
Thank's, KFFA not recovered and Bin4ry work only after turn off adb / usb debugging
Ciao dal Max
gregcavaretta said:
Thank you!!! i got root access by flashing with twrp recovery witch i downloaded at
http://teamw.in/project/twrp2/79
on my other kindle i used Bin4ry root witch work but i had to turn off adb/usb debugging and turn it back on during the process because it wouldn't find the device if i didn't
you can download Bin4ry here
http://forum.xda-developers.com/showthread.php?t=1886460
Click to expand...
Click to collapse
wtf????? that was a twrp image for the kf1, that should have broken more than it fixed on a kfhd.
Holy ****!!! Your kindle works after flashing the recovery IMG that was for the kf1???
Sent from my Kindle Fire HD 7 running PAC-man
wire55 said:
Holy ****!!! Your kindle works after flashing the recovery IMG that was for the kf1???
Sent from my Kindle Fire HD 7 running PAC-man
Click to expand...
Click to collapse
stunts513 said:
wtf????? that was a twrp image for the kf1, that should have broken more than it fixed on a kfhd.
Click to expand...
Click to collapse
I posted the Wrong link i'm truly sorry if you messed up your kindle fire
Hi
I know the update just got pushed a couple of days back, but wanted to check if anyone had already identified how to root a Kindle Fire HD with 11.3.2?
I lost my root access after this update.
Thanks.
abhi.ko said:
Hi
I know the update just got pushed a couple of days back, but wanted to check if anyone had already identified how to root a Kindle Fire HD with 11.3.2?
I lost my root access after this update.
Thanks.
Click to expand...
Click to collapse
Use this: http://forum.xda-developers.com/showpost.php?p=50985251&postcount=347
Just worked fine for me couple of minutes ago.
Regards.
is there any exploit working which doesn't need a factory cable?
yomagin said:
is there any exploit working which doesn't need a factory cable?
Click to expand...
Click to collapse
i'm not an expert with the 2013 kindles, but you shouldn't need one if adb is enabled, you should be able to run "adb reboot bootloader", unless for some reason you have no adb access.
no there isnt as of yet. adb reboot fastboot does not function on this device so you need the fact cable to get it into that mode to run the exploit
O well that sucks least I know this now. Can't believe they disabled the easy way to get into it.
Sent from my Amazon Kindle Fire HD using Tapatalk
Hello
I've had the same issue. My kindle was rooted fine but then a recent update has caused it to become unrooted. Version is 11.3.2
Does anyone know if there is a way for me to root this again?
Much appreciated
Look up a few posts... The one by eLiTeFLO...
Sent from my Amazon Kindle Fire HD using Tapatalk
root 11.3.2
stunts513 said:
Look up a few posts... The one by eLiTeFLO...
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
So anybody know how to root the kindle fire 7" 2013 running 11.3.2 without factory cable? Otherwise is there a way to downgrade to 11.3.1?
11.3.2.3.2
Hi, rooting noob here-literally just starting!
Can't find anything on rooting my Kindle Fire HD 2nd Gen which is running the 11.3.2.3.2 version. It was installed today (so I'm not suprised that I can't find anything).
Anyway, tried using the files above by downloading and running the runme batch filebut it kept getting stuck on "Waiting for device." You mentioned fixing it somehow...How?
Please be thorough, I'm new.
Gotcha_Hotshot22 said:
Hi, rooting noob here-literally just starting!
Can't find anything on rooting my Kindle Fire HD 2nd Gen which is running the 11.3.2.3.2 version. It was installed today (so I'm not suprised that I can't find anything).
Anyway, tried using the files above by downloading and running the runme batch filebut it kept getting stuck on "Waiting for device." You mentioned fixing it somehow...How?
Please be thorough, I'm new.
Click to expand...
Click to collapse
Same here, been scouring the web and have found nothing, looks like we may be stuck for a while. The thing that drives me NUTS is that I got this warranty replaced by Amazon, and the day I turned it on it updated from 11.x...if ONLY I'd left it in airplane mode!!
unbwogable said:
Same here, been scouring the web and have found nothing, looks like we may be stuck for a while. The thing that drives me NUTS is that I got this warranty replaced by Amazon, and the day I turned it on it updated from 11.x...if ONLY I'd left it in airplane mode!!
Click to expand...
Click to collapse
^^ Same here.
Even contacted Amazon Support to see if there's any way to downgrade or reset to complete stock.... and was told that due to my Kindle Fire 7" 2nd Gen "lagging" and "freezing up" (wasnt sure exactly WHY I was trying to revert pre-update lol) all he could recommend was sending it in for repair/replacement. Dang it.
Off I go to (attempt) a fastboot cable.... <wish me luck!>
Send it in and then restart rooting it again.
Sent from my Amazon Tate using XDA Premium 4 mobile app
wire55 said:
Send it in and then restart rooting it again.
Sent from my Amazon Tate using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This...
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
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?