yashsingh1/xdaforums huggingface dataset:
[Kindle Fire General] boazjuggalo:
Yay Root! Yay Launcher! Boo Brick!

Ok I started off by rooting using the KindleFireRoot method and it worked beautifully.

Then I followed: http://xdaforums.com/showthread.php?t=1351283 to install the full market and did everything listed EXACTLY as listed and it seemed fine. I saw no market, but upon reading comments I read that the market would not show up in the Amazon launcher that i'd have to install a custom.

I then followed: http://xdaforums.com/showthread.php?t=1349462 to installed GoLauncherEX as my launcher. I read comments and saw the 4th comment said to get the beta version, so I did. I didn't get the Home Switcher since the comments said it wasn't needed anyways. I followed the steps perfectly and installed Go Launcher Ex.

As soon as install was finished I hit my home button and it popped up the box asking me which home i wanted to use. I (stupidly) checked the box saying "Make default" and chose Go Launcher EX and hit ok. It popped up a "We have experienced an error." or soemthing to that extent and my screen froze. I had to hold the power and do a hard restart. Upon restart all I get is the "kindle fire" logo over and over.

I followed the guide in the first post and used the "IF NONE OF THE ABOVE APPLIES TO YOU THEN DO THESE STEPS:" portion and everything goes good until I get to the "$ fastboot -i 0x1949 -w" line. When i enter it it pops up "< waiting for device >" and just sits here. The guide said this portion might take a while, so I went and took a shower and got a bite to eat (about 20 minutes) and it's still just sitting here. About to hard reset and start the process over and hope for the best.

Please get back to me if you have the time. Thanks.

PS: I did search and didn't see anything like this in scanning.

Edit: Maybe worth mentioning, when I type "ls", per the guide, I get...

"ls

zergRush

boomsh

sh"

while in your example you show

"ls

boomsh

zergRush

sh"

could those being out of order affect this? Also, since my initial post I've done this again, sitting on < waiting for device > again.
[Kindle Fire General] ubeezee:
Thanks for the complete post.

First, those being out of order wont matter, you just want to remove anything but zergRush.

Can you post a pic what the permissions of your /system is?

adb shell
ls -l /system

Also restart the how-to again up until your error and post that as well.

There isn't really a exact fix to the <waiting for device> issue i dont think. I mean you can restart the device/computer/adb, unplug replug the device etc. Thats what I would try at least.
[Kindle Fire General] ubeezee:
Try again with out the //run zergRush part.. it should only be ./zergRush

See if that makes any difference.

If that works, you need to fix permissions in /system/font. Follow the directions for fixing permissions on /system/app but instead you will do /system/font

Also, just because you have the su binary doesnt mean you actually have root. If zergRush didnt complete you do not have root.
[Kindle Fire General] boazjuggalo:
Uploaded the pic to the permissions window. What do you mean by "remove anything but zergRush"? how do i "remove" them? And I have no error, the only error i got was in the launcher how to and I can't get back to that while bricked. I'm just stuck at the "waiting on device"
[Kindle Fire General] zonbal33:
I think I bricked my KF, can anyone help?

I rooted it fine, I belive.

I installed the GoogleServicesFramework.apk to /system/ and to /system/app/, both by accident. I know that it only should be in /system/app/. After I rooted I used Root Explorer to delete the GoogleServices.apk from /system/. I had problems, restarted my KF and I'm now stuck at the splash screen in constant bootloop.

What can I do? Please help, my KF is just sitting here in bootloop.
[Kindle Fire General] ubeezee:
when you type "rm" that means remove.. what you have is fine, i was letting you know that when they are out of order it does not matter.

Anyway, your permissions look okay.

Can you go through the guide again up until where it says "waiting for device" and post this since some steps got removed somehow.. its fixed now so just try again.. should be okay now
[Kindle Fire General] yareally:
You can start by trying to read the OP and doing something yourself.
[Kindle Fire General] zonbal33:
Like I said, I tried following the Unbricking guide here at XDA but not sure what I'm doing.

I tried typing this:

It says restarting as root? My KF never restarted or anything. It's still in bootloop. I don't know what I'm doing or what I just did? Can anyone help me with this?
[Kindle Fire General] yareally:
why are you typing the comments out with the command?

$ ./zergRush //run zergRush
./zergRush //run zergRush

you don't type the //run zergRush part on the lines...

also that's how temp root works....it restarts adb and kicks you out of the shell (does not your device)...keep going in the tutorial...we didnt make that tutorial to screw with you and make you think that half way you should stop and ask questions when nothing as gone wrong *yet*

you have to understand these constant posts by people that screw up their device here start to look like a blur and there's only 2 of us giving answers. It's also 3am here. So cut me a break...
[Kindle Fire General] zonbal33:
I'm confused. I havent used ADB in years and most of this is gibbersh. No need to get all angry. It's 3 AM here, my son needs this KF tomorrow. If this wasnt urgent I wouldnt be posting. I just want to unroot. I do appreciate your help, I really do.

This is what has happened so far:

I'm stuck as "waiting for device". I don't know how long I'm suppose to wait or if I did this right? After it said "killing adb" above, I just entered in this:

"fastboot -i 0x1949 -w"

I'm not stuck at "< waiting for device >" with a blinkin cursor. Nothing is happening, I don't see this at all:
[Kindle Fire General] yareally:
Not angry, just stressed over multiple things (things other than xda mostly like unruly code that wont compile in my work). I'm sure he'll survive without it for a day but anyways...

I looked at the OP (haven't done so in a while) and it's missing steps now, which is why you're having problems.

You need to go on and do this:

adb shell

cd /system/bin

idme bootmode 4002

reboot

and then do the command you were doing before (in your last post) shortly after it reboots (and do the rest of the commands you saw in the OP).

Hopefully that works, because I'm spent and cannot stay awake any longer. The OP is afk as far as I know for now (but may come back and reply later) so best of luck :)
[Kindle Fire General] zonbal33:
cd c:\KindleFireRoot\files

c:\KindleFireRoot\files>adb shell

$ cd /system/bin

cd /system/bin

$ idme bootmode 4002

idme bootmode 4002

<idme> write 4002 to offset 0x1000

$ reboot

reboot

reboot: Operation not permitted

$

It wont reboot for some reason, I get "operation not permitted"? My KF is in a bootloop still I dont know if that matters. This is a nightmare, LOL, if I can fix this, never rooting this again. Also, what happens once my KF battery dies? Does it still charge even in bootloop?
[Kindle Fire General] ubeezee:
If anyone tried this within the last day you need to redo it because steps got deleted somehow! It is fixed now so if you were having issues like <waiting for device>, please try again.
[Kindle Fire General] ubeezee:
Not sure but did you temp root first.. there should be # instead of $? Just reboot yourself and move on to the next step, if it doesn't work then restart from step 1.
[Kindle Fire General] helentsang1214:
after i pressed the power key to restore my device

it returns to the splashing screen for nearly half an hour

is this normal??:eek:
[Kindle Fire General] zonbal33:
Now my KF isn't recognized by my PC. I tried restarting my PC, turned my KF off, switched USB ports, etc.
[Kindle Fire General] helentsang1214:
i had this problem before

it's because the device is still in fastboot mode and adb can't be used

i solved it by flashing the boot.img and recovery.img with the following steps:

1. fastboot -i 0x1949 flash boot boot.img

2. fastboot -i 0x1949 flash recovery recovery.img

3. fastboot -i 0x1949 -w

4. fastboot -i 0x1949 boot boot.img

after the device is rebooted, u will find ur KF in My Computer again and adb works again

now u have to change bootmode to 0x4000 again by:

1. adb shell

2. idme bootmode 0x4000

hope it helps

now it seems i am at the last stage of unbricking the device with splashing words 'kindle fire" on the screen

but i stuck at this stage for nearly an hour

i don't know whether it's normal /_\

---------- Post added at 10:51 PM ---------- Previous post was at 10:08 PM ----------

also, i got a 'cross-device link' error after this step:

adb shell mv /data/local/tmp/framework-res.apk /system/framework/framework-res.apk

does anyone have solutions to this?

finally i fixed my fire by using the following command after tmp root

next time i should go through ALL the posts first!! :)

thx for u guys' help in this thread!

adb shell mount -o remount rw /system

adb push framework-res.apk /system/framework/framework-res.apk

adb shell chown root /system/framework/framework-res.apk

adb shell chmod 644 /system/framework/framework-res.apk

adb reboot
[Kindle Fire General] zonbal33:
where do i find the boot and recovery img? btw, thx for all your help, glad some people actually care here.

oh im getting this error?

c:\KindleFireRoot\files>fastboot -i 0x1949 flash boot boot.img

