Was rolling back my kindle fire hdx 7 3rd gen. Using this method, rolled back to 3.2.8. All good, no problems. Then tried to download the firmware to go to 4.5.2, some reason my laptop kept stopping the download partway through, so I tried to download on the tablet, battery was about 40%, download for 4.5.2 was 20% or so. I leave it alone for five minutes and come back and it won't turn on. I tried charging it for bout half an hour, tried resetting it by holding it for 30 seconds, no luck. I plug it into the computer, it shows up as QHSUSB_BULK, tried updating drivers and it can't find anything. I'm at a loss for what to do, I can't find the box for it in case I need to turn it in for another one, I believe it's still under warranty. So my only hope is to somehow unbrick it. Any help would be appreciated.
If its under warranty, get a new one. I'm not sure if you could recover form that with a locked bl.
MinerBoy004 said:
If its under warranty, get a new one. I'm not sure if you could recover form that with a locked bl.
Click to expand...
Click to collapse
I lost the box for it, will try to look for it later. Is it absolutely necessary to find the box? I live on Guam, think of a ****tier version of Hawaii, don't think there are any amazon stores here. What do I need to get another? Pretty sure it's still under warranty.
Rengiil said:
Was rolling back my kindle fire hdx 7 3rd gen. Using this method, rolled back to 3.2.8. All good, no problems. Then tried to download the firmware to go to 4.5.2, some reason my laptop kept stopping the download partway through, so I tried to download on the tablet, battery was about 40%, download for 4.5.2 was 20% or so. I leave it alone for five minutes and come back and it won't turn on. I tried charging it for bout half an hour, tried resetting it by holding it for 30 seconds, no luck. I plug it into the computer, it shows up as QHSUSB_BULK, tried updating drivers and it can't find anything. I'm at a loss for what to do, I can't find the box for it in case I need to turn it in for another one, I believe it's still under warranty. So my only hope is to somehow unbrick it. Any help would be appreciated.
Click to expand...
Click to collapse
Sorry, you did not read through the instructions and numerous cautions that explicitly warn against having a network connection while/after doing a 3.2.8 rollback. Your device received a OTA update which is a death sentence with absolutely no chance of recovery. Hopefully Amazon will allow an exchange.
Davey126 said:
Sorry, you did not read through the instructions and numerous cautions that explicitly warn against having a network connection while/after doing a 3.2.8 rollback. Your device received a OTA update which is a death sentence with absolutely no chance of recovery. Hopefully Amazon will allow an exchange.
Click to expand...
Click to collapse
Ah I see, I did read it, but it honestly slipped my mind when the darn thing wouldn't download on my laptop. Let this be a warning to others then.
Related
So, I've had my Kindle Fire HDX 7' for a while now, and it's been running great. But amazon updated it from 4.5.3 to 4.5.4 and then it wouldn't boot. It would say: Fire is Upgrading, please wait... Then it would prompt me to choose the default kindle launcher, nova launcher, or the setup wizard. Which ever one I chose, it would close the window, but then come back to the same place. I contacted amazon support, and they said to boot into recovery (power+volume up) and factory reset, which I did. And now what happens is it says Fire is Upgrading please wait... then says that it is starting applications. But it stays there, and nothing happens. Anybody know a way I can fix this?
A very long shot, but try holding down the power button for 2 minutes.
lekofraggle said:
A very long shot, but try holding down the power button for 2 minutes.
Click to expand...
Click to collapse
Nope, that just force rebooted it a bunch of times
ftf841 said:
So, I've had my Kindle Fire HDX 7' for a while now, and it's been running great. But amazon updated it from 4.5.3 to 4.5.4 and then it wouldn't boot. It would say: Fire is Upgrading, please wait... Then it would prompt me to choose the default kindle launcher, nova launcher, or the setup wizard. Which ever one I chose, it would close the window, but then come back to the same place. I contacted amazon support, and they said to boot into recovery (power+volume up) and factory reset, which I did. And now what happens is it says Fire is Upgrading please wait... then says that it is starting applications. But it stays there, and nothing happens. Anybody know a way I can fix this?
Click to expand...
Click to collapse
You mentioned Nova which suggests device was rooted. Once rooted you have to block OTA. Not a lot of options unless root was retained through the update (unlikely) and you have adb enabled. I would work with Amazon given the 4.5.4 update hosed your device. Might get a discount on a replacement. Probably best not to mention root, Nova or any other customizations.
Davey126 said:
You mentioned Nova which suggests device was rooted. Once rooted you have to block OTA. Not a lot of options unless root was retained through the update (unlikely) and you have adb enabled. I would work with Amazon given the 4.5.4 update hosed your device. Might get a discount on a replacement. Probably best not to mention root, Nova or any other customizations.
Click to expand...
Click to collapse
When I contacted them, I didn't mention anything about those. However, it had been past a year, and so the warranty was out, and they said they couldn't do anything about it. I get a 20 dollar discount though
ftf841 said:
When I contacted them, I didn't mention anything about those. However, it had been past a year, and so the warranty was out, and they said they couldn't do anything about it. I get a 20 dollar discount though
Click to expand...
Click to collapse
If I were to guess is your Kindle is trying to start the native launcher but is encountering a conflict with Nova. On most devices this would be fairly easy to fix. Recent Kindles are locked down by Amazon. A next-to-use useless recovery environment compounds the problem. So far no one has figured out how to crack this nut on an unrooted device running Fire v4.
Press your case with Amazon. If you are regular customer a supervisor may be willing to make an exception or offer a larger discount. Your argument is based on an unwanted/unrequested/unnecessary amazon update that went bad. Just minding your own business and blamo ... an OTA out of the blue turned your world upside down. Or something like that ....
Davey126 said:
If I were to guess is your Kindle is trying to start the native launcher but is encountering a conflict with Nova. On most devices this would be fairly easy to fix. Recent Kindles are locked down by Amazon. A next-to-use useless recovery environment compounds the problem. So far no one has figured out how to crack this nut on an unrooted device running Fire v4.
Press your case with Amazon. If you are regular customer a supervisor may be willing to make an exception or offer a larger discount. Your argument is based on an unwanted/unrequested/unnecessary amazon update that went bad. Just minding your own business and blamo ... an OTA out of the blue turned your world upside down. Or something like that ....
Click to expand...
Click to collapse
If Nova was conflicting, the factory reset should've fixed it. Something I forgot to mention, is if I shut it down after it prompts me which launcher to choose, it goes through the same process all over again, with the updating, leading me to believe it's something deeper than just the launchers conflicting.
ftf841 said:
If Nova was conflicting, the factory reset should've fixed it. Something I forgot to mention, is if I shut it down after it prompts me which launcher to choose, it goes through the same process all over again, with the updating, leading me to believe it's something deeper than just the launchers conflicting.
Click to expand...
Click to collapse
A factory reset on a Kindle isn't what you think. It restores some files but does not perform a comprehensive refresh. A reasonable (albeit imperfect) comparison is system restore in Windows. Addresses some issues but is by no means comprehensive. Unlike Windows you don't have access to low level files without root and usually can't fix a start-up problem even if you know the source. What you really want is a true 'reset' or 'restore'; those options aren't available in the stock recovery.
I'm not saying it's 100% unresolvable. But few users exit the dreaded 'setup loop' w/o root access. Don't mean to be negative but also do not want to raise false hopes. There are a few clever (and very talented!) individuals who monitors these forums. Let this post sit for awhile and see who chimes in.
Davey126 said:
A factory reset on a Kindle isn't what you think. It restores some files but does not perform a comprehensive refresh. A reasonable (albeit imperfect) comparison is system restore in Windows. Addresses some issues but is by no means comprehensive. Unlike Windows you don't have access to low level files without root and usually can't fix a start-up problem even if you know the source. What you really want is a true 'reset' or 'restore'; those options aren't available in the stock recovery.
I'm not saying it's 100% unresolvable. But few users exit the dreaded 'setup loop' w/o root access. Don't mean to be negative but also do not want to raise false hopes. There are a few clever (and very talented!) individuals who monitors these forums. Let this post sit for awhile and see who chimes in.
Click to expand...
Click to collapse
Well, thanks anyways
Holding the power button is a way of clearing the cache. It seems like it is just rebooting, but if you do not have a true recovery (which you don't, it is a long shot which has worked for many. If you gave up after a few rounds, stick to it). If that does not work, try pressing poker once and Now, instead of choosing your launcher, enforcing the Kindle to give you the notification bar. Try holding power for just a second and clicking cancel and swiping down from the top. If youngest into settings, you may be able to try the update again. That may reset whatever broke, but Davey is correct, if you indeed were rooted, this is looking bad. If you were not, and you just downloaded nova, there is still a bit of hope.
lekofraggle said:
Holding the power button is a way of clearing the cache. It seems like it is just rebooting, but if you do not have a true recovery (which you don't, it is a long shot which has worked for many. If you gave up after a few rounds, stick to it). If that does not work, try pressing poker once and Now, instead of choosing your launcher, enforcing the Kindle to give you the notification bar. Try holding power for just a second and clicking cancel and swiping down from the top. If youngest into settings, you may be able to try the update again. That may reset whatever broke, but Davey is correct, if you indeed were rooted, this is looking bad. If you were not, and you just downloaded nova, there is still a bit of hope.
Click to expand...
Click to collapse
Well, Amazon told me to boot to recovery and factory reset and that may have screwed me over, because now it doesn't show the nova or kindle launcher, in place of that it says, starting applications, but nothing happens after that. I'll try holding the power button, because I did give up after 3 reboots.
The factory reset could have been a mistake, but I would assume they would have taken you through the power button piece first. Hmm. But, you did try their advice, and it got worse, so perhaps they will hand you a shiny referb. in return. If they do, check it for structural damage. I needed a return, because one of their updates messed my original one up (the kindle app and clipboard would not load), and they sent one with an old boot loader, but it had a cracked bezel. I did eventually get one that worked well, but it took a few rounds. They all had software or hardware issues. Through it all, tech support was stellar.
ftf841 said:
Well, Amazon told me to boot to recovery and factory reset and that may have screwed me over, because now it doesn't show the nova or kindle launcher, in place of that it says, starting applications, but nothing happens after that. I'll try holding the power button, because I did give up after 3 reboots.
Click to expand...
Click to collapse
lekofraggle said:
The factory reset could have been a mistake, but I would assume they would have taken you through the power button piece first. Hmm. But, you did try their advice, and it got worse, so perhaps they will hand you a shiny referb. in return. If they do, check it for structural damage. I needed a return, because one of their updates messed my original one up (the kindle app and clipboard would not load), and they sent one with an old boot loader, but it had a cracked bezel. I did eventually get one that worked well, but it took a few rounds. They all had software or hardware issues. Through it all, tech support was stellar.
Click to expand...
Click to collapse
I think you have a pretty good argument for your next Amazon engagement given the advise given actually made things worse. Obviously demeanor is important; treat everyone with respect and (gently) ask to speak with a supervisor if things grind to a halt. Reputation and customer satisfaction are important to Amazon but you have to be persistent.
Btw - lekofraggle is one of those clever/talented individuals I referenced earlier. Thought s/he might stop by. As always, great to hear multiple perspectives! Good luck.
You must have been in Warranty Leo. I tried so many times. The most helpful tech managed to get me a hundred bucks off, but this was several hours on the phone... He said that a few other people had the same hard brick that I had(never mentioned root) but... no warranty. @op good luck trying to fix this. Amazon is worse than Verizon imo because there is practically no way to fix this damned thing.
I was under warranty. That is too bad because not only is there no way to fix this, there was no way (that they know or want you to be privy to) to prevent it. That is wrong imo.
I'm having the same situation. My kindle was working fine before the night, and the Amazon auto upgrade bricked my Kindle. I contacted Amazon for help. During the conversation they changed 5 agents including one who claimed himself "one of the leaders". Most of them didn't seem to know what happened and how to fix it. Two of them mentioned that I need to factory reset my tablet, but none of them show me how to get into the recovery mode. After 4 hours of conversation they told me my kindle cannot be fixed and the only choice I have is to replace my kindle. And then they said since I've own my kindle for more than one year, the warranty is expired, as a result they cannot replace the kindle for me but they can offer me a discount if I buy another one from them. I was annoyed because what broke my Kindle is Amazon's update, not me. To me, they literally sold me a kindle and broke it after the warranty expired, and then try to sell me another one. They ended up giving me a $50 gift card for whatever sold and shipped by Amazon.
After the conversation I found the way to get into the recovery mode. And I hit the factory reset button. After the reset progress is complete my kindle is still stuck at "starting application", sometimes it passes "starting application" and the screen start flashing... as if the tablet is going to explode....I doubt maybe it is the factory reset file's problem, but it is too late for me to get into the storage using ADB since I don't have debugging mode activated after factory reset.
You may still have adv after factory reset. It only resets some settings. And deletes portions of the /data partition. It does not delete anything from the sd card or much from the /system partitions (which is why it does not help too much if there was a botched install or you messed something up with root powers.
That said, it does remove root, so adb is limited.
Brad D said:
I'm having the same situation. My kindle was working fine before the night, and the Amazon auto upgrade bricked my Kindle. I contacted Amazon for help. During the conversation they changed 5 agents including one who claimed himself "one of the leaders". Most of them didn't seem to know what happened and how to fix it. Two of them mentioned that I need to factory reset my tablet, but none of them show me how to get into the recovery mode. After 4 hours of conversation they told me my kindle cannot be fixed and the only choice I have is to replace my kindle. And then they said since I've own my kindle for more than one year, the warranty is expired, as a result they cannot replace the kindle for me but they can offer me a discount if I buy another one from them. I was annoyed because what broke my Kindle is Amazon's update, not me. To me, they literally sold me a kindle and broke it after the warranty expired, and then try to sell me another one. They ended up giving me a $50 gift card for whatever sold and shipped by Amazon.
After the conversation I found the way to get into the recovery mode. And I hit the factory reset button. After the reset progress is complete my kindle is still stuck at "starting application", sometimes it passes "starting application" and the screen start flashing... as if the tablet is going to explode....I doubt maybe it is the factory reset file's problem, but it is too late for me to get into the storage using ADB since I don't have debugging mode activated after factory reset.
Click to expand...
Click to collapse
If you rooted your Kindle then over-the-air (OTA) updates must also be blocked. That's the case for many devices as the update package expects a device is in a specific condition which may no longer be true after rooting. If the device has never been rooted or otherwise modified an an 'unsupported' manner (including side loading applications; read the disclaimer) then I agree you have a strong case against Amazon and should reengage with the understanding that you will take stronger action if they do not provide a better resolution. Worth a shot unless you are satisfied with the $50 or have something to 'hide'.
Davey126 said:
If you rooted your Kindle then over-the-air (OTA) updates must also be blocked. That's the case for many devices as the update package expects a device is in a specific condition which may no longer be true after rooting. If the device has never been rooted or otherwise modified an an 'unsupported' manner (including side loading applications; read the disclaimer) then I agree you have a strong case against Amazon and should reengage with the understanding that you will take stronger action if they do not provide a better resolution. Worth a shot unless you are satisfied with the $50 or have something to 'hide'.
Click to expand...
Click to collapse
I didn't have my kindle rooted, while I did install some applications from 1 mobile market. I even asked them to take my kindle back for further inspection, while they simply refused my suggestion and insisted their solution, which is either I return the kindle for the discount for a new purchase, or the $50 gift card. I figured that it may cost me more to take further action as I'm just one foreign customer and I don't see many who met the same situation in here.
Hello,
I own the kindle fire HDX 8.9 3rd generation. Yesterday i rerolled my version back to 3.2.4, everything seemed to be working just fine.
But after i closed my case and reopened it after half an hour my device was shutted down (the battery was 80%). Since i've been trying to turn it on with no succes. I've also contacted amazon support who were willing to give me an "huge" sale on my next purchase (20$) since they don't think it will ever work again.
On my pc in device manager my kindle does show up, but when i try to install adb drivers i get an error 10.
I'm hoping to get some help here.
HybridLion said:
Hello,
I own the kindle fire HDX 8.9 3rd generation. Yesterday i rerolled my version back to 3.2.4, everything seemed to be working just fine.
But after i closed my case and reopened it after half an hour my device was shutted down (the battery was 80%). Since i've been trying to turn it on with no succes. I've also contacted amazon support who were willing to give me an "huge" sale on my next purchase (20$) since they don't think it will ever work again.
On my pc in device manager my kindle does show up, but when i try to install adb drivers i get an error 10.
I'm hoping to get some help here.
Click to expand...
Click to collapse
Did you block OTA and/or disable WiFi after rolling back to 3.2.8? If not you likely received an update from Amazon which often leads to a hard brick (no recovery).
What version were you on before and did you directly edit build prop?
Try holding the power button for up to 60 sec. Any response?
Davey126 said:
Did you block OTA and/or disable WiFi after rolling back to 3.2.8? If not you likely received an update from Amazon which often leads to a hard brick (no recovery).
What version were you on before and did you directly edit build prop?
Try holding the power button for up to 60 sec. Any response?
Click to expand...
Click to collapse
No i didn't block the OTA, i wasn't even planning on rooting and stuff, i downloaded the 3.2.4 from amazons site.
I downgraded from the newest versien 4.?.? (it didn't work with my vpn)
I have absolutely no response when pressing it for 60 seconds
HybridLion said:
No i didn't block the OTA, i wasn't even planning on rooting and stuff, i downloaded the 3.2.4 from amazons site.
I downgraded from the newest versien 4.?.? (it didn't work with my vpn)
I have absolutely no response when pressing it for 60 seconds
Click to expand...
Click to collapse
You can't go from 4.x to anything below 3.2.8. Amazon incorporated anti-rollback protection after 3.2.6. If you try to install an earlier version it will permanently disable the device. Also known as an 'efuse'. Sorry mate, there is no recovery.
Davey126 said:
You can't go from 4.x to anything below 3.2.8. Amazon incorporated anti-rollback protection after 3.2.6. If you try to install an earlier version it will permanently disable the device. Also known as an 'efuse'. Sorry mate, there is no recovery.
Click to expand...
Click to collapse
What the ****...
Why the fuc*k* do they offer a download of 3.2.5 on their website?
So there is seriously no way to recover it? Well good by all my brithday money:good:
**** you amazon
HybridLion said:
What the ****...
Why do they offer a download of 3.2.5 on their website?
So there is seriously no way to recover it? Well good by all my brithday money:good:
**** you amazon
Click to expand...
Click to collapse
Really sorry this happened. For future reference system images are supplied to repair or upgrade a device. Downgrades are always risky and rarely supported regardless of mfg. In this case a little knowledge (likely gained through these forums) met a loaded gun. Unfortunately, there is no known fix to an efuse brick.
Davey126 said:
Really sorry this happened. For future reference system images are supplied to repair or upgrade a device. Downgrades are always risky and rarely supported regardless of mfg. In this case a little knowledge (likely gained through these forums) met a loaded gun. Unfortunately, there is no known fix to an efuse brick.
Click to expand...
Click to collapse
Yeah i feel like a huge turd...
Well thanks anyway... F#king amazon :c
Have you looked at some of the possible techniques around from last year? There were reports of holding the power button down for over a minute to try and get to Fastboot or something... have a look around and you may find something, hope isn't always lost.
You can get into fastboot by holding the minus button while booting, but I am not sure how much it will help with a locked boot loader. Technically, it should flash a factory image, but I am not sure anyone has gotten that to work on the hdx. Note, if you try this, the windows drivers are a pain and there is a special way to run commands for the hdx. Check out the boot unlock op for the commands, the rest of the thread for the drivers, and know you are in uncharted territory.
Good luck,
Leko
From my understanding, blowing an eFuse is physical and thus irreversible unless you replace the actual chip.
I messed mine up, too I believe. I tried flashing the new safestrap ROM with the older safestrap. And now only the gray kindle fire logo stays on. I tried holding down the power button a minute, but just turns the gray logo off and on. I'm assuming there is no way out of this, correct?
manymarius73 said:
I messed mine up, too I believe. I tried flashing the new safestrap ROM with the older safestrap. And now only the gray kindle fire logo stays on. I tried holding down the power button a minute, but just turns the gray logo off and on. I'm assuming there is no way out of this, correct?
Click to expand...
Click to collapse
Correct (sorry).
Yeah.. I gambled. Guess I lost this round.
what kind of douchebag company keeps a version of an os on their website that will brick their device without warning ? if i were you i would never buy one of their products and since the same thing happened to me i will do the same :/
Jasonbrody14 said:
what kind of douchebag company keeps a version of an os on their website that will brick their device without warning ? if i were you i would never buy one of their products and since the same thing happened to me i will do the same :/
Click to expand...
Click to collapse
While I appreciate your frustration this is not Amazon's fault. The actions you and others took are not recommended by Amazon nor most other device manufacturers. The 3.2.8 rollback file that you used was silently captured w/o Amazon's permission and was intended for devices that would never received an OTA update. A few clever individuals figured out how to exploit that file to facilitate 4.5.4 -> 4.5.2 rollbacks (also not supported by Amazon). There are warnings everywhere that wifi must be kept off (or the device placed in 'airplane mode') when using this rollback technique. I am very sorry you lost your device but ultimately the risks and responsibility for bad outcomes are borne by the owner.
Davey126 said:
While I appreciate your frustration this is not Amazon's fault. The actions you and others took are not recommended by Amazon nor most other device manufacturers. The 3.2.8 rollback file that you used was silently captured w/o Amazon's permission and was intended for devices that would never received an OTA update. A few clever individuals figured out how to exploit that file to facilitate 4.5.4 -> 4.5.2 rollbacks (also not supported by Amazon). There are warnings everywhere that wifi must be kept off (or the device placed in 'airplane mode') when using this rollback technique. I am very sorry you lost your device but ultimately the risks and responsibility for bad outcomes are borne by the owner.
Click to expand...
Click to collapse
yeah its my fault for installing an old update i admit that but they host several other versions on their website that arnt 3.2.8 that also brick the device. i just wonder why they would even do that at least instead of permanently killing the device it would just soft brick it :/
Jasonbrody14 said:
yeah its my fault for installing an old update i admit that but they host several other versions on their website that arnt 3.2.8 that also brick the device. i just wonder why they would even do that at least instead of permanently killing the device it would just soft brick it :/
Click to expand...
Click to collapse
Amazon updates don't brick unless: 1) the device is rooted (which means you can get around all protections); or 2) something goes wrong with the update (as occasionally happens to all devices regardless of make). The stock updater will reject attempts to rollback or install an incompatible update. My local auto parts store carries lots of engine elixirs that can work wonders if used correctly. Go off-label and one can 'brick' a $4K engine in minutes.
I'm not ragging on you; what's done is done. Hopefully this post will help someone else contemplating rolling back their device. Tinkers beware: the road to the candy store is laced with land mines.
My Apollo is stuck trying to upgrade itself.
Background
Previously I did have Safestrap 3.75 and was running Nexus 1.0.1 is in a slot. I had 14.3.2.8 sitting in the Stock Rom slot.
Decided to upgrade to Nexus 4.0.5 so I went back to the stock slot and uninstalled safestrap 3.75.
Saw in the Safestrap 4.0.1 thread that I needed to be on 14.4.5.2 for it to work, so I manually forced upgrade to that version.
Then while I was attempting to get root back (quickly allowing wifi access for it to work) the damn machine downloaded a newer version of stock and tried to install it.
Well I thought "fine I will let it upgrade and then roll back to 14.3.2.8 and start again"
Wrong!. The HDX rebooted and then when it restarted it is now stuck at "Fire is upgrading..." and "Starting applications..." (shortly after the second orange Kindle Fire boot logo)
Now I cant access by adb because the unit is "unauthorized".
Any hope of getting it back online? Its been stuck at boot for a day now. Any hope of a way to bypass the upgrade during the boot phase?
Thanks in advance.
maccaberry said:
My Apollo is stuck trying to upgrade itself.
Background
Previously I did have Safestrap 3.75 and was running Nexus 1.0.1 is in a slot. I had 14.3.2.8 sitting in the Stock Rom slot.
Decided to upgrade to Nexus 4.0.5 so I went back to the stock slot and uninstalled safestrap 3.75.
Saw in the Safestrap 4.0.1 thread that I needed to be on 14.4.5.2 for it to work, so I manually forced upgrade to that version.
Then while I was attempting to get root back (quickly allowing wifi access for it to work) the damn machine downloaded a newer version of stock and tried to install it.
Well I thought "fine I will let it upgrade and then roll back to 14.3.2.8 and start again"
Wrong!. The HDX rebooted and then when it restarted it is now stuck at "Fire is upgrading..." and "Starting applications..." (shortly after the second orange Kindle Fire boot logo)
Now I cant access by adb because the unit is "unauthorized".
Any hope of getting it back online? Its been stuck at boot for a day now. Any hope of a way to bypass the upgrade during the boot phase?
Thanks in advance.
Click to expand...
Click to collapse
Unfortunately, not much you can do without adb access. As a long shot try a factory reset from the native Kindle Fire recovery menu. Often this makes things worse but you have little to loose given the symptoms and age of device (likely long out of warranty).
Davey126 said:
Unfortunately, not much you can do without adb access. As a long shot try a factory reset from the native Kindle Fire recovery menu. Often this makes things worse but you have little to loose given the symptoms and age of device (likely long out of warranty).
Click to expand...
Click to collapse
On the phone with Amazon right now. They also suggested Factory Reset. I know it cant get worse because I already have no root. So I gave it a go. Just bootloops now - still trying to upgrade itself.
They want me to replace it with a refurb at my cost.
Thanks for nothing Amazon. I was on stock when this happened and it was your update that screwed me! LOL Probably get a Samsung or Nexus to replace. It was fun while it lasted though.
maccaberry said:
On the phone with Amazon right now. They also suggested Factory Reset. I know it cant get worse because I already have no root. So I gave it a go. Just bootloops now - still trying to upgrade itself.
They want me to replace it with a refurb at my cost.
Thanks for nothing Amazon. I was on stock when this happened and it was your update that screwed me! LOL Probably get a Samsung or Nexus to replace. It was fun while it lasted though.
Click to expand...
Click to collapse
What you experienced is not uncommon based comments posted in XDA forums and Amazon customer reviews. OTAs are never 100% reliable but HDX devices seem to be more vulnerable to soft bricks with limited/no recovery options. Obviously the vast majority of users upgrade without incident but even a low single digit failure rate during the expected lifespan of the device raises a red flag. Amazon's replacement policy is also consistent: once out of warranty they will offer a refurb at current prices occasionally muted with a modest discount (eg: $20 USD off). BFD.
HDX is a great hunk of hardware if you can tame it. Nexus and Samsung tablets are a notch below imo but are much easier to mod. Sorry for your loss; good luck with whatever direction you opt to go.
Davey126 said:
What you experienced is not uncommon based comments posted in XDA forums and Amazon customer reviews. OTAs are never 100% reliable but HDX devices seem to be more vulnerable to soft bricks with limited/no recovery options. Obviously the vast majority of users upgrade without incident but even a low single digit failure rate during the expected lifespan of the device raises a red flag. Amazon's replacement policy is also consistent: once out of warranty they will offer a refurb at current prices occasionally muted with a modest discount (eg: $20 USD off). BFD.
HDX is a great hunk of hardware if you can tame it. Nexus and Samsung tablets are a notch below imo but are much easier to mod. Sorry for your loss; good luck with whatever direction you opt to go.
Click to expand...
Click to collapse
Hi Davey, thanks for the thoughts. Its the truth that after 2 years this specs on the 3rd gen HDX are still right up there. The image quality and sound quality are outstanding compared to just about anything available - even today. But unfortunately if you like to tinker then its just too much work. Samsung and other manufacturers are heading down the same path with locked bootloaders but even so modding seems a dream compared to the HDX.
Probably going to get a tablet that utilizes a stylus since I really want to use it as a digital notepad for work and a movie player for leisure. My regular kindle e-reader is still the best option for reading books due to very light weight. As good as the HDX is (and any tablet for that matter), tablets are still a bit to heavy for serious reading in bed and the back light disturbs your sleep patterns.
If anyone else reading this has a viable option to get the unit to reboot without upgrading I am all ears, because as I have said I would love to get a bit more life out of this fantastic HDX hardware.
maccaberry said:
If anyone else reading this has a viable option to get the unit to reboot without upgrading I am all ears, because as I have said I would love to get a bit more life out of this fantastic HDX hardware.
Click to expand...
Click to collapse
Take a peek at this thread for ideas. Long shot at best. The small glimmer of hope is you made it past the grey logo so dealing with a soft vs hard brick. That said, if USB debug wasn't enabled on 4.5.2 you will be hard pressed to secure meaningful access. Sorry this happened. Might look at grabbing a HDX from an auction site. You are wiser now and would likely make it through the rollback/upgrade procedure intact.
stackoverflow.com/questions/18011685/cant-connect-nexus-4-to-adb-unauthorized
maccaberry said:
Hi Davey, thanks for the thoughts. Its the truth that after 2 years this specs on the 3rd gen HDX are still right up there. The image quality and sound quality are outstanding compared to just about anything available - even today. But unfortunately if you like to tinker then its just too much work. Samsung and other manufacturers are heading down the same path with locked bootloaders but even so modding seems a dream compared to the HDX.
Probably going to get a tablet that utilizes a stylus since I really want to use it as a digital notepad for work and a movie player for leisure. My regular kindle e-reader is still the best option for reading books due to very light weight. As good as the HDX is (and any tablet for that matter), tablets are still a bit to heavy for serious reading in bed and the back light disturbs your sleep patterns.
If anyone else reading this has a viable option to get the unit to reboot without upgrading I am all ears, because as I have said I would love to get a bit more life out of this fantastic HDX hardware.
Click to expand...
Click to collapse
Hi did you ever manage to find a way to bring it back, my HDX has just done the same thing today.
Another Fire HDX 3rd gen. Stock FireOS have same issue today. Still looking for answer...
aedahh said:
Another Fire HDX 3rd gen. Stock FireOS have same issue today. Still looking for answer...
Click to expand...
Click to collapse
Unfortunately, no solution if you can't connect via ADB. Tough loss ...
I just want to start off by saying that I don't know too much about rooting or much of Android/Amazon OS in general. I have had my (Apollo) Fire HDX 8.9" since March 2, 2013. I have side-loaded apps and I am just a typical user. I know how to modify applications and such, so I know a bit but probably not as much as I should. I'm up-to-date with a lot of tech, but not all the rooting stuff. Anyway... Last night (November 25, 2015) I decided that I wanted to root. I started by finding some important info, specifically from this forum. (http://forum.xda-developers.com/kindle-fire-hdx/general/rollback-13-3-2-8-rollback-ota-captured-t3046204) So being as lazy as I am I did as much as I could without my computer and got 14.3.2.8 up and running over night. When I woke up I started the setup and enabled the wifi just quick enough to get ES File Manager. I got it installed successfully with no problems and turned off the wifi. After that I didn't really understand the OTA thing and TBH I still don't. I am assuming that is what updates my Kindle automatically. Anyway I just ignored that and moved on to my next step, installing 14.4.5.2. (Which I did on my computer.) After realizing my internet was really slow I decided to go reset the modem. Doing this messed up the modem and it kept going into "Limited mode". I had an idea that it could just be my Ethernet cable so to check that I turned my Kindle's wifi to see if I could connect through wireless. It still didn't work so I just decided to get ready for the day. This was around 11 AM (MST)(Thanksgiving 2015). When I am all done getting ready I go check my computer to see if my wifi is working, and it was finally working. So I go grab my Kindle, but now it wont turn on at all. I am assuming that this is a hard brick. I am still on 14.3.2.8 (I'm guessing that there is still stuff on my Kindle) and have no root and never did turn on developer options. When I connect it to my computer it takes a second and then say that it is unrecognizable. I am aware of "Restore2Stock", but I want to know if there are any other options. I don't want to spend $20 on a service that I don't necessarily trust. Anyone able to help???
My original post was a reply on a different thread. (http://forum.xda-developers.com/kindle-fire-hdx/help/help-thread-question-noob-friendly-t3206752/page11#post64025036)
DiaperBandit said:
I just want to start off by saying that I don't know too much about rooting or much of Android/Amazon OS in general. I have had my (Apollo) Fire HDX 8.9" since March 2, 2013. I have side-loaded apps and I am just a typical user. I know how to modify applications and such, so I know a bit but probably not as much as I should. I'm up-to-date with a lot of tech, but not all the rooting stuff. Anyway... Last night (November 25, 2015) I decided that I wanted to root. I started by finding some important info, specifically from this forum. (http://forum.xda-developers.com/kin...lback-13-3-2-8-rollback-ota-captured-t3046204) So being as lazy as I am I did as much as I could without my computer and got 14.3.2.8 up and running over night. When I woke up I started the setup and enabled the wifi just quick enough to get ES File Manager. I got it installed successfully with no problems and turned off the wifi. After that I didn't really understand the OTA thing and TBH I still don't. I am assuming that is what updates my Kindle automatically. Anyway I just ignored that and moved on to my next step, installing 14.4.5.2. (Which I did on my computer.) After realizing my internet was really slow I decided to go reset the modem. Doing this messed up the modem and it kept going into "Limited mode". I had an idea that it could just be my Ethernet cable so to check that I turned my Kindle's wifi to see if I could connect through wireless. It still didn't work so I just decided to get ready for the day. This was around 11 AM (MST)(Thanksgiving 2015). When I am all done getting ready I go check my computer to see if my wifi is working, and it was finally working. So I go grab my Kindle, but now it wont turn on at all. I am assuming that this is a hard brick. I am still on 14.3.2.8 (I'm guessing that there is still stuff on my Kindle) and have no root and never did turn on developer options. When I connect it to my computer it takes a second and then say that it is unrecognizable. I am aware of "Restore2Stock", but I want to know if there are any other options. I don't want to spend $20 on a service that I don't necessarily trust. Anyone able to help???
My original post was a reply on a different thread. (http://forum.xda-developers.com/kin...on-noob-friendly-t3206752/page11#post64025036)
Click to expand...
Click to collapse
As you probably realize your device is toast. Leaving WiFi enabled resulted in receiving an incompatible OTA (over the air) update from Amazon. There is no recovery.
Davey126 said:
As you probably realize your device is toast. Leaving WiFi enabled resulted in receiving an incompatible OTA (over the air) update from Amazon. There is no recovery.
Click to expand...
Click to collapse
So is there anything that I can do with my $300 tablet now called a brick? Can I call support and see of they can do something? I'm sad and I realize that it is my fault but I'm pretty over the top that my tablet now has a worth of a dime. I would expect there to be some sort of company that would buy my "brick". Like a junkyard for disfunctional devices. My guess it that there is not a single thing in the entire world that can fix this.
DiaperBandit said:
So is there anything that I can do with my $300 tablet now called a brick? Can I call support and see of they can do something? I'm sad and I realize that it is my fault but I'm pretty over the top that my tablet now has a worth of a dime. I would expect there to be some sort of company that would buy my "brick". Like a junkyard for disfunctional devices. My guess it that there is not a single thing in the entire world that can fix this.
Click to expand...
Click to collapse
Check eBay or similar auction sites to get an idea what your device is worth (very little) in its current state. To my knowledge there is no company that refurbishes bricked Kindles (at least HDX models) and no one on XDA has figured out how to resurrect crippled devices. Sorry for your loss.
Davey126 said:
Check eBay or similar auction sites to get an idea what your device is worth (very little) in its current state. To my knowledge there is no company that refurbishes bricked Kindles (at least HDX models) and no one on XDA has figured out how to resurrect crippled devices. Sorry for your loss.
Click to expand...
Click to collapse
Thanks for the help. I'll see how much I can get.
I'm in a position equal to his own , I have nuna 3rd kindle fire and think that just left on the wifi was going to be the tablet is useless crap ..
Friend anything that might serve to regain our fire I notice , just hope you do the same , never give that friend to relive our Kindle
I just replaced the motherboard in mine. The 16gb board I bought was $36
I just ordered a daughter board also. I must have damaged it also when I was messing with it.
I took the daughterboard out of my wife's to test just to make sure.
Daughterboard was $14
Bought both from ifixit but they are out of motherboards.
Google them and you should be able to find one.
Be patient removing the display from the back frame.
Just posted a thread with a link for motherboards.
Sent from my SM-N920T using Tapatalk
donharden2002 said:
I just replaced the motherboard in mine. The 16gb board I bought was $36
I just ordered a daughter board also. I must have damaged it also when I was messing with it.
I took the daughterboard out of my wife's to test just to make sure.
Daughterboard was $14
Bought both from ifixit but they are out of motherboards.
Google them and you should be able to find one.
Be patient removing the display from the back frame.
Just posted a thread with a link for motherboards.
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Good stuff! Offers some hope for those with bricked devices (especially pricey Apollo/Saturns) and moderate skills in electronics disassembly/repair. At present there are few viable alternatives to the outstanding display and unique form factor of the HDX line. Thanks for sharing.
OkGreetings, fellow enthusiasts I would like to know if it's possible to turn off auto updates from Amazon with out root? I would like to connect my tablet to my Wi-Fi but I don't want my current build to be updated due to I'm waiting for root to come around. Im only talking about the updates to the Fire OS.
Can you provide more details?
Yes I can. Let me start from the beginning. I had the firmware 5.1.2 originally I having used the device and been collecting dust got it on black Friday deal so it was uber cheap. I hate Fire OS so I figured I'll try to root it. Well I plugged it let it charged for awhile turned it on then put it to sleep. It updated to firmware 5.3.3 the newst installment without asking. So I read you can downgrade the device by using adb sideload then the firmware you provided witch was 5.1.2. It complete the download and said on the device it successfully completed the task when back to the recovery menu. Tried to reboot the device and it became a hard brick. It doesn't respond to any buttons or holding or down volume and power. It doesn't even show the battery icon thing when you plug it in. I used my phone charger so I know it's the device not the cord or charger. I hope this helps clear things up a bit. Hopefully helps find a way to in brick it.