OK so i have searched everywhere for days. Tried tons of kindle unlock/unbrick tools including the Kindle Fire Utility. I rooted my Kindle fire HD7 (no sd card slot) using kingroot and twrp. at some point i used a utility that also put SuperSU on it. Everything seemed successful and i rebooted several times tweaking other settings, when i was almost finished tweaking i tried to remove kingsroot and rebooted which put me into some kind of boot loot. I only see the white AMAZON (arrow under the word AMAZON) logo it only stays up for about 15 secs then goes black and starts over. All the unbrick tools i have tried either say can't find device and fail or say <waiting for device> and are never able to find it. I have installed new signed kindle device drives successfully, android SDK with kindle fire drivers and google usb drivers. Windows device manager does show an Other device (with accompanying ding dong sound) > MTX65xx Preloader for about 5 secs then it disappears, the kindle never shows up as a drive thou. I ordered and am using a Fastboot cable that i ordered from amazon as well as a samsung galaxy usb cable which seems to have no effect. Ive tried using it in usb 2.0 slot as well as 3.0 (which they say won't work) The cable is from Atomic Market (3ft Motorola Factory Cable unbrick Droid Xoom Fire).
I also tried loading linux Ubunto via USB and running all unbrick tools i could find, always the same result .. they can't find device or waiting for device.
Windows 7 and Windows 10 same problem
Does anyone know how to help me? every article or guide i find talks about the kindle Fire logo that is orange and white or blue and white i never see either anymore (mine used to be orange and white)with an animation or without. or a triangle... i have not read one article that talks about the white amazon logo.
Thank you,
Mnfire
You have tried holding Power and Volume-up buttons to see if you can boot to recovery? If that doesn't work, you are unrecoverably hard-bricked and just wearing yourself out trying methods designed for other devices:
* Fastboot cable doesn't work with Fire HD.
* There's no unbricking tool for the Fire HD
If still under warranty, contact Amazon for replacement. If not under warranty, used Fire HDs are going for as low as $30: http://www.amazon.com/gp/offer-list...iguration=all&mv_digital_storage_capacity=all
DoLooper said:
You have tried holding Power and Volume-up buttons to see if you can boot to recovery? If that doesn't work, you are unrecoverably hard-bricked and just wearing yourself out trying methods designed for other devices:
* Fastboot cable doesn't work with Fire HD.
* There's no unbricking tool for the Fire HD
If still under warranty, contact Amazon for replacement. If not under warranty, used Fire HDs are going for as low as $30: http://www.amazon.com/gp/offer-list...iguration=all&mv_digital_storage_capacity=all
Click to expand...
Click to collapse
Boss, are you sure the fastboot cable wont work with the fire HD 6 / 7 ?
if you are 100% sure of this I will stop right now looking for a way to fix mine, which is stuck at recovery.
yurais said:
Boss, are you sure the fastboot cable wont work with the fire HD 6 / 7 ?
if you are 100% sure of this I will stop right now looking for a way to fix mine, which is stuck at recovery.
Click to expand...
Click to collapse
100% sure. If you're stuck at OS 4 recovery (no adb sideload option), it can't be fixed.
DoLooper said:
100% sure. If you're stuck at OS 4 recovery (no adb sideload option), it can't be fixed.
Click to expand...
Click to collapse
Piggy backing on this thread, mine goes past the amazon then to the glowing fire logo. I do adb devices and its says it's offline. Can this be fixed?
Sent from my KFFOWI using Tapatalk
twinturbor said:
Piggy backing on this thread, mine goes past the amazon then to the glowing fire logo. I do adb devices and its says it's offline. Can this be fixed?
Click to expand...
Click to collapse
Doubt it. These devices are almost unfixable if you can't get to the OS, TWRP or OS 5 recovery. It's kind of weird that you get anything from adb devices mid-boot. Exact condition producing "offline" slips my mind atm, but I think it just means you're, uh, offline--not booted. You could see what device manager shows and search for offline.
DoLooper said:
100% sure. If you're stuck at OS 4 recovery (no adb sideload option), it can't be fixed.
Click to expand...
Click to collapse
dont wanna be a fly in the milk, but are you sure this procedure will not work:
http://www.ebay.com/gds/How-to-fix-or-root-Amazon-Kindle-Fire-HD-7-HD-8-9-/10000000176942274/g.html
they also say the hd6 and hd7 are the same thing
yurais said:
dont wanna be a fly in the milk, but are you sure this procedure will not work:
http://www.ebay.com/gds/How-to-fix-or-root-Amazon-Kindle-Fire-HD-7-HD-8-9-/10000000176942274/g.html
they also say the hd6 and hd7 are the same thing
Click to expand...
Click to collapse
Look, all I know is what little I know. You are welcome to try anything. Sometimes people strike luck! But why would want to use a procedure for a 2012 device that has fastboot capability on a 2014 device that doesn't? Believe me, I understand desperation (been there!), but I have yet to see anyone fix a Fire HD with a method designed for a different device.
This thread discussion seems to be hd7 not hd
Enviado desde mi One mediante Tapatalk
yurais said:
This thread discussion seems to be hd7 not hd
Click to expand...
Click to collapse
Problem is, there are 3 (4?) years of HD 7s and they're all HDs, right? :laugh: This thread, and forum, is for the 2014 Fire HD 6 and 7 tablets (4th gen). Pretty sure that the OP and everyone who's posted are using that device. But . . .
Anyone who's unsure what Amazon tablet they have, should check @sd_shadow's fine index here: http://forum.xda-developers.com/fire-hd/general/index-fire-hd-6-7-2014-t3206774
DoLooper said:
Problem is, there are 3 (4?) years of HD 7s and they're all HDs, right? :laugh: This thread, and forum, is for the 2014 Fire HD 6 and 7 tablets (4th gen). Pretty sure that the OP and everyone who's posted are using that device. But . . .
Anyone who's unsure what Amazon tablet they have, should check @sd_shadow's fine index here: http://forum.xda-developers.com/fire-hd/general/index-fire-hd-6-7-2014-t3206774
Click to expand...
Click to collapse
I give up...
I cant find anything for this tablet, model PW98VM, every time I think I found something then something sends me ages back again, I cant with this.
same problem here!. i bricked my device. i disassembly the battery and i connected to my pc. mtk65xx not disappearing anymore!
pls dont give up we can do it!
I gave up, returned the tablet to customer. Never found driver for that preloader
Enviado desde mi SM-N920T mediante Tapatalk
---------- Post added at 01:43 PM ---------- Previous post was at 01:42 PM ----------
Try to manually force soccer installation with android mtk drivers.
Enviado desde mi SM-N920T mediante Tapatalk
Related
Hi everyone my kindle hdx7 is bricked several day ago.
First my kindle is shown stuck on grey kindle fire logo connect normal data cable
So i decide connect factory cable however, my kindle is shown black screen.
Nothing any logo but my laptop recognized Qhsusb_bulk.
I read gssole and follow his step but my kindle still brick anyone solve this problem?
Hehelp.me plz
Hello
cjdfyd2 said:
Hi everyone my kindle hdx7 is bricked several day ago.
First my kindle is shown stuck on grey kindle fire logo connect normal data cable
So i decide connect factory cable however, my kindle is shown black screen.
Nothing any logo but my laptop recognized Qhsusb_bulk.
I read gssole and follow his step but my kindle still brick anyone solve this problem?
Hehelp.me plz
Click to expand...
Click to collapse
Hi
I have the same problem, and I am in exactly the same situation as you, having got the factory cable from Amazon just today. unlike the other kindles, it doesn't appear with the yellow triangle, but its a big step since your PC recognises the kindle. Now all you really need is a unbrick utlity, but I haven't found one yet, I'll write to you as soon as i sort something out with my kindle so you can do exact same thing on yours.
---------- Post added at 12:11 PM ---------- Previous post was at 12:01 PM ----------
http://forum.xda-developers.com/showthread.php?t=2553474
ferrouskid said:
Hi
I have the same problem, and I am in exactly the same situation as you, having got the factory cable from Amazon just today. unlike the other kindles, it doesn't appear with the yellow triangle, but its a big step since your PC recognises the kindle. Now all you really need is a unbrick utlity, but I haven't found one yet, I'll write to you as soon as i sort something out with my kindle so you can do exact same thing on yours.
---------- Post added at 12:11 PM ---------- Previous post was at 12:01 PM ----------
http://forum.xda-developers.com/showthread.php?t=2553474
Click to expand...
Click to collapse
Hello
Can you get fastboot ultility to recognise your kindle? If it can,you can do a factory reset, by putting in the following command.
"fastboot -w -i 0x1949".
This is thanks to r3pawn.
Lets hope we goet somewhere.
cjdfyd2 said:
Hi everyone my kindle hdx7 is bricked several day ago.
First my kindle is shown stuck on grey kindle fire logo connect normal data cable
So i decide connect factory cable however, my kindle is shown black screen.
Nothing any logo but my laptop recognized Qhsusb_bulk.
I read gssole and follow his step but my kindle still brick anyone solve this problem?
Hehelp.me plz
Click to expand...
Click to collapse
Hard to say anything since there is no magic fix. Fixes are based on what you broke & your post gives no indication of what you did when you "bricked" it. Until I know what you did, I can not tell you what may, or may not, work.
Similar situation
Although I had Safe Strap, SU and etc. installed on my rooted HDX 7", I panicked when my firewall failed to block the 13.3.2.1 update and cut the power off in mid update. Unfortunate reflex that led to a soft brick. Although I now can get into Fastboot no problem (I can't access the ADB commands though), I have tried to flash recoveries, boot images and so on. I can erase data (I'd call myself an expert at this part of the rooting process) and arrange file system layouts but then can't get past this error:
FAIL: flashing not allowed for locked hw.
Anyone know how to, maybe change permissions on the hardware or whatnot to get the device to let me write to the system partition? I'm flashing from a iMac btw.
I mean the Christmas colors of the text as far as what worked and what didn't are fun to look at, but the actual loading of the Kindle OS might provide more long term visual excitement. Thanks and love all y'all's insights into navigating the treacherous waters of root access and tweaking the twerkinator in these here twandroids.
----
EDIT: I can use the ./adb commands but I was having trouble before with the period-less version. Was still getting no device to show up when I query adb but got this through fastboot:
fastboot -i 0x1949 devices -l
(serial number) fast boot usb:FA130000
Redaction is mine ...
qhsusb_bulk
So...
My Kindle Fire HDX is in the same boat... Honestly, not sure what happened. I had rolled back to 3.2.8, installed Saftstrap, SU, thought that I had disabled the OTA update but only by renaming the file. I was rooted and flashed ggow's Nexus mod on the ROM SLOT 1 and left the stock alone. It was working fine, never tried to update anything that night. Was plugged in and connected and booted to the Nexus side. The next morning I was showing someone how I could switch to the Amazon side through Safestrap and still had no issues. I set the Kindle on my desk at work and looked over to see it at the Kindle Fire logo and below it a progress bar saying Installing System Update! What I don't understand is I had not connected to the WiFi at work. The Kindle was wiped out and did not have the WiFi passwords nor did I accept the WiFi policy when connecting.
I had a couple of file on the SD card that I had transferred via the USB cable on the SD portion of the Kindle. The nexus mod .zip file and a copy of the renamed OTA update file that I had changed the name and extension on. Did it somehow recognize the .zip nexus file as an update and try to load it?? I am lost...
I am able to plug it into the computer and was getting the qhsusb_bulk as the device type. I have tried to access that through adb but it doesn't find it.
Amazon was kind enough to offer me a refurbished kindle for $149. I said I can buy a new HD7 for $99!? So... I have just over a year old 64gb HDX staring at me... asking me why I messed with it. Good question...
If anyone has any advice or possible solution, that would be great!
Thanks
I think I know what was happening. The I am not sure the rename to block ota does work on 3.2.8. I know it is not supposed to be able to update at all, but obviously it seems like it can. Odd.
Sent from my KFTHWI using Tapatalk
I installed twrp on my kindle 8.9, then i installed a couple of roms onto it. It worked just perfect. That until i got bored of the CM and i wanted to get back to the original OS. I followed the instructions on this site : //androidcowboy.com/2013/06/how-to-return-kindle-fire-hd-to-stock// , and then it got stuck to the static white/orange boot screen. I tried several restore softwares like kfhd, kffa, kindle unbrick, utilities and then i got the redscreen. After that i searched the internet and everyone adviced me to use either the kfhd uility or the kffa, and then BOOM, the device won't turn on.
I read that i could do the shorting trick, but nobody tried that. Is my kindle bricked for good, or do I still have any hope?
Have you tried holding the power button down for 30 seconds, releasing, then trying to boot?
Sent from my KFAPWI using xda app-developers app
MoisoiuMihai said:
I installed twrp on my kindle 8.9, then i installed a couple of roms onto it. It worked just perfect. That until i got bored of the CM and i wanted to get back to the original OS. I followed the instructions on this site : //androidcowboy.com/2013/06/how-to-return-kindle-fire-hd-to-stock// , and then it got stuck to the static white/orange boot screen. I tried several restore softwares like kfhd, kffa, kindle unbrick, utilities and then i got the redscreen. After that i searched the internet and everyone adviced me to use either the kfhd uility or the kffa, and then BOOM, the device won't turn on.
I read that i could do the shorting trick, but nobody tried that. Is my kindle bricked for good, or do I still have any hope?
Click to expand...
Click to collapse
First & foremost, you say you did this on a "Kindle Fire HD 8.9". Is this correct? If so, you are in the WRONG forum. This is for the NEW Kindle model, called the HDX.
If you do something for the HDX on the HD you will likely make the situation much worse. If you truly are on the OLDER Kindle Fire HD, then you can ALMOST ALWAYS recover using fastboot, but that will require either buying or making a factory fastboot cable.
GSLEON3 said:
First & foremost, you say you did this on a "Kindle Fire HD 8.9". Is this correct? If so, you are in the WRONG forum. This is for the NEW Kindle model, called the HDX.
If you do something for the HDX on the HD you will likely make the situation much worse. If you truly are on the OLDER Kindle Fire HD, then you can ALMOST ALWAYS recover using fastboot, but that will require either buying or making a factory fastboot cable.
Click to expand...
Click to collapse
Yes, i have the 8.9 hd model not the hdx. I tried holding the power button for 30 sec/ 1min , but it didn't work. And i don't know if any recovery/fastboot cable could help me, the device won't even turn on. Also, im sorry for misplacing this thread, but by any chance, does anyone know what should i start with? Maybe an older thread or anything.
MoisoiuMihai said:
Yes, i have the 8.9 hd model not the hdx. I tried holding the power button for 30 sec/ 1min , but it didn't work. And i don't know if any recovery/fastboot cable could help me, the device won't even turn on. Also, im sorry for misplacing this thread, but by any chance, does anyone know what should i start with? Maybe an older thread or anything.
Click to expand...
Click to collapse
Here is where you should start. http://forum.xda-developers.com/kindle-fire-hd
As I have BOTH the HD 8.9 & the HDX 8.9, I can tell you that a factory fastboot cable would likely work. It allows you to flash over adb, like other normal Android devices. At any rate, there are several threads & tools available in the forums I linked above that should help to get you going again.
Hi everyone,
I bought HDX 7 just 2 months ago. I was on 4.5.2 and last week i requested amazon to downgrade my device and they allowed me to downgrade to 3.2.8. Then I rooted it using Towelroot and used Safestrap bootloader to install Nexus 2.0.3 ( For Kindle Device).After completion of Installation of Nexus ROM (ZIP file) from safestrap, device restarted and just hanged on some NEXUS logo and could not start up. But after some manual force restarts the safestrap was replaced by normal Kindle bootloader and finally NEXUS 2.0.3 was able to load. But i could not use some Google apps therefore In order to install Gapps I tried to flash TWRP 2.3.3.0 with Flashify i bricked the device. The device just hangs on KINDLE FIRE logo and dont show any response to PC and cant be able to move in Fastboot mode or bootloader mode.
Is there any thing i could do at this moment or should i ask amazon for replacement?
Thanks !!!
marshhhh said:
Hi everyone,
I bought HDX 7 just 2 months ago. I was on 4.5.2 and last week i requested amazon to downgrade my device and they allowed me to downgrade to 3.2.8. Then I rooted it using Towelroot and used Safestrap bootloader to install Nexus 2.0.3 ( For Kindle Device).After completion of Installation of Nexus ROM (ZIP file) from safestrap, device restarted and just hanged on some NEXUS logo and could not start up. But after some manual force restarts the safestrap was replaced by normal Kindle bootloader and finally NEXUS 2.0.3 was able to load. But i could not use some Google apps therefore In order to install Gapps I tried to flash TWRP 2.3.3.0 with Flashify i bricked the device. The device just hangs on KINDLE FIRE logo and dont show any response to PC and cant be able to move in Fastboot mode or bootloader mode.
Is there any thing i could do at this moment or should i ask amazon for replacement?
Thanks !!!
Click to expand...
Click to collapse
Yeah, HDX is a finicky device. Looks like you may have skipped a few critical prerequisites (eg: NEXUS 2.0.3 not guaranteed to run w/Safestrap; TWRP is not compatible with 3.2.8) but that's water under the bridge. Flashing stock recovery is your first step IMHO but if you can't see your device via tether then you are pretty much hosed.
Should you seek a replacement Amazon will likely provide a refurbished unit given you are outside the 30-day return window. There have been reports of refurbished units coming with older firmware that that can be exploited (bootloader unlock) which will permit TWRP, Nexus and other ROMs to be installed. You'll need to do some reading to explore your options.
Davey126 said:
Yeah, HDX is a finicky device. Looks like you may have skipped a few critical prerequisites (eg: NEXUS 2.0.3 not guaranteed to run w/Safestrap; TWRP is not compatible with 3.2.8) but that's water under the bridge. Flashing stock recovery is your first step IMHO but if you can't see your device via tether then you are pretty much hosed.
Should you seek a replacement Amazon will likely provide a refurbished unit given you are outside the 30-day return window. There have been reports of refurbished units coming with older firmware that that can be exploited (bootloader unlock) which will permit TWRP, Nexus and other ROMs to be installed. You'll need to do some reading to explore your options.
Click to expand...
Click to collapse
Ja, its true because of more excitation and some laziness i escaped some important things to know. Anyway learned something.
I just called amazon and the conversation was like this.
Me: My device hanged on Kindle fire logo. what shall i do?
Amazon: since when ?
Me: Yesterday
Amazon: is that device rooted?
Me: No
Amazon: But I can see that it was rooted using some apps. and you asked for downgrade 2 days ago.
Me: I tried but i was not able to do so, But i had this problem when i did factory reset. ( It was a lie )
Amazon: Ok. Did you drop the device or was it in water before you had this problem.
Me: No No
Amazon: Ok then it should be defect. so send it to us. Thanks
But I am not sure whether they will replace it.
Amazon (at least in the US) will likely make some type of accommodation to keep you happy; they are good that way. Keep us posted!
marshhhh said:
Ja, its true because of more excitation and some laziness i escaped some important things to know. Anyway learned something.
I just called amazon and the conversation was like this.
Me: My device hanged on Kindle fire logo. what shall i do?
Amazon: since when ?
Me: Yesterday
Amazon: is that device rooted?
Me: No
Amazon: But I can see that it was rooted using some apps. and you asked for downgrade 2 days ago.
Me: I tried but i was not able to do so, But i had this problem when i did factory reset. ( It was a lie )
Amazon: Ok. Did you drop the device or was it in water before you had this problem.
Me: No No
Amazon: Ok then it should be defect. so send it to us. Thanks
But I am not sure whether they will replace it.
Click to expand...
Click to collapse
Davey126 said:
Amazon (at least in the US) will likely make some type of accommodation to keep you happy; they are good that way. Keep us posted!
Click to expand...
Click to collapse
Ya, i just got a mail from amazon and it says that my new device will be in front of my door in 3 days. Actually amazon are willing to have a good relationship with their customers. Impressive...
I used the almighty wipe feature of safesortrap and now i have no zips on the device, no way to put them on it, i tried adb push, sideload,etc. i do have a fastboot cable, although when it is plugged in to the fastboot cable, it wont turn on at all. my computer recognizes it as an unknown
device in safestrap, troubleshooting doesnt work. I have the OS I need, I just need a way of getting it onto the device. Any help is greatly appreciated! c: NOTE: 3rd gen kindle fire hdx 7. Also, is it possible when it is unbricked to unlock the bootloader in this situation?
Depends on the Fire OS version you had installed. Only versions below x.3.2.4 are unlockable (i.e. 3.2.3.2 or lower). Note that you can NOT downgrade below 3.2.8 once 3.2.8 or higher have been installed! Attempt would brick the device, thanks to rollback protection by amazon.
Which Safestrap version do you have installed, and what did you wipe?
Cl4ncy said:
Depends on the Fire OS version you had installed. Only versions below x.3.2.4 are unlockable (i.e. 3.2.3.2 or lower). Note that you can NOT downgrade below 3.2.8 once 3.2.8 or higher have been installed! Attempt would brick the device, thanks to rollback protection by amazon.
Which Safestrap version do you have installed, and what did you wipe?
Click to expand...
Click to collapse
I have Safestrap v4.01 and i wiped dalvik,data,cache, and system(im an idiot, i know lol). I had 4.5.2 installed, so no BL unlock.
InfiniteSpace said:
I have Safestrap v4.01 and i wiped dalvik,data,cache, and system(im an idiot, i know lol). I had 4.5.2 installed, so no BL unlock.
Click to expand...
Click to collapse
Don't be so quick, Safestrap v4 has a built-in System-wipe-protection, could've helped here.
Stay away from amazon's stock recovery! Using it with Safestrap installed will brick the device!
Try to get adb access, I think there's a thread somewhere here where a user was able to get access and to revive the HDX. May be the PDA drivers help regarding that. If not, try the original amazon drivers again.
Also try different USB cables, the HDX is surprisingly picky regarding cables. Fastboot cables won't work anyway btw.
You mean the PDANET drivers?
Nvm found it, trying this
I have adb access, i think it was the cable and im a noob, thank you for your time!
Kindle Fire THOR Black Screen wont connect to ADB
Okay so long long story short- my daughter has a kindle fire HD 7 inch version 3rd generation tablet. I did root it a while back and thought I had disabled the updates. However she accidentally so how allowed the updates and duringt the process it went black screen and wont boot or do anything at all. I have read countless forums and tried almost all the un-bricking tools out there as well as the commands in ADB. Currently what I have concluded is that the tools and typical un-bricking methods wont work since the tablet will not power on it wont connect to the computer in ADB mode and I have no idea if its in USB debugging mode at this time.
It will sorta power on (screen still blank- by holding the power button for 20 secs) and the computer "senses" it but at that point it will not be recognized by the PC, and give the error that the "USB device has malfunctioned". I have tried about everything out there- can you guys help me out to get the power back on at least where I can get the ADB to recognize the device? Thanks in advance.
Oh- I did purchase a fastboot cable as well but that did not help matters at all.....
Amazon: "3ft Fastboot Factory Cable For Motorola Unbrick Droid Xoom Fire by Atomic Market"
Athruz
Athruz said:
Okay so long long story short- my daughter has a kindle fire HD 7 inch version 3rd generation tablet. I did root it a while back and thought I had disabled the updates. However she accidentally so how allowed the updates and duringt the process it went black screen and wont boot or do anything at all. I have read countless forums and tried almost all the un-bricking tools out there as well as the commands in ADB. Currently what I have concluded is that the tools and typical un-bricking methods wont work since the tablet will not power on it wont connect to the computer in ADB mode and I have no idea if its in USB debugging mode at this time.
It will sorta power on (screen still blank- by holding the power button for 20 secs) and the computer "senses" it but at that point it will not be recognized by the PC, and give the error that the "USB device has malfunctioned". I have tried about everything out there- can you guys help me out to get the power back on at least where I can get the ADB to recognize the device? Thanks in advance.
Oh- I did purchase a fastboot cable as well but that did not help matters at all.....
Amazon: "3ft Fastboot Factory Cable For Motorola Unbrick Droid Xoom Fire by Atomic Market"
Athruz
Click to expand...
Click to collapse
You mentioned "THOR" in the title later expanding that to "HD 7". They are two distinctly different devices. For the purpose of this post I'll assume you are referincing a 3rd gen HDX 7 device (Thor). Unfortunately nothing can be done short of board replacement which is not cost effective given the current price point of pre-owned devices in good condition. As you probably read fastboot/factory cables are useless on HDX models which is the only way to communicate with an otherwise comatose device. Sorry for your daughter's loss. Poke around action sites like eBay; I have seen supposedly new 16GB HDX 7's going for $50-60 USD. If you daughter is younger a 5th gen 7" fire is a good alternative as it can be rooted and with several quality custom ROMs available you FireOS is not to you/her liking.
Thanks
Davey126 said:
You mentioned "THOR" in the title later expanding that to "HD 7". They are two distinctly different devices. For the purpose of this post I'll assume you are referincing a 3rd gen HDX 7 device (Thor). Unfortunately nothing can be done short of board replacement which is not cost effective given the current price point of pre-owned devices in good condition. As you probably read fastboot/factory cables are useless on HDX models which is the only way to communicate with an otherwise comatose device. Sorry for your daughter's loss. Poke around action sites like eBay; I have seen supposedly new 16GB HDX 7's going for $50-60 USD. If you daughter is younger a 5th gen 7" fire is a good alternative as it can be rooted and with several quality custom ROMs available you FireOS is not to you/her liking.
Click to expand...
Click to collapse
Thank you very much for the info - I was suspecting that unfortunately.
Question
Apologies, to hasty in getting a question onto the forums
I recently received both my Nexus 5 and LG G4 second hand boot-lopped and I, with prior experience, hopped to restore them. I downloaded all the images and firmware needed and tried to get the most recent versions to avoid any downgrade problems. Then everything went south. Using the lg tool, the G4 got flashed 100% but then that was it. It would not boot up and not turn on. My computer would recognize it but it would leave me a "Unknown USB Device (Device Descriptor Request Failed)" message. At that point I lost hope and moved onto the nexus 5. I used wugfresh nexus root toolkit and went through the usual process of unlocking boot loader and downloading image. Well when it started to flash boot.img it restarted and that was it as well. Now both my nexus 5 and lg 4 are dead and leave me the same message when plugged in. I'm very confused as to what has happened. I've done this dozens of times before and it has never given me this. I believe they are hard bricked now and i dont know why. Is it Windows 10 anniversary update? Is there a solution? I'm desperate and lost at this point because I cant find anything online. (Not able to access recover mode on either). Please help.
Check this out, there are a couple of videos too. Also, how did you flash your nexus 5 image, did you use adb or fastboot? As for the LG phone, take a look at this thread, it might be a hardware issue that is LG's fault.
RAZERZDAHACKER said:
Check this out, there are a couple of videos too. Also, how did you flash your nexus 5 image, did you use adb or fastboot? As for the LG phone, take a look at this thread, it might be a hardware issue that is LG's fault.
Click to expand...
Click to collapse
Thanks I'll look into it. As for the Nexus 5, it was done through adb. The thing I'm not understanding is why it happened. Usually my nexus devices don't get bricked like this and it weird that it happened to both of them
The0nlyboss said:
Thanks I'll look into it. As for the Nexus 5, it was done through adb. The thing I'm not understanding is why it happened. Usually my nexus devices don't get bricked like this and it weird that it happened to both of them
Click to expand...
Click to collapse
I recommend flashing via fastboot instead (fastboot flash boot.IMG) But you'll have to look into the link to solve the driver issue.