I've been handed a Kindle Fire 1st gen (orange/white "Kindle Fire" text). It doesn't boot to Android - the device "powers on" (green LED power button lights up) and "Kindle Fire" displays in static orange/white text indefinitely when the power button is pressed and the unit is running off battery power. The usual shimmer/wave of the "Kindle Fire" text does not happen and it stays at the static screen until I hard power off the device by holding the power button for 5-10 seconds.
Plugging the device into a computer, the unit does not boot at all. The power button doesn't do anything. It doesn't light up, there is nothing displayed on the screen etc. Holding it down and keeping it pressed doesn't show any signs of life either. Windows has nothing in Device Manager and Linux returns nothing in dmesg, lsusb, lspci etc - it's as if the device isn't even there. I am aware of adb driver issues in Windows but this device isn't even recognised in either operating system, so it's a problem before the drivers are used in my view.
When plugged in to an AC outlet, the unit powers up and the above mentioned "Kindle Fire" text is displayed (and never goes away). No boot to anything further.
I've tried with a range of different USB cables and do I have a factory cable, in the hope that I can fastboot/flash recovery on this to get it working again. Unfortunately I'm falling at the first hurdle, as I can't get the unit to power on with a cable plugged in to a computer. When the device is powered on and the USB cable is then plugged in, the device is not showing on Windows/Linux either. In my mind it's not communicating over the USB D+/D- lines, or something is shorting that is preventing it from doing so.
The device has been rooted before, but with what ROM/what method I do not know. I'm not concerned with keeping root or the ROM that is on there - my aim is to return it to stock first and then consider other options later.
Any suggestions greatfully received! I'm stumped!
Plugging the device into a computer, the unit does not boot at all. The power button doesn't do anything. It doesn't light up, there is nothing displayed on the screen etc. Holding it down and keeping it pressed doesn't show any signs of life either. Windows has nothing in Device Manager and Linux returns nothing in dmesg, lsusb, lspci etc - it's as if the device isn't even there. I am aware of adb driver issues in Windows but this device isn't even recognised in either operating system, so it's a problem before the drivers are used in my view.
When plugged in to an AC outlet, the unit powers up and the above mentioned "Kindle Fire" text is displayed (and never goes away). No boot to anything further.
I've tried with a range of different USB cables and do I have a factory cable, in the hope that I can fastboot/flash recovery on this to get it working again. Unfortunately I'm falling at the first hurdle, as I can't get the unit to power on with a cable plugged in to a computer. When the device is powered on and the USB cable is then plugged in, the device is not showing on Windows/Linux either. In my mind it's not communicating over the USB D+/D- lines, or something is shorting that is preventing it from doing so.
The device has been rooted before, but with what ROM/what method I do not know. I'm not concerned with keeping root or the ROM that is on there - my aim is to return it to stock first and then consider other options later.
Any suggestions greatfully received! I'm stumped!
via xda-developers http://ift.tt/1RaUdji
Put the internet to work for you.
No comments:
Post a Comment