Related
I rooted (or at least I thought I did) and checked in a root file browser to see if I could change files. No luck. So I tried rerooting. Now my Kindle Fire is bricked and stuck at the boot logo. I also accidentaly uninstalled the Android ADB drivers. Any help would be greatly appreciated.
Did you try the 20 second hold
Sent from my Kindle Fire using xda premium
if you find something I posted helpful please thank me
If you used KFU, then you might be in luck. Hold you power button down for like 10-30 seconds. That should turn it off. Then, if you see a yellow triangle or a kindle fire symbol hold down the power button. If it is a yellow triangle hold down until the power button turns orange. If it is kindle fire with "fire" in blue hold down the power button until you enter boot mood menu. Next, select recovery (if it is Fire in Blue). If it was a yellow triangle then you would be in recovery after my second step. If you make it to recovery, select wipe, then select factory reset, After that is done reboot system. You should then be unbricked.
If you do not see the triangle or the "fire" in blue. Then you may have a problem. If this happens, go into KFU and install adb drivers. Then, plug in your KF(kindle fire should just be booted up how you normally would) and restart KFU. If it says adb status online, go into boot mode. And go into recovery. This will also get you into the recovery. If this works follow my previous steps about doing a factory reset.
Let me know if this worked.
(sent from my kindle fire)
gregory99mar said:
If you used KFU, then you might be in luck. Hold you power button down for like 10-30 seconds. That should turn it off. Then, if you see a yellow triangle or a kindle fire symbol hold down the power button. If it is a yellow triangle hold down until the power button turns orange. If it is kindle fire with "fire" in blue hold down the power button until you enter boot mood menu. Next, select recovery (if it is Fire in Blue). If it was a yellow triangle then you would be in recovery after my second step. If you make it to recovery, select wipe, then select factory reset, After that is done reboot system. You should then be unbricked.
If you do not see the triangle or the "fire" in blue. Then you may have a problem. If this happens, go into KFU and install adb drivers. Then, plug in your KF(kindle fire should just be booted up how you normally would) and restart KFU. If it says adb status online, go into boot mode. And go into recovery. This will also get you into the recovery. If this works follow my previous steps about doing a factory reset.
Let me know if this worked.
(sent from my kindle fire)
Click to expand...
Click to collapse
I don't have access to a Vista/7 computer ATM. Any ideas? Oh and I don't have TWRP or any other recovery menus installed. They didn't install even though I had the .img file.
TheZeldaLova said:
I don't have access to a Vista/7 computer ATM. Any ideas? Oh and I don't have TWRP or any other recovery menus installed. They didn't install even though I had the .img file.
Click to expand...
Click to collapse
Alright, so take it you did not root with KFU. The only idea that comes to mind is, (asuming that you are on a Mac) run a virtual device of windows 7 or vista on you Mac. Use KFU to install drivers, and boot up you KF. Re-open KFU and see if says adb online. If so, attempt to flash twrp using FKU. This will bring you right into the recovery. The recovery might not even stick but you only need to get into it once.
gregory99mar said:
Alright, so take it you did not root with KFU. The only idea that comes to mind is, (asuming that you are on a Mac) run a virtual device of windows 7 or vista on you Mac. Use KFU to install drivers, and boot up you KF. Re-open KFU and see if says adb online. If so, attempt to flash twrp using FKU. This will bring you right into the recovery. The recovery might not even stick but you only need to get into it once.
Click to expand...
Click to collapse
Nope. I'm on Windows. I just used a friends computer with Vista ( I have XP ) Thank you though. I'll use a Virtual PC like you said.
gregory99mar said:
Alright, so take it you did not root with KFU. The only idea that comes to mind is, (asuming that you are on a Mac) run a virtual device of windows 7 or vista on you Mac. Use KFU to install drivers, and boot up you KF. Re-open KFU and see if says adb online. If so, attempt to flash twrp using FKU. This will bring you right into the recovery. The recovery might not even stick but you only need to get into it once.
Click to expand...
Click to collapse
All I did was flash TWRP, Them it booted normally. I don't know but whatever. And thanks for the help!
You welcome, Glad I could help.
Hi All.
I’ve rooted my Kindle device successfully before (during v6.2 – have the driver installed from this and cable worked successfully )
Now with the 6.3.1, I used the KFU v0.9.6 to do it – option 2 ‘Install Permanent Root with Superuser’
Followed the instructions as per http://forum.xda-developers.com/showthread.php?t=1399889
- On my XP machine, it detected my Kindle initially but it stopped and my Kindle Fire was showing the stock welcome screen but kept on rebooting.
- Then I tried on a Win 7 machine and ran option 2 again – it did something and now my Kindle is stuck on the FFF screen (Kindle Fire logo in blue and white – v1.4a).
- Now when I run ‘ran.bat’, pc it shows ‘waiting for device’
- The FFF screen was blinking initially but now it’s permanently on.
- I can off my Kindle by pressing the on button for about 20 seconds and when I connect my Kindle in the off state to the pc, it turns on and remain on the FFF screen
1. Installing the driver
So I figured the above is due to the driver.
- However, the Kindle is not appearing in the Device Manager with a yellow ! – hence can’t manually install the drivers.
- Tried install_drivers.bat – it says ‘Google, Inc. (WinUSB)…..Install failed (Unsigned)’
- I ensured that the ‘Driver Signing Options’ is set to ‘Ignore – Install the software and don’t ask for my approval’ and ‘Make this action the system default’.
- So next, I tried to force my XP to install the drivers (Kindle unplugged), by using ‘Add Hardware’ and installing drivers from c:\kfu\drivers –
- Installed all 3 drivers – Android ADB Interface, Android Bootloader Interface & Android Composite ADB Interface.
- Received this message at the end – ‘The software for this device is now installed, but may not work correctly. The device cannot start. (Code 10)’
- But when I plugged in my Kindle and run KFU it still says ‘waiting for device’.
I tried the above steps with:-
- 3 XP machines and 1 Win 7, and
- on different USB ports (tried both USB 2.0 and 3.0)
- and tried using 4 different usb cables
- Same results ‘waiting for device’
- One exception though – for the Win 7 machine – when I ‘install_drivers.bat’, it says ‘Google, Inc. (WinUSB) ….Ready to use’ – but still shows ‘waiting for device’, when running KFU.
2. Delete old drivers
Followed this (http://forum.xda-developers.com/showthread.php?t=1459116) to uninstall the drivers (including the Microsoft support page).
- But XP and Win 7 still did not detect the Kindle in ‘Device Manager’
- Tried to force install the 3 drivers again and still ‘waiting for device’
Additionally tried to download the Google Usb driver from Android SDK - same issue - no yellow !
And tried to connect via 'c:\KindleAdb\adb devices' (learned from the previous root exercise) - no devices appears.
3. Kindle Fire Unbrick Utility
Tried this next - http://forum.xda-developers.com/showthread.php?t=1428428
Tried the many options available. When it is executed, its says ‘error’, despite saying Kindle unbricked at the end.
4. Firekit LiveUSB repair kit 1.1
Finally decided to use the Linux method (http://forum.xda-developers.com/showthread.php?t=1430038)
- Created a USB Ubuntu and ran the program but suprisingly still the same problem – stuck at ‘waiting for device’ (see snapshot attached).
So I’m a bit confused right now. From the above it seems to me that the Kindle is not talking to the PC.
- But if in Linux, it doesn’t work (which from what I read doesn’t require a driver?) then it could possibly be my cable.
- But the cable did work when I rooted in 6.2 and it also worked initially when I used KFU. And also, I tried with 4 different cables.
- Am not sure if the cables are ‘factory cable’ – but it did work initially.
I’m stuck here. Any help/advice would be deeply appreciated. Thank you.
A few things that might help you...
1) If you have FFF 1.4a, you can access its boot menu and have the device boot normally or into recovery. As it boots up, look at the power button LED and watch as it goes from a bright green to a dim green. As soon as it goes dim, press and release the button to bring up the menu on the screen. You can then flip through the menu options by repeatedly pressing and releasing the power button. Leave it alone for a few seconds and it will continue to boot using the selected option.
2) If you don't know whether or not you have a factory cable, you probably don't have one...
http://forum.xda-developers.com/showthread.php?t=1550999
3) For the computer to issue fastboot commands to the device, it must already be connected to the computer before booting into fastboot mode. That is... you cannot boot the KF into fastboot mode and then connect it to the computer. If the computer is <waiting for device>, try turning the KF off by pressing and holding the power button for around 20 seconds to shut it down completely, then turning it back on again. For more information on fastboot....
http://forum.xda-developers.com/showthread.php?t=1668159
If the above suggestions don't work for you, make sure you are getting the expected hardware IDs shown in the previous link.
Thank you kinfauns for your immediately reply.
kinfauns said:
A few things that might help you...
1) If you have FFF 1.4a, you can access its boot menu and have the device boot normally or into recovery. As it boots up, look at the power button LED and watch as it goes from a bright green to a dim green. As soon as it goes dim, press and release the button to bring up the menu on the screen. You can then flip through the menu options by repeatedly pressing and releasing the power button. Leave it alone for a few seconds and it will continue to boot using the selected option.
Click to expand...
Click to collapse
Unfortunately this doesn't happen on my KF. The power button is bright green. And the bootlogo is persistent and remain bright on the display.
I've tried repeatedly pressing and releasing the power button but didn't work.
2) If you don't know whether or not you have a factory cable, you probably don't have one...
http://forum.xda-developers.com/showthread.php?t=1550999
Click to expand...
Click to collapse
Just bought a USB factory fastboot mode cable online .
3) For the computer to issue fastboot commands to the device, it must already be connected to the computer before booting into fastboot mode. That is... you cannot boot the KF into fastboot mode and then connect it to the computer. If the computer is <waiting for device>, try turning the KF off by pressing and holding the power button for around 20 seconds to shut it down completely, then turning it back on again. For more information on fastboot....
http://forum.xda-developers.com/showthread.php?t=1668159
Click to expand...
Click to collapse
I tried this method but nothing changes - when I turn it back on, it goes back to the bootlogo. KFU still says <waiting for device>.
Also tried 'Temporary fastboot mode' - 'fastboot getvar product' - still <waiting for device>.
If the above suggestions don't work for you, make sure you are getting the expected hardware IDs shown in the previous link.
Click to expand...
Click to collapse
My KF doesn't show up on 'Device Manager' - no yellow question mark or whatsoever.
When I manually installed 'Android ADB Interface' - it shows an yellow ! and even after I connect the KF it still shows the yellow !.
Current hardware ID (for 'Android ADB Interface' with yellow !): usb\vid_0bb4&pid_0c01
Device status: This device cannot start. (Code 10)
So I guess, I will wait for my factory cable, unless you have any other suggestions? Thank you.
ivanovicch said:
My KF doesn't show up on 'Device Manager' - no yellow question mark or whatsoever.
When I manually installed 'Android ADB Interface' - it shows an yellow ! and even after I connect the KF it still shows the yellow !.
Current hardware ID (for 'Android ADB Interface' with yellow !): usb\vid_0bb4&pid_0c01
Device status: This device cannot start. (Code 10)
So I guess, I will wait for my factory cable, unless you have any other suggestions? Thank you.
Click to expand...
Click to collapse
I have no idea what that ID number is, but it's definitely not the one you should see for fastboot. That means you have those drivers installed on the wrong interface. I also suspect your bootloader might be corrupt or otherwise not functioning correctly. Using the factory cable will give you a better idea what's going on since you can (almost) be certain that the device has put itself into fastboot mode. Then you can focus on getting the drivers installed properly for the interface that appears in the device manager. As a last resort, you might have to open up the case and use USB boot (in Firekit) to flash a new bootloader.
Just quickly skimmed over your thread but have you tried holding down the power button for a minute or so and then powering it on? I would tend to agree with kinfauns that somehow your bootloader is broken if so a factory cable will do nothing only firekit will remedy a broken bootloader that's why I ask about the long press power off attempt...
Thepooch said:
Just quickly skimmed over your thread but have you tried holding down the power button for a minute or so and then powering it on? I would tend to agree with kinfauns that somehow your bootloader is broken if so a factory cable will do nothing only firekit will remedy a broken bootloader that's why I ask about the long press power off attempt...
Click to expand...
Click to collapse
I pressed power button for more than a minute - tried 2 ways:-
- with the KF on - it switches off and remains switched off.
- with the KF off - it switches on for a bit and then switches off and remains switched off.
I'll just give the factory cable a try when it arrives - will update here again. Hopefully I don't have to open up the case.
Thanks kinfauns and Thepooch.
I have no idea what that ID number is, but it's definitely not the one you should see for fastboot. That means you have those drivers installed on the wrong interface. I also suspect your bootloader might be corrupt or otherwise not functioning correctly. Using the factory cable will give you a better idea what's going on since you can (almost) be certain that the device has put itself into fastboot mode. Then you can focus on getting the drivers installed properly for the interface that appears in the device manager. As a last resort, you might have to open up the case and use USB boot (in Firekit) to flash a new bootloader.
Click to expand...
Click to collapse
Just quickly skimmed over your thread but have you tried holding down the power button for a minute or so and then powering it on? I would tend to agree with kinfauns that somehow your bootloader is broken if so a factory cable will do nothing only firekit will remedy a broken bootloader that's why I ask about the long press power off attempt...
Click to expand...
Click to collapse
Just to update - the factory cable didn't do the trick. KF still stuck at KF blue/white logo - the bootloader must be corrupted.
Hence am going to try opening the case and flash a new bootloader. Wish me luck - will update again soon. Thanks.
Please help me My Kindle is stuck at black screen after Kindle Fire logo. I have Android Composite ADB Interface driver installed, but when I plugged my Kindle Fire to my PC, it detected as a USB Mass Storage, and won't connect as an Android device so I couldn't do anything with adb commands or KFU...
See it in my topic for more information: http://forum.xda-developers.com/showthread.php?p=30542544#post30542544
ivanovicch said:
Just to update - the factory cable didn't do the trick. KF still stuck at KF blue/white logo - the bootloader must be corrupted.
Hence am going to try opening the case and flash a new bootloader. Wish me luck - will update again soon. Thanks.
Click to expand...
Click to collapse
Dear All. My KF is ALIVE! Had to open my back case and do the short point trick - http://forum.xda-developers.com/showthread.php?t=1405052.
Worked like a charm.
Thanks pokey9000, kinfauns and mainly the Thepooch - thank you for guiding me through this.
your welcome I`m quite pleased its fixed myself
same issue not unable to solve
i have exact same issue but i am having a problem to fix it. i wonder if anyone can help me here. i am trying to short the test point but in device manager its shoing usb not recognized again and again. please guide me whats wrong i am doing. using windows 7 (64bit)
I have kfhd7 (tate) and i updated it from cm12.1 to cm13 but after the reboot it is now stuck on white-blue "kindle fire" logo. everytime i reboot it shows the white-yellow logo and then gets stuck on the blue one. moreover, i cant get to twrp3 using keys as it gets stuck and device gets hot. Tried fastboot and adb but the devices is shown offline. I dont have access to a fastboot cable and even dont hope that i will get one shipped sooner. kinldy help
hasanalikhattak said:
I have kfhd7 (tate) and i updated it from cm12.1 to cm13 but after the reboot it is now stuck on white-blue "kindle fire" logo. everytime i reboot it shows the white-yellow logo and then gets stuck on the blue one. moreover, i cant get to twrp3 using keys as it gets stuck and device gets hot. Tried fastboot and adb but the devices is shown offline. I dont have access to a fastboot cable and even dont hope that i will get one shipped sooner. kinldy help
Click to expand...
Click to collapse
this is only for kindle fire 1 (2011)
there is a separate section for device see
Fire Index: Which Amazon (Kindle) Fire Do I have?
for correct forum link
Sent from my XT1254 using XDA Labs
The phone is in bootlopp (i think).When i turn on appears android on groundb with the red triangle and a chinese word.This disappears and appears again,for an infinite time.Display stays turned on.Turning on in bootloader it works,but just in bootloader.If i try to enter in "Restart bootloader,"recovery,"normal boot"ecc it's in bootloop again.So i can access only bootloader at the moment.I want to reflash system,droidboot imgs ecc with fastboot but...tried to recognize phone on an old HP Compaq nx6110 with usb 2.0 and win7.installed on it adb drivers,adb and fast-tools.don't think zenf2 drivers are important at the moment,now should consider just the adb drivers cause i can access only bootloader.however i think zenf2 drivers are installed on it.nothing.phone no recognized by fastboot and no recognized by windows.consider that on a xp and 2.0 usb pc (with fastboot,adb,and adb drivers on it) phone is recognized by windows as Android-Phone but then windows says i've not the drivers for the installation (appears the drivers' choosing window).No asus driver on it,on the win7 pc there are!!
CenereZar said:
The phone is in bootlopp (i think).When i turn on appears android on groundb with the red triangle and a chinese word.This disappears and appears again,for an infinite time.Display stays turned on.Turning on in bootloader it works,but just in bootloader.If i try to enter in "Restart bootloader,"recovery,"normal boot"ecc it's in bootloop again.So i can access only bootloader at the moment.I want to reflash system,droidboot imgs ecc with fastboot but...tried to recognize phone on an old HP Compaq nx6110 with usb 2.0 and win7.installed on it adb drivers,adb and fast-tools.don't think zenf2 drivers are important at the moment,now should consider just the adb drivers cause i can access only bootloader.however i think zenf2 drivers are installed on it.nothing.phone no recognized by fastboot and no recognized by windows.consider that on a xp and 2.0 usb pc (with fastboot,adb,and adb drivers on it) phone is recognized by windows as Android-Phone but then windows says i've not the drivers for the installation (appears the drivers' choosing window).No asus driver on it,on the win7 pc there are!!
Click to expand...
Click to collapse
When you see the dead android with red triangle, hold the power button and keep pressing it and quickly
press volume up button and release it but keep the power button and you will see the Recovery options.
Then choose "format Cache" with volume up & down button and enter with power button to format cache partition.
It would take a long time so don't be alarmed. When done, choose restart system and the boot loop should be fixed.
Good luck.
samteeee said:
When you see the dead android with red triangle, hold the power button and keep pressing it and quickly
press volume up button and release it but keep the power button and you will see the Recovery options.
Then choose "format Cache" with volume up & down button and enter with power button to format cache partition.
It would take a long time so don't be alarmed. When done, choose restart system and the boot loop should be fixed.
Good luck.
Click to expand...
Click to collapse
Thank you bro,you saved me
samteeee said:
When you see the dead android with red triangle, hold the power button and keep pressing it and quickly
press volume up button and release it but keep the power button and you will see the Recovery options.
Then choose "format Cache" with volume up & down button and enter with power button to format cache partition.
It would take a long time so don't be alarmed. When done, choose restart system and the boot loop should be fixed.
Good luck.
Click to expand...
Click to collapse
Didn't work for me ... if I keep pressed the power button for a long time, power off the phone and it doesn't entry in Recovery mode...
I resolved with "fastboot erase cache" command
It is normal to get that error when selecting 'recovery mode'
The next step is a little tricky. You have to press and hold the power button, then press the volume up button. It may take a few tries. Both buttons will have to be pressed together simultaneous to enter Android system recovery. Please also see http://www.asus.com/us/support/FAQ/1011956/
Sincerely,
ASUS_USA
Asus_USA said:
It is normal to get that error when selecting 'recovery mode'
The next step is a little tricky. You have to press and hold the power button, then press the volume up button. It may take a few tries. Both buttons will have to be pressed together simultaneous to enter Android system recovery. Please also see http://www.asus.com/us/support/FAQ/1011956/
Sincerely,
ASUS_USA
Click to expand...
Click to collapse
Hi,
I´m having a problem with mine. Can´t recognize phone in fastboot but it´s different. I already asked for help in general thread - all resources (page 47 to 50) but still can´t solve.
I rooted my device using method 3 (one click root) and first everything seems fine, but on my first reboot i entered on bootloader - recovery and started a wipe cache, but didn´t finished it, push power button and force it of (i seemeed stuck there - was wipping for more than 10 minutes). Since then i can´t solve anything, tried many ways to unbrick my phone but i seem the problem was i can´t connect fastboot. After a lot o tries, i entered in TWRP using method 2 and wipe, made a recovery, everything and as magic i can enter again on recovery, even tried adb sideload (it started, but when starts to write something - at 50% of the process just ended). So, long story short, i did a flash of the original firmware i downloaded from asus website using method 2 and now it´s working as original, but i still having the same problem (or maybe worst, since i can´t enter the TWRP recovery using method 2 anymore) and can´t root my device. When i tried to do anything using fastboot it´s just shows "FAILED", When i request adb devices shows a blank line. If my phone is on, using android, it shows the correct serial number.
I don´t know what´s happening, it seems to estabilsh a connection (when on its ok, method 2 freeze on teamwin logo - the tool can write something on phone) but can´t write anything. i´m worried because i think i won´t be able to do any update and i wanted a rooted phone to.
Anyone seems a solution?
I'm having the same problem today and I solved it just now! I can't even open the fastboot and recovery. Finally I install the software "shuame"(I'm Chinese, you guys may find other software) on my PC, and with it my computer read zenfone2, and I use the function in the software to open fastboot mode, then I flash the WW version recovery.img and boot.img with a one-click tool in zentalk(TW), then I just double wipe, the phone is alive now !
Sent from my ASUS_Z00AD using XDA Free mobile app
ityoung said:
I'm having the same problem today and I solved it just now! I can't even open the fastboot and recovery. Finally I install the software "shuame"(I'm Chinese, you guys may find other software) on my PC, and with it my computer read zenfone2, and I use the function in the software to open fastboot mode, then I flash the WW version recovery.img and boot.img with a one-click tool in zentalk(TW), then I just double wipe, the phone is alive now !
Sent from my ASUS_Z00AD using XDA Free mobile app
Click to expand...
Click to collapse
I don´t know any other software. Is this software only in chinese ? Can i try?
My phone is actually working, but i can´t flash anything, even MOFD_update.zip (the file it is used to make ota uptades)
is Your phone rooted? which method did you use? Now you can use fastboot normally?
<<.>>Asus Zenphone 2 z008 stuck after hard reset cannot open!>> I am out of options
Dear all kind developers ,
I went to the recovery mode of my asus zenpone 2 and wipe of the data from it.
After I clicked data wipe it did not continued , it was stuck for like 20 minutes and I restarted the phone .
After that every time I try to open it or go to recovery I cannot open the phone. It only shows an android logo and an error.
I can go to the boot loader menu .
I have already searched the whole internet and found I solution for it , which I have to
* Download intel driver, and some abd files
* Enable Usb debugging and switch of the phone
* Go to boot loader and switch volume up until it shows fastboot
* Connect the phone via usb and open the adb files in cmd
* Type fast boot remove cache in the cmd
And it says that the phone will be alright after the process !
BUT, I DID NOT KEEP THE USB DEBUGGING TOOL ON ALL THIS TIME !
Can anybody help me with a solution to this ! Please
When you have that error logo, press your volume button and then power button and release it immediately. I think thats how you get into recovery mode/bootloader menu. If this doesn't work, try its vice versa because its been a long time since I've gone ito recovery mode/bootloader menu.
rooter789 said:
Dear all kind developers ,
I went to the recovery mode of my asus zenpone 2 and wipe of the data from it.
After I clicked data wipe it did not continued , it was stuck for like 20 minutes and I restarted the phone .
After that every time I try to open it or go to recovery I cannot open the phone. It only shows an android logo and an error.
I can go to the boot loader menu .
I have already searched the whole internet and found I solution for it , which I have to
* Download intel driver, and some abd files
* Enable Usb debugging and switch of the phone
* Go to boot loader and switch volume up until it shows fastboot
* Connect the phone via usb and open the adb files in cmd
* Type fast boot remove cache in the cmd
And it says that the phone will be alright after the process !
BUT, I DID NOT KEEP THE USB DEBUGGING TOOL ON ALL THIS TIME !
Can anybody help me with a solution to this ! Please
Click to expand...
Click to collapse
When you get to the Android with "ERROR" underneath, hold power and press volume up. It should go to recovery. Try clearing cache again from recovery.
If that doesn't work, go and get the latest version of the rom from the ASUS site, put it on a FaAT32 formatted sd card (rename to MOFD_SUPDATE) and put in phone. Go to recovery and flash rom from sd card.
Otherwise use fastboot and download an image, pre-rooted images available in Original Android Developement, thankyou Shakalaka, and flash from fastboot with command "fastboot flash system system.img" (make sure you put the system.img file in the same directory so you don't have to go hunting).
Solution found !
I've found a solution for this problem
All you need to find is a same device which is normal or BUY a new one ! OR BEG,Borrow, or steal from a friend
Find a asus zenfone 2 from a friend and enable usb debugging
Download intel driver
Just google it
Download Abd driver installer from the link bellow
Just google it
Just enable the usb debugging mode from the phone which you found
Open the adb driver intaller and fetch the abd driver directly from the installer for your asus phone
After that, download the following adb interface
Google it like " Abd interface for asus fastboot"
Then, extract the file , hold shift and right click the folder you will see a option in cmd option
Click that and a cmd window will be opened
Turn off your phone
Hold volume up and power button
After the phone vibrates realease from power button and keep holding volume up button
Boot loader will open and press volume up until you see "continue in fastboot mode"
Keep it the mode and connect your device to pc
It will directly intstall usb driver and adb driver after that
Just go back to your pc and type "fastboot format cache" and the process will continue
You will know when the process is over from the cmd in your pc
After that reboot your phone and you will still see the error
Click power and volume up button and the recovery mode will apear
Just wipe your data and every thing is going to be ALRIGHT
I was recently planning to install Miui 7 on my Fire Phone. So, i installed safestrap 4.01.
1. I opened safestrap recovery mode
2. I wiped (First screen of Safestrap recovery mode)
3. I installed Cleansystempartition.zip
and then i don't know why, but i lost my mind and decided not to install Miui 7 and i went back and clicked on reboot.
So, now my Amazon Fire phone is stuck at boot logo and i can't even enter recovery mode.
It doesn't respond when connected to PC. It is charging and again when i boot again get stuck on boot logo.
Please reply ASAP.
Erictic67108 said:
I was recently planning to install Miui 7 on my Fire Phone. So, i installed safestrap 4.01.
1. I opened safestrap recovery mode
2. I wiped (First screen of Safestrap recovery mode)
3. I installed Cleansystempartition.zip
and then i don't know why, but i lost my mind and decided not to install Miui 7 and i went back and clicked on reboot.
So, now my Amazon Fire phone is stuck at boot logo and i can't even enter recovery mode.
It doesn't respond when connected to PC. It is charging and again when i boot again get stuck on boot logo.
Please reply ASAP.
Click to expand...
Click to collapse
What you need:
1 x USB Cable, 1 x PC, 1 x Fire Phone update bin, adb and correctly installed drivers. GOOGLE
How too:
1. Ensure phone is turned OFF
2. Plug the USB cable into your phone.
3. Press and keep held the Volume UP (+) button only
4. Now plug the other end of the USB cable into the PC. (keeping the Volume UP held)
5. The phone will now boot into recovery and you can let go of the volume button.
6. Select "apply update from ADB"
7. type
Code:
adb sideload your-firmware-version.bin
Use google or search the Fire Phone threads on how to install adb and drivers etc etc.
bigrammy said:
What you need:
1 x USB Cable, 1 x PC, 1 x Fire Phone update bin, adb and correctly installed drivers. GOOGLE
How too:
1. Ensure phone is turned OFF
2. Plug the USB cable into your phone.
3. Press and keep held the Volume UP (+) button only
4. Now plug the other end of the USB cable into the PC. (keeping the Volume UP held)
5. The phone will now boot into recovery and you can let go of the volume button.
6. Select "apply update from ADB"
7. type
Code:
adb sideload your-firmware-version.bin
Use google or search the Fire Phone threads on how to install adb and drivers etc etc.
Click to expand...
Click to collapse
Thanks for your time, but i couldn't understand how ADB is used. I installed adb drivers (tried bunch of times) but can't figure out how to do steps you suggested.
Could you please elaborate in detailed step-by-step, or provide me some revalent link so that I (noob) could understand easily. Once again thanks for help !
Code:
Is there any way i can ensure that proper drivers are installed for my Fire Phone?
Since i understood how adb is used, I categorized further remaining problem into two type:-
1. If I hadn't installed right drivers...
I tried installing driver from different source but i failed (i guess).
So anyone can provide me link for Drivers for Fire Phone?
2. If i have installed right drivers then :
I tried steps as you suggested but my phone won't boot into recovery mode. When i connect Phone to my pc holding volume + , It shows charging symbol as usual.
If i am doing the process in wrong way, please correct me. I will be waiting for helps...:crying:
@Erictic67108
https://forum.xda-developers.com/fire-phone/help/cm-11-to-fire-os-question-t3198620/post62768812
https://forum.xda-developers.com/fire-phone/help/cm-11-to-fire-os-question-t3198620/post62844581
Firmware for sideload you can download from Amazon. Your need last version.
https://www.amazon.com/gp/help/customer/display.html?nodeId=201607550
Kramar111 said:
@Erictic67108
https://forum.xda-developers.com/fire-phone/help/cm-11-to-fire-os-question-t3198620/post62768812
https://forum.xda-developers.com/fire-phone/help/cm-11-to-fire-os-question-t3198620/post62844581
Firmware for sideload you can download from Amazon. Your need last version.
https://www.amazon.com/gp/help/customer/display.html?nodeId=201607550
Click to expand...
Click to collapse
I cannot go to recovery mode. I tried many times/ways but i couldn't access. Please help.
Erictic67108 said:
I cannot go to recovery mode. I tried many times/ways but i couldn't access. Please help.
Click to expand...
Click to collapse
If Fire Phone detected in Windows Device Manager with PID 9008 you can't do anything (as i know). PID 9006 give you a little chance.
Erictic67108 said:
I cannot go to recovery mode. I tried many times/ways but i couldn't access. Please help.
Click to expand...
Click to collapse
Talk with amazon for warranty, if you are from europe, talk with amazon.de, you will get a new one, but u must return to amazon germany the bricked fire phone.
Erictic67108 said:
I cannot go to recovery mode. I tried many times/ways but i couldn't access. Please help.
Click to expand...
Click to collapse
Your only hope to revive this phone is to get into the stock recovery.
If you wiped the stock recovery or messed with it then your screwed as there is no PC flashtool like odin, spflashtool, etc etc that works on the fire phone that I am aware of so you need the stock recovery to be functional.
To get into recovery re-read post #2 HERE very carefully on how to do it. :fingers-crossed:
There is no need to PM me just simply quote me in this thread and I will then get notified.
You also need to provide as much info as possible things such as screenshots, photo's, Videos, logs etc etc as these will help when people try to assist you.
Once you are in stock recovery we can move on.
I quit guys. I just can't get that thing on recovery mode. I tried several times, tried other ways but nope. My phone is not giving a damn ****. Its just gets stuck on boot screen logo. That's all. I guess, i won't get my phone returned/exchanged since had i rooted it which violates its warranty.
Am having thee same issue
Erictic67108 said:
I quit guys. I just can't get that thing on recovery mode. I tried several times, tried other ways but nope. My phone is not giving a damn ****. Its just gets stuck on boot screen logo. That's all. I guess, i won't get my phone returned/exchanged since had i rooted it which violates its warranty.
Click to expand...
Click to collapse
i also quit gyz i tried almost every thing but its stuck on amazon logo
Weirdly enough -my gfs fire phone started exhibiting the same exact issue just yesterday(amazon logo blinks on start up and doesnt go any further no matter how long you wait) and this is the first link google gave on the problem. Did anyone find a resolution to this? She loves this phone and I already replaced battery once few months ago.