Related
Hey guys my name is Vito, even though this is my first post I have been reading Xda developers forums for a while. More than a year ago I bricked my first generation Kindle Fire and ever since been trying to unbrick it. These days i have a new version of kindle fire but from time to time i get back into trying to fix the old tablet without succeeding. I've read many threads on this forum in regards to Kindle Fire trouble shooting and used the search button dozens of times so i hope i don't repeat an existing threads. I am posting here as my last resort to try to trouble shoot the problem and get some experienced advice to hopefully fix the tablet because i failed trying to fix it on my own.
My kindle fire 1st gen has been rooted, it has FireFireFire bootloader v1.4a and working TWRP v2.2.2.1 also I got factory cable and otg cable, and USB debugging Disabled, No ROM,
How I bricked it: One day i was playing with an operating system tuning application and after pressing auto tune kindle fire either froze or shut down and when i power it back on it would just freeze on "booting, with blue kindle fire logo". That's where i made a few mistakes i believe, instead of researching xda developers forum thoroughly i went into TWRP and wiped cache, dalvik cache, factory reset, and unfortunately system (ROM) however i did not wiped the external storage so that still there. Also USB debugging was disabled on my kindle fire at the time i bricked the device.
What I tried to fix it: I tried to install and re install many different kindle fire drivers for windows on at least 4 different computers and operating systems ( XP, WIN7, WIN8 ) but my kindle fire would not be detected and adb would not work, also tried going trough guides on installing Android SDK and getting ADB working but now i know that i wont be able to get ADB working without having USB debugging enabled.
So i ended up with only one option Fastboot. I tried installing Ubuntu on one of the computers with soupkit but linux would not recognize kindle fire being connected, it would always say waiting for device, same thing would be if i log on to ubuntu from flash drive boot.
Also when i type # lsusb command in ubuntu command prompt it gives me all usb ports and connected devices but kindle fire does not get detected in any mode while my new kindle fire does get detected in ubuntu once connected.
When i get into fastboot mode and i type # fastboot getvar product every time i get < waiting for device >.
So that's about it, all the above i tried and re tried hoping to get it going but im either doomed or im just doing something wrong or missing something all the way which is possible. I would really appreciate anyone's help and feedback on this post and would really love to just try to figure this thing out.
Thank you.
Vito,
I am new and far from an expert, however, I just discovered if you have TWRP, there is an option to mount the sdcard space and copy files. Not sure about the version you have but give it a try:
- Connect USB to PC
- Boot on TWRP
- Mount sdcard
- copy ROM (make sure you use one that works with your TWRP version and whatever other software is there)
- install ROM
Like I said, far from expert, but I believe all you need is a ROM.
pokeys fire kit should sort it. im back in 2 hours. i can help you then
Sent from my Nexus 5 using Tapatalk
pm me when your online
shabuboy said:
Vito,
I am new and far from an expert, however, I just discovered if you have TWRP, there is an option to mount the sdcard space and copy files. Not sure about the version you have but give it a try:
- Connect USB to PC
- Boot on TWRP
- Mount sdcard
- copy ROM (make sure you use one that works with your TWRP version and whatever other software is there)
- install ROM
Like I said, far from expert, but I believe all you need is a ROM.
Click to expand...
Click to collapse
Thanks for replying, my TWRP version has that option to mount sdcard but unfortunately it does not work, if only it did
lovejoy777 said:
pokeys fire kit should sort it. im back in 2 hours. i can help you then
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Hey Lovejoy777, thanks for the help, I will send you PM.
it does not mount it? Or it does not show on Windows? If it is the Windows part, you probably need the drivers. I used Kindle Fire Utility v0.9.9.zip.
This also helped me after rooting my device.
http://forum.xda-developers.com/showthread.php?t=2308295
and sorry, this is where my expertise ends
Hi All,
Today I should be picking up a KF2 (Kindle Fire 2nd Gen) today from a friend. And although I have experience with this device in the past, as I rooted one a while ago, and installed Google PlayStore bits and bobs for another friend... This was a while back.
A few months back, I read somewhere although cannot find it now... That Amazon have rolled out a serious Update to most Kindles (KF2, KF-HD, and possibally KF-HDX) that has updated the baseband/kernel to a certain version. Which prevents Unlocking, and tampering with it could cause the device to Hard Brick...
So was wondering, what is the best procedure to tackle this? Easy method to Root / Recovery??
And what does this 2nd BootLoader actually do?? Does it allow you to DualBoot both original stock Kindle firmware as well as second partition for Custom Roms??
Thanks, Lister
OK first off which kindle do you have, because a kf2 is. Of a 2nd gen kfhd. If its a 2013 kindle fire HD, don't bother with second bootloader because it will just brick it. If it is in fact a kf2 then here's what second d bootloader does. Basically we can't unlock our devices bootloader so 2nd bootloader is a workaround. It allows us to run our own unsigned kernels and custom recovery. Once we have that we can flash a custom ROM like cm. And no no dual booting, Amazon's os is too different from cm to be able to.
To install 2nd bootloader + twrp you must be rooted, suggest kindle fire first aid for that, there's a tutorial in the dev section for kf2 for installing second bootloader + twrp here.
Make sure you check the md5sum of the bootloader before flashing it so you don't risk hard bricking, also I suggest putting the ROM and its gapps on the kindle ahead of time if your are running 10.4.8 because it will boot loop into recovery after the process until you flash a different rom, so its easier to have the ROM o. Ahead of time rather than "adb push" it.
Sent from my Amazon Kindle Fire HD using Tapatalk
Hi @stunts513,
Sorry for the delay getting back to you, my friend didnt bring the device in until yesterday...
I can confirm that it is a Kindle Fire 2nd Gen (Otter2), and it is running 10.4.6 firmware/baseband...
I tried to root it in work, on my Windows 8.1 and Windows 7 based PCs, and unfortunately it wasn't detecting it, or working with the ADB drivers....
I tried at home on my Windows XP and Vista setup, and again wasn't detecting it. However it did detect on my Windows 7 setup at home (triple boot). This must of been the partition I used for my friends one many months ago... (although I found various Kindle related files on each partition).
Anyway, I got the damn thing rooted now, thankfully... and shall move onto the 2nd Bootloader thing... However, is there any other way, or easy way of doing this other than whats in that post?? I don't mind doing it, and will follow it again. However late last night I was losing the will to live as it was hard work getting to do things... (compared to other Android devices that are a breeze to do...).
I tried to backup my partitions on the Kindle what it says to do at the start, and it kept saying it couldnt find these on the Kindle... I read in the guide that it said I could download them from a website, but all I could see was scripts and not backup partitions... Is it really important to backup my own ones, or could I just download someone else's Kindle Fire 2nd (8Gb) model??
And yeah, is there any other way to get custom recovery / rom on, other than the original guide...?? - not gonna give up, just last night kept falling asleep trying to follow it... when things werent working and patiently waiting for things to happen/work... lol
Anyway, thanks so much for replying to my question, and for all the help you have given me to get me started... much appreciated!!
Thanks, Lister
Lister Of Smeg said:
Hi @stunts513,
Sorry for the delay getting back to you, my friend didnt bring the device in until yesterday...
I can confirm that it is a Kindle Fire 2nd Gen (Otter2), and it is running 10.4.6 firmware/baseband...
I tried to root it in work, on my Windows 8.1 and Windows 7 based PCs, and unfortunately it wasn't detecting it, or working with the ADB drivers....
I tried at home on my Windows XP and Vista setup, and again wasn't detecting it. However it did detect on my Windows 7 setup at home (triple boot). This must of been the partition I used for my friends one many months ago... (although I found various Kindle related files on each partition).
Anyway, I got the damn thing rooted now, thankfully... and shall move onto the 2nd Bootloader thing... However, is there any other way, or easy way of doing this other than whats in that post?? I don't mind doing it, and will follow it again. However late last night I was losing the will to live as it was hard work getting to do things... (compared to other Android devices that are a breeze to do...).
I tried to backup my partitions on the Kindle what it says to do at the start, and it kept saying it couldnt find these on the Kindle... I read in the guide that it said I could download them from a website, but all I could see was scripts and not backup partitions... Is it really important to backup my own ones, or could I just download someone else's Kindle Fire 2nd (8Gb) model??
And yeah, is there any other way to get custom recovery / rom on, other than the original guide...?? - not gonna give up, just last night kept falling asleep trying to follow it... when things werent working and patiently waiting for things to happen/work... lol
Anyway, thanks so much for replying to my question, and for all the help you have given me to get me started... much appreciated!!
Thanks, Lister
Click to expand...
Click to collapse
As far as i know offhand that method for the kf2 is the only method, which is kinda sad because its the same manual method as the other hd's, and the hd's have fireflash, but fireflash never had the support added in for the kf2 for some reason last i checked. I wouldn't worry too much about the backups, once you run the dd command on the partitions to store them on the sdcard folder, then even if adb pull doesn't work you can always copy them over mtp. i don't like how adb pull works on windows. Only image i would be concerned with storing is the boot0block.
If i made some incorrect references its probably because i vaguely remember it maybe having a different command than the hd model, but the hd's backup command would work on a kf2 as well.
Hi @stunts513,
Just wanted to say THANK YOU SO MUCH!!!
With your help, you have helped me accomplish what seemed like a scary trip to KindleFire Bricks'ville...
But thanks to you, I am all rooted, TWRP'd and ready to go... Shall flash a rom, and sort dads Birthday Pressie now...
Really appreciated, top guy!! thank you... Lister
stunts513 said:
As far as i know offhand that method for the kf2 is the only method, which is kinda sad because its the same manual method as the other hd's, and the hd's have fireflash, but fireflash never had the support added in for the kf2 for some reason last i checked. I wouldn't worry too much about the backups, once you run the dd command on the partitions to store them on the sdcard folder, then even if adb pull doesn't work you can always copy them over mtp. i don't like how adb pull works on windows. Only image i would be concerned with storing is the boot0block.
If i made some incorrect references its probably because i vaguely remember it maybe having a different command than the hd model, but the hd's backup command would work on a kf2 as well.
Click to expand...
Click to collapse
Rooting KF2
Can you give a list of the links that you used to root you KF2?
I've tried to connect to my with ADB but I can't get it to see my device. I can connect my KF2 to my WINXP machine, and transfer files, but I can't get ADB to recognize the device, and I can't get any root options to work. Any help would be appreciated. Ultimately I would like to install a new ROM like CM, but until I can do the basics, I can't get that done.
You should check to see if it has the driver installed for adb in the device manager, if it doesn't even show up as a adb device in device manager you probably haven't turned USB debugging on on the kindle itself.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
You should check to see if it has the driver installed for adb in the device manager, if it doesn't even show up as a adb device in device manager you probably haven't turned USB debugging on on the kindle itself.
Click to expand...
Click to collapse
Checked and verified that USB debugging is in fact turned on on my kindle.
Settings>>Security>>Enable ADB is ON.
Settings>>Device>>Allow Installation of Applications is ON
I still can't get adb to recognize my device.
I installed ADB from adt-bundle-windows-x86-20140321.zip if that makes any difference.
I had read in the forums that I might need a special cable for fastboot. Is that what I'll need to get?
For what it's worth, I just found and followed this tutorial:
EDIT: Well crap, this forum won't let me post the outside url. I guess if you search for "Setting up ADB driver for Kindle Devices" by David Isbitski" on developer dot amazon dot com, you will be able to find the tutorial
It was very helpful, and it was the first tutorial I've found that actually showed how to install adb windows drivers for the kindle fire.
In windows Device Manager >> Portable Devices >> Kindle is installed, then uninstall Kindle, as they are the wrong drivers.
In the SDK Manager
Go to TOOLS >> Manage Add On Sites
Go to the User Defined Sites tab
add the url found in the tutorial listed above, save and quit that window.
Back at the manager, do "Packages >> Reload" to update the list.
For the kindle fire 2nd generation, I had to expand "Android 4.0.3 (API 15) to find and install:
"Kindle Fire 2nd Generation"
Under Extras, install:
Amazon AVD Launcher (Windows)
Kindle Fire Device Deffinitions
Kindle Fire USB Driver
Once installed go to \extras\amazon\kindle_fire_usb_driver and run "KindleDrivers.exe"
You should then find "Device Manager >> Kindle Fire >> Android Cmposite ADB Interface"
You can then stop/start adb, then do a adb devices.
That is what worked for me!
New to the forum and trying to recognize what you are doing here......
I have a Kindle Fire 2nd Gen with 10.4.8 SW installed. Would like to dump a much newer Android version on it and looking for the correct path.
Any help is greatly appreciated.
Thanks
Alright So i rooted my fire tv stick v5.0.5, with kingroot 4.82, everything was working perfect, i blocked ota updates, and i froze the fireTV Home, and used firestarter. I rebooted the fire tv and it rebooted perfect, still had root, everything was great! I wanted to connect my playstation controller to it, but i couldnt access the fire tv settings because i froze the fire tv home and the built in settings is part of the fire tv home, i tried to install regular settings.apk, i tried several different ones but it would just fail installing, i thought my regular settings was interfering with it, so i backed it up and froze the fire tv settings just to try to install regular android settings afterward, and i rebooted the stick. Now my stick is stuck at the fire stick logo and wont boot, im sure its because i froze the settings, since it booted fine with root before i froze that, and that was the only change i did. Anyone got any ideas on how i can fix it?
Any help is greatly appreciated!
Thanks,
Deershoot3r
I had the same issue with the FireTv Stick but another os.
I had a hardware rooted FireTv-Stick on Software: 54.1.1.0_user_110031420. That means FireOS 3, not FireOS 5.
Yesterday I let the stick push some file with ES-File-Explorer to my NAS. In this process the system restart (I think because to much power consumption and less powerfull usb port yesterday).
Now it does not start anymore. @deershoot3r
Perhaps we had a chance to get our sticks back by flashing a stock-rom from amazon.
Once I read something about fastboot and recovery possibilities.
At first you should load your stock-rom from here: http://www.aftvnews.com/software/
Perhaps we can connect a usb cable and start fastboot, see here: http://forum.xda-developers.com/showpost.php?p=57308281&postcount=6
Greetings by I_did_it_just_tmrrow
I_did_it_just_tmrrow said:
I had the same issue with the FireTv Stick but another os.
I had a hardware rooted FireTv-Stick on Software: 54.1.1.0_user_110031420. That means FireOS 3, not FireOS 5.
Yesterday I let the stick push some file with ES-File-Explorer to my NAS. In this process the system restart (I think because to much power consumption and less powerfull usb port yesterday).
Now it does not start anymore. @deershoot3r
Perhaps we had a chance to get our sticks back by flashing a stock-rom from amazon.
Once I read something about fastboot and recovery possibilities.
At first you should load your stock-rom from here: http://www.aftvnews.com/software/
Perhaps we can connect a usb cable and start fastboot, see here: http://forum.xda-developers.com/showpost.php?p=57308281&postcount=6
Greetings by I_did_it_just_tmrrow
Click to expand...
Click to collapse
Actually i tried this, i cannot connect to it through fastboot, because the fire tv will not get past the "FireTv Stick" logo, any suggestions? am i doing something wrong?
deershoot3r said:
Actually i tried this, i cannot connect to it through fastboot, because the fire tv will not get past the "FireTv Stick" logo, any suggestions? am i doing something wrong?
Click to expand...
Click to collapse
fastboot kicks in as soon as you power off your unit, if you get to the amazon logo it is already too late however fastboot will not work for you anyway as your firestick boot loader is locked.
Please push my amazon community topic:
https://www.amazon.com/forum/fire/r...orum=Fx2L8EBNTOXFSA7&cdThread=Tx2LHG0S7L0Y9MK
Perhaps amazon help us and provide a solution!
But I need you guys!
Greetings by Idijt
Edit:
By the way, here is a thread in the Amazon developer Account, asking for a way to unbrick devices in an officially way:
https://forums.developer.amazon.com/forums/thread.jspa?threadID=11981&tstart=0
We should Support it by pushing this thread.
Greetings by Idijt
Looks like I bricked my fireTV Stick today.
What i did: After i updated to 5.2.1.0 I rooted with Kingo Root. I checked if everything was still running fine, which was the case.
Then i removed Kingo Root App and the superuser app that came with Kingo Root. I installed Chainfires latest supersu.apk which did not work (immediately crashed after start). Then i downloaded older version v1.97 of chainfires supersu. This version did not crash directly after starting it. It asked to update the su binary, which I accepted. Unfortunately it did not seem to work, that's why i rebooted the stick after some minutes.
Now it stucks at the "fireTV stick" logo.
Connection to adb works if i connect the Stick to my PC.
Is there anything i can try? Is there a way to factory reset via adb or anything like that?
Bierfreund said:
Looks like I bricked my fireTV Stick today.
What i did: After i updated to 5.2.1.0 I rooted with Kingo Root. I checked if everything was still running fine, which was the case.
Then i removed Kingo Root App and the superuser app that came with Kingo Root. I installed Chainfires latest supersu.apk which did not work (immediately crashed after start). Then i downloaded older version v1.97 of chainfires supersu. This version did not crash directly after starting it. It asked to update the su binary, which I accepted. Unfortunately it did not seem to work, that's why i rebooted the stick after some minutes.
Now it stucks at the "fireTV stick" logo.
Connection to adb works if i connect the Stick to my PC.
Is there anything i can try? Is there a way to factory reset via adb or anything like that?
Click to expand...
Click to collapse
Connect your fire stick to a windows pc/laptop. (i used windows 10 64bit)
Let the drivers install.
Download the windows version of Kingo root.
Click root, try this a couple of times (it probably will fail and stick at 70 percent)
unplug the stick and try again, when it hits 70 percent again plug your hdmi lead in (already connected to tv)
It should root and write back the correct su files.
If you want to unroot, install kingo and super user again on the fire stick then either use the unroot feature in super user app (you will have to purchase mouse toggle for fire tv, if you havent got it already to navigate to the 3 little dots menu icon top right corner)
Or re plug it into windows pc/laptop and unroot through the windows tool.
Worked! Did not know, that there's also an windows application for Kingo root.
So it's better to not use another superuser app when rooting the fireTV (stick) with Kingo root?
Thanks sconnyuk. I have a bricked Stick from the Feb. KingRoot -> SuperSUMe disaster. Tried a lot of things, no luck.
But the Windows KingoRoot worked on the first try. (No 70% stoppage or anything.) I now have a root shell over adb. I'm going to wait on a rooted ROM to get it back to a normal state, but at least now I have hope.
Bierfreund said:
Worked! Did not know, that there's also an windows application for Kingo root.
So it's better to not use another superuser app when rooting the fireTV (stick) with Kingo root?
Click to expand...
Click to collapse
Just use Kingo roots superuser. Im going to try a few different su versions later see if I have any luck.
At the moment any other than kingoroots will brick, (caun unbrick if in this situation so I guess anyome can try)
---------- Post added at 05:53 PM ---------- Previous post was at 05:52 PM ----------
ftgftg said:
Thanks sconnyuk. I have a bricked Stick from the Feb. KingRoot -> SuperSUMe disaster. Tried a lot of things, no luck.
But the Windows KingoRoot worked on the first try. (No 70% stoppage or anything.) I now have a root shell over adb. I'm going to wait on a rooted ROM to get it back to a normal state, but at least now I have hope.
Click to expand...
Click to collapse
No need to wait. Try this guide ive put together, just do it over usb. Cant see why I wouldnt work.
http://forum.xda-developers.com/fire-tv/development/fire-tv-stick-downgrade-firestarter-3-2-t3399298
sconnyuk said:
Connect your fire stick to a windows pc/laptop. (i used windows 10 64bit)
Let the drivers install.
Download the windows version of Kingo root.
Click root, try this a couple of times (it probably will fail and stick at 70 percent)
unplug the stick and try again, when it hits 70 percent again plug your hdmi lead in (already connected to tv)
It should root and write back the correct su files.
If you want to unroot, install kingo and super user again on the fire stick then either use the unroot feature in super user app (you will have to purchase mouse toggle for fire tv, if you havent got it already to navigate to the 3 little dots menu icon top right corner)
Or re plug it into windows pc/laptop and unroot through the windows tool.
Click to expand...
Click to collapse
Thanks for the tutorial. But it doesn't work for me. I have and old fire stick TV with 5.0.5 that I bricked with KingRoot (not Kingo) -> SuperSUMe. I tried to follow your steps and KingoRoot goes to 100% at the first time. But when I connect the stick to my PC it's still stucks at the FireTV Logo . I don't know if I followed some step wrong.
PS: Sorry for my bad english.
SrTommy said:
Thanks for the tutorial. But it doesn't work for me. I have and old fire stick TV with 5.0.5 that I bricked with KingRoot (not Kingo) -> SuperSUMe. I tried to follow your steps and KingoRoot goes to 100% at the first time. But when I connect the stick to my PC it's still stucks at the FireTV Logo . I don't know if I followed some step wrong.
PS: Sorry for my bad english.
Click to expand...
Click to collapse
Try multiple times with Kingoroot, You can try windows version of KING root multiple times also.
Failing this you can try to run both programs simultaneously.
Good luck
sconnyuk said:
Try multiple times with Kingoroot, You can try windows version of KING root multiple times also.
Failing this you can try to run both programs simultaneously.
Good luck
Click to expand...
Click to collapse
It finally works!!!...... almost
Now the sticks pass the fire tv logo, but takes a lot of time to open the firestarter menu. And I can't do anything there. The remote doesn't response. I try to do a factory reset to the stick but I can't find the way . Thank you anyway. At least I can escape from the loop at boot.
SrTommy said:
It finally works!!!...... almost
Now the sticks pass the fire tv logo, but takes a lot of time to open the firestarter menu. And I can't do anything there. The remote doesn't response. I try to do a factory reset to the stick but I can't find the way . Thank you anyway. At least I can escape from the loop at boot.
Click to expand...
Click to collapse
Try removing the batteries and re-pairing the remote, try this multiple times as it has happened to me before.
sconnyuk said:
Try removing the batteries and re-pairing the remote, try this multiple times as it has happened to me before.
Click to expand...
Click to collapse
I thought that I had edited my previous post but it seems that it didn't save the changes. Finally I could restore my fire stick following your downgrade guide. I reinstalled the firmware 5.0.5 and everything works perfect. Thanks a million!!!
SrTommy said:
I thought that I had edited my previous post but it seems that it didn't save the changes. Finally I could restore my fire stick following your downgrade guide. I reinstalled the firmware 5.0.5 and everything works perfect. Thanks a million!!!
Click to expand...
Click to collapse
Your welcome.
Glad I could help.
Hi,
I tried to install XPosed to be able to install Google Play store later following a guide I successfully used on my rooted FTV 1st gen.
XPosed installation went fine but probably I deleted some user file I had not and box started checking for updates. I stopped the process in the meantime. Nothing seems to be affected. Root is still in place and firmware version is still 5.0.5. BUT each time a reboot my stick now it asks to pair my remote, then asks me to choose a language as it wants to complete an update. Just when I goes further it says that it has not been possibile to complete update. I tried to "downgrade" with a clear 5.0.5 firmware zip. It went fine but I had to disable OTA again to avoid the online updates. So it still fails to check for updates and each time it tries to reinitialize update process. basically default amazon launcher doesnt work anymore but it's not a issue cause I have Firestarter 3.3 which works fine. The worst issue is that each time I reboot it asks for rempote pairing and I can't use amazon video anymore. Basically I'd like to remove this "checking for update" process and return to my actual rom. Is that possibile?
Thanks.
puppinoo.
Hoping someone can help me out. My stick is bricked. I loaded up the Kingoroot and tried to run the steps to recover it. However i dont think it's recognize the device since kingoroot is stuck at the loading page. Which driver files did you install for the fire stick? thanks.
Bricked fire stick- any advice
I tried to transfer a ustv4.0 APK zip file to the firestick via USB after some extensive instructions on YouTube video but found that using Google Drive with ES File Explorer would be the quick and easy method. I also got lost in the instructions after downloading ADB and fire starter. When plugging the firestick back into the TV to go the ES file route, the firestick doesn't even show up on the TV now- the HDMI port that I had used would display 'fire stick' and display the HDMI port #, now nothing shows up and then the screen times out quickly as if nothing is plugged in. When I first plugged in the firestick to my windows 10 laptop, I checked the drives and it didn't show up although I could hear a USB connection chime as if something just was connected and if I disconnected it, it had a disconnect chime as well. I did see in device manager before unplugging it that it had shown up as 'unknown device' towards the bottom land labeled as AFTM. Can anyone tell me what they think may have gone wrong and why it no longer shows up on the TV or why it's now not starting up for that matter? Any help would be appreciated.
tjmethod said:
I tried to transfer a ustv4.0 APK zip file to the firestick via USB after some extensive instructions on YouTube video but found that using Google Drive with ES File Explorer would be the quick and easy method. I also got lost in the instructions after downloading ADB and fire starter. When plugging the firestick back into the TV to go the ES file route, the firestick doesn't even show up on the TV now- the HDMI port that I had used would display 'fire stick' and display the HDMI port #, now nothing shows up and then the screen times out quickly as if nothing is plugged in. When I first plugged in the firestick to my windows 10 laptop, I checked the drives and it didn't show up although I could hear a USB connection chime as if something just was connected and if I disconnected it, it had a disconnect chime as well. I did see in device manager before unplugging it that it had shown up as 'unknown device' towards the bottom land labeled as AFTM. Can anyone tell me what they think may have gone wrong and why it no longer shows up on the TV or why it's now not starting up for that matter? Any help would be appreciated.
Click to expand...
Click to collapse
Hi did you find a solution. I have the same problem.
Thx
so i have my kindle fire gen 1 with cyanogen mod and twrp installed i tried to do a factory reset with twrp and i think ive removed the os im trying to get the device to recognise via pc but it connects the disconnects within a second of conecting it wont turn on wont boot nothing ive tried a fast boot cable nothing with that either any ideas please people
I dumped amazon for forcing updates on my firestick. See if you can get back to stock using Fire-Iso 1?
Fire-Iso 2 requires you update way too much for the layman like me .
Also, lots of tools for that device on rootjunky.com 'scuse the external links admin, I see this as justified here