Bricked Fire TV, what are the options? - Fire TV Q&A, Help & Troubleshooting

Well this day has been a long time coming and it finally happened
In short I had reflashed my device with RBox prerooted rom via TWRP without any issues. In order to use certain applications I was using "hide my root" only to find once the su binary was hidden the application was unable to restore.
When I shouldve reflashed the rom I decided to take a short cut and install Super Su directly via TWRP, big mistake.
Device is now stuck on the Amazon logo (not the colourful splash screen) I've attempted to access the system recovery menu via the keyboard hotkey but the keyboard is unresponsive, in fact there seems to be no power coming from the USB. Which got me thinking, this is more than likely related to drivers, perhaps using an older keyboard with P/S2 and a USB adapter would work. I am yet to try this.
Any advice?
Would opening the device and unsoldering certain components perhaps initiate a reset of some kind?
Just throwing ideas around at I'm stuck with a paper weight
Any suggestions?

http://forum.xda-developers.com/fire-tv/development/firetv-2-unbrick-image-t3313349
This should help. The shorter option didn't work for me. I've used you the longer on mine and two other peoples ftv. It's worked every time.

I have a Fire TV 1, do you know of there are any recovery images available for this edition

Related

[Q] another boot loop post..

Hey guys, before I begin, yes i read the '[HOW-TO] Before asking for troubleshooting help...' page as well as the '[GUIDE] Kindle Fire For Beginners' page, and am still in need of a bit of assistance due to my hilariously lacking knowledge of the workings of electronic equipment. :silly:
I just dug my kindle fire out of my dresser drawer where it has been sitting due to being 'bricked' for quite some time (stuck at the boot logo - white kindle text and orange fire text shimmering on a pure black background - holds a charge but is indefinitely at this screen). It is completely stock, having not downloaded or installed any ROMs or any other software, and initially began experiencing this problem the morning after running it out of battery while downloading a few books and games one night. I promptly plugged it in, went to bed, and woke up to it in this state that next morning.
I have tried downloading Kindle Fire Unbrick V1.1 by ZombiePiratez and running that to fix it, but it does not recognize my kindle fire. So, i downloaded Eclipse ADT with Android SDK for windows and followed some instructions i found for getting it to recognize my kindle as "Android Composite ADB Interface" in hopes that then the unbricking tool would recognize it and work its magic for me. But it didnt. I imagine this is because the process that I followed is flawed.
My question is, if i were to buy a "factory cable" would I be able to unbrick my kindle fire without having to do any of this command promp shamanism thats clearly over my head? Kinfauns states in his guide that "With a factory cable, unbricking just comes down to "plug it in and flash new stuff" in almost every bricking situation." But what does 'flash new stuff' mean; should I have picked that up from the guide as well? Or could I just use the factory cable in conjunction with ZombiePiratez unbricking tool to get back to the factory settings?
Thanks in advance for any pointers
See my How to flash twrp and firefirefire with a Fastboot cable
http://forum.xda-developers.com/showpost.php?p=53652317&postcount=2
Sent from my XT862 using Tapatalk
Hey @sd_shadow !
Thanks for the link to that, the videos you've created make it possible for even someone with my level of tech knowledge to work through this problem. Immensely better than trying to follow a written guide
Anyway, I finally got my fastboot cable and followed the steps in your videos to the tee, however I'm still encountering one small problem. When I get to the point where I'm installing update-kindle-prerooted.6.3.3.v1.zip in TWRP by swiping across the screen, it runs until it gets to the line thanking paulobrien and two others but then promptly freezes (or so i assume since it doesnt continue on and the loading bar halts in its tracks). I decided after a few tries to just hold the power button to get it to shut off and then booted the kindle in normal boot mode - and it worked! - despite not being able to complete the process as shown in your video. But this concerns me, as I do not have any of the additional apps shown in your video (not that this truly matters to me) and under settings -> device it shows that I am running version 6.3.1_user_#####. So I have two questions:
1) Did the fff and twrp processes work, but the 6.3.3 update fail thus enabling me to use my kindle as a v6.3.1 device again?
2) Will it harm my device in any way (e.g. re-bricking) if I just call it good and use it as it is now?
Thanks for all the help so far :highfive:
noobSaurus said:
Hey @sd_shadow !
Thanks for the link to that, the videos you've created make it possible for even someone with my level of tech knowledge to work through this problem. Immensely better than trying to follow a written guide
Anyway, I finally got my fastboot cable and followed the steps in your videos to the tee, however I'm still encountering one small problem. When I get to the point where I'm installing update-kindle-prerooted.6.3.3.v1.zip in TWRP by swiping across the screen, it runs until it gets to the line thanking paulobrien and two others but then promptly freezes (or so i assume since it doesnt continue on and the loading bar halts in its tracks). I decided after a few tries to just hold the power button to get it to shut off and then booted the kindle in normal boot mode - and it worked! - despite not being able to complete the process as shown in your video. But this concerns me, as I do not have any of the additional apps shown in your video (not that this truly matters to me) and under settings -> device it shows that I am running version 6.3.1_user_#####. So I have two questions:
1) Did the fff and twrp processes work, but the 6.3.3 update fail thus enabling me to use my kindle as a v6.3.1 device again?
2) Will it harm my device in any way (e.g. re-bricking) if I just call it good and use it as it is now?
Thanks for all the help so far :highfive:
Click to expand...
Click to collapse
1 yes installing TWRP and FFF reset boot, and allowed 6.3.1 to boot normally
2. the only problem should be that, when connected to wifi, update will redownload and try again once a day or so
Kindle will reboot to TWRP, but update should fail, if that does not bother you it is fine
3. what twrp version did you install? says in twrp if you are not sure
I installed TWRP v2.7.1.0-blaze because that is what you used in the video, even though i had read that 2.2.2.1 may be preferable for stock unrooted kindle fires. I did this so that I could follow your video exactly without having to change any steps except for switching otter to blaze in the cmd promt code I inputted.
Also, as I write this, Ive realized that I still may have made a mistake and installed one of the alternate test files for the 6.3.3 prerooted update and not the complete file itself, so ill get back with that info.
Yeah, i installed the alternate test file the first time :silly:
Went back through and followed your instructions to the 'tee' again and its up and running.
I do have one more question though; when I am using the device I dont get very far before selecting an application or making another command causes the screen to go black, only displaying the time and settings option at the top and the home button, back button, search button, etc at the bottom - none of which respond when selected. This happens with both the go launcher and the kindle launcher, and each time the only way I can stop it is resetting the device... Any suggestions to counteract this?