error: cannot load 'boot.img'
[Kindle Fire General] boazjuggalo:
Sorry for the delay, sleep and work. :-)

Just reran the guide with the 'new' steps back and have my cmd window attached. Still gettingn to < waiting for device > with a blinking cursor. The difference is now with the 'reboot' command, when the KF restarts windows throws up a 'could not install driver' popup. I tried reinstalling using the driver that came with KindleFireRoot but it didn't recognize it and said the driver must support 64 bit (I'm running Win7 Ultimate 64).
[Kindle Fire General] Misune:
Here you go!

Boot.img: multiupload(dot) com /4MX67457I5

Recovery.img: multiupload(dot) com /UFAHJ6UTZH"

PS: If the links get removed download the update from amazon and make the update.bin to update.zip and you will see them.

PS (2): I better not get an infraction for helping some one. ;)
[Kindle Fire General] boazjuggalo:
I'm having the same problem, windows don't detect the device after the 'reboot' command. I tried your method you listed before with the 2 downloads in my /files/ directory. When I enter your first command (fastboot -1 0x1949 flash boot boot.img) i just get the old familiar < waiting for device > with a flashing cursor. Any idea why it won't continue?
[Kindle Fire General] ubeezee:
I dont think doing all of that is really neccessary..

If your device is in fastboot you can just try

fastboot -i 0x1949 oem idme bootmode 4000

which will return your device back to normal boot

then do

fastboot -i 0x1949 reboot

after this adb shell should work and you can try again from step 1

If not then you may have to follow those steps.
[Kindle Fire General] ubeezee:
Did you ever download the google usb driver package from the andriod sdk and modify the adb_usb.ini file? I assume if you rooted your device before you did. If not that would be my first guess. I know I had this done, not sure if it makes a difference or not.
[Kindle Fire General] andyspam:
I bricked my kindle and couldn't get this to work. It boots to a black screen and I can adb shell. The way it happened is I was trying to go back to stock from cm7 by flaskinj the update-kindle with fastboot and now i'm here.
[Kindle Fire General] shug176:
Still stuck at the very start i bricked my kindle fire after setting up the go launcher and think i changed permissions on the market app which i installed via apk file.

Think i rooted my kindle originally with zergRush root and in cmd i can navigate to C:\KindleFireRoot\files> no problem however i tried to go through the steps of zergRush root again but get stuck at the driver update its not compatible with my windows 64 bit so i went no further however im guessing this makes no difference as i have the device rooted already?Can anyone help iv read through the thread and i dont think im too far away if only i can connect with my device i think i will be able to fix it.

[/URL] Uploaded with ImageShack.us[/IMG]
[Kindle Fire General] Misune:
Hold down the lock/shutoff button for about 15-20 seconds until the screen turns off and goes black. Then press the lock button so it turns on. Wait about 30 seconds so it can connect. Then try the fastboot commands I gave you.
[Kindle Fire General] yareally:
When you get that message from windows about the driver, you're in fastboot. Ignore the message and just run the fastboot commands anyways.
[Kindle Fire General] rdwyer228:
Alright so, I have been trying to do this for a few days now. My KF is charging at the moment so I can't do much but wait. I seem to have the general problem of every time I try to enter something that is required to be in adb shell (i.e. i see the money sign >> $ adb push zergRush /data/local/tmp) i get this message adb: permission denied. Can anyone tell me what I am doing wrong? Do I need to download the file from amazon.com and if so, what do I do with it and where do I put it?

Thank you in advance for all the help.
[Kindle Fire General] ubeezee:
Not sure if you are typing adb shell before doing adb push zergRush /data/local/tmp but you dont want to adb shell. If you were try again without adb shell.
[Kindle Fire General] rdwyer228:
Okay I think that was my problem. I'll pull it off the charger and try that again.

EDIT: Okay so I got through those two lines and then I type adb shell and I do not get the notification that adb server is out of date and it does not kill the server. I think I am getting close! Lol, once I am through this, somebody hit me with a not-stupid-as-**** stick.
[Kindle Fire General] ubeezee:
Its okay if you don't get the notification, just continue with the next steps.
[Kindle Fire General] rdwyer228:
Okay, did just that a second ago and now it says battery too low (9%).

Will it charge while plugged into the computer?
[Kindle Fire General] ubeezee:
So you completed all the steps? Yes it will charge while plugged in. But if you finished all the steps okay, you can disconnect from the pc and plug into the wall charger since it will be faster. Also if you read past step 6 I explained what happened to mine at the point you are at.
[Kindle Fire General] rdwyer228:
Oh okay! Cool, I just wasn't sure if I needed my computer anymore. Thank you so much! It was quite the struggle, but I'm glad I got it to work again. Now to call Amazon and tell them I don't need the replacement unit they sent me. Lol. Will donate once I have then money too!
[Kindle Fire General] ubeezee:
No problem, glad to help. I'd wait until you get it back up and running for sure before calling amazon just incase lol. It may bootloop again after the restore screen, in that case we'd just have to check the permissions. But hopefully it will be okay without. Let me know if/when it's back up.
[Kindle Fire General] rdwyer228:
Will do!
[Kindle Fire General] rdwyer228:
One last question! Does it start the restoration process once it gets to a certain percentage of battery or can I do it manually at any percentage?
[Kindle Fire General] ubeezee:
I don't remember the % but you dont have to do anything. Just wait for it to go to the restore screen after its charged enough.
[Kindle Fire General] rdwyer228:
Okay it just did it and I'm back up and running! And for the record (incase you want to add this into the op, the percentage is 30%) thanks again for the help man!
[Kindle Fire General] ubeezee:
Wooo! Awesome, glad it worked.
[Kindle Fire General] zonbal33:
I followed what your posted and my KF rebooted. I'm now back in Normal Boot I assume. ADB SHELL does work. Where do I go from here? What directions do I follow now to try and unbrick my phone? The last time I tried to follow the tutorial on the main page it got me in worse trouble. Could you possible tell me what I need to do word for word please?
[Kindle Fire General] ubeezee:
No, the tutorial did not get you in trouble. You tried running fastboot commands in adb without temp root - thats what got you in trouble. If you follow the guide now step by step starting at #1, it should be fine. If something comes up along the way just post it and we can go from there.
[Kindle Fire General] zonbal33:
YOUR THE MAN! I think it worked.

The Power button on my KF turned orange and then a popup screen came, but it went away to fast to tell what it was, then my KF shut off.

It's now charging. A screen is currently on saying "Kindle Fire" "Battery (3%) is too low, please let charge".

Once it's done charging, I just power it up and I'm back to a unrooted KF? Will it automatically restart or something once it hits a 100% or how do I turn it on at like 30%?
[Kindle Fire General] ubeezee:
It will do it automatically, just wait for it to charge enough. It will go to the recovery screen which it will ask you to press the power button and it will do its thing, restart and you should be good to go. Someone else here said it would be around 30% charged so just leave it be for awhile. If you want to charge it on the wall charger it will be quicker then letting it charge on the pc. Let me know when/if its up and running.
[Kindle Fire General] zonbal33:
Awesome! Thank you for you help! Now I can call Amazon back and tell them to cancel the replacement.

---------- Post added at 07:21 AM ---------- Previous post was at 07:15 AM ----------

Say I wanted to root again, no mistakes this time. Do I have to start from Step 1 all over or can I just go ahead and just use SuperOneClickv2.2-ShortFuse? I didn't know if I had to install drivers again and so forth.
[Kindle Fire General] ubeezee:
Please don't. Its still so new that everything is still experimental, reason why a lot of people are having problems. I would wait until more things like recovery etc are stable and then do it. BUT if you reallllllyyyyyyyyyyyy want to, which I don't recommend.. nothing in this guide would help you. You would want to follow a rooting guide for the KF somewhere on the forum.
[Kindle Fire General] zonbal33:
Gotcha. I'm not going to but why does my KF still say I'm rooted? I just installed Root Explorer and it works. SuperOneClick says I'm still rooted. How is that possible when I just wiped my KF? It also seems Go Launcher puts my KF into bootloop.
[Kindle Fire General] yareally:
because it doesnt wipe the system partition
[Kindle Fire General] ksymphony:
I messed up my Build.prop file

I am using CM7 and i changed my build.prop file, forgetting about the issue that CM7 had when it was first installed which is the screnn being off by 90% and the screen not working right. So I have tried to enter adb shell but it says

Error: device not found

But windows sees it. I even did cd \

cd Android

cd platform-tools

adb kill-server

adb devices

and it still does not see it. What can I do to fix this issue. I have not seen anyone else with this issue
[Kindle Fire General] yareally:
You never actually said if you bricked your device.

