Can't get any computer or OS to recognize my kindle fire HD 7 even with the factory cable. Help!!!:crying:
I was in fastboot mode and did a reboot and when it booted back up it stuck on the start screen and won't let me do anything anymore. The fastboot cable I bought doesn't put it into fastboot mode and it is not recognized by any of my computers or OS. Tried everything but my mac so far. That includes XP, 7, 8 and Ubuntu.
I'll try a hard reset again. I've done that several times hoping that one time it would get recognized by the computer.
Before you panic too much, you need give more information. What were you doing to "brick it"?
Have you tried a hard reset btw? (Hold the power button down for 30 seconds) then let go and turn on?
Worked for me before when I thought messed up
Kgyuszko
Sent from my KFTT using xda app-developers app
duncanidahoe said:
Can't get any computer or OS to recognize my kindle fire HD 7 even with the factory cable. Help!!!:crying:
I was in fastboot mode and did a reboot and when it booted back up it stuck on the start screen and won't let me do anything anymore. The fastboot cable I bought doesn't put it into fastboot mode and it is not recognized by any of my computers or OS. Tried everything but my mac so far. That includes XP, 7, 8 and Ubuntu.
I'll try a hard reset again. I've done that several times hoping that one time it would get recognized by the computer.
Click to expand...
Click to collapse
You were doing something in fastboot mode, What was it? did you try to install the 2nd bootloader by hashcode or just restoring your device?
duncanidahoe said:
Can't get any computer or OS to recognize my kindle fire HD 7 even with the factory cable. Help!!!:crying:
I was in fastboot mode and did a reboot and when it booted back up it stuck on the start screen and won't let me do anything anymore. The fastboot cable I bought doesn't put it into fastboot mode and it is not recognized by any of my computers or OS. Tried everything but my mac so far. That includes XP, 7, 8 and Ubuntu.
I'll try a hard reset again. I've done that several times hoping that one time it would get recognized by the computer.
Click to expand...
Click to collapse
I did something similar and have what i though 'bricked' the kindle. Have another good read through hashcode 2nd bootloader thread, others have has similar, and there are some instructions on how to resolve fastboot cable not recognised, and kndle is bricked. if not, go down the firstaide thread, that also deals with bricked kindles.
good luck
kgyuszko
have you successed to fix it ?
unluckily, I have the same problem.
factory cable is no use.
gogolovedell said:
have you successed to fix it ?
unluckily, I have the same problem.
factory cable is no use.
Click to expand...
Click to collapse
I just had same problem. Factory cable no use. I intalled Kinology but thought to restore to a Kindle version. When the bootloader was being flashed, a black brick ... Anyone knows how to deal with this? I even opened the case and unplug battery.
qiudongxiao said:
I just had same problem. Factory cable no use. I intalled Kinology but thought to restore to a Kindle version. When the bootloader was being flashed, a black brick ... Anyone knows how to deal with this? I even opened the case and unplug battery.
Click to expand...
Click to collapse
Your problem will be overcome if you follow here
Hi, I also ahve a black brick. It won't start after I used the wrong bootloader(the one for KFHD8 isntead if KFHD7)
I do have a factory cable but still nothing.
duncanidahoe said:
Can't get any computer or OS to recognize my kindle fire HD 7 even with the factory cable. Help!!!:crying:
I was in fastboot mode and did a reboot and when it booted back up it stuck on the start screen and won't let me do anything anymore. The fastboot cable I bought doesn't put it into fastboot mode and it is not recognized by any of my computers or OS. Tried everything but my mac so far. That includes XP, 7, 8 and Ubuntu.
I'll try a hard reset again. I've done that several times hoping that one time it would get recognized by the computer.
Click to expand...
Click to collapse
gogolovedell said:
have you successed to fix it ?
unluckily, I have the same problem.
factory cable is no use.
Click to expand...
Click to collapse
qiudongxiao said:
I just had same problem. Factory cable no use. I intalled Kinology but thought to restore to a Kindle version. When the bootloader was being flashed, a black brick ... Anyone knows how to deal with this? I even opened the case and unplug battery.
Click to expand...
Click to collapse
kindleuser01 said:
Hi, I also ahve a black brick. It won't start after I used the wrong bootloader(the one for KFHD8 isntead if KFHD7)
I do have a factory cable but still nothing.
Click to expand...
Click to collapse
You all have a paperweight on your hands. The factory cable was the very last resort. If you're in warranty, send it in for a replacement.
possible solution
searching i found this page where explain how to fix the hard brick, black screen no sing of life, cant post links so, search in google "new life for a dead Kindle fire hd, is in mascote..... can any expert try it and explain that to the rest of us,
bryanfeanor said:
searching i found this page where explain how to fix the hard brick, black screen no sing of life, cant post links so, search in google "new life for a dead Kindle fire hd, is in mascote..... can any expert try it and explain that to the rest of us,
Click to expand...
Click to collapse
A while back, I brought this question up to Pokey9000, the developer of FireFireFire and Firekit for the Original Kindle Fire. His exact response to me was...
When the OMAP USB boots, it first waits a bit to handshake with a host. If the handshake is successful, the host sends a small loader to the OMAP that then does some hardware init and handshakes again with the host to get a payload to shove into RAM. This loader is similar to x-loader in that it has to be small to fit in the SRAM of the OMAP, and does low level initialization like mux, clock, and memory setup. However it differs in that it replaces the MMC and FAT handling in x-loader with USB loading as there's not enough room for a generic x-loader that does MMC and USB.
On HS (fused) OMAPs this initial USB loader payload must be signed just like x-loader has to be for eMMC boot. If the payload doesn't have a signature that checks out, the OMAP halts until it's reset. This is enforced by hardware, so short of finding a sploit in the OMAP ROM code or a copy of Amazon's USB boot tools used in factory it's not going to work.
TL;DR not likely.
Click to expand...
Click to collapse
Considering his knowledge of bootloaders and low level hardware stuffs far exceeds mine, and the fact that he's been looking at this issue ever since the B&N Nook devices (maybe even longer), I have to assume he knows what he's talking about.
The information on the page at Mascote seems to contradict what Pokey9000 says because usbboot uses an a-boot(x-loader) instead of this not-so-typical USB loader mentioned previously. And the answer to whether or not the author was actually successful in reviving the KFHD using this method has been left a little ambiguous.
But, as much as it would suck for me to have been the d*ck that told everyone that it couldn't be done, I would LOVE to be proven wrong.
I'd say, if you have a hard-bricked KFHD, then I guess there's not much else you can lose by testing it out.
soupmagnet said:
A while back, I brought this question up to Pokey9000, the developer of FireFireFire and Firekit for the Original Kindle Fire. His exact response to me was...
Considering his knowledge of bootloaders and low level hardware stuffs far exceeds mine, and the fact that he's been looking at this issue ever since the B&N Nook devices (maybe even longer), I have to assume he knows what he's talking about.
The information on the page at Mascote seems to contradict what Pokey9000 says because usbboot uses an a-boot(x-loader) instead of this not-so-typical USB loader mentioned previously. And the answer to whether or not the author was actually successful in reviving the KFHD using this method has been left a little ambiguous.
But, as much as it would suck for me to have been the d*ck that told everyone that it couldn't be done, I would LOVE to be proven wrong.
I'd say, if you have a hard-bricked KFHD, then I guess there's not much else you can lose by testing it out.
Click to expand...
Click to collapse
I have tried this on the 2012 KFHD (tate) and found it to work. After trying every recovery option via adb/fastboot. plus using factory cable. i was left with no choice. i used a pin needle with grounding wire attached to chassis of the kindle. be carefull the top is power(button?), bottom is restart. if you lose contact at all during the process. It will boot/reboot as normal.
with this method you must use CMD(in admin mode from pc) and adb push/pull/install/uninstall as needed. device has no input in this boot.
bryanfeanor said:
searching i found this page where explain how to fix the hard brick, black screen no sing of life, cant post links so, search in google "new life for a dead Kindle fire hd, is in mascote..... can any expert try it and explain that to the rest of us,
Click to expand...
Click to collapse
Were you able to get yours going using that?
go8soccer said:
Were you able to get yours going using that?
Click to expand...
Click to collapse
sadly no, it´s been more than 3 years now that my kindle brick.
Djskizo said:
I have tried this on the 2012 KFHD (tate) and found it to work. After trying every recovery option via adb/fastboot. plus using factory cable. i was left with no choice. i used a pin needle with grounding wire attached to chassis of the kindle. be carefull the top is power(button?), bottom is restart. if you lose contact at all during the process. It will boot/reboot as normal.
with this method you must use CMD(in admin mode from pc) and adb push/pull/install/uninstall as needed. device has no input in this boot.
Click to expand...
Click to collapse
I just recently bricked mine. Black screen. And all it does is charge. I can tell because the cable and device gets hot. Before i waste my time, would this help me. And yes i have that exact version
Otak98 said:
I just recently bricked mine. Black screen. And all it does is charge. I can tell because the cable and device gets hot. Before i waste my time, would this help me. And yes i have that exact version
Click to expand...
Click to collapse
A few hours ago I was given a Tate to fix, and having read around the subject, Djskizo's post sounds either like a complicated homemade factory fastboot cable, or to be honest a fake. Perhaps the OP meant fastboot instead of ADB, but that combined with vague details puts me off trying it. Try a factory cable perhaps, I'm gonna try making one (short out micro usb pins 1 and 4) and I'll get back to you on the results.
Any updates?
Any updates on this? I hard bricked mine yesterday flashing the wrong bootloader. Can't believe how easy it is to brick it. I just have myself to blame, I know...
I saw this post on Mascote and it seems like a post for KFHD Gen 1. Is this the one being referred to, by you guys?
Only Djskizo seems to claim that this works for KFHD Gen 2(tate) so far. Is this true?
Djskizo said:
I have tried this on the 2012 KFHD (tate) and found it to work. After trying every recovery option via adb/fastboot. plus using factory cable. i was left with no choice. i used a pin needle with grounding wire attached to chassis of the kindle. be carefull the top is power(button?), bottom is restart. if you lose contact at all during the process. It will boot/reboot as normal.
with this method you must use CMD(in admin mode from pc) and adb push/pull/install/uninstall as needed. device has no input in this boot.
Click to expand...
Click to collapse
I cant seem to figure out how to do the usbboot trick. I have a fire hd 3rd gen. On the board there is actually a point that says usb boot next to it but when i ground that out and plug it in it's still froze at the unanimated boot screen, sometimes the background also turns white? What am i doing wrong or is this point labeled just to confuse me
Added photos
Here is the pic of the usb boot and the board name.
Hello Guys!
I currently own a Kindle Fire 7" HD 7.4.6(Rooted) but I have a little problem getting my kindle to show up on 'My Computer' (Trying to transfer some music to my device) I have looked everywhere for this one specific question that I cant find an answer to hopefully it could be solved here... Anyways before my device was rooted Windows couldn't detect the device plugged in but here is the confusing part after I found out about rooting, I went on to try to do it and I managed to successfully root the kindle (following this guide: http://forum.xda-developers.com/showthread.php?t=2351201) installed the ADB drivers and yes "Root_with_Restore_by_Bin4ry_v31" program did detect my Kindle and rooted it which is weird because I mean Windows couldnt detect my kindle but that program did? I can plug in my kindle and it is detected as an ADB and even shows up in my device manager, but my question is, how do I get my kindle to be recognized so I can manage it (i.e. adding music/pictures) Another weird thing is that yes my kindle is detected but you know the sound that Windows makes when you plug something in via USB? Well when I plug in my kindle that sound is different I dont know if it has anything to do with this problem... Well that is my question hopefully someone will come to save the day!
Is the kindle listed under portable devices in the device manager?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Is the kindle listed under portable devices in the device manager?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Actually, no it doesnt, when I go in Device manager it has its own little tab called Kindle and when I click on the plus sign next to it it says ADB
CyKo616 said:
Hello Guys!
I currently own a Kindle Fire 7" HD 7.4.6(Rooted) but I have a little problem getting my kindle to show up on 'My Computer' (Trying to transfer some music to my device) I have looked everywhere for this one specific question that I cant find an answer to hopefully it could be solved here... Anyways before my device was rooted Windows couldn't detect the device plugged in but here is the confusing part after I found out about rooting, I went on to try to do it and I managed to successfully root the kindle (following this guide: http://forum.xda-developers.com/showthread.php?t=2351201) installed the ADB drivers and yes "Root_with_Restore_by_Bin4ry_v31" program did detect my Kindle and rooted it which is weird because I mean Windows couldnt detect my kindle but that program did? I can plug in my kindle and it is detected as an ADB and even shows up in my device manager, but my question is, how do I get my kindle to be recognized so I can manage it (i.e. adding music/pictures) Another weird thing is that yes my kindle is detected but you know the sound that Windows makes when you plug something in via USB? Well when I plug in my kindle that sound is different I dont know if it has anything to do with this problem... Well that is my question hopefully someone will come to save the day!
Click to expand...
Click to collapse
Plug your Kindle Fire HD in to USB port. Go to your device management. Look for the driver that is being detected right now. Right click on it and click and choose properties. Click to uninstall the driver. Now unplug the KFHD and plug it back in. Let the driver install. This should fix it. Restarting your computer after uninstalling the driver might be tried as well. removing the root hubs is sometimes necessary as well.
First off I'm not a total "Newb" with kindles, but am new to root/restoring KDF's. That said here's my problem: bought on eBay a bricked KDF HD to restore, did some reading got some root/restore programs, made a Factory/FastBoot cable, but cant get the computer to recognize the kindle in fastboot. The first gen KDF HD 7" (3rd gen fire) behavior: kindle logo flashes once shimmers slow once then shimmers fast and will do so till battery is dead.
That said. The problem I cant overcome is that windows does not recognize and fails to load drivers (which i did get the most up to date ones) so i cant get any of the root/restore programs find the KDF.
Please, this is my last hope before i have to shell out more cash to have someone else fix it, and if they cant i still shell out cash
Shunloc said:
First off I'm not a total "Newb" with kindles, but am new to root/restoring KDF's. That said here's my problem: bought on eBay a bricked KDF HD to restore, did some reading got some root/restore programs, made a Factory/FastBoot cable, but cant get the computer to recognize the kindle in fastboot. The first gen KDF HD 7" (3rd gen fire) behavior: kindle logo flashes once shimmers slow once then shimmers fast and will do so till battery is dead.
That said. The problem I cant overcome is that windows does not recognize and fails to load drivers (which i did get the most up to date ones) so i cant get any of the root/restore programs find the KDF.
Please, this is my last hope before i have to shell out more cash to have someone else fix it, and if they cant i still shell out cash
Click to expand...
Click to collapse
Use this http://forum.xda-developers.com/showthread.php?t=1951254 if your tablet stays in fastboot, you're good to run the bat . You can set an environment path with the sdk package but the bat tool will push the images for you.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
LinearEquation said:
Use this http://forum.xda-developers.com/showthread.php?t=1951254 if your tablet stays in fastboot, you're good to run the bat . You can set an environment path with the sdk package but the bat tool will push the images for you.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ok ran KDFHD SRT the only response that i got was a (waiting on device)
Shunloc said:
ok ran KDFHD SRT the only response that i got was a (waiting on device)
Click to expand...
Click to collapse
Here is a video tutorial on how what to do after you download the sdk package https://www.youtube.com/watch?v=oaNM-lt_aHw
LinearEquation said:
Here is a video tutorial on how what to do after you download the sdk package https://www.youtube.com/watch?v=oaNM-lt_aHw
Click to expand...
Click to collapse
Just wanted to say thanks for the info. I did have Sdk up and it only needed a slight tweek. BUT it didn't help still "waiting for device " is all I get when I run SRT
Hi, firts of all sorry for my english.
My sister give to me a BLU R1 HD 2GB RAM/16 ROM, it come without Amazon ads (so i think its OEM version). Its running BLU_R001UU_V21_GENERIC.
She told me that one day just not was recognized by PC to transfer files,photos, music. I make a wipe from recovery and still the problem no USB detection at all just charging, no sounds like new USB device was conected, no device on Device Manager.( i do this on diferents PC Windows 10, Windows 8, and Linux Elementary OS , Deeping OS)
I enable Developer Options and change MTP/PTP/Only Charge option and nothing happened; I opened the device to check the pins on the USB connector and check continuity and all seem like be perfect.
I thing that may be when was update to the last software something happen and lost USB recoginition, I want to Root the device and change Recovery but i see that the steps need connect the R1 HD to PC and make some things throw ADB console.
My question is: can i downgrade the original rom from SDcard in the actual Recovery.. to try recover the USB functions. or may be its something wrong on any internal chip that no make the USB conection.
Ty.
mykrov said:
Hi, firts of all sorry for my english.
My sister give to me a BLU R1 HD 2GB RAM/16 ROM, it come without Amazon ads (so i think its OEM version). Its running BLU_R001UU_V21_GENERIC.
She told me that one day just not was recognized by PC to transfer files,photos, music. I make a wipe from recovery and still the problem no USB detection at all just charging, no sounds like new USB device was conected, no device on Device Manager.( i do this on diferents PC Windows 10, Windows 8, and Linux Elementary OS , Deeping OS)
I enable Developer Options and change MTP/PTP/Only Charge option and nothing happened; I opened the device to check the pins on the USB connector and check continuity and all seem like be perfect.
I thing that may be when was update to the last software something happen and lost USB recoginition, I want to Root the device and change Recovery but i see that the steps need connect the R1 HD to PC and make some things throw ADB console.
My question is: can i downgrade the original rom from SDcard in the actual Recovery.. to try recover the USB functions. or may be its something wrong on any internal chip that no make the USB conection.
Ty.
Click to expand...
Click to collapse
I have not seen any other reports of usb dying after OtA update. You say you tried with different PC, what about using different usb cable?
But more bad news for your plans. If you have official v21 update, then you are not rootable anyway.
mrmazak said:
I have not seen any other reports of usb dying after OtA update. You say you tried with different PC, what about using different usb cable?
But more bad news for your plans. If you have official v21 update, then you are not rootable anyway.
Click to expand...
Click to collapse
I tried with diferents usb cables, and nothing happened.
mykrov said:
I tried with diferents usb cables, and nothing happened.
Click to expand...
Click to collapse
Do you know if any of them are sync cables??
codyalan said:
Do you know if any of them are sync cables??
Click to expand...
Click to collapse
They are USB cables that i use on others phones (lg 4x HD and Honor 6X) and work fine with those phones but not on my R1Hd
mykrov said:
Hi, firts of all sorry for my english.
My sister give to me a BLU R1 HD 2GB RAM/16 ROM, it come without Amazon ads (so i think its OEM version). Its running BLU_R001UU_V21_GENERIC.
She told me that one day just not was recognized by PC to transfer files,photos, music. I make a wipe from recovery and still the problem no USB detection at all just charging, no sounds like new USB device was conected, no device on Device Manager.( i do this on diferents PC Windows 10, Windows 8, and Linux Elementary OS , Deeping OS)
I enable Developer Options and change MTP/PTP/Only Charge option and nothing happened; I opened the device to check the pins on the USB connector and check continuity and all seem like be perfect.
I thing that may be when was update to the last software something happen and lost USB recoginition, I want to Root the device and change Recovery but i see that the steps need connect the R1 HD to PC and make some things throw ADB console.
My question is: can i downgrade the original rom from SDcard in the actual Recovery.. to try recover the USB functions. or may be its something wrong on any internal chip that no make the USB conection.
Ty.
Click to expand...
Click to collapse
I have the exact same issue... and it happened just after an OTA Update. After that it showed it was charging only when the phone was shut down.
No USB recognition whatsoever. PC/Mac. Tried several cables.... All USB modes... Factory Reset... Nothing made it work.
I contacted BLU with the issue. As soon as I have an answer (If ever) I will let you know.
If any of you know anything about this please share it here.
Oddly enough, After a cache wipe and factory reset, I have no ads on the lock screen. The app is running on the background but nothing shows up.
elcarmi said:
I have the exact same issue... and it happened just after an OTA Update. After that it showed it was charging only when the phone was shut down.
No USB recognition whatsoever. PC/Mac. Tried several cables.... All USB modes... Factory Reset... Nothing made it work.
I contacted BLU with the issue. As soon as I have an answer (If ever) I will let you know.
If any of you know anything about this please share it here.
Oddly enough, After a cache wipe and factory reset, I have no ads on the lock screen. The app is running on the background but nothing shows up.
Click to expand...
Click to collapse
I think if we can downgrade to a official rom under the actual recovery maybe that fix the USB. But all methods are under USB connection to PC.
mykrov said:
I think if we can downgrade to a official rom under the actual recovery maybe that fix the USB. But all methods are under USB connection to PC.
Click to expand...
Click to collapse
As far as I know downgrading is not possible without making the phone unusable. If by any chance that is possible maybe an update from an SD Card can work.