Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,738,440 Members 51,074 Now Online
XDA Developers Android and Mobile Development Forum

[HOW TO] Unbricking/Restoring your Kindle Fire

Tip us?
 
ubeezee
Old
(Last edited by ubeezee; 30th December 2011 at 08:18 AM.)
#1  
ubeezee's Avatar
Member - OP
Thanks Meter 55
Posts: 95
Join Date: Aug 2011

 
DONATE TO ME
Default [HOW TO] Unbricking/Restoring your Kindle Fire

UPDATE: It has come to my attention that zergRush root has been patched and no longer works on the most resent updates. At the moment I haven't checked to see what to use to replace it. I would advise anyone who is needing to unbrick your device to go over to this thread started by Vashypooh: http://forum.xda-developers.com/show....php?t=1399889. It is the Kindle Fire Utility v0.9.1 and has options to unbrick your kindle fire among many other great features. Please try his utility out as I have not been keeping up with this thread much over the holidays.


My kindle fire was stuck in a bootloop/bricked (info on what was going on prior to fixing: forum.xda-developers.com/showthread.php?t=1355371) after some complications when trying to install google apps. I may of deleted system files, really not sure what happened at this point. Anyway, this is what finally fixed it. This will get your device to the just out of the box state. Just follow along with the commands. I documented as much as I could, but if you have any questions feel free to ask. Hope this helps anyone whos Kindle Fire wont boot up!


For this to work you will need fastboot and zergRush root
get fastboot here: http://multiupload.com/TPWBYSCGM7
details on how fastboot works: http://wiki.cyanogenmod.com/wiki/Fastboot
zergRush root: http://rootkindlefire.com/kindle-fir...t-kindle-fire/
->zergRush should be in the folder called files when extracted
Also make sure your device is charged, this will save you some time at the end!

I most likely not respond to private messages. This is a general thread so anyone can post here. It is beneficial to others since they may be experiencing the same problems as you. Being in my inbox wont help anyone.

***DISCLAIMER***: This process may not work for everyone! It really does depend on what you did to brick your kindle fire!! Also please consider thinking twice about messing with your device again after you fix it. Unless, of course, you think you can fix it on your own or are an advanced user.

PS: Read other peoples posts! Many have posted a lot of useful information, please use this to your advantage before asking questions!

PPS:What you did to brick your device is probably not unique. in order to prevent this thread from annoying those trying to help and from getting too long, we may ignore posts that ask questions or ask for solutions that have already been asked. If you don't get a reply within 24 hours, your problem probably falls under this.

PPPS:If the directions don't work and you don't see a solution in this thread already then you probably bricked your device beyond this way of recovery and need to seek other ways. If you are still having troubles please post a DESCRIPTIVE (pictures, links, anything and everything you did to get where you are at now) question/post with the problems you are facing and we can try and help you. Thank you.

---------------------------------------///------------------------------------

Hard reset may work for some people - hold power button for ~20 seconds and turn back on. If it doesn't then proceed:
---------------------------------------///------------------------------------

How to begin the how-to using cmd:

1. Download the files you need and stick them in your C:\ directory

2. stick fastboot in C:\KindleFireRoot\files directory

3. open cmd (command prompt)

4. navigate to the files directory on your C:\ drive
should look similar to this:
Code:
Select Code
C:\users\userName>cd C:\KindleFireRoot\files
5. now you are in the kindleFireRoot\files directoryshould look something like this:
Code:
Select Code
C:\KindleFireRoot\files>
Now you can start following the directions in the how-to and type exactly what you see to the right of the $ and # symbols. You should see them but do not type another one next to what you already see.
---------------------------------------///------------------------------------

IF YOU THINK MODIFYING PERMISSIONS ON /system/app IS WHAT CAUSED YOUR DEVICE TO BOOTLOOP THEN FOLLOW THESE STEPS:
check your permissions first
Code:
Select Code
adb shell
 ls -l /system/
they should look like:
Code:
Select Code
drwxr-xr-x root root 1970-01-01 00:00 lost+found
 drw-r-xr-x root root 2011-11-29 12:31 app
 drwxr-xr-x root shell 2011-11-16 03:03 bin
 -rw-r--r-- root root 2144 2008-08-01 12:00 build.prop
 drwxr-xr-x root root 2011-11-16 03:03 etc
 drwxr-xr-x root root 2011-11-16 03:03 fonts
 drwxr-xr-x root root 2011-11-16 03:03 framework
 drwxr-xr-x root root 2011-11-16 03:03 lib
 drwxr-xr-x root root 2011-11-16 03:03 media
 drwxr-xr-x root root 2011-11-16 03:03 tts
 drwxr-xr-x root root 2011-11-16 03:03 usr
 drwxr-xr-x root shell 2011-11-16 03:03 vendor
 drwxr-xr-x root shell 2011-11-29 12:31 xbin
if yours do not look like this then continute:

follow the steps to temp root FIRST(steps 1 and 2 below)!

AFTER you temp root:
Code:
Select Code
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 755 /system/app
then reboot

Note: this can work with any directory that has permissions messed up

---------------------------------------///------------------------------------

IF YOU CHANGED WALLPAPERS/THEME AND BRICKED YOUR DEVICE BY MESSING WITH FRAMEWORK-RES.APK TRY THIS:
if you have adb active, try

adb shell ls -l /system/framework/framework-res.apk

if you dont see it show permissions as rw-r--r--
temp root (steps 1 and 2) first then run:

adb shell mount -o remount rw /system
adb shell chown root /system/framework/framework-res.apk
adb shell chmod 644 /system/framework/framework-res.apk
adb shell mount -o remount ro /system
adb reboot

if that does not work, then you need to go back to the old file, get it from the amazon update (download the update from their site and unzip it with 7zip or winrar, ignore the fact it's called bin and just rename it if you don't know how to do it otherwise to .zip).

then run

adb push framework-res.apk /data/local/tmp
adb shell mount -o remount rw /system
adb shell mv /data/local/tmp/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
---------------------------------------///------------------------------------

IF NONE OF THE ABOVE APPLIES TO YOU THEN DO THESE STEPS:

//Step 1: push zergRush on the device then run chmod 755 on zergRush
Code:
Select Code
$ adb push zergRush /data/local/tmp

$ adb shell chmod 755 /data/local/tmp/zergRush

//Step 2: temp root
Code:
Select Code
$ adb shell
adb server is out of date. killing...
* daemon started successfully *
$ cd data/local
cd data/local
$ cd tmp
cd tmp
$ ls
ls
boomsh
zergRush
sh
$ rm sh boomsh Remove everything but zergRush here, it will not matter if yours is missing/out of order compared to mine
rm sh boomsh
$ ./zergRush 
./zergRush

[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.

[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.

[+] Found a GingerBread ! 0x00015118[*] Scooting ...[*] Sending 149 zerglings ...
[+] Zerglings found a way to enter ! 0x10
[+] Overseer found a path ! 0x000151e0[*] Sending 149 zerglings ...
[+] Zerglings caused crash (good news): 0x40119cd4 0x0054[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd195cb 0xafd3937f[*] Popping 24 more zerglings[*] Sending 173 zerglings ...

[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!
//Step 3: reboot into fastboot
//note: 4002 for fastboot


Code:
Select Code
$ adb shell
# cd /system/bin
cd /system/bin 
# idme bootmode 4002 
idme bootmode 4002
<idme> write 4002 to offset 0x1000
# reboot
reboot
//Step 4: clear user data and cache using fastboot
//note: 0x1949 is the device-id for the kindle so fastboot can recognize it


Code:
Select 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:
Select 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:
Select Code
$ fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.016s
At this point the kindle hit splash screen for a few minutes then told me that my device needed to be charged (was at 13%) to continue. **So make sure your device is charged**, otherwise you will have to wait about 20-30 minutes depending on your charge %. The amber light finally came on while connected to PC which it wasn't doing before so this was a good sign.

After it was charged enough the next step stated: "Your kindle has detected a problem and must clear app storage.The recovery precess 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 you press the power button it shows a progress bar, reboots, hits splash screen for a few minutes then takes you to set up your Kindle Fire account YAYYYY!
The Following 36 Users Say Thank You to ubeezee For This Useful Post: [ Click to Expand ]
 
yareally
Old
#2  
yareally's Avatar
Senior Member
Thanks Meter 220
Posts: 1,422
Join Date: Feb 2011

 
DONATE TO ME
Just a suggestion but perhaps one of the mods could move this to the developer's forum (or sticky it and make the links have http:// in front)? The OP could not post it there since they do not have 10 posts yet, but they're a friend of mine and we worked together to unbrick their device.
The Following 4 Users Say Thank You to yareally For This Useful Post: [ Click to Expand ]
 
bjanice44
Old
#3  
Senior Member
Thanks Meter 40
Posts: 129
Join Date: May 2009
Default unbricking from recovery

I am going to try the method for unbricking, but not sure it will work on mine. My fire is stuck on the boot screen where it has a long message saying there is a problem with the fire and that it needs to restore the apps and bring it back to default.

It then says to press the power button continue with the restore. Then it completes, says success, then reboots right back into the same message screen all over again.

When I adb devices I get "firexxxxxSN recovery"
I am hoping fastboot can help me or perhaps I need to re-image recovery or boot.

What happened was this. I tried to follow a method to change my wallpapers using metamorph. I followed all the steps then started getting theme errors and such while in the kindle. I rebooted and was stuck in the bootloop as described here.

Being the novice I am, I thought I could then copy over a fresh copy of "system" from the fire system dump that was posted. I did this and this is where I am now.

Any help would be appreciated. It might be a good idea for us to figure this one out so that we have the procedure.
 
transfuntioner
Old
#4  
Member
Thanks Meter 8
Posts: 37
Join Date: May 2011
Location: champaign, il
you dont need root to run idme.

But since you can get root, try clearing the /data/dalvik-cache by hand & reboot.. much quicker than a full userdata wipe.
 
bjanice44
Old
#5  
Senior Member
Thanks Meter 40
Posts: 129
Join Date: May 2009
Hi, assuming your responding to me, whats idme? Right now I cant get root just a bootloop. And when I adb devices I get my device serial # recovery where is normally says device serial # device

---------- Post added at 03:57 PM ---------- Previous post was at 03:46 PM ----------

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.
 
bjanice44
Old
#6  
Senior Member
Thanks Meter 40
Posts: 129
Join Date: May 2009
Hey, can you please tell me how you get into fastboot? I went to the wiki and did everything it said there but am stuck because I am getting stuck on step 5

Boot device into bootloader - How do I do this? Is this simply powering on the fire?
Make sure the device is in FASTBOOT and not HBOOT - same question
 
justki
Old
#7  
Junior Member
Thanks Meter 0
Posts: 1
Join Date: Nov 2011
I'm getting "zergRush: permission denied" any help?
 
md202000
Old
#8  
Junior Member
Thanks Meter 1
Posts: 10
Join Date: Mar 2011
Wow, I'm so glad I found this! You just may be my life/job saver. I'm going to try this right now and reply with status.
The Following User Says Thank You to md202000 For This Useful Post: [ Click to Expand ]
 
ubeezee
Old
#9  
ubeezee's Avatar
Member - OP
Thanks Meter 55
Posts: 95
Join Date: Aug 2011

 
DONATE TO ME
Quote:
Originally Posted by transfuntioner View Post
you dont need root to run idme.

But since you can get root, try clearing the /data/dalvik-cache by hand & reboot.. much quicker than a full userdata wipe.
I tried this previous to what I explained in my fix above and it didn't work. I was still stuck in bootloop and getting the same errors in the logs.
The Following User Says Thank You to ubeezee For This Useful Post: [ Click to Expand ]
 
md202000
Old
(Last edited by md202000; 21st November 2011 at 09:57 PM.) Reason: typos
#10  
Junior Member
Thanks Meter 1
Posts: 10
Join Date: Mar 2011
Quote:
Originally Posted by transfuntioner View Post
you dont need root to run idme.

But since you can get root, try clearing the /data/dalvik-cache by hand & reboot.. much quicker than a full userdata wipe.
@transfuntioner - This sounds logical and I did try this. In my specific case it didn't work either but may work for others.

Tags
bootloop, bricked, kindle fire wont start, stuck on splash screen, wont boot
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes