Related
So I looked in the bricked section and the bootup sections and couldn't find my answer. I am sure it is somewhere but my search didn't turn it up. I have been using the sprint SII for about 8 months now, no real problems. I rooted it and flashed over using Odin an older version of Calkin's EG4T rom, it worked fine, I updated it about 3 months ago to the newest version (honestly I forget which but it was right before ICS started coming out). Today I come home from work and find my phone black screen off when I hadn't turned it off. I try and turn it on and nothing. So I pop out the battery and restart it, it loads up but everytime I try something it comes up with provider error and crashes the program, even when calling. So I boot into recovery and delete the cache and try again, same problem. Try to reinstall using recovery from the old update.zip file, it goes through but now it only boots into recovery, no booting into a new ROM at all. I check to see if I can still enter the download option and I can but I haven't gotten the newest tar file to push from odin so I quit. I try one last time to use android commander to copy over a new ROM, it appears to copy and I try the install and it claims it completed and now my phone only boots to the Samsung Galaxy SII screen. It won't go any further, I can't enter recovery OR download screen. I have tried leaving the battery out for 5 minutes and still stuck at the same screen. I can reboot from the screen but nothing else. Odin is unable to push the newest rom onto the system. Anyone who has any ideas I welcome it as I really do need this phone tomorrow.
thanks and I do hope I didn't miss an obvious thread covering this exact problem, but I do not believe i did.
you say you can't get into recovery or download, but also say that odin won't push newest rom onto system. Are you sure you're holding right buttons to get into download mode? (power+vol dwn, then volume up once the screen comes up to bootloader)
Well update, still fun. I pulled the battery for 10 minutes and now am able to get to the download screen (I was clicking for it correctly before I swear), and I pushed the newest Calkin's rom and it went through. But I am still stuck on load at the samsung screen. And what is even more fun is it won't actually turn off. I hold the power button for power off and it just restarts the sucker. I am going to try and push the stock rom next. Any other ideas?
thanks
If you can't get into download you're bricked. What update.zip did you flash? Usually that only works if you flash an authentic sprint/Samsung update or created a signed update.zip on your own. Also, did you flash it from stock recovery or clockwork mod?
Sent from my SPH-D710 using XDA
dante32278 said:
If you can't get into download you're bricked. What update.zip did you flash? Usually that only works if you flash an authentic sprint/Samsung update or created a signed update.zip on your own. Also, did you flash it from stock recovery or clockwork mod?
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
I did the update through cwm just as I had done previously so I figured it would work, but it seems I figured wrong
I am now able to get back into CWM but still unable to actually load past the samsung screen (yes I have left it going for a while), any ideas? Also trying to determine which specific kernal is the newest stock kernol for the sprint s II, any links? I am seeing lots of modified but nothing stock (in tar format).
thanks
edit- When I access the phone through android commander (it finds it) the folders it shows as being on the phone are all incorrect. Some of the titles are correct but the actual files within are missing or it is claiming the folders were made in 2000. I know I have not wiped the SD card as I can see it via cwm but can't seem to edit it on commander.
Also I am unable to actually view the phone when in cwm through android, only finding it in commander when it is stuck in the loading samsung screen
Final edit:
Finally got a stock one click to fully complete through Odin! back to stock, now to reroot and get my old stock on there
Okay so basically I decided to root my Kindle Fire. I have rooted my android phone and my iPod before so I wasn't too worried about it, but it's gone horribly wrong and I need major help.
So here's what happened:
I got my root from rootkindlefire.com and followed the necessary steps (i'm running on 6.3.1)
It got halfway through and froze and I stupidly unplugged my kindle
Then it was stuck on this screen with a yellow triangle with a flame in it and at the bottom is said press power button for recovery, but when I pressed it nothing happened
So I went messing around online, in my drivers, etc. I ended up deleting my kindle drivers (like the original ones) and now my kindle is freaking out.
I watched this other tutorial on rootkindlefire.com and tried to follow the steps on how to unbrick it but when I managed to get into the recovery (i can't remember what it's called? blue screen with options like install, mount, reboot, etc.) and put the zip drive he said to, in there... i couldn't see it.
I then downloaded KFU and managed to get my kindle to reboot, but it is now stuck on the "Kindle Fire" screen. I can turn it off, get into recovery, etc. I cannot get it to move past the start up screen however.
I do not believe I am in fastboot, but one of the sites I was on could have misled me. Anyway... HELP! please... I'm sad:/
You should be able to find all you need to get it going here http://forum.xda-developers.com/showthread.php?t=1923010
Thepooch said:
You should be able to find all you need to get it going here http://forum.xda-developers.com/showthread.php?t=1923010
Click to expand...
Click to collapse
I followed all the steps and everything worked just like it said....but when my kindle rebooted, it is still stuck at the kindle fire screen but now there's animation...which it did not have before.
Any suggestions?
If your getting animation and it doesn`t go any further this usually indicates a broken system which TWRP are you using ? If you are using 2.3.1.1 there`s a problem with how it formats best you revert to an older version 2.2.2.1 or older then it should work for you. Full wipe except your external storage/sdcard, refalsh rom and gapps. The proper methods for wiping are also provided in the link I gave you.
Very good point though make sure your using the newest version of KFU 9.6 the older version uses burrito root which no longer works on the Kindle Fire. Really though alll you need is a bootloader and recovery rooting is obsolete.
lexibrowni said:
Okay so basically I decided to root my Kindle Fire....
I got my root from rootkindlefire.com and followed the necessary steps (i'm running on 6.3.1)
I watched this other tutorial on rootkindlefire.com and tried to follow the steps on how to unbrick it but when I managed to get into the recovery (i can't remember what it's called? blue screen with options like install, mount, reboot, etc.) and put the zip drive he said to, in there... i couldn't see it.
I do not believe I am in fastboot, but one of the sites I was on could have misled me. Anyway... HELP! please... I'm sad:/
Click to expand...
Click to collapse
First off, definitely listen to Thepooch and Josepho1997. Next, do you just want a rooted KF running the basic 6.3.1 firmware, or will you be switching to ICS or JB?
Next, is the blue screen you mentioned the TWRP screen? (TeamWin screen with 8 different choices)? If you are, then go to (I think) the bottom right and select mount, then mount system or USB or whatever it says. After that you can add files for a custom ROM or whatever you want through your computer. I forgot to mention that you need to of your KF into your computer.
Sent from my Amazon Kindle Fire using Tapatalk 2
lexibrowni said:
Okay so basically I decided to root my Kindle Fire. I have rooted my android phone and my iPod before so I wasn't too worried about it, but it's gone horribly wrong and I need major help.
So here's what happened:
I got my root from rootkindlefire.com and followed the necessary steps (i'm running on 6.3.1)
It got halfway through and froze and I stupidly unplugged my kindle
Then it was stuck on this screen with a yellow triangle with a flame in it and at the bottom is said press power button for recovery, but when I pressed it nothing happened
So I went messing around online, in my drivers, etc. I ended up deleting my kindle drivers (like the original ones) and now my kindle is freaking out.
I watched this other tutorial on rootkindlefire.com and tried to follow the steps on how to unbrick it but when I managed to get into the recovery (i can't remember what it's called? blue screen with options like install, mount, reboot, etc.) and put the zip drive he said to, in there... i couldn't see it.
I then downloaded KFU and managed to get my kindle to reboot, but it is now stuck on the "Kindle Fire" screen. I can turn it off, get into recovery, etc. I cannot get it to move past the start up screen however.
I do not believe I am in fastboot, but one of the sites I was on could have misled me. Anyway... HELP! please... I'm sad:/
Click to expand...
Click to collapse
Hi I am exactly where you were at (Deleted drivers=Freaking Out at yellow triangle). What do i do from here!? Please Help Me!!???
http://forum.xda-developers.com/showthread.php?t=1923010
Help
I have done everything that has been listed here. My kindle is stuck on the kindle fire screen, I can not boot into recovery and I do believe the TWRP that was previously on it, has been removed as well as the OS...My son was messing with it and all I could get out of him was he was on a blue screen and swiped to reboot and he thought it said no OS installed. So, I have the done the Alternate method for rooting, however, when run the kfu, it says its online but boot status is unknown. I can not get it to say any different. What am I doing wrong?
I think my 1st gen KF is stuck trying to boot to recovery. I was trying to restore back to stock from CM10.1. Downloaded the Amazon update 6.2.1 bin file, renamed it to update.zip, booted into TWRP recovery, tried to flash and it failed (several times). After some research, I found that the fix for this was to downgrade TWRP to v2.2.2.1 (I was on 2.6.0.0 or something like that). I tried several methods for doing that and it wouldn't take, even though it looked like flashing the TWRP v2.2.2.1 finished successfully. So finally I found a method (thanks to XDA's wonderful developers) to install CWM. Finally was able to get it to boot into CWM recovery, tried flashing the update.zip again, and all went through successfully. However, when I rebooted it was stuck at the Kindle Fire logo screen. Tried rebooting several times...nothing. AFter more research, found that the bootmode was incorrectly set so I tried to change the bootmode to recovery (which failed miserably)...now I'm stuck on the Kindle Fire logo screen. Seems like it is trying to boot to stock recovery but can't get there. Now none of my computers will recognize it at all. Is there anything I can do to unbrick this? I've tried just about every method I can get my hands on but without the computer recognizing it, not sure what else I can do.
Any help would be GREATLY appreciated. This is my 8-year old son's Kindle!
Thanks,
caseym
caseym said:
I think my 1st gen KF is stuck trying to boot to recovery. I was trying to restore back to stock from CM10.1. Downloaded the Amazon update 6.2.1 bin file, renamed it to update.zip, booted into TWRP recovery, tried to flash and it failed (several times). After some research, I found that the fix for this was to downgrade TWRP to v2.2.2.1 (I was on 2.6.0.0 or something like that). I tried several methods for doing that and it wouldn't take, even though it looked like flashing the TWRP v2.2.2.1 finished successfully. So finally I found a method (thanks to XDA's wonderful developers) to install CWM. Finally was able to get it to boot into CWM recovery, tried flashing the update.zip again, and all went through successfully. However, when I rebooted it was stuck at the Kindle Fire logo screen. Tried rebooting several times...nothing. AFter more research, found that the bootmode was incorrectly set so I tried to change the bootmode to recovery (which failed miserably)...now I'm stuck on the Kindle Fire logo screen. Seems like it is trying to boot to stock recovery but can't get there. Now none of my computers will recognize it at all. Is there anything I can do to unbrick this? I've tried just about every method I can get my hands on but without the computer recognizing it, not sure what else I can do.
Any help would be GREATLY appreciated. This is my 8-year old son's Kindle!
Thanks,
caseym
Click to expand...
Click to collapse
I'm having exactly the same issue on my Kindle Fire. I just recently got it from a friend; it seemed to be bricked, but the friend stated that he had never tried modifying the stock OS. I was able to use KFU to install the most up-to-date version of TWRP, but not FFF; I wanted to get it to stock before doing any additional hacking. That version of TWRP booted without any issues.
As OP mentioned, the most up-to-date version of TWRP has issues with installing the current version of the Amazon software. So, I tried downloading a copy of TWRP 2.2.2.1 (attached) and used KFU to install it, by extracting recovery.img, renaming it to twrp.img, and dropping it in KFU's /recovery/ folder.
Since then, I've seen the same symptoms as OP. The Fire boots to the Kindle Fire bootscreen, with no animation. It's not detected at all by any computer I attach it to. Windows doesn't chime or show it in Device Manager and KFU and adb don't see it. I also tried setting up FireKit, but none of the tools in that package are able to see it.
I'm going to test to see if this persists after depleting the battery for a while. I do not have a fastboot cable to test with, but I'm open to opening the case if you guys think that'll help get it back up and running.
Update; I was able to use the shorting trick to put it into OMAP boot mode and install FFF and TWRP, as well as reset the boot mode using Firekit. Firekit also installs TWRP 2.0, which is able to restore the stock Kindle Fire firmware.
haikuginger said:
Update; I was able to use the shorting trick to put it into OMAP boot mode and install FFF and TWRP, as well as reset the boot mode using Firekit. Firekit also installs TWRP 2.0, which is able to restore the stock Kindle Fire firmware.
Click to expand...
Click to collapse
OK...can you explain what you mean by the "shorting trick"? The battery on mine has been dead for about a day and a half. I had the case open the other day but didn't really do anything. What do I need to do?
Thanks,
caseym
caseym said:
OK...can you explain what you mean by the "shorting trick"? The battery on mine has been dead for about a day and a half. I had the case open the other day but didn't really do anything. What do I need to do?
Thanks,
caseym
Click to expand...
Click to collapse
First, get the Kindle charged. Then, boot to Ubuntu and set up FireKit (link above). Then, with the back cover off, hook the Kindle up to the computer. It'll power up, but hold down the power button to shut it off immediately.
Once you've done that, run the "usb_install_fff_twrp" script from Terminal. It'll say that its waiting for an OMAP device. Here's where the shorting comes in. Short the pad circled in the picture in this post to the metal frame around the CPU:
http://forum.xda-developers.com/showpost.php?p=19762674&postcount=51
Then, keeping it shorted, press the power button.
Firekit should see the device over USB now, and write the appropriate settings. Once booted to TWRP, you should be able to install the stock firmware from /sdcard/.
It might take a couple tries, but keep trying. I used a continuity tester with an LED in it to make sure I had shorted that pad correctly.
haikuginger said:
First, get the Kindle charged. Then, boot to Ubuntu and set up FireKit (link above). Then, with the back cover off, hook the Kindle up to the computer. It'll power up, but hold down the power button to shut it off immediately.
Once you've done that, run the "usb_install_fff_twrp" script from Terminal. It'll say that its waiting for an OMAP device. Here's where the shorting comes in. Short the pad circled in the picture in this post to the metal frame around the CPU:
http://forum.xda-developers.com/showpost.php?p=19762674&postcount=51
Then, keeping it shorted, press the power button.
Firekit should see the device over USB now, and write the appropriate settings. Once booted to TWRP, you should be able to install the stock firmware from /sdcard/.
It might take a couple tries, but keep trying. I used a continuity tester with an LED in it to make sure I had shorted that pad correctly.
Click to expand...
Click to collapse
Well it worked the first time. I was able to get it to boot and the FireKit utility installed TWRP and I was able to flash the stock rom. After doing that, I disconnected the USB cable and the KIndle immediately shut off and I can't get it to turn back on. What did I do wrong?! Is it fried or something?
--
caseym
caseym said:
Well it worked the first time. I was able to get it to boot and the FireKit utility installed TWRP and I was able to flash the stock rom. After doing that, I disconnected the USB cable and the KIndle immediately shut off and I can't get it to turn back on. What did I do wrong?! Is it fried or something?
--
caseym
Click to expand...
Click to collapse
I'm afraid I've got nothing for you at this point. Hopefully someone more knowledgeable than I can sound off.
I'd like to preface this by saying I read the FAQ and did some searching here, but couldn't spot anything that sounded like my problem. I've half got an idea of what to do, but I'm quite confused and feel like some stuff needs clarifying. I apologize if this is more common than I realize, cause if it is I'm sure y'all are sick of answering questions like this.
---
I got a used Kindle Fire from a friend that came with CM10 on it. I wanted to use it for reading, but the Kindle android app was recently broken by Amazon so I reluctantly reverted it back to stock (I really liked having a tablet, but I've got a phone for that stuff and I needed an e-reader). The very next day they fixed the app so I decided I should load CM10 back onto the Kindle. Now, I flashed CM10 onto my phone last year and it was a painless process so I figured it'd be the same here. Somehow in the process I completely messed things up.
From stock FireOS, I used Kindle Fire Utility to flash TWRP on my Kindle, then from there installed CM10 again. What I didn't know, was that CM no longer comes with gApps preloaded. I had no clue, as when I flashed it onto my phone it had all the gApps on there. So I google it and find out I need to flash gApps on there. Here's the problem: I can't boot this thing into recovery. Somehow TWRP was lost in the process. I enabled developer options in the settings, then enabled the option to choose reboot into recovery in the power menu but when I choose it, it just reboots into CM10 again. I'm not sure how I'm supposed to revert back to stock or flash gApps in if I can't get to TWRP again.
It's clear this has gotten way over my head.
Summary:
* Have a kindle w/ fresh install of CM10 on it.
* No gApps and can't boot into recovery.
* I think TWRP might be gone somehow.
* I want to either return to stock or get TWRP back safely and gApps flashed on here.
You need to boot back into Kindle Fire Utility and install the boot loader FireFireFire to boot into recovery.
themetalman said:
You need to boot back into Kindle Fire Utility and install the boot loader FireFireFire to boot into recovery.
Click to expand...
Click to collapse
I can't seem to get KFU to recognize my plugged in Kindle. IIRC when I first used KFU, when it recognized the Kindle it displayed "ADB Status: Online" and "Boot Status: 4000". Now it's ADB Offline / Boot Unknown.
I've been told elsewhere that I need to locate a stock recovery image and load it up using terminal emulator since it appears my recovery was broken. Where might I find one for my Kindle? I perused the various stickied threads / guides around here but did not see one.
e: Would it be against the rules re: buying/selling if I offered whoever helps me get this fixed $10? Haha.
TheSMP said:
I've been told elsewhere that I need to locate a stock recovery image and load it up using terminal emulator since it appears my recovery was broken. Where might I find one for my Kindle? I perused the various stickied threads / guides around here but did not see one.
e: Would it be against the rules re: buying/selling if I offered whoever helps me get this fixed $10? Haha.
Click to expand...
Click to collapse
I have used the download and the bottom of this page to repair a bricked kindle fire.
Link: http://n2aos.com/
Then go back into kindle utility and reinstall TWRP and firefirefire.
You might also want to look at this site. He has great tutorial videos. Link: https://sites.google.com/site/tomsgt123/all-videos/kindle-fire
My story, used Fire off ebay, sweet deal,w/ 3.5.0. os. Used d630 Dell, Vista,clean install. Both same week.
Downloaded........... 4.6.1---3.5.0---4.6.3--,4.6.6,adbfastboot 15 sec 1.3/1.4.3,safestrap,kingroot,esfile,
1st attempt...root and safestrap said recovery installed but "go to recovery" button went to black screen, reboot only went to Amazon,lost recovery and os.
2nd attempt.... waited 3 days went back to the phone, vol up/power/plugged into laptop at the same time, boom I had os(?), tried again 3x to recovery through safestap,still no recovery but system was back. I upgraded ota to 3.5.1, restored recovery, kept root.
Now everything is good except the "cannot read update.bin". I noticed in properties ,4.6.1 is actually is a .zip but renamed .bin. If i convert it using some kind of freeware, will the result be a brick or "can read update.bin"?
Why does every place i read, 4.6.6 is the latest update but mine doesn't see beyond 3.5.1?
Do I still have to download to 3.5.0 from 3.5.1 to do 4.6.1, to install cm?
Why doesnt safestap install recovery on 3.5.0?
I haven't tried safestap on 3.5.1, not until I can adb or push/fastboot????