Related
Hello,
I think i just bricked my Amazon Fire 5th generation.
I Installed CM12.1 using the flashfire method. Because I cant get amazon prime instant video to work, I decided to go back to stock.
I head over to this thread: http://forum.xda-developers.com/ama...howto-how-to-restore-frimware-device-t3238740
As I can remember, I first wiped everything then installing the newest firmware 5.2.2 via sideload. Before I flashed to CM12.1, I came from fireos 5.2.2.
Now, my device is stuck in an bootloop. The screen is black all the time and I cant get the device back to work. If the device is connected to my pc, it showed up in device manager from time to time with unkown device, after some seconds it disapears and MT65xx Preloader shows up. Again after some seconds this disappears again and after some seconds the same happens over and over.
I cant force the device to stop that because it dosent do anything if i try to shut it down or trying to get into fastboot or recovery.
Is there any way to get the fire back to work?
Did you have amazon FireOS version 5.0.1 or 5.1.1?
If you had 5.1.1 then flashing 5.0.1 will brick it. And will cause your preloader to endlessly cycle as you describe. That "5.2.2" file Awesomeslayerg links to in his thread is 5.0.1, he really should have changed that post since anyone on 5.1.1 following his instructions will be hard bricked.
hAtE NeVeR dIeS said:
If the device is connected to my pc, it showed up in device manager from time to time with unkown device, after some seconds it disapears and MT65xx Preloader shows up. Again after some seconds this disappears again and after some seconds the same happens over and over.
Click to expand...
Click to collapse
I'm sorry to say, the preloader cycling like that shows that you have a hard brick (unrecoverable).
blueberry.sky said:
Did you have amazon FireOS version 5.0.1 or 5.1.1?
Could you have had 5.1.1 but accidentally flashed 5.0.1? That will cause your preloader to endlessly cycle as you describe.
I'm sorry to say, the preloader cycling like that shows that you have a hard brick (unrecoverable).
Click to expand...
Click to collapse
Before I flashed to CM12.1, I came from fireos 5.2.2. So I flashed Firmware 5.2.2 back.
Well, looks like I have to send the tab to amazon...
"5.2.2" is just the file name. We normally refer to it as FireOS 5.0.1, that is name amazon uses & system update menu displays. And it causes less confusion. I don't know why Awesomeslayerg uses "5.2.2" instead of 5.0.1.
hAtE NeVeR dIeS said:
I Installed CM12.1 using the flashfire method.
Click to expand...
Click to collapse
Did you ever try twrp? FlashFire is in beta & can be buggy. If you have 5.0.1 then you should really use twrp.
I downloaded the file linked in the post. Maybe It happens because I wiped everything before flashing the firmware and not after.
Not my fault for your guys mistakes. I'm also dome with the fire development as this community has a lack of common sense.
Awesomeslayerg said:
Not my fault for your guys mistakes. I'm also dome with the fire development as this community has a lack of common sense.
Click to expand...
Click to collapse
No problem dude. Things can happen so everything is alright. I am totally aware of that you are not responsible for damages that happen to the devices. Amazon is sending a new one. If i have to pay for this, its my problem not yours. You dont have to apologise.
But it will be great if you edit your thread and write in there, that the firmware you postet isnt fpr the 5.1.1. bootloader to prevent other users from making such a mistake.
hAtE NeVeR dIeS said:
Hello,
I think i just bricked my Amazon Fire 5th generation.
I Installed CM12.1 using the flashfire method. Because I cant get amazon prime instant video to work, I decided to go back to stock.
I head over to this thread: http://forum.xda-developers.com/ama...howto-how-to-restore-frimware-device-t3238740
As I can remember, I first wiped everything then installing the newest firmware 5.2.2 via sideload. Before I flashed to CM12.1, I came from fireos 5.2.2.
Now, my device is stuck in an bootloop. The screen is black all the time and I cant get the device back to work. If the device is connected to my pc, it showed up in device manager from time to time with unkown device, after some seconds it disapears and MT65xx Preloader shows up. Again after some seconds this disappears again and after some seconds the same happens over and over.
I cant force the device to stop that because it dosent do anything if i try to shut it down or trying to get into fastboot or recovery.
Is there any way to get the fire back to work?
Click to expand...
Click to collapse
I
think many people have this problem and I am of those
I'm a new member but can't post links, so:
Go to YouTube > search: How to Firmware Restore or Unbrick your Amazon Fire 5th gen Tablet by Rootjunky.
It really helped me out when I bricked my fire 5th Gen.
stewie2806 said:
I'm a new member but can't post links, so:
Go to YouTube > search: How to Firmware Restore or Unbrick your Amazon Fire 5th gen Tablet by Rootjunky.
It really helped me out when I bricked my fire 5th Gen.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=63943805
[Videos] Tutorials on how to root, flash roms and more on the Amazon Fire 5th gen.
Sent from my KFFOWI using Tapatalk
sd_shadow said:
http://forum.xda-developers.com/showthread.php?p=63943805
[Videos] Tutorials on how to root, flash roms and more on the Amazon Fire 5th gen.
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
thank you sir
I am looking into using SP Tools to restore the stock rom onto a bricked 5th gen. The stock roms do not have the scatter file needed to use SP Tools however there is a tool to create a scatter file but I don't have a working stock tablet to read. In addition if we can create a scatter file maybe 5.0.1 can be flashed via SP Tools onto a device that was previously 5.1.1. I would be willing to test this out if someone could create a scatter file from a stock Kindle fire 5th gen. Here is the link for the MTK tool that will create a scatter file. http://androidmtk.com/create-scatter-file-for-mtk-devices
FireBill said:
I am looking into using SP Tools to restore the stock rom onto a bricked 5th gen. The stock roms do not have the scatter file needed to use SP Tools however there is a tool to create a scatter file but I don't have a working stock tablet to read. In addition if we can create a scatter file maybe 5.0.1 can be flashed via SP Tools onto a device that was previously 5.1.1. I would be willing to test this out if someone could create a scatter file from a stock Kindle fire 5th gen. Here is the link for the MTK tool that will create a scatter file. http://androidmtk.com/create-scatter-file-for-mtk-devices
Click to expand...
Click to collapse
Won't let me create a scatter file on 5.0.1 stock, see attachment.
Didn't fare any better with the scatter file using CM rather than stock. Busybox is installed, SD card has 30GB free space, adbd insecure enabled. Sorry, not much else I know to try.
percussionking said:
Didn't fare any better with the scatter file using CM rather than stock. Busybox is installed, SD card has 30GB free space, adbd insecure enabled. Sorry, not much else I know to try.
Click to expand...
Click to collapse
Thanks, I appreciate you trying. It's always worth a shot
Can someone trying creating scatter file for 5.1.1? Maybe it works...hopefully it works.
Sent from my Moto G 2014 using Tapatalk
@lost_droid21
http://forum.xda-developers.com/showpost.php?p=65262531&postcount=13
same thing on 5.1.1
Kramar111 said:
@ost_droid21
http://forum.xda-developers.com/showpost.php?p=65262531&postcount=13
same thing on 5.1.1
Click to expand...
Click to collapse
It's not reading the MT8127 I also tried with the CM 12.1 however the software should read a firmware.info file and use that to create a scatter file. Problem is I don't see that in any of the update files. What we actually need is the OEM firmware file and not the updates and we probably won't ever see that! If we could try another backup from a rom manager that would provide a scatter or firmware.info file we may be on to something.
FireBill said:
It's not reading the MT8127 I also tried with the CM 12.1 however the software should read a firmware.info file and use that to create a scatter file. Problem is I don't see that in any of the update files. What we actually need is the OEM firmware file and not the updates and we probably won't ever see that! If we could try another backup from a rom manager that would provide a scatter or firmware.info file we may be on to something.
Click to expand...
Click to collapse
Thanks for trying that. It seems to be worse than I thought. I know it's probably going to be unlikely that we find a way to unlock the boot loader. So I guess we really need a OEM firmware file. Can anyone pitch in on that?
Sent from my Moto G 2014 using Tapatalk
I also bricked my Fire
Hi All,
I also bricked my fire while trying to downgrade to 5.0.1. Has anyone flashed ROM using any tool on bricked fire?
I have FireOS 5.3.1.0 on my 5th gen Amazon tablet and I want to put Cyanogenmod on it. I understand that I need to first go back to 5.1.2 in order for TWRP to work but I'm also seeing reports that going back to an older version bricks the device. Is it possible to put a new rom on this device? If so, does anyone know where I can find a how-to?
TragicWarrior said:
I have FireOS 5.3.1.0 on my 5th gen Amazon tablet and I want to put Cyanogenmod on it. I understand that I need to first go back to 5.1.2 in order for TWRP to work but I'm also seeing reports that going back to an older version bricks the device. Is it possible to put a new rom on this device? If so, does anyone know where I can find a how-to?
Click to expand...
Click to collapse
- 5.1.3 can be successfully rolled back to 5.1.2
- 5.3.1 is new; consequences of a rollback attempt are unknown
- twrp is not an option (period); you'll need to use FlashFire for managing custom roms
I tried, despite the warnings, and with knowledge that it could be "fatal", to put 5.1.2 on a 5th gen Fire that had 5.3.1.0 on it. It's now bricked. Only comes up to the MediaTek MT65XX PreLoader, loops on that, never shows anything on the screen. Don't do what I did.
Keith Lollis said:
I tried, despite the warnings, and with knowledge that it could be "fatal", to put 5.1.2 on a 5th gen Fire that had 5.3.1.0 on it. It's now bricked. Only comes up to the MediaTek MT65XX PreLoader, loops on that, never shows anything on the screen. Don't do what I did.
Click to expand...
Click to collapse
Thank you for sharing your findings. This small, selfless act will help others avoid a similar outcome. A respectful head nod to your device for paying the ultimate price.
@sd_shadow, @ggow - FYI.
Keith Lollis said:
I tried, despite the warnings, and with knowledge that it could be "fatal", to put 5.1.2 on a 5th gen Fire that had 5.3.1.0 on it. It's now bricked. Only comes up to the MediaTek MT65XX PreLoader, loops on that, never shows anything on the screen. Don't do what I did.
Click to expand...
Click to collapse
Was about to share the same experience... !
Keith Lollis said:
I tried, despite the warnings, and with knowledge that it could be "fatal", to put 5.1.2 on a 5th gen Fire that had 5.3.1.0 on it. It's now bricked. Only comes up to the MediaTek MT65XX PreLoader, loops on that, never shows anything on the screen. Don't do what I did.
Click to expand...
Click to collapse
Cbtg2005 said:
Was about to share the same experience... !
Click to expand...
Click to collapse
It may still be possible to re-flash 5.3.1 bootloaders via AFTV2 tools ... But right now the best route is to talk to Amazon
Crap
Keith Lollis said:
I tried, despite the warnings, and with knowledge that it could be "fatal", to put 5.1.2 on a 5th gen Fire that had 5.3.1.0 on it. It's now bricked. Only comes up to the MediaTek MT65XX PreLoader, loops on that, never shows anything on the screen. Don't do what I did.
Click to expand...
Click to collapse
F&$! Sorry about that Keith. I also have a Fire 2015 with 5.3.1.0 on it and Android 5.1.1 and I've only been able to put google apps on it and not been able to root it at all. I think you may be able to save it. Let me know.
Michael
What about going from 5.1.4? Will that brick my device? I wanna downgrade and root it.
stvy_g said:
What about going from 5.1.4? Will that brick my device? I wanna downgrade and root it.
Click to expand...
Click to collapse
I bought two tablets during Prime Day, both came with 5.1.4. I mistakenly accepted the OTA system update for 5.31. on one of the tablets, and couldn't find a way to root or downgrade (I was only able to install google play/apps). After doing a factory reset, I exchanged it at Best Buy (no restock fee!) for a tablet with 5.1.4.
I have since successfully downgraded both tablets to 5.1.2 using RootJunky's tools (Search YouTube for a video by RootJunky titled "How to Firmware Restore or Unbrick your Amazon Fire 5th gen Tablet "), and then I followed the steps from talesofatech.com from the articles list below, to root and flash to an AOSP rom.
"Kindle Fire 7″ 5th Gen: Root, Custom Home Screen, Etc"
"Kindle Fire 7″ 5th Gen: AOSP ROM"
**I have a new account, but have been lurking around here for a while. Unfortunately cannot post links yet due to forum rules.
darby123 said:
I bought two tablets during Prime Day, both came with 5.1.4. I mistakenly accepted the OTA system update for 5.31. on one of the tablets, and couldn't find a way to root or downgrade (I was only able to install google play/apps). After doing a factory reset, I exchanged it at Best Buy (no restock fee!) for a tablet with 5.1.4.
I have since successfully downgraded both tablets to 5.1.2 using RootJunky's tools (Search YouTube for a video by RootJunky titled "How to Firmware Restore or Unbrick your Amazon Fire 5th gen Tablet "), and then I followed the steps from talesofatech.com from the articles list below, to root and flash to an AOSP rom.
"Kindle Fire 7″ 5th Gen: Root, Custom Home Screen, Etc"
"Kindle Fire 7″ 5th Gen: AOSP ROM"
**I have a new account, but have been lurking around here for a while. Unfortunately cannot post links yet due to forum rules.
Click to expand...
Click to collapse
I will downgrade and post an update on the outcome.
darby123 said:
I bought two tablets during Prime Day, both came with 5.1.4. I mistakenly accepted the OTA system update for 5.31. on one of the tablets, and couldn't find a way to root or downgrade (I was only able to install google play/apps). After doing a factory reset, I exchanged it at Best Buy (no restock fee!) for a tablet with 5.1.4.
I have since successfully downgraded both tablets to 5.1.2 using RootJunky's tools (Search YouTube for a video by RootJunky titled "How to Firmware Restore or Unbrick your Amazon Fire 5th gen Tablet "), and then I followed the steps from talesofatech.com from the articles list below, to root and flash to an AOSP rom.
"Kindle Fire 7″ 5th Gen: Root, Custom Home Screen, Etc"
"Kindle Fire 7″ 5th Gen: AOSP ROM"
**I have a new account, but have been lurking around here for a while. Unfortunately cannot post links yet due to forum rules.
Click to expand...
Click to collapse
I used rootjunkys downgrade tool he posted a couple of days ago and i successfully downgraded my kindle fire and now i will try and root it
stvy_g said:
I used rootjunkys downgrade tool he posted a couple of days ago and i successfully downgraded my kindle fire and now i will try and root it
Click to expand...
Click to collapse
NOTE: the above statement refers to downgrading 5.1.3/5.1.4 -> 5.1.2. It does NOT apply to higher versions of FireOS. At this time there is no option to downgrade 5.3.1.x to a lower (rootable) version. Any attempt to do so will likely yield a brick.
stvy_g said:
I used rootjunkys downgrade tool he posted a couple of days ago and i successfully downgraded my kindle fire and now i will try and root it
Click to expand...
Click to collapse
Many people have done that (I am one). I think it's misleading to have 5.1.3/5.1.4 posts in the 5.3.1.x thread.
Read the warning too late about the 5.3.1.0 OS and now my Fire HD 8 tablet is bricked. Any one know how to get it back working again? It was 5.1.4 just the other day and I decided to downgrade today, but did not think of checking the OS version and end it up bricking it.
5.12
:good::good:
stvy_g said:
I will downgrade and post an update on the outcome.
Click to expand...
Click to collapse
:good:
Hey that's awesome. Mine came with 5.3.1 also. Can't root yet but I have google play store etc... I have a rooted Kindle HD I bought in 2012 I actually like a little better than this new one that's rooted. Hopefully there will be an update for the 5.3.1 someday. I'm glad you were able to get those down graded, it sure feels good when stuff just works right !!
Michael
Danny1976 said:
Read the warning too late about the 5.3.1.0 OS and now my Fire HD 8 tablet is bricked. Any one know how to get it back working again? It was 5.1.4 just the other day and I decided to downgrade today, but did not think of checking the OS version and end it up bricking it.
Click to expand...
Click to collapse
Wrong forum; not for HD devices. Try here:
http://forum.xda-developers.com/hd8-hd10
Anyone tried rooting 5.3.1.0 without downgrading?
sys32down said:
Anyone tried rooting 5.3.1.0 without downgrading?
Click to expand...
Click to collapse
Suspect that was one if the first things tried as there is typically no risk associated with root attempts (the payload included with some rooting apps is another story). Beyond that several have analyzed the security 'fixes' incorporated into 5.3.1 and concluded previously leveraged exposures have been closed while others have yet to be exploited. You can bet Amazon will be working to close those too.
argh... received a 5.1.4, and red to late the downgrade option to root. Tried King root, it said a root option would be possible. So I upgraded the fire tablet to 5.3.1.0 in two steps und tried in both king root... nothing worked. So I also have to wait for a new freaky instruction to root a fire 5.3.1.0
mulle1978 said:
argh... received a 5.1.4, and red to late the downgrade option to root. Tried King root, it said a root option would be possible. So I upgraded the fire tablet to 5.3.1.0 in two steps und tried in both king root... nothing worked. So I also have to wait for a new freaky instruction to root a fire 5.3.1.0
Click to expand...
Click to collapse
Welcome to Amazon's world. First rule: never update FireOS if you care about root (there are exceptions; too many caveats to detail). Second rule: ask before acting as likely someone before you has fallen into the firery pit and has a helpful tale to share.
In your case FireOS 5.1.4 was just fine - could be rolled back and rooted. 5.3.x not so much. Live and learn.
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.
Hi, is it possible to downgrade FireOS 5.4.0.1 to 5.4.0.0 on a Kindle Fire 5th Gen? If I downgrade, will it brick the device?
I'm not looking for a rootable version, I just want to downgrade it.
Thanks!
philip_io said:
Hi, is it possible to downgrade FireOS 5.4.0.1 to 5.4.0.0 on a Kindle Fire 5th Gen? If I downgrade, will it brick the device?
I'm not looking for a rootable version, I just want to downgrade it.
Thanks!
Click to expand...
Click to collapse
We don't know, nobody has tried yet. If they did, they didn't post about it. You could try at YOUR OWN RISK. I'd say it's not a good idea, but if you do try please post back with whether it worked or not. Good luck.
Sent from my KFFOWI using Tapatalk
Downgrade from 5.4.0.1 to 5.4.0.0 works fine
Today, I used the adb sideloader to downgrade my 5th gen 7" Fire from 5.4.0.1 to the less restrictive 5.4.0.0. No problems, not bricked. Will post back if I find anything wrong with it. 5.4.0.0 allows you to use shell commands to delete unwanted system apps, for those of you who don't know.
Coneyfox said:
Today, I used the adb sideloader to downgrade my 5th gen 7" Fire from 5.4.0.1 to the less restrictive 5.4.0.0. No problems, not bricked. Will post back if I find anything wrong with it. 5.4.0.0 allows you to use shell commands to delete unwanted system apps, for those of you who don't know.
Click to expand...
Click to collapse
Thanks for the information!
Coneyfox said:
Today, I used the adb sideloader to downgrade my 5th gen 7" Fire from 5.4.0.1 to the less restrictive 5.4.0.0. No problems, not bricked. Will post back if I find anything wrong with it. 5.4.0.0 allows you to use shell commands to delete unwanted system apps, for those of you who don't know.
Click to expand...
Click to collapse
This is great news! Can you give the details on how you did it? I'm not familiar with sideloading firmware; I've only ever sideloaded .apk's. Thanks!
Coneyfox said:
Today, I used the adb sideloader to downgrade my 5th gen 7" Fire from 5.4.0.1 to the less restrictive 5.4.0.0. No problems, not bricked. Will post back if I find anything wrong with it. 5.4.0.0 allows you to use shell commands to delete unwanted system apps, for those of you who don't know.
Click to expand...
Click to collapse
Please can you link to the file you used to sideload.
edit NVM, i found it. Right where it belongs. lol..on amazon.
forawesome said:
This is great news! Can you give the details on how you did it? I'm not familiar with sideloading firmware; I've only ever sideloaded .apk's. Thanks!
Click to expand...
Click to collapse
See video in OP of this thread. Be sure to use the file (.bin) for FireOS 5.4.0.0 vs whatever build is mentioned in the video.
Coneyfox said:
Today, I used the adb sideloader to downgrade my 5th gen 7" Fire from 5.4.0.1 to the less restrictive 5.4.0.0. No problems, not bricked. Will post back if I find anything wrong with it. 5.4.0.0 allows you to use shell commands to delete unwanted system apps, for those of you who don't know.
Click to expand...
Click to collapse
I am skeptcal of this users report of being able to downgrade.
*no details
* no response to requests for details
* poster is new xda poster with only 3 posts, all of which are claiming successfull downgrade.
maybe just me , but I would not want to be first to follow his footsteps.
mrmazak said:
I am skeptcal of this users report of being able to downgrade.
*no details
* no response to requests for details
* poster is new xda poster with only 3 posts, all of which are claiming successfull downgrade.
maybe just me , but I would not want to be first to follow his footsteps.
Click to expand...
Click to collapse
It's the same guy who made the post about 5.3.3 root by flashing SuperSu. Seriously though guys, if you plan on actually using your tablet and not just experimenting with it for fun, don't do this. Especially if you aren't in the 30 day exchange period anymore.
Technocian said:
It's the same guy who made the post about 5.3.3 root by flashing SuperSu. Seriously though guys, if you plan on actually using your tablet and not just experimenting with it for fun, don't do this. Especially if you aren't in the 30 day exchange period anymore.
Click to expand...
Click to collapse
Don't have time to look now; if this guy has a history of intentionally misleading members (potentially leading to bricked devices) will report and let the mods deal with him.
The same went for those reporting it CAN'T be done...new users, a few posts. I try to have an open mind, but unless they're regular users, I take some new user posts with a grain of salt. Always be careful.
EDIT: I did walk one user through trying to downgrade an HD 8 FROM 5.4.0.1, which was unsuccessful and resulted in an unrecoverable brick. It's likely the same thing for the Fire 7.
Hi, new to XDA forums - about 2 weeks ago I came here looking for a way to re-google my fire 7 (which I'd just bought) but mine was already upgraded to 5.4.0.1
I tried to downgrade using a .bin from amazon but it failed during verification so I gave up. Because of this thread I re-downloaded the .bin (which seems to have changed? I'm unexperienced but the update number is different) and tried again.
It downgraded fine and I'm running 5.4.0.0 - I'm honestly not sure what changed but thought I'd put this out there.
shw2921 said:
Hi, new to XDA forums - about 2 weeks ago I came here looking for a way to re-google my fire 7 (which I'd just bought) but mine was already upgraded to 5.4.0.1
I tried to downgrade using a .bin from amazon but it failed during verification so I gave up. Because of this thread I re-downloaded the .bin (which seems to have changed? I'm unexperienced but the update number is different) and tried again.
It downgraded fine and I'm running 5.4.0.0 - I'm honestly not sure what changed but thought I'd put this out there.
Click to expand...
Click to collapse
Do you know if your fire is 5th or 7th gen?
mrmazak said:
Do you know if your fire is 5th or 7th gen?
Click to expand...
Click to collapse
It's a 7th gen
mrmazak said:
Do you know if your fire is 5th or 7th gen?
Click to expand...
Click to collapse
It appears the Fire 7 CAN be downgraded, but likely the HD 8 CANNOT be. I don't know how this is possible though. Maybe someone else can chime in about the specifics.
If you are on 5.4.0.0, you can uninstall/disable system apps. So if that's what you're looking to do, congrats...You can still do it
shw2921 said:
I tried to downgrade using a .bin from amazon but it failed during verification so I gave up. Because of this thread I re-downloaded the .bin (which seems to have changed? I'm unexperienced but the update number is different) and tried again.
Click to expand...
Click to collapse
Hi,
this sounds like during the first attempt you used (tried to use) a firmware that was created for the 5th gen fire 7 (codenamed "ford"), not the 7th gen ("austin") that you have. Their names differ in only one place AFAICT: it's a 37 (5th) or a 55 (7th).
While for both device generations there's no 5.4.0.1 for download, someone might have a closer look at the .bins to learn about the hardware differences between 5th and 7th - beyond what we already know.
steve8x8 said:
Hi,
this sounds like during the first attempt you used (tried to use) a firmware that was created for the 5th gen fire 7 (codenamed "ford"), not the 7th gen ("austin") that you have. Their names differ in only one place AFAICT: it's a 37 (5th) or a 55 (7th).
While for both device generations there's no 5.4.0.1 for download, someone might have a closer look at the .bins to learn about the hardware differences between 5th and 7th - beyond what we already know.
Click to expand...
Click to collapse
Awesome! That explains it. The more I learn the better. Also to DragonFire - yes I wanted 5.4.0.0 for system app removal, so it turned out good in the end.
shw2921 said:
Awesome! That explains it. The more I learn the better. Also to DragonFire - yes I wanted 5.4.0.0 for system app removal, so it turned out good in the end.
Click to expand...
Click to collapse
Sorry to repeat this again. But there were some conflicting reports about whether it is possible to go from Fire OS 5.4.0.1 to Fire OS 5.4.0.0. (One report of failure for Fire HD8 (7th Generation)).
Would you please confirm the following steps:
(1). You have Fire 7 (7th Generation, 2017 model) with Fire OS 5.4.0.1
(2). You go to this Amazon site to download Fire 7th Generation OS 5.4.0.0 :
https://www.amazon.com/gp/help/customer/display.html/ref=hp_left_v4_sib?ie=UTF8&nodeId=202144590
(3). You sideload the file from Step (2) above by typing ,from a PC window, "adb sideload update-kindle-55.5.7.9_user_579225620.bin"
Thank you so much.
I am waiting for more reports of success before I attempt to "roll-back" my Fire 7 (7th Generation) from OS 5.4.0.1 to OS 5.4.0.0, so that I can "pm uninstall" most of the Amazon Apps.
My Amazon Fire 2015 downgraded to 5.4.0.0 just fine. Removed OTA updates, Lockscreen Offers, and Amazon Apps.
Nice to know that if in the event a Fire does update to 5.4.0.1, it can be rolled back.
Sent from my KFFOWI using Tapatalk
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?