yashsingh1/xdaforums huggingface dataset:
[Kindle Fire General] yareally:
I would gather that the "recovery" means you're still stuck somewhere in limbo (because normal recovery on devices you can still run adb shell). I would think it would say you're in fastboot if you are, but perhaps not since the kindle is kind of weird like that. Try seeing if anything comes up in fastboot when you run a command with it.

You did only wipe user data right? You didnt try wiping /system or the kernel? If you did wipe those things, don't panic, you can undo that stuff (I think as long as you can get back to fastboot again), just makes for more work though.

Adb does seem to respond so maybe there's also a chance you can push the borne shell (sh) back to /system/bin/ to get access to the shell (though I have no idea exactly the current state of your device without more details [the more details, the better]).

When you say loop, do you mean it keeps rebooting or it's just stuck on a screen. I think the term "looping" gets misused too much when what one really means is "soft-bricked." Looping, to me, would mean the device keeps resetting or alternating between some screens, but I've seen people say that when it's not actually doing that as well.
[Kindle Fire General] ubeezee:
You're welcome!
[Kindle Fire General] acteck19:
Kindle seems to stuck in fastboot mode , but

but i cannot access it using adb or fastboot?

i have only kindle fire title in the middle of the screen and when i connect it to usb , nothing happened. There used to be message like usb is not recognised or even kindle connected, but now nothing

i am using vm ware windows on mac..

fastbood says <waiting for device>

help would be much appreciated

Thank you
[Kindle Fire General] yareally:
Is the device actually getting passed through to the virtual machine? In VM Workstation you have to specify a USB device is allowed to be connected to the virtual machine. I would double check to make sure it's connected to the virtual machine and not to your host machine.

Also, why are you doing it in a virtual machine, let alone Windows on OSX (you have a perfectly good command line at your disposal with bash in the osx terminal)? Other than the tutorial supplying only fastboot for windows, you could easily find the fastboot binary for linux or for osx with a google search. Given that you have the proper fastboot binary file for your system, the rest of the tutorial will work fine on linux or osx. Although you could do it in windows as well (the OP was using cygwin on windows to do it, although I think cmd.exe will work okay as well). Just thinking you're making more work for yourself than needed :)
[Kindle Fire General] acteck19:
i have tried on Mac as well

and no luck, i am thinking maybe something is wrong with the cable, because before i had this message where do i want to connect USB device to MAc or windows, now i do not have this message it is like nothing is happaning when i connect kindle to the computer...

i have tried to use mac, however fastboot says the same waiting for the device...

so obviously something is not right...

i wish i had stopped playing with it before i had gotten to this point, but it is too late for that so i need to find a way to return it back to live

I will take it today to work and will try different cables and normal windows, not virtual, maybe it will work.

it is strange though, that i had this message before about connecting USB, but not anymore.. I am trying to charge it in full and will see how it goes..

Thank you

---------- Post added at 06:05 AM ---------- Previous post was at 05:58 AM ----------

Interestedly, the other day , when my poor kindle was almost out of power, i plugged it in to the computer and had this message that USB is not recognised and so on , but when i disconnected it, it made interesing knows and i saw the first screen with slider and time. Unfortunately, i as soon as i disconnected it turned it self off..Now i do not have even that stage...see my previous post..

Thank you

--update

i have charged my poor kindle and connect it to MAc

and ren fastboot

./fastboot-mac -i 0x1949 -w

erasing 'userdata'... OKAY

erasing 'cache'... OKAY

..-MacBook-Air:tools leo$ ./fastboot-mac -i 0x1949 oem idme bootmode 4000

... OKAY

..-MacBook-Air:tools leo$ ./fastboot-mac -i 0x1949 reboot

rebooting...

so, it looks like it is working, but rebooting has been already on the screen for 5 minutes..it should not take that long to reboot, shouldn't it?

Maybe i need to reboot it manually?

--update

as i said before it stuck in rebooting...so i manually rebooted it and it looks like now it is doing what is should do according your manual, so, you are life saver,

It is so great that you have done this work for people like me :-) THANK YOU!
[Kindle Fire General] gurpz:
Just had a few problems with my kindle fire "process android.process.acore has stopped unexpectedly" will this be able to resolve my problem it doesnt let me get past that screen but allows me to enter my password and swipe. Sorry for being nooby :(

---------- Post added at 11:41 PM ---------- Previous post was at 11:21 PM ----------

now it wont boot past the kindle fire screen!
[Kindle Fire General] yareally:
Awesome, glad it worked out in the end :)
[Kindle Fire General] yareally:
Probably need to do a full wipe of your user data then like in the OP's directions to fix things.
[Kindle Fire General] gurpz:
Il give it a go but don't really understand some of the stuff
[Kindle Fire General] yareally:
Ask questions if you don't. Explicit questions with lots of details, please of course :)
[Kindle Fire General] acteck19:
maybe you can try that..

obviously, i am not expert in Android tablets ( look my post above) but it seems that you need fully charge your tablet and do fastboot to erase everything to factory settings. However, i am not sure wherever you are ready to loose all your data or not.
[Kindle Fire General] ogreinside:
This is exactly what is happening to me. However, I may have done this by accident. I had rooted successfully with SuperOneClick, and installing apps were working. When I got to trying to get the Market app installed, I remounted /system as rw, then stupidly following random posts (because it kept failing in ES File Explorer and I didn't try adb push/install) I did chmod 644 /system. Immediately I got a dialogue box in strange language, then just hung. After waiting almost an hour I held the power button down for 10 or so seconds and rebooted it. It then went to the screen with the kindle fire logo and a paragraph stating it would attempt recovery and erase my user data, press power to proceed.

After doing this it shows the kindle fire logo again with a progress bar that completes, then reboots after a few minutes - right back into the recovery message. I tried holding the power button for 20 seconds, then holding for 2 as Amazon's site says, same thing.

It never responds to fastboot, just says <waiting for device> no matter what I do.

"adb shell" commands simply give "no such file or directory". However, it does respond to "adb reboot" and "adb reboot-recovery".

Is there anything I can try to do to push a clean image (if there is one somewhere)? Or push chmod permissions w/o using the shell? Or am I hosed?

I'm a dumbass, but hopefully others out there who are new to rooting will read and understand the Market part properly. I think next time I'll just buy and sideload Root Explorer (or try adb push/install). I'm guessing this is where a recovery mod would help for backups. Maybe I'll wait to try again when that is working.

A Moron.
[Kindle Fire General] yareally:
You can't flash any sort of image without being able to access fastboot. Keep trying to bring up fastboot.

The proper permissions for the /system directory itself (if you didnt do a recursive chmod on the directory) are 755 if you can still change it somehow in adb.

Maybe you can use the adb restore somehow. Though, I am not sure how the syntax for it goes (if it wants an .img file or say a .tar.gz).
[Kindle Fire General] victimofcanada:
Am I screwed?

ADB wont recognize my kindle and I cant adb shell
[Kindle Fire General] yareally:
Have to be more descriptive than that. In as many details as possible:

1) what were you doing that you need to now "unbrick?"

2) did adb ever work for you on the kindle?

3) were you able to complete any of the "unbricking" process and if so, what step was the last one you were able to complete?

4) Does your Operating System detect your kindle when you plug it in?
[Kindle Fire General] Nerfherder_1:
Fastboot problem with Kindle Fire

Hey guys,

I rooted my kindle and managed to get android market place installed and was loving life there for a while untill I installed Go Launcher Ex from the web. After that it would not get past the Kindle Fire logo.

So I followed the instructions by Ubeezee and I managed to get fastboot on the kindle in step 3 done, now my computer is not comunicating with the Kindle. None of the fastboot commands work and I'm wondering if it could be a usb driver issue? Or do I need a special usb cable?

Update!!

I found it! It was my USB driver. I selected a different one from four options I had and then everything worked like it should, now my Kindle Lives Again!!!

I just want to thank all the people who post the answers and help us noobs out!
[Kindle Fire General] ubeezee:
No you dont need a pc. All you need is a command line which in your case is called Terminal

You will however, need to find a mac version of fastboot
[Kindle Fire General] Vashypooh:
Just in-case someone has this issue here, I am going to offer this.

I had a friend today brick his KF, and through remote desktop I was able to completely restore the device back to

stock

. This thread didn't seem to work, as what he did completely mangled it trying to remove CM7. The important thing here to note is, he had

totaled

the SDcard and it was unmountable with whatever he did.

If someone else has a KF, and can ONLY access ADB/Fastboot, and can not get back to workable by any means, I would be interested in seeing if I can fix yours too, to try and automate what I did for others. I am pretty nifty with some batch files and such, so could probably come up with a slick way of doing it.

For a dev who maybe has one and wants:

Download and label it as update.zip http://www.amazon.com/gp/help/customer/display.html?nodeId=200790620

Create command file with "--update_package=/data/local/tmp/update.zip" inside of it

ZergRush

Mounted /cache/ RW

adb push stock recovery

Write stock recovery

adb push command file to /cache/recovery/

adb push update.zip to /data/local/tmp/

Rebooted to recovery 5001

This is from the top of my head what I did to make it work. I don't own a kindle fire, so I can't really test it here. Hope this helps.

Please keep in mind this is a complete last ditch resort. If you have the SD card working and can mount it, there are

much

better ways of doing this, but if all you have is ADB/Fastboot, this will get you fixed up.
[Kindle Fire General] animefun135:
and again, if fastboot and adb don't work - this can't help restore kindle fire?
[Kindle Fire General] yareally:
There's already a thread that tells you how to do this and/or you could add to it there. Please don't pollute this thread with ways to unbrick from experimental firmware. We're trying to keep people from asking questions about cm7 on this thread.

http://xdaforums.com/showthread.php?t=1378063
[Kindle Fire General] Vashypooh:
That thread wouldn't work when the SDCard is totaled and completely unmountable, and what I listed is another method for unbricking. Its just a complete wipe and start over.

This thread is about unbricking the KF, and what I posted directly relates to unbricking it..
[Kindle Fire General] yareally:
If you say so...but I and the OP (we worked together on it FYI) did not start the thread for what you think.

We have already said we do not support people screwing with experimental firmware (that one willingly knows has a good chance of screwing up their device) until there are safer and noob friendly ways to do so. If you wish to start a separate thread about it, by all means do :)

We both do not own kindle fires (we just know enough about how they work as they come) so we cannot possibly answer questions about cm7 and no one else out there is constantly chiming in to help soo it makes sense to keep it away from methods that involve experimenting in ways that deviant from what we know. In that regard, how many people do you see helping people that do not actually own the device?

Now if you're volunteering to keep answering questions (because I know right now, there will be people asking questions no matter how detailed you think your guide is), then by all means, post whatever you want. However, 99% of people pump and dump in this thread and never reply again, leaving it to us two to answer. Pretty much this whole thread is just a conversation between myself, ubeezee and those that brick their device.

So before you start saying what this thread is and what it isn't, are you volunteering to keep helping people?
[Kindle Fire General] MayfairDROID:
Also, I had an issue where the PC couldn't find my device after running the temp root as others have. I had to reload the drivers by going to my computer, manage and then device manager. Once I told the device manger to use the drivers I had modified, it recognized them and moved forward.
[Kindle Fire General] yareally:
Just to help out others, can you give the steps you did to modify whatever your issue was? I don't recall if someone already gave them or not. Thanks!
[Kindle Fire General] Vashypooh:
If I posted, I am cool with helping. In fact I even offered to remote in and try o repair someones and in the process build a batch file that could just revert the fire to stock. So yep, I am offering to try and help :)
[Kindle Fire General] yareally:
Cool, glad someone else wants to help :)

Ubeezee and I sometimes feel like it's "many versus us" in this thread as far as answers versus questions (and it wears on us), so we'll gladly take any offers of someone else that wants to dedicate themselves.
[Kindle Fire General] Vashypooh:
Yea, I am not an expert by any means, but I have dug myself into enough holes that I can generally find my way out of it. :D
[Kindle Fire General] toasterjack:
Hello,

I have various of the similar problem discussed within page 7 and 34.

I completed step 3, and with the only little hitch as

rm sh boomsh

there were no rm detected or something like that.

Now I am have the situation that my kindle fire only shows the logo without the gliding light.

The device is reading as 'kindle', however, no drives are present.

I thought I was already in fastboot,

however issueing a command via

c:\kindlefireroot\files>fastboot -i 0x1949 -w only leads to

<waiting for device>

also,

adb shell and other adb commands

does not work because it cannot detect device

Other things to be noted, under devices

my fire is listed as

Android Phones

Android sdk

(I think)

I changed the service to the one from android sdk saved in 1 click root (x86)

and my brick error was when I copy-pasted market.apk to system/app folder, I messed up, and then force-continue, and boom, error.

Any help would be appreciated
[Kindle Fire General] Husam2011:
I think i messed it up even more, i had CMD with no permissions maybe, and i just tried everything including idme but reboot didnt work because it had no permission?

So i rebooted my the kindle myself and now its not even showing in adb.
[Kindle Fire General] Vashypooh:
Try:

fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot

It may be in fastboot mode.
[Kindle Fire General] Husam2011:
It says waiting for device. As i said, its not even reading it thro adb/ usb is unknown atm on this pc, altho it says kindle on another pc.

It also has a green led always on, which i think wasnt on before?
[Kindle Fire General] Vashypooh:
On the other computer are you able to fire up ADB at all?
[Kindle Fire General] Husam2011:
Just finished installing everything there, still no for adb. I will sleep now and will try tomorrow, can i return it somehow if it doesnt work?

Check my latest post on the arabic font on dev forum, or click on my username and click latest posts and see what i exactly did there.
[Kindle Fire General] Vashypooh:
Without ADB or fastboot working, you probably are going to need the TBH factory cable to put it into fastboot. Have you tried fully killing power to the device using the 20second method and trying to power it back up then?
[Kindle Fire General] Husam2011:
Yes, i tried that that alot.
[Kindle Fire General] Vashypooh:
:( You might just be out of luck, you could build yourself a fastboot cable, or order one unless someone else has any better ideas.
[Kindle Fire General] Husam2011:
Well, i wonder if i can just return it, as it has 3 big backlight bleeds? I also got it 2 days ago.

Edit: I just read that i had did something that the thread owner said not to do. I think he has done the same thing before and maybe he has a fix for it? I hope he answers tomorrow.

http://xdaforums.com/showthread.php?p=20278772#post20278772

I kinda of did the opposite.
[Kindle Fire General] Vashypooh:
I am going to palce this here, but I make NO clames about is effectiveness at the moment, please keep in mind I have no kindle fire atm, so its hard for me to test this by hand, so most of this was done by memory / reading this post.

The procedures and everything I have done here are not my own, all I did was attempt to put a more user friendly face on it.

Here is a quick rundown on how it is designed to work:

ZergRush; You will want to try and get the ADB shell root access for every other option in the menu, so start with #1 if you do not have it in root already.

Repair Permissions; This option will try to repair the system/app and the framework-res.apk and ensure that they are okay. (If other things need permission checking ubeezee & yareally let me know, we can add them in

Wipe Data; loads into fastboot and attempts to nuke data and cache.

Obtain KF Update.zip; This will go out to amazon and download the update.zip and extract it locally into \update_extract\ so all the files are available directly from amazon.

Replace framework-res.apk; This will replace it and correct permission errors on the apk using the stock download from amazon.

Factory reset; This will completely attempt to revert the KF to stock using the trick I used. This should be a last resort.

I would love feedback from anyone who gives it a whirl. I can continue to make it better for everyone and easier. Hope this helps at-least one person :)

Kindle_Fire_Debricker_v2.zip
[Kindle Fire General] yareally:
You could probably just recursively set the permissions on things in the subfolders to be sure

adb shell chmod 644 /system/framework/*

adb shell chmod 755 /system/framework

adb shell chown -R root.root /system/framework/

adb shell chmod 644 /system/app/*

adb shell chmod 755 /system/app

adb shell chown -R root.root /system/app/
[Kindle Fire General] Vashypooh:
Awesome, will add that.

---------- Post added at 02:16 AM ---------- Previous post was at 01:23 AM ----------

Updated my origional post with new link.

Kindle_Fire_Debricker_v2.zip
[Kindle Fire General] Husam2011:
Looks like what my made my device not even connect to adb anymore and show up as an unknown device is because i did ->idme bootmode 4002 -> reboot -> reboot no permission -> i reboot device myself by clicking power button for 20~ sec and turning it back on. Green led on the power and not even connecting :( i would appreciate it if somebody knows how to fix this.
[Kindle Fire General] mjjferreira:
I have the same issue. And i solve it.

Turn off your kindle.

Connect kindle to you pc using the usb cable. (it should turn on, if it doesnt, then turn it on)

When the kindle stops in the splash screen, do this in the KindleRootFiles folder:

//Step 4: clear user data and cache using fastboot

//note: 0x1949 is the device-id for the kindle so fastboot can recognize it

Code:

fastboot -i 0x1949 -w

//this part might take a while

erasing 'userdata'... OKAY [110.203s]

erasing 'cache'... OKAY [ 28.328s]

finished. total time: 138.531s

//Step 5: change back to normal boot mode in fastboot

//note: 4000 is for normal boot

Code:

fastboot -i 0x1949 oem idme bootmode 4000

... OKAY [ 0.219s]

finished. total time: 0.219s

//Step 6: use fastboot to restart kindle fire

Code:

fastboot -i 0x1949 reboot

rebooting...

finished. total time: 0.016s
[Kindle Fire General] Husam2011:
Wow man, looks like its kinda of working! Thanks!!!!!

I won't complete all steps i guess because my school starts in 7mins lmao. i will try it.

---------- Post added at 12:39 PM ---------- Previous post was at 12:31 PM ----------

Thank you too, looks like when i tried it yesterday it didnt work.
[Kindle Fire General] Vashypooh:
No problem, glad you got it working. If you have any more problems just keep posting, we will try to help.

Anyone given my file a whirl just yet?
[Kindle Fire General] SikYou:
Yea, I gave your file a whirl. It looks great, and the concept is spectacular, but I knew it would not work for me :( I bricked my device with a bad boot.img flash and I can't even get in to fastboot. So, of course when I ran your unbrick script it just sat waiting for mt device while my device bootlooped like there was no tomorrow (because there isn't a tomorrow). I'm sure I'll get my device fixed once my parts arrive for my fastboot dongle.

As for your script; you should start a dedicated thread and give some basic instructions on getting it running (remember the script is for newbs so they may not even know what to do with it, i.e. unzip...etc). Also, a linux version would be very nice, I had to dust off my windows machine and hope that it still worked ;)

Thanks for the work you are putting into the unbricker, very nice!
[Kindle Fire General] Vashypooh:
Hmm, for now I would like to keep it here I think unless they would like me to move it. I do not have a kindle fire, so its easier if I have help.

As for your fire, if you use a factory cable you might still be able to get into fastboot :)
[Kindle Fire General] shug176:
Wow this fixed mine thanks a lot :D Glad to get my kindle fixed after so long but its down to everyone on here helping so thanks a lot for the help esp op
[Kindle Fire General] Husam2011:
After it recovering to factory mode, it still stays in the kindle fire screen :(
[Kindle Fire General] BradOKeefe:
I've tried but no success. Hope you can help :)

Current Progress:

1. I've made a factory cable and can boot into Fastboot.

2. Having problems with ADB. I can Push files but cannot Shell. When I attempt to shell I receive the following:

- exec '/system/bin/sh' failed: No such file or directory (2) -

3. So I connected the factory cable, rebooted and then set the bootmode with fastboot to 4002. I then rebooted with normal USB cable into fastboot.

4. I then : Flashboot -i 0x1949 flash recovery updaterecovery.img

to try and install Clockwork.

5. Rebooted, and CWM comes up. At this point I can ADB Shell and receive this prompt:

~#

6. I then used ADB and pushed your Command file to the /cache/recovery folder and pushed the update.zip file to the /data/local/tmp folder.

At this point I am unsure of how to push the stock recovery back onto the device using ADB or am I able to use Idme from the ADB Shell. I receiving the following error:

~# idme bootmode 5001

idme bootmode 5001

/sbin/sh: idme: not found

If I simply reboot the device at this point, the android robot pops up for a second with a progress bar. Progress bar moves about 10 percent, and then displays robot and triangle with exclamation point.

Your original instructions listed:

5.adb push stock recovery

6.Write stock recovery

I'm not sure how to do this with ADB.

Thanks,

Brad
[Kindle Fire General] ubeezee:
Glad to hear you got yours working!!
[Kindle Fire General] ubeezee:
Check your permissions

adb shell

ls -l /system/

check the original post in the section about permissions. Post what you see here if you are unsure if they are correct or not
[Kindle Fire General] Husam2011:
d

Did /system, now if somebody only visits the thread i posted, he may know what i ****ed up..