my kindle fire 2 is stuck in the blue whit fire-fire screen
I can access the twrp recovery but after a incorrect wipe i have no android or so i am assuming.
i have installed the Google usb drivers through adb but the tablet will not show up i explorer
it will show as a android device but will not load anything else.
i have also booted into the twrp and attempted to mount it and it didn't work
lastly i have tried to use a fastboot cable. i get a screen on the device that says fastboot and what looks like a stoplight with the green blinking but again will not show up in explorer
dyson77 said:
my kindle fire 2 is stuck in the blue whit fire-fire screen
I can access the twrp recovery but after a incorrect wipe i have no android or so i am assuming.
i have installed the Google usb drivers through adb but the tablet will not show up i explorer
it will show as a android device but will not load anything else.
i have also booted into the twrp and attempted to mount it and it didn't work
lastly i have tried to use a fastboot cable. i get a screen on the device that says fastboot and what looks like a stoplight with the green blinking but again will not show up in explorer
Click to expand...
Click to collapse
First check you have fastboot drivers installed correctly:
Plug the cable into your device and then the computer. Reboot the Kindle. It *SHOULD* show a Fastboot screen. Once at the screen use this command on your computer:
fastboot -i 0x1949 devices
You should see something like this:
0123456789ABCDEF
Click to expand...
Click to collapse
Then enter these commands one at a time
fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
fastboot -i 0x1949 flash boot otter2-freedom-boot-10.4.6.img
fastboot -i 0x1949 flash recovery otter2-twrp-2.6.3.0-recovery.img
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
kidicarus1602 said:
First check you have fastboot drivers installed correctly:
Then enter these commands one at a time
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B0q-ce_LYNLFQW16QWFEbDlKSUk/edit?usp=sharing
the unit wont show up in explorer at all,I have tried to run the command listed and it just says waiting for device.
I have tried rebooting into recovery reboot and still locks up
any other ideas
{
"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"
}
this is what device manager says
dyson77 said:
View attachment 2709099
View attachment 2709100
View attachment 2709101
this is what device manager says
Click to expand...
Click to collapse
any ideas?
Manually install the drivers.
-》Sent from my mind to your screen.
i have installed the google and adb drivers what other ones are there
dyson77 said:
i have installed the google and adb drivers what other ones are there
Click to expand...
Click to collapse
MANUALLY install the adb drivers.
-》Sent from my mind to your screen.
ok I have manually installed the drivers.
it then was showing up as a Otter-2
I then went through the same steps to add the drivers for it as a google usb driver.
but its still not showing up in my explorer and when i do a adb devices it doesn't show up
mind you that was all with the fastboot cable
when I hook it up with a standard usb and gho into the teamwin twrp it shows as a Kindle fire 2
and adb devices finds it as 0123456789abcdef
see attached pics
Ok I have been able to push a file to the fire 2 but the only file that will install is cm-10.1.3-otter2.zip
when i try to install anything else i get a error 7 and then it wont boot at all when i reboot it just goes into a loop.
would like to put cm 11 on there seems a little better
You need to update your recovery.
Sent from my Galaxy Nexus using Tapatalk
Bro you are in the wrong section. I repoted you so this thread should be in the right section soon.
Related
Okay guys, I'm trying to root my Fire 6.3 using KFU 0.9.5 (on Win7 Ultimate). I installed the drivers correctly and device manager shows "Android Composite ADB Interface". So I load up KFU and it says:
ADB Status: Online
Boot Status: Unknown
If I hit option 2 to install Perm Root, it gets to the part where it checks for twrp.img, then sets to fastboot mode. The kindle does reboot into fastboot, but then gets stuck on the "Kindle Fire" logo. Also, KFU just sits there waiting. See screenshot.
{
"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"
}
If I terminate the batch, then rerun KFU, goto Bootmode Menu and set to Normal, I can get the kindle to reboot back to normal mode and all is good. I've tried searching the forum and all through Vashypooh's thread here, tried various tricks, but still have been unable to get it to work. Tried different USB ports, different cables (none are kindle oem), still nothing. Anyone else have this issue or know a way to fix it?
You could install twrp manually.
Get into fastboot mode (4002)
Shift + right click on your KFU "tools" folder containing fastboot.exe
Select the option that says something to the effect of "Run as command"
In the command window that pops up, enter:
fastboot -i 0x1949 flash recovery /path/to/twrp.img
!!VERY IMPORTANT!! Make sure you use that command with the twrp that comes with KFU. Accidentally using it on an older version could cause problems that you don't want to deal with.
When finished, reboot and change your bootmode back to normal.
soupmagnet said:
fastboot -i 0x1949 flash recovery /path/to/twrp.img
Click to expand...
Click to collapse
Tried this, it just said waiting for devices. One thing I noticed is when it's in fastboot, it doesn't even show in device manager. I read in a post about a separate driver for fastboot. Anyway, now it's stuck in fastboot...trying to get it back into normal mode.
You must be in fastboot mode and at the Kindle Fire logo/yellow triangle before issuing the command.
If that doesn't work hold the power button until your device shuts down and enter the command again. Turn it back on when it says 'waiting for device"
If that doesn't work, it is a driver failure. Uninstall/delete/reinstall your drivers and try again.
[Edit:] There are no separate drivers for fastboot
I switched to a different USB port and was able to use KFU to get it back to normal mode. I tried switching back to fastboot and this time it does show up in device manager in fastboot, but not with the yellow ! on it. It shows up as "Android ADB Interface". Running fastboot devices gives me a blank list.
I'm starting to wonder if it's the cable I'm using. It's my transfer cable for my EVO Design. Wondering if I should just get a factory cable and see if that fixes the problem.
Just because Windows says the drivers are there doesn't mean they're working properly. It is a well known issue with Windows and KFU.
Uninstall/delete/reinstall
[Edit:] You may have to do it twenty times or so, be patient with it.
Hello,
ive been trying to change rom (not the first time),
and while in fastboot mode
any trying to burn boot.img, but in order to do that I must open the usb thruogh fastboot mode,
and my phone say it cant open the USB.
is it a problem with the sense 5?
ive downloaded again the htc sync manager.
and I can load the usb from the when the phone is on.
how can I fix it?
thanks for reading!
Download and unzip the attachement.
Open a command prompt to that folder.
Connect your device
Set it in fastboot mode
Type "fastboot devices"
Tell me what you see.
Actually sounds like you are referring to "failed to open usb master mode" and if that is the case it is simply because you have the cable plugged in when you are switching between hboot and fastboot. each time you want to switch, pull out the cable then reconnect when you have changed modes
webpatrick said:
Download and unzip the attachement.
Open a command prompt to that folder.
Connect your device
Set it in fastboot mode
Type "fastboot devices"
Tell me what you see.
Click to expand...
Click to collapse
{
"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"
}
http://imageshack.us/f/811/wm6o.jpg/
nogotaclue said:
Actually sounds like you are referring to "failed to open usb master mode" and if that is the case it is simply because you have the cable plugged in when you are switching between hboot and fastboot. each time you want to switch, pull out the cable then reconnect when you have changed modes
Click to expand...
Click to collapse
It doesnt says now there is a problem with the usb, but it still wont load it on computer.
arnon124 said:
http://imageshack.us/f/811/wm6o.jpg/
It doesnt says now there is a problem with the usb, but it still wont load it on computer.
Click to expand...
Click to collapse
Your device is recognized by fastboot, so you can flash a boot.img, the command is:
Code:
fastboot flash boot boot.img
Make sure you have copied the boot.img to the fastboot folder on your PC.
You cannot see your device in windows explorer when you are in fastboot.
Edit: You can in recovery when you mount your storage.
webpatrick said:
Your device is recognized by fastboot, so you can flash a boot.img, the command is:
Code:
fastboot flash boot boot.img
Make sure you have copied the boot.img to the fastboot folder on your PC.
You cannot see your device in windows explorer when you are in fastboot.
Edit: You can in recovery when you mount your storage.
Click to expand...
Click to collapse
finished changing the rom, thanks alot for helping!
I have a 1st gen fire, and I attempted to root it, it froze on the startup logo screen. Now I tried to reconnect it to my computer to use unbrock utility and it won't recognize the device. Did a clean install of adb drivers and I still cant find my kindle.
Thanks for the time.
You are probably stuck in fastboot. Get the necessary fastboot executable and files and run command 'fastboot devices' to ses if your serial number comes up.
Sent from my Nexus 7 using Tapatalk
SwoRNLeaDejZ said:
You are probably stuck in fastboot. Get the necessary fastboot executable and files and run command 'fastboot devices' to ses if your serial number comes up.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
And i do that how?
I tried installing twrp recovery using kfu 0.9.9 and it stops at fast reboot says waiting for device.
[fastboot] stock 6.2.1 fastboot mode without rooting or cables
http://forum.xda-developers.com/showthread.php?t=1414832
Sent from my XT894 using Tapatalk
sd_shadow said:
[fastboot] stock 6.2.1 fastboot mode without rooting or cables
http://forum.xda-developers.com/showthread.php?t=1414832
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
So i downloaded the file, what do i do with it? Im very noob at this, i rooted my HTC one no problem but this is kicking my butt lol
Wish I could just pay someone to fix this.
You need to use the adb and fastboot.exe files that are included with KFU, to push the files to the kindle.
Some basic adb instructions in my list. sd_shadow's collection of links for: Kindle Fire 1
Sent from my XT894 using Tapatalk
Im doing the manual install of the drivers and when i select the "findle fire drivers" in my download folder, it says was unable to install driver could not find driver for your device.
Did you unzip drivers?
Did you uninstall old drivers?
May need to reboot pc a couple of times
Sent from my XT894 using Tapatalk
Yes
Yes
No
Im running 8.1 if that makes a difference.
I restarted the computer and it says the same thing.
I tried to manually install the drivers from KFU and it gave me this.
{
"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"
}
Tried another driver and got this.
Omg I finally fixed it. Just a quick run down of what I did.
Windows 8.1
Stuck on boot logo
Drivers wouldn't load.
Had to disable driver signature
manually installed adb drivers (ignored the warnings)
unpluged kindle and plugged it back in
ran KFU hit recovery.
great, I don't have win 8, and forgot about the disabling driver signature trick
kfu
Try to get your kindle fire recognize by your Pc... run Krupp. Get your adb status online..enter boot menu boot normal mode 4000
I have ADB installed, Android SDK.
I've tried to sideload and I get the error message "can't read".
Should I be changing the directory in terminal?
This is frustrating.
Thanks.
Anyone? Lol
koooba said:
Anyone? Lol
Click to expand...
Click to collapse
Is your phone coming up after using the command ADB devices?
What are you trying to sideload
No for whatever reason it's not.
I have the drivers installed, debugging on phone set.
Didn't list when I type advice devices.
What directory should terminal be in?
Wondering if I'm in the wrong directory perhaps?
Thanks
ADB could be anywhere and it'll work, double check the drivers and make sure the ADB drivers are installed and not just the MTP drivers.
What are you sideloading btw?
ADB can be anywhere, okay good to know. Thanks.
I'm trying to sideload Oxygen 3.2.1 since I'm having microphone issues - people can't hear me sometimes or my voice gets all messed up.
Apparently sideloading this update fixes this issue, at least for a few people it did.
When I connect the phone to the computer in regular mode, the device is listed.
When I go into RECOVERY mode with the phone, the computer doesn't find the device at all.
I'm going by the OnePlus instructions to turn it off and go into this mode.
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_3.2.1/
unlock bootloader
install twrp
make Nandroid Backup
download FreedomOS 3.2.1
move to phone
Wipe Caches and system, no need to wipe data (in TWRP)
Install FreedomOS ( u may need to redownload SU and flash manually if not working in FreedomOS Aroma)
Done... If still issues do a clean flash, go to twrp and Advance Wipe (Caches, Data, System) DO NOT DO STORAGE!!!!
No this will not Void your warranty with OnePlus
Click here for better instructions
Thanks Brad, first I'd like to try sideload method first if at all possible.
I can't figure out why the computer won't recognize the device in RECOVERY MODE...? Tried everything, I have to be doing something wrong.
Drivers are okay when it's not in recovery mode
The weird thing is, when the phone is OFF and plugged into the computer, the computer recognizes the device when I type "adb devices".... WTH????
koooba said:
Thanks Brad, first I'd like to try sideload method first if at all possible.
I can't figure out why the computer won't recognize the device in RECOVERY MODE...? Tried everything, I have to be doing something wrong.
Drivers are okay when it's not in recovery mode
The weird thing is, when the phone is OFF and plugged into the computer, the computer recognizes the device when I type "adb devices".... WTH????
Click to expand...
Click to collapse
what drivers did u install, so when u type "adb devices" nothing at all comes up?
I installed the drivers that are on the phone when you plug it in.
When the phone is on and plugged into the computer, it recognizes it.
This is what I get -> http://imgur.com/B3a8AMg
When I turn it off and plug it in, it recognizes the device.
When I'm in recovery mode, it doesn't recognize it at all.
i am not sure how stock recovery works, but if u are in fastboot mode, does it recognize?
with it unathurized that means u did not check the box on the phone when plugged in to ur computer.... u should get this on your phone when booted into the OS
{
"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"
}
i would try to boot into fastboot mode and push the file to ur phone and install via zip in stock recovery
and try this: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
I checked that box off, yes.
I'm about to give up, now it's not even showing a "storage" folder at all when plugged in.
Cannot even copy files into the phone, no storage showing.
OP, so many problems and it's only 4 days old.
anyone, please
Hello good morning
I have been trying to install android 12 gsi on my a52s 5g via ADB for some time. I know that my phone already has the android 12 update but I would still like to try android 12 gsi.
I have already unlocked the bootloader and installed all the necessary drivers.
I have USB debugging and OEM mode enabled.
When I enter ADB and want to enter the command "fastboot reboot fastboot" I get the following message below the command: C:\ADB>fastboot reboot fastboot
< waiting for any device >
And when I try to enter fastboot through recovery, it restarts the phone. I have also tried with the "reboot recovery" command but still not successful.
Since then I have not been able to continue with the steps. I have already granted the usb debugging permissions and everything necessary so right now I don't know what to do.
Any solution to the problem????
{
"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"
}
mrjacobosuper said:
Hello good morning
I have been trying to install android 12 gsi on my a52s 5g via ADB for some time. I know that my phone already has the android 12 update but I would still like to try android 12 gsi.
I have already unlocked the bootloader and installed all the necessary drivers.
I have USB debugging and OEM mode enabled.
When I enter ADB and want to enter the command "fastboot reboot fastboot" I get the following message below the command: C:\ADB>fastboot reboot fastboot
< waiting for any device >
And when I try to enter fastboot through recovery, it restarts the phone. I have also tried with the "reboot recovery" command but still not successful.
Since then I have not been able to continue with the steps. I have already granted the usb debugging permissions and everything necessary so right now I don't know what to do.
Any solution to the problem????
View attachment 5661025
Click to expand...
Click to collapse
Do you have a recovery with fastboot installed on your phone? I got into fastboot with: adb reboot fastboot (enter)
bobfrantic said:
Do you have a recovery with fastboot installed on your phone? I got into fastboot with: adb reboot fastboot (enter)
Click to expand...
Click to collapse
No, but already tried the "Adb Reboot Fastboot" command and yet the only thing it does is restart the phone
mrjacobosuper said:
No, but already tried the "Adb Reboot Fastboot" command and yet the only thing it does is restart the phone
Click to expand...
Click to collapse
for it to work you need to have the recovery with fastboot in it. try pushing this to your phone with adb... but doso at your own risk, i accept no responsibilty if it causes a soft brick or anything else on your phone. it is the recovery that is on my phone though so should be alright. Make sure it is for the A52s 5G.