Related
I'm trying to repair someone's Kindle Fire but there doesn't seem to be anything I can do.
1) Neither of our computers have the Kindle Fire driver installed.
2) When I use the factory USB cable, all I see is a yellow triangle flashing for like 5 seconds, then nothing, then the triangle again, and so on.
3) It won't turn on at all if you press the power button.
4) I can't install the driver no matter how hard I try, the device simply doesn't exist according to my laptop.
By any chance are you using usb 3.0 ports? If so try 2.0 you will have better success. Also sounds like a 5 second bootloop http://forum.xda-developers.com/showthread.php?t=1623244 I have seen it near impossible to correctly install the driver under these circumstances or to get the computer to recognize the kindle for long enough or for windows to do what it does very poorly anyway. To remove the driver problem from the equation I suggest creating a live linux bootable usb drive as in the process described here http://forum.xda-developers.com/showthread.php?t=1670405 but this does not resolve the possible issue at hand a dead battery in addition to creating the pendrive you will want to correctly add firekit found here http://forum.xda-developers.com/showthread.php?t=1430038 in order to usb boot the device and replace the bootloader with one that is designed to charge under such conditions which can be sent using firekit. Good luck
Hello
Im now the proud owner of a bricked first gen kindle fire. I decided to go ahead and successfully installed this ROM on my device. After messing around with the apps the screen froze, i decided to do a hard reset and now my device wont turn on and im not seeing any lights when its plugged in. After some investigation ive come to the conclusion that the device has a bootloader error of some kind. Ive tried using fire kit and the shorting trick to get around this issue but its seems that im out of my depth. Im messed around with "soupkit" and have gotten the drivers installed on my linux distro (ubuntu) howver when i run "adb devices" im not seeing my device. I occassionally see the device pop up in my listing when i run "lsusb" however.
any help would be greatly appreciated.
what you linked as a rom is not a rom unless you flashed update.zip but everything would surely go wrong if you flashed the kindle fire utility??? Power on issues are usually from a completely dead battery. It could fail to turn on depending on what you did flash if it was way off the chart incorrect. So I`m confused about your post you must clarify. You will certaily need firekit to repair if it fails to power on with a full battery pm me I will try to assist you in fixing your completely brain dead device.
0beah said:
Hello
Im now the proud owner of a bricked first gen kindle fire. I decided to go ahead and successfully installed this ROM on my device. After messing around with the apps the screen froze, i decided to do a hard reset and now my device wont turn on and im not seeing any lights when its plugged in. After some investigation ive come to the conclusion that the device has a bootloader error of some kind. Ive tried using firekit and the shorting trick to get around this issue but its seems that im out of my depth. Im messed around with "soupkit" and have gotten the drivers installed on my linux distro (ubuntu) howver when i run "adb devices" im not seeing my device. I occassionally see the device pop up in my listing when i run "lsusb" however.
any help would be greatly appreciated.
Click to expand...
Click to collapse
The "shorting trick" will work...but rarely on the first shot. Keep trying and don't give up.
A few things to note before trying the shorting trick:
* Be sure you aren't using a USB 3.0 port
* Make sure the power is completely off. Even if there are no outward signs of life, the device can still be on and the Firekit will fail. Hold the power button for 15 seconds or so to make sure there is no power to the device before plugging in and attempting the shorting trick.
* Be sure you fully understand the instructions in the Firekit/Rekindle threads. There is important information there that can easily be overlooked if you aren't attentive.
Unfortunately, the USBboot method is one of the few things you're completely on your own with. No one here can help you with it. That being said, it's one of those things you just need to be persistent with it. Everyone I've seen use the Firekit, has succeeded, eventually.
shorting trick again.
So I've done the shorting trick again. Connected the 3rd dot on the board to the metal case around it. Fire kit sees something obviously and my usb port pick up this:
Bus 001 Device 016: ID 0451:d00f Texas Instruments, Inc.
Still no light still no power and fire kit moves from:
waiting for OMAP44xx device...
to:
< waiting for device >
and just hangs there. I've been informed that for custom roms it will take a while, but how long is that exactly? i've left it there fro roughly about half an hour.
advice?
0beah said:
So I've done the shorting trick again. Connected the 3rd dot on the board to the metal case around it. Fire kit sees something obviously and my usb port pick up this:
Bus 001 Device 016: ID 0451:d00f Texas Instruments, Inc.
Still no light still no power and fire kit moves from:
waiting for OMAP44xx device...
to:
< waiting for device >
and just hangs there. I've been informed that for custom roms it will take a while, but how long is that exactly? i've left it there fro roughly about half an hour.
advice?
Click to expand...
Click to collapse
BTW the rom i used was gotten from here
Yeah leaving it <waiting for device> really does nothing If you dont get any action within 3 or 4 mins start the procedure again. You must keep the short until it runs through as well 30 mins is overkill. Make sure you are contacting the correct test point here it is shown circled in red http://forum.xda-developers.com/showpost.php?p=19762674&postcount=51 .
Thepooch said:
Yeah leaving it <waiting for device> really does nothing If you dont get any action within 3 or 4 mins start the procedure again. You must keep the short until it runs through as well 30 mins is overkill. Make sure you are contacting the correct test point here it is shown circled in red http://forum.xda-developers.com/showpost.php?p=19762674&postcount=51 .
Click to expand...
Click to collapse
Yeah thats exactly what i did. Unfortunately im busy with work now but im gonna leave it plugged in and the fire kit running for the rest of the day and see if there's any change.
You can leave it plugged in for 10 years and firekit running and if your not shorting it there never will be a change.
same hinesAn
So I'm definitely not sure if I'm shorting this properly. I have set up a pin to touch the point and the frame to leave my hands free. Running some diagnostics. Not sure if its relevant but I'm in the 11.10 environ of ubuntu btw. I'm noticing the device keeps getting disconnected by the system with the following message:
device: 38 was not an MTP device
USB disconnect, device number 38
checking on some libmtp things maybe the issue is that my linux install just doesn't recognize the device?
Use the intel 86 desktop CD image http://releases.ubuntu.com/precise/
Okay so ive made a live cd off of the link provided (cant make a bootable usb at the moment). Same issue as before except now i get the following according to th logs:
[ 3824.857537] usb 1-1.2: new high-speed USB device number 24 using ehci_hcd
[ 3824.950355] usb 1-1.2: unable to get BOS descriptor
[ 3825.427367] usb 1-1.2: USB disconnect, device number 24
A live CD will not work because of persistent only a live USB has this capability sorry. You could try my iso its possible that it may work as a live CD http://forum.xda-developers.com/showthread.php?t=1413358 post 7 but I have never tested use the per instructions to created the CD. Sorry for the large download but its totally prefab create boot and use nothing else needed. The way you're doing it when you reboot no Soupkit changes will be saved to the CD.
Thepooch said:
A live CD will not work because of persistent only a live USB has this capability sorry. You could try my iso its possible that it may work as a live CD http://forum.xda-developers.com/showthread.php?t=1413358 post 7 but I have never tested use the per instructions to created the CD. Sorry for the large download but its totally prefab create boot and use nothing else needed.
Click to expand...
Click to collapse
Im sorry im not following exactly why i NEED persistent? is it only the adb drivers? cause ive gotten those dld via PPA. Just would like to now out of curiosity really. Regardless i'll grab a 4gb USB ASAP.
The persistent or Casper r/w allows for changes to be save between reboots on a live USB that's why it will not work on a CD because no data including udev rules aren't preserved. Soupkit is intended to either be ran on a live USB or a full install. I recommended 12.04 because through the process of testing Soupkit well over 200 times that I found there to be some mild issues that accompanied the use of 11.10. I tested every viable distro that allowed for persistent xubuntu,kubuntu, multiple distros of Ubuntu and Linux mint mate and found that 12.04 Ubuntu and Linux mint mate 32 bit worked the very best with less hassles to the user.
rsomeoe Having
I now have 12.04 tried running the firekit tool while doing the "shorting trick". Still no change as from before. Still getting:
[ 716.828012] usb 1-2: new high-speed USB device number 8 using ehci_hcd
[ 716.960808] usb 1-2: unable to get BOS descriptor
[ 719.962054] usb 1-2: USB disconnect, device number 8
0beah said:
I now have 12.04 tried running the firekit tool while doing the "shorting trick". Still no change as from before. Still getting:
[ 716.828012] usb 1-2: new high-speed USB device number 8 using ehci_hcd
[ 716.960808] usb 1-2: unable to get BOS descriptor
[ 719.962054] usb 1-2: USB disconnect, device number 8
Click to expand...
Click to collapse
So i now have a pen drive. installed soupkit. ran the firekit install on in and now im now stuck at "waiting for device:". Any assistance?
So I was trying to change my son's Fire 2 over to the new Kit Kat OS, and as I was downloading the necessary files to my computer, I thought I would wipe everything, since he had managed to pretty much fill it with junk, (he's 8). I have TWRP, (2.3.3.0) installed, and used that to wipe everything, including the internal storage and the format data wipe. I have done this with my Fire 1 with no issues, but this time I ran into a problem. TWRP works fine, but now windows won't recognize the tablet. When I go to mount the usb storage to copy the os files over, windows 7 cant load the device drives, and in my device manager it shows the Amazon Kindle fire 2 with the yellow exclamation mark next to it, saying that the drivers for this device are not installed. I have the SDK installed, and I have gone through and re installed the device drivers several times, and also uninstalled the kindle from the device list in manager. Nothing is working. I have attempted fastboot, but when I do try, it gets stuck at the "press the button menu" for TWRP, and after running the fastboot -i 0x1949 getvar product command, it tells me it sees an Otter2-Prod-04.
Does anybody have any ideas or suggestions on how I can get into the usb storage so I can load the OS info? Thanks for any help.
Dead?
Well, I rebooted from TWRP and it just went black. No light when the cable is plugged in, (factory cable), no twenty second reset working, nothing. IS it safe to assume I now have a pretty paperweight, and I should be looking into getting my son another tablet?
xanthian23 said:
Well, I rebooted from TWRP and it just went black. No light when the cable is plugged in, (factory cable), no twenty second reset working, nothing. IS it safe to assume I now have a pretty paperweight, and I should be looking into getting my son another tablet?
Click to expand...
Click to collapse
Leave it on the charger overnight. Keep trying 20 second reboot. If you can get back into recovery you can adb sideload a rom into the device.
You've never been able to USB Mount this device from recovery.
Good luck. No reason it should be bricked....
How did you try to get into fast boot? You need a fastboot cable. This device is NOTHING LIKE the kf1.
Edit: also need to be sure exactly which kf2 you have.
--》Sent from my mind to your screen
mindmajick said:
Leave it on the charger overnight. Keep trying 20 second reboot. If you can get back into recovery you can adb sideload a rom into the device.
You've never been able to USB Mount this device from recovery.
Good luck. No reason it should be bricked....
How did you try to get into fast boot? You need a fastboot cable. This device is NOTHING LIKE the kf1.
Edit: also need to be sure exactly which kf2 you have.
--》Sent from my mind to your screen
Click to expand...
Click to collapse
I have the standard cheap Kf2, no HD, just the upgrade from the first from last year, (2012), they were selling around Christmas last year. I have tried getting it to start back up, but with no success. I don't even understand why it shut down like that. I hadn't done anything to it other than reboot, which I had done successfully several times before. As for the fastboot, I may be incorrect. I ran the adb command: fastboot -i 0x1949 getvar product in CMD, and then plugged the kindle in and booted up. It showed it was an otter4 or something like that, which I thought meant it was in fastboot. At that time I was using my S4 usb cable. I'm sure I can sort out ho to sideload a rom via adb if I can ever get it started back up again. I had thought about opening it up and unplugging the battery and then re-plugging it back it to try to reset it, but I doubt it will help. Would getting a fastboot cable possibly make it start back up? If anyone has any suggestions on how I can get this thing started up again I would greatly appreciate it. I fell like crap for bricking my kids kindle, he's 8, so it's really important to him. It'll take me several months to save up to buy another one, so if I can get it running again, that would be awesome.
Here's a bit of an oddity, and maybe this spells some hope for me yet. So I plug the KF2 into the computer with the factory cable, hold down the power button for twenty seconds, let go, and then hit the power button again, for about a second, and windows makes the usb device plugged in sound, followed by a usb rejected or not recognized sound. It repeats this over and over for about thirty seconds or so and then stops. So there is something going on with the kindle, and its not flat out dead, or at least it seems. Is this a good sign? Does this help anyone to figure out what I might need to do?
So just to be sure that I was using a fastboot cable, even though I believe that my samsung s4 cable is fastboot capable, and I'm pretty sure I am using the factory cable, (it's not marked so I can't be 100% sure), I built my own fastboot cable, via instructions on how to do so on xda. (found HERE) It's doing the same thing with windows making the usb device inserted / recognized sound, followed by the usb device error sound. I'm guessing that this is a bad thing, am I correct?
One more bit of information to add to the list. I attempted to do the fastboot mode again,and decided to watch my device manager. Whenever windows chimes off that it detects a usb device, something called OMAP 4430 pops up for about a second before disappearing when the error sound comes on. I'm going to try and get a driver for that, just to see what happens. Maybe it'll help. I doubt it, but you never know until you try...
This just keeps getting weirder and weirder. So I installed the omap driver for windows and android, and now windows recognizes the device, but only for about a second. It just keeps cycling through the usb connected sound, recognizing the omap device, and then the usb disconnected sound, as though the device were being plugged in and then unplugged about every second for roughly thirty seconds. I'm starting to think there is something seriously wrong, which bites. If anyone has any suggestions, I'm all ears.
That's a hard brick' we can't use the usboot/aboot utility to fix the device like you can on other omap devices because we need a certain signed file to fix the boot loader. Only amazon has that file and they aren't giving it out. There is a way to recover your device from a hard brick but you need to be good with a soldering iron and have a USB sdcard reader, the kind that kinda is like a flashdrive rather than the multi type readers and some really small wire. Kurohyou wrote a tutorial on how to fix it in the kf2 dev section, not sure if he ever added the part in on how to reflash the boot loader from Linux, but if you take this route and try to fix it I wouldn't mind helping.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
That's a hard brick' we can't use the usboot/aboot utility to fix the device like you can on other omap devices because we need a certain signed file to fix the boot loader. Only amazon has that file and they aren't giving it out. There is a way to recover your device from a hard brick but you need to be good with a soldering iron and have a USB sdcard reader, the kind that kinda is like a flashdrive rather than the multi type readers and some really small wire. Kurohyou wrote a tutorial on how to fix it in the kf2 dev section, not sure if he ever added the part in on how to reflash the boot loader from Linux, but if you take this route and try to fix it I wouldn't mind helping.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
OK, I have both a tf - micro sd card usb card reader, and a full sd card usb card reader. I'll have to go digging for them in the morning, but I think I can find them. I'm also really good with a soldering iron, (used to be a vcr / tv repair technician), It took me roughly two minutes to do the homemade factory cable. So I am game, especially since at this point I really have nothing to loose by trying. Would you mind posting a link to where the tutorial is? I'm going to go looking for it, but just in case I can't find it, a link would help. And thank you so much for this suggestion!
OK, I found the tutorial on how to wire everything up and what's needed. I'll have to go get some small wire and a better tip for my iron, but aside form that, the wiring and soldering seems simple enough. My problem is going to be dealing with linux. I know Windows backwards and forwards, but I have a pretty limited knowledge of linux, aside from a few things we did in school to cover general PC repair. I can get it up an running, which I will do tomorrow, but I may need some help sorting out what to do with it once I have the board lined up and ready to roll, which will have to wait till next week when I get back from a work trip. Do you know if kurohyou offers repairs? If it's not too expensive, I would be willing to pay for the fix.
He might repair it, he just made a solderless repair tool to repair them. But like I said I'm more than willing to help with the Linux side, I'm a PC tech myself and use Linux primarily, you can basically burn an ubuntu live CD or put it on a USB stick and boot into the entire os without having to install it, from there's its as simple as plugging the device into the PC, and seeing what device path it assigned to the kindle's emmc, and running a dd command to flash the boot loader back onto the device.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
... you can basically burn an ubuntu live CD or put it on a USB stick and boot into the entire os without having to install it, from there's its as simple as plugging the device into the PC, and seeing what device path it assigned to the kindle's emmc, and running a dd command to flash the boot loader back onto the device.
Click to expand...
Click to collapse
Yeah, I've ran a live usb version of unbuntu a few times, and in the past I have had the full version on my system, but I rarely ever used it, so I got rid of it. I have an extra 600 gig's of space just sitting around on my laptop, so I will install a full version, and get off my lazy rear and start learning linux. This should be a good first lesson. I can't do any of this until next week though, so I will be pm'ing you once I've gotten everythig hooked up and ready to go. Thanks again for the help.
I had a question about the repair though. I went through the discussion, and I may have just missed it, but did he ever figure out how to get the OS up and running? From what I could tell, he was still working on it, and hadn't managed to get a working rom loaded. I probably just either missed it, or didn't understand one of the post's.
All of the instructions I found for doing this weren't exactly clear, so I'm writing this out in a way that even dummies like me can understand. So, my Nvidia Shield TV got soft bricked when I tried to update my TWRP to this version.
First, you have two options for the cables:
This: http://www.monoprice.com/Product?p_id=9724
and this: http://www.monoprice.com/product?p_id=5443
Plug them into each other so they're just 1 cable now.
The second option is to use a USB to micro USB data/charging cable, like the one that it came with.
Here are the steps, read it completely through 1 time before doing anything. I find that makes things easier to understand when you're ready to actually do it.
Install FASTBOOT DRIVERS: https://developer.nvidia.com/gameworksdownload#?search=SHIELD Family Windows USB
Install Minimal FASTBOOT & ADB: http://forum.xda-developers.com/showthread.php?t=2317790
Download OS Image: https://developer.nvidia.com/gameworksdownload
Extract the OS Image to your desktop.
Go to the installation folder for Minimal FASTBOOT & ADB and copy its contents into the OS Image folder you just created.
Open a Windows command prompt in this folder.
Make sure power cable & USB OTG cable on NSATV are UNPLUGGED.
Make sure HDMI cable is PLUGGED IN.
Plug the standard USB end of the USB OTG cable pair into a PC.
*** DO THE STEPS BELOW IN THE EXACT ORDER ***
Plug in USB OTG end of the USB OTG cable pair into NSATV.
Plug in the power cable. The next step follows quick.
Quickly touch and hold the power button until the FASTBOOT screen appears on your TV, then release.
Now, go back to your PC.
In the Windows command prompt, type: fastboot devices
Make sure the fastboot device appears.
If you see your fastboot device, then you can follow the instructions in the HowTo-Flash-Recovery-Image.txt file.
I hope this helps. If there's any part that's confusing, let me know and I'll edit it.
Yeah, you guys are awsome, it worked!!!!!
Thanks so much for all your help and advice :good:
You could also just use the charge cable that you get for your controllers rather than buying the extra cables, it works fine.
Sent from my HTC One M9 using Tapatalk
gffmac said:
You could also just use the charge cable that you get for your controllers rather than buying the extra cables, it works fine.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
It doesn't need an OTG cable?
Nope, using the supplied cable just connect the micro usb end to shield other to PC and bobs your uncle ?
Sent from my HTC One M9 using Tapatalk
any idea if this will work for my shield 16GB? since i was updating it to 3.0 this morning and the electric went now all it does it boot right to TWRP recovery. also i still have access to fastboot.
beefy143 said:
any idea if this will work for my shield 16GB? since i was updating it to 3.0 this morning and the electric went now all it does it boot right to TWRP recovery. also i still have access to fastboot.
Click to expand...
Click to collapse
It should?
tried and no it does not just left at the nvidia boot creen with the odd black screen reboot back to the nvidia symbol any ideas as to what i can do to fix my shield?
beefy143 said:
tried and no it does not just left at the nvidia boot creen with the odd black screen reboot back to the nvidia symbol any ideas as to what i can do to fix my shield?
Click to expand...
Click to collapse
Follow the instructions EXACTLY. I have the 16Gb model and mine was doing the same thing as yours.
Just to repeat what others said the back of the shield TV has a microusb port so you don't need a otg cable just use any standard microusb cable you have laying around plug small end into shield TV and big end to laptop/computer
Hi!
I tried but failed. The issue is, that it reboots directly after showing the recovery menu.
Only see it 2 seconds, then reboot. No reaction on menu choices...
I guess it happened when I tried to copy the SD card to another one.
You should be using fast boot to do this. Plus, there's no SD card in the instructions. Not sure what you are trying to do.
JoCamel said:
Hi!
I tried but failed. The issue is, that it reboots directly after showing the recovery menu.
Only see it 2 seconds, then reboot. No reaction on menu choices...
I guess it happened when I tried to copy the SD card to another one.
Click to expand...
Click to collapse
Try again without an sd card attached maybe. Also try 'fastboot boot recovery.img' instead of flashing it.
Neo3D said:
[*]In the Windows command prompt, type: fastboot devices
[*]Make sure the fastboot device appears.
[*]If you see your fastboot device, then you can follow the instructions
Click to expand...
Click to collapse
Hi
All fine up to that point... Fastboot Devices... nothing shows up!
? anyone?
My box is stock, I have not messed with it at all.
if i not enable debug? how to do?
fredphoesh said:
Hi
All fine up to that point... Fastboot Devices... nothing shows up!
? anyone?
My box is stock, I have not messed with it at all.
Click to expand...
Click to collapse
Could be a driver issue? Make sure the drivers are properly installed and working? Try rebooting?
Will these steps work with the 2017 16GB version? Cause I want to have full Android on the Shield but the processes I've seen are pretty confusing.
I want to try this, will this work with the new 5.2 update?
Jabadabaduu!! It solved my problem
Hey Neo
First of all, your guide saved my day! - Thanx!
I know this must be a strange question, but is the person on your XDA profile picture, and the one that has written the article really the same person ?
Neo3D said:
All of the instructions I found for doing this weren't exactly clear, so I'm writing this out in a way that even dummies like me can understand. So, my Nvidia Shield TV got soft bricked when I tried to update my TWRP to this version.
First, you have two options for the cables:
This: http://www.monoprice.com/Product?p_id=9724
and this: http://www.monoprice.com/product?p_id=5443
Plug them into each other so they're just 1 cable now.
The second option is to use a USB to micro USB data/charging cable, like the one that it came with.
Here are the steps, read it completely through 1 time before doing anything. I find that makes things easier to understand when you're ready to actually do it.
Install FASTBOOT DRIVERS: https://developer.nvidia.com/gameworksdownload#?search=SHIELD Family Windows USB
Install Minimal FASTBOOT & ADB: http://forum.xda-developers.com/showthread.php?t=2317790
Download OS Image: https://developer.nvidia.com/gameworksdownload
Extract the OS Image to your desktop.
Go to the installation folder for Minimal FASTBOOT & ADB and copy its contents into the OS Image folder you just created.
Open a Windows command prompt in this folder.
Make sure power cable & USB OTG cable on NSATV are UNPLUGGED.
Make sure HDMI cable is PLUGGED IN.
Plug the standard USB end of the USB OTG cable pair into a PC.
*** DO THE STEPS BELOW IN THE EXACT ORDER ***
Plug in USB OTG end of the USB OTG cable pair into NSATV.
Plug in the power cable. The next step follows quick.
Quickly touch and hold the power button until the FASTBOOT screen appears on your TV, then release.
Now, go back to your PC.
In the Windows command prompt, type: fastboot devices
Make sure the fastboot device appears.
If you see your fastboot device, then you can follow the instructions in the HowTo-Flash-Recovery-Image.txt file.
I hope this helps. If there's any part that's confusing, let me know and I'll edit it.
Click to expand...
Click to collapse
Awesome, works like a charm
So I bricked my FireTV last night during an upgrade to rbox's latest fw...
Short story is, it got to the Amazon app optimization after the flash fine so I went back to the computer to start working on the second box while it did it's thing. I mistakenly sent the reboot recovery command to the box that was optimizing itself. I didn't notice I was sending the command to the wrong box until I saw that my second unit was not rebooting to recovery.
Needless to say, it now no longer boots to any logos, and does not turn on at all (no light when plugged in, not even for a split second).
What are my options to unbrick? I'm taking a guess that the SD reader/eMMC method is the only one. If so, is it possible to retain an unlocked bootloader/etc with this method? I've read you'd lose it, but I'm not familiar.
If someone could point me in the right direction that'd be awesome. I tried google but it's filled with loads of outdated or unrelated information (mostly debricking if the amazon logo appears) or info from when the initial hardware root method came out.
i am in the same boat. if you find anything let me know.
after following the downgrade tutorial, I executed the command as instructed adb reboot recovery
device reboots into recovery,
update starts..... after while reboots...
upon reboot
no light on device no logo on screen - black screen
connecting to win7 machine with USB cable it initially recognizes the box, but cannot connect with either ADB nor FASTBOOT - searching for device
sparkd said:
i am in the same boat. if you find anything let me know.
after following the downgrade tutorial, I executed the command as instructed adb reboot recovery
device reboots into recovery,
update starts..... after while reboots...
upon reboot
no light on device no logo on screen - black screen
connecting to win7 machine with USB cable it initially recognizes the box, but cannot connect with either ADB nor FASTBOOT - searching for device
Click to expand...
Click to collapse
At least you can connect with USB! I get no connection at all to the pc with a A-A cable.
I would suggest for you trying to get the timing right and initiate the fastboot commands right when the device is recognized.
You people need to reflash your partitions, this happened to me months ago. Can't search for the thread now, I think the steps were in the FireTV1 5.0.5.1 thread...
my device bootloader is not unlocked. I was following the steps to downgrade firmware in an attempt to unlock the bootloader.
in Win7 Control Panel > System > Device Manager the FireTV1 appears as QHSUSB_DLOAD - i think I am also going to try this ... http://forum.xda-developers.com/showpost.php?p=66961740&postcount=676
thanks for the advice ldeveraux, ill take a look.
Ordered the eMMC adapter from exploiteers. This is likely the only way I'll be able to fix this as the USB A-A cable is not detecting my FTV
Well I managed to get my device talking with an A-A USB cable while waiting for my eMMC adapter. So now to flash
Is there a way to recover with this method without losing the ability to unlock the bootloader? Bootloader was unlocked prior to the brick.
UPDATE: annnddd it didn't work for me. Was getting I/O errors while writing and now the device no longer gives me partitions in /dev/. The usb device still shows up however.
how did you get the /dev/ partition to appear ?
which linux distro did you download / install as I cannot see any partitions on my device
did you use the linux in a VM ? & did you have the windows drivers installed beforehand ?
thanks