If you didn't, you're asking for help in the wrong thread, as we are not a cm7 kindle fire support thread.

If this is not the case, there has been (at least issues of people screwing with build.prop).

You probably need that cable that launches the device into fastboot (and revert it back to stock) and not mess around with your device anymore after fixing it until someone can make it properly "noob proof".

The other possibility is because you didnt enable debugging...I would try this first. If that's the case, you just have to enable and then you can use adb to fix whatever you screwed up. I reccomend finding the build.prop file you need and pushing it to the device with the PROPER permissions and owner (else you'll be crying when you really really screw things up). If you own another android device, the permissions for it are the same, so just match those. If you don't know how to set them, google it, as there are plenty of topics out there about it.

This may sound like an afterthought, but when you get this fixed finally by our help...screwing with build.prop is NOT a good idea (nor is installing experimental software [unofficial alpha-like build of cm7 on a device without a proper recovery] on a device you're not comfortable with fixing at a very low level interface [fastboot and adb]).

We really don't support experimenting with your device beyond the stock firmware in this thread for now (so that would include cm7). However the above suggestions might help as they are not exactly specific to the firmware you chose to flash.
[Kindle Fire General] shug176:
so close

Right guys this is getting closer each night :D i THINK i have done step 4 correctly i pasted this

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

then step 5 i pasted this

fastboot -i 0x1949 oem idme bootmode 4000

... OKAY [ 0.219s]

finished. total time: 0.219s

BUT It just hangs on waiting for device iv waited ages manually rebooted the kindle yet nothing

[/URL] Uploaded with ImageShack.us[/IMG]
[Kindle Fire General] ubeezee:
from your picture it looks as though you are actually typing "erasing 'userdata'... OKAY [110.203s]" these things are not commands... you only type the command and you will see these things in return so you know they completed correctly... so the only thing you type is "fastboot -i 0x1949 -w" and "fastboot -i 0x1949 oem idme bootmode 4000" etc. Im really unsure what you are doing and where you are at. Maybe post a pic of the entire cmd?
[Kindle Fire General] shug176:
Hi i think im stuck around step 4 i should have inserted fastboot -i 0x1949 -w but i added on all the info beside it duh ! everything was running smooth unto device rebooted now it always says waiting on device and now my kindle just sits at boot screen saying kindle fire.ps thanks for your patience i will make donation regardless if i get a fix or not as getting plenty of help.edit i think im stuck in fastboot then so no need to go through all the steps again? iv tried this below in cmd but just get device waiting

C:\KindleFireRoot\files>fastboot -i 0x1949 -w
[Kindle Fire General] yareally:
You're not in fastboot anymore, that's why.

Just start the whole guide over, it's the easiest way to explain it to you and try to avoid doing what you did this time :)
[Kindle Fire General] ubeezee:
Yep, this. If you have any questions then please feel free to ask.
[Kindle Fire General] soundslikemitch:
I tried to add a custom keyboard using : http://xdaforums.com/showthread.php?p=20247330#post20247330

and got a reboot loop. Do I need a pc to attempt these methods? I only have a mac.
[Kindle Fire General] dingo8baby:
i tried on linux also and I'm getting the same message, as if the -i switch is not recognized by fastboot

---------- Post added 23rd November 2011 at 12:10 AM ---------- Previous post was 22nd November 2011 at 11:58 PM ----------

ah! that sounds like it might be it. I'll try again as soon as i download the new fastboot.

thanks!

---------- Post added at 12:26 AM ---------- Previous post was at 12:10 AM ----------

yes! that was it! thank you so much for your help, and for the excellent guide!
[Kindle Fire General] ubeezee:
Yay! You're very welcome! Glad I could help!
[Kindle Fire General] xiaoruisong:
thank you so much!!!

after trying for three hours, i successfully restored my kindle fire!

THANK YOU!!!
[Kindle Fire General] kuokkun:
In my case, after Reset My Kindle Fire to Restore Factory Default Settings,

it loop between "Formatting" and "Media Partition Erased" screen

I try to use adb to connect my fire, but the adb shell seem not work

C:\KindleFireRoot\files>adb devices

adb server is out of date. killing...

* daemon started successfully *

List of devices attached

283XXXXXXXXXXXX recovery

C:\KindleFireRoot\files>adb shell

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

C:\KindleFireRoot\files>

____________________________

Anyone can help me?