I bougt a second hand bricked hdx 7'' yesterday before i read some topic show that the factory cable method is unavailable for hdx. When i try to plug it in with usb cable, nothing happens. Another try with factory cable, windows realize the device is HS-USB QDLoader 9008. I ask the previous owner and she said that she did nothing except download ebook and surf web with its original web browser. After 2 days, she stuck in the screen shows 2 lines : Reset kindle and factory reset "Your Kindle doesn't seem to be able to boot", she chose factory reset again 2 times but it stuck again. I think she absolutely didn't touch anything in system files and it also unroot too. The only reason i can imagine that the hdx was bricked because of unsuccessful OTA update.
I also cannot get any information about the version of stock FireOS . Is there any solution for my problem? I have to wait for it?
Related
Hey everyone. I'm in a very big issue right now. I've searched far and wide on the internet to try to find a solution to this, but to no avail. I was recently messing around in TWRP on my Kindle Fire HD 7", when all of a sudden I went to reboot it and then just a blank red screen. So obviously I have bricked it. I know how to run the recovery program to get it unbricked, no issue. I have bricked my Kindle before in the past and was able to easily fix it by running the Kindle restore recovery program. So now when I went to my PC to try and unbrick it, I get this message "One of the USB devices attached to this computer has malfunctioned, and Windows does not recognize it." So clearly the drivers aren't working. I went into the devices manager and located it under Universal Serial Bus Controllers as "Unknown Device." When I attempt to update the drivers, there is no Amazon option. I have tried uninstall and reinstalling the drivers countless times. I tried as many different driver sources as I possible could come across and nothing is working. I have used three different computers so far, and none are working. I do have a fastboot cable, which is what I'm using to do this. I can get my Kindle into fastboot but that still doesn't change the fact that the drivers aren't working. I have made a YouTube video about this. I will post the link to my video that I made so anyone can better understand this. I am desperate at this point, and I appreciate any help I can get.
EDIT: I can't post the link at this time since i'm "new and probably a spambot," so feel free to PM me and I'll provide the link.
I'm so sorry man the only advice I can give you is to try to flash a custom ROM over fastboot but that probably won't work you might be able to find a program that let's your computer find your device without it powered on or bricked. Sorry man also they are like 50 bucks on utube if worst comes to worst.
Do you think it has anything to do with something being broken internally? Because I have never had an issue with it not being recognized in fastboot.
Sent from my SM-G900V using XDA Free mobile app
I don't think so the same happened to me and I just flashed a custom ROM after a factory reset and that worked also did you enable adb before this happened? Because if you didn't, your going to have to toy with twrp until you can find a custom ROM you might have previously downloaded.
Yes, I always have adb enabled. But I can't even get into twrp. It's fully bricked, it just boots up to a blank red screen.
Sent from my SM-G900V using XDA Free mobile app
Ummmmm you could try sending it to amazon or a service on eBay that's kind of your last resort but still try to look for a fix I'll be looking around for a fix
Ok so about a month ago my tablet bricked because i was stupid and downloaded google play store apps off of the 1MobileApp Market, and i shut down my tablet and when i turned it back on later it went through the Red Triangle Recovery Loop
and i instanlty went online looking for help, and discovered i would need a Fastboot cable which i now have, however in many recovery solutions the ADB would not detect my device, and ive screwed with the drivers so much it doesn't even detect my device as a kindle, and i no longer have the kindle drivers, at this point don't even care if i have to recover the system i just want the data on it. and i checked dozens of other forums and threads for solutions none have helped......
My PC is Windows 7
My Kindle is a Kindle 7" HD
I do have a Fastboot cable
I Dont have the drivers for anything
I would like to simply retrieve the data on the device
ANY HELP, ANYYYY, WOULD BE APPECIATED! Thanks.
First go here and determine which model you have. (You keep refering to "kindle," but you posted in the Fire HD (4th gen) forum and fastboot cable doesn't work with Fire HD.) If you've got Fire HD, you're out of luck; contact Amazon for replacement. If you have 3rd gen, post in KFSOWI modding on G+. If 2nd gen, try here: http://forum.xda-developers.com/kindle-fire-hd
Hello,
I have a rooted Ematic EGS-102. Following some instructions to swap my internal sd with the external one (as the memory where the apps' data get downloaded to was only 500MBs), I believe I have typed something incorrectly inside the vold.fstab file, because after rebooting my tablet it's forever stuck on the logo screen. This is my first android tablet so please bear with me. The solution that comes to mind is to open the root files by some program on my PC and edit the vold.fstab file back (I even have a backed up version of it from a few weeks earlier), or even flash a new ROM. Now, the problem is, my computer cannot see my tablet when I connect it through USB. At all. Back before when the tablet was fine, I could use the USB to transfer files to and from my computer, but after I killed my tablet, my computer doesn't even make the sound which indicates that a USB device has been connected.
I have tried changing the USB cable and the port where I connect it to (never mind that the same cable and port work with other devices), to no avail. Having given up on the USB method working, I decided to follow some instructions on installing a custom ROM that has worked on EGS-004, and according to the one who posted that, would work on other variants such as EGS-102. Basically It was steps to installing the ROM from the external card through Recovery mode, which I followed thoroughly to no avail. The tablet still gets stuck on the "ematic" logo start screen.
I've noticed that in the Device Manager my tablet is displayed as "USB Device(VID_1f3a_PID_efe8)" with a yellow triangle mark indicating that it's not working properly (code 10). I tried searching that error code and trying all the solutions I found to no avail, including updating the driver (just refuses to update and keeps telling me that my driver is up to date.)
Sadly all the other methods that would have a decent shot at working (Root explorer on PC, android recovery program, even a flash EGS-004 firmware method on ematic's website) requires USB. I'm out of solutions, and unless I can get the USB to work somehow, or find out why the ROM method didn't work, my tablet would officially be dead. I'm utterly miserable that such a stupid mistake on my part ruined my tablet, and I have no way of buying another (broke student here) or returning it (out of warranty and I'm pretty sure I voided it anyway). I would absolutely appreciate any help, and thanks in advance.
Edit: It's stuck on logo screen, not a bootloop. I'm terribly sorry for this confusion, my head isn't straight right now.
Still haven't found a solution :/
I factory reset my kindle fire and I went through the setup and it started updating and when it was finished it went black. After I realized it was bricked I tried the unbrick tool but I couldn't get my kindle to stay connected to my computer for long enough to use it. Can anyone help me out?
Seanballer94 said:
I factory reset my kindle fire and I went through the setup and it started updating and when it was finished it went black. After I realized it was bricked I tried the unbrick tool but I couldn't get my kindle to stay connected to my computer for long enough to use it. Can anyone help me out?
Click to expand...
Click to collapse
This is how you unbrick ;
http://forum.xda-developers.com/fire-hd/development/unbrick-fire-hd-6-7-flashing-lollipop-t3405797
Don't rush it, take your time !
/reader.sh not working .. its just hang there .............
aamszia said:
/reader.sh not working .. its just hang there .............
Click to expand...
Click to collapse
I am running into the same issue. I had rooted the Fire 6 (4th gen) and it has SuperSU Installer on it still after I thought I had restored back to factory and this is preventing me from doing any updates. I also no longer have the recovery option (VolUp+Power), it just blinks and reboots so I don't even have TWRP. I tried following the restore process above using a Boot USB but the READER.SH does nothing. I read it was maybe the USB hardware in the computer so I've tried 5 different computers all with the same result, both with a regular USB cord and fastboot cord. READER.SH just does nothing and I have to CTRL+C out. I'd say try other computers to see if that works. Anyone have any idea why mine isn't working?
ccbst10 said:
I am running into the same issue. I had rooted the Fire 6 (4th gen) and it has SuperSU Installer on it still after I thought I had restored back to factory and this is preventing me from doing any updates. I also no longer have the recovery option (VolUp+Power), it just blinks and reboots so I don't even have TWRP. I tried following the restore process above using a Boot USB but the READER.SH does nothing. I read it was maybe the USB hardware in the computer so I've tried 5 different computers all with the same result, both with a regular USB cord and fastboot cord. READER.SH just does nothing and I have to CTRL+C out. I'd say try other computers to see if that works. Anyone have any idea why mine isn't working?
Click to expand...
Click to collapse
I know this is old, but so you have the all the drivers installed and showing up in your computer's device manager?
The unbrick process and iso posted do not work with the newer FireOS versions starting with FireOS 5.3.1. Ask me how I know besides that it is posted a the top of this thread: https://forum.xda-developers.com/fire-hd/development/unbrick-fire-hd-6-7-flashing-lollipop-t3405797
I have two bricked devices in my closet. Do not think there has been any movement on finding a way around it.
Last week Wednesday I went to do an update on my phone and it hard bricked on me. So, I brought it to my carrier and they said it is bricked and nothing we can do. Then I brought it to U Break I Fix and they said they never seen something as bricked as that phone.
So, I did some searching and found this thread https://forum.xda-developers.com/galaxy-s8/help/s8-g950u-hardbrick-t3668572. I tried it and only get "expecting sahara_end_transfer but found 0". Tried on a Vista computer in test mode and the integrity checks disabled with the same results. Then tried grounding one on the data pins and it fails right away.
Then I also tried using QFIL on a Win 10 Desktop and only ever get Sahara Error.
The phone is model SM-950UZKALRA.
When plug in it is seen as a Qualcomm 9008 device. In the Device Manager, it only shows up in COMS and Ports.
Thanks for all the help in advance,
Fishinfiend