Yesterday afternoon, I took it upon myself to attempt a Kindle Fire root, which seemed to be successful. I had followed the instructions and I had even installed TWRP (At least, I think I did). I think was asked to reboot, and I did. Unfortunately, I am now met with a brick. All that is showing right now everytime I turn on the device is the "Kindle fire" logo all in white letters with the screen's brightness down. It does not go any further than that at all. I had tried to remedy the situation by using Unbrick tools, but anytime I clicked on "Stuck on Logo", I got the "error: device not found" message. I even tried to do the standard "Hold power button for 20 seconds", but that didn't work either.
All the rooting and TWRP flashing/installation was done with a regular Amazon USB cable. I didn't have a fastboot cable, so I made do with a regular one. Now it seems as though I might need to purchase one from Amazon. Although I had read somewhere online that someone was able to use an Xbox One Play and Charge Cable claiming that it works the same as a fastboot cable (can anyone confirm this, by the way?). Hopefully, my Kindle Fire HD can be saved with or without a fastboot cable.
No amount of Googling has gotten me very far at all. I would include a screenshot of what my Kindle Fire looks like when turned on, but I cannot due to being a new user. I may, however, be able to send a PM if requested.
Forgot to add. The model of my Kindle is the Kindle Fire HD 7 3rd Generation
UPDATE: Apparently, my computer can still kind of detect it. Whenever I have the device plugged into my computer and press the power button and volume down, I get a USB connection sound with a message "the last USB device you connected to the computer malfunctioned and Windows does not recognize it"
EDIT2: I think this might be in the wrong section.
Really? No help on this issue at all? That's sad, man.
Did you try to boot to the recovery?
If you can turn it off do so. Wait a few seconds and then press power and volume + button at the same time until it boots.
Does it boot to the recovery screen?
xSentinel said:
Did you try to boot to the recovery?
If you can turn it off do so. Wait a few seconds and then press power and volume + button at the same time until it boots.
Does it boot to the recovery screen?
Click to expand...
Click to collapse
Yes I have tried that, but that did not boot to recovery at all. The Kindle Fire is still stuck at the white Kindle Fire logo and won't go any further at all. It even shuts off probably because I am holding the power button.
I am running Windows 10 if that helps.
Windows 10 should not matter for this particular thing because I am talking about not being connected to your PC. If you are connected to the PC while doing this that could interfere with the process I would imagine, so do this while not connected.
I read in another post where a guy had similar freeze and had to press power first for a second then vol + and hold it for a long time. Eventually it came up.
Mine never had a white fire logo. Mine starts with a white amazon logo followed by colored/flashing fire logo. From what I have read if you can make it to the colored fire logo you can save it. If you are stuck at the white amazon logo then it's worse.
But I have never read of a white fire logo. Mine is a 6 (4th gen) which could be the difference.
When mine screwed up I was stuck at colored fire logo (past white amazon logo). It took numerous resets but eventually I got back in.
Neither pressing and holding volume + or - seemed to help at all. Volume - seems to do at least something as the computer detects it for a split second. I'm not really sure what that is, though.
Even when not connected, I'm getting nowhere with this.
Okay, so further progress has been made, I think. I had left the Kindle off and held the Volume - button, then connected it to the computer. Lo and behold, I hear a USB Device connected sound with no error message in sight. I have no idea where to go from there.
EDIT: Saw error message. I spoke too soon.
DragonfireEX402 said:
Okay, so further progress has been made, I think. I had left the Kindle off and held the Volume - button, then connected it to the computer. Lo and behold, I hear a USB Device connected sound with no error message in sight. I have no idea where to go from there.
EDIT: Saw error message. I spoke too soon.
Click to expand...
Click to collapse
Sorry to say, you used a root guide for the 2014 Fire HD 6/7 on your 2013 Kindle Fire. Try posting here: http://forum.xda-developers.com/kin...p/help-thread-question-noob-friendly-t3206681 or (more people) at KFSOWI Modding on G+
DoLooper said:
Sorry to say, you used a root guide for the 2014 Fire HD 6/7 on your 2013 Kindle Fire. Try posting here: http://forum.xda-developers.com/kin...p/help-thread-question-noob-friendly-t3206681 or (more people) at KFSOWI Modding on G+
Click to expand...
Click to collapse
Actually, I didn't use a root guide for the 2014 Fire HD on my 2013 Kindle Fire. I actually followed a guide on a different website which I cannot find record of because Google Chrome's browsing history has a way of messing up.
Thanks for the link, by the way. Really helps.
Regrettably I can't help you. I have a 2014 HD 6, so I have no familiarity with your device. And on mine all I have done is rooted it and disabled practically all the Amazon stuff to try to make it the most android like that I could possibly get without bricking it.
I have not installed a different launcher.
I have not installed a custom ROM.
I have not installed TWRP (yet)
I have not install gapps (or any Google stuff at all)
I have not installed TWRP because, to me at least, the instructions posted here are very difficult to follow. After reading them numerous times I still don't get it. I'm not sure what to download, from where, what to run or how.
Also I don't know what value having TWRP would be for me because I have no desire to install gapps or any Google stuff. So, at this point at least, I have not had any need for TWRP yet. Other than installing Google stuff I have not needed TWRP.
I have not install gapps because I am trying to make this thing light and android like. It seems to me that taking off a ton of Amazon stuff just to replace it with a ton of Google stuff defeats my personal purpose with this tablet. I have all the apps I need or use downloaded directly from their sources so I don't need Google Play.
xSentinel said:
Regrettably I can't help you. I have a 2014 HD 6, so I have no familiarity with your device. And on mine all I have done is rooted it and disabled practically all the Amazon stuff to try to make it the most android like that I could possibly get without bricking it.
I have not installed a different launcher.
I have not installed a custom ROM.
I have not installed TWRP (yet)
I have not install gapps (or any Google stuff at all)
I have not installed TWRP because, to me at least, the instructions posted here are very difficult to follow. After reading them numerous times I still don't get it. I'm not sure what to download, from where, what to run or how.
Also I don't know what value having TWRP would be for me because I have no desire to install gapps or any Google stuff. So, at this point at least, I have not had any need for TWRP yet. Other than installing Google stuff I have not needed TWRP.
I have not install gapps because I am trying to make this thing light and android like. It seems to me that taking off a ton of Amazon stuff just to replace it with a ton of Google stuff defeats my personal purpose with this tablet. I have all the apps I need or use downloaded directly from their sources so I don't need Google Play.
Click to expand...
Click to collapse
The thread I've started is not in the appropriate section anyway, so don't feel any regret.
xSentinel said:
Windows 10 should not matter for this particular thing because I am talking about not being connected to your PC. If you are connected to the PC while doing this that could interfere with the process I would imagine, so do this while not connected.
I read in another post where a guy had similar freeze and had to press power first for a second then vol + and hold it for a long time. Eventually it came up.
Mine never had a white fire logo. Mine starts with a white amazon logo followed by colored/flashing fire logo. From what I have read if you can make it to the colored fire logo you can save it. If you are stuck at the white amazon logo then it's worse.
But I have never read of a white fire logo. Mine is a 6 (4th gen) which could be the difference.
When mine screwed up I was stuck at colored fire logo (past white amazon logo). It took numerous resets but eventually I got back in.
Click to expand...
Click to collapse
@xSentinel
how did you get it working again. currently I am stuck at the flashing fire logo and goes no where else. any help is appreciated.
Sorry for the delay.
Honestly I don't know exactly what specific thing I did, as I was panicking at the time and tried everything. First off I booted to the recovery screen. I tried clearing the cache partition and then rebooting. That did not appear to fix it as it still hung at the fire logo.
Next I tried every other option in the recovery list one by one except for reset and return to factory defaults. I did not want to do that yet and lose all I had gained so far.
Eventually I just set it down on the fire logo and walked away, figuring I needed a break and time to clear my head and contemplate my next move. Probably I also took some time to post in here and see if anyone had an answer. By the time I came back I saw it had booted up correctly and was working fine. So it is possible that all it needed was an inordinate amount of time to boot.
So sadly I can't say with any specificity what actual thing I did that did it or if it just fixed itself when I left it alone for a long time. I wish I could be more help.
favorite
I have a kindle fire hdx that I had fixed two weeks ago for a broken screen and broken charging port, (why you ask and why I didn't bother to get a new one is because this kindle has important files that I didn't put on my computer or printed out which was a mistake) anyway, it is finally fixed and it looks like it is working, except when I charged it, it was rebooting when all of a sudden it gave me a complete blue screen when it tried to go to the page where you put your password in. I tried restarting it for 30 seconds and now when it reboots, the opening before you enter the password where it has the words kindle fire twice font is blurry and scratchy looking. I really need those files as they are personally important to me. Is there anyone that can help?
After I charged it, the blue screen went away and it is stuck on booting up where the kindle fire logo appears and doesn't go past the screen where I can put in my password. I got close to where the screen changes from the logo to the screen where I can put my password but it freezes and reboots again.
I have a kindle fire hdx that I had fixed two weeks ago for a broken screen and broken charging port, (why you ask and why I didn't bother to get a new one is because this kindle has important files that I didn't put on my computer or printed out which was a mistake) anyway, it is finally fixed and it looks like it is working, except when I charged it, it was rebooting when all of a sudden it gave me a complete blue screen when it tried to go to the page where you put your password in. I tried restarting it for 30 seconds and now when it reboots, the opening before you enter the password where it has the words kindle fire twice font is blurry and scratchy looking. I really need those files as they are personally important to me. Is there anyone that can help?
After I charged it, the blue screen went away and it is stuck on booting up where the kindle fire logo appears and doesn't go past the screen where I can put in my password. I got close to where the screen changes from the logo to the screen where I can put my password but it freezes and reboots again
I have a Windows 10 PC and a Kindle Fire HDX 8.9 that I purchased about 2 years ago. Up until the past few days I was a very basic user. Just spotify, web browsing and some games. The most advanced things I did on it were install some apk files from the internet and make it so the screen was always on in the secret developer options menu. Up until Monday I had no intentions of rooting my tablet or doing any high level tech wizardry with it.
But the past few weeks I have been noticing significant performance decreases in my kindle. Apps crashing, screen freezing, slow performance. I didn't think much of it, I figured I just had too many terrible games on it. On Friday morning it crashed while I was using it and attempted to boot back up but with the [fastboot] text under the word amazon. It got stuck on this screen, restarting it just brought it back to this, attempting to hold the power button and the volume up button didn't appear to do anything either. Eventually after restarting it about 20 times it booted normal for whatever reason. After this it worked normal for another day and then it crashed again and booted with the [fastboot] text. I read up more on fastboot and various kindle fire issues and jammed restarts until it randomly worked again.
This time I when it was working I tried restoring it to factory default in case something I had done or added was the cause of these boot loops or whatever. I also went into developer options and turned on usb debugging since my reading made it seem like that was pretty necessary.
It crashed and restarted again Monday morning but it didn't get stuck in fastboot this time, it just got stuck on the word amazon. So I installed the various tools and drivers I have read about on here and I have been doing my best to try and make it work again. But as someone with zero experience with this sort of thing I have hit a wall.
When I first hooked it up last night I set the driver to the "adb interface driver", I got adb to see the device and I was able to execute some commands to it. I made it reboot just to see if I could, it still stopped at the word amazon, and then I went to sleep. Today I turned on my computer and adb will not find the device. Apparently something changed overnight and windows will now only see the device as a standard mtp usb device. I have attempted to force it to change with the "update drivers -> browse my computer -> let me pick from a list -> Have disk " line. But when I choose the kindle drivers or the adb drivers it tells me they are incompatible. Unplugging and plugging back in doesn't do anything. Restarting doesn't do anything. Attempting to uninstall the drivers doesn't do anything. I don't know what is left or how to fix this so I can proceed. And honestly even after I get through this road block I have no idea what I should do to try and make my tablet operational again. So I am in need of some guidance. Is there anyone out there that can show me the way or at least get adb to see my device again?
horgenblorg said:
I have a Windows 10 PC and a Kindle Fire HDX 8.9 that I purchased about 2 years ago. Up until the past few days I was a very basic user. Just spotify, web browsing and some games. The most advanced things I did on it were install some apk files from the internet and make it so the screen was always on in the secret developer options menu. Up until Monday I had no intentions of rooting my tablet or doing any high level tech wizardry with it.
But the past few weeks I have been noticing significant performance decreases in my kindle. Apps crashing, screen freezing, slow performance. I didn't think much of it, I figured I just had too many terrible games on it. On Friday morning it crashed while I was using it and attempted to boot back up but with the [fastboot] text under the word amazon. It got stuck on this screen, restarting it just brought it back to this, attempting to hold the power button and the volume up button didn't appear to do anything either. Eventually after restarting it about 20 times it booted normal for whatever reason. After this it worked normal for another day and then it crashed again and booted with the [fastboot] text. I read up more on fastboot and various kindle fire issues and jammed restarts until it randomly worked again.
This time I when it was working I tried restoring it to factory default in case something I had done or added was the cause of these boot loops or whatever. I also went into developer options and turned on usb debugging since my reading made it seem like that was pretty necessary.
It crashed and restarted again Monday morning but it didn't get stuck in fastboot this time, it just got stuck on the word amazon. So I installed the various tools and drivers I have read about on here and I have been doing my best to try and make it work again. But as someone with zero experience with this sort of thing I have hit a wall.
When I first hooked it up last night I set the driver to the "adb interface driver", I got adb to see the device and I was able to execute some commands to it. I made it reboot just to see if I could, it still stopped at the word amazon, and then I went to sleep. Today I turned on my computer and adb will not find the device. Apparently something changed overnight and windows will now only see the device as a standard mtp usb device. I have attempted to force it to change with the "update drivers -> browse my computer -> let me pick from a list -> Have disk " line. But when I choose the kindle drivers or the adb drivers it tells me they are incompatible. Unplugging and plugging back in doesn't do anything. Restarting doesn't do anything. Attempting to uninstall the drivers doesn't do anything. I don't know what is left or how to fix this so I can proceed. And honestly even after I get through this road block I have no idea what I should do to try and make my tablet operational again. So I am in need of some guidance. Is there anyone out there that can show me the way or at least get adb to see my device again?
Click to expand...
Click to collapse
The symptoms you describe suggest a hardware vs software problem. Guessing bad memory (or controller) given the random boot behavior. Unfortunately, there is little you can do to rectify the problem, even if software based, on an unrooted 4th gen HDX. ADB will not allow privileged access unless the device rooted.
Look on eBay for another motherboard. Might also want to grab a daughterboard as well.
Watch some teardown videos on YouTube. Everything applies to the 4th gen as it does from the 3rd gen as far as taking it apart.
In total you can fix it for around $65. That's with buying both boards which you possibly only need the motherboard.
Sent from my KFSAWI using Tapatalk
Evening all!
I managed to brick an Ulefone S10 Pro by trying to flash a rom onto it which ended in a brief error message and then the screen went black.
Since then, it wont boot up. There is just a black screen and it vibrates briefly as if it's starting up but then nothing, before repeating ad infinitum.
When I connect it to a computer, the computer makes the connection sound, then a few seconds later, the disconnection sound. Nothing is shown on the phone nor the PC at this time.
I have no clue what to do as it doesnt stay connected to the computer long enough to be recognised before disconnecting and nothing appears on the phone screen. Ive tried disconnecting the battery and connecting to the computer without it but the same thing happens
Haylp! :laugh:
Thanks
Why not simply contact Techbone? https://www.techbone.net/ask-a-question
jwoegerbauer said:
Why not simply contact Techbone?
Click to expand...
Click to collapse
Because I simply didn't know about them...
...but now i do...ta!
no joy there, site continually redirects.
Anyone else got any ideas?