Usually I fix all my friends and families androids, and am know as the head of technology amongst my people, but here I am asking bigger people for help. I have a Kindle Fire HD 7", 7.4.1, rooted with no second bootloaders or custom roms whatsoever, just a stock to root. It recently ran out of battery and I've been stuck for the last hour trying to get it to turn on PROPERLY. I've googled it, checked here at XDA, and all I read is "charge it, hold for 20-30 seconds, play with the volume buttons while pressing power, etc" but it does not help. At first sight, the battery is indeed dead. I had the settings to sleep the screen in 5 minutes and that's how it got like that. Now IT DOES turn on, I see the nice Kindle Fire logo, it flashes once as it always does when its ready to start up, but that's where it stays. It will not go beyond that. I've tried all types of tricks here at XDA, I have NO factory cable, (wouldn't mind making one if I had the proper thread/tools) and the ridiculous USB and charging base I'm using is not the original (they are good brand though...), so I'm assuming, from what I've heard, its not getting the proper charge. Okay I'd admit that, but why does it stay stuck in the logo? I did nothing but play Falling Fred before it died, and I have no type of custom mods to it for it to be bricked or in a boot loop? Can anybody help/guide me into what to do?
Crossvxm said:
Usually I fix all my friends and families androids, and am know as the head of technology amongst my people, but here I am asking bigger people for help. I have a Kindle Fire HD 7", 7.4.1, rooted with no second bootloaders or custom roms whatsoever, just a stock to root. It recently ran out of battery and I've been stuck for the last hour trying to get it to turn on PROPERLY. I've googled it, checked here at XDA, and all I read is "charge it, hold for 20-30 seconds, play with the volume buttons while pressing power, etc" but it does not help. At first sight, the battery is indeed dead. I had the settings to sleep the screen in 5 minutes and that's how it got like that. Now IT DOES turn on, I see the nice Kindle Fire logo, it flashes once as it always does when its ready to start up, but that's where it stays. It will not go beyond that. I've tried all types of tricks here at XDA, I have NO factory cable, (wouldn't mind making one if I had the proper thread/tools) and the ridiculous USB and charging base I'm using is not the original (they are good brand though...), so I'm assuming, from what I've heard, its not getting the proper charge. Okay I'd admit that, but why does it stay stuck in the logo? I did nothing but play Falling Fred before it died, and I have no type of custom mods to it for it to be bricked or in a boot loop? Can anybody help/guide me into what to do?
Click to expand...
Click to collapse
Many Android devices, once depleted of battery, will not boot properly until the battery is anywhere from 20% or above. Try letting it charge longer. To speed up the process, use a wall adapter from your other devices. it will pump more voltages. As you said, there aren't any mods I can see that would cause bootloops or bricks.
Try charging it for a good hour, not booted up. To make sure it has charge. Then try to turn it on. This is very weird though, first time I heard a Android device acting up like that.
Sent from my air conditioner unit running CyanogenMod
I left it charging from 5am to now and it hasn't charged a thing because when I disconnected it and tried to turn it on it turned off after 7 minutes of the Kindle Fire logo. I also noticed that the reflection animation on the logo moves faster than it usually does. It just stays there. I'm guessing my only option would be a factory cable of some sort. No matter how many 20 second power button thing I use, it just stays stuck on the logo, as if something had damaged the firmware somewhere, but how? I will try to charge it once more for a while and see.
EDIT : I made my own "factory cable" and got it to fastboot. Now what can I do to restore it???
Hopeless???
Okay so here's how far I've gotten:
1. Tried to charge it for hours, used 20 second reset (no good)
2. Looked up instructions on how to restore from a brick (bologna because I can't get the ADB working at all, no clue how to use)
3. Made my own factory cable off of a Samsung USB, got into fastboot with no problem
4. Stuck at what to try next. I tried using the thread http://forum.xda-developers.com/showthread.php?t=2166637 (which I know I'm not hard bricked but either way tried) and used the KFHD_SRTv1.3.5 for 7.3.0 from another thread and my device does not get detected. When I go to Device Manager, the Kindle appears as Tate-PVT-08, don't know if that's normal, but I have run out of solutions.
Where do I possibly go from here? Its only been 19 hours without this thing and I already miss it...unlike other "noobs" who ask for help here, I actually tried on my own to get a solution but got nowhere.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Crossvxm said:
Okay so here's how far I've gotten:
1. Tried to charge it for hours, used 20 second reset (no good)
2. Looked up instructions on how to restore from a brick (bologna because I can't get the ADB working at all, no clue how to use)
3. Made my own factory cable off of a Samsung USB, got into fastboot with no problem
4. Stuck at what to try next. I tried using the thread http://forum.xda-developers.com/showthread.php?t=2166637 (which I know I'm not hard bricked but either way tried) and used the KFHD_SRTv1.3.5 for 7.3.0 from another thread and my device does not get detected. When I go to Device Manager, the Kindle appears as Tate-PVT-08, don't know if that's normal, but I have run out of solutions.
Where do I possibly go from here? Its only been 19 hours without this thing and I already miss it...unlike other "noobs" who ask for help here, I actually tried on my own to get a solution but got nowhere.
View attachment 2012991
View attachment 2012994
Click to expand...
Click to collapse
Once you get into fastboot, unplug the cable and plug in a regular USB cable that came with the device, and try to restore with the System Restore Tool.
seokhun said:
Once you get into fastboot, unplug the cable and plug in a regular USB cable that came with the device, and try to restore with the System Restore Tool.
Click to expand...
Click to collapse
I tried and the System Recovery Tool does not detect the device. It stays at "waiting for device"
One step forward and two steps back
Okay each time I advance, I am stuck with a new obstacle. I got ADB working (can use its commands) but my device isn't detected when I use the command "adb devices." As mentioned before, in Device Manager > Other Devices, Kindle appears as Tate-PVT-08, updating that "driver" is no use, and here I am Kindle-less once again. This is like a nightmare. Had I caused this issue by flashing a rom, or second bootloader, I'd probably give up and say "oh well I read the warnings, went along and I messed it up." But the case is that I did nothing to cause this, it only ran out of battery which happened once before and that time there were no issues starting up. I've searched left and right, high and low but cant find a way to now get this thing detected so I can see what I can do next. Can anyone please give me a list of what to do to get out of this Kindle Fire logo?
Since you can go to fastboot.
I suggest you check if you have the fastboot drivers installed since you said that you see the <waiting for device>. After that use the KFHD SRT
Sent from my air conditioner unit running CyanogenMod
dugoy13 said:
Since you can go to fastboot.
I suggest you check if you have the fastboot drivers installed since you said that you see the <waiting for device>. After that use the KFHD SRT
Sent from my air conditioner unit running CyanogenMod
Click to expand...
Click to collapse
Yeah I tried searching for drivers for it and I can't find them. I found one Chinese/Japanese website mentioning updating the driver by using the "android_winusb.inf" found inside sdk > extras > google > usb_driver, but when I try updating it with that file edited as they described, all I get is an error mentioning that the driver WAS found, but is likely corrupt or the victim of tampering. (which technically I did tamper with it by adding the lines I was told to add to the file from the following website)
http://translate.google.com/translate?hl=en&sl=ja&u=http://ameblo.jp/conpe/entry-11437514328.html&prev=/search%3Fq%3DTate-PVT-08%26biw%3D1366%26bih%3D673
Is there any specific place/thread with the drivers to the fastboot?
If you installed the Kindle Fire adb drivers,
Boot the kindle to fastboot mode and plug it in your PC
Then go to device manager, you will see a name called kindle with a yellow triangle beside it. After that right click on it and press "Update Device Drivers", then click "Let me pick", then click "browse installed drivers" then find the name Kindle Fire in the list and press next. You should see two things, Android ADB Interface and Android Composite ADB Interface. Click the Android Composite ADB Interface and press install/next. After that the drivers should be installed
Sent from my air conditioner unit running CyanogenMod
Possibly Solved
Crossvxm said:
Yeah I tried searching for drivers for it and I can't find them. I found one Chinese/Japanese website mentioning updating the driver by using the "android_winusb.inf" found inside sdk > extras > google > usb_driver, but when I try updating it with that file edited as they described, all I get is an error mentioning that the driver WAS found, but is likely corrupt or the victim of tampering. (which technically I did tamper with it by adding the lines I was told to add to the file from the following website)
Is there any specific place/thread with the drivers to the fastboot?
Click to expand...
Click to collapse
Solutions
1. What root tool did you use? A: if it was bin4ry type in notepad 0x1949 and save it to .android under users/Your User/.android
Like for me it would be users/chris/.android and you would save it to .android dir. if you dont have an .android dir. make one. Then see if your device is reconized as android composite adb device or at least kindle. Also try installing drivers for the kindle and uninstall the drivers and reinstalling them
2. I had a similar problem i rooted my kfhd and it became so slow it wouldnt turn on eventully after 30min. it turned on but was so slow when i sided to unlock it took five minutes. I also i tried rerooting without unroot. it worked so i used binary's root like i was unrooted and my kindle was back again. it turned out when i rooted i only had 50% battery and you NEED to have at least 90%. this also fixed any audio issues.
3. your original kf cord that came when shipped maybe shot and you may need a new one if it wont charge like someone else said "android devices need at least 20% battery to turn on". i dont find this to be true i need at least 5% but find a new cord and charge it seee if it works then.
4. if it turns on the the kindle fire logo flashes quicker then you can boot into recovery. the recovery screen should be a red warning sign saying reboot or restore click restore.
5. with a home made factory cord try booting into recovery mode and follow solution (4).
6. what root apps did you have on the device fire flash? A: fire flash will not work with the new 7.4.1 ota update
Let me know from there if you get your kindle working if no i can supply more solutions based on your answers and the reactions from my solutions.
I can also supply drivers and root tools
CVanB said:
Solutions
1. What root tool did you use? A: if it was bin4ry type in notepad 0x1949 and save it to .android under users/Your User/.android
Like for me it would be users/chris/.android and you would save it to .android dir. if you dont have an .android dir. make one. Then see if your device is reconized as android composite adb device or at least kindle. Also try installing drivers for the kindle and uninstall the drivers and reinstalling them
2. I had a similar problem i rooted my kfhd and it became so slow it wouldnt turn on eventully after 30min. it turned on but was so slow when i sided to unlock it took five minutes. I also i tried rerooting without unroot. it worked so i used binary's root like i was unrooted and my kindle was back again. it turned out when i rooted i only had 50% battery and you NEED to have at least 90%. this also fixed any audio issues.
3. your original kf cord that came when shipped maybe shot and you may need a new one if it wont charge like someone else said "android devices need at least 20% battery to turn on". i dont find this to be true i need at least 5% but find a new cord and charge it seee if it works then.
4. if it turns on the the kindle fire logo flashes quicker then you can boot into recovery. the recovery screen should be a red warning sign saying reboot or restore click restore.
5. with a home made factory cord try booting into recovery mode and follow solution (4).
6. what root apps did you have on the device fire flash? A: fire flash will not work with the new 7.4.1 ota update
Let me know from there if you get your kindle working if no i can supply more solutions based on your answers and the reactions from my solutions.
I can also supply drivers and root tools
Click to expand...
Click to collapse
Yeah I used "Root_with_Restore_by_Bin4ry_v26." The .android folder has adb_usb.ini and inside it is named "0x1949" although I'm no sure sometimes I check it and it comes with extra words like "do not edit this" and extra numbers. I'm guessing maybe SDK did it? But it was fine, its battery just died, then the thing won't come on no matter how much I put it to charge. I don't have that original cable, as this was given to my by a friend who no longer needed it.
When I put the device into fastboot, that's where I'm stuck. I see it stays on the fastboot logo, but no matter how many times I connect it to any USB, my computer does detect it as a device being connected, but ADB or any other related software always says (waiting for device) and I cant make any moves.In the device manager, its neither Kindle, or Android ADB Interface, just Tate-PVT-08.
I will try to uninstall and reinstall things just to make sure
An other option
Crossvxm said:
Yeah I used "Root_with_Restore_by_Bin4ry_v26." The .android folder has adb_usb.ini and inside it is named "0x1949" although I'm no sure sometimes I check it and it comes with extra words like "do not edit this" and extra numbers. I'm guessing maybe SDK did it? But it was fine, its battery just died, then the thing won't come on no matter how much I put it to charge. I don't have that original cable, as this was given to my by a friend who no longer needed it.
When I put the device into fastboot, that's where I'm stuck. I see it stays on the fastboot logo, but no matter how many times I connect it to any USB, my computer does detect it as a device being connected, but ADB or any other related software always says (waiting for device) and I cant make any moves.In the device manager, its neither Kindle, or Android ADB Interface, just Tate-PVT-08.
I will try to uninstall and reinstall things just to make sure
Click to expand...
Click to collapse
1. Also, ive heard this but it could be the case
The usb your using for fastboot could be using the name of an other device that was used for charging or connecting to the computer. Try connecting the other device to the usb and eject it properly then connect the kindle.
2. also using a fastboot cable that is specifed for the kindle could help.
3. the one thing i dont understand is the kindle isnt bricked so the firmware must be corrupted possibly because of the ota update to 7.4.1 in other words you rooted durring the ota update or tried to use superuser during an update.
4. also the last time you turned it on fully did it say updating kindle or anything like that. lastly you could have lost power when the update was installling or was about to install this could corrupt the data.
CVanB said:
1. Also, ive heard this but it could be the case
The usb your using for fastboot could be using the name of an other device that was used for charging or connecting to the computer. Try connecting the other device to the usb and eject it properly then connect the kindle.
2. also using a fastboot cable that is specifed for the kindle could help.
3. the one thing i dont understand is the kindle isnt bricked so the firmware must be corrupted possibly because of the ota update to 7.4.1 in other words you rooted durring the ota update or tried to use superuser during an update.
4. also the last time you turned it on fully did it say updating kindle or anything like that. lastly you could have lost power when the update was installling or was about to install this could corrupt the data.
Click to expand...
Click to collapse
It updated randomly from 7.3.1 to 7.4.1 on May 30th (aprox 5 days ago) that same day I rooted it after it erased my root with the same guide I used for 7.3.1 that was based on 7.4.1. It worked perfectly, but around that time I never let the battery die during those few days. In record, I've only let the battery die once before, this time makes it 2 times total. The cable I made is from a Samsung, I made it using instructions on making it for the Kindle Fire HD 7 specifically, although as I've heard, you may be right. But when I research that "device" (Tate-PVT-08) on google, the Kindle Fire pops up in search results, but none are really helpful. Example, the bottom of this thread I'm posting below, people have similar issues and the "Tate" thing:
http://forum.xda-developers.com/showthread.php?t=1930656
Same problem
I´m noob, certainly, but I spend many hours searching and reading (dealing with the problem that english is not my native language as you could see) but I think I have a similar problem as the described here with the difference that my battery was ever up 50 - 55%. I have post a threat a few days ago where I think it would be pertinent and I´m waiting for a response.
My big problem (I think) is that I have ADB disabled on my KFHD as I post here: http://forum.xda-developers.com/showthread.php?t=2308788 I´m now trying Seokhun guide but I´can´t make it for this reason.
Thanks for any idea.
dugoy13 said:
If you installed the Kindle Fire adb drivers,
Boot the kindle to fastboot mode and plug it in your PC
Then go to device manager, you will see a name called kindle with a yellow triangle beside it. After that right click on it and press "Update Device Drivers", then click "Let me pick", then click "browse installed drivers" then find the name Kindle Fire in the list and press next. You should see two things, Android ADB Interface and Android Composite ADB Interface. Click the Android Composite ADB Interface and press install/next. After that the drivers should be installed
Sent from my air conditioner unit running CyanogenMod
Click to expand...
Click to collapse
Crossvxm, did you ever try what dugoy said, that should work for getting your device recognized?
---------- Post added at 10:03 PM ---------- Previous post was at 09:45 PM ----------
Elgari said:
I´m noob, certainly, but I spend many hours searching and reading (dealing with the problem that english is not my native language as you could see) but I think I have a similar problem as the described here with the difference that my battery was ever up 50 - 55%. I have post a threat a few days ago where I think it would be pertinent and I´m waiting for a response.
My big problem (I think) is that I have ADB disabled on my KFHD as I post here: http://forum.xda-developers.com/showthread.php?t=2308788 I´m now trying Seokhun guide but I´can´t make it for this reason.
Thanks for any idea.
Click to expand...
Click to collapse
Elgari, if I get your situation correctly, you won't be able to use adb. Adb can only be used when you're in recovery or when you're booted. You'll have to go with fast boot. If you can get into fast boot, then you can use the kindle SRT tool from the development thread. Do you have a factory cable?
DroidIt! said:
Crossvxm, did you ever try what dugoy said, that should work for getting your device recognized?
---------- Post added at 10:03 PM ---------- Previous post was at 09:45 PM ----------
Elgari, if I get your situation correctly, you won't be able to use adb. Adb can only be used when you're in recovery or when you're booted. You'll have to go with fast boot. If you can get into fast boot, then you can use the kindle SRT tool from the development thread. Do you have a factory cable?
Click to expand...
Click to collapse
Yeah I tried that and even my own little invention. But I give up. I'm just scrapping the whole project. Its useless, I'll just have to get me a Nexus 7, I don't want to get stuck with another brick. Amazon is pretty ridiculous. Their system is unstable, their device is crap. I have read about problems like this on these things everywhere. Whether its the charging refusal, 0% battery, not starting up, not having Google Play, root headaches and nearly impossible restore scheme, these things are well worth their cheap price.
Shame for you to scrap it, thought I'd throw in my two cents. I've never put mine in fast boot so I don't know if it supposed to show up as Tate in the task manager but I do know if you run fast boot with the get var product it should report something back as Tate so I assume that what you see is good, thing I'd like to ask is did the drivers install for Tate, and if not can u tell me in the tates properties what its hardware id's are? I think you probably need to mod the driver, or you said you did but I don't know if you installed it, usually u have to have a unsigned driver, and I think if it gives u trouble about not letting you install it because its been tampered with you just have to delete or rename the cat file in the directory the drivers are in, then it will just say they are unsigned and prompt you to install them anyways. If you happen to be on windows 8 this probably will get more complicated, because u have to boot up in a special mode to install unsigned drivers
Sent from my Amazon Kindle Fire HD using xda app-developers app
stunts513 said:
Shame for you to scrap it, thought I'd throw in my two cents. I've never put mine in fast boot so I don't know if it supposed to show up as Tate in the task manager but I do know if you run fast boot with the get var product it should report something back as Tate so I assume that what you see is good, thing I'd like to ask is did the drivers install for Tate, and if not can u tell me in the tates properties what its hardware id's are? I think you probably need to mod the driver, or you said you did but I don't know if you installed it, usually u have to have a unsigned driver, and I think if it gives u trouble about not letting you install it because its been tampered with you just have to delete or rename the cat file in the directory the drivers are in, then it will just say they are unsigned and prompt you to install them anyways. If you happen to be on windows 8 this probably will get more complicated, because u have to boot up in a special mode to install unsigned drivers
Sent from my Amazon Kindle Fire HD using xda app-developers app
Click to expand...
Click to collapse
Thanks for trying. But if you'd see what I did to the poor thing out of frustration you'd call me nuts. Its really not coming back now...
Related
Alright, so I've seen alot of posts asking about a root for the kindle fire 2
We've had multiple members use this method and it seems to work absolutley fine.
Follow the steps in this thread to gain root,
http://forum.xda-developers.com/showthread.php?t=1893838
I was able to gain root while running ver 10.1.3 and I've seen many other members also able to do the same.
To use a launcher download the apk of the launcher you want to use, after installing move the apk file to your "app" folder found in the "system" file and change permissions for that apk to user - rw ; group - r ; other - r. Once those steps are done simply reboot your kindle and a prompt will appear asking which launcher to use.
Credits to the respective thread starters and to bodi524 for sharing the info with me.
[ list of recommended launchers ]
-Go launcher ( EX or HD )
-chameleon launcher
-lightning launcher
-nova launcher
there are a ton more to check out, just look around.
Dassen said:
Alright, so I've seen alot of posts asking about a root for the kindle fire 2
We've had multiple members use this method and it seems to work absolutley fine.
Fopllow the steps in this thread to gain root,
http://forum.xda-developers.com/showthread.php?t=1893838
I was able to gain root while running ver 10.1.3 and I've seen many other members also able to do the same.
Click to expand...
Click to collapse
Huh. I can't get the .bat to recognize the device, despite installing the drivers and enabling ADB on the Kindle. However, when I do install the drivers, the installer looks like they install properly, yet I get a dialog that says "Drivers not installed successfully. Install manually." Or something to that effect. Thoughts?
Got the same error , I just tried re installing the drivers a couple of times and it worked, I actually got an error message while installing the drivers once that read drivers installed unsuccessfully then tried to run the bat for the luls and that's when the root worked. xD
I dont really know what the deal is with the drivers but it seems like they arent that important... try re-installing them a couple times see if that helps.
Spent too much time on it. Reverted back by the end!!
Help Me Please. I root KindleFire 2 gen
i root my Kindle Fire (2nd Generation) Software Version 10.1.3 by How to root tool Qemu http://forum.xda-developers.com/showthread.php?t=1893838
but i can't copy file .apk to folder /system/app and program Root Explorer show detail /dev/block/platform/omap/omap_hsmmc.1/by-name/System (r/o) and don't have Remount as R/W button
help me please.
Can any one give a more detailed guide on how to move the .apk and change the settings to get it to work??
Would be greatly appreciated thanks!
Sent from my KF2 using xda app-developers app
Now that's ****ing great.
I tried rooting it a couple times without success. It always came down to the 5073 port error and after too many restarts it is increadibly slow plus the kindle fire logo is flickering on the screen every few seconds...
Edit:
OK after painfully managing to finally get to the "reset factory settings" it is working again. But I think this root method might not be working for me with Version 10.2.1
Root Kindle Fire 2 v10.2.1
Hi, I tried using [ROOT][TOOL]Qemu automated root [09/18/2012] Got the drivers installed succesfully and then ran the bat file but does not seem to work. My kindle fire 2 version is v10.2.1 anyone had success with this one yet?
Never mind I tried with a Samsung USB cable and it worked.
I have mine rooted on 10.2.1 and running go luncher ex
Sent from my KF2 using xda app-developers app
Is it possible, that Windows 8 64bit might be an issue? Installing the drivers was only possible after renaming the signed drivers by deleting the "signed_" part. the bat installer only recognizes the device after repluging it a couple times. Then I get a cmd line saying "root or "shell" but putting in the stuff from the video doesn't work.
Rooted Kindle Fire 2 fine....but
The root process went perfectly clean and it rebooted fine. Then I couldn't find instructions to install the Play Store. I finally found some that said to copy GoogleServicesFramework.apk to the Kindle and install, I did that cleanly. Then to copy vending.apk to /system/app/ and I did that and was able to change permissions to 664. I then rebooted the Kindle. It goes straight to the triangle. If you push the power button 5 times it reboots to the same thing. I did not try to flash TWRP to it because I saw some having problems with it. I have 10.2.1 on it. I have the proper drivers installed and each time the Kindle rebooted during boot the computer beeped that it recognized it. Since the triangle the PC no longer recognizes it, it does not show up in Device manager and it does not show up in explorer as connected. I think it is hard bricked but wanted to run it by everyone.
Sparkym3's root process went flawlessly on my Fire2, It only took a couple minutes to root and be booted to a working Kindle. I just screwed up the market process somehow.
Let me know your thoughts. Being that everything went so clean with rooting I have a hard time thinking it can be the drivers, cable, usb port.
I've rooted a phone and 2 tablets multiple times but never had this happen. Any help is greatly appreciated.
This is an exact description of the problem:
I get the Kindle Fire logo, sits there several seconds, reboots and the power light goes out and back on, then the logo comes up again, it flashes a couple of times then I get an orange triangle with an exclamation point inside Below that is a message stating "Your Kindle device cannot boot".
Below that is You can reset device to Factory defaults to fix this issue (all data will be deleted from the device"
<Menu options>
To reboot your device, press and hold the power button for 4 seconds and release.
To reset to Factory Defaults, press the power button 5 times in succession.
Well the 4 second thing does not work at all, more like 20 seconds. The pressing 5 times just reboots to the same problem and warning triangle. I tried fastboot commands but nothing.and my laptop no longer recognizes the Kindle and nothing is in Device Manager about the Kindle now. The fastboot command just says waiting for device. As I said above the root process went flawlessly and the Fire reboot 3-4 times and the laptop beeped each time that it saw it.
Any help is greatly appreciated
So, I'm totally lost. Maybe a frisbee at this point.
Hi
I rooted my KF and install GO Launcher with method that was discribed in first post. But this method is usless to install Google Play. How can I install GP? (Sorry for my English)
wmccombs said:
The root process went perfectly clean and it rebooted fine. Then I couldn't find instructions to install the Play Store. I finally found some that said to copy GoogleServicesFramework.apk to the Kindle and install, I did that cleanly. Then to copy vending.apk to /system/app/ and I did that and was able to change permissions to 664. I then rebooted the Kindle. It goes straight to the triangle. If you push the power button 5 times it reboots to the same thing. I did not try to flash TWRP to it because I saw some having problems with it. I have 10.2.1 on it. I have the proper drivers installed and each time the Kindle rebooted during boot the computer beeped that it recognized it. Since the triangle the PC no longer recognizes it, it does not show up in Device manager and it does not show up in explorer as connected. I think it is hard bricked but wanted to run it by everyone.
Sparkym3's root process went flawlessly on my Fire2, It only took a couple minutes to root and be booted to a working Kindle. I just screwed up the market process somehow.
Let me know your thoughts. Being that everything went so clean with rooting I have a hard time thinking it can be the drivers, cable, usb port.
I've rooted a phone and 2 tablets multiple times but never had this happen. Any help is greatly appreciated.
This is an exact description of the problem:
I get the Kindle Fire logo, sits there several seconds, reboots and the power light goes out and back on, then the logo comes up again, it flashes a couple of times then I get an orange triangle with an exclamation point inside Below that is a message stating "Your Kindle device cannot boot".
Below that is You can reset device to Factory defaults to fix this issue (all data will be deleted from the device"
<Menu options>
To reboot your device, press and hold the power button for 4 seconds and release.
To reset to Factory Defaults, press the power button 5 times in succession.
Well the 4 second thing does not work at all, more like 20 seconds. The pressing 5 times just reboots to the same problem and warning triangle. I tried fastboot commands but nothing.and my laptop no longer recognizes the Kindle and nothing is in Device Manager about the Kindle now. The fastboot command just says waiting for device. As I said above the root process went flawlessly and the Fire reboot 3-4 times and the laptop beeped each time that it saw it.
Any help is greatly appreciated
So, I'm totally lost. Maybe a frisbee at this point.
Click to expand...
Click to collapse
So here's my wild ass guess (WAG). The fastboot "waiting for device" thing happened to me as well with my Fire (not a 2). My fix was getting root installed and getting it into fastboot mode on one computer then doing the fastboot commands and getting it out of fastboot on another computer.
I've seen posts where people get adb working and copy files with it, then issue a fastboot command, reboot the Kindle then fastboot can't see it anymore.
My WAG is somehow the USB drivers are confused by seeing a similar device but it's different enough for the driver to fail. The solution I've seen given to people on Windows is to uninstall and re-install the Fire USB drivers (I'm on Linux, so my solution was to install fastboot on my Powerbook and send the fastboot commands from it since it saw the device when Linux fastboot wouldn't).
These are probably just the rantings of a raving lunatic, but try to find another computer and see if you can run fastboot commands and get it out of fastboot.
Dassen said:
Got the same error , I just tried re installing the drivers a couple of times and it worked, I actually got an error message while installing the drivers once that read drivers installed unsuccessfully then tried to run the bat for the luls and that's when the root worked. xD
I dont really know what the deal is with the drivers but it seems like they arent that important... try re-installing them a couple times see if that helps.
Click to expand...
Click to collapse
Sounds like you did the same thing as me. It's bugging me because I don't know EXACTLY what I did to finally get root access, I just know it worked! I had to reinstall drivers a couple of times and run the q program until it showed 'rooted'. Whatever I did, it worked and it's fun to mess with!
Kindle Fire 2
I haven't tried rooting mine yet, and with the way this thread has gone back-and-forth, I'm kinda afraid to.
As far as I can tell, there has been a lot of success on 10.1.3 and 10.2.4 using various tools.
Is there a definitive way to root 10.2.4 or do I just need to mess around with drivers and hope for the best?
Is there a way to get gapps (google play, gmail, etc.) on there safely?
I'll post again (or edit) when I get mine rooted but I'm going to hold off on getting gapps or other ROM's on it until those with better programming and troubleshooting abilities than I have a chance to figure it out.
Click to expand...
Click to collapse
EDIT:
I was able to root my KFOT 10.2.4 and got Google Play, Calendar, and Gmail to work. Got ADW launcher to replace the default.
So, about a week ago, Amazon pushed an update that took my software to 10.2.6, which removed my root access and set my launcher back to their default.
The last root method that worked for me I found here.
My question is, will that method still work? (I assume it still works on the HD as well...)
On a side note, has the bootloader for KFOT been cracked yet? I'd like to get another ROM on it so I can use ICS in its full glory (if possible)
:good:
-skpacman
root it
The quickest & easiest way to root a Kindle Fire 2nd gen (non-HD/HDX) firmware 10.3.1 - 10.4.6 (if your's is lower, upgrade) ... available here :
staticchaos.freeoda.com/fire/
Hi, I have 2 bricked KFHD's 7" after trying to Root them, I have just received my SKORPN Factory Cable, followed the instructions as sent by the man himself and nothing, any ideas????? I was under the impression that the battery does not need to be charged and that connection would put the Kindles into Fastboot to allow me to flash the devices, I am at a loss as to what to do, i know my ADB drivers are installed correctly as it shows in Device Manager on my PC when I connect my wifes' KFHD.
Please Help - failing my efforts does anyone know of anyone who repairs these devices?
FatedBoot said:
Hi, I have 2 bricked KFHD's 7" after trying to Root them, I have just received my SKORPN Factory Cable, followed the instructions as sent by the man himself and nothing, any ideas????? I was under the impression that the battery does not need to be charged and that connection would put the Kindles into Fastboot to allow me to flash the devices, I am at a loss as to what to do, i know my ADB drivers are installed correctly as it shows in Device Manager on my PC when I connect my wifes' KFHD.
Please Help - failing my efforts does anyone know of anyone who repairs these devices?
Click to expand...
Click to collapse
Other than "bricked", what state are the devices in? Better yet...What were the instructions that Skorpn gave you?
Both Kindles are totally unresponsive, have tried previous Factory cables but no use. I bought the SKORPN cable as it has such good reviews and the instructions are as follows, sent with the cable;
1) Turn OFF the Kindle Fire and wait 30 seconds or so, (mine don't even turn on so no problem there).
2) First, plug the USB Micro-B end into the Kindle Fire.
3) Then plug the standard Type-A end into the computer.
4) Profit...
Exactly as typed on the accompanying paperwork.
FatedBoot said:
Both Kindles are totally unresponsive
Click to expand...
Click to collapse
Totally unresponsive, how? Unresponsive as in...there is nothing on the display and nothing happens when you press the power button? Do you mean that kind of "totally unresponsive"?
Exactly that, nothing happens with the power button pressed, nothing on the screen
Your device is lost, unfortunately. What exactly did you do to it before this happened?
Just tried rooting them, all seemed to be going well until the reboot process and they never turned on again - never mind, off to the bin they go - cheers for your help
FatedBoot said:
Just tried rooting them, all seemed to be going well until the reboot process and they never turned on again - never mind, off to the bin they go - cheers for your help
Click to expand...
Click to collapse
Yet another "Kindle fire utility" Victim!
I'll assume you used kindle fire utility since this is the only tool that tries to install a 2nd bootloader along with root (flashing the wrong bootloader is the only thing that causes a device to not even power up), What you need to do now is contact amazon and send it back to them they'll most likely give you a replacement!
Or you can send it to prokennexusa At
Xerocomm, Inc
Attn: Chris Bryant
1684 Northstar Drive
Petaluma, CA 94954
He'll fix it for you and you can always thank him by giving him a small donation!
*My KFHD7 will not load passed the initial, "kindle fire" logo.
*While running KFFirstAide64 runme.bat, it reads, "The system cannot find the path specified" after I try the recovery.
*In Device Manager under other devices it states, "Soho-PVT-Prod-07"; My computer is communicating with the Kindle.
*I am using a factory (fastboot) cable and my tablet is in fastboot mode as of right now.
*Last updated version known: 11.2.3.2
Is there any other program or recovery option that I can use to restore my KFHD7 to it's factory conditions? How can I get the system to "find the path specified"?
Solution!
I don't know how I missed it but here it is.
http://forum.xda-developers.com/showthread.php?t=1951254
Additional Problems...
When I run the program to recover, it reads, "<waiting for device>".
*I am using "KFHD_SRTv1.3.5" SR Tool which was recommended to me.
*I've tried using different USB ports.
*Waiting for the device proves to be pointless.
*I have downloaded the ADB driver but installing it shows no improvements.
What can I do?
That is for the Kindle fire HD 2012 edition. If you flash it to your Kindle you will Brick it.
You need this program.
http://dl.kfsowi.com/tools/kindlesuite/KindleSuite.zip
Thanks for the reply
Red_81 said:
You need this program.
Click to expand...
Click to collapse
I have downloaded the program and tried to restore my device but I ran into the same problem, "waiting for device". I've installed the device drivers as well. I checked on one of the other programs my ADB status and it is not on. I don't believe I can turn it on without getting passed the initial bootlogo.
Do I need the ADB enabled in order for a full recovery? How can I get my device to be acknowledged by this program when my computer is reading that it's there?
EDIT:
I need to restore my kindle.
While in fastboot mode, the logo has 3D orange font that says "fastboot" with a black background. There is nothing else that shows up. Before I tried to root there was green font in I think the top left corner; looked like a cmd prompt was running something (if I recall correctly)..
if you are in fast boot and stuck waiting for device you are probably having a driver problem like I had. I used fastboot on Linux instead of Windows and solved my driver issue that way.
Sent from my SCH-I535 using XDA Premium 4 mobile app
muiriddin said:
I used fastboot on Linux instead of Windows and solved my driver issue that way.
Click to expand...
Click to collapse
Sorry for the late reply. I'll try out Linux OS and see what happens. I'll let ya'll know the news :fingers-crossed:
EDIT::
So my computer crashed trying to fix my kindle; hard drive malfunction of some sort. My friend put the hard drive into his computer and it erased his BIOS. We then put in an 80GB hard drive that we got for $10, re-installed windows and tried again. Hard drive crashed crashed again. Maybe when I tried to install the drivers they were installed onto my computer instead of the Kindle?
This is an on going process but I probably won't be posting again any time soon. Maybe when I actually start programming things will be a little more self explanatory.
Thanks for all your help. This is all for this thread.
My audio stopped working randomly, which it has been doing. I figured, "no problem, I can just get a factory reset."
I rooted my kindle and used Stunts' Wallpaper Fix, so when I factory reset the Stunts Wallpaper Fix and the Root were gone, but the notification bar went in and out. After hours of frustration, I decided I'd just download CM11 because I was getting tired of the way the notification bar going funky.
I followed all of the steps of the TWRP + 2nd Bootloader Thread but it was via another source, and I forgot to add the CM11 to the Kindle and wiped OS.
Now my Kindle Fire is stuck on the blue logo, it's not responding computer wise, I've probably downloaded the Android SDK, Google USB Driver, kindle ADB drivers and Fastboot drivers about 10 million times and my kindle can recognize fastboot, the computer will not.
Kinda stuck, don't know what to do, and I'm not trying to hardbrick this. Any ideas? :crying: I've been working on this for about 5 days now and my fastboot cable came in today (i had another for when i bricked it the first time, but it's lost.) so i tried working with it for about 3 hours but my frustration is getting the best of me and the Kindle's battery life is getting the best of it.
I fixed it! I fixed my baby~! About 5-6 days later and I finally got it to work!
I'm going to assume if you bricked your kindle that hard, then you should have had a Kindle Fire driver previously, this is necessary! Do not let this be a first time install!
Here's what I did!
I deleted my drivers for Kindle.
The first step is getting your Kindle recognized. Make sure you download the android SDK (you need ADB and Fastboot)
I found a good program for that, search up "15 second ADB installer" or something like that.
Once installed, remember where your driver is (or go to Start search and search up "Amazon.com.")
Plug in your fastboot cable (if you have one) or your normal cable.
Go to Device Manager (accessible in Start search) and look for Tate-VT-08 or something like that, it's under "Other Drivers" and it won't show up unless you've wiped out your drivers.
Right click it until you can update your driver, and then look for list of previous drivers. Look for "Kindle Fire" (it's there if you've plugged in your kindle before)
Click it
and you are now recognized fastboot wise! Go girl/boy!
Next, download KF SRT (Kindle fire system recovery tool) and do option 3 because I did both options 1 and 2 and it bootlooped mine so I had to start this process all over.
You're now at factory settings for 7.3.0. Wait until it naturally updates (it will) and you should be good to continue tinkering around.
Lesson learned: Always ALWAYS read the directions carefully, and don't get too ahead of yourself! :highfive:
Introduction
This tool is for returning the Kindle Fire back to stock automatically. This is for Windows ONLY. If you can spare about 1 GB on your hard drive, you're good to go.
Code:
Disclaimer:
By using this tool, you accept that you're taking full responsibility if anything bad happens.
Blame any of us (me, XDA Devs, etc) and I'll ask you to read the licence agreement slowly &
carefully.
You have been warned.
Requirements
A fastboot/factory cable (They can go for as cheap as $2)
A Kindle Fire 2
ADB and Fastboot drivers
A PC running Windows
Time
Download
Installer
Google Drive: Installer
MediaFire: Installer
Zip & & 7z files
MEGA
ZIP format
7z format
Google Drive
7z format
Rootjunky's DL Server (thanks Tomsgt.)
ZIP format
Android File Host
ZIP format
NOTICE: I am not developing this anymore. If any download links go down, I will not be able to help. Sorry. ¯\_(ツ)_/¯
Does this work? Has anyone tried it?
Please help!!! MODS PLEASE READ !!!!
Ok Ive tried searching and Ive tried everything on this site, I have a Kindle Gen 2 I can get into Fastboot but everything else was deleted off the Kindle, EVERYTHING !!! I just want to restore it for my daughter to use in the car Windows 10 does not reconize it but it shows up in device manager as OTTER2 with no drivers when i plug it in with fastboot cable. anyone who can point me in a direction please help.
Bwangster12 said:
Does this work? Has anyone tried it?
Click to expand...
Click to collapse
I know I'm over a year late in this reply, but I accidentally bricked my Kindle with the red triangle screen, but didn't have a fastboot cable, so I ordered a cheap one on Amazon which arrived an hour ago. Immediately I took it to my computer, plugged in my powered off Kindle, and it went straight into fastboot mode. I opened disaster recovery from this thread ran it with the fastboot cable plugged in, swapped for a regular cable on the step it tells you to, did the factory reset it told me to do, and sure enough my KF2 is back in the state it was fresh out of the box. I'm mostly just going to be using it for my e-books and audible purchases, but it's nice to have it working again. Going to try installing the prime video app on it since on stock it will try to use silk+flash for prime video and I'm not sure that will even work anymore. If it does, cool, but if not I should be able to install the apk for prime video as a user app without having to dig up old root methods by using the internet archive on dead links.
---------- Post added at 05:42 PM ---------- Previous post was at 05:35 PM ----------
Panettaone said:
Ok Ive tried searching and Ive tried everything on this site, I have a Kindle Gen 2 I can get into Fastboot but everything else was deleted off the Kindle, EVERYTHING !!! I just want to restore it for my daughter to use in the car Windows 10 does not reconize it but it shows up in device manager as OTTER2 with no drivers when i plug it in with fastboot cable. anyone who can point me in a direction please help.
Click to expand...
Click to collapse
Don't know what to tell you, my dude. Worked fine with Windows 10 for me with a fastboot cable. Might have to manually download the drivers if you haven't already, but my computer straight up recognized it.
Do you have any USB2.0 ports available? I find that with older devices, 2.0 is the way to go and 3.x tends to either not detect the device or causes errors during critical data transfers.
This tool, when you get your Kindle detected, will fix exactly your problem. I'd say try right clicking the .bat file, go to properties, then in the compatibility tab make sure it's running as administrator. That insures the fastboot and adb processes will have the proper permissions to write to the Kindle. Might even work now even with it coming up as OTTER2.
Panettaone said:
Ok Ive tried searching and Ive tried everything on this site, I have a Kindle Gen 2 I can get into Fastboot but everything else was deleted off the Kindle, EVERYTHING !!! I just want to restore it for my daughter to use in the car Windows 10 does not reconize it but it shows up in device manager as OTTER2 with no drivers when i plug it in with fastboot cable. anyone who can point me in a direction please help.
Click to expand...
Click to collapse
Had this problem just now actually! I went and grabbed the official driver files from amazon and installed them (can't link since I'm a new user but you'll find it if you search "Kindle Fire ADB Drivers").
Then I clicked on the device otter2-prod4 in device manager and manually assigned it to Amazon ADB Device and that solved the issue for me.
It's now discoverable via fastboot and I'm running this recovery script right now!