I rooted my 1st Gen Kindle Fire, installed twrp, and fff, everything worked fine. I wanted to update my android sys so I could more easily use google play. I installed 4.2.2 but it would never boot up... just got to the colorful undulating lines continuously... so I restored back to my back up sys and everything was as it used to be, still rooted. Then I installed 4.2.1 and Id get to the colorful undulating lines but they would never switch to the welcome screen to allow me access. I would hit the button and they'ed switch to the new welcome screen with a low battery message and then go black. When I tried to charge... the light would go from green to orange, to a faint orange to black. It doesnt seem to be charging and I cannot get anything to boot up at all now...
HELP !!!!!
Problem solved !!!
poolprof said:
I rooted my 1st Gen Kindle Fire, installed twrp, and fff, everything worked fine. I wanted to update my android sys so I could more easily use google play. I installed 4.2.2 but it would never boot up... just got to the colorful undulating lines continuously... so I restored back to my back up sys and everything was as it used to be, still rooted. Then I installed 4.2.1 and Id get to the colorful undulating lines but they would never switch to the welcome screen to allow me access. I would hit the button and they'ed switch to the new welcome screen with a low battery message and then go black. When I tried to charge... the light would go from green to orange, to a faint orange to black. It doesnt seem to be charging and I cannot get anything to boot up at all now...
HELP !!!!!
Click to expand...
Click to collapse
I looked around some other posts here and found my answer! Low power charge for and hour on my macbook pro... it booted up and began charging... switched it over to the stock wall charger... everything fine now!
Related
hey guys, i bought the fire for my wife for valentines day, immediately rooted it to get rid of that terrible kindle launcher and stuff, well, I've got a transformer prime and galaxy nexus, so after a couple months of her playing with my ics awesomeness she now wants to come over the good side, only t hing is, for the life of me i can't rememeber what i did as far as recover goes on this fire. I've read to hold the power button until it turns orange, but it won't do that for me. So how do i get into recovery with the kindle fire?
With your Kindle Fire off, hit the power button (and release it), and wait for the FireFireFire logo (triangular) to appear. Then, hit the power button until it turns from green to orange/red, and let go. You will then go into recovery.
first off, thank you very much for your reply.
When i pushed the power button (with the kindle off) it just went to a black screen with the word "kindle" in white and the word "fire" in orange. stayed there for about a minute or two then booted up. never a yellow triange.....any ideas?
vballrkc said:
When i pushed the power button (with the kindle off) it just went to a black screen with the word "kindle" in white and the word "fire" in orange. stayed there for about a minute or two then booted up. never a yellow triange.....any ideas?
Click to expand...
Click to collapse
Oops! Looks like you lost FireFireFire somewhere along the way. Probably because of the recent Kindle update, which also would have unrooted you, unfortunately. You will need to re-root (which will reload the FireFireFire boot loader).
The Kindle Fire Utility can root a 6.3 (OS) Kindle Fire. Not sure how you rooted last time. If you did not use KFU, the old procedure you used may not work any longer.
Ah. Ok. I was unaware you get iota updates after rooting. Thanks ill just start all over.
I rooted my KF with FFU .9.6 Everything was fine, I got AOKP M5 installed. However, it didn't seem to charge, even though the orange light was on. So it died. Now it goes from FFF to fastboot(kindle fire boot(in orange). I can't start it, or get it in recovery. I have tried re-installing drivers. I have tried Kindle brick utility. I can't seem to get it started. I have rooted previous mobile phones: og Droid, Droid X, and my current Galaxy Nexus. I have never bricked any mobile device. This Fire is driving me nuts. It is my second one. The first one would not charge, and this one does the same thing unless I wiggle the cord. Should I send it back to Amazon, they said they would replace it due to the charging issue(before I rooted it). PLEASE HELP
From your description it sounds like you need to try this:
http://forum.xda-developers.com/showthread.php?p=25400963
Once you get everything in order, use recovery to install FFF1.4. That will enable you to charge your device in extreme low power conditions.
Also, AOKP M5 and other 3.0 kernel versions of ICS have charging issues. The charging indicator doesn't work, even if it is charging and sometimes it will only charge while asleep, but it's very intermittent. It charges fine in TWRP so if all else fails you can take that route.
I re-installed kfu .95. I re-installed FFF. This got me into recovery. Then I did a factory reset, installed AOKP M5, apps. Bingo, my fire is back from the dead. I have it charging with kindle fire wall charger. The orange light shows, but it does not say charging on the home screen.
cehrl7 said:
I re-installed kfu .95. I re-installed FFF. This got me into recovery. Then I did a factory reset, installed AOKP M5, apps. Bingo, my fire is back from the dead. I have it charging with kindle fire wall charger. The orange light shows, but it does not say charging on the home screen.
Click to expand...
Click to collapse
It won't
Ok. It is really hard to get the Fire charging. I have to mess with the cord to get the orange light. Like I said this is my second one. Does anyone else have this issue?
cehrl7 said:
Ok. It is really hard to get the Fire charging. I have to mess with the cord to get the orange light. Like I said this is my second one. Does anyone else have this issue?
Click to expand...
Click to collapse
Create a backup and switch to a cm7 rom to see if what you are experiencing is due to the device or the kernel. All 3.0 kernel roms have charging issues in some form or another, including the one you're describing.
Well, I figured out that under settings>device>battery shows charging, even though orange light is off. Actually when you turn on screen the led lights orange. Once the screen shuts off, the light goes off. But, is still continues to charge. Screwy.
Its charging the battery icon just doesn't indicate it but if you enable the battery bar and locate it above your nav bar and enable charging animation you will see it is charging
I flashed the new FFF through TWRP as stated in the title of this post, but I didn't read any of the instructions which is sadly why I'm here now x.x...When I turn the kindle on, whether it's connected to my PC or if its connected to a wall outlet, the screen never turns on, but the power button light goes bright green for a split second, then bright orange, then it turns into a very dim orange and thats it, will anyone please help me on this on what to do?
How recently did you do this? A new version was released yesterday that was supposed to prevent that from happening.
Recent
soupmagnet said:
How recently did you do this? A new version was released yesterday that was supposed to prevent that from happening.
Click to expand...
Click to collapse
Like half an hour ago :\ and, I made some food and came back to find the gedeROM booting, and as soon as it booted, it said Powering Down because the battery was too dead, then the kindle restarted and I took the power cable out, and it said Charging please wait, but thats it, that shows up for like a split second then the screen goes black again
EDIT - Sorry for being so paranoid, I ran over to check how my tablet was doing and I pressed the power button, and its successfully booted at 4% battery. I guess the battery was just THAT dead
Sorry, I misunderstood your post. I thought you meant you flashed the .zip through fastboot instead of TWRP.
But yeah, that's normal.
Charge it hopefully you'll be good
Hello,
Got an AFTV at staple the other day. I tried to follow the aftvnews guide "How to setup a new AFTV...".
Apparently my AFTV was pretty old since the initial unplug/plug trick did not work and the box was always stuk on waiting to download the update. I finally let the update run through and ended up with Firmware 51.1.0.2_user_510058520.
After that I tried to root the AFTV. For this I used adbFire. I was able to connect to the box (no internet connection at that time) and click on the Towelroot option. I did click on "Make it ra1n" and wait for a very long time. I never saw any message indicating that it succeded or failed. With the remote I ended up going back to the previous menu. I tried to install SuperSu but that did not work. Su was not installed. After rebooting the box, I get the back and white Amazon logo and then the screen goes black. The TV shows the selected input as if the AFTV is not sending any signal. I tried to plug the internet cable (with the 2 domains blocked) and the AFTV finally goes from the Orange blicking led to the Blue one but it's still stuck after the amazon back and white logo. I did try the ALT-I-PrntScr (which had worked previously when I was trying to prevent the update to install, I managed to get into recovery and do a factory reset ,so I know the keyboard itself is OK). But this time ALT-I-PrntScr only get the box to restart and brings me back to the Amazon black and white logo that disappear after a minute.
Nevertheless, I can still access the box from an adb shell, adbFire can connect to the AFTV. But since I no longer see any menu on the screen I can't attempt to reroot from adb fire.
A reboot recovery does not work as it's not authorized.
su command is not found , so it would confirm supersu did not install (properly). What's weird though is that if I do a ps, I see a process "u0_a1 6199 328 476352 18640 ffffffff 00000000 S eu.chainfire.supersu"
Any idea how I can unstuck the box ?
Thank you.
Some info for people in the same situation, the issue was that Towelroot needs internet access to complete.
i have exactly the same situation here. system doing an update and the power got cut off and viola. Welcome white amazon logo and pulsing white and orange indicator light. Tried all the possible ways found on the forum and net but no joy. Now its sitting on my drawer and hoping i can still find a way to make it alive.
DhiJay23 said:
i have exactly the same situation here. system doing an update and the power got cut off and viola. Welcome white amazon logo and pulsing white and orange indicator light. Tried all the possible ways found on the forum and net but no joy. Now its sitting on my drawer and hoping i can still find a way to make it alive.
Click to expand...
Click to collapse
I have the same exact issue right now, probably that same update yours downloaded from 2 weeks ago:
https://forum.xda-developers.com/fire-tv/general/fire-tv-stuck-amazon-logo-adb-t3809305
This guy had the same problem too, and he has a big list of things to try, none of which worked for me:
https://forum.xda-developers.com/fire-tv/help/fire-tv-remains-stuck-amazon-firetv-t3561797
Mine's unrooted on the latest version, so I guess I can't root and reinstall rom. I'd hate to have to throw this away it's only 2 years old. I have a 5 year old Roku that still runs great.
"Perfect" timing I guess with Prime Day coming up?
Edit: couple more guys having the same issue recently, sounds like a mass bricking going on
https://forum.xda-developers.com/fire-tv/help/firetv-box-white-amazon-logo-blank-t3472867
https://forum.xda-developers.com/fire-tv/help/fire-tv-stucks-white-amazon-logo-t2889867
https://forum.xda-developers.com/showthread.php?t=2799779&page=7
DhiJay23 said:
i have exactly the same situation here. system doing an update and the power got cut off and viola. Welcome white amazon logo and pulsing white and orange indicator light. Tried all the possible ways found on the forum and net but no joy. Now its sitting on my drawer and hoping i can still find a way to make it alive.
Click to expand...
Click to collapse
I played with mine a bit more today and I was able to fix
I read somewhere that someone else was having the same issue and said it was a HDCP handshake issue and they were able to fix by plugging to a different HDMI port on the TV. I tried that and it booted up to the colorful Amazon logo, showed the home page for a sec, then went to a black screen. From here, it would flash the home screen really quick randomly every 30 secs or so, so I know it booted up and I'm on the home page, it's just not displaying correctly. I was then able to pair my remote (I unpaired before because I was using flirc), then us the remote shortcut to factory reset. Good to go after the reset.
TBH, I did not try turning it on before I swapped HDMI ports so I'm not 100% sure if switching ports really did help it boot past the white logo, or if it just happen to get fixed after some time.
Interestingly while on the colorful logo, the alt+i+printscreen trick did not work for me. So it took me longer before I could get to the factory reset.
johnusesandroid said:
I played with mine a bit more today and I was able to fix
I read somewhere that someone else was having the same issue and said it was a HDCP handshake issue and they were able to fix by plugging to a different HDMI port on the TV. I tried that and it booted up to the colorful Amazon logo, showed the home page for a sec, then went to a black screen. From here, it would flash the home screen really quick randomly every 30 secs or so, so I know it booted up and I'm on the home page, it's just not displaying correctly. I was then able to pair my remote (I unpaired before because I was using flirc), then us the remote shortcut to factory reset. Good to go after the reset.
TBH, I did not try turning it on before I swapped HDMI ports so I'm not 100% sure if switching ports really did help it boot past the white logo, or if it just happen to get fixed after some time.
Interestingly while on the colorful logo, the alt+i+printscreen trick did not work for me. So it took me longer before I could get to the factory reset.
Click to expand...
Click to collapse
I wish I had the same luck like you but i tried different tv's, all the ports availble and different HDMI cables but still no luck.
Anyone able to find a solution to fix it? or should I just throw it out?
DhiJay23 said:
Anyone able to find a solution to fix it? or should I just throw it out?
Click to expand...
Click to collapse
Sorry you weren't able to fix. Before you throw away, try contacting support. Not because they can fix it, they most probably can't. When I had problems with mine, I contacted them and they gave me a $15 credit off of a new one because I was out of warranty. This was a couple days before Prime Day so I was able to snag a new one for really cheap. Plus my old one started working again, so I now have 2 Fire TVs
Hi, hoping someone can help.
Having a major problem with my P605 (Hong Kong version), It just will not start up anymore.
Current State:
At the moment, with just the power button, it shows the samsung galaxy note 2014 logo. Then a few seconds later the startup sound will play. Then a few seconds later the samsung boot animation plays. Then once the animation stops and just displays the samsung logo, nothing else. It stays on that, and can stay on it for hours.
Note: The Samsung boot animation has a very pink hue to it, like the cyan and yellow are no longer there. More on that later.
With the Power + Home + Vol Up it says recovery mode is starting, then resets and boots as above.
With the Power + Home + Vol Down it goes into download mode no problem.
Background (Some of it may or may not be relevant, just putting it on here in case it is):
Up until a couple of weeks ago it was stock, but rooted JB (IIRC), then it was accidentally dropped (not by me). It is in a Trident Krakhen case, but that did not stop damage being done, the damage being the backlight stopped working. I followed a Youtube guide and removed/reinserted the ribbon. Put it back together and switched it on, and worked, sorted!
Now I thought as the seal of freshness has been popped, I may as well upgrade it to Lollipop so I can play Pokemon Go. As Lollipop has not been released for HK p605's I used the Irish (I think) firmware. Upgraded using Odin, no problem. So then I wanted root access, so I used the method described on XDA to root Lollipop using "CF-Auto-Root-lt03lte-lt03ltexx-smp605.zip". Again, flashed with Odin, no problem. But the root didn't take, a few programs randomly lost root access, others would not ask for access and just say the tablet was not rooted, etc. I reflashed the file at least 6 times to try and get it to take. Eventually it did.
Forward to the next day, I go to unlock my tablet and the screen has gone all pink, same as above, like Cyan and Yelow have gone. And a black shadow is over the left half of the screen. I restarted the tablet, colours came back, yay. All fine up until yesterday, the pink and shadow were back again. This was late at night while I was in bed, so not near the computer. I restarted the tablet. This time the pink stayed. OK, so I thought I will wipe the tablet back to factory and see if that helps (not done a wipe or anything else up until this point) so I try to go into recovery mode. It showed the logo and the little blue recovery text, then black screen, then normal boot logo and back into the OS. Tried a few times to get into recovery mode, but just kept resetting back to OS. So I told ROM toolbox to force a recovery restart, big mistake! It went into recovery boot loop. Just Galaxy Note 2014 entering recovery" then blank, repeat. No sound, nothing. I think that perhaps if I can turn it off, it may reset the whole thing, I put the tablet into download mode, then go to sleep. In the morning, the battery is dead. Great! Plug it in, instantly recovery boot loop. Fudge! From this point I don't know the battery level of the tablet, so that MAY be causing issues. I plug it into the PC to flash with Odin. Flashed stock lollipop, restarted, flashed stock bootloader, flashed CF auto root. Multiple times in each. Nothing seems to bring it out. The closest I got to something was the tablet telling me recovery was screwed and I needed to use Kies recovery. I left it plugged in for a few hours to try and build up some battery power, the PC does not provide enough power to charge, it makes the screen flicker rapidly when the battery is empty, but all the time while charging it is boot looping and the screen is on full brightness so I don't know how much I gained.
Finally flashed stock KK, and now it just hangs on the Samsung animation logo as above.
Is there anything I can do?
Does the pink hue and black shadow mean hardware is affected? The colours seem fine in download mode.
If anyone could help that would be great as I am scratching my head here.
EDIT 1: OK, I took the casing off, found that the little push on connector next to the usb connector had pried itself loose, I reattached it, and removed/reinserted the screen ribbon cable. All while the tablet was powered on (my old electronics teacher would have had a fit!). Restarted, the pink tinge has gone and the boot animation came up at the same time as the audio. Good signs. But still froze on the 'glow' effect. Tried recovery and YES it went into recovery, although the little android fell over with an exclamation mark over him. But still, progress. So now I am reflashing stock, will see how it goes.