Related
1) Yes I checked search results.
2) Yes I've googled.
3) Yes I've tried the Kindle Fire Utility, the http://forum.xda-developers.com/showthread.php?t=1356257... links options.
With that being said, here's my issue;
Got a KF a couple days ago...
Yesterday, followed some online instructions to put GO Launcher EX on there to replace the carousel deal.
Followed instructions to the T.
Restarted. Got to "Choose your OS" screen (or whatever it precisely says...)
Picked GO... then it froze.
Now, when it restarts (yes, its the 30 second hard restart), it gets stuck on the Kindle Fire splash screen.
I have tried the above utilities.
I have hard restarted.
I have fully charged and ran the battery dry and tried again.
When I use the utilities, the problem is, my PC will not recognize the Kindle (it see's it as a removable storage device, but it doesn't click over to 'Kindle', and thus the utilities can't interact with the device itself, I suppose).
I've tried different USB ports and connecters (I have 2 regular kindles in the house, too). But I know all the peripherals work through cross-testing.
Essentially, what else can I do? (I got it from WalMart, and they're currently out of stock, so I can't return it till next week, but I'd like it fixed before then if possible)
I've tried several different methods from these forums too, but I *always* hit the same snag... whenever any utility is 'waiting for device', it simply will not find it, because the PC doesn't see it properly. It sees *something* (removable storage) but not as a kindle, and thus won't allow the utilities to interface with it.
Are there any physical things I can do to hard reset it without destroying any warrantys?
Any help appreciated!
there is no need to return it
from what you say i think you have a bad launcher on it and the kf tries to start it but can't
first i need to know if you have fff (custom bootloader - yellow triangle) on it ?
then do you have a recovery (twrp) on it ?
what os/bit of computer ?
In kindle utility go to bootmodes and enter normal (4000). Just had that problem last night.
awidawad - I've tried that. It stays on 'waiting for device' forever. Please explain step by step what you did? At which point did you power on the KF, when did you run KFU, etc, etc.
b63 - I hope your right!
no - I do not have the yellow triangle.
no - I do not have TWRP on it, i have tried, but cannot get anything onto the kindle.
my PC is window7, 64bit
Euryon said:
awidawad - I've tried that. It stays on 'waiting for device' forever. Please explain step by step what you did? At which point did you power on the KF, when did you run KFU, etc, etc.
Click to expand...
Click to collapse
Do you have all the kf drivers installed on your computer? I know that when I unbricked mine I had all the drivers installed but I had to reinstall them for some reason. If you do not have them I can post them later on tonight when I'm at home. However, I have TWRP installed on mine, and Cyanogenmod 7.2, so hopefully yours is able to connect to your computer.
---------- Post added at 12:56 PM ---------- Previous post was at 12:50 PM ----------
b63 said:
there is no need to return it
from what you say i think you have a bad launcher on it and the kf tries to start it but can't
Click to expand...
Click to collapse
In order to remove the bad launcher, you need to have your device connected to your computer to remove it using adb.
ok so b63 helped me out big time here....
about 2 hours ago we got on a teamviewer session (download this if you want these guys to help you with serious issues!)
took me a minute to figure out how to allow him/her proper access to my screen
anyway
i don't understand the technical stuff
but
what i had done wrong is that i didnt root the KF before trying to install the GO... software (i think)
b63 had a heck of a time trying to discern the problem with me being about as useful as a dead fish, but get there he/she did
after much fanangaling, b63 managed to install the TWRP and ADP on my KF, allowing it to fastboot, and basically allowing it to be read by my PC, and so fixed.
im sure it would have taken b63 all of 5 minutes in real time, but using the quirky teamview and my slow net speed didn't help
still, thanks VERY MUCH to b63 for fixing the **** out of my KF, and being very helpful and patient all along!
thanks
Just wanted to drop b63 a note here that I "thanks"ed their post above - not necessarily for the post but for going above and beyond. The people on these forums are (for the most part) really great. (Too bad there have to be a few who are demanding of the developers to get this feature or that fix done faster without taking into account that the devs do this all in their free time.)
YES, search finally led me here!
Euryon, I have the exact same thing happening with my KF right now.
Do you remember any specifics of how b63 carried out the steps you listed?
b63, any chance you could help me with mine? My issue is identical with Euryon's down to the letter.
Same Problem
Could someone please help me i have the same problem
same problem here! please can someone give a step by step? My fire is unrooted and I did nothing to it except try to install the go launcher and after I selected it as the default launcher it got stuck at the kindke fire logo.
I tried the Kindle unbricking utility but it cannot find the device even after I installed the adb composite interface
also, my fire is not showing up as a kindle - it is showing up as an android device.
rollno88 said:
also, my fire is not showing up as a kindle - it is showing up as an android device.
Click to expand...
Click to collapse
Have you added the fires usb ID to your system?
Sent from my Amazon Kindle Fire using Tapatalk 2
thanks for replying, and I have no clue how to do that. I'll search and get back .
---------- Post added at 10:12 AM ---------- Previous post was at 09:57 AM ----------
okay, I already did that by editing the android sdk(as a prerequisite to rooting, which I planned to do eventually) - so when I connect my fire it first shows up as a kindle, and after updating the software through windows and installing drivers through KFU, it comes up as an android device and the interface is adb composite. Now if I try to install TWRP through KFU it keeps switching between adb composite interface and plain adb. And both KFU and KUFU keep waiting but are unable to find my device.
also, my fire alternately shows up as a usb composite device and an android device. PLEASE help
okay I solved it with KFU (finally!) although I have no clue how I did it as I didn'tdo anything I hadn't tried earlier so, managed to install TWRP and then wiped everything and finally my fire could be read - then I deleted go launcher and now my fire is back from the grave
A big thank you to all the helpful posts at this forum - u guys are the best
Same issue
Tried rooting my KF, but couldn't change permissions and thus could not install android market. Superuser didn't do anything other than show me a log folder that had no logs. Tried to change permissions on /system and /apps with one of the file management apps on amazon and it said the device *wasn't* rooted, despite GO launcher and android interface.
Did a factory wipe to try to reroot or fully(?) root the KF, and that's when it all went wrong. Got stuck on boot loop, but KFU helped me break out of that. Now it's stuck on the Kindle Fire splash screen with no animation. I read somewhere that this was the fastboot getting "stuck."
At any rate, i have TWRP 2.0 installed and can mount and unmount the device in its interface, but it is only recognized as ADB android device, or when mounted via TWRP, USB composite device. As such, ADB commands only work occasionally - all other times it simply says <waiting for device>.
I am running Windows 7 64 bit, and 6.3 on the KF. All restarts on the KF are hard restarts, except occasionally cmd lets me fastboot reboot.
I have spent the past 2 days trying everything I have found online (2 KF unbrick applets, 15+ tabbed browsers with different threads) to no avail. I am finally posting, pleading for assistance.
Thanks in advance for any (helpful) replies. Real thanks clicking afterwards.
edit: when rerunning KFU, i kept getting the message that many execs failed because "/system/bin/sh" directory does not exist.
I don't know if that helps narrow down what might be happening, but I saw that coming up a lot in the cmd prompt.
zeissbickham said:
Tried rooting my KF, but couldn't change permissions and thus could not install android market. Superuser didn't do anything other than show me a log folder that had no logs. Tried to change permissions on /system and /apps with one of the file management apps on amazon and it said the device *wasn't* rooted, despite GO launcher and android interface.
Did a factory wipe to try to reroot or fully(?) root the KF, and that's when it all went wrong. Got stuck on boot loop, but KFU helped me break out of that. Now it's stuck on the Kindle Fire splash screen with no animation. I read somewhere that this was the fastboot getting "stuck."
At any rate, i have TWRP 2.0 installed and can mount and unmount the device in its interface, but it is only recognized as ADB android device, or when mounted via TWRP, USB composite device. As such, ADB commands only work occasionally - all other times it simply says <waiting for device>.
I am running Windows 7 64 bit, and 6.3 on the KF. All restarts on the KF are hard restarts, except occasionally cmd lets me fastboot reboot.
I have spent the past 2 days trying everything I have found online (2 KF unbrick applets, 15+ tabbed browsers with different threads) to no avail. I am finally posting, pleading for assistance.
Thanks in advance for any (helpful) replies. Real thanks clicking afterwards.
Click to expand...
Click to collapse
Read this...
http://forum.xda-developers.com/showthread.php?t=1552547
with an emphasis on post #2. You need to know what mode your device is in by looking at the device manager and make sure your drivers are loading correctly for that mode. If you can get to TWRP, you can mount your USB mass storage device, copy a new zip file of either the stock software or a custom ROM and flash it.
Thank you. I will be trying this shortly.
fully bricked
I followed the guide and got to a point where the Kindle Fire animation was playing. It loaded up to the unlock screen and then automatically shut itself down - would not stay on when either connected or disconnected. Tried installing a ROM but still shut down. Started the recovery and hit factory reset, still auto shutdown. Tried clearing a partition as described in the tutorial and now it's fully bricked. Will not turn on when connected to computer, to outlet, to another cable.
Thanks for trying to help.
Ok, so here's what happened.
When I got my ouya, the first thing I did was root it and set up Wireless adb. I noticed that when I had adb running over wifi though, it would disable my micro usb port for some reason, and I couldnt copy anything to the device while I had debugging enabled.
Long story short, I disabled adb to copy some files, and I accidentally replaced the launcher while trying to get GAPPS working. Unfortunately whatever launcher overwrote the ouya one doesnt work, and just force closes on boot.
Does anyone know of a recovery mode for the ouya? Most phones require holding down the power button as well as one of the volume buttons, but the ouya doesnt have any volume buttons.
I opened the case, and didnt see any switches or jumpers either.
I even tried using a usb keyboard and holding down the volume buttons on it out of desperation haha.
Is it possible to get Clockwork Mod booting from USB or something?
with wireless adb, if you disconnect from it by closing the cmd window, you need to type adb usb to re-enable the usb mode
its okay if the launcher fails as long as it still boots and you get into android, you can turn on adb again and just re-install stock launcher. I'll attach it in an sec
Wanted to mention, you don't need to root (already rooted), I wouldn't suggest flashing any random recovery, it needs to get made for it first(eventually gonna happen soon).
I would suggest deleting/uninstalling whatever launcher you tried installing. Because the launcher they used is built with the framework so you need to do more work to get an third party launcher to work correctly.
First:
adb install Pathofapk\OUYALauncher.apk
Second:
adb shell
su
cd /data/app
ls (get the name of the launcher that's FC)
rm name.apk
Paulenski said:
Wanted to mention, you don't need to root (already rooted), I wouldn't suggest flashing any random recovery, it needs to get made for it first(eventually gonna happen soon).
I would suggest deleting/uninstalling whatever launcher you tried installing. Because the launcher they used is built with the framework so you need to do more work to get an third party launcher to work correctly.
First:
adb install Pathofapk\OUYALauncher.apk
Second:
adb shell
su
cd /data/app
ls (get the name of the launcher that's FC)
rm name.apk
Click to expand...
Click to collapse
Thanks for attaching the launcher. I hopefully will be able to use that soon. Unfortunately, I disabled USB debugging in the Developer options on the Ouya itself.
I tried running your command (adb usb) and it tells me that no devices were found. I tried doing 'adb connect x.x.x.x' as well, but since USB debugging is disabled, it won't connect that way either.
Thanks for the suggestion though. Do you have any other ideas?
I have this samba app installed, and I was hoping i could access root through that, but I can only figure out how to access the sd card.
I also have airdroid and es file manager installed if there are any exploits to get those running.
Thanks for any help offered
Check this command
adb devices
does it even show up on the list?
Paulenski said:
Check this command
adb devices
does it even show up on the list?
Click to expand...
Click to collapse
i tried it, but it doesn't show up. I also checked device manager to see if it came up it there but all I get is an mtp device. I also copied the hardware id from that device and added it to the adb driver and reinstalled it that way, but it still does not show up in adb devices.
just to clarify, the mtp has a different hardware id than the adb mode one. When I did adb TCP originally, it disabled my micro USB port from mtp access, so I could not transfer files. That's why I had to disable USB debugging on the ouya. I'm afraid adb is doomed to not work until we can figure out how to get a USB bootable recovery image.
thanks for the suggestions I really appreciate it
any other ideas? I have been toying around with samba a little. I noticed that there is a share named admin$ but it doesn't work with the password I set up for the other share. Does anyone know what the default root password is for samba? If this will let me access the system folder, I can dump the launcher back in through samba.... Probably a long shot though.
https://devs.ouya.tv/developers/docs/setup
Did you follow that? If you don't do the echo command, it won't work on usb adb.
If you have Skype or GTalk, let me know, we can talk on there to try and remedy your problem
Paulenski said:
https://devs.ouya.tv/developers/docs/setup
Did you follow that? If you don't do the echo command, it won't work on usb adb.
If you have Skype or GTalk, let me know, we can talk on there to try and remedy your problem
Click to expand...
Click to collapse
I have PM'd you.
I double checked, and made sure to do the echo command. Still no dice.
Just as an update, MBM on the ouya dev forums posted how to get into the recovery mode of the console if anyone is interested. I was able to get my ouya running again with his help.
This is the process:
HOW TO RECOVER:
This is a hack, an unintended sequence of events that results in recovery mode; what you need to do is crash the startup using sysrq.
For this you'll need a usb keyboard with the sysrq key, this is usually the printscreen button if your keyboard isn't labeled. As the OUYA starts to boot, hold down the alt-sysrq keys and press i, wait a few seconds and then repeat. This key combination is kill-all-tasks; thanks to whoever left this enabled in the kernel. Each time you kill the tasks the init process will restart them, after about 5 or 6 times init will print a warning on the console that one of the processes marked critical has been restarted too many times -- this then triggers an automatic reboot into recovery mode.
Unfortunately it's not always obvious when the ouya is in recovery mode. You might get screen with the ouya logo and a large red exclamation mark, or the screen might be entirely black; usually I got a black screen. Press the home button on the keyboard to bring up the recovery menu; it's actually a toggle so feel free to press the home button repeatedly until you see the menu since the timing isn't otherwise obvious.
Once you get to the recovery menu, the select the second option to update from adb. Download the OTA update from the link at the end of this post, and run the command "adb sideload RC-OUYA-1.0.193-r1_ota.zip" this will reformat the system partition and reinstall the ouya software. You might also want to do a factory reset before rebooting.
Links to download the OTA updates can be found on this xda thread: http://forum.xda-developers.com/showthread.php?t=2266629
Click to expand...
Click to collapse
check out the thread here: http://forums.ouya.tv/discussion/1380/recovery-mode
Thanks for all the help here guys! I am glad to be running again
darthcircuit said:
Just as an update, MBM on the ouya dev forums posted how to get into the recovery mode of the console if anyone is interested. I was able to get my ouya running again with his help.
Click to expand...
Click to collapse
Glad it helped.
- mbm
Hey Guys,
as the title says, I can't connect to my OUYA anymore.
What have I done?
Set up adb and sdk descripted here
https://devs.ouya.tv/developers/docs/setup
Set up wireless adb, busybox, superuser, and su binaries descripted here
http://forum.xda-developers.com/showthread.php?t=2272266
Everything worked fine so far.
Then I rebooted the OUYA. From now on the device manager didn't found the OUYA anymore. If I switch USB-debugging off, its found as 'portable device'. If I switch USB-debugging on, it disappears and there is no other new item.
OUYA factory reset
This didn't helped anything. But with this step I lost SU.
So, as i read, USB-ADB is shut down on OUYA as soon as you enable wireless-ADB. A terrible 'feature', whatever. Now I can't modify the build.prop to take out the "service.adb.tcp.port=5555" line.
I managed to get into the recovery mode (by connecting a keyboard and pressing alt+print+i multiple times, then home) , but that's pretty helpless if adb can't find the ouya.
Has anybody an idea how I can get adb working properly again? Any ways are good, flashing a new rom, getting su, factory reset, anything =D
JackBackstack said:
Hey Guys,
as the title says, I can't connect to my OUYA anymore.
What have I done?
Set up adb and sdk descripted here
https://devs.ouya.tv/developers/docs/setup
Set up wireless adb, busybox, superuser, and su binaries descripted here
http://forum.xda-developers.com/showthread.php?t=2272266
Everything worked fine so far.
Then I rebooted the OUYA. From now on the device manager didn't found the OUYA anymore. If I switch USB-debugging off, its found as 'portable device'. If I switch USB-debugging on, it disappears and there is no other new item.
OUYA factory reset
This didn't helped anything. But with this step I lost SU.
So, as i read, USB-ADB is shut down on OUYA as soon as you enable wireless-ADB. A terrible 'feature', whatever. Now I can't modify the build.prop to take out the "service.adb.tcp.port=5555" line.
I managed to get into the recovery mode (by connecting a keyboard and pressing alt+print+i multiple times, then home) , but that's pretty helpless if adb can't find the ouya.
Has anybody an idea how I can get adb working properly again? Any ways are good, flashing a new rom, getting su, factory reset, anything =D
Click to expand...
Click to collapse
If you can get into recovery, just copy over the latest OTA file onto a usb stick, wipe Data/cache then flash the OTA.
Also for windows, not doing " echo 0x2836 >> "%USERPROFILE%\.android\adb_usb.ini" " can sometimes make it not be found on its own, was originally required to do it for ADB
In recovery mode, the only way is to flash the OTA via ADB. There is no option like from usb-stick or internal/external sd-card.
and my adb_usb.ini seems to be correct.
But thanks for your suggestions (=
I had the same issues. I'm waiting on a replacement. http://forums.ouya.tv/discussion/comment/13562
JackBackstack said:
Hey Guys,
as the title says, I can't connect to my OUYA anymore.
What have I done?
Set up adb and sdk descripted here
https://devs.ouya.tv/developers/docs/setup
Set up wireless adb, busybox, superuser, and su binaries descripted here
http://forum.xda-developers.com/showthread.php?t=2272266
Everything worked fine so far.
Then I rebooted the OUYA. From now on the device manager didn't found the OUYA anymore. If I switch USB-debugging off, its found as 'portable device'. If I switch USB-debugging on, it disappears and there is no other new item.
OUYA factory reset
This didn't helped anything. But with this step I lost SU.
So, as i read, USB-ADB is shut down on OUYA as soon as you enable wireless-ADB. A terrible 'feature', whatever. Now I can't modify the build.prop to take out the "service.adb.tcp.port=5555" line.
I managed to get into the recovery mode (by connecting a keyboard and pressing alt+print+i multiple times, then home) , but that's pretty helpless if adb can't find the ouya.
Has anybody an idea how I can get adb working properly again? Any ways are good, flashing a new rom, getting su, factory reset, anything =D
Click to expand...
Click to collapse
I haven't messed with root/cwm, since there really isn't much brick protection... you might try 'adb reboot recovery' during bootup... if you can force it to fastboot, you can boot the recovery image, and it should have adb with su access, you should be able to repair you mistakes from there, or just do a data/cache reset to wipe the device.
EDIT: assuming you can get to fastboot somehow, you would just have to 'fastboot boot recovery.img' where recovery.img is the build of cwm.
EDIT 2: try booting with a usb keyboard, during boot, you might be able to spam the kernel with the key combination alt-SysRq-i. This may force it to boot into recovery... Then you should be able to either use regular ADB, maybe push a OTA.zip via ADB, and ultimately install a OTA... Hope some of this is helping, I have no real hands on practice with much of ADB on this specific device... But I'm a LONG time android tinkerer.
EDIT 3: If you're able to get it to crash and boot into recovery via Alt-SysRq-i . It's a recovery based on 4.x as it should be... and you should be able to 'adb sideload OTA.zip'... Sorry for all these edits, I just keep realizing I have more to say.
Here's the link for the apk(down page a bit) to enable disable wireless adb allowing USB adb:
http://forum.xda-developers.com/showthread.php?t=961466
Sent from my Galaxy Nexus using xda app-developers app
HaYNigloo said:
Here's the link for the apk(down page a bit) to enable disable wireless adb allowing USB adb:
http://forum.xda-developers.com/showthread.php?t=961466
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Will that require root?
Yes, since it's right inline with installing su, busybox, and supersuer using ADB. With the option to go ADB wireless, this is a necessity if you'll be installing CWM.
HaYNigloo said:
Yes, since it's right inline with installing su, busybox, and supersuer using ADB. With the option to go ADB wireless, this is a necessity if you'll be installing CWM.
Click to expand...
Click to collapse
Yeah that's what sucks. I followed a post on here and thought I had the unit rooted but either I messed it up or the OTA updates wiped it out. Since I no longer have adb access I cannot get root to enable wireless adb access. Snake eating its own tale
Oh! I believe there are wireless adb apps that don't require root. Try looking into the play store to find out which ones.
Edit 1: The Play Store has a wireless ADB app by Sherdle [ADB Wireless (no-root)]which doesn't require root!
Sent from my Galaxy Nexus using xda app-developers app
Hi everyone,
Actually I'm stuck the exact same way and I'm wondering if beowolfschaefer and JackBackstack have found a solution to get ADB work over TCPIP.
Thanks guys.
KrelianGS said:
Hi everyone,
Actually I'm stuck the exact same way and I'm wondering if beowolfschaefer and JackBackstack have found a solution to get ADB work over TCPIP.
Thanks guys.
Click to expand...
Click to collapse
I'm missing something. I have read this a couple times but cant figure out what is happening.
Is your Ouya not booting up at all?
If it boots can you do an
adb connect xxx.xxx.xxx.xxx and then adb shell to get a shell?
HT123 said:
I'm missing something. I have read this a couple times but cant figure out what is happening.
Is your Ouya not booting up at all?
If it boots can you do an
adb connect xxx.xxx.xxx.xxx and then adb shell to get a shell?
Click to expand...
Click to collapse
The Ouya is booting perfectly and wifi-ADB is enable. Problem is I can't connect to it anymore.
I already tried adb connect 192.168.xxx.xxx but i get a "device not found" error. It's the good IP (check on the Ouya and on my router with the MAC Adress)
It might be a port probleme. I tried both 5037(default) and 5555.
By the way, in the settings, should I switch USB-Debugging on or off ? Or it doesn't matter ?
KrelianGS said:
The Ouya is booting perfectly and wifi-ADB is enable. Problem is I can't connect to it anymore.
I already tried adb connect 192.168.xxx.xxx but i get a "device not found" error. It's the good IP (check on the Ouya and on my router with the MAC Adress)
It might be a port probleme. I tried both 5037(default) and 5555.
By the way, in the settings, should I switch USB-Debugging on or off ? Or it doesn't matter ?
Click to expand...
Click to collapse
I am pretty sure USB debugging needs to be on for ADB to accept connections. make sure it is on
hi I am using the safe root method of root and trying to flash the FFF and TWRP , in this stib I am stuck in the fastboot mode I unplugged it and reconnect it help plz
Windows version?
How is it listed in Device Manager?
Error message?
I'm having the same problem and had posted a separate thread in the general forum, but coming here I see that I'm not the only one. I was following a guide here on how to saferoot, install FFF and TWRP on a 1st gen Kindle fire and after setting it for fastboot the first time my laptop could no longer see the device and it was stuck sitting at the non-animated "kindle fire" screen. I reset the device, uninstalled drivers and re-installed, rebooted my laptop, all to no avail, so I left it and went to bed. Little did I know that the device wasn't charging while at this screen and just left it plugged to my laptop and went to bed.
Now it seems the device is completely dead, or too dead to boot. The kindle fire screen will display for a couple seconds then the screen goes black, over and over. I used a high power charger(5v 2.2A) instead of the laptop USB port for over 12 hours and it's still just looping. Is there anything that can recover this thing?
Windows 7
Shows in Device MGR as Android ADB (before it went dead)
Before it went dead it just sat at the non-animated Kindle Fire screen, now it boot loops to the non-animated kindle fire screen
In linux, watching /var/log/messages, I see the Amazon Kindle and serial # pop up the first time I plug it in and then it says the device was disconnected as it reboots.
Thanks
g17jimmy said:
I
Windows 7
Shows in Device MGR as Android ADB (before it went dead)
Click to expand...
Click to collapse
That is what you wanted.
Before it went dead it just sat at the non-animated Kindle Fire screen, now it boot loops to the non-animated kindle fire screen
In linux, watching /var/log/messages, I see the Amazon Kindle and serial # pop up the first time I plug it in and then it says the device was disconnected as it reboots.
Thanks
Click to expand...
Click to collapse
you tried powering off Kindle? Hold power for 15 secs
then reconnect to wall charger
sd_shadow said:
That is what you wanted.
you tried powering off Kindle? Hold power for 15 secs
then reconnect to wall charger
Click to expand...
Click to collapse
Previously ,if I disconnected from any power source it just powered off and the power button didn't seem to stop the loop. As soon as I plugged it in it would start the loop again. *BUT* - I just reconnected after having had it disconnected for a few hours and was able to power it off by holding the power button ~15sec. It seems like I was able to leave it plugged in but not have it in a loop. Maybe it will charge now.
g17jimmy said:
Previously ,if I disconnected from any power source it just powered off and the power button didn't seem to stop the loop. As soon as I plugged it in it would start the loop again. *BUT* - I just reconnected after having had it disconnected for a few hours and was able to power it off by holding the power button ~15sec. It seems like I was able to leave it plugged in but not have it in a loop. Maybe it will charge now.
Click to expand...
Click to collapse
It will not charge in Fastboot mode, best to flash the twrp and FFF, if it is a stable connection
---------- Post added at 03:41 PM ---------- Previous post was at 03:40 PM ----------
Edit: It will not charge in Fastboot mode
It has charged now that it stopped the boot loop, but still just sitting at the fastboot non-animated 'kindle fire' screen. Soupkit on my linux laptop doesn't see it, still:
{see attachment, I couldn't link to the image host site since I'm a new member}
My system sees the kindle:
{see attachment, I couldn't link to the image host site since I'm a new member}
I'll check from my windows system in a sec.
g17jimmy said:
It has charged now that it stopped the boot loop, but still just sitting at the fastboot non-animated 'kindle fire' screen. Soupkit on my linux laptop doesn't see it, still:
{see attachment, I couldn't link to the image host site since I'm a new member}
My system sees the kindle:
{see attachment, I couldn't link to the image host site since I'm a new member}
I'll check from my windows system in a sec.
Click to expand...
Click to collapse
not sure, but soupkit may only work on 32bit systems
sd_shadow said:
not sure, but soupkit may only work on 32bit systems
Click to expand...
Click to collapse
It did not want to work due to missing 32bit libraries at first, but you can install the 32bit libraries along side the 64 bit libraries, don't know if that makes soupkit happy though. It stopped complaining. I have a 32bit live-cd I can run just to test-
but.... here's where things are on the windows side:
Device manager sees "android ADB interface", neither ADB nor fastboot can see the device. Kindle just sits there as shown in the phone pic. At least now the thing isn't acting completely weird, I'll do some more searching on the forum, but if you have any suggestions I'm all ears. FWIW this is the post I was following - http://forum.xda-developers.com/showpost.php?p=54124313&postcount=3 - I am stuck after completing step 5.
Thanks!
g17jimmy said:
It did not want to work due to missing 32bit libraries at first, but you can install the 32bit libraries along side the 64 bit libraries, don't know if that makes soupkit happy though. It stopped complaining. I have a 32bit live-cd I can run just to test-
but.... here's where things are on the windows side:
Device manager sees "android ADB interface", neither ADB nor fastboot can see the device. Kindle just sits there as shown in the phone pic. At least now the thing isn't acting completely weird, I'll do some more searching on the forum, but if you have any suggestions I'm all ears. FWIW this is the post I was following - http://forum.xda-developers.com/showpost.php?p=54124313&postcount=3 - I am stuck after completing step 5.
Thanks!
Click to expand...
Click to collapse
tried different usb ports? usb 2.0?
sd_shadow said:
tried different usb ports? usb 2.0?
Click to expand...
Click to collapse
If I leave it hung on the kindle fire screen and plug it in to a different port Windows gives an error (screenshot attached.) If I turn it off (power button 15sec) and then plug it in it comes on and windows sees it properly as an android adb interface, but adb and fastboot still cannot see it.
I haven't looked into messing with it on my mac, I'll check that out, too.
The only live cd I had handy was an old version of Backtrack (BT5r3,) but it's 32bit and still adb and fb cannot see the device, even though the system sees it being plugged in and disconnected.
BTW- on the 64bit Centos 7 side of this system, I installed these packages to make Soupkit at least seem to work:
yum install gtk2.x86_64 gtk2.i686 libXtsc.x86_64 libXtsc.i686 ncurses-libs.i686
Something about the way the new CentOS works won't allow you to install the i686 libraries without including the x86_64 install at the same time.
Ok, disregard my issues. I can write to the device even though ADB and fastboot couldn't see it. I'm past step 5 now.
g17jimmy said:
Ok, disregard my issues. I can write to the device even though ADB and fastboot couldn't see it. I'm past step 5 now.
Click to expand...
Click to collapse
good.
Not sure what is causing the no reply to fastboot devices
I may need to change my directions.
Did you ever try?
Code:
fastboot reboot
android tools
I like to have two terminals open. One with root permissions for fastboot commands and a normal terminal for adb. Some distros have a root terminal program, but if you don't, just sudo <gnome-terminal>,<xterm>, or whatever your favorite is.
Thanks to SD_Shadow for all his work. I don't know how he can keep track of all the possible screw ups one can perform rooting and flashing, and get to the bottom of things.
sd_shadow said:
good.
Not sure what is causing the no reply to fastboot devices
I may need to change my directions.
Did you ever try?
Code:
fastboot reboot
Click to expand...
Click to collapse
I'm not sure why it didn't show in the fastboot devices list either. It shows now if I put it in fastboot. I have twrp 2.8.3.0 loaded and I'm trying to install a ROM but it doesn't work. I used adb to copy the file to the kindle but it's not installing. If I try to mount the device in windows or linux I get a message that the disk isn't formatted. Is this normal? I don't see any steps that indicate I should format a disk.
g17jimmy said:
I'm not sure why it didn't show in the fastboot devices list either. It shows now if I put it in fastboot. I have twrp 2.8.3.0 loaded and I'm trying to install a ROM but it doesn't work. I used adb to copy the file to the kindle but it's not installing. If I try to mount the device in windows or linux I get a message that the disk isn't formatted. Is this normal? I don't see any steps that indicate I should format a disk.
Click to expand...
Click to collapse
another pic
g17jimmy said:
another pic
Click to expand...
Click to collapse
Uncheck all in Mount options
, then try mounting storage
---------- Post added at 01:36 PM ---------- Previous post was at 01:34 PM ----------
Also I don't recommend 2.8.x.x, suggest downgrading to 2.7.x.x
---------- Post added at 01:37 PM ---------- Previous post was at 01:36 PM ----------
Kindle Fire Flashable Recoveries TWRP/COTR/CWM[2014]
OK. I'll go back to 2.7.x and try again.
I tried to downgrade to 2.7.x, but it said "image too large for partition", but while trying to clear that up I seem to have accidentally fixed the sdcard mount. I wiped everything and rebuilt sdcard and now it allowed me to run the install of cm11. What causes the "image too large for partition error"?
Thanks.
Merry Christmas
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