Cant mount SD card on kindle fire. - Kindle Fire Q&A, Help & Troubleshooting

So I was messing with my kindle and it was trying to upgrade it to jelly bean and i guess i missed one of the steps and bricked it. I was going through the process of unbricking but when i was trying to do extract the update.zip folder it would not allow me to because it could not mount the SD card. All i need to figure out how to do is get the SD slot mounted. I am slowly picking up on command prompt and still trying to figure out adb shell but that is all i need help with.
I can unbrick it if someone knows how i can get my kindle to mount back to my computer!
Any advice or step by step for it would be very helpful, Thanks guys

Could you be more specific as to how your Kindle is "bricked"?

soupmagnet said:
Could you be more specific as to how your Kindle is "bricked"?
Click to expand...
Click to collapse
I can only get to CWM. It does nothing but boot loop and does not go any farther then that. I can plug it into the computer and get the drivers connected and KFU can recognize it. when i put it in cwm this is the first thing i see

Forgive my redundancy but please describe the "boot loop". Does it just sit at the Kindle Fire logo? Does the Kindle Fire logo flash, or change brightness? Does it make it to the boot animation? Black screen?

soupmagnet said:
Forgive my redundancy but please describe the "boot loop". Does it just sit at the Kindle Fire logo? Does the Kindle Fire logo flash, or change brightness? Does it make it to the boot animation? Black screen?
Click to expand...
Click to collapse
It will go to the kindle fire logo and then it would go to a black screen. It makes no boot animation. It will change some brightness. The words kindle fire are in white and blue. It flashes where is needs to do the boot animation and then just goes to a black screen

dontgoback4cody said:
I can only get to CWM. It does nothing but boot loop and does not go any farther then that. I can plug it into the computer and get the drivers connected and KFU can recognize it. when i put it in cwm this is the first thing i see
Click to expand...
Click to collapse
The image shows a very low battery. The behavior you describe suggests a low battery. You're in a boot loop caused by no power.
Let it sit for several hours (better...over night).
Edit:...ie. let it sit with your charger attached.....
---------- Post added at 11:14 AM ---------- Previous post was at 10:46 AM ----------
dontgoback4cody said:
I can only get to CWM. It does nothing but boot loop and does not go any farther then that. I can plug it into the computer and get the drivers connected and KFU can recognize it. when i put it in cwm this is the first thing i see
Click to expand...
Click to collapse
It might be a good idea to consider installing TWRP rather than using CWM. CWM is known to have problems with some newer ROMs.

acii22 said:
The image shows a very low battery. The behavior you describe suggests a low battery. You're in a boot loop caused by no power.
Let it sit for several hours (better...over night).
Edit:...ie. let it sit with your charger attached.....
---------- Post added at 11:14 AM ---------- Previous post was at 10:46 AM ----------
It might be a good idea to consider installing TWRP rather than using CWM. CWM is known to have problems with some newer ROMs.
Click to expand...
Click to collapse
I have tried to install it from KFU but it is always has a problem doing so. I let it charge over night and it is still doing the same thing. Here is what is says when i try to install twrp

Replace the TWRP.img that comes with KFU, with the ACTUAL one from the TWRP website.

soupmagnet said:
Replace the TWRP.img that comes with KFU, with the ACTUAL one from the TWRP website.
Click to expand...
Click to collapse
Ok i did that but it still will not let me connect the kindle to the computer it keeps giving me sdcard errors. any idea how to fix the sd card issue?

Hey were u able to fix it??
Had the same problem with mine when I used TWRP to format my SD card..but was able to solve it..
What I did was a very simple thing..got the kindle recognised as a drive..used windows partition manager to format it
It worked.. I tx the stock and installed it
Try it and let me know
Sent from my MB526 using Tapatalk 2

I had the same problem before and only had to reboot the kindle.

Nothing is working. i have given up all hope. Like this is crazy. It is screwed up for good. I cant get it to mount. If anyone wants to take a shot at it just shoot me a pm with an address and we can discuss something about trying to fix it or what the hell i did to it. Its crazy! and really messed up.

dontgoback4cody said:
Nothing is working. i have given up all hope. Like this is crazy. It is screwed up for good. I cant get it to mount. If anyone wants to take a shot at it just shoot me a pm with an address and we can discuss something about trying to fix it or what the hell i did to it. Its crazy! and really messed up.
Click to expand...
Click to collapse
I have an Idea. If you have fastboot working on your computer. You could try flashing a rom from your computer by typing
fastboot -w(wipes device)
fastboot update <path to rom> (flashes rom)
If it works, you can then fix the sdcard easier with adb/shell/partition manager. Its worth a shot.
I also found this on a website
ROM update without SDcard
If you don't have an sd card, or your slot is broken you can try this trick, but you will need a custom recovery like Clockwork.
Boot up your phone to recovery. And move your rom file to the adb directory, and start a command line ( cmd )
adb shell
mount data
adb push D:\custom_rom.zip /data/
Wait until the push finised, and restart your device to recovery again with "adb reboot-bootloader"
mount data
mount /data /sdcard ( mount the data folder into your sdcard folder, so your recovery will think that you have an sdcard installed )
Locate the ROM .Zip file you wish to flash.
Confirm the flash by following the on-screen instructions (ie: pressing the trackball, pressing the call button, etc.)
If no errors arise during the flashing process then the ROM flash was successful, Reboot the device.
With some root file explorer, remove the rom file if you don't need it anymore, to free up space.
Or use adb to remove the custom recovery
adb shell rm data/custom_rom.zip

I will give it a shot. Only thing is i dont think there is even any software on here. when i try to get it into fastboot mode here is what it says.

Then you need a factory cable to get into fastboot.

dontgoback4cody said:
I will give it a shot. Only thing is i dont think there is even any software on here. when i try to get it into fastboot mode here is what it says.
Click to expand...
Click to collapse
Hey i had the same exact problem and i had posted what i did to recover it.. did you try..
I know it sounds too simple.. but it worked for me
sometimes its the way you have formatted ur sd card

