I hope someone here can help me, I tried updating my kindle to the official 6.3 update and now Im stuck at recovery, KFU wont recognize my device to change the boot mode. I dont know how to recover my device. Please, help me.
use kfu option1 - bootmode normal (anyway)
or manually:
adb shell idme bootmode 4000
adb reboot
or:
fastboot oem idme bootmode 4000
fastboot reboot
if it says <waiting for device> power it off by holding the pwr button for ~20sec till it turns of - pwr on again - the command should resume and finish
a second pwr off/on will bring you back to normal
if none is working check your drivers:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
Ok....
b63 said:
use kfu option1 - bootmode normal (anyway)
or manually:
adb shell idme bootmode 4000
adb reboot
or:
fastboot oem idme bootmode 4000
fastboot reboot
if it says <waiting for device> power it off by holding the pwr button for ~20sec till it turns of - pwr on again - the command should resume and finish
a second pwr off/on will bring you back to normal
if none is working check your drivers:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
Click to expand...
Click to collapse
KFU recognized my device but when I try to use option1 for normal boot it say "The system cannot find the drive specified" and nothing more. still stuck.
and the manual commands ?
driver status in device manger ?
info
b63 said:
and the manual commands ?
driver status in device manger ?
Click to expand...
Click to collapse
with the manual commands, I dont know if doing it correctly, cmd says "adb is not recognized as an internal or external command, operable program or batch file".
and driver status is device manager says, "Android Composite ADB interface" - "device is working properly"
when I launch KFU it says
ADB Status: Online
Bootmode: 5001
J_RosarioX2 said:
with the manual commands, I dont know if doing it correctly, cmd says "adb is not recognized as an internal or external command, operable program or batch file".
and driver status is device manager says, "Android Composite ADB interface" - "device is working properly"
when I launch KFU it says
ADB Status: Online
Bootmode: 5001
Click to expand...
Click to collapse
driver seems fine - kfu seems fine
the message about "cannot find the drive specified" is disturbing
did you move kfu to c:\ and rename it that it is c:\kfu ?
because kfu don't like spaces in pathname
then option 1 bootmode normal should work
tried...
b63 said:
driver seems fine - kfu seems fine
the message about "cannot find the drive specified" is disturbing
did you move kfu to c:\ and rename it that it is c:\kfu ?
because kfu don't like spaces in pathname
then option 1 bootmode normal should work
Click to expand...
Click to collapse
I tried that, still no response, I was using the latest KFU version and now I switched to the previous version (the one I originally used to root my device) and it says
ADB Status: Online
ADB Rooted: Yes
Boot Status: 5001
I tried using the first option in the bootmode menu but it does nothing I just get the message "Activating Normal (4000)" on the header but then nothing happens.
It just stays there doing nothing...
any further ideas?
would try power off the kf by holding pwr ~20sec till it turns off
then disconnect and reconnect - it should power up by itself - retry kfu
if it don't work - same as above till diconnect
then power down the computer and power on again (no restart)
and reconnect the kf - retry kfu
(because sometimes windows thinks it is still connected)
b63 said:
would try power off the kf by holding pwr ~20sec till it turns off
then disconnect and reconnect - it should power up by itself - retry kfu
if it don't work - same as above till diconnect
then power down the computer and power on again (no restart)
and reconnect the kf - retry kfu
(because sometimes windows thinks it is still connected)
Click to expand...
Click to collapse
ok, I'll try that tonight as soon as I get home, im going to work right now, I'll post what happens. thanks for ur help.
Sent from my HTC HD2 using xda premium
No
b63 said:
would try power off the kf by holding pwr ~20sec till it turns off
then disconnect and reconnect - it should power up by itself - retry kfu
if it don't work - same as above till diconnect
then power down the computer and power on again (no restart)
and reconnect the kf - retry kfu
(because sometimes windows thinks it is still connected)
Click to expand...
Click to collapse
I just tried that and It didnt work, I was wondering... Is there a way for me to flash a custom ROM on my kf using the PC, or to transfer the ROM to the KF through the Recovery menu (access device storage via recovery?) so that I can flash the ROM from TWRP?
to flash an other rom will not change the bootmode
here the manual way:
http://forum.xda-developers.com/attachment.php?attachmentid=943772&d=1331571368
Finally...
b63 said:
to flash an other rom will not change the bootmode
here the manual way:
http://forum.xda-developers.com/attachment.php?attachmentid=943772&d=1331571368
Click to expand...
Click to collapse
I just got my KF up and running with those manual commands, thanks again for your help.
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
Related
I just overall screwed up big time with this thing. I rooted 6.2.1, then uninstalled/froze a bunch of the stock apps (including the default Kindle launcher, as I had Go Launcher installed).
I then decided I wanted to restore to the factory default settings, as I wanted to use Amazon prime, among other things. I went into settings and hit the "restore to factory defaults button" (which was stupid, I know). Unsurprisingly, this resulted in Kindle Fire bootloops.
Trying to fix this, I used the KindleFireTool to install the most recent TWRP...which didn't work at all. It would just stay on the yellow triangle screen. Now, things have gotten even worse, though I don't know why. Whenever I plug the fire into the computer, it goes into TWRP bootloops!
For the brief few seconds that the Fire is on when plugged into my computer, the driver isn't recognized at all (shows up as "kindle" with a triangle next to it in device manager).
I know what I did was dumb, but even so, any help would be hugely appreciated.
YES YES YES!!!! OK HERES HOW I DID IT TO FIX THE BOOTLOOP OF TWRP
First you must download Kindle Fire Utility and extract it to your desktop
then go to command prompt or cmd then type in the location of the folder heres mine for example: C:\Users\Madaran\Desktop\Kindle Fire Utility\tools
then type in fastboot -i 0x1949 oem idme bootmode 4000
For me it said waiting for device all I did is rebooted the device and it worked
as the device reboot it will still go back to TWRP now type this in the command prompt
fastboot -i 0x1949 oem idme bootmode 4000
then it should reboot again and ITS FIXED
----------------------------------
I used this thread to fix it.
http://forum.xda-developers.com/showthread.php?t=1428715
Thank you so much! I'll post results when I get the opportunity.
Well it didn't work...the thing isn't connecting to the computer properly. I think it's a goner.
Mine didn't connect also but it still worked. You don't need the device to be connected just plug it in and put it in the TWRP recover mode. Then do the steps again.
1.Download Kindle Fire Utility
2.Extract it to desktop.
3.You can't connect it while its in FastBoot mode so open up CMD or Command Prompt.
4.Again locate the folder and type it in the CMD for example I typed:
"cd C:\Users\Madaran\Desktop\Kindle Fire Utility\tools"
5.Then type this in "fastboot -i 0x1949 oem idme bootmode 4000"
6.It should say waiting for device. Go to TWRP and hit reboot system.
7.It should work now and while waiting for your Kindle to boot up, the power button should be orange.
8.When it turned orange I immediately typed this in the CMD or Command Prompt
"fastboot -i 0x1949 oem idme bootmode 4000" so it wouldn't boot to the TWRP recovery menu.
9.It should reboot again and load up your CyanogenMod 7
10. If it work hit the thanks button please.
I did all of that up until step 6. My device won't allow me to reboot. When it's plugged in via USB, it boots up, dies within 20 seconds, then boots again. I can't break the cycle, and it just says waiting for device on and on...
skippwhy said:
I did all of that up until step 6. My device won't allow me to reboot. When it's plugged in via USB, it boots up, dies within 20 seconds, then boots again. I can't break the cycle, and it just says waiting for device on and on...
Click to expand...
Click to collapse
It maybe your battery its low. Try to charge it and connect it again.
Definitely worth a shot
You were right! It was a battery issue
sirmavs said:
Mine didn't connect also but it still worked. You don't need the device to be connected just plug it in and put it in the TWRP recover mode. Then do the steps again.
1.Download Kindle Fire Utility
2.Extract it to desktop.
3.You can't connect it while its in FastBoot mode so open up CMD or Command Prompt.
4.Again locate the folder and type it in the CMD for example I typed:
"cd C:\Users\Madaran\Desktop\Kindle Fire Utility\tools"
5.Then type this in "fastboot -i 0x1949 oem idme bootmode 4000"
6.It should say waiting for device. Go to TWRP and hit reboot system.
7.It should work now and while waiting for your Kindle to boot up, the power button should be orange.
8.When it turned orange I immediately typed this in the CMD or Command Prompt
"fastboot -i 0x1949 oem idme bootmode 4000" so it wouldn't boot to the TWRP recovery menu.
9.It should reboot again and load up your CyanogenMod 7
10. If it work hit the thanks button please.
Click to expand...
Click to collapse
Hey guys... I kinda bricked my Kindle... I tried all the steps mentioned above. My Kindle boots but it freezes on the Kindle Fire Boot Screen. It does not load the home screen of Kindle with Shelf.
Please help
http://forum.xda-developers.com/showthread.php?t=1428428
I have rooted a few phones and even two kindle fires but I messed up my fathers.. Rooting went fine, I was able to install the google framework and vending.apk.
On reboot kindle fire logo kept repeating.
Where I think I went wrong wrong was changing the permissions on vending.apk I might have changed permission on system/apps.. I ran the unbrick application but didn't know what the right issue so I ended up going a little hog wild trying "stuck at logo", "recovery" and "modded system/application"
now it only boots to press power for recovery page.
It is correct that I need to get adb shell working to have a shot here? I decided (a little to late) to slow it down but the shell didn't seem to be working at the point I stopped..
the kf is in fastboot mode - adb ist'n working in this mode
what tells your device manager? it should be "android adb interface" under "android phones" - if not update your drivers
then you can issue:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
if it says <waiting for device> to the first command let the command open and power off the kf by holding pwr button ~20sec - power on again - the command should be picked up and finished - pwr off/on again
Thanks... Will try this in a few hours when I get home
Thanks... After that I was able to get the ADB shell and find the issue with my permissions...
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
I tried to use the kindle fire utility in order to root my fire, but when I tried to use it, the first thing I did was install the drivers..... Then change it into fast boot mode, which I didn't realize would make it automatically reboot.... With out TWRP, or the fire fire fire boot loader. It is stuck at the "Kindle Fire" splash screen, and does not even connect to my computer. Is there a way to change it back to normal boot mode? Because when I tried to use the kindle de-bricking utility, it did not work, because it says waiting for device. If anyone could give me some advice, I would appreciate it.
May not help, but try the following: http://forum.xda-developers.com/showpost.php?p=21477909&postcount=13
have you tried to hold pwr button for ~20sec ?
I had the same problem and it was because the TWRP file was corrupt or incomplete. It went to reboot, and just stuck on the Kindle Fire logo. tried resetting, and everything. What I did was re-install the drivers, plug the device back in to the computer and even if KFU says your kindle isn't connected, try changing the boot mode back to normal. It worked for me and I restarted and tried the whole TWRP installation process over with a non-corrupt file and it worked just fine.
b63 said:
have you tried to hold pwr button for ~20sec ?
Click to expand...
Click to collapse
I actually did, I had tried a hard reboot several times.
then i would try as suggested above - if it don't work you can do it manually by opening a (elevated) command prompt and cd to the tools folder of kfu (eg c:\kfu\tools) and issue "fastboot -i 0x1949 oem idme bootmode 4000"
if it says <waiting for device> cold reboot the kf - the command should be picked up and finished - another reboot should bring you to normal boot
if this not working then you should check your drivers:
for fastboot it should be "android adb interface"
jblack426 said:
I had the same problem and it was because the TWRP file was corrupt or incomplete. It went to reboot, and just stuck on the Kindle Fire logo. tried resetting, and everything. What I did was re-install the drivers, plug the device back in to the computer and even if KFU says your kindle isn't connected, try changing the boot mode back to normal. It worked for me and I restarted and tried the whole TWRP installation process over with a non-corrupt file and it worked just fine.
Click to expand...
Click to collapse
I will try as soon as I get home. Thanks for the help so far!
jblack426 said:
I had the same problem and it was because the TWRP file was corrupt or incomplete. It went to reboot, and just stuck on the Kindle Fire logo. tried resetting, and everything. What I did was re-install the drivers, plug the device back in to the computer and even if KFU says your kindle isn't connected, try changing the boot mode back to normal. It worked for me and I restarted and tried the whole TWRP installation process over with a non-corrupt file and it worked just fine.
Click to expand...
Click to collapse
I tried your method and it rebooted my kindle succesfully, although it restored itself to factory conditions (which i dont think it's a bad thing, since i was scared of seeing the device stuck with the logo)
I will try to run kfu all over again and see if it works this time. I'll let know how it goes.
Thanks!
EDIT: Which twrp file did you use the second time? Can you post a link to it?
EDIT2: Nevermind about the first edit; the second time, kfu downloaded twrp instead of using its own recovery.img (which i believe is the corrupt file). I still cannot install firefirefire; a command line says "'adb' is not recognized as an internal or external command, operable program or batch file." Any help with that? Or can my kindle be safe without firefirefire? Thanks again!
it's not save without fff ! you need it to get to twrp and to have fastboot available for some seconds during startup
would recomend to try with kfu 0.9.3 and 0.9.1
some people have success with only one of the versions
Glad you got back to stock at least. The problem I had was that my internet connection timed out when KFU was downloading the files for the TWRP and FFF installation. There were incomplete files that KFU recognized as being there when i re-tried and it tried to install them again. You need to make sure you delete the files in the TWRP folder before you try again that way KFU won't find them and will download them again, hopefully successfully this time. You could also just delete the entire KFU you already have on your computer and download the whole thing again and re-try.
Hopefully this helps.
elporsche said:
I tried your method and it rebooted my kindle succesfully, although it restored itself to factory conditions (which i dont think it's a bad thing, since i was scared of seeing the device stuck with the logo)
I will try to run kfu all over again and see if it works this time. I'll let know how it goes.
Thanks!
EDIT: Which twrp file did you use the second time? Can you post a link to it?
EDIT2: Nevermind about the first edit; the second time, kfu downloaded twrp instead of using its own recovery.img (which i believe is the corrupt file). I still cannot install firefirefire; a command line says "'adb' is not recognized as an internal or external command, operable program or batch file." Any help with that? Or can my kindle be safe without firefirefire? Thanks again!
Click to expand...
Click to collapse
That means it can't find the ADB.exe in tools for Kindke Fire Utility. The tools folder must be in the same folder as the batch file.
b63 said:
then i would try as suggested above - if it don't work you can do it manually by opening a (elevated) command prompt and cd to the tools folder of kfu (eg c:\kfu\tools) and issue "fastboot -i 0x1949 oem idme bootmode 4000"
if it says <waiting for device> cold reboot the kf - the command should be picked up and finished - another reboot should bring you to normal boot
if this not working then you should check your drivers:
for fastboot it should be "android adb interface"
Click to expand...
Click to collapse
Worked! Thank you so much sir! Now that I followed a guide! (since I am no longer a derp about it) I am now rooted.
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
Can you please tell me how you changed the boot mode because i also bricked my kindle by the kfu.
- run kfu
- key in "1" and enter (bootmode menu)
- key in "1" and enter (bootmode normal)
that's it
can't explain easier ...
b63 said:
- run kfu
- key in "1" and enter (bootmode menu)
- key in "1" and enter (bootmode normal)
that's it
can't explain easier ...
Click to expand...
Click to collapse
Not Exactly. First he needs to check the device status by pressing 0, becouse if device have offline mode in KFU, he can't do much (propably he will need to use fastboot comands rather than adb)
papugoz said:
Not Exactly. First he needs to check the device status by pressing 0, becouse if device have offline mode in KFU, he can't do much (propably he will need to use fastboot comands rather than adb)
Click to expand...
Click to collapse
wrong - if the device is in fastboot mode adb will allways be offline !
btw. kfu is using fastboot commands
So what your saying is i can't do anything.
kingrafa135 said:
So what your saying is i can't do anything.
Click to expand...
Click to collapse
it is nearly impossible to realy brick a kf - just do as i suggested
if it's not working tell us what exactly happens ...
some important hints from the op of kfu:
Known Tricks
•If you end up stuck at the yellow triangle, in KF Utility select Boot Normal, wait for it to say <waiting for device> and then press and hold the power button 20 seconds until the fire turns off, then when its off turn it back on. This sometimes happens, I have yet to find a clean solution
•If you end up stuck with a yellow triangle, do not EVER unplug it. Leave it plugged in. Check the windows drivers to make sure it isnt showing as "kindle" again. Fastboot is different and can cause this.
Click to expand...
Click to collapse
and from vashypooh - dev of kfu:
http://forum.xda-developers.com/showpost.php?p=20945694&postcount=506
b63 said:
wrong - if the device is in fastboot mode adb will allways be offline !
btw. kfu is using fastboot commands
Click to expand...
Click to collapse
From my exp with KFU, I had to use fastboot command directly, becouse KFU, couldn't hadle it.
Help! After installing Firefirefire not loaded, the animation is loading and everything. In fastboot flashing betrayed recovery type error downloading boot.img failed. Who does not want to be defined in kfu. Hangs in the boot animation. Drivers removed cleanly and raised again, no result (
sorry for my english
Solved!
Can you reboot using fastboot reboot command.
Try
fastboot reboot. If it reboots, then change the mode of booting to normal using kfu.
Sent from my Amazon Kindle Fire using Tapatalk
I can not change to fastboot, it says error: device offline or waiting device
would try to use kfu option 1 - bootmode normal
if it says <waiting for device> power it off by holding the pwr button for ~20sec till it turns of - pwr on again - the command should resume and finish
a second pwr off/on will bring you back to normal
if this is not the case check your device manager - the kf uses 2 drivers
one for adb and one for fastboot - about drivers:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
Animation is loading normal mode. name in the Device Manager android composite adb interface. After waiting device, nothing happens
it seems your kf is in fastboot mode - the composite driver is for normal and recovery mode - try to update the driver to android adb interface - then the kfu command should work
adb status: Online (sometimes)
adb rooted: No
boot status: unknown
If I choose to act kfu, it says error: device not found
By some miracle I managed to run the light. But the internal memory for applications, downtrodden, buggy. Fff and put cwr, wrote downloading boot.img Filed, root is. Something with the memory I think. What should I do? than flash? Different kfu, does not help. I wanted to put gscript, but it is put into the internal memory, and then total space 0 and Apps 30mb, and where the SD, then 5gb total space
I just did a restore setting in the CM7 option after that I cannot boot into the CM7 but only the TWRP...
Can anyone tell me how to reinstall the TWRP...
I tried to use the kindle fire utility to re-install it, however it doesn't connect...
always shows offline..
please help
thanks
Did you restore bootloader, recovery and system from your backup using TWRP? If so you should have TWRP installed.
Please provide detail info what you have done to give further help.
You may need to update your USB diver to get adb working and to be able to install recovery software.
Sent from my Amazon Kindle Fire using Tapatalk
i think you said boot to recovery in cm7 - now you'r in a recovery bootloop - means it boots allways to recovery by itself - right ?
if so (if it is booted to twrp) use kfu option1 - bootmode normal
or issue manually:
adb shell idme bootmode 4000
adb reboot
an other method is to use fastboot commands:
fastboot oem idme bootmode 4000
fastboot reboot
in the case it says <waiting for device> power it off by holding the pwr button for ~20sec till it turns of - pwr on again - the command should resume and finish
a second pwr off/on will bring you back to normal
if commands don't work check your drivers:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
Can anyone tell me what the befits are to running cm7 vs a lunched like adw ion the fire?