Hello, everyone.
My Kindle Fire is rooted and running stock version 6.3.1. It had been working well for about a month.
This evening I plugged it into the wall charger while having dinner and watching the game. I came back after the game, about three hours later, and saw that the LED was still yellow. Oddly, it should have been green by that time. Unplugging it, I saw that the battery hadn't charged at all. This seemed really odd, so I shut it down by holding the power button until I saw the dialog box asking if I wanted to shut it down.
I waited a few moments after shutting down and tried to start it again. First I saw the familiar blue and white screen I've seen since rooting it (side note: is this the current FireFireFire logo?) with v1.4a then it went to the yellow and white splash screen and remained stuck there for a good five minutes.
Something seemed really wrong, so I leaned on the power button for twenty seconds and tried booting again with the same result.
I tried plugging it into the computer to see what KFU says. It reported that the Fire is in bootmode 4000 (normal).
I've got a backup made about ten days ago with TWRP, but I moved it from the SD card and onto the computer. If I can't get the Fire running again, do you think I might yet be able to restore from this backup?
Yes, 1.4a is the latest FFF and it sounds like something is wrong with your system software.
Restoring from your backup might be a good idea. You can use FFF's recovery selection to get back into TWRP (I'm guessing this is your recovery). If you aren't familiar with how to do this... Start up your device and watch the power button LED. As soon as it goes from bright to dim, press the power button again (sometimes it takes a few presses) and a selection menu will appear on the display. Press and release repeatedly to scroll through the options until recovery is selected and then wait.... it will boot into recovery.
Use the "Mount" feature to get to mount it on your computer and transfer the backup onto the device. You should then be able to restore your backup.
Thank you! Yes, I'm using TWRP for recovery. Never thought I'd actually need it. I'll give it a try tonight.
I think I'll change my username to "flabbergasted." You can call me that. The Fire is working again.
Thank you, kinfauns, from the bottom of my heart for your help with this and your excellent guide, Kindle Fire For Beginners.
As you suggested and instructed above, I booted into TWRP recovery (version 2.1.1) and selected the Mount feature. This caused an Autoplay dialog box to open on my Win7 desktop with an option to Open Folder to View Files (Using Windows Explorer). Selecting this option opened a window displaying the contents of the SD card. I thought wrongly that I was going to have to push the files using adb.
Navigating to the folder in which I placed the backup folder (in this case named "2012-06-08--19-15-36" which I surmise is the date and time of the backup), I cut and pasted the entire folder to the window showing the contents of the SD card under the filepath:
Removable Disk G:\TWRP\Backups\0000000000000000\2012-06-08--19-15-36
I then carefully disconnected the Fire and used Unmount before returning to the main menu to use the Restore feature. Here's where something weird happened. TWRP didn't show the backup set I had just copied onto the SD card. I had to power down and reboot before Restore displayed that backup set. Restoration itself took a couple of minutes.
I then used the System option under Reboot to restart the Fire, having found that if you use the Power Off option, it will subsequently continue to boot into recovery. It booted into the home screen as I had left it about ten days ago.
The Fire is now charging.
Related
My T989 is rooted. I use it to log my work hours in "It's About Time". I back that app's data up every day to the box folder, and I sync with box. HOWEVER, the box syncing has aparently been pretending to work and doing nothing since february, so I'm screwed right now as the touchscreen on the phone was shattered today. It has no visuals or touch ability. the gorilla glass survived just fine, but the screen behind it is gone.
What I need to know is how can I access the data in the builtin memory. I would love to use Kies, but Kies, points out that my phone is locked (I use a pattern lock) and says I have to unlock it.
Is there someway to remotely unlock a broken phone? The phone can go be a doorstop at this point, but I HAVE to have those backup files sitting in the box folder. They aren't on the microsd card.
So the display is damaged but the digitizer is fine correct? As for data just pull files with adb....I believe you can do that unless you never had USB debugging on
Sent from my SGH-T989 using Tapatalk
CptCrackers said:
My T989 is rooted. I use it to log my work hours in "It's About Time". I back that app's data up every day to the box folder, and I sync with box. HOWEVER, the box syncing has aparently been pretending to work and doing nothing since february, so I'm screwed right now as the touchscreen on the phone was shattered today. It has no visuals or touch ability. the gorilla glass survived just fine, but the screen behind it is gone.
What I need to know is how can I access the data in the builtin memory. I would love to use Kies, but Kies, points out that my phone is locked (I use a pattern lock) and says I have to unlock it.
Is there someway to remotely unlock a broken phone? The phone can go be a doorstop at this point, but I HAVE to have those backup files sitting in the box folder. They aren't on the microsd card.
Click to expand...
Click to collapse
You can always boot into recovery and pull from your data partition using ADB. Then you can restore that to another phone after you install your time tracking app.
I have been in usb debugging. It may be in usb debugging mode right now.
When I connect it, it shows the drive, but they show as empty. Which is the same thing that happens on my GS4G when it's in debugging.
If you could tell me how to go about extracting files, that would be great, assuming there is even a way.
Is the digitizer the touch portion of the touch screen? If so, then no, that's not working. The phone boots, it receives texts, makes other sounds like it's working, but the screen is black. The LCD is cracked, and it will not accept touch input. I have haptic feedback on and it's definitely not letting me attempt to do the unlock screen.
slm4996 said:
You can always boot into recovery and pull from your data partition using ADB. Then you can restore that to another phone after you install your time tracking app.
Click to expand...
Click to collapse
Could you tell me how I do this? The only time I ever booted into recovery was during the rooting process. Do I need to be able to see the screen to do it, or is there a way to get into it remotely? If so, can you either tell me what to do or point me at a tutorial or something? I wouldn't know where to start.
CptCrackers said:
Could you tell me how I do this? The only time I ever booted into recovery was during the rooting process. Do I need to be able to see the screen to do it, or is there a way to get into it remotely? If so, can you either tell me what to do or point me at a tutorial or something? I wouldn't know where to start.
Click to expand...
Click to collapse
To get into recovery, pull your battery then put it back in, then hold both vol up and vol down and hit the power button.
Type "help" without quotes in ADB to get a list of commands.
Sent from my SGH-T989 using xda premium
try this http://forum.xda-developers.com/showthread.php?t=628138
It got me out of a jam once on my vibrant, when the same thing happened to me and needed some pictures for my work. USB debuggin has to be on though.
To backup the data from a damaged phone using ADB:
1) Enter Recovery mode:
Turn the phone off, remove the battery. Insert battery, hold volume up AND down while turning on. Plug in usb cable.
2)Open up your terminal/console. Enter the following commands (one command per line, press enter after each)
(this backs up the entire data partition)
Code:
mkdir phoneDataBackup
adb shell mount data
adb pull /data phoneDataBackup
You now have a copy of your phones /data folder, this contains the settings and data from your apps. Get a new phone and then install you app on it. Once you do that simply put the correct named folder from the phoneDataBackup back into your new phones /data folder.
Code:
adb push phoneDataBackup/data/com.rds.itsabouttime /data/data/
This should work just fine for you, I assume you already have ADB installed or can install it first.
THANKS ALL!!!
I am currently using the suggested Android commander to dump everything out of the phone. Lucky the usb debugging got left on when I was cleaning out bloatware last week!!!
Once it's done, or if even if it doesn't work, I'll be playing with the adb connection since it's not like I can break the phone worse... good learning opp!
Thanks for all the tips from everyone.
Quick update, and info in case someone later finds this thread in a search. The android commander did get back what I needed most. However, it also did some strange things. It can see a lot of stuff on the phone, but when pulling things from the phone, for some reason, some files and directories do not come over. I imagine this may have to do with permissions on those items.
I'm basically making thsi note here in case someone finds the thread, thinks they have dumped heir whole phone... just make sure you pick through the important directories before you think you've got everything and discard the phone.
Thanks again everyone. Ass officially saved.
Hello everyone.
I also just cracked my screen and have neither touch capability nor screen lighting, so I'm effectively blind in controlling my phone.
I know I have Clockworkmod recovery 5.0.2.7 installed and rooted, but these solutions are not working for me.
I have tried removing the batt, reinserting the batt, holding UP+DOWN+POWER until the device vibrates, then let go of the POWER while holding UP+DOWN for another 10 seconds to be sure.
I then plug in the USB cable and my Windows 7 laptop does the "found USB device chime", so I know the device is on (and has not booted into Android, since the Samsung Galaxy logo jungle has not played.)
I also see that Windows 7 sees new "Removable Drives" that it adds after I plug in the device, but the drives cannot be accessed/are not available to Windows 7.
I'm definitely sure I'm in recovery because when I hit POWER, the Windows 7 "unplugged USB device" chime plays, the device vibrates and I'll hear the Galaxy S logo chime, which means I hit the 1st "reboot device" option on the recovery menu.
But when I open a console and type "adb devices" none are listed.
I have also tried Android Commander, and no devices are there either, so these 2 methods do not work. I'm wondering why adb cannot see recovery on mine if people are saying that it can.
I know that Clockworkmod recovery has a option for mounting the sdcard and data via USB. I also see that different versions of Clockworkmod have different menus.
Can someone help me by letting me know what/how many button presses I need to do to get to the "mount sdcard" and "mount data" options once I'm in recovery as I'm flying blind.
Thank you for any help.
soundwave4 said:
Hello everyone.
I also just cracked my screen and have neither touch capability nor screen lighting, so I'm effectively blind in controlling my phone.
I know I have Clockworkmod recovery 5.0.2.7 installed and rooted, but these solutions are not working for me.
I have tried removing the batt, reinserting the batt, holding UP+DOWN+POWER until the device vibrates, then let go of the POWER while holding UP+DOWN for another 10 seconds to be sure.
I then plug in the USB cable and my Windows 7 laptop does the "found USB device chime", so I know the device is on (and has not booted into Android, since the Samsung Galaxy logo jungle has not played.)
I also see that Windows 7 sees new "Removable Drives" that it adds after I plug in the device, but the drives cannot be accessed/are not available to Windows 7.
I'm definitely sure I'm in recovery because when I hit POWER, the Windows 7 "unplugged USB device" chime plays, the device vibrates and I'll hear the Galaxy S logo chime, which means I hit the 1st "reboot device" option on the recovery menu.
But when I open a console and type "adb devices" none are listed.
I have also tried Android Commander, and no devices are there either, so these 2 methods do not work. I'm wondering why adb cannot see recovery on mine if people are saying that it can.
I know that Clockworkmod recovery has a option for mounting the sdcard and data via USB. I also see that different versions of Clockworkmod have different menus.
Can someone help me by letting me know what/how many button presses I need to do to get to the "mount sdcard" and "mount data" options once I'm in recovery as I'm flying blind.
Thank you for any help.
Click to expand...
Click to collapse
If you have adb setup just do adb pulls. You can get anything that way. Slow, but a plan b if nothing else. I would count for you but I run twrp and I don't have time or battery to flash it over to cwm right now.
Edit: for whatever reason tapatalk didn't load anything past the OP...disregard.
Tapatalked from my Galaxy S II.
I have had a Kindle Fire since they day they came out. I immediately disliked the stock Rom so I ran the kindle fire utility and installed Fire Fire Fire and TWRP, rooted it, and installed CM7 Rom which has been working great. Transferred files and programs between my PC and Kindle with no issue for months. Now with all the ICS roms available and working I decided to try and upgrade to one of those and thats when everything went wrong. Its in a bootloop and the triangle appears, fades, lights up again and immediately boots to TWRP. I have flashed the entire kindle using TWRP trying to get everything off of it. Upon plugging it into my PC BRIEFLY when the triangle logo pops up I get a "USB device not recognized" on my PC. I have tried using KFUtility to reinstall drivers, tried uninstalling n reinstalling drivers but the same thing happens. I cannot use TWRP to mount at all, nothing happens. Kindle Fire UTility keeps saying adb offline, CMD adb devices also results in 0 devices found. I have tried putting it on normal boot using both ADB and KFUtility and it says "wait for device" and nothing ever happens. Any idea? Not even sure if I have a rom installed on my kindle anymore but my PC wontread it so I cannot push another image to it. Got a plane trip on Saturday and would love to have this working to kill the bordom lol. Any advise would be greatly appreciated.
It sounds like your bootmode is set to recovery. An easy way to fix this is download FFF1.4 to your computer and use the mount function in recovery to place it on your sdcard.
Flash it in recovery as you would a rom except don't wipe anything. When you reboot, hold the power button like you're trying to enter recovery and you'll be given the option to reset the bootmode.
Thank you so much for your advice but there in lies the problem. Inside the recovery console i choose to mount it and nothing happens. My PC will not let me access the kindle in anyway at all, either mounting the SD Card or via ADB/KFUtility.
anomiefaunus said:
Thank you so much for your advice but there in lies the problem. Inside the recovery console i choose to mount it and nothing happens. My PC will not let me access the kindle in anyway at all, either mounting the SD Card or via ADB/KFUtility.
Click to expand...
Click to collapse
Generally, the only thing that would prevent adb/kfu from communicating with the device is the drivers. Make sure they're installed properly. You may have to uninstall them (delete if applicable) and reinstall them.
Follow the instructions in this guide to install and verify your drivers.
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
K heres the latest (we r making progress!)
I got my device to be detected by my PC and used KFutility to change it to normal boot. Now instead of booting into recovery everytime it boots normally.... to a black screen (guessing my rom is shot or I deleted it while playing with it). The issue is the ONLY time my PC recognizes my kindle is for a .5 second period when i first turn my KF on and the yellow triangle appears. I can use this window to change it to normal bootmode, reinstall TeamWin, stuff like that, but i cannot mount it so I can transfer or adb so I can push. You can watch device manager and it'll pop up ADB android phone or whatever it should but poof, a second later gone.
anomiefaunus said:
K heres the latest (we r making progress!)
I got my device to be detected by my PC and used KFutility to change it to normal boot. Now instead of booting into recovery everytime it boots normally.... to a black screen (guessing my rom is shot or I deleted it while playing with it). The issue is the ONLY time my PC recognizes my kindle is for a .5 second period when i first turn my KF on and the yellow triangle appears. I can use this window to change it to normal bootmode, reinstall TeamWin, stuff like that, but i cannot mount it so I can transfer or adb so I can push. You can watch device manager and it'll pop up ADB android phone or whatever it should but poof, a second later gone.
Click to expand...
Click to collapse
Get your device drivers working so you can use adb. Follow the instructions in the post below...
http://forum.xda-developers.com/showpost.php?p=26144447
That is excellent advice and I wish it would work but I cannot pull up ADB once in TeamWin. Keeps saying no devices. As i said my PC detects it and ADB will detect it for .5 seconds on the orange triangle. Once the orange triangle disappears and it either boots to blackness or boots to TeamWin ADB stops recognizing my device. But I will play around with your suggestions once I get off work and let you know what i find out. Thanks again for everyones support.
Frozen screen during rooting
Hi,
I am new to the forum. I have a kF screen stuck (where it says 'kindle fire') while I was trying to root it. I tried hard reset, charging for half hour, calling AMAZON...nothing works. The screen goes off if I hold it for 20 seconds but when I put it back on same thing. I was trying to root it with 'fastboot (?). Is there anything at all I can do? Thanks.
peredexter said:
Hi,
I am new to the forum. I have a kF screen stuck (where it says 'kindle fire') while I was trying to root it. I tried hard reset, charging for half hour, calling AMAZON...nothing works. The screen goes off if I hold it for 20 seconds but when I put it back on same thing. I was trying to root it with 'fastboot (?). Is there anything at all I can do? Thanks.
Click to expand...
Click to collapse
Don't hijack the threads please. If you have a problem or question, post it in the Q&A section.
Coming from a phone with microSD extension, I had never encountered such an issue:
I bought this phone with a stock 4.2 Rom installed and tried to install a custom Rom. I first installed the latest version of touch recovery (tried it and it seemed to work fine) and did a backup using the default settings. Then I erroneously chose to format system and data, thinking that I could then "install from zip". Strangely, these steps deleted everything in the /sdcard directory and I couldnt select "external SD" (because the phone isnt equipped with it anyways?). Then I made a second mistake and restarted the phone, despite the message warning that I no longer had an OS installed. I took the battery out, and then held the power down while pressing the power button. The phone couldn't get into recovery, but instead showed a screen with the android logo, a large "Start" sign above it, and "Downloading...", "Do not turn off target !!" below it. Pressing the power button now got the phone to show just "Google" and a lock logo under it. The PC (windows 7) can not detect the phone throughout the process.
I tried the latest tool kit and samsung's USB driver but couldnt get the phone recognized by the PC.
Does this mean that the phone is doomed???
Please help!!!
Trent
Relax, it's not easy to 'doom' your Nexus. Especially with all the hard-workers in XDA
Try accessing Recovery mode by holding down BOTH vol up + vol down, as well as power. Holding just vol down + power is 'Download Mode', and at the least you can get to this. Means your phones far from doomed
Thanks a lot for the reply!
As a matter of fact, I also figured out how to get back to recovery (if only I had read your post earlier, my pain would've been much less!). But the problem remains that I can not get a target ROM onto the phone, since: 1. whatever I did seemed to have gotten rid of the nand backup supposedly stored in /data/media/TWRP/BACKUPS/ (I'm using TWRP V. 2.3.2.1). 2. I can not get my PC(or Mac, for that matter) to recognize the phone or the internal storage.
Any pointer from here?
Thanks again!!!
Trent
You can download a factory image and install with fastboot. It's quite easy and instructions are readily available on this forum. You can then install a custom ROM afterwards if stock is not your thing.
Found the answer finally!
It's the adb push method. Basically, it's to install adb drivers and execute a few commands via the command window. Not too bad... Don't know much about fastboot yet though ... If anyone else needs more details, please PM me (to save public bandwidth).
Thanks a lot anyways, whpnhp and jocalderone!!!
Trent
I have a first generation kindle fire, and was attempting to root the device using the kindle fire utility. So far, I had installed FFF and TWRP, but the tutorial I was following was outdated and by the time I realized this I had installed both utilities multiple times. It was on about the third attempt that the device froze.
The device is currently stuck on the boot screen with the "fire" in blue. In the top right corner, it says "v1.4a". At the bottom of the screen, it says "Press power button for boot menu". Unfortunately, the power button doesn't do anything; It doesn't shut the kindle down, doesn't enter the boot menu, nothing. When I have the kindle plugged into my windows 7 (64 bit) pc, a notification pops up saying "USB device not recognised". Sure enough, in the device manager window it shows up as "unknown device".
I've been searching for hours trying to find the solution but nothing matches the same problem. Any help would be greatly appreciated.
Crowbar Offensive said:
I have a first generation kindle fire, and was attempting to root the device using the kindle fire utility. So far, I had installed FFF and TWRP, but the tutorial I was following was outdated and by the time I realized this I had installed both utilities multiple times. It was on about the third attempt that the device froze.
The device is currently stuck on the boot screen with the "fire" in blue. In the top right corner, it says "v1.4a". At the bottom of the screen, it says "Press power button for boot menu". Unfortunately, the power button doesn't do anything; It doesn't shut the kindle down, doesn't enter the boot menu, nothing. When I have the kindle plugged into my windows 7 (64 bit) pc, a notification pops up saying "USB device not recognised". Sure enough, in the device manager window it shows up as "unknown device".
I've been searching for hours trying to find the solution but nothing matches the same problem. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Very informative...kudos to you.
Make sure the device is completely powered down (hold power button until it shuts off) and power it up again. When you see the Kindle Fire logo, press and hold the power button, or tap it repeatedly, and hopefully the boot menu will appear at the bottom.
Let's see if that works and we'll go from there.
Bob
soupmagnet said:
Very informative...kudos to you.
Make sure the device is completely powered down (hold power button until it shuts off) and power it up again. When you see the Kindle Fire logo, press and hold the power button, or tap it repeatedly, and hopefully the boot menu will appear at the bottom.
Let's see if that works and we'll go from there.
Click to expand...
Click to collapse
----------------------------------------------------------------------------------------------------------
I have exactly the same problem, with the same screen details. I tried your suggestion several times, with no response.
An old borrowed Windows 7 box got me nowhere - TWRP kept complaining that it couldn't connect, although I'd loaded adb. I quit when it started loading endless Explorer windows full of crapware and became unresponsive. I'm totally lost with Windows, anyway, so I just hit the wall switch to end to pain.
I'm running debian sid and I'm much happier with linux, after using it exclusively for well over ten years, although I'm an experienced user rather than an expert.
I've pried the back off my Kindle, but I'm afraid to touch the inside, except as a last resort. I downloaded SoupKit, but can't decompress it.
What's the best thing to try next?
Paleoflatus said:
----------------------------------------------------------------------------------------------------------
I have exactly the same problem, with the same screen details. I tried your suggestion several times, with no response.
An old borrowed Windows 7 box got me nowhere - TWRP kept complaining that it couldn't connect, although I'd loaded adb. I quit when it started loading endless Explorer windows full of crapware and became unresponsive. I'm totally lost with Windows, anyway, so I just hit the wall switch to end to pain.
I'm running debian sid and I'm much happier with linux, after using it exclusively for well over ten years, although I'm an experienced user rather than an expert.
I've pried the back off my Kindle, but I'm afraid to touch the inside, except as a last resort. I downloaded SoupKit, but can't decompress it.
What's the best thing to try next?
Click to expand...
Click to collapse
Are you unable to bring up the boot menu upon startup?
Bob
soupmagnet said:
Are you unable to bring up the boot menu upon startup?
Click to expand...
Click to collapse
First, thanks for the help you're generously offering.
No. The start button quickly raises the centred "kindle(white) fire(blue)", with "v1.4a" at the top right and "Press power button for boot menu" at the bottom. Neither my Debian sid box (file manager, or lsusb), nor a borrowed win7 box (file manager) recognises it. Repeated presses, or a few seconds of the power button at boot have no effect, but a very long press shuts it down.
I managed to detach the back without damage, but I'm reluctant to do the shorting trick at boot, if there's a better way. If all is lost, it's no further problem, as it was never much use, anyway, due to Amazon's geoblocking here in Australia. If I can't get cyanogenmod or equivalent on it, I'll just chuck it.
I'd prefer to fix it with my Linux box, if possible, as I've used nothing but Linux and Android for well over ten years.
I knew I shouldnt of done it. Its just my luck.
Tonight I installed the R112.....V8-R851T02-LF1R112 CFW posted a few days back.
Previous to this I had V8-R851T02-LF1V453.018444 (stock)
Install went fine. Booted up, I went through set up. I enabled developer options and enabled adb. My phone could not find the tv to sideload anything so I restarted the TV. Powered down, then back on. But flickering every few seconds along with the white light on the bottom.
The bottom doesn't work for anything. I found if I unplug it and plug it back in then immediately hold down the button the light will start flashing like its installing a firmware. I tried to reinstall the one I previously mentioned. It blinked for a bit but then back to the same flickering on and off.
No help expected, anything GREATLY appreciated.
I tried to include as much info as I could.
Thanks
First, R112 is not for your TV.
If you can enter TV setting , reflash firmware by "Local update" with V458 OTA file ,posted here:
TCL Android TV model 55p8m / Android Recovery TCL/BeyondTV/BeyondTV
My TCL Android TV model 55p8m has stuck and can't press any key in remote. The screen gives options to - Try Again - Factory data reset, but do not know how to select one of this option and continue without a keyboard or remote connected to the...
forum.xda-developers.com
or try reflash by TV power button.
No IMG file released for S343.
Hello Stasiof, Thanks for replying.
I fell asleep last night waiting for the file to transfer to USB.
This morning before work, I unzipped all files onto the root of a FAT32 USB stick, put it in, started the TV holding down the button. It flashed like it was updating, but very briefly. I would say about 15 seconds. And nothing afterward. A blank screen still. Was I not supposed to unzip?
xdeadxpoolx said:
Hello Stasiof, Thanks for replying.
I fell asleep last night waiting for the file to transfer to USB.
This morning before work, I unzipped all files onto the root of a FAT32 USB stick, put it in, started the TV holding down the button. It flashed like it was updating, but very briefly. I would say about 15 seconds. And nothing afterward. A blank screen still. Was I not supposed to unzip?
Click to expand...
Click to collapse
Do not unzip, copy to USB as downloaded.