kishorev said:
Hey i had the same exact problem and i had posted what i did to recover it.. did you try..
I know it sounds too simple.. but it worked for me
sometimes its the way you have formatted ur sd card
Click to expand...
Click to collapse
When you see the error message:
Code:
- exec '/system/bin/sh' failed: No such file or directory (2)
It means you don't have access to the shell in order to switch bootmodes and access recovery, which is needed to fix this type of problem. The only way to change bootmodes without access to the shell, is in fastboot. Unfortunately, you need access to the shell to change the bootmode to fastboot as well...catch-22.
For this, you need a factory cable. The factory cable will tell the device to boot into fastboot without the need for a shell. Even with a factory cable, and access to recovery, you'll still likely need to either reformat, or repartition your sdcard in order to get it to mount.

soupmagnet said:
When you see the error message:
Code:
- exec '/system/bin/sh' failed: No such file or directory (2)
It means you don't have access to the shell in order to switch bootmodes and access recovery, which is needed to fix this type of problem. The only way to change bootmodes without access to the shell, is in fastboot. Unfortunately, you need access to the shell to change the bootmode to fastboot as well...catch-22.
For this, you need a factory cable. The factory cable will tell the device to boot into fastboot without the need for a shell. Even with a factory cable, and access to recovery, you'll still likely need to either reformat, or repartition your sdcard in order to get it to mount.
Click to expand...
Click to collapse
You are right..
But i too was had the same msg when i was trying to fastboot it.. but then it worked.. I had formatted it and then tx the stock rom and flashed it..
Probably i missing something here..
Anyways thnx

Can't mount SD card on kindle fire
I was in a similar situation and after reading the various forums i came across this action "hold down the power button until the kindle goes off and continue to hold for about 30 seconds I believe this resets the kindle and then tick debugging and mount usb storage the sdcard will open on your pc" and then you can go from there. Worked for me so good luck.

Related

[Q] Help! Stuck in Kindle Fire Recovery

I tried the unbricking guide on here but did not work. I could not get fastboot to work.
Here is the exact message I get on the screen:
'Your Kindle has detected a problem and must clear app storage. The recovery process will erase some applications and data from your device. Apps from the appstore are stored in the cloud and can be reinstalled later.
This will reset your kindle to its original factory settings. you will need to re-register your kindle prior to downloading items from your Amazon account.
Please press power button to proceed.'
After i press the power button I get a status bar indicating the restore, it then says success, then reboots and ultimately comes back to the same restore screen as noted above.
Any help is appreciated.
I have the same issue, I had just used one click to gain root access and was changing permissions to instal Vending.apk under /system/apps
A bit more information I've gathered:
* I can run adb push/shell before the Kindle Fire starts the recovery mode.
* BUT when I try to run a adb shell command I get the error
Code:
/system/bin/sh failed permission denied (13)
I've spent the best part of the day trying to find a solution to no avail. I had a good read through this post too.
I did find a couple of threads talking about a factory reset cable, I don't know if this would be any good?
http://rootzwiki.com/topic/10591-kindle-fire-fastboot-without-idme/
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
http://www.youtube.com/watch?v=7OCpJbkGb7M&feature=player_embedded
PLEASE HELP
As soon as i get my factory cable and time I'll make a guide. But really all you need to do is flash the images from the 6.2 update via fastboot
Yeah I got to that point to where it doesn't just go into logo, but infinitely boots you into recovery mode. when you launch adb it even says its recovery mode and all the folders are hidden/missing.
Sigh, I fixed my kindle and got it working again then I broke it again by accidentally changing the entire system folder to chmod 644 haha.
Anyways so far I have found no fix around it so I just returned it and got a new one. live and learn I guess.
What did you do exactly to put it in a boot-loop? I did this once before by tampering with some system files, but i was able to push the regular one's back using adb.
I made a factory cable and managed to get fastboot working to flash over a new system image.
Does anyone have a system.img file for the Kindle Fire?
OR know another way to bring up a shell via fastboot?
I might just wait till next week and see what the status is then on the CM7 ROM.
I really need to get me one of those factory cables :S but they are sold out on black hat at the moment.
hey dk560 or JandD
how was u able to get ur kindle work again? where u get the recovery files or original files? my kindle stucks in flashin kindle fire screen over and over..
i try this
http://forum.xda-developers.com/showthread.php?t=1356257
everything worked fine...but at the and had the same problem..i have normal acces with adb and all to the devide but iam not experienced...how i get the original files back to the kindle? Or any help what i can try? i stuck....
plz any suggestions...thx!!
I dunno. But I think I may have the same issue. Got brick while doing wallpaper n now my fire stuck at fastboot and window cannot detect n fastboot nv finish the run always in waiting for device. Does this mean the doom for my 3 dar old kindle fire?
finally i solved it!!
IF YOU THINK MODIFYING PERMISSIONS ON /system/app IS WHAT CAUSED YOU TO BOOTLOOP THEN FOLLOW THESE STEPS:
http://forum.xda-developers.com/showthread.php?t=1356257
thats what was my problem...it worked for me..after tmp root then this steps..and finally kindle was out of bootloop...thanks!!
I have follow that link, but my kindle now seem to be in fastboot n window detect kindle fire as unknown device. In cmd, device cannot be found, and fastboot rerun say waiting for device but nv work, I try, really wanna resolve the mess I created. I try to read n understand how to resolve but my current issue wasn't mention.
I'm still stuck with a screwed /system partition on the Kindle Fire.
I tried Calvin's instructions on installing CM7. I couldn't adb push the update.zip to the sdcard as my system folder was corrupted. I did manage to flash the Clockwork program via flashing updaterecovery.img
I got excited when adb push update.zip /sdcard/update.zip copied over, however following Calvin's instructions for Clockwork gave me a failed to mount /sdcard error. I'm guessing the clockwork mount points are virtual mount points of some kind and not the physical device
Still seeking a system.img for the Kindle Fire. I'll give it a try building one myself I guess.
UPDATE:
This post helped on building a system.img - foiled by remote data too large problem
If a rooted kindle fire user could install mkyaffs2image and grab the system.img file for me I'd be very grateful!
"mkyaffs2image /system/ /sdcard/system.img
factory cable
I think your likely in the same boat as me - though for another reason. I can't get a shell from adb and have screwed up r/w access to /system files trying to change permissions with File Expert in order to get android market to work. Seems to be one of a couple of common themes. Anyway, as far as I can tell I'm going to have to get (or just make) a factory cable in order to throw it into fastboot so that I can boot from usb. If you'll read this entire thread here: http://forum.xda-developers.com/showthread.php?p=20017371#post20017371 then you may get a better idea of what you're dealing with. JackpotClavin has so graciously donated his time and skills. You'll have to be patient for complete instructions but I think they'll be forthcoming soon. Me, I'm going to go ahead with the cable as there's not much else I can do without shell methinks. If I get something workable first, I'll post for all.
kfuller said:
I think your likely in the same boat as me - though for another reason. I can't get a shell from adb and have screwed up r/w access to /system files trying to change permissions with File Expert in order to get android market to work. Seems to be one of a couple of common themes. Anyway, as far as I can tell I'm going to have to get (or just make) a factory cable in order to throw it into fastboot so that I can boot from usb. If you'll read this entire thread here: http://forum.xda-developers.com/showthread.php?p=20017371#post20017371 then you may get a better idea of what you're dealing with. JackpotClavin has so graciously donated his time and skills. You'll have to be patient for complete instructions but I think they'll be forthcoming soon. Me, I'm going to go ahead with the cable as there's not much else I can do without shell methinks. If I get something workable first, I'll post for all.
Click to expand...
Click to collapse
I have the same problem. I did the same thing you did, right after I did it I realized what I had done I had an epic face palm moment. Ill try to make a factory cable from this http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html -- after I'm in fastboot I have no idea what to do. Looking foward to JackpotClavin's guide. Thanks JackpotClavin!
I came across this and couldn't find a solution to my issue. All issues seem to be different, but in my case I could have my device recognized in the Kindle Fire Utility, and it noted that I was in recovery mode. Trying to change one of the boot modes caused it to just hang at the activation screen.
While it's hanging if you just try to cancel the operation, CTRL+C, it will suddenly decide it wants to work, and then you just tell it not to stop. Then you're back in normal boot mode and business as usual.
Just thought I'd share since this was about the only thing that showed up from a series of google searches involving the words recovery loop, lol.
every time i load a rom in recovery (i do all wipes) it always boots back into recovery
Upstreammiami said:
every time i load a rom in recovery (i do all wipes) it always boots back into recovery
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1428428
im having trouble on getting my kindle off from the boot loop and ive read ur thread, but i cant seem to get in to fastboot nor cant i mount my kindel from TWRP so i could inject files to the SD CARD. CAN SOMEONE HELP ME????
Zenroy said:
I have the same problem. I did the same thing you did, right after I did it I realized what I had done I had an epic face palm moment. Ill try to make a factory cable from this http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html -- after I'm in fastboot I have no idea what to do. Looking foward to JackpotClavin's guide. Thanks JackpotClavin!
Click to expand...
Click to collapse
emccalment said:
I came across this and couldn't find a solution to my issue. All issues seem to be different, but in my case I could have my device recognized in the Kindle Fire Utility, and it noted that I was in recovery mode. Trying to change one of the boot modes caused it to just hang at the activation screen.
While it's hanging if you just try to cancel the operation, CTRL+C, it will suddenly decide it wants to work, and then you just tell it not to stop. Then you're back in normal boot mode and business as usual.
Just thought I'd share since this was about the only thing that showed up from a series of google searches involving the words recovery loop, lol.
Click to expand...
Click to collapse
Dj Skama said:
im having trouble on getting my kindle off from the boot loop and ive read ur thread, but i cant seem to get in to fastboot nor cant i mount my kindel from TWRP so i could inject files to the SD CARD. CAN SOMEONE HELP ME????
Click to expand...
Click to collapse
As b63 linked you, download that utility, and then do this:
-Turn your kindle off by holding the power button down for at most 20 seconds.
-Plug kindle into your computer
-Run the unbrick utility
-Turn kindle on
-Wait for the Caution Sign with the fire logo (firefirefire logo)
-Choose first option on utility (Recovery Loop)
-Wait... (a max of 10 minutes)
This should work, if not, try to turn off your kindle on and off, and then try again.
This should work regardless if your device was found or not. This sounds like the problem I had. I wish you guys the best of luck.
emccalment said:
While it's hanging if you just try to cancel the operation, CTRL+C, it will suddenly decide it wants to work, and then you just tell it not to stop. Then you're back in normal boot mode and business as usual.
Click to expand...
Click to collapse
This saved me. 2 Keystrokes...amazing

[Q] Kindle Fire keeps looping Kindle Fire logo

So I've read the similar threads, no clear answer.
I've searched the forums with no real clear answer.
So before I continue, I just want to make sure that this is correct.
Kindle Fire turns on, I have fully charged it overnight, and it still boot loops. The Kindle Fire logo comes on, flashes on and off, logo shows again with the logo glimmering, and then turns off and back on. It starts the process over. Very rarely will it go all the way to the arrow that you slide but you can't ever slide it over to get in, it just restarts.
So from my understanding is that the shell is corrupt and I need a factory cable to force fastboot. Is this correct? Thank you for reading my post.
Not necessarily. If you are talking about the stock "Kindle Fire" logo. Skip to the second half.
If you are talking about the FFF1.3 Kindle Fire logo with the Andy above it, you should be able to get into recovery, so long as you flashed a recovery.
If this is the case, start the kindle and watch the power button. When it dims press it a few times. It should change to an orange/amber color after a few presses and then boot into your recovery. From there you can load a rom and get yourself back on track.
If you have the stock bootloader, I'm not sure this will work for you, but it won't hurt to try. Worst case you are out the time it took you to make the USB.
As I found out yesterday, fastboot occurs so quick that Windows might not have the chance to discover and install drivers. So if you have a USB drive, create a firekit LiveUSB.
Once you have a LiveUSB and have booted off it and started firekit, try running normal_boot and then, when powered off, plug the kindle into the computer. With luck, it will reboot and start up into your rom.
If you are unlucky, try install_fff_twrp. Again have the kindle off, and connect it to the USB.
If that does not work try again with install_fff_twrp_from_stock as a last ditch effort.
If that fails, get your factory cable. You can try the other commands too, but I wouldn't hold your breath. But, if it works great.
ok well first off when I first turn it on, I get the yellow fire warning sign that states at the bottom to push the power button for recovery.
I'm getting things to install just fine but anytime it has anything to do with ADB, it does not work. It doesn't work with a regular cable nor the factory cable. Everytime it states that device is not found.
From what I've read the drivers are working properly if I'm able to use fastboot and it shows up in the device manager as a Android Phone > Android ADB Device.
The only time I can keep it recognized by the computer is with the factory cable.
If I use the regular cable, it recognizes it for a second then boots into TWRP but the computer doesn't see the Kindle anymore.
All I'm needing to do is reinstall STOCK Firmware. When I first got it, it just boot looped.
Use the factory cable to change your bootmode to 4000. Reboot, then turn it off and let it charge. It sounds like you are stuck in fastboot mode (4002) with a dead battery, and if I'm not mistaken the device won't charge in fastboot. The factory cable forces fastboot mode, bypasses the battery and provides power directly to the device which is why you are able to issue fastboot commands with the cable.
Sent from my Amazon Kindle Fire using xda premium
Charged
When I am not working on it, I plug it back up to the charger to charge, so charging isn't the problem. TWRP states that the battery is 98% charged when I unplug it.
in twrp you have to manually mount the system and sd card from mount options!
Mount the sd card, save the kindle update bin file, renaming it to update.zip and install from twrp
[Note to self:] Avoid using XDA while on Ambien.
wiredextreme said:
I'm getting things to install just fine but anytime it has anything to do with ADB, it does not work. It doesn't work with a regular cable nor the factory cable. Everytime it states that device is not found.
From what I've read the drivers are working properly if I'm able to use fastboot and it shows up in the device manager as a Android Phone > Android ADB Device.
Click to expand...
Click to collapse
Not necessarily true when using Windows and KFU. Sometimes you still have to uninstall/delete your drivers and reinstall again.
The only time I can keep it recognized by the computer is with the factory cable.
Click to expand...
Click to collapse
If I use the regular cable, it recognizes it for a second then boots into TWRP but the computer doesn't see the Kindle anymore.
Click to expand...
Click to collapse
If it boots directly into TWRP, then you have your bootmode set to recovery.
All I'm needing to do is reinstall STOCK Firmware. When I first got it, it just boot looped.
Click to expand...
Click to collapse
If all you want to do is reinstall stock this is easy to fix. Go to the Amazon Kindle website and download the latest 6.3 update. It will be in a .bin format.
Change the name of the update.bin to update.zip
Boot your Kindle to TWRP
Go to "Mount" and mount your SDcard
You should see "[X] Unmount Sdcard" before pressing "Mount to USB"
Your device's sdcard will show up on your computer
Place the newly renamed update.zip on your sdcard
Go to "Install" and flash the update.zip
When installed, the update.zip will turn everything back the way it was when you turned it on for the first time.
Sent from my Kindle Fire using xda premium
In TWRP, it will not let me select Mount SD Card, it will only let me select Mount System. :X
The only option I know of besides Linux liveUSB Firekit, would require you to format your sdcard and you would lose all of your data. You might be able to mount your system folder to transfer files and just flash it in TWRP from there but I've never tried it. If that doesn't work and you don't mind erasing your whole sdcard...
Boot into recovery (TWRP)
Get your command prompt ready with adb in your present working directory (if you're not sure type: dir )
adb shell
echo /dev/block/mmcblk0p12 > /sys/devices/platform/usb_mass_storage/lun0/file
That will mount sdcard to your computer like an external drive. You'll probably have to format it. In Windows, select Quick Format > FAT32 > block size 4096.
Just make sure that the volume you are formatting is your sdcard (>5Gb) You should be able to move your update.zip to it then.
soupmagnet said:
You'll probably have to format it
Click to expand...
Click to collapse
May be am missing something here, but why can't he "adb push update.zip sdcard/Download" and Flash it from twrp?
I tried to install [JB 4.3.1] CM10.2/SGT7 [20131022] and now bootlogo CM is looping. Tried reinstall but result is the same. I can enter in FFF, TWRP is installed. What should i do?

[Q] kindle fire boot loop-ing CM9 after gede ROM flash

Hi
I rooted my KF using kindle fire utility 0.9.5 -successfully.
After flashing gede ROM, KF is boot looping (there is a CM9 logo with the android guy flashing on the screen)---rebooting KF brings me back to the same screen
I have absolutely no access to the device. Kindle unbrick v.1--does not do anything, it gives: waiting for device
kindle fire utility gives: device offline
adb device gives: error: device not found
however, when i plug in the KF into my computer, under Device Manager--the KF is listed as "Galaxy" with a yellow triangle. No longer listed as kindle.
Please help! Thanks
Does this sound like it may apply to you?
http://forum.xda-developers.com/showthread.php?p=25400963
&
http://forum.xda-developers.com/showthread.php?p=20317299
soupmagnet said:
Does this sound like it may apply to you?
http://forum.xda-developers.com/showthread.php?p=25400963
&
http://forum.xda-developers.com/showthread.php?p=20317299
Click to expand...
Click to collapse
Thank you for your response. the KF is fully charged so power is not an issue. The biggest issue is I have no access to the device in order to do anything. Device cannot be recognized and it reads as a Galaxy in device manager
Oh, that problem...
OK, read these
Driver information:
http://forum.xda-developers.com/showthread.php?p=23747671
Hardware ID information and reply from gedemis w/fix:
http://forum.xda-developers.com/showthread.php?p=25444709
soupmagnet said:
Oh, that problem...
OK, read these
Driver information:
http://forum.xda-developers.com/showthread.php?p=23747671
Hardware ID information and reply from gedemis w/fix:
http://forum.xda-developers.com/showthread.php?p=25444709
Click to expand...
Click to collapse
Thanks soupmagnet. However still no progress. my device is still bootlooping.
How can I get into recovery while it is still bootlooping.
I am quite (100%) certain the issue you are describing is a dead battery. It is the only issue known that causes the boot logo to flash like that. Your battery most likely died while asleep as some roms don't sleep or shut down properly.
I'm willing to bet if you pay attention and follow the steps from the links I originally gave you, you'll be able to fix your device.
soupmagnet said:
I am quite (100%) certain the issue you are describing is a dead battery. It is the only issue known that causes the boot logo to flash like that. Your battery most likely died while asleep as some roms don't sleep or shut down properly.
I'm willing to bet if you pay attention and follow the steps from the links I originally gave you, you'll be able to fix your device.
Click to expand...
Click to collapse
Qem is saying that as soon as the ROM was flashed and went into boot mode, the kindle kept bootlooping the ROM intro over and over.
Turning the KF on and off does nothing as the KF is trying to boot into the ROM but never gets past the intro screen (blue-ish android cartoon, CM9 type intro).
Because of the bootlop, there is no way to get into recovery physically and when connected to the computer, the kindle is being shown as a galaxy unit with no drivers, probably due to the flashed ROM.
mrslax said:
Qem is saying that as soon as the ROM was flashed and went into boot mode, the kindle kept bootlooping the ROM intro over and over.
Turning the KF on and off does nothing as the KF is trying to boot into the ROM but never gets past the intro screen (blue-ish android cartoon, CM9 type intro).
Because of the bootlop, there is no way to get into recovery physically and when connected to the computer, the kindle is being shown as a galaxy unit with no drivers, probably due to the flashed ROM.
Click to expand...
Click to collapse
My apologies. Apparently I misunderstood that portion of the first post and it's likely I'm just getting threads confused. So again, I apologize.
Based on this newly discovered information, I'm willing to bet you have Clockwork Mod recovery installed as opposed to TWRP. Yes? or No?
soupmagnet said:
My apologies. Apparently I misunderstood that portion of the first post and it's likely I'm just getting threads confused. So again, I apologize.
Based on this newly discovered information, I'm willing to bet you have Clockwork Mod recovery installed as opposed to TWRP. Yes? or No?
Click to expand...
Click to collapse
Qem can't post links so I posted her response instead.
"Again, thanks for your response. Yes I have clockwork Mod.
At first the KF kept bootlooping to the KF intro screen followed by a small portion of the ROM intro.
After multiple resets the intro just continues forever.
Here is a link to what it looks like. Its been like this even after powering off and on.
http://www.youtube.com/watch?v=npx9HIbF5Po"
Any ideas for bootloop
soupmagnet said:
My apologies. Apparently I misunderstood that portion of the first post and it's likely I'm just getting threads confused. So again, I apologize.
Based on this newly discovered information, I'm willing to bet you have Clockwork Mod recovery installed as opposed to TWRP. Yes? or No?
Click to expand...
Click to collapse
Please do you have any ideas re:bootloop. I am stuck.
Qem said:
Please do you have any ideas re:bootloop. I am stuck.
Click to expand...
Click to collapse
Yes. I'll try to explain it in a way that you'll understand.
You have Clockwork Mod
You need TWRP
no way to mount TWRP
soupmagnet said:
Yes. I'll try to explain it in a way that you'll understand.
You have Clockwork Mod
You need TWRP
Click to expand...
Click to collapse
Thanks.
However did you see the you-tube link in chat #9?
I do not have any access to the device (in order to install TWRP) because no application (KF utility, Kindle unbrick, cmd prompt) can find the device: "ERROR: device not found".
The only place in which the device is found is in device manager but it lists the KF as "Galaxy".
May be I might be missing something...
You need to flash a different rom, like cm7, older version of cm9, or MoDaCo, just long enough to install TWRP. CWM will not install later versions of cm9.
You can mount your sdcard in TWRP, or if your drivers are working properly, you can use the "push" command in adb to transfer another rom.
soupmagnet said:
You need to flash a different rom, like cm7, older version of cm9, or MoDaCo, just long enough to install TWRP. CWM will not install later versions of cm9.
You can mount your sdcard in TWRP, or if your drivers are working properly, you can use the "push" command in adb to transfer another rom.
Click to expand...
Click to collapse
I am having the same issue.
The problem is we flashed CWM, then a CM9 rom. Now just runs the aminamtion.zip boot screen and does nothing. it is unable to get into fastboot or CWM. inorder to flash another rom to install TWRP
KF has internal sdcard... cant mount TWRP
soupmagnet said:
You need to flash a different rom, like cm7, older version of cm9, or MoDaCo, just long enough to install TWRP. CWM will not install later versions of cm9.
You can mount your sdcard in TWRP, or if your drivers are working properly, you can use the "push" command in adb to transfer another rom.
Click to expand...
Click to collapse
Thanks. I appreciate your help.
Pardon me I am desperate to get my KF in a working condition.
However the KF does not have an external SD card. Therefore to mount TWRP on the sdcard, I need access to the device. This access is what i dont have... The sdcard on the KF is internal and I cannot open any folders in the KF due to the bootloop
Qem said:
Thanks. I appreciate your help.
Pardon me I am desperate to get my KF in a working condition.
However the KF does not have an external SD card. Therefore to mount TWRP on the sdcard, I need access to the device. This access is what i dont have... The sdcard on the KF is internal and I cannot open any folders in the KF due to the bootloop
Click to expand...
Click to collapse
No, you're misunderstanding me.
If you want to install the TWRP from inside the rom (i.e. using gscript or smirkit), you have to access recovery (in your case, CWM) to mount your sdcard. It will mount to your computer as an external drive, like a thumb drive. While mounted, transfer a rom that will work with CWM from your computer to your sdcard, then flash it in recovery to have a working rom to install TWRP.
Otherwise, if you want to use the command line method to install TWRP...
fastboot flash recovery /path/to/twrp2.1.img
...but considering KFU says "offline", that is out of the question unless you can get your drivers working.
soupmagnet said:
No, you're misunderstanding me.
If you want to install the TWRP from inside the rom (i.e. using gscript or smirkit), you have to access recovery (in your case, CWM) to mount your sdcard. It will mount to your computer as an external drive, like a thumb drive. While mounted, transfer a rom that will work with CWM from your computer to your sdcard, then flash it in recovery to have a working rom to install TWRP.
Otherwise, if you want to use the command line method to install TWRP...
fastboot flash recovery /path/to/twrp2.1.img
...but considering KFU says "offline", that is out of the question unless you can get your drivers working.
Click to expand...
Click to collapse
So I was able to find drivers for the "Galaxy" (http://pastebin.com/nhbaaWMu) and installed it. This enabled KFU to recognize my device as "online".
However there are two issues (1) there is no access to the drive. it mounts like an external drive, but does not open/explore. like an external drive or USB would.
(2) when i try to go into recovery mode via KFU, KFU gets stuck.
When you say fastboot flash recovery /path/to/twrp2.1.img, does the "path/to/twrp2."1-- mean the actual file path to where TWRP is located on my computer or is the "path/to" part of the cmd line input
Qem said:
When you say fastboot flash recovery /path/to/twrp2.1.img, does the "path/to/twrp2."1-- mean the actual file path to where TWRP is located on my computer or is the "path/to" part of the cmd line input
Click to expand...
Click to collapse
Actual path to file.
[Edit:] I've heard one of the roms here won't mount the sdcard in TWRP but I'm not sure which one. It may be gedeRom.
still boot looping affter fastboot+twrp2
soupmagnet said:
Actual path to file.
[Edit:] I've heard one of the roms here won't mount the sdcard in TWRP but I'm not sure which one. It may be gedeRom.
Click to expand...
Click to collapse
Thank you for your help thus fat, I appreciate it. However I still have not fixed the issue...
I tried it (actual path to file), it still said "waiting for device".
after a while, I held held power button to manually reboot, still nothing.
I also uninstalled and re installed the drivers... nothing
using KFU to boot into normal mode still returns "system cannot find the drive specified."
at wits end...
Pardon the typo..
soupmagnet said:
Actual path to file.
[Edit:] I've heard one of the roms here won't mount the sdcard in TWRP but I'm not sure which one. It may be gedeRom.
Click to expand...
Click to collapse
In prev post, I meant thanks for your help thus "far" and not "fat"
sorry for the typo

Kindle Fire stuck on boot triangles

I was told to post this here:
The Problem:
I tried to take the crappy amazon software that only works in the US off this kindle fire, Installed JandyKane and Gapps with no problems (i cleared dalvik cache, regular cache, and factory reset) Also installed Clockwork Recovery (which i read somewhere that might have been the problem).
(note: I used the KF utility)
Now when i turn the device on, it shows the Kindle fire logo for a second or two, then a bunch of triangles float on the screen forever and nothing happens.
Ive tried a few unbrick utilities but it keeps saying it cant find the device. Im having troubles booting into recovery mode. (the utility says device not found)
This isnt even my Kindle Fire and its causing me so many problems >.>
Justos said:
I was told to post this here:
The Problem:
I tried to take the crappy amazon software that only works in the US off this kindle fire, Installed JandyKane and Gapps with no problems (i cleared dalvik cache, regular cache, and factory reset) Also installed Clockwork Recovery (which i read somewhere that might have been the problem).
(note: I used the KF utility)
Now when i turn the device on, it shows the Kindle fire logo for a second or two, then a bunch of triangles float on the screen forever and nothing happens.
Ive tried a few unbrick utilities but it keeps saying it cant find the device. Im having troubles booting into recovery mode. (the utility says device not found)
This isnt even my Kindle Fire and its causing me so many problems >.>
Click to expand...
Click to collapse
Is this what you're refering to when you say you see floating triangles?
http://androidbootanimation.com/wp-content/uploads/2012/08/nexus-7-bootanimation.jpg
If so, That is the jandycane/Jellybean Boot animation. On first boot that could take a few minutes before it finishes. It does, however, sound like you are having other problems... have you tried contacting the kindle using fastboot?
Also, I would highly suggest flashing TWRP (team win recovery project) rather than CWM on the Kindle Fire, on most devices I would recommend CWM but on this one it doesn't work as well and leads to problems >>
I also assume that you flashed firefirefire because you said you saw the kindlefire logo before it went to the triangles so you should be fine on that front.
nschiwy said:
Is this what you're refering to when you say you see floating triangles?
If so, That is the jandycane/Jellybean Boot animation. On first boot that could take a few minutes before it finishes. It does, however, sound like you are having other problems... have you tried contacting the kindle using fastboot?
Click to expand...
Click to collapse
Yes thats it! Im going to leave it on for about 5-15 minutes and see what happens. il let you know
I have tried to boot into fastboot mode with the utility and it says cannot find the file specified.
btw: i dont think i installed firefirefire...
EDIT: Yep, after letting the animation run for 10 minutes still nothing.
Im going to try using TWRP now. Il let you know if it helped.
EDIT2: Nope im getting random errors in the command prompt. Is it 100% necessary to use this program?
Justos said:
Yes thats it! Im going to leave it on for about 5-15 minutes and see what happens. il let you know
I have tried to boot into fastboot mode with the utility and it says cannot find the file specified.
btw: i dont think i installed firefirefire...
EDIT: Yep, after letting the animation run for 10 minutes still nothing.
Im going to try using TWRP now. Il let you know if it helped.
EDIT2: Nope im getting random errors in the command prompt. Is it 100% necessary to use this program?
Click to expand...
Click to collapse
If you're talking about KFU, then no. It is not 100% necessary, It is just designed to make it easier for users so they don't have to use command prompt on their own. I am uploading KindleADB from the burrito root method to help us with what you need to do. I will post a link here when it is finished uploading. Do you know how to use command prompt/adb at all?
KindleADB.zip: http://www.mediafire.com/?1fb30q3wqf95b3i
download this file and unzip and then place it on the root directory of your C:/ Drive (this is not completely necessary, it is just for convenience)
Then try seeing if your device shows up in adb by typing in:
Code:
cd /
cd kindleadb
adb devices
OR
Code:
cd /
cd kindleadb
fastboot getvar product
Either way you want it to show either a series of numbers or say something like amazon kindle or something to that degree, if it is blank or does not leave the <waiting for device> status then we will need to go in another direction. My suggestion for fastboot would be to turn the kindle completely off and then do those commands and then plug in your kindle when it says <waiting for device>... get back to me on your results and we can go from there
Did both of them. On the first part it says
List of Devices attached: (nothing shows up)
second time i did exactly what you said. it was waiting for device before i turned the kindle on, nothing happened.
EDIT: Okay I tried using the utility again, whenever i try to fastboot or boot into recovery it gives me this error
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The kindle has been told to reboot in Fastboot Mode.
Press any key to continue . . .
I'm having the same issue here.
The triangles keep turning and nothing happens.
In the KFU the devices keep showing OFFLINE and Boot Status UNKNOW.
The cd /
cd kindleadb
adb devices
don't show the device and
cd /
cd kindleadb
fastboot getvar product
show waiting for device
Edited:
I dunno what i've done, but im KFU appears Online in normal boot (4000), but the options don't work anymore.
Justos said:
Did both of them. On the first part it says
List of Devices attached: (nothing shows up)
second time i did exactly what you said. it was waiting for device before i turned the kindle on, nothing happened.
EDIT: Okay I tried using the utility again, whenever i try to fastboot or boot into recovery it gives me this error
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The kindle has been told to reboot in Fastboot Mode.
Press any key to continue . . .
Click to expand...
Click to collapse
As long as you have CWM instead of TWRP, you're just wasting your time trying to install Jelly Bean. Install TWRP and try again.
same problem
I have the same exact problem with my fire, it happened two days ago but i hadn't seen anyone else with the problem. I couldn't fix it so i ordered a factory cable on ebay, I'm waiting on that now...
no fff? how about just booting to recovery and flashing a new rom after a full wipe or restoring a backup or have the normal ways of doing things just become obsolete lol I mean so you cant flash isc or jelly bean mount your sd card in recovery transfer one of a few different cm7 roms which will flash right on cwmr and your golden ...
Thepooch said:
no fff? how about just booting to recovery and flashing a new rom after a full wipe or restoring a backup or have the normal ways of doing things just become obsolete lol I mean so you cant flash isc or jelly bean mount your sd card in recovery transfer one of a few different cm7 roms which will flash right on cwmr and your golden ...
Click to expand...
Click to collapse
I'm trying to but, but when I try to enter in recovery mode, i get this:
The system cannot find the drive specified.
Failed to Copy 'files\rcmode' to 'data/local/rcmode' : permission denied
unable do chmode /data/local/rcmode: no such file or directory
/system/bin/sh: data/local/rcmode: not found
recovery?
Reinaque said:
I'm trying to but, but when I try to enter in recovery mode, i get this:
The system cannot find the drive specified.
Failed to Copy 'files\rcmode' to 'data/local/rcmode' : permission denied
unable do chmode /data/local/rcmode: no such file or directory
/system/bin/sh: data/local/rcmode: not found
Click to expand...
Click to collapse
i'm seeing that too when i try to change it to recovery on KFU, but now its actually showing adb online and boot status 4000 as oppposed to when it said offline and unknown for me
What are all the ways to boot into recovery mode? It wont do it with the KFU.
I understand what I need to do now, Factory reset, then install TWRP, then firefirefire, then flash the rom and Gapps?
How am i supposed to do this if i cant get into recovery mode?
Justos said:
What are all the ways to boot into recovery mode? It wont do it with the KFU.
I understand what I need to do now, Factory reset, then install TWRP, then firefirefire, then flash the rom and Gapps?
How am i supposed to do this if i cant get into recovery mode?
Click to expand...
Click to collapse
First I would try using the kindle unbrick utility:
I couldn't find the thread for this so I just have it uploaded to my mediafire account: http://www.mediafire.com/download.php?6kxjs8kbmgn8h3l
I also found this Kindle Fire Unbrick Utility, it might actually be a newer version of the one I provided above with a Graphic UI: http://forum.xda-developers.com/showthread.php?t=1428428
If that doesn't work I would suggest trying a linux environment to contact your device, as Android is linux based and therefore can communicate with a linux machine better than a windows machine. (plus drivers are always a giant mess in windows)
Use this guide to make a portable linux box to try to save your kindle:
http://forum.xda-developers.com/showthread.php?t=1670405
If all else fails, you're probably going to need a factory cable to get your Kindle back up and running:
http://forum.xda-developers.com/showpost.php?p=20380015&postcount=9
Once you have this you can run commands from linux very easily to unbrick your kindle. If you need help with this feel free to PM me.

[Q] Computer dosn't see the Kindle fire

Good time of the day to everyone. I have the problem with my Kindle Fire first gen. Please tell me the solution If someone knows. First was the problem with picture on the screen then I changed the controller of LVDS and then image became normal. But first I thought that this problem is software and though I almost didn't see nothing on the screen I tried to solve the problem in TWRP. When display started to show good picture I did see that tablet do not boot on. So now I can start TWRP recovery but in the log I see that tablet cannot mount sd-card. This is half of the proble. I saw the solution on this forum how to mount by ADB and some command from command line. But the computer also do not see the tablet. The tablet shoes in device manager just from the begining of the booting for about 2 sec. And I cannot do something. Is there any solution in this situation?
Ichigo said:
You can't mount? Take a look at this: http://forum.xda-developers.com/showthread.php?t=1949372
Click to expand...
Click to collapse
Thanks, I will. The problem is that I cannot do any adb which needs that tablet is connected to computer and recognized. My computer see thee tablet only in the time of booting in the begining.
One question, is it possible to write all commands wich I see in instractions for unbricking kindle in native terminal of the TWRP?
Is it possible to solve the problem with "can't mount /sdcard (invalid argument)" from TWRP itself without ADB, I mean computer. Then I could
make some BAT file wich will handle connection with KF in the begining of booting and write update.zip to sdcard on the tablet, then I could
to flash it.
Please help! I can PAY for the real help by PayPal.
toly084 said:
One question, is it possible to write all commands wich I see in instractions for unbricking kindle in native terminal of the TWRP?
Is it possible to solve the problem with "can't mount /sdcard (invalid argument)" from TWRP itself without ADB, I mean computer. Then I could
make some BAT file wich will handle connection with KF in the begining of booting and write update.zip to sdcard on the tablet, then I could
to flash it.
Please help! I can PAY for the real help by PayPal.
Click to expand...
Click to collapse
Here`s your answer http://forum.xda-developers.com/showthread.php?t=1850038 a live usb with soupkit. If you want help and you can catch me online I would be happy to assist and it wont cost you a dime just time.
Thepooch said:
Here`s your answer http://forum.xda-developers.com/showthread.php?t=1850038 a live usb with soupkit. If you want help and you can catch me online I would be happy to assist and it wont cost you a dime just time.
Click to expand...
Click to collapse
Thank you very much. I see that Soupkit is just what I needed. First I need to install Ubuntu, then will try to recover my KF wich I made two of them not working. I hope one will work. I thought I have no luck and only way to reball a flash from another board of KF wich I have as spare.
Thepooch said:
If you want help and you can catch me online I would be happy to assist and it wont cost you a dime just time.
Click to expand...
Click to collapse
Dear Sir. So, I tried SoupKit. The same situation as with ADB in Windows. My KF can be seen just in the begining of the booting.
And this is not enaugh time to do something. Also I wanted to ask that man wich made SoupKit, but for now it is not allowed for me to pos there.
toly084 said:
Dear Sir. So, I tried SoupKit. The same situation as with ADB in Windows. My KF can be seen just in the begining of the booting.
And this is not enaugh time to do something. Also I wanted to ask that man wich made SoupKit, but for now it is not allowed for me to pos there.
Click to expand...
Click to collapse
Boot into recovery and see if your computer will detect it.
soupmagnet said:
Boot into recovery and see if your computer will detect it.
Click to expand...
Click to collapse
Thank you for the answer, I tried to post in your theme but it wasn't allowed.
The computer see my KF only in the begining of the booting 2-3 sec. I also tried your SoupKit in the Ubuntu, the same problem,
I just can flash bootloader, recovery and that's all.
toly084 said:
Thank you for the answer, I tried to post in your theme but it wasn't allowed.
The computer see my KF only in the begining of the booting 2-3 sec. I also tried your SoupKit in the Ubuntu, the same problem,
I just can flash bootloader, recovery and that's all.
Click to expand...
Click to collapse
Okay, boot into Ubuntu, let the device boot up normally and enter the following in the terminal...
Code:
lsusb
Let me know what the output is
soupmagnet said:
Okay, boot into Ubuntu, let the device boot up normally and enter the following in the terminal...
Code:
lsusb
Let me know what the output is
Click to expand...
Click to collapse
I'm sorry, but I can't do this right now. Notebook on wich I installed Ubuntu I left on the work and tablet also. Tomorrow I will try to do so. I will explain what happened. First I had a problem with picture on the screen, I hardly could see what is on the screen. I thought it was the software problem and try in the recovery to solve the problem. But as I couldn't see what I do, I done something what bricked my KF. The problem with picture was solved by reballing the LVDS controller. And now I have a tablet wich cannot mount system, data, sdcard what I saw in log of TWRP. And also tablet can't be seen now by computer as it was and I cannot recover tablet by ADB. I also asked before if is it possible to do something in TWRP in terminal that to solve the problem with mount of partitions.
toly084 said:
I'm sorry, but I can't do this right now. Notebook on wich I installed Ubuntu I left on the work and tablet also. Tomorrow I will try to do so. I will explain what happened. First I had a problem with picture on the screen, I hardly could see what is on the screen. I thought it was the software problem and try in the recovery to solve the problem. But as I couldn't see what I do, I done something what bricked my KF. The problem with picture was solved by reballing the LVDS controller. And now I have a tablet wich cannot mount system, data, sdcard what I saw in log of TWRP. And also tablet can't be seen now by computer as it was and I cannot recover tablet by ADB. I also asked before if is it possible to do something in TWRP in terminal that to solve the problem with mount of partitions.
Click to expand...
Click to collapse
First we need to see if Linux is detecting your device when plugged into USB, hence the 'lsusb' command. We need to get the communication problem resolved before you can fix your mounting issues. As far as using TWRP's command line to fix the partitions, not likely. I've tried it before and it didn't work out.
It's possible, for whatever reason, your device is reporting a different product ID than what is configured in the udev rules, but we probably won't know for sure until we have access to 'lsusb'.
soupmagnet said:
First we need to see if Linux is detecting your device when plugged into USB, hence the 'lsusb' command. We need to get the communication problem resolved before you can fix your mounting issues. As far as using TWRP's command line to fix the partitions, not likely. I've tried it before and it didn't work out.
It's possible, for whatever reason, your device is reporting a different product ID than what is configured in the udev rules, but we probably won't know for sure until we have access to 'lsusb'.
Click to expand...
Click to collapse
Tomorrow I will try "lsusb" and will write an answer.
toly084 said:
Tomorrow I will try "lsusb" and will write an answer.
Click to expand...
Click to collapse
Good time of the day. As I thought computer do not see the device.
But now I can remain in fastboot mode by the comman "fastboot getvar product". And SoupKit see the device in fastboot. Is it possible somehow to transfer the firmware file to the KF?
toly084 said:
Good time of the day. As I thought computer do not see the device.
But now I can remain in fastboot mode by the comman "fastboot getvar product". And SoupKit see the device in fastboot. Is it possible somehow to transfer the firmware file to the KF?
Click to expand...
Click to collapse
If SoupKit sees the device in fastboot as you say, use it to install recovery and boot into it
soupmagnet said:
If SoupKit sees the device in fastboot as you say, use it to install recovery and boot into it
Click to expand...
Click to collapse
I have FFF booty v1.4a installed and TWRP recovery installed.
I think because of the problem of the mounting of sdcard / system / data computer do not see the device.
toly084 said:
I have FFF booty v1.4a installed and TWRP recovery installed.
I think because of the problem of the mounting of sdcard / system / data computer do not see the device.
Click to expand...
Click to collapse
Use fastboot to reinstall TWRP and check 'lsusb' again.
soupmagnet said:
Use fastboot to reinstall TWRP and check 'lsusb' again.
Click to expand...
Click to collapse
By the help of your instructions from the another post about mounting of SYSTEM DATA CACHE and SDCARD,
now all partition can be mounted only SDCARD won't. But computer as it was before do not see device in normal mode,
just in fastboot. All work concirning mounting SYSTEM DATA CACHE was made from the terminal of TWRP.
soupmagnet said:
Okay, boot into Ubuntu, let the device boot up normally and enter the following in the terminal...
Code:
lsusb
Let me know what the output is
Click to expand...
Click to collapse
In the list there is no the device. Only standart wich belongs for notebook hardware. If I could mount sdcard then I could flash update.zip from fastboot, but I can't.
toly084 said:
By the help of your instructions from the another post about mounting of SYSTEM DATA CACHE and SDCARD,
now all partition can be mounted only SDCARD won't. But computer as it was before do not see device in normal mode,
just in fastboot. All work concirning mounting SYSTEM DATA CACHE was made from the terminal of TWRP.
Click to expand...
Click to collapse
Your mounting issues shouldn't have anything to do with whether or not Linux will detect your device. Are you using a LiveUSB, VM, or full Linux boot?
soupmagnet said:
Your mounting issues shouldn't have anything to do with whether or not Linux will detect your device. Are you using a LiveUSB, VM, or full Linux boot?
Click to expand...
Click to collapse
I installed full Ubuntu. I do not know why tablet can't be seen in linux.

Categories

Resources