Related
Three days ago I went through the process of rooting my kindle fire using KFU. Being a noob, this took me many many hours. I got everything to work, GO Launcher, Google Play, Amazon App store. I even used the Voodoo OTA Rootkeeper to temporily un-root so that I can watch amazon streaming videos. I was feeling pretty good about my accomplishment.
Late last night, for no apparent reason, the Kindle Fire restarted itself and got stuck on the yellow triangle (is this FireFireFire?). I got nervous, freaked out a little. I plugged into my computer and tried to restart the Kindle after selecting 'Recovery (5001)'. No luck. I then tried the same thing after selecting 'Normal (4000)'. I could hear the USB connect/disconnect many times and then I saw the "Kindle Fire" screen and let out a sigh of relief. It booted up just fine. This was about 2 hours ago.
But, now, my Kindle randomly goes back to the yellow triangle and hangs there. I need to go through the same process above to fix things. This has happened at least four times already. It did not seem to happen while the Kindle was "connected" to my computer. It happens once I 'disconnect'.... usually after about 10 - 20 minutes. It has happened while using both GO Launcher EX and the Amazon Launcher. Any idea?
You've got the same issue I do - the kindle keeps trying to apply the new update, and it isn't working, dumping it into recovery mode. I haven't figured out an answer to getting the update successfully applied yet (will work on that tonight), but until that happens, you should be able to remove the update from the sdcard /kindleupdates, and through something like root explorer rename /etc/security/otacerts.zip to something like /etc/security/otacerts.bak (or better yet, move it to the sdcard). That will stop it from redownloading the update and auto-rebooting.
Look Here
Have you looked at this http://forum.xda-developers.com/showthread.php?t=1417234 thread. The video explains the most common fix, and he goes through it step by step.
Also, so you grow a thick skin for posting on this forum, check out this link http://forum.xda-developers.com/showthread.php?t=1633343.
Hope this helps
Thanks for listening.
Sincerely,
William
[Kindle Fire: gedeROM v1.2 {3.0 Kernel, CM9, Android 4.0.4} - Stock Kernel]
[HTC Evo 4G Supersonic: MikG 3.11 ROM - Chop Suey Custom Kernel]
[Retired: HTC CDMA Hero: Gingerbread Hero Deck ROM - Stock Kernel]
end.
Ok. I just tested it, and had it also confirmed in another thread, but here is one way to get 6.3.1 on when the update fails to apply, putting you into the recovery, force to normal boot, kindle updates, back to recovery loop:
if you have a copy on your device, copy the update to the root of the sdcard volume or download it from amazon. Rename the file update.zip, then reboot into recovery.
Under install, install the update.zip. Once it is done, you'll have 6.3.1 applied. Now, you'll have to both reroot, and reinstall recovery, but since you just did it with KFU a few days ago, it should be pretty quick. Then go move/rename the otacerts.zip file to prevent the next unexpected update.
There might be another way that doesn't blow away recovery, but this worked for me.
Thanks so much for all of the help! It looks like everything is working again. I got 6.3.1 installed (not really sure how that happened but it did!). Also got re-rooted and reinstalled TWRP and did a backup. I renamed the otacerts.zip. There is also a cacerts.bks file in the /etc/security directory... what does that do?
Also... will I ever want/need the updates? I assume renaming the otacerts.zip stops the updates indefinitely. Will this ever be a problem?
Thanks again!
Moving the otacerts.zip prevents the kindle from automatically downloading updates. When a new update has been released, you can download it from amazon's site manually, or put back the cert file to enable the download. Since updates often break root, this method will help keep you rooted until it is known how to root the new versions. As for want/needing them, it'll depend on what changes, but as long as they are rootable, they should generally bring improvements for the device.
The. bks file is a keystore for the certificate authority certs. You shouldn't need to ever touch that file.
powers down
Ok, I've got the exact same issue but one glaring difference. That after using KFU to boot to normal, it within 10-20sec powers down. Starting the bootloop all over. Don't know what to do, please help.
Does it actually fully boot into the kindle os? I haven't heard of it trying to apply the update that fast after start up, but not saying that it won't do that.
If using twrp, you can mount the kindle over usb from twrp - mount, and then move the update file out of kindleupdates. That should stop the boot cycle if it is being caused by the update. Another thing to check would be to look at the twrp console and make sure it is complaining about the update failing and not something else.
When I try to mount it ask me to format the drive, is that safe? Won't I lose everything then? Also, it won't allow me to select just the sd, it only allows me to select system.
ms6146 said:
Ok, I've got the exact same issue but one glaring difference.
Click to expand...
Click to collapse
That sounds eerily familiar...Where have I seen that before?
That after using KFU to boot to normal, it within 10-20sec powers down. Starting the bootloop all over. Don't know what to do, please help.
Click to expand...
Click to collapse
Only kidding...Actually that problem isn't the same at all and is described in detail here: http://forum.xda-developers.com/showthread.php?p=25400963
ms6146 said:
When I try to mount it ask me to format the drive, is that safe? Won't I lose everything then? Also, it won't allow me to select just the sd, it only allows me to select system.
Click to expand...
Click to collapse
Formatting your sdcard will erase everything on it. Besides trying to mount your sdcard, what are you trying to accomplish?
Well I'm stuck in bootloop with the powering off problem. The kindle is not recognized on the computer. All I want is to get the kindle back working. I have tried the unbrick utility but I think that made it worse. Getting back to a regular firmware even if its the latest would be fine. However being the noob that I am, I need step by step instructions. Thanks in advance.
ms6146 said:
Well I'm stuck in bootloop with the powering off problem. The kindle is not recognized on the computer. All I want is to get the kindle back working. I have tried the unbrick utility but I think that made it worse. Getting back to a regular firmware even if its the latest would be fine. However being the noob that I am, I need step by step instructions. Thanks in advance.
Click to expand...
Click to collapse
Your problem can still be fixed, but considering the fact you can't get the computer to recognize your device, you only have a couple of options left:
You could acquire a factory cable which would directly power your device in order to replace the bootloader.
If you don't have the means to acquire a factory cable you need to mount your sdcard in order to transfer FFF1.4 for flashing in recovery. From what I understand in your earlier post, it would in your case, require formatting your sdcard
yellow triangle and restart, please help
Jarden said:
Three days ago I went through the process of rooting my kindle fire using KFU. Being a noob, this took me many many hours. I got everything to work, GO Launcher, Google Play, Amazon App store. I even used the Voodoo OTA Rootkeeper to temporily un-root so that I can watch amazon streaming videos. I was feeling pretty good about my accomplishment.
Late last night, for no apparent reason, the Kindle Fire restarted itself and got stuck on the yellow triangle (is this FireFireFire?). I got nervous, freaked out a little. I plugged into my computer and tried to restart the Kindle after selecting 'Recovery (5001)'. No luck. I then tried the same thing after selecting 'Normal (4000)'. I could hear the USB connect/disconnect many times and then I saw the "Kindle Fire" screen and let out a sigh of relief. It booted up just fine. This was about 2 hours ago.
But, now, my Kindle randomly goes back to the yellow triangle and hangs there. I need to go through the same process above to fix things. This has happened at least four times already. It did not seem to happen while the Kindle was "connected" to my computer. It happens once I 'disconnect'.... usually after about 10 - 20 minutes. It has happened while using both GO Launcher EX and the Amazon Launcher. Any idea?
Click to expand...
Click to collapse
Hello Jarde, I have the same problem but I am super noob, my kindle is restarting at the yellow triangle every 3 seconds, you said " then tried the same thing after selecting 'Normal (4000)'. I could hear the USB connect/disconnect many times and then I saw the "Kindle Fire" screen and let out a sigh of relief", what do you mean selecting 'Normal (4000)', how can I do this?, and finally how did you solve the problem, thanks a lot and sorry for my poor english.
notforever said:
Hello Jarde, I have the same problem but I am super noob, my kindle is restarting at the yellow triangle every 3 seconds, you said " then tried the same thing after selecting 'Normal (4000)'. I could hear the USB connect/disconnect many times and then I saw the "Kindle Fire" screen and let out a sigh of relief", what do you mean selecting 'Normal (4000)', how can I do this?, and finally how did you solve the problem, thanks a lot and sorry for my poor english.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=25400963
I had the same issue - shutdown after a few seconds after boot, then the KF boots back into yellow triangle error.
I was able to get out of this loop by booting into recovery and wiping the cache partition (and the Dalvik cache for good measure) to remove the downloaded update file. After wiping the caches, my KF rebooted normally without issue. I could then us Root Explorer to rename the /etc/security/otacerts.zip file to something else as suggested in an earlier post. I have not had a problem since.
OK...I'm a first time poster to the Kindle Fire forum and I'm having issues. I'm a little above average with my Android knowledge. I've flashed CM9 onto three Toucpads and have been fooling with my phones for a few years. HOWEVER, I'm completely stumped. Here's what's happening and what I've done.
1) I downloaded Kindle Fire Utility to root. It all went fine, as far as I could tell.
2) I downloaded the aokp_otter_build-M5>0xD34D build for CM9
3) I downloaded the gapps-ics-20120429-signed zip
4) Booted into the TWRP recovery
5) Made a backup of the stock Kindle
6) Flashed the CM9 zip and the Gapps zip. Everything seemed fine with the TWRP. Never used it before. Very familiar with CWM and seemed similar
7 Rebooted.
The Kindle Fire logo came up and then went to a blank screen. It boot-looped (is that a verb?) five or six times. While I went surfing to find answers it looped once more and came up to this screen with a pissed off looking unicorn and the Team Kang logo. It's stuck there and won't go past. The screen is still animated. The battery is not dead. I've read dozens of posts where the first suggestion is to charge the Kindle. That's not the problem. I've restarted the Kindle a hundred times and nothing.
Here's what I've tried:
1) Every combination of holding down the power button/pressing the power button combination. Nothing.
2) Downloaded the Kindle Unbrick Utility. The computer isn't recognizing the Kindle, so this isn't doing any good. I've tried all of the six different UI buttons. Nothing.
3) I went back to the Kindle Fire Utility and reinstalled the drivers and then opened the CMD window. As I expected, it's telling me "waiting for device" and doing nothing.
I have no idea where to go from here. There's got to be a way for me to get this thing to be recognized on my computer. Please help. Any advice would be greatly appreciated. Thanks! -Jeff
It's like deja vu...
http://forum.xda-developers.com/showthread.php?t=1658205
Even the description of the bootanimation is eerily the same.
I think my assessment of his problem would apply to you as well. If you want to skip most of the discussion, my post is at (or very near) the end.
Wow...that is creepy. I did a search on here for pink unicor/team kang, etc. Nothing came up. It's almost 2am and I can hardly see straight. I'll read through everything in the morning. Where would I get one of these magic cables I'm reading about?
jeffjoleen said:
Wow...that is creepy. I did a search on here for pink unicor/team kang, etc. Nothing came up. It's almost 2am and I can hardly see straight. I'll read through everything in the morning. Where would I get one of these magic cables I'm reading about?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1550999
Probably wouldn't hurt for you to look this over either...
http://forum.xda-developers.com/showthread.php?t=1552547
I dont see anything mentioned in your post about doing a full wipe before flashing AOKP just I thats where your method above went haywire with twrp. When going from one system to another always factory/ data restore wipe cache wipe dalvik and yes wipe system before flashing your rom and gapps. Pretty high likelyhood that why your stuck in a bootloop. You need to get back into recovery wipe the heck out of it and restore your backup. Also didnt hear mention of a bootloader. Do you get to a screen with a yellow triangle or one with a white kindle and a blue fire both these screen are bootloader splash screens for two different bootloaders. If you come to the yellow triangle hold the power button down immediatly till it turns orange this will put you into recovery. Alternatly if your greeted by a white kindle with a blue fire rapidly push the power button till some small words come up at the bottom of the screen 1. Normal 2. Recovery 3. Reset bootmode use the power button to toggle through the selections till it looks like --recovery-- this will get you into twrp where you can do as I said above wipe wipe wipe wipe restore backup reboot. Or maybe you havent got a bootloader installed.
You said you rooted with the Kindle Fire Utility and all went well. If that's the case you should have access to recovery. If so, you don't need a "magic" factory cable to fix your problem.
When you first boot your Kindle, what does the boot logo look like, exactly?
Thepooch said:
I dont see anything mentioned in your post about doing a full wipe before flashing AOKP just I thats where your method above went haywire with twrp. When going from one system to another always factory/ data restore wipe cache wipe dalvik and yes wipe system before flashing your rom and gapps. Pretty high likelyhood that why your stuck in a bootloop. You need to get back into recovery wipe the heck out of it and restore your backup. Also didnt hear mention of a bootloader. Do you get to a screen with a yellow triangle or one with a white kindle and a blue fire both these screen are bootloader splash screens for two different bootloaders. If you come to the yellow triangle hold the power button down immediatly till it turns orange this will put you into recovery. Alternatly if your greeted by a white kindle with a blue fire rapidly push the power button till some small words come up at the bottom of the screen 1. Normal 2. Recovery 3. Reset bootmode use the power button to toggle through the selections till it looks like --recovery-- this will get you into twrp where you can do as I said above wipe wipe wipe wipe restore backup reboot. Or maybe you havent got a bootloader installed.
Click to expand...
Click to collapse
Honestly...don't remember if I did a full wipe of dalvik. I assumed I would have, but really don't remember. No...I don't get the yellow triangle and my kindle fire logo color is white "kindle" with a yellow "fire". I used the kindle fire utility and I think that installs the twrp by default. I don't have CWM installed. Wish I did. I'm comfortable with it. I just can't get to any kind of a recovery screen.
soupmagnet said:
You said you rooted with the Kindle Fire Utility and all went well. If that's the case you should have access to recovery. If so, you don't need a "magic" factory cable to fix your problem.
When you first boot your Kindle, what does the boot logo look like, exactly?
Click to expand...
Click to collapse
Yes...the KFU went fine, I think. I was able to access twrp and created my backup before I flashed the ICS. The Kindle logo has the white "kindle" and yellow "fire". Pauses for a few seconds or two...screen goes black...then that damned pink unicorn shows up and stays there. The unicorn screen is animated. I can power it down from there and start over without any problem. Any ideas?
without a bootloader you wont have access to recovery regardless of twrp/cwm
One other thing that I'm not sure matters, but when I do power it off and back on, I head the little "bong" on my computer telling me that a new device has been plugged in. I go to the device manager and under the "Other" category it shows "Amazon" with the yellow triangle the black exclamation point symbol.
Reinstall your drivers
Thepooch said:
without a bootloader you wont have access to recovery regardless of twrp/cwm
Click to expand...
Click to collapse
I guess that's where I am a little confused with definitions. I understand about the twrp and cmw recovery set ups. What exactly is a bootloader? Thanks for not laughing...
Thepooch said:
Reinstall your drivers
Click to expand...
Click to collapse
Through the Kindle Fire Utility? If so, I've done that several times. Would trying a different computer and installing them there make any difference?
the bootloader allows you to access recovery im not laughing cause its a bummer to see things go this way you need to get your drivers going to push a bootloader to your device
First, read this...
http://forum.xda-developers.com/showpost.php?p=23747567
You need to make sure your drivers are in order so you can change the bootmode to 5001 and reboot. A custom bootloader will let you do this easily but considering you don't have one you need to use adb instead.
Code:
adb shell
idme bootmode 5001
adb reboot
Thepooch said:
the bootloader allows you to access recovery im not laughing cause its a bummer to see things go this way you need to get your drivers going to push a bootloader to your device
Click to expand...
Click to collapse
So, without a functioning bootloader I won't even be able to get to the twrp to access my back up I made. Nice. Just bought this damn thing yesterday. I'm kinda missing the one-click jailbreak software from my old iphone a few years back!
if the adb method that soup posted above doesnt work which required your adb drivers working your next route is likely here http://forum.xda-developers.com/showthread.php?t=1430038
---------- Post added at 09:58 AM ---------- Previous post was at 09:54 AM ----------
while your pondering your next move might wanna look at this http://forum.xda-developers.com/showthread.php?t=1552547
Thepooch said:
if the adb method that soup posted above doesnt work which required your adb drivers working your next route is likely here http://forum.xda-developers.com/showthread.php?t=1430038
---------- Post added at 09:58 AM ---------- Previous post was at 09:54 AM ----------
while your pondering your next move might wanna look at this http://forum.xda-developers.com/showthread.php?t=1552547
Click to expand...
Click to collapse
I just read through the basic instructions. I'll grab a usb thumbdrive and give it a shot. Thx
good luck hope you get through this is the not so fun side of rooting
Thepooch said:
if the adb method that soup posted above doesnt work which required your adb drivers working your next route is likely here http://forum.xda-developers.com/showthread.php?t=1430038
---------- Post added at 09:58 AM ---------- Previous post was at 09:54 AM ----------
while your pondering your next move might wanna look at this http://forum.xda-developers.com/showthread.php?t=1552547
Click to expand...
Click to collapse
Thanks. It answered some of my questions. I guess it helped me relax a little, too. I know this is a problem that can be fixed. Just need to dig in an try each suggestion until I find one that works.
I believe im having the "5 second bootloop" problem, no idea why since my KF was never rooted, flashed, or modified in any way. I plugged the Micro B in the KF (KF was off) and then plugged the Type-A end into my PC, the KF turned on in like 10 seconds (maybe less) and it isn't doing the bootloop anymore which i guess is a good thing but its been like 10 minutes and it still just says kindle fire (with a green light on the bottom). What should I do from here for my specific situation? Any help would be great! Thanks in advance!
edit: just wanted to add that before when i would plug it in, it would keep rebooting and usually not even get to the slide to unlock screen, but sometimes it would and then instantly reboot again.
First off...what bootloader do you have installed?
How could I find out? I never modified it if that helps? So it should be stock everything.
also i downloaded KFU and installed the drivers, but it does not recognize my device, altho when i first plugged it in after installing the drivers it said kindle in Device Manager, since it didnt go anywhere i unplugged the kindle and turned it off, when i tried again it installed ADB, but still doesnt recognize it (it also prompted me to restart, which i did right before i posted this reply, and still not recognized, also still at the kindle fire screen with green light on)
Untraumatized said:
How could I find out? I never modified it if that helps? So it should be stock everything.
also i downloaded KFU and installed the drivers, but it does not recognize my device, altho when i first plugged it in after installing the drivers it said kindle in Device Manager, since it didnt go anywhere i unplugged the kindle and turned it off, when i tried again it installed ADB, but still doesnt recognize it (it also prompted me to restart, which i did right before i posted this reply, and still not recognized, also still at the kindle fire screen with green light on)
Click to expand...
Click to collapse
ok so i read that sometimes it just wont read that it worked... so i check device manager, it said android phone, went to KFU, still said unknown after 0+enter, then i tried 3, it said it worked and to press any key to reboot, i pressed a key but the kindle didnt reboot, is it supposed to? also i tried 4 then like i read to do and it says the download path is incorrect so whats wrong?
Untraumatized said:
ok so i read that sometimes it just wont read that it worked... so i check device manager, it said android phone, went to KFU, still said unknown after 0+enter, then i tried 3, it said it worked and to press any key to reboot, i pressed a key but the kindle didnt reboot, is it supposed to? also i tried 4 then like i read to do and it says the download path is incorrect so whats wrong?
Click to expand...
Click to collapse
sorry for triple posting i will fix it but i dont want to confuse you on the timing of these events lol... so i figured out that CWM may be broken right now??? anyways since twrp worked i insatlled FFF with worked and now its at a menu that is kindle fire but BLUE fire text and says press power button for boot menu, but when i do that it doesnt do anything, do i need to unplug it?
Untraumatized said:
sorry for triple posting i will fix it but i dont want to confuse you on the timing of these events lol... so i figured out that CWM may be broken right now??? anyways since twrp worked i insatlled FFF with worked and now its at a menu that is kindle fire but BLUE fire text and says press power button for boot menu, but when i do that it doesnt do anything, do i need to unplug it?
Click to expand...
Click to collapse
you still there buddy? lol, i unplugged it and ya that worked, so now im at TWRP, just because it seems like a good idea i am backing up the things that were already checkmarked when i clicked backup
but now im afraid to continue without help, what step am i at exactly now? lol
EDIT: stuck at the end of the backup, been stuck there a while, will probably try to turn it off in a few minutes or so... anybody have some advice?
How about a little more information about what it is you intend to accomplish with your device?
soupmagnet said:
How about a little more information about what it is you intend to accomplish with your device?
Click to expand...
Click to collapse
i just want it to work! my power went out one day while i was sleeping and it was charging, for some reason it was dead (had been at 100% so shouldnt have drained, but the power going out messed with it) and when i tried to charge it, it bootloops
right now i have TWRP installed and FFF installed, what should i do now? i have tried booting it up and it just gets to the slide to unlock screen and then resets back to the blue kindle fire screen
i also just tried to install permanent root with superuser and it seemed to be working then said rebooting and "please wait...." and it never did anything (except the kindle booted back to the blue kind fire screen)
Untraumatized said:
i just want it to work! my power went out one day while i was sleeping and it was charging, for some reason it was dead (had been at 100% so shouldnt have drained, but the power going out messed with it) and when i tried to charge it, it bootloops
right now i have TWRP installed and FFF installed, what should i do now? i have tried booting it up and it just gets to the slide to unlock screen and then resets back to the blue kindle fire screen
i also just tried to install permanent root with superuser and it seemed to be working then said rebooting and "please wait...." and it never did anything (except the kindle booted back to the blue kind fire screen)
Click to expand...
Click to collapse
ANY help would be appreciated... im sitting here screwing with it waiting for a reply....
Untraumatized said:
ANY help would be appreciated... im sitting here screwing with it waiting for a reply....
Click to expand...
Click to collapse
well i managed to fix it by just factory resetting it with no help AT ALL
Very likely the factory reset had nothing to do with it. Just simply having it plugged in via USB may have given it enough time to charge. Questions of this nature are best handled in q & a not in development.
Untraumatized said:
well i managed to fix it by just factory resetting it with no help AT ALL
Click to expand...
Click to collapse
I'm sorry for not sitting at my computer, waiting with baited breath for you to respond, so I can devote all of my attention to your problem. I hope you can forgive me.
I wasnt trying to be offensive lol I was just proud to figure it out with NO HELP AT ALL! But anyways I am pretty sure it wasnt the charge because it was at 56% before and after i did the factory reset, and after the factory reset i backed it up and it finished that time (last time i had to unplug the KF and hard reset it)... Also I tried resetting it a couple times before the factory reset and it always rebooted once it got to the slide to unlock screen. Anyways it works, I am probably going to give it to my mom because of the simplicity (she just needs email, and internet... lol) and I might try to get my hands on a Nexus 7
AND HOW DO I DELETE ALL THOSE REPOSTS? THE DELETE BUTTON ISNT WORKING FOR ME ^__^'
Untraumatized said:
I wasnt trying to be offensive lol I was just proud to figure it out with NO HELP AT ALL! But anyways I am pretty sure it wasnt the charge because it was at 56% before and after i did the factory reset, and after the factory reset i backed it up and it finished that time (last time i had to unplug the KF and hard reset it)... Also I tried resetting it a couple times before the factory reset and it always rebooted once it got to the slide to unlock screen. Anyways it works, I am probably going to give it to my mom because of the simplicity (she just needs email, and internet... lol) and I might try to get my hands on a Nexus 7
AND HOW DO I DELETE ALL THOSE REPOSTS? THE DELETE BUTTON ISNT WORKING FOR ME ^__^'
Click to expand...
Click to collapse
Correct me if im wrong but you can't delete posts....but this thread should not be in Android Dev section, it should be in Q and A... Not to be mean or anything I am going to report this thread so it can be moved to the right section (to help the mods out)
OP, First This Thread Is In The Wrong Place. And It Appears To Me Users Where Trying To Help, On Limited Information. But You Figure It Out On Your Own Great.
Thank You And Thread Closed.
I rooted using the Bin4ry method, and after turning back on the Kindle is doing some weird stuff. The screen flashes black every couple of seconds, there is no ad on the lockscreen, instead nothing, and no icons are showing up. The device is almost unusably slow. I'm about to factory reset it. Will this fix it? Have I bricked it? Please help.
By the way, I have searched for this and only found one thread with this exact issue and no resolution.
If you are going to ask me to "search for it" please link a relevant thread.
Thanks.
Edit: Factory reset fixed it, and it rooted fine afterward.
Hi,
I put CM 11 on my fire phone. After I dialed a phone number and pushed send, the screen instantly went black. That was enoying so I tried to install the recent CM 11 from 02/16/2016. (Now I know that the display protection might have caused the issue) After the installation I booted the phone. After I had to choose the language in cyanogenmod in the phone was written that the installer was stopped. So I was in a loop of beeing asked for the language.
So I put OS (via adb sideolad) on the fire phone again and installed CM11 and the recent open gapps. Everytime the installer stopped and I was in that loop again.
I tried it with different Open gapps and CM11.
Now suddenly the Fire Phone does not do anything anymore. Just a black screen. I tried several button combinations with several time combinations. Even not the amazon sign appears.
I have two fire phones and am more or less scilled in flashing and installing. But now I do not know how to tread the issue.
I think about opening the Fire Phone and disconnect the battery for some seconds. That move might do something....
Any recommendations? Any ideas? Anybody had similar issues?
Thank you! Have a nice one!
Ingo
Some ideas...
Hi ingo,
welcome to the forums :cyclops:
first of all the following are just some ideas i've got of helping you in your case.
Maybe you already done some of them but anyway
Idea 1. Hold down Power button for about 10 secs or more (to try to reboot to see if the amazon logo appears)
Idea 2. Hold down Power button and Volume down together for about 10 secs or more (maybe we can get out of the boot loop).
Idea 3. Hold down Power button and Volume UP together for about 10 secs or more (maybe we can get out of the boot loop).
Idea 4. Don't charge the phone for about 3 Days and see if it shows something when you then connect the charger (then try to repeat Idea1 to Idea3).
After one of this succeed:
Your issue with CM not going over language selection is already known.
Try to remove SIM and use WLAN to go over the setup....
Or install the one from january (no issue) and then dirty update to the current one
If you killed your SafeStrap recovery you will have to go back to stock, root, safestrap and start over...
That's for now from me.
Report if something changed
regards
Will open the Fire Phone
Hi. Thank you for your answear! I appreciate that!
I checked your ideas already. The first ideas did not work out. I will open the Phone to disconnect the battery for a while. I will see what that may bring.
I will tell about the outcome of that.
Have a nice one.
Best Regards, Ingo
Dont forget: if you still (ok i doubt ) have warranty on the phone that the battery pack is secured inside with a "magic tape" that will break when you remove it...
Good luck
Will find sollution
Thank you for your reply. Warranty. Ahaha.:laugh: Would be funny to try it though.
I ordered the right tools for opebing the Fire Phone (There are two small torx screws).
I saw in the list of devices that there are 6 extra disks shown when I connect the phone to the pc. The PC just can see the content of one of them. I cannot open the files, the PC is not able to open the filetypes (for example adsp.b10)
I will keep on trying!
See you!
I got my new tools. Disconnecting the battery did not make it better. Same situation like before. So right now I do net know the next step.
Of course I tried to charge the phone, I tried different button combinations ......
Its a pitty. I have got two fire phones and it is the one with the 64gb.
I will keep on.. If anybody has a hint please tell me.
Thank you!
Regards Ingo
Anybody got an idea?
ingokabel said:
Anybody got an idea?
Click to expand...
Click to collapse
Hi,
after a while I start to try to fix my fire phone again. I still do not have any clew how to solve the issue.
Any of you?