Hello, is my first time posting. My kindle fire (otter2 as cyanogenmod calls it) was bricked (bad build.prop) and is giving me a black screen after the kindle fire start (It should of shown a animation after the static picture) The back light is on and it has this purple tint.
So I went to fastboot and it worked. It showed a traffic light with the green light glowing. Bad thing is that there is not usb signal (Windows did not even try to see it and device manager did not refresh when I connected it!). I even tried linux and same thing! Only power works AND ALL DRIVERS WERE INSTALLED! (ALL WERE USB 2.0)
Any issues here? I tried 3 cables from and made 1 and no usb signal
jojo9092 said:
Hello, is my first time posting. My kindle fire (otter2 as cyanogenmod calls it) was bricked (bad build.prop) and is giving me a black screen after the kindle fire start (It should of shown a animation after the static picture) The back light is on and it has this purple tint.
So I went to fastboot and it worked. It showed a traffic light with the green light glowing. Bad thing is that there is not usb signal (Windows did not even try to see it and device manager did not refresh when I connected it!). I even tried linux and same thing! Only power works AND ALL DRIVERS WERE INSTALLED! (ALL WERE USB 2.0)
Any issues here? I tried 3 cables from and made 1 and no usb signal
Click to expand...
Click to collapse
Can you still get into twrp? You should be able to adb push cyanogenmod back into the device.
--》Sent from my mind to your screen
mindmajick said:
Can you still get into twrp? You should be able to adb push cyanogenmod back into the device.
--》Sent from my mind to your screen
Click to expand...
Click to collapse
Don't forget adb sideload!
Sent from my VS840 4G using xda app-developers app
Related
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
After searching and reading many threads and trying several "fixes", I think my last resort is this post (at least before I try Firekit or similar). I hope I didn't miss the one thread that has my answer.
Background:
Using Win7 64 bit
KF 1st gen (I believe)
Completely stock
Using Amazon KF HD charger and USB cable Amazon supplied when similar issue happened with our other KF (that new charger fixed that one)
Symptoms:
While plugged into the charger the green light will appear and a few seconds later we'll get the "KINDLE FIRE" logo on screen, sometimes it's animated and sometimes not. Sometimes the logo appears for about 5 seconds and other times about 30 seconds. When the logo appears the screen back-light first starts out low and then after a second or so it will brighten until the logo disappears and the KF appears to turn off, at least until some seconds later the green power light will come on and the process starts all over and keeps repeating. On occasion during the cyclic boot process I have seen the slide lock screen which was unresponsive and once I saw the screen with the KF device name, time, WiFi status, batt level (and no I didn't notice), etc. Lately I haven't seen either of those screens again, just the logo or nothing.
I've downloaded the Android SDK and installed the drivers but when I plug the KF into any of my USB ports the KF is not recognized. So if I can't get the PC to recognize the KF I can't go any further with trying to restore to factory default using TWRP or similar.
So my question is does anyone have something else I/we can try before moving on to Firekit? Thanks to all for your time and attention. BTW Amazon offered to sell me a new KFHD for $129 but I just don't have that in my budget right now so your help is much appreciated.
hiltoncp said:
After searching and reading many threads and trying several "fixes", I think my last resort is this post (at least before I try Firekit or similar). I hope I didn't miss the one thread that has my answer.
Background:
Using Win7 64 bit
KF 1st gen (I believe)
Completely stock
Using Amazon KF HD charger and USB cable Amazon supplied when similar issue happened with our other KF (that new charger fixed that one)
Symptoms:
While plugged into the charger the green light will appear and a few seconds later we'll get the "KINDLE FIRE" logo on screen, sometimes it's animated and sometimes not. Sometimes the logo appears for about 5 seconds and other times about 30 seconds. When the logo appears the screen back-light first starts out low and then after a second or so it will brighten until the logo disappears and the KF appears to turn off, at least until some seconds later the green power light will come on and the process starts all over and keeps repeating. On occasion during the cyclic boot process I have seen the slide lock screen which was unresponsive and once I saw the screen with the KF device name, time, WiFi status, batt level (and no I didn't notice), etc. Lately I haven't seen either of those screens again, just the logo or nothing.
I've downloaded the Android SDK and installed the drivers but when I plug the KF into any of my USB ports the KF is not recognized. So if I can't get the PC to recognize the KF I can't go any further with trying to restore to factory default using TWRP or similar.
So my question is does anyone have something else I/we can try before moving on to Firekit? Thanks to all for your time and attention. BTW Amazon offered to sell me a new KFHD for $129 but I just don't have that in my budget right now so your help is much appreciated.
Click to expand...
Click to collapse
You need a factory cable
KF Factory Cable
soupmagnet said:
You need a factory cable
Click to expand...
Click to collapse
I appreciate the quick reply. So my follow-up is to say I'm using the USB cable that came with the Amazon charger they sent when having problems with our other KF. Is that not a "factory" cable? If not, do you have any idea if this one would work: ebay.com/itm/like/271275399661?lpid=82 ??? Or do I need to spend $17 on this one: amazon.com/Factory-Amazon-Kindle-Motorola-Tablets/dp/B00BPDH4G4 ???
Thanks again.
hiltoncp said:
I appreciate the quick reply. So my follow-up is to say I'm using the USB cable that came with the Amazon charger they sent when having problems with our other KF. Is that not a "factory" cable? If not, do you have any idea if this one would work: ebay.com/itm/like/271275399661?lpid=82 ??? Or do I need to spend $17 on this one: amazon.com/Factory-Amazon-Kindle-Motorola-Tablets/dp/B00BPDH4G4 ???
Thanks again.
Click to expand...
Click to collapse
Yes 'factory' as in the one they use at OEM to install software.
Build Your own factory Cable is also an option if you can solder tiny things.
I have a galaxy nexus, uses the Eclipse-2.1-toro-build4 rom (old I know, but it was smooth and worked for me, so I kept it).
Last night, after keeping it in my backpack during a bike ride, I went to go use it. The screen is black and I noticed a few solid color black lines running through the screen. Screen is likely dead, my guess.
I am able to boot up the phone fine. I see the L..E.D. notification light come on, and when I get new emails (I left it on wifi the last time I used it), I'll hear notifications...
But, when I try to connect my phone through usb and attempt to connect to it via adb, I'm getting a device not found. I've connected my phone dozens of times using this method without a problem.
Anytime I issue a command with adb from my computer (ubuntu 12.04), it gives me the device not found although the device is connected via usb. This happens even when the galaxy nexus is displayed in nautilus, so it's clearly connected to the computer.
Any idea how to access my sdcard with adb then or to troubleshoot why it's not being read?
Does your phone have a screen lock? Try pressing the power button to unlock it and see if you can find the unlock button (assuming the touch screen still works). If you have a pin, it might be quite hard to get it
I can't access adb whilst my phone is locked. I think it is a security measure.
My wife and I bought my father-in-law a Fire TV which worked fine for some time. Then he brought it to my house because it wasn't working any more. I don't know what he did, but all it does is hang at the initial boot screen (black screen, white Amazon logo). Amazon has sent us a replacement Fire TV, but they let me keep the brick. Is there any way to recover this Fire TV? I've read through some of the threads. Tried using a keyboard to enter recovery (didn't work). Haven't tried adb (I don't have a USB-A to USB-A cable).
Thanks!
same issue
i hadn't used my fire tv for a couple months but was working flawlessly the last time I did use it and now no matter what tv I try to connect it to or how many hdmi cables I tried I can't get my fire tv to boot past the initial boot screen of the white Amazon logo it don't make it to the fire tv logo or any other screen it's just a black screen and screens all say no signal. I had rooted it back before I stopped using it with towel root and had adb enabled but after I boot it and it goes past the Amazon logo to the black screen the logo the led on the box is white then starts blinking then turns an amber color and sorta pulses or blinks differently than the while led blinked. Any help would b much appreciated I have been searching all over several forums and websites for days and nobody seems like they r having this issue so I'm totally lost
Stuck on Amazon Logo right out of the box/new
ryanrickard85 said:
i hadn't used my fire tv for a couple months but was working flawlessly the last time I did use it and now no matter what tv I try to connect it to or how many hdmi cables I tried I can't get my fire tv to boot past the initial boot screen of the white Amazon logo it don't make it to the fire tv logo or any other screen it's just a black screen and screens all say no signal. I had rooted it back before I stopped using it with towel root and had adb enabled but after I boot it and it goes past the Amazon logo to the black screen the logo the led on the box is white then starts blinking then turns an amber color and sorta pulses or blinks differently than the while led blinked. Any help would b much appreciated I have been searching all over several forums and websites for days and nobody seems like they r having this issue so I'm totally lost
Click to expand...
Click to collapse
Hi, were you able to fix it, I have same issue, except mine did it right out of the box, brand new, first time plugging it in. any help will be appreciate it.
Mike Power
Hi All,
I've been looking into the forum and came across couple of issue with 'dead' nexus 7 but none of them applies for mine. I was browsing the device, when suddenly it flashed and powered down. Now the table wont charge (there is no battery logo) and even the table wont powering on. I tried both with power and usb charging (for long hours).
The device is recognized by adb drivers (as unauthorized) hence could not do any modifications and not recognized at all by fastboot. I was wondering if someone had similar issue in the past with nexus 7 2013 (2nd gen) or similar android tablets/handsets.
I appreciate any help!
Thanks
attam9891 said:
Hi All,
I've been looking into the forum and came across couple of issue with 'dead' nexus 7 but none of them applies for mine. I was browsing the device, when suddenly it flashed and powered down. Now the table wont charge (there is no battery logo) and even the table wont powering on. I tried both with power and usb charging (for long hours).
The device is recognized by adb drivers (as unauthorized) hence could not do any modifications and not recognized at all by fastboot. I was wondering if someone had similar issue in the past with nexus 7 2013 (2nd gen) or similar android tablets/handsets.
I appreciate any help!
Thanks
Click to expand...
Click to collapse
How is it recognized in ADB or fastboot without powering on? My understanding is that the tab would not turn on if the battery is dead since it doesn't use the current supplied through USB directly. It could be something as simple as that; or the battery connector came off as it is rare one would go out abruptly like that.
graphdarnell said:
How is it recognized in ADB or fastboot without powering on? My understanding is that the tab would not turn on if the battery is dead since it doesn't use the current supplied through USB directly. It could be something as simple as that; or the battery connector came off as it is rare one would go out abruptly like that.
Click to expand...
Click to collapse
It is recognized in ADB as an unauthorized and every command is type the response is "error: device unauthorized ...." Is there a way to Enable USB debugging from command line (windows/linux)? There are no blinking leds, and cannot boot it up into recovery mode.
attam9891 said:
It is recognized in ADB as an unauthorized and every command is type the response is "error: device unauthorized ...." Is there a way to Enable USB debugging from command line (windows/linux)? There are no blinking leds, and cannot boot it up into recovery mode.
Click to expand...
Click to collapse
I understand your saying "it won't power on" to mean nothing happens when you try to turn it on- as in it's totally dead. In that state, PC won't even see anything, let alone recognize an ADB device. You might want to backtrack a bit and tell what you did, what happened, and what you're trying to accomplish now, and maybe someone can help.
Does it turn on at all, and if it does, how far would it get?
graphdarnell said:
I understand your saying "it won't power on" to mean nothing happens when you try to turn it on- as in it's totally dead. In that state, PC won't even see anything, let alone recognize an ADB device. You might want to backtrack a bit and tell what you did, what happened, and what you're trying to accomplish now, and maybe someone can help.
Does it turn on at all, and if it does, how far would it get?
Click to expand...
Click to collapse
Thank you for your reply.
After troubleshooting I noticed that its not dead since i am able to see the devices under adb devices. I also noticed that the device isnt dead because it rang when I clicked locate my device from my google account.
I think its the display which is faulty. I will buy an HDMI cable for the nexus 2013 device and connect it to hd tv to mirror the display.
Thanks