Hello, just to start out I’m not really familiar with Kindles or Android devices in general despite owning one for a few months now. A few days ago I decided to root it, and after much struggle and attempts I finally got it working. Afterwards I first got rid of the Ads, IMDB, and Cloud9 app since they were a waste of space or in the way.
Since then however I ran into a different problem. I can’t seem to open any of my books that I sideloaded onto my Kindle HD. They’re in mobi format and they show up in the books tab but whenever I click them all that happens is the picture that’s now gone after my last restart gets big like it’s about to open and then after about twenty seconds it just returns to the home screen.
I believe I deleted the wrong app in the process of trying to get rid of the bloat on the device so I tried to install Kindle from the store. The App doesn't show up but it’s installed, however it’s still not working.
Is there any way to fix this problem without doing a factory reset? If that would even fix my problem that is.
Any and all help is much appreciated.
I'd also like to add in that I have tried moving the files from the Books folder to the kindle folder and vice-versa with no luck either way.
I had whatever, that updated to 7.3 as soon as I turned it on. Rooted fine with KF First Aide. Installed ES File Explorer, Google Play, etc. All was well. Then I read a post here how hard it was to copy/paste with ES File Explorer. I was joking about it with my husband and showing him how easy it was and copied random file... literally just randomly long pressed a file to show him the options, picked copy, and then went to another directory and *meant* to point to but touched paste instead... it was one of the Google Play files.
Kindle fire hd 7" immediately started freaking out. A mac address type error flashing so quick I couldn't do anything else. It was the same low letters and numbers you'd get with a mac address but said error and just an OK button which did nothing when you manage to tap in while flashing. Restarted, thinking if I was lucky Google Play just would't work... got the red triangle and neither option helped. So I ordered one of SkOrPn's cables which works flawlessly and boots right into fastboot. Yay for SkOrPn! Not so ya for me... (not their fault!).
It shows up as "Tate-PVT-08". I've tried every variation of driver I can find. Uninstalling all old things I can find, complete with the command line command to show ghost hubs/devices and what not and removing them and shut down/start up fresh too... no joy. Also removing and restarting between each driver try... neither of the Amazon drivers work for fastboot for me. I've tried so many things at this point my brain is fried.
So I'm hoping someone can help direct me how to fix this. . I won it in an online giveaway, so I'm not out anything, but it'd sure be nice to use it! As messed up as the Kindle crap is I'd be pissed if I bought it... but I'm majorly spoiled on Sony (Ericsson) and their "ya, play with it, screw it up, we don't care, here's how to fix it online just plug it in"... even before they had the online thing they'd let you send it back (and paid shipping both ways for it!) would reflash firmware and send it back with paper ticket that said "No problems found" lol... even on a device you actually bricked (wouldn't turn on... not the cute "brick"="I screwed it up but it's fixable" that people use now).
Any help or advice would be greatly appreciated. Especially if you could steer me to drivers that work for 2nd generation HD 7 inch in fastboot on Windows 8. Thanks for reading if nothing else!
Try The SoupKit found here.
This is a Kinology HD using XDA Premium
Swap cables. Boot with the factory cable then switch to a normal one.
Thanks for the reply, but I've been doing that. Great advice for anyone who doesn't know though!
You couldn't have damaged anything by just copying a file unless either:
You cut the file
OR
You overwrote a system file
OR
You filled up your system partition.
If you still need help, I might be able to do some researching.
Sent From my Kindle Fire HD running CM10.1
I'd say your fast boot driver didn't install right mine showed up like that and I had to keep playing with drivers to get it to work
Sent from my Amazon Kindle Fire HD running CM 10.1
Same Problem
I'm having the same problem! If you fixed it please let me know!
FIXED!!
It's fixed! You have to use KindleFireAide. Just follow all of the directions and it's perfect.:laugh::laugh::laugh::good::good::good:
Shawnsch said:
I'd say your fast boot driver didn't install right mine showed up like that and I had to keep playing with drivers to get it to work
Sent from my Amazon Kindle Fire HD running CM 10.1
Click to expand...
Click to collapse
Thanks, I was hoping there was a better answer than just keep uninstalling/reinstalling various drivers in various ways til it works lol.
I've got a pc I haven't plugged it in to I'll try this weekend, if that doesn't work I'll do the Linux Soup Kit.
Deviantelf said:
Thanks, I was hoping there was a better answer than just keep uninstalling/reinstalling various drivers in various ways til it works lol.
I've got a pc I haven't plugged it in to I'll try this weekend, if that doesn't work I'll do the Linux Soup Kit.
Click to expand...
Click to collapse
Use Kindle Fire Aide. It comes with all of the drivers.
Geckodudes said:
Use Kindle Fire Aide. It comes with all of the drivers.
Click to expand...
Click to collapse
That was my first thing to try. Unfortunately one of them says stopped by user (preferred one) and the alternate won't install, gets to the end of installing and says didn't install, do manually... which has the same results. I'm getting the same results on another pc. Fun times lol.
Edit... I give up, it's Linux time. Will report back later.
My husband did the Soup kit (correct version, followed directions, etc.) with it for me while I was at work today on an pc he put Linux on (so nothing phone/tablet/adb/driver has ever touched it for anything). He's more savvy with Linux, I haven't used it much since the 90s while he regularly has it as a dual boot on his main pc. He used Ubuntu, followed the Soupkit directions and still no Linux love either.
I'm pretty much down to just sending it back, worst case they send it back and tell me I'm screwed. Both of us are so spoiled on Sony (me) and Google/Nexus (him)... that this some things only works sometimes and just keep bashing your head into the wall and something you already tried three times will work thing is out of our frame of reference (which is what it took to get it rooted lol). I've already spent more time trying to fix the stupid thing for something that shouldn't have even caused an issue than I've spent on both my Sonys combined... even though I've borked both more than once... crazy.
My only advice ... buy a real tablet lol. Luckily I won this so I'm not out anything if Amazon won't swap it... but I really like the 7" size for book reading.
I'll fix it for you...
Deviantelf said:
My husband did the Soup kit (correct version, followed directions, etc.) with it for me while I was at work today on an pc he put Linux on (so nothing phone/tablet/adb/driver has ever touched it for anything). He's more savvy with Linux, I haven't used it much since the 90s while he regularly has it as a dual boot on his main pc. He used Ubuntu, followed the Soupkit directions and still no Linux love either.
I'm pretty much down to just sending it back, worst case they send it back and tell me I'm screwed. Both of us are so spoiled on Sony (me) and Google/Nexus (him)... that this some things only works sometimes and just keep bashing your head into the wall and something you already tried three times will work thing is out of our frame of reference (which is what it took to get it rooted lol). I've already spent more time trying to fix the stupid thing for something that shouldn't have even caused an issue than I've spent on both my Sonys combined... even though I've borked both more than once... crazy.
My only advice ... buy a real tablet lol. Luckily I won this so I'm not out anything if Amazon won't swap it... but I really like the 7" size for book reading.
Click to expand...
Click to collapse
If you're gonna send it anywhere, if you pay for shipping I could try to fix it. No guarantees, of course.
If you are on Windows 8 to install kfhd drivers you must advanced boot with unsigned drivers install mode active
Sent from my KFTT using xda premium
KindleFireGuy said:
If you are on Windows 8 to install kfhd drivers you must advanced boot with unsigned drivers install mode active
Sent from my KFTT using xda premium
Click to expand...
Click to collapse
Ya did all that fun stuff, repeatedly with various drivers with all the 20 steps in between to remove others, lol.
Husband spent quite some time with Linux and SoupKit to no avail also. He could get his phone to work (making sure he had all the rules and steps correct), but it never would do anything with the tablet.
I gave up and called Amazon late Monday. They had me turn it on and verify the red triangle screen then sent me a new one that arrived today. Take the new one out of the box and put the old one in they said. They paid shipping both ways. If they complain I'll tell them send me the old and I'll send the new one back lol (at my expense). If they want to make the thing such a mess to deal with what do they expect? They know there's a whole group of people that won't live with the crappy launcher mess they have .
First of all it's working again so I'm not really looking for any help to get it running but still I thought this is worth mentioning
I wanted to import a .mobi book to Nexus 7. This book was sent to me by a friend and I wasn't completely sure what it was. Not even sure if a .mobi file could cause this. But here it goes:
I tried to import this ebook to Aldiko, turned out, it does not even find the file - so I've downloaded Moon Reader from Play Store which found the book and offered me to import it. While importing it the app froze and superuser showed me that "Shell" asked root permissions but was denied. Eventually the tablet itself froze. After a few minutes the message occured that Moon reader does not response and I chose to kill the app. Then the display turned black and the tablet seemed to have turned off.
After that point the tablet was not responsive anymore. No matter what I tried, it would not respond to anything. Battery was at 40% before but I connected it to the charger anyways. I've tried to boot up again and this time I got some disfigured weird glitches but nothing like a bootscreen. After some time it actually booted into Android (at that point it was an older PACman ROM). As soon as I've tried to unlock the screen the tablet made some weird noises (sounded like R2D2 ) and turned black again.
Again the only reaction to pressing the power button were some glitches...I left the device untouched for a few minutes and tried booting again, this time holding volume down button and it got me into download mode where I was able to choose recovery mode which then gave me the chance to restore a backup. After that it worked as if all the above never occured
However I've decided to flash cm10.2 nightly build then since I had my little issues with PACman on Nexus 4. Though I don't blame the ROM. But quite frankly I don't have the slightest idea why this happened, what caused it and what exactly this issue was.
So I just thought maybe someone encountered similar before and might be able to tell me, what all this was about.
Besides I've checked this .mobi file with virustotal.com and not one antivirus raised alarm. Still don't know what was inside that .mobi, but I don't really wanna try it on any other device
Anyone ever had this?
Good morning everyone. I have been a long time lurker. Thanks to the incredibly talented people on this forum, I was able to root my phone about 8 months ago. Now I hope that someone here can help me. About a month ago I experienced a screen glitch. I picked up my phone one day and it suddenly had a black bar across the screen along with scrambled pixels. I tried to reboot, got stuck in loop. So I booted into twrp and did a full restore. Everything was working fine for a fee days, then I started to notice things were wrong. I can no longer get Bluetooth or my mobile hotspot to turn on. I click the button in settings and the widgets on my homescreen. They will slide to on back be greyed out. They never turn on, in fact if unleavened one of the settings, the slider is off again when I return to it. App in my apk drawer all say app not installed when I try to uninstall them. Uninstalling them with lucky patcher, google play (for official apps) and the built in "Make more storage" in settings, is the only way to uninstall apps. The apps setting crashes when I try to uninstall through that. The only way to install 3rd party apk files is through lucky patcher. I have cleared cache files and data in apps that had it. Bluetooth widget app along with some other apps always show 0.00 data. When I try to open my data usage setting it informs me that there is no activity found for this action. Hardware test show that Bluetooth is fine, I am suspecting serious software failure. I have even tried a factory reset a few times to no avail. Thank you again for all of your hard work and I hope some of you will be able to guide me through at least some of my problem. Btw, I have not installed any custom roms. I had xposed a few weeks before my problems started. After realizing how much space it used up along with the tweaks, I decided to remove it. I am in no way saying that xposed is to blame, just stating that I had it installed at one point. One more thing, I have searched the forum and google, for solutions to individual issues. Tried all the things I read to do. I'm still on lollipop also. HTC sync doesn't recognize my phone as being connected either
Hey Guys,
I've got two Fire (5th Gen) 7in tablets, which are my kids. they're both completely stock, no Root at all running FireOS 5.3.2.1 and are exclusively used in the Fire for Kids app. They're kept in those huge foamy kids cases with handles and we've drummed into them that they should look after them well which they do.
However, both tablets have shown the same issue; When not in use for a couple of minutes they reboot themselves. After each reboot you can start using them fine, but after a few minutes of not being used they reboot again. So if not actively using the tablets, they will reboot continually until the battery dies.
Amazon has replaced both of these tablets. The replacements are doing the exact same thing. I suspected at this point is may be a problem with my account or profile so I factory reset and registered them on my Wife's amazon account, did not restore from backup, just had them fresh.... And the same problem happens.
Is there a known issue with 5.3.2.1?! Amazon have now processed another pair of replacements which I think is unnecessary, it seems like a software issue to me but they don't have any other suggestions. So I'm hoping some of the brains here may have seen it before!
The only idea I have left is that the "Expandable Storage" option suddenly became available around the time this started happening. Might be a coincidence but I've now factory reset one of them and removed the SD card to see if it makes any difference. Any other ideas guys?
Jay_uk1185 said:
Hey Guys,
I've got two Fire (5th Gen) 7in tablets, which are my kids. they're both completely stock, no Root at all running FireOS 5.3.2.1 and are exclusively used in the Fire for Kids app. They're kept in those huge foamy kids cases with handles and we've drummed into them that they should look after them well which they do.
However, both tablets have shown the same issue; When not in use for a couple of minutes they reboot themselves. After each reboot you can start using them fine, but after a few minutes of not being used they reboot again. So if not actively using the tablets, they will reboot continually until the battery dies.
Amazon has replaced both of these tablets. The replacements are doing the exact same thing. I suspected at this point is may be a problem with my account or profile so I factory reset and registered them on my Wife's amazon account, did not restore from backup, just had them fresh.... And the same problem happens.
Is there a known issue with 5.3.2.1?! Amazon have now processed another pair of replacements which I think is unnecessary, it seems like a software issue to me but they don't have any other suggestions. So I'm hoping some of the brains here may have seen it before!
The only idea I have left is that the "Expandable Storage" option suddenly became available around the time this started happening. Might be a coincidence but I've now factory reset one of them and removed the SD card to see if it makes any difference. Any other ideas guys?
Click to expand...
Click to collapse
It sounds like the devices may be trying to auto-update and failing for whatever reason. Pure speculation as I no longer run FireOS.