Related
So, I've been up all night after buying this Fire trying to fix it, and I've decided to go along with my original decision to just return it. I'll rewind a bit to give you guys a play by play to show how I got to what I've determined is a FUBAR situation, and hopefully you guys can help me at least remove TWRP so I can return it without much issue.
If it's tl;dr, I bolded the main errors I got from the console and TWRP
1. I purchased my Kindle Fire from Best Buy with a 1 Year Protection plan, so in all reality, I could just break it in half and get a replacement, but I don't necessarily want a replacement.
2. I initially purchased it for my mom, but when I found out that the stock Fire OS didn't have Korean input or the option to have a Korean interface, I did a bit of research and started reading up on how to root, how to install the market, things like that. My mom's not a native English speaker, so this was an important thing for her, etc etc.
3. I read multiple guides on this forum and others, and rooted using the guide found here , since a few of the threads I was reading through seemed to point in that direction, and I had a bad experience with SOCR on my Droid X.
4. The root was successful, so I moved on and used KFU .3 to do the rest of the important bits; android market, etc etc.
5. Everything was working fine, but, after looking through it, I realized that it wouldn't work for what I needed it to, and I would have to return it, so, I attempted to unroot the tablet using TWRP's interface.
6. I cleared the cache, the devlak cache, and system wiped, then restored using the system restore point in the TWRP folder, figuring after that, the Kindle would boot up with stock OS and then I would just system restore the default way. This method got me stuck in a recovery-loop, and no matter what I did, the Fire always booted to recovery mode.
7. I figured I had bricked it, so I followed the steps in this guide, but always seemed to have problems at the step where I have to chmod 755 of the zergRush. I get "Not a directory" error, which after doing some research, I believe is on account of me no longer having rw privilege?
8. I looked around some more, ignoring that guide, and found a method to force-push the amazon update, but TWRP would no longer run the update, saying it could not Mount the SD Card due to an Invalid Argument, and I have yet to determine what that means.
9. After manually changing it to fastboot in an attempt to at least get it out of recovery mode, I have the Fire recognizable as a device in my ADB, but it is now stuck in a fastboot loop, and when I attempt to re-root it in order to give myself rw privileges again, it stalls on "waiting for device" and never gets past that point.
Update
I tried to reroot while the Fire was stuck in the Kindle Fire splash screen using the KFU tool, and used zergRush, but the error message I got was - exec '/system/bin/sh' failed: No such file or directory (2) - 4 times over.
What I think the problem is, is that when I wiped the cache/devlak cache/ and system reformatted, it wiped my SU privileges, and as a result, no longer allowed me to write the backup to the Fire, therefore leaving me in a perpetual state of limbo?
What I'm asking for from you is;
What can I do to fix this?
Is there any more information you need/want from me?
And finally,
Is there an easy way for me to remove TWRP from the system?
Thank you.
Hi!
There are a lot of great tips regarding TWRP and fastboot over at RootzWiki.
Some users are reporting the same fastboot loop that you currently experience. I suggest you read the thread and follow the suggestions. One suggestion which you may want to try first is the one in this post.
Thank you for the reply. I did as you suggested and followed the links and the post on the guide, and although that did change the nature of my fastboot loop, I'm still stuck in a fastboot loop.
I was initially stuck in a fastboot loop on the Kindle Fire logo, which I determined by running fastboot devices, while it was stuck on that logo, and it showed the device as being fastboot. After following that guide, and using the hard reset, then using the "How to Unbrick" in order to change back to a normal boot, I'm stuck in a fastboot loop on the TWRP splash screen of a triangle with a fire in it. I'll continue looking through the guides to see if I can solve the problem, but thank you once again, and sorry for not clarifying which type of fastboot loop I was in.
Sorry it didn't work out! However...
isjonamon said:
I'm stuck in a fastboot loop on the TWRP splash screen of a triangle with a fire in it.
Click to expand...
Click to collapse
I really though the solution posted over at RootzWizi would solve this problem. Getting stuck at the yellow triangle is 'common'. I really though adding
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0100
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0100&MI_01
Click to expand...
Click to collapse
to android_winusb.inf would solve it. But if you are able to recognize your Fire in fastboot mode via your PC, I guess that's not where your problem is.
Is this tip to any help?
And lastly... the great Kindle Fire Utility thread is worth checking out, in case you haven't already
I hope you'll find a solution to this problem!
I've tried the tip you linked me to, and sadly it didn't do anything for me.
Moving on, though, I'm reading through the KFU thread again to see if there was anything I missed, and decided I might as well try re-flashing to CM7 to see if I can at least get it working up to a rooted/rom standpoint. I figure from there, I can at least have a working platform to factory reset from. If I can't do that... well...
Does anyone know a way to just return everything to factory settings? To just wipe everything and make it so it turns on like it's out of the box? Either through adb commands, or TWRP or anything?
Sorry for the double post, but I managed to get CM7 back up on my Fire, and managed to regain SU access. Can anyone point me to a guide to restoring it back to its former "glory" so I can return it?
Fixed it!!
For anyone interested, this is what worked for me;
From where I ended up with the problem, I followed hachiueno's advice and read through the KFU's thread as well as the TWRP thread on Rootzwiki, that led me to adding those lines to the device firmware, which I think was the first step in the solution, so...
Step 1. Add
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0100
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0100&MI_01
to android_winusb.inf , then restart your computer with your Fire unplugged.
After that, I was inspired, through reading the KFU thread, to attempt to manually install CM7 since I wasn't having much luck zergRushing on my own, so, I went to the CM7 thread and pushed the Update.zip there, and used my TWRP to install that, effectively rebuilding my filestructure, since it seems the Kindle Fire doesn't have so much as a SH folder in it.
Step 2. MANUALLY (maybe) install CM7 if you can.
Once I got CM7 up and working, using the USB mounting option, I replaced the update.zip in the sdcard folder with the Amazon 6.2 firmware downloaded from their website, renamed to update.zip, and then unmounted my fire from my laptop.
Step 3. Download the Amazon 6.2 Firmware from amazon's website (I can't post...), rename it to update.zip, and replace the CM7 mod update.zip in your /sdcard directory with it.
Then, I figured if I ran TWRP like it was supposed to run, and just ran the update.zip like any other ROM, it should fill in the blanks in the filesstructure, bypassing Amazon's own lack of certain folders, and various other things, filling in the gaps as they were. The next step might be entirely redundant, since I'm a bit clueless, and it might have been entirely luck on my part, but I initially forgot to wipe my cache, devlak cache, and system restore, so I did all that and did it again, and my wishful thinking leads me to believe that doing that saved my ass from having a crapton of errors....
Step 4. Using the install function on TWRP, install the renamed Amazon update.zip, reboot, clear your cache, devlak cache, system reformat, then reinstall the update.zip. Reboot one more time, and you should come up to the Kindle Fire splash screen. Leave it for a few minutes, and it'll be like it just came out of the box.
Thanks for all your help. I love you. Seriously. No homo. Maybe a little. I love you.
Good to hear that you managed to boot it again!
isjonamon said:
Sorry for the double post, but I managed to get CM7 back up on my Fire, and managed to regain SU access. Can anyone point me to a guide to restoring it back to its former "glory" so I can return it?
Click to expand...
Click to collapse
This guide seems to be an easy solution to this. However, no one has replied any success or failure, so not sure if it's 100% bulletproof for everyone... if I were you, I would follow JackpotClavin's guide here. He's a known developer here and knows what he's doing, and many successful replies from users having used this method... so yeah, just to be 'sure' (can you ever be...?) that you won't experience any further problems, I recommend the last one.
I actually used the first guide in order to get the Amazon update, but couldn't post a reply since I'm still a noob. I had to do a few things differently, and ultimately got a few different results, but posted up my own version of the steps.
Once again, thanks for all your help!
It seems to me that the majority of problems people are having are driver related. When I was using KFU to install TWRP it stalled half way through and just said waiting for device. Just had to install drivers again and it happily completed the install.
Sent from my Kindle Fire using xda premium
all u needed do initially was change bootmode it seemed. thrn u went and did all kinds of stuff that wasnt necessary.
sent from my kindle fire
smirkis said:
all u needed do initially was change bootmode it seemed. thrn u went and did all kinds of stuff that wasnt necessary.
sent from my kindle fire
Click to expand...
Click to collapse
I actually changed bootmodes quite frequently, following multiple threads and guides, changing from recovery, to normal, to fastboot, and back and forth when called for. Changing to fastboot stuck me in an eternal fastboot loop, changing to normal reverted me to a recovery loop, and recovery was the only bootmode I could access adb from.
Sheolrock said:
It seems to me that the majority of problems people are having are driver related. When I was using KFU to install TWRP it stalled half way through and just said waiting for device. Just had to install drivers again and it happily completed the install.
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
Driver issues seemed to be part of the problem for me, but just updating the drivers didn't fix the issue entirely. I'm jealous that you got it to work with just a driver update...
Hey i believe im in the same problem but i keep reading the posts and im still stuck and i have no idea what to do im worried that i cant fix it.... Some please help me ASAP
Thanks in advance
wrong boot mode ?
with adb:
adb shell su -c "idme bootmode 4000"
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot reboot
bad drivers ?
http://forum.xda-developers.com/showpost.php?p=20855280&postcount=54
I have had the looping problem and none of these would fix it. I got it to work by adding those lines to android_winusb and running the run.bat, trying to make it switch to normal mode as the kindle was turning on. Somewhere along the yellow triangle when it was loading it accepted the command from KFU. Hope this helps, only thing that worked for me.
the drivers i included contain all the necessary entries in adb_usb.ini and android_winusb.inf
Please can someone help me!?
I did idme bootmode 4002 and now my fire won't boot up or show up in android adb. Any solution?
awidawad said:
I did idme bootmode 4002 and now my fire won't boot up or show up in android adb. Any solution?
Click to expand...
Click to collapse
you switched it to fastboot (4002) - adb commands are not working in fastboot mode !
little guide:
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
here all the possible commands to change bootmode:
with adb (secure kernel):
adb shell su -c "idme bootmode 4000"
adb reboot
or (twrp or unsecure kernel):
adb shell idme bootmode 4000
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or:
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or:
fastboot oem idme bootmode 4000
fastboot reboot
the number is the bootmode you want to switch to:
normal boot -> 4000
fastboot -> 4002
boot to recovery -> 5001
and if you know:
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO
then you only have to count 1 and 1 together and can master nearly each hanging situation !
Click to expand...
Click to collapse
Not sure if this is totally helpful to anyone but originally I thought the thread was started with a posting of being stuck bootlooping into twrp in recovery mode with a complete loss of file structure. I had this same issue my Kindle would not start in anything but straight to twrp and if I tried to flash my CM9 ICS rom it was not there and only the twrp folder empty was. So I went to mount and mounted usb storage and moved the stock update zip file from amazon to the twrp folder and flashed that. Worked like a charm now I appear to be straight stock. I am no developer of this stuff I just am a bit of a tinkerer so don't understand all the code stuff but it starts like a normal kindle and appears totally stock. So hopefuly that helps you return your deice to stock for return or to continue wahtever modifications you intend.
2992
Hello all,
I've got a bricked droid, and haven't been able to find a fix that worked in other threads here.
I rooted my droid successfully, and installed GO Launcher EX, along with the android market, and a number of apps from there.
Among those, busybox, metamorph (which i then used to change the wallpaper), titanium backup, etc. I had successfully rebooted after all these installations and after changing the wallpaper.
I was getting on a plane the other day and turned off the KF, and havent been able to get it to boot since.
Originally it was in a boot loop, getting to the kindle fire icon and rebooting every 3 seconds.
I tried using the KFU, but it was unsuccessful at changing the boot mode (drivers were successfully installed).
Failing at that, i tried following the instructions in http://forum.xda-developers.com/showthread.php?t=1414832
After the reboot, it is now just stuck in the kindle fire screen, and i cant run any adb commands, device not found.
Am I straight up screwed now? or anything I might be able to do at this point.
Much appreciated, thanks for any advice.
Do you have fastboot access? Try running the following...
fastboot -i 0x1949 oem idme bootmode 4000
Try this: http://forum.xda-developers.com/showthread.php?t=1422832
Thanks guys, ill try those and post back w the results.
so i tried fastboot -i 0x1949 oem idme bootmode 4000
and it seems to have been successful, in that it is now back to its original boot loop state. however, it is still not booting fully.
it seems that adb commands are now working, i can do adb shell, and navigate root folders (system etc).
zombie, i havent had much luck with that route, i had tried that earlier.
I've seen people mentioning that the cause for their brick had something to do with permissions, so i did ls -l in the adb shell, here are the permissions for some of the relevant folders. if there are any others that might be helpful, let me know.
root -> drwx------
system -> drwxr-xr-x
sdcard -> lrwxrwxrwx
oh and framework-res.apk -> -rw-r--r-- (same as all other files in that directory)
i did modify the framework-res to change the background image. it successfully booted at least once after the modification - i used metamorph, i loaded the file, then rebooted for it to take effect. this was successful, but i believe it was the next reboot which did my kindle in, so possibly related.
i rambled a bit, but maybe if i replaced the current framework-res.apk with the stock framework-res.apk, that might be worth trying? are all stock framework-res.apk files the same at stock? because i don't have a copy of the original that came with my kindle.
i would go back into fastboot and then flash over TWRP... and then reinstall your os from scratch. it would probably be easier than trying to root around fixing it from the inside.
Thanks xrishox, I might do that. Is there a thread detailing how to do that?
When I tried doing fastboot I lost the ability to use adb commands so I'm not sure how to go about flashing twrp.
Download the fbmode binary and TWRP image. Then run the following.
Code:
adb push fbmode /data/local/temp
adb shell /data/local/tmp/fbmode
arbiter reboot
Your device should reboot and be stuck on the Kindle bootscreen. You are currently in fastboot mode. Now run the following...
Code:
fastboot -i 0x1949 poem idme bootmode 4000
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.image
Your device will reboot after that last command. It will boot into the TWRP installer. When it completes, tap "Reboot". Then boot into TWRP recovery and install the factory update, or a custom image that won't replace FireFireFire and TWRP.
jackofaiitrades said:
Hello all,
I've got a bricked droid, and haven't been able to find a fix that worked in other threads here.
I rooted my droid successfully, and installed GO Launcher EX, along with the android market, and a number of apps from there.
Among those, busybox, metamorph (which i then used to change the wallpaper), titanium backup, etc. I had successfully rebooted after all these installations and after changing the wallpaper.
I was getting on a plane the other day and turned off the KF, and havent been able to get it to boot since.
Originally it was in a boot loop, getting to the kindle fire icon and rebooting every 3 seconds.
I tried using the KFU, but it was unsuccessful at changing the boot mode (drivers were successfully installed).
Failing at that, i tried following the instructions in http://forum.xda-developers.com/showthread.php?t=1414832
After the reboot, it is now just stuck in the kindle fire screen, and i cant run any adb commands, device not found.
Am I straight up screwed now? or anything I might be able to do at this point.
Much appreciated, thanks for any advice.
Click to expand...
Click to collapse
Howdy!
I recently just dealt with this same issue. My KF was stuck in boot loop and wouldn't be recognized by my computer. I left it in bootloop until it ran out of battery. Once it was completely drained, I connected it to my computer and my computer recognized it, I then reinstalled the drivers. Right after that I used KFU to change bootmode to normal boot and let it fully charge! Good to go! Hope this helps someone.
from the op of kfu:
Known Tricks
•If you end up stuck at the yellow triangle, in KF Utility select Boot Normal, wait for it to say <waiting for device> and then press and hold the power button 20 seconds until the fire turns off, then when its off turn it back on. This sometimes happens, I have yet to find a clean solution
•If you end up stuck with a yellow triangle, do not EVER unplug it. Leave it plugged in. Check the windows drivers to make sure it isnt showing as "kindle" again. Fastboot is different and can cause this.
Click to expand...
Click to collapse
and here is a note from vashypooh - the op of kfu
http://forum.xda-developers.com/showpost.php?p=20945694&postcount=506
maybe it helps someone ...
Thanks guys, I won't be near a computer until tonight but will try these out as soon as I get back
lmntone said:
Download the fbmode binary and TWRP image. Then run the following.
Code:
adb push fbmode /data/local/temp
adb shell /data/local/tmp/fbmode
arbiter reboot
Your device should reboot and be stuck on the Kindle bootscreen. You are currently in fastboot mode. Now run the following...
Code:
fastboot -i 0x1949 poem idme bootmode 4000
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.image
Your device will reboot after that last command. It will boot into the TWRP installer. When it completes, tap "Reboot". Then boot into TWRP recovery and install the factory update, or a custom image that won't replace FireFireFire and TWRP.
Click to expand...
Click to collapse
Tone you're a life saver, thanks. I'm up and good to go.
good that it's working again !
have you seen this one in the dev section - could save a lot of handwork:
http://forum.xda-developers.com/showthread.php?t=1428428
Also, when I get back to my computer again, ill update my OP to include the solution so that others might benefit. its like a 20 minute fix but took me days to resolve it (largely due to lack of comp access but that's beside the point).
and that worked fine. I restored my backup and had the stock rom up and running fine. I then tried to install the android market but root explorer would not let me change the "mount as R/W" option. So under system settngs, device, I did a factory reset. Well after doing so I was met with TWRP, where I found out that my backup for the stock rom and CM7 was gone.
I tried re-installing CM7 via TWRP only to get met with it telling me:
E:Can't open/cache/recovery/log
E:Can't open/cache/recovery/last_log
E:Cannot load volume/misc!
So now I take it doing the factory reset wasn't the greatest idea. My question now is, how do I get my kindle running again? I would prefer to get back to the stock rom with access to the android market until a stable ICS rom is released, but have no problem going back to CM7 if necessary.
Any help would be greatly appreciated.
Thank You.
NastyNasdaq said:
and that worked fine. I restored my backup and had the stock rom up and running fine. I then tried to install the android market but root explorer would not let me change the "mount as R/W" option. So under system settngs, device, I did a factory reset. Well after doing so I was met with TWRP, where I found out that my backup for the stock rom and CM7 was gone.
I tried re-installing CM7 via TWRP only to get met with it telling me:
E:Can't open/cache/recovery/log
E:Can't open/cache/recovery/last_log
E:Cannot load volume/misc!
So now I take it doing the factory reset wasn't the greatest idea. My question now is, how do I get my kindle running again? I would prefer to get back to the stock rom with access to the android market until a stable ICS rom is released, but have no problem going back to CM7 if necessary.
Any help would be greatly appreciated.
Thank You.
Click to expand...
Click to collapse
Well that quick looks like I have done more damage.
I tried to run the unbrick kindle utility found in the developers forums. I ran that and selected option 5, it then asked me if I had the yellow triangle so I selected no. It then rebooted the kindle and I am now stuck with the yellow triangle.
Any help?
NastyNasdaq said:
Well that quick looks like I have done more damage.
I tried to run the unbrick kindle utility found in the developers forums. I ran that and selected option 5, it then asked me if I had the yellow triangle so I selected no. It then rebooted the kindle and I am now stuck with the yellow triangle.
Any help?
Click to expand...
Click to collapse
Uhhhhh select yes.....Now that you have the triangle
Tried that and it gave me an error. Forget what it said (turned pc off, going to sleep) and did nothing to the kindle. Pc recognizes it as android phone but not as a usb storage drive.
Any suggestions?
Have you tried to fastboot it via adb?
its in fastboot. reinstall twrp. this is why I ordered a fastboot cable.
how did u install twrp the first time? sounds like u have a drivers issue.
Sent from my HTC Glacier using xda premium
in case you have a driver issue you could follow this thread:
http://forum.xda-developers.com/showthread.php?t=1436147
then you can use kfu or unbrick utility to set bootmode to normal
if you like to do it manually here are all commands depending on rooting method and the bootstate (use only the fastboot commands in your case):
with adb:
adb shell su -c "idme bootmode 4000"
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or
fastboot oem idme bootmode 4000
fastboot reboot
UPDATE 3: I've got it back to as stock as I can get it. I think I'm going to just return it and get a new one. Thank you all for your help.
UPDATE 2: As of right now, I'd like to completely remove FFF from the device, but I can only use fastboot to do it. I have absolutely no adb access. Is there a way?
UPDATE: Here is a video showing what is happening to my KF: http://www.youtube.com/watch?v=MH6oUg1NmC0
I hate to start another thread about boot loops/bricking, but I'm not sure what's going on with my fire.
I had CM7 installed successfully since the day after Christmas. This morning I woke up and my Fire was being really sluggish, so I rebooted it (I did not select reboot into recovery).
After it powered on, I was stuck at the CM7 boot screen (with the skateboarding android). I let it sit, but no luck. I went into TWRP to try and restore the backup I made of the stock rom. It looked successful, but when I rebooted I was stuck at the Kindle Fire boot screen.
Next, I tried wiping the device and re-installing CM7, but I received an error (something along the lines of E:Error unable to find /tmp/sideload/blahblah).
So I again restored my backup of the stock rom. Now when I power on my Fire I see the yellow triangle, then the kindle fire logo, yellow triangle, kindle fire logo, and it just keeps repeating. The problem is I am unable to connect to adb because the PC only seems to recognize the adb device for a few seconds after the yellow triangle, which does not give me enough time to fix the problem.
Any ideas?
looks like you'r out of battery ! the kf is rebooting !
would take the wall charger and charge for an hour
it's not possible to charge with the computer - it lasts forever
then it should respond in a stable state
b63 said:
looks like you'r out of battery ! the kf is rebooting !
would take the wall charger and charge for an hour
it's not possible to charge with the computer - it lasts forever
then it should respond in a stable state
Click to expand...
Click to collapse
Recovery shows my battery level to be at 53%. I've got it on the charger now, but I have a feeling there is something else going on.
Also, I am unable to mount my Fire's SD to my computer in recovery. It looks like it is working, but my computer never acknowledges it.
maybe because your last installation failed
nevertheless i would try to charge and then go in twrp and retry the installation
if that's not sucessful i would try to switch the kf to fastboot and copy a new rom. stock or prerooted stock or cm7 - whatever you like
in twrp there is a point "mount" - sdcard - then you should get it from computer
b63 said:
maybe because your last installation failed
nevertheless i would try to charge and then go in twrp and retry the installation
if that's not sucessful i would try to switch the kf to fastboot and copy a new rom. stock or prerooted stock or cm7 - whatever you like
in twrp there is a point "mount" - sdcard - then you should get it from computer
Click to expand...
Click to collapse
Thanks for the reply. Is adb required to get into fastboot? The problem is that I am unable to get into adb because my computer only sees the Fire for about 1 second. When I go into device manager, I don't see it at all.
EDIT: Yeah, I see the mount in TWRP, but it does not do anything when I select it.
Hi Im a beginner but Id like to try to help :
In case you become desperate ignore twrp's battery display and try wall charger.
Anorher idea id have is to shut down throughr twrp and start up then instead of rebooting.
ADB is needed to get into fastboot, but it's quick. If you use KFU, you can probably hit the option during the couple seconds you have available. I would say your best bet, however, is booting into twrp, doing a full wipe of system, cache, davlik cache, and maybe data, and then trying the rom install again.
skourg3 said:
ADB is needed to get into fastboot, but it's quick. If you use KFU, you can probably hit the option during the couple seconds you have available. I would say your best bet, however, is booting into twrp, doing a full wipe of system, cache, davlik cache, and maybe data, and then trying the rom install again.
Click to expand...
Click to collapse
So this time it looks like the installation worked in TWRP, but after reboot now I'm stuck at the CM7 boot screen. This is at least some progress, so when I get home I'll see what I can do.
Sent via my internet connected mobile cellular telephone.
Well, the battery is definitely not the issue. I've been trying to get fastboot, but the problem is the fact that I can not get adb. Has anyone else had issues with getting adb? I've already tried to install the drivers, and that doesn't work.
EDIT: I've tried issuing "adb devices" from the command prompt repeatedly as soon as I hear the ding until it disconnects a second later, but still I have had no luck.
Also, I found this thread in which someone else appears to have had a similar issue to mine.
[Q] New kind of unfixable Super Brick?
at the moment adb is useless - you should try to get the device in fastboot mode - correctly recognised from your computer - then work with fastboot commands - if you don't get that then your next opinion is buying or making a factory cable - but we should try to avoid that ...
b63 said:
at the moment adb is useless - you should try to get the device in fastboot mode - correctly recognised from your computer - then work with fastboot commands - if you don't get that then your next opinion is buying or making a factory cable - but we should try to avoid that ...
Click to expand...
Click to collapse
I can not seem to get fastboot to work either. Does fastboot rely on adb? Or do you just run the .exe file? I tried to run it, and nothing happened.
fastboot has nothing to do with adb - calling just the exe does nothing -
you have to issue fastboot commands
ok have reread the whole thread and have some ideas:
your currently stuck at the cm7 boot screen ?
have you used the "stock rom version" to wipe data and cache partitions as described here ?
http://forum.xda-developers.com/showthread.php?t=1390773
perhaps it will help to wipe data/cache with twrp ...
b63 said:
fastboot has nothing to do with adb - calling just the exe does nothing -
you have to issue fastboot commands
ok have reread the whole thread and have some ideas:
your currently stuck at the cm7 boot screen ?
have you used the "stock rom version" to wipe data and cache partitions as described here ?
http://forum.xda-developers.com/showthread.php?t=1390773
perhaps it will help to wipe data/cache with twrp ...
Click to expand...
Click to collapse
Just wanted to let you know I updated the OP with a video showing what is happening to my KF.
Haven't tried that particular rom yet, but I have wiped data and cache and attempted to re-install CM7.
great idea with the video !!!
b63 said:
fastboot has nothing to do with adb - calling just the exe does nothing -
you have to issue fastboot commands
ok have reread the whole thread and have some ideas:
your currently stuck at the cm7 boot screen ?
have you used the "stock rom version" to wipe data and cache partitions as described here ?
http://forum.xda-developers.com/showthread.php?t=1390773
perhaps it will help to wipe data/cache with twrp ...
Click to expand...
Click to collapse
OK, so I restored my original rooted kindle rom, but I still can't get into fastboot because of the problem I showed in the video. It is doing exactly the same thing, just instead of the CM7 boot screen, it is the Kindle Fire boot screen.
Is is possible to get into fastboot without the computer? Can anyone think of a reason why I would not be able to mount my device in TWRP?
I just want to understand something about fastboot... can you upload and flash roms with it? Or can you only get TWRP / FFF with it? I ask because I already have them, and I still can't do anything (mount from inside TWRP doesn't work). Thanks!
Sent via my internet connected mobile cellular telephone.
with fastboot you can install the newest fff and if you need twrp
but with the newest fff you can issue ""fastboot oem format"
see here:
http://forum.xda-developers.com/showthread.php?t=1369405
that should solve every issue ...
b63 said:
with fastboot you can install the newest fff and if you need twrp
but with the newest fff you can issue ""fastboot oem format"
see here:
http://forum.xda-developers.com/showthread.php?t=1369405
that should solve every issue ...
Click to expand...
Click to collapse
Cool. I just ordered one of SkOrPn's cables, so once I get it I'll be sure to give an update. Thanks for all the help so far!
The cable isn't need when you have the FFF bootloader, in fact, when your computer does see the device for the short amount of time shown in the video, fastboot is active. It's a feature of FFF. Fastboot is a command line tool like adb but is used for different things. It comes in Android sdk which if you have that, you should update the tools packages in the Android manager and it will update adb and fastboot. It looks like something is not working correctly in twrp and the OS is failing to load. I'm not sure you need to oem format tho.....
At some point you had to have used fastboot to install twrp and/or FFF.... Unless you used adb dd? :what:
Anyway, I can help more but it's late where I am, need to sleep. Was going to write more but... Need sleep lol. I'll post some questions and check back tomorrow.
Have you used adb before? Do you know if platform-tools is in your environment variables PATH? In other words, can you open up cmd and type adb or do you need to "cd" to platform-tools then use adb? If you know where adb is located? If so, is a file called fastboot in there? (Maby called fastboot.exe)
foxdog66 said:
The cable isn't need when you have the FFF bootloader, in fact, when your computer does see the device for the short amount of time shown in the video, fastboot is active. It's a feature of FFF. Fastboot is a command line tool like adb but is used for different things. It comes in Android sdk which if you have that, you should update the tools packages in the Android manager and it will update adb and fastboot. It looks like something is not working correctly in twrp and the OS is failing to load. I'm not sure you need to oem format tho.....
At some point you had to have used fastboot to install twrp and/or FFF.... Unless you used adb dd? :what:
Anyway, I can help more but it's late where I am, need to sleep. Was going to write more but... Need sleep lol. I'll post some questions and check back tomorrow.
Have you used adb before? Do you know if platform-tools is in your environment variables PATH? In other words, can you open up cmd and type adb or do you need to "cd" to platform-tools then use adb? If you know where adb is located? If so, is a file called fastboot in there? (Maby called fastboot.exe)
Click to expand...
Click to collapse
Yep, I've used adb successfully, and it is set up as an environmental variable. I actually installed FFF and TWRP with the KFU. Problem is I think something else is botched; perhaps it is TWRP itself, since I am unable to mount from TWRP. I'll try again when I get home.
Sent via my internet connected mobile cellular telephone.
Solved
thanks to all for the great info
i have a fire that is stuck on the static kindle logo. was rooted and had fff and twrp. while messing with flashing different roms i used a custom rom that had several apks removed. after booting i still had fff and twrp but my wifi stopped working. i flash the 6.2.1 stock rom that removes fff and twrp, but did a stupid and wiped some stuff before i booted the stock rom. now im stuck with kfu showing online but under status says unknown. i can use adb to reboot but that seems all i can get it to do. im at work now and cannot quote the messages i get. something like /systme/whatever is not there. seems like i wiped the sd card and all. now with that information can i still use a factory cable to fix this? im working on one now to try and see. just wanted to hear from someone who has maybe done the same.
thank you very much for any info
I was in the same exact situation and with the factory cable i managed to fix my brick. Don't worry, your Fire is fine.
The same thing happened on mine 20 minutes ago. I worked it out with the method used in this thread.
lmntone said:
The same thing happened on mine 20 minutes ago. I worked it out with the method used in this thread.
Click to expand...
Click to collapse
That won't work without a working adb shell (http://forum.xda-developers.com/showthread.php?t=1418080), whik i think is the case.
man i hate being a noob fire owner i have my cable done 5v on 1 and 4 but not getting what i was looking for. kfu still shows
adb: online
adb rooted: no
boot status: unknown
im on windows 7 and can reboot the fire with cmd window adb reboot. but i have no idea where to go from here.
i thought the factory cable would put it in fastboot, but not sure how to check or what to do.
adb shell gets this:
-exec '/system/bin/sh' failed: no such file or directory (2) -
It won't show up in kfu, just select flash twrp anyway.
Sent from my myTouch_4G_Slide using XDA App
Use fastboot.exe located in the tools directory and run "fastboot.exe -i 0x1949 boot twrp-blaze-2.0.0RC0.image". But you have to download the TWRP image and place it in the same folder as fastboot.exe.
Iguanadon said:
man i hate being a noob fire owner i have my cable done 5v on 1 and 4 but not getting what i was looking for. kfu still shows
adb: online
adb rooted: no
boot status: unknown
im on windows 7 and can reboot the fire with cmd window adb reboot. but i have no idea where to go from here.
i thought the factory cable would put it in fastboot, but not sure how to check or what to do.
adb shell gets this:
-exec '/system/bin/sh' failed: no such file or directory (2) -
Click to expand...
Click to collapse
you know you're in fastboot mode when your kindle fire logo is static instead of glimmering
maybe you want to take a look here:
http://forum.xda-developers.com/showpost.php?p=21391952&postcount=38