[Q] 51.1.4.0_514006420+updated something went wrong

I downgraded to 5.1.1.0.2 fine. And installed CWM Recovery 6.0.5.1.3 (first time I've used this version, previously was using 6.0.5.1.1). And on a side note, I couldn't figure out how to mount the usb drive over hub like I had on the previous version. So I attempted to install 51.1.4.0_514006420+updated using sideload.
The file transferred fine, but when installing it gave an error saying some symlinks failed updating, and that it failed, error 7 I think it was. I didn't take a screenshot unfortunately.
I figured maybe it was due to the downgrade update still being in the /cache dir (not sure if it gets deleted when the update runs or not). But I didn't consider that maybe it wouldn't boot when I reboot now, and tried that. But it just sits on the white Amazon logo now.
Any ideas as to if it's possible to get back into recovery somehow?
What happens when your FireTV boots? You may be able to break into recovery mode with the "Alt+PrintScr+I" key combination from a USB keyboard. Take a look at this thread.
http://forum.xda-developers.com/showthread.php?t=2799779
kraqh3d said:
What happens when your FireTV boots? You may be able to break into recovery mode with the "Alt+PrintScr+I" key combination from a USB keyboard. Take a look at this thread.
http://forum.xda-developers.com/showthread.php?t=2799779
Click to expand...
Click to collapse
I did see that thread, I only have a wireless keyboard though (which does work normally) so will be getting a USB keyboard to try asap. But it mentions to press the buttons when the colored logo shows up, and mine never gets to that point, so I'm doubtful it will work :S

Bricked my Fire TV Stick 1?

Hi there!
I think I may have bricked my Fire TV Stick 1 (bought at launch in Germany)...
Current situation:
- stick turns on, shows white amazon logo on black background
- continuously rebooting; ~5s black screen, ~5s amazon logo
After months not having it used, I found out I may be able to root it by now. So I did research over the vast amount of threads and posts and was overwhelmed by the information... So I tried to get started but struggled to find the right steps and therefore maybe failed.
I updated it to 5.0.5 (stock) and tried King Root, then Kingo Root, which was a success.
I tried to use the TWRP 3.0.0-7 v2 zip and used the sh command from the respective thread (I thought that was it, since all my devices before used either TWRP or CWM).
To this point, all went through and I wanted to reboot into recovery, but there was only this generic (stock?) red text recovery screen. I waited to be sure, nothing happened and I unplugged it to reboot.
It booted fine and I reflashed the TWRP zip, in case I didn't do it properly. Again it did as expected.
I then pushed the latest prerooted 5.2.0.1 zip and rebooted to recovery, but again this generic screen, so I unplugged it early, I think.
From there on, I got stuck at the white amazon logo, see above.
I did not unlock the bootloader, adb shell confirmed it not being unlocked before.
During bootloops, I did not manage to get any control via adb or fastboot.
So, is it bricked once and for all? If not, how can I save it?
I don't care about anything stored on it.
I also have a Y-USB-OTG cable and connected a keyboard before, but could not interfere yet.
(If bricked, would a Teensy be of any use? I have one from CCast rooting days)
Thanks for reading and in advance.
I had same problem with my fire stick when used the USB power of my TV.
Did you try to power the fire stick TV with the power point and USB adapter?
l_aios said:
Hi there!
I think I may have bricked my Fire TV Stick 1 (bought at launch in Germany)...
Current situation:
- stick turns on, shows white amazon logo on black background
- continuously rebooting; ~5s black screen, ~5s amazon logo
After months not having it used, I found out I may be able to root it by now. So I did research over the vast amount of threads and posts and was overwhelmed by the information... So I tried to get started but struggled to find the right steps and therefore maybe failed.
I updated it to 5.0.5 (stock) and tried King Root, then Kingo Root, which was a success.
I tried to use the TWRP 3.0.0-7 v2 zip and used the sh command from the respective thread (I thought that was it, since all my devices before used either TWRP or CWM).
To this point, all went through and I wanted to reboot into recovery, but there was only this generic (stock?) red text recovery screen. I waited to be sure, nothing happened and I unplugged it to reboot.
It booted fine and I reflashed the TWRP zip, in case I didn't do it properly. Again it did as expected.
I then pushed the latest prerooted 5.2.0.1 zip and rebooted to recovery, but again this generic screen, so I unplugged it early, I think.
From there on, I got stuck at the white amazon logo, see above.
I did not unlock the bootloader, adb shell confirmed it not being unlocked before.
During bootloops, I did not manage to get any control via adb or fastboot.
So, is it bricked once and for all? If not, how can I save it?
I don't care about anything stored on it.
I also have a Y-USB-OTG cable and connected a keyboard before, but could not interfere yet.
(If bricked, would a Teensy be of any use? I have one from CCast rooting days)
Thanks for reading and in advance.
Click to expand...
Click to collapse
I guess you did not read enough.
At this point in time you can only root (kingoroot or kingroot) and replace root with SuperSu on a Firestick. TWRP (recovery) can not be installed because it was not released by rbox as of yet, that particular recovery\pre-rooted image is for firetv1 upgraded to OS5 and not for firestick.
Sorry man.
Have you tried to connect to a computer via USB and run kingoroot or kingroot for windows (whatever you used)? It is a small chance that will recover but it is a slim one....
mjnman said:
I had same problem with my fire stick when used the USB power of my TV.
Did you try to power the fire stick TV with the power point and USB adapter?
Click to expand...
Click to collapse
I could not remember, so I just retried it with two different chargers and two different cables (both used to power my Nexus 5).
Unfortunately resulting in the very same loop... But thanks nonetheless.
bula1ca said:
I guess you did not read enough.
At this point in time you can only root (kingoroot or kingroot) and replace root with SuperSu on a Firestick. TWRP (recovery) can not be installed because it was not released by rbox as of yet, that particular recovery\pre-rooted image is for firetv1 upgraded to OS5 and not for firestick.
Sorry man.
Have you tried to connect to a computer via USB and run kingoroot or kingroot for windows (whatever you used)? It is a small chance that will recover but it is a slim one....
Click to expand...
Click to collapse
Dang... Usually I don't make mistakes this dumb. Guess I learned my first lesson. I'll try to trace my mistake though, for future attempts.
I rooted it with the Kingo app, I think, and got that typical "stuck at 90%" and rebooted it like others did. It rebooted fine and Kingo verified it rooted.
I did not use Windows, I use Ubuntu, occasionally with Wine, yet I had no luck passing USB devices to it. (And always these missing libs...)
Normally, adb and fastboot (console) work fine (i.e. with my phone).
Now I have no chance to interfere with the bootloop, I think.
IIRC, sometimes I could spam commands and at one point adb was stuck at "waiting for device".
I tried to reproduce it just now, but could not get it again.
So, should I try adb or fastboot on another computer to be sure?
Would King(o) for Windows be of any help at this point? If so, what would be my best bet to catch it at some point I can recover it?
Is there any other way I could try? From my nooby perspective, could the bootsplash be an entrance for fastboot? Could it be just stuck trying to access erroneous partitions?
At this point I would try the most crazy and risky idea, since it is unusable anyway.
Thanks both of you for your answers.
l_aios said:
I could not remember, so I just retried it with two different chargers and two different cables (both used to power my Nexus 5).
Unfortunately resulting in the very same loop... But thanks nonetheless.
Dang... Usually I don't make mistakes this dumb. Guess I learned my first lesson. I'll try to trace my mistake though, for future attempts.
I rooted it with the Kingo app, I think, and got that typical "stuck at 90%" and rebooted it like others did. It rebooted fine and Kingo verified it rooted.
I did not use Windows, I use Ubuntu, occasionally with Wine, yet I had no luck passing USB devices to it. (And always these missing libs...)
Normally, adb and fastboot (console) work fine (i.e. with my phone).
Now I have no chance to interfere with the bootloop, I think.
IIRC, sometimes I could spam commands and at one point adb was stuck at "waiting for device".
I tried to reproduce it just now, but could not get it again.
So, should I try adb or fastboot on another computer to be sure?
Would King(o) for Windows be of any help at this point? If so, what would be my best bet to catch it at some point I can recover it?
Is there any other way I could try? From my nooby perspective, could the bootsplash be an entrance for fastboot? Could it be just stuck trying to access erroneous partitions?
At this point I would try the most crazy and risky idea, since it is unusable anyway.
Thanks both of you for your answers.
Click to expand...
Click to collapse
Do you still have root? Is your stick responding to the su command?
If so read this post: http://forum.xda-developers.com/fire-tv/help/guidance-recovering-bootloop-firetv-t3446902
If not:
Try kingoroot for windows however it is a slim change in my opinion as you wrote a FireTv image to your FireStick.
Copy and paste from: http://forum.xda-developers.com/fire-tv/development/guide-fire-stick-replace-king-o-root-t3440923
"IF YOU RUN INTO SOFTBRICK ISSUE (stuck at fire tv logo)
Make sure you have ADB drivers properly installed in your windows pc/laptop.
connect a genuine usb lead to the firestick/pc.
download the windows version of KINGO ROOT and install it.
open KINGO ROOT on the pc with Fire Stick connected up to pc and tv.
wait for the button to pop up and click root.
if you dont see AFTV or get enable debugging in the KINGO ROOT program on pc/laptop please unplug the stick from usb and replug it back in.
if this still wont work restart the pc/laptop or try another pc/laptop.
you should after clicking root boot back up into your homescreen, if it doesnt boot back into your homescreen automatically, wait around 5 minutes and unplug usb and re-plug it again. "
bula1ca said:
Do you still have root? Is your stick responding to the su command?
If so read this post: http://forum.xda-developers.com/fire-tv/help/guidance-recovering-bootloop-firetv-t3446902
If not:
Try kingoroot for windows however it is a slim change in my opinion as you wrote a FireTv image to your FireStick.
Copy and paste from: http://forum.xda-developers.com/fire-tv/development/guide-fire-stick-replace-king-o-root-t3440923
"[...]"
Click to expand...
Click to collapse
Thanks for the links, but from what I see, I need to get past the bootloader splash for adb to work. I'm stuck at the white "amazon" splash, not the colored "FireTV Stick" splash after the amazon one.
Sorry for not making it clear (and for that amount of text that maybe hid it)...
From what I understand and recall, I did only flash the recovery, right? Or does it automatically flash the zip I pushed to internal storage?
And what confuses me, the first attempt booting into recovery AFTER flashing the wrong one I got the former mentioned screen with red text. Reboot worked and the Stick was running. So I did retry and got the same red text after rebooting to recovery. I assumed it did not flash again and unplugged it earlier than the first attempt. Since then it got stuck at the white bootsplash.
Since I am still a noob, it seems to me the system wasn't touched, maybe a faulty recovery integrity forcing the bootloader to loop.
l_aios said:
Thanks for the links, but from what I see, I need to get past the bootloader splash for adb to work. I'm stuck at the white "amazon" splash, not the colored "FireTV Stick" splash after the amazon one.
Sorry for not making it clear (and for that amount of text that maybe hid it)...
From what I understand and recall, I did only flash the recovery, right? Or does it automatically flash the zip I pushed to internal storage?
And what confuses me, the first attempt booting into recovery AFTER flashing the wrong one I got the former mentioned screen with red text. Reboot worked and the Stick was running. So I did retry and got the same red text after rebooting to recovery. I assumed it did not flash again and unplugged it earlier than the first attempt. Since then it got stuck at the white bootsplash.
Since I am still a noob, it seems to me the system wasn't touched, maybe a faulty recovery integrity forcing the bootloader to loop.
Click to expand...
Click to collapse
I have no idea what you did however it will not automatically flash your zip, problem is you installed TRWP that was not meant for Firestick and overwrote its booting sequence. You most probably would had recover from your first attempt by re-installing a new image but once you tried to install it again it most probably finished writing the whole thing and damaged booting sequence.
bula1ca said:
I have no idea what you did however it will not automatically flash your zip, problem is you installed TRWP that was not meant for Firestick and overwrote its booting sequence. You most probably would had recover from your first attempt by re-installing a new image but once you tried to install it again it most probably finished writing the whole thing and damaged booting sequence.
Click to expand...
Click to collapse
Yeah, sad thing I got the wrong device, should have taken my time even more...
I googled the screen I got to two times before getting stuck:
http://forum.xda-developers.com/showpost.php?p=65968901&postcount=60
First time I waited approx. 15 minutes before pulling the plug to reboot. Since I noticed no difference I tried again and got the same screen. But this time I pulled the plug earlier, <1 minute.
I'd like to add that my bootloader was locked. Can I damage the booting sequence by corrupting the recovery or was my mistake that major to be able to do that?
I googled some key combinations to get into recovery or to bypass it, but I don't know if I get the right keys.
With my remote control I don't think I have enough time to hold the keys. Additionally I have a USB keyboard (Cherry KC1000; if possible, which keys btw?) and may be able to connect it via powered Y OTG cable.
So if anyone got any further input or ideas for me to rescue my FTVS, I'd be glad to receive it.
Thanks to all.
Anyone else maybe an idea?
The thing is, I cannot believe it is unsavable.
To summarize the current state (please see full details above):
- stuck in bootloop, white amazon logo
- flashed wrong recovery, after first flash the system booted, after second flash it got stuck (characteristics above)
- never flashed anything other than recovery
Strange thing it booted in first place, but now it refuses. Also I got the screen I mentioned above and unplugged as described above.
Can I possibly bypass the recovery check and try to boot directly to system? Or maybe interrupt for fastboot access?
If connected to PC, can you see it thru 'lsusb'? Or 'dmesg | tail'?
Kramar111 said:
If connected to PC, can you see it thru 'lsusb'? Or 'dmesg | tail'?
Click to expand...
Click to collapse
I tried both
watch -n 0.5 'dmesg | tail'
and
watch -n 0.5 'lsusb'
but with no identification whatsoever.
I double-checked with my Nexus 5 on the same port with the same cable, it identified fine.
One last bump for ideas before putting it into the trash.

Have I bricked my FTV 4K stick beyond repair?

Sorry if this is posted in the wrong section, I am never quite sure where these sort of queries should go
To cut a long story short I unlocked and rooted 1 of my FTV 4K sticks, I was struggling with an issue on 1 and ended up installing a Magisk update. I know there are warning all over the forum about this please put it down to a lack of experience.
On reboot it just comes up with the black screen and the white amazon logo, it stays on this for about 2 minutes then restarts to the same black screen. i.e. its caught in a boot loop. It never gets to the white amazon screen.
I bought myself an OTG cable thinking this would get me to twrp so I could go into recovery and wipe it and start again or something, but even with the OTG cable plugged in it still does exactly the same thing. I have tried the same OTG cable and entertainment keyboard setup on another FTV 4K stick and it gives me the 5 second boot menu to get into recovery.
I am guessing I have killed it beyond repair? Is there anything else I can try to do?
Thanks
you need a usb keyboard and then you need to press a combination shown on youtube: , Don't be afraid it is very hard to do it but i can confirm it works 100% for sure!! The timing for holding the key press is all that matters to be successfully...
Try different timings if it's not working on the first run but you need then to hold the buttons for very long time until your fingers feel dead....
..im not sure if adb is working in "safe mode" you need to test that. If yes - you could use "adb reboot recovery".
2. you need to reflash Magisk in core mode.
Aq
dougie175 said:
Sorry if this is posted in the wrong section, I am never quite sure where these sort of queries should go
To cut a long story short I unlocked and rooted 1 of my FTV 4K sticks, I was struggling with an issue on 1 and ended up installing a Magisk update. I know there are warning all over the forum about this please put it down to a lack of experience.
On reboot it just comes up with the black screen and the white amazon logo, it stays on this for about 2 minutes then restarts to the same black screen. i.e. its caught in a boot loop. It never gets to the white amazon screen.
I bought myself an OTG cable thinking this would get me to twrp so I could go into recovery and wipe it and start again or something, but even with the OTG cable plugged in it still does exactly the same thing. I have tried the same OTG cable and entertainment keyboard setup on another FTV 4K stick and it gives me the 5 second boot menu to get into recovery.
I am guessing I have killed it beyond repair? Is there anything else I can try to do?
Thanks
Click to expand...
Click to collapse
You haven't killed your stick, install fastboot drivers and app.
Connect your stick to your pc via usb.
Enter
Code:
fastboot devices
when you see black screen with amazon logo, it should be inside fastboot mode
(If somehow you flashed update to boot.img as written in the guide)
If you see the stick in fastboot mode,
Pull twrp from kamakiri.zip
Place it in fastboot folder
Enter
Code:
fastboot flash boot boot.img
(boot.img or whatever the name of your twrp image)
Code:
fastboot reboot recovery
It should work, if not you can use shorting method again.
Thanks very much both, I will have a play around this evening when I get home from work and the kids are in bed, hopefully with the info above I can get back to recovery again.
Thanks for the help gents, in the end I had to do the shorting method to get the stick to do anything. It took about 6 attempts before kamakiri script even registered it as anything being plugged in, it just kept saying wait for boot.
Once it realised the stick was present and shorted I was away though, I have ended up having to factory reset and wipe everything so will need to start again with it but I am just pleased I don’t need to shell out again for a new stick.
Thanks again for your help

Fire TV Stick (2nd Gen) looping - can't use any of the usual methods.

I have a FTVS 2nd gen. When I boot it, I get the Amazon logo, then a brief black screen, then the "Fire TV . . ." screen.
Then, it goes to "Optimising system storage and apps - this may take up to ten minutes". It takes a lot longer than this; then it reboots. Rinse and repeat.
I have an OTG "Y" cable with a logitech K360 wireless keyboard (confirmed working), and a working remote paired to the stick.
I have tried "Back and right" held down throughout the entire boot process with zero response from the stick; I have tried ALT-FN-PrtSc-I repeatedly during the whole time it's on; I have also got funky and tried ALT Gr-FN-PrtSc-I, Alt-FN-Insert-I, and have tried throwing "CTRL" into the mix a few times too.
Nothing elicits any response from the stick. I don't think that the stick gets to the point of firing up the network stack, so there's no ADB via wifi; and of course I can't enable debugging via USB so there's no ADB by USB either.
Is there any way I can proceed? It's so old I don't mind opening it up if I have to, but that's a last resort.
TIA for informed responses.
dossvidanya said:
I have a FTVS 2nd gen. When I boot it, I get the Amazon logo, then a brief black screen, then the "Fire TV . . ." screen.
Then, it goes to "Optimising system storage and apps - this may take up to ten minutes". It takes a lot longer than this; then it reboots. Rinse and repeat.
I have an OTG "Y" cable with a logitech K360 wireless keyboard (confirmed working), and a working remote paired to the stick.
I have tried "Back and right" held down throughout the entire boot process with zero response from the stick; I have tried ALT-FN-PrtSc-I repeatedly during the whole time it's on; I have also got funky and tried ALT Gr-FN-PrtSc-I, Alt-FN-Insert-I, and have tried throwing "CTRL" into the mix a few times too.
Nothing elicits any response from the stick. I don't think that the stick gets to the point of firing up the network stack, so there's no ADB via wifi; and of course I can't enable debugging via USB so there's no ADB by USB either.
Is there any way I can proceed? It's so old I don't mind opening it up if I have to, but that's a last resort.
TIA for informed responses.
Click to expand...
Click to collapse
Yes you can follow the thread "Unlock Root Twrp Unbrick Firetv Stick Tank" and once youve unlocked and rooted, flash a new fimware and start fresh.
Something has became corrupted in your sticks /system folder. Just take your time and follow the steps to the letter and dont be scared to ask for help if you get stuck.
Regards
Bertonumber1 said:
Yes you can follow the thread "Unlock Root Twrp Unbrick Firetv Stick Tank" and once youve unlocked and rooted, flash a new fimware and start fresh.
Something has became corrupted in your sticks /system folder. Just take your time and follow the steps to the letter and dont be scared to ask for help if you get stuck.
Regards
Click to expand...
Click to collapse
Thank you my man, much appreciated!
OK, a combination of my shakes and my traditional mini soldering iron (HUGE compared to this circuit) I am unable to complete step 2 which is to short the CLK line to GND. At the risk of damaging my stick, I've given up.

Categories

Resources