Database Users

How I was able to unbrick my Kindle Fire

Hi everyone.
I managed to brick my kindle fire within an hour of purchasing it, but using the suggestions on this forum, I was able to get it back up and running in a few hours.
The method that I had to use involved suggestions grabbed from several threads, so I wanted to provide instructions on exactly how I managed to fix mine in case someone ends up in the same situation as me.
For starters, I had just updated my Kindle Fire to 6.2.1 and I was messing around with trying to get the google app manager installed. I rooted the device, and I was changing permissions in the /system/app directory when the device crashed and became stuck on the boot animation. I did not have TWRP installed at the time.
So if you are like me, or in a similar situation, this may be applicable.
These instructions assume that you have adb on your computer.
First, ensure that you are able to communicate with your device using ADB. Verify this by using the command:
adb devices
Click to expand...
Click to collapse
or by using the kindle fire utility and ensuring that the status is online.
If you are not able to communicate with your device AND have the boot animation (right to left reflection across the "Kindle Fire" logo text), you likely have a driver issue.
Several possible ways to resolve this. First, I recommend going to device manager and unistalling the driver for the android phone adb interface. Unplug the kindle fire and plug it in again. The device should show up without a driver as "kindle". Manually apply the proper driver again and check the adb connection. If this does not work, uninstall the driver again and add 0x18d1 at the end of adb_usb.ini on a line underneath "0x1949" and reapply the driver. Toss in a few shutdowns in between some of these steps if you are still having trouble. Hopefully you now have a connection to your device.
If you are not able to communicate with your device AND do not have the boot animation (right to left reflection across the "Kindle Fire" logo text), your kindle fire is in the wrong bootmode (likely fastboot).
To fix this, download fastboot.exe (if you don't already have it) and run the following command, even if you don't have an adb connection)
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
or if that doesn't work
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
Click to expand...
Click to collapse
Your kindle fire should restart and now be stuck at the logo with animation, and you should have the ability to communicate with your device through adb now.
Now, you should download the kindle fire firmware (6.2.1 as of the time of writing this) from http://www.amazon.com/gp/help/customer/display.html?nodeId=200790620. Rename this to update.zip and drop it in the same directory as adb.exe on your pc. Execute the following command.
adb push update.zip /sdcard/
Click to expand...
Click to collapse
Now, you need to use fbmode to enable the fastboot mode, per pokey9000's instructions at http://forum.xda-developers.com/showthread.php?p=20755810
Assuming that that was able to complete successfully, you need to flash TWRP 2.0 per pyrostic's instructions at http://rootzwiki.com/topic/12363-ho...our-kindle-fire/page__pid__301703#entry301703
You now should be stuck at a screen with a yellow triangle. Pressing the power button several times until it turns orange should bring you into the recovery screen. Do the following:
Wipe cache
Wipe dalvik cache
Factory reset
Go back to the home screen and select install -> update.zip
And when that's done, you can tell it to reboot.
It'll think for a minute or two at the kindle fire boot, and then it will go into the initial setup screen. You're now the proud owner of a working fact0ry default kindle fire!
Quick note: I wrote this from memory quickly to try to help anyone experiencing problems. I'm no android expert, so if there are ways to improve on this or corrections to be made, please let me know so that the community can benefit.
And I don't want to appear to take undue credit for any of these instructions. I did not come up with anything on this guide on my own, everything came from various threads on this forum. These are just the steps that I followed to successfully bring my kindle fire back from death.

Man, My Kindle Fire does not even get detected by my PC

Now, you need to use fbmode to enable the fastboot mode, per pokey9000's instructions at http://forum.xda-developers.com/show...php?p=20755810
Assuming that that was able to complete successfully, you need to flash TWRP 2.0 per pyrostic's instructions at http://rootzwiki.com/topic/12363-how...03#entry301703
You now should be stuck at a screen with a yellow triangle. Pressing the power button several times until it turns orange should bring you into the recovery screen. Do the following:
Wipe cache
Wipe dalvik cache
Factory reset
Go back to the home screen and select install -> update.zip
And when that's done, you can tell it to reboot.
It'll think for a minute or two at the kindle fire boot, and then it will go into the initial setup screen. You're now the proud owner of a working fact0ry default kindle fire!
****When I run the fbmode I am getting stuck on the boot logo screen. Can someone please help me??

that is normal - you are in fastboot mode now - adb commands don't work in this mode - fastboot commands do - resume with the description ...

Thanks for your post.
I also "bricked" my kindle the day I got it but my issue was not having the correct drivers installed when I started the rooting process. My drivers would recognize the Kindle when it was booted normally but when it went into fastboot mode the Kindle would just show as "Unknown Device" in device manager. In windows you can't remove the drivers for unknown device so I had no way of backing out the old drivers.
What I ended up doing was grabbing my other laptop and making sure I had the correct drivers installed, then connected the kindle and was able to back it out of fastboot mode.
---------- Post added at 09:05 AM ---------- Previous post was at 09:04 AM ----------
umarsl said:
Man, My Kindle Fire does not even get detected by my PC
Click to expand...
Click to collapse
Does it show up as "unknown Device" in device manager?

you can uninstall the drivers
win 7:
http://www.petri.co.il/removing-old-drivers-from-vista-and-windows7.htm
xp:
http://www.techrepublic.com/article/removing-unused-device-drivers-from-windows-xp-machines/6017628

Just wanted to say thanx for the post. I ran into the exact same condition that the op did where I inadvertently screwed up the permissions on the /system/app directory which caused the kf to wig out and brick. I wished I had seen your post earlier because I ended up going to many posts and piecing together the information which was a little confusing at times. The op is great and I just wanted to point out two observations that seemed to me the most confusing working through the issue and getting it unbricked and hopefully will bring some clarity for folks.
1. Understanding the different states of the "kindle fire" logo.
- Shimmering animation and appears to loop = normal boot mode and is the state that you should be able to communicate with adb. This is the state where you can push files to the kf like twrp and fbmode which is what is needed to get kf in fastboot mode when bricked like this.
- The logo is static and does not "wink" out or loop = fastboot mode. This is when you use fastboot commands on your PC to change boot modes and also execute files such as twrp to get it installed once you pushed it to the kf with adb.
2. USB Drivers.
- This can be a real killer. After playing with this for hours, the one thing that I found that helped the most was when the driver stopped working I would unplug the kf from the PC and then hard reboot the kf (hold on/off ~20 seconds) then just plug back in, don't use on/off. Keep the device manager open on the PC and watch. You will soon start to see a pattern when you have the right driver and do this a few times.
Once these things are ironed out all eventually works out. BTW, this occurred after my kf was upgraded to 6.2.2. So the instructions and tools and everything else you will find still works. Good luck to anyone working through this issue. Just remember, if you can communicate with it, it's almost certain there is a way to recover it.

[Q] Kindle fire totally dead

Sorry to open a new thread...I've been searching for a similar problem with no result...
My KF was bricked in a bootloop with acces through adb or fasboot but i can't solve the problem via KFU o Unbrick tool, so I was trying to install TWRP
The last command a typed in cmd was (big mistake):
"fastboot flash bootloader twrp-blaze-2.0.0RC0.img"
after that the KF shuts down forever... no charging light, no adb, no fastboot, nothing...
plz any idea to revive my KF???

dietomant said:
Sorry to open a new thread...I've been searching for a similar problem with no result...
My KF was bricked in a bootloop with acces through adb or fasboot but i can't solve the problem via KFU o Unbrick tool, so I was trying to install TWRP
The last command a typed in cmd was (big mistake):
"fastboot flash bootloader twrp-blaze-2.0.0RC0.img"
after that the KF shuts down forever... no charging light, no adb, no fastboot, nothing...
plz any idea to revive my KF???
Click to expand...
Click to collapse
Make/buy a factory cable and fastboot the proper bootloader from the stock update package.
Sent from my myTouch_4G_Slide using XDA App

I was a little confused about this myself at one point... There are a bunch of 'low-level' partitions that are really important not to mix up.
'bootloader' contains the basic bootloader, which loads everything else and you should pretty much never touch it, except to install FireFireFire.
'recovery' is the partition where TWRP or ClockWorkMOD should go.
Finally, 'boot' is what launches Android.
I almost made the same mistake last night installing CWM (it was 2am and my brain+fingers were being stupid)
Anyway OP, it sounds like a factory cable would be your best bet, unless that just tells something to the bootloader, in which case getting a warranty replacement from Amazon might be your only option...
Just remember next time that you want to flash recovery ;-)

dietomant said:
Sorry to open a new thread...I've been searching for a similar problem with no result...
My KF was bricked in a bootloop with acces through adb or fasboot but i can't solve the problem via KFU o Unbrick tool, so I was trying to install TWRP
The last command a typed in cmd was (big mistake):
"fastboot flash bootloader twrp-blaze-2.0.0RC0.img"
after that the KF shuts down forever... no charging light, no adb, no fastboot, nothing...
plz any idea to revive my KF???
Click to expand...
Click to collapse
I have had a similar situation on my KF. I used a factory cable to solve my issue. Send a private message to SkOrPn with Factory Cable in the subject. His cable is well built and arrived very quick via USPS. Not to mention he sells them at a good price.

Finally I got my factory cable.... but the problem is not fixed..
I connect the Factory cable to KF...in am at the command prompt and no matter what fastboot instruction I put always the same message "waiting for device"
If anyone knows what I should do I really appreciate it...

Try adding the device ID 0bb4:0c01 to your USB configuration
Sent from my Amazon Kindle Fire using Tapatalk

dietomant said:
Finally I got my factory cable.... but the problem is not fixed..
I connect the Factory cable to KF...in am at the command prompt and no matter what fastboot instruction I put always the same message "waiting for device"
If anyone knows what I should do I really appreciate it...
Click to expand...
Click to collapse
I think you've gotten somewhat misleading information from the previous posters. The factory cable will always put the KF into fastboot mode if (this is a HUGE if) the device has a working bootloader. The bootloader is the piece of software that will put the device into fastboot mode, so without that the factory cable cannot do its job.
I'm quite surprised you were able to break the bootloader by trying to flash that image onto it. In my experience, fastboot flash checks for the size and would fail when I tried to give it something > 256KB for the bootloader... but that's neither here nor there...
If you cannot get a "kindle fire" or the "yellow triangle" to come up on the display, your bootloader is broken. Your last hope is to open up the case and use usbboot to temporarily load a bootloader into memory via USB and use that to flash a permanent bootloader. You'll probably need a case pry tool to do this fairly safely and linux installed because I don't believe usbboot was ever ported to Windows.
Additional information: http://forum.xda-developers.com/showthread.php?t=1405052

Nexus 7 Bootloader Locked!

After Android tried to update itself to the newest version, it seemed that this failed and has caused a "boot failed" message. The tablet refuses to go into recovery mode, its marked as red. The only accessible mode is going into bootloader. After reading many forums and trying my luck with toolkits of all sorts (Nexus 7 Root Toolkit, Nexus Root Toolkit, Android SDK commands), the bootloader refuses to unlock. I have successfully installed the usb drivers since my pc recognizes the device. fastboot devices recognizes the devise but adb devices doesn't. The bootloader is locked and nothing else is accessible, whats worse is that through all of these toolkits and commands bootloader refuses to unlock, trying to unlock it always results in a failure message (unknown error). Commands such as format, unlock or erase fail in reviving the system. Anyone have any experience with this? I have searched for over a week now and im terribly frustrated by this. :silly:

AndiS21 said:
After Android tried to update itself to the newest version, it seemed that this failed and has caused a "boot failed" message. The tablet refuses to go into recovery mode, its marked as red. The only accessible mode is going into bootloader. After reading many forums and trying my luck with toolkits of all sorts (Nexus 7 Root Toolkit, Nexus Root Toolkit, Android SDK commands), the bootloader refuses to unlock. I have successfully installed the usb drivers since my pc recognizes the device. fastboot devices recognizes the devise but adb devices doesn't. The bootloader is locked and nothing else is accessible, whats worse is that through all of these toolkits and commands bootloader refuses to unlock, trying to unlock it always results in a failure message (unknown error). Commands such as format, unlock or erase fail in reviving the system. Anyone have any experience with this? I have searched for over a week now and im terribly frustrated by this. :silly:
Click to expand...
Click to collapse
do it the right way, dont use toolkits.
to unlock the bootloader, go into the bootloader(fastboot), connect the divice via usb, type..
fastboot devices(to make sure your device is visable)
fastboot oem unlock(to unlock the bootloader)
if you get an error, reboot the bootloader and try again. i had an error the first time on my replacement seven, second time it unlocked.

simms22 said:
do it the right way, dont use toolkits.
to unlock the bootloader, go into the bootloader(fastboot), connect the divice via usb, type..
fastboot devices(to make sure your device is visable)
fastboot oem unlock(to unlock the bootloader)
if you get an error, reboot the bootloader and try again. i had an error the first time on my replacement seven, second time it unlocked.
Click to expand...
Click to collapse
Thanks for the reply, i tried this several times, each time rebooting bootloader, but the command still posts an error in unlocking the bootloader. Recovery and Restart bootloader are marked in red font, Start is in Green, Power off White. I also tried flashing the recovery, since its inaccessible but because of bootloader being locked in won't allow me. :S Anything else you know that can be done ?

Reflash the bootloader?
edit: making VERY sure that you DON'T erase the existing bootloader first.

Try a manual update
AndiS21 said:
After Android tried to update itself to the newest version, it seemed that this failed and has caused a "boot failed" message. The tablet refuses to go into recovery mode, its marked as red. The only accessible mode is going into bootloader. After reading many forums and trying my luck with toolkits of all sorts (Nexus 7 Root Toolkit, Nexus Root Toolkit, Android SDK commands), the bootloader refuses to unlock. I have successfully installed the usb drivers since my pc recognizes the device. fastboot devices recognizes the devise but adb devices doesn't. The bootloader is locked and nothing else is accessible, whats worse is that through all of these toolkits and commands bootloader refuses to unlock, trying to unlock it always results in a failure message (unknown error). Commands such as format, unlock or erase fail in reviving the system. Anyone have any experience with this? I have searched for over a week now and im terribly frustrated by this. :silly:
Click to expand...
Click to collapse
You can try a manual update. Download the update and run adb sideload. That was not working for me, cause my Nexus it's allready updated, but hopefully it will work for you.

dave_uk said:
Reflash the bootloader?
edit: making VERY sure that you DON'T erase the existing bootloader first.
Click to expand...
Click to collapse
fortunatley though bootloader doesn't allow any command even the erase, it wouldn't allow me, nor formatting it as well. So i think the bootloader is intact. This is the screen i get from pressing Power and Vol Down.

pettymro said:
You can try a manual update. Download the update and run adb sideload. That was not working for me, cause my Nexus it's allready updated, but hopefully it will work for you.
Click to expand...
Click to collapse
As i have come to learn, adb can only function when debugging is enabled, in my device it wasn't unabled. Also the recovery program cannot be opened so sideloading through commands cannot be done. At least according to how some forums described the How To sideload through adb

try do it on another pc

AndiS21 said:
Thanks for the reply, i tried this several times, each time rebooting bootloader, but the command still posts an error in unlocking the bootloader. Recovery and Restart bootloader are marked in red font, Start is in Green, Power off White. I also tried flashing the recovery, since its inaccessible but because of bootloader being locked in won't allow me. :S Anything else you know that can be done ?
Click to expand...
Click to collapse
Can you post here the error message?

Israafiyl said:
Can you post here the error message?
Click to expand...
Click to collapse
Sure here it is. When i type in fastboot oem unlock, the message to unlock on my nexus comes up and when i click yes to unlock does the procedure start and end with failure.

AndiS21 said:
Sure here it is. When i type in fastboot oem unlock, the message to unlock on my nexus comes up and when i click yes to unlock does the procedure start and end with failure.
Click to expand...
Click to collapse
I don't know if fastboot let you flash the stock bootloader/recovery without unlocking but you may try:
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot flash recovery recovery-stock-jro03d-nakasi.img

Israafiyl said:
I don't know if fastboot let you flash the stock bootloader/recovery without unlocking but you may try:
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot flash recovery recovery-stock-jro03d-nakasi.img
Click to expand...
Click to collapse
thanks for the files, but bootloader won't allow me to change a single thing on it. Trying to flash recovery or the bootloader results in Failure result:bootloader locked!. :S

AndiS21 said:
thanks for the files, but bootloader won't allow me to change a single thing on it. Trying to flash recovery or the bootloader results in Failure result:bootloader locked!. :S
Click to expand...
Click to collapse
try one more time with a different port/pc if it daesn't work it may be a hardware fault, i think a corrupted sd.
(you will have to send it to warranty but don't worry, asus have a really good assistence, you may have a new nexus in a less than 2 days)

Manual update
AndiS21 said:
As i have come to learn, adb can only function when debugging is enabled, in my device it wasn't unabled. Also the recovery program cannot be opened so sideloading through commands cannot be done. At least according to how some forums described the How To sideload through adb
Click to expand...
Click to collapse
Use the volume up/down keys to navigate to "Recovery mode", then press the power button.
When the Android with the red exclamation point appears, hold down power first, followed quickly by volume down and volume up. (So that to start, you're holding down power, then you're holding down all three). After 2-3 seconds, release all three keys.
Use the volume up/down keys to select "apply update from ADB," then press power to select it.
On your computer, open up a command prompt or terminal window.
Using the command line, navigate to the folder containing the ADB executables and the update file.
type:
adb.exe sideload <update filename>
On my Nexus with Jelly 4.2 usb debugging is not enabled too, but I still get the option in recovery mode menu. Operation not succesful cause I cannot upgrade from 4.2 to 4.2. I will wait for another update and then try it again. Good luck!

Israafiyl said:
try one more time with a different port/pc if it daesn't work it may be a hardware fault, i think a corrupted sd.
(you will have to send it to warranty but don't worry, asus have a really good assistence, you may have a new nexus in a less than 2 days)
Click to expand...
Click to collapse
I tried it on the laptop too, even changed the drivers to universal naked drivers, but nothing! Restart bootloader is with red, clicking it wont reboot the tablet, also recovery mode red, the only working button is the Start (green) but that leads to boot failure and power off.

pettymro said:
Use the volume up/down keys to navigate to "Recovery mode", then press the power button.
When the Android with the red exclamation point appears, hold down power first, followed quickly by volume down and volume up. (So that to start, you're holding down power, then you're holding down all three). After 2-3 seconds, release all three keys.
Use the volume up/down keys to select "apply update from ADB," then press power to select it.
On your computer, open up a command prompt or terminal window.
Using the command line, navigate to the folder containing the ADB executables and the update file.
type:
adb.exe sideload <update filename>
On my Nexus with Jelly 4.2 usb debugging is not enabled too, but I still get the option in recovery mode menu. Operation not succesful cause I cannot upgrade from 4.2 to 4.2. I will wait for another update and then try it again. Good luck!
Click to expand...
Click to collapse
recovery mode cannot be opened, the text font is red on the tablet and clicking it does nothing. :S

Also tried to completley flash the device but unable to. Going back and doing an fastboot oem unlock yields the same feedback.

Unlock Bootloader on 4.2
Hello, I was wondering if the bootloader in 4.2 can be unlocked the same way as it was on 4.1.2? I recently got a new nexus 7 and updated to 4.2.
Thanks and Cheers!

After some research into my issue, i have discovered that other users have posted "unbricking" solutions through a program called nvflash, when the device is put in APX mode. But unfortunatley i've yet to find a nvflash solution for nexus 7. I will experiment with the commands and what the others have reported as a solution.

ErnestoV31 said:
Hello, I was wondering if the bootloader in 4.2 can be unlocked the same way as it was on 4.1.2? I recently got a new nexus 7 and updated to 4.2.
Thanks and Cheers!
Click to expand...
Click to collapse
Yes it can.
Sent from my GT-I9300 using Tapatalk 2

[Q] Permanent problem with Unlocking Bootloader Nexus S

Hi guys,
I searched forums, web with no positive results. So I start a new thread. Here is the situation: one day my Nexus S (Worldwide edition) froze on restarting with the Google Logo on the screen. Every time I try to turn the phone on it stacks at Google logo. When in the fastboot mode the status is Locked. Every time I try fastboot oem unlock I get Phone’s prompt with Yes or Not to unlock bootloader and after choosing Yes, the status doesn’t change to Unlock. Tried on Linux, Mac, Windows (drivers installed successfully), the same result. Tried to force Flash Stock + Unroot in Wugfresh, doesn’t work due to the Locked Bootloader.
typing "adb devices" in cmd (should return the device number) shows:
List of devices attached
......
Empty line above
Any word of advise how to force Unlocking the Bootloader would be greatly appreciated. Please help. Thank you!

alpheus said:
Hi guys,
I searched forums, web with no positive results. So I start a new thread. Here is the situation: one day my Nexus S (Worldwide edition) froze on restarting with the Google Logo on the screen. Every time I try to turn the phone on it stacks at Google logo. When in the fastboot mode the status is Locked. Every time I try fastboot oem unlock I get Phone’s prompt with Yes or Not to unlock bootloader and after choosing Yes, the status doesn’t change to Unlock. Tried on Linux, Mac, Windows (drivers installed successfully), the same result. Tried to force Flash Stock + Unroot in Wugfresh, doesn’t work due to the Locked Bootloader.
typing "adb devices" in cmd (should return the device number) shows:
List of devices attached
......
Empty line above
Any word of advise how to force Unlocking the Bootloader would be greatly appreciated. Please help. Thank you!
Click to expand...
Click to collapse
It looks like your device is not recognized in Fastboot mode...
Have you turned on USB Debugging while connecting PC and Allow in Device when Prompt some message ..
Go to fastboot mode and write this command... fastboot devices
If it will give you a message like this
List of devices
1235456785164
Then your devices is successfully recognized...:good:

It is not recognized by adb devices, but:
fastboot devices - gives the following output:
ERROR: could not get pipe properties
3331E6EBCA6000EC fastboot
Click to expand...
Click to collapse
fastboot oem unlock - gives the following:
ERROR: could not get pipe properties
...
FAILED (remote: Erase Fail)
finished. total time: 4.753s
Click to expand...
Click to collapse

alpheus said:
It is not recognized by adb devices, but:
fastboot devices - gives the following output:
fastboot oem unlock - gives the following:
Click to expand...
Click to collapse
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data

demkantor said:
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
Click to expand...
Click to collapse
Thanks, I tried 3 different cables on 3 different operating systems, with the same problem unlocking the fastboot. When I send fastboot oem unlock the device opens a prompt with Yes or No choice, but after choosing Yes, it stays Locked

Something indeed is strange...
So fastboot is for bootloader and adb is for within os and in recovery.
Try booting into recovery and see if adb works, also boot normal into your bootloop and see if adb works there too

demkantor said:
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
Click to expand...
Click to collapse
demkantor said:
Something indeed is strange...
So fastboot is for bootloader and adb is for within os and in recovery.
Try booting into recovery and see if adb works, also boot normal into your bootloop and see if adb works there too
Click to expand...
Click to collapse
Loading into basic recovery and trying to wipe data/factory reset - doesn't work. adb devices returns the following output:
./adb-linux devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
****empty line here****
Somehow, adb doesn't recognize the device, whereas fastboot devices shows it.
Is there a way to flash new bootmode with the currently locked bootloader?
Thank you!

alpheus said:
Loading into basic recovery and trying to wipe data/factory reset - doesn't work. adb devices returns the following output:
./adb-linux devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
****empty line here****
Somehow, adb doesn't recognize the device, whereas fastboot devices shows it.
Is there a way to flash new bootmode with the currently locked bootloader?
Thank you!
Click to expand...
Click to collapse
I am damn Sure What's Your problem is, ADB is not working..
PROCEDURE:-
1) Download My attachement and unzip it and Place it in Folder...
See image 1.png
2) Go to that folder and Press CTRL+SHIFT+ Right click on mouse and Select Open Command Window here..
See image 2.png
3) Now type here Fastboot devices and Now you will get Those list of devices Number..
See image 3.png
If Everything will be done as Procedure and you will get List of devices Number... Now, You type those command for Unlocking bootloader and Root Your Devices...:good:
Hope this Guide will help..

UPDATE (resolved)
Here is an update. Hope this would help others with similar issue, as I've read many threads and folks complaining that they weren't able to unlock fastboot and further root their Nexus S, and who can't boot the phone, which stacked with Google Logo (soft loop). This was the case with my device and finally I got it resolved. I've read some guy tried to hit the phone and after that he was able to boot phone normally. It related to some hardware electrical circle issue. Anyways, I tried to hit my phone by placing it under the direct sun in balcony for some time until the phone got hot and then power it on. And ooops, my phone started booting passed by that Google Logo which was the good sign. Once the phone booted up, I went ahead and activated USB debugging and restarted the phone into the Fastboot mode. while the phone was still hot and in Fastboot mode I run "fastboot oem unlock" and hey, fastboot is Unlocked! Again, this was done while the phone was hot, any previous attempts (read above) weren't successful. From that point, I went ahead and rooted my Nexus S by Nexus Root Toolkit, available on wugfresh.com/nrt, without a slightest problem. Now my phone is fully rooted, bootable and working fine. I thank all who replied to my thread and tried to help and hope this info would help someone with the similar issue.

Rushabh22 said:
I am damn Sure What's Your problem is, ADB is not working..
PROCEDURE:-
1) Download My attachement and unzip it and Place it in Folder...
See image 1.png
2) Go to that folder and Press CTRL+SHIFT+ Right click on mouse and Select Open Command Window here..
See image 2.png
3) Now type here Fastboot devices and Now you will get Those list of devices Number..
See image 3.png
If Everything will be done as Procedure and you will get List of devices Number... Now, You type those command for Unlocking bootloader and Root Your Devices...:good:
Hope this Guide will help..
Click to expand...
Click to collapse
Thank you for your help and suggestions.

Q Mobile X 32
bootloader oem unlock problem
plz help

Q-mobile said:
Q Mobile X 32
bootloader oem unlock problem
plz help
Click to expand...
Click to collapse
Wrong device thread..
Try here..
https://forum.xda-developers.com/showthread.php?t=2363923

Setting.Out said:
Wrong device thread..
Try here..
https://forum.xda-developers.com/showthread.php?t=2363923
Click to expand...
Click to collapse
can you help me in rooting Qmobile x32

Q-mobile said:
can you help me in rooting Qmobile x32
Click to expand...
Click to collapse
That thread didn't help?

Here's what the guide says...

not able to boot into bootloader/recovery/fastboot

So I looked around here and on the interwebz to find an answer to my question before I decided to state my question to you.
I just acquired the Sony Xperia X Compact (F5321; Android 7.1.1).
In order to get TWRP on it, I consulted a lot of online guides including those described here. Of which I thought this would be the most suitable:
https://forum.xda-developers.com/x-compact/development/recovery-twrp-3-1-1-xperia-x-compact-t3640914
So after:
having adb tools and fastboot incl. drivers (also tried the minimal)
developer options -- oem unlocking -- bootloader allowed to be unlocked; and developer options -- USB debugging -- debug mode when USB is connected
checking the service *#*#7378423#*#* , which shows "bootloader unlock allow : YES"
phone connected to PC
I encounter the following problem.
While the sony stock rom it comes with is running,
via adb I am able to feed the phone the following command with the respective outcome:
adb reboot fastboot (reboots into Android, with the LED lighting briefly up in red)
adb reboot recovery (reboots into Android, with the LED lighting briefly up in red)
adb reboot bootloader (boots down, but does not boot into Android; there is only a black screen and the LED is on and stays blue)
in any of those states, if I enter an adb command there is always this output as if the phone wasn't connected or recognized or off:
error: device '(null)' not found
So I am able to communicate commands to the phone when it is running. I assume this means my drivers are all in order, right?
Also. While it is off and disconnected from the PC.
I keep the power button and the volume down button pressed, the Sony Logo comes up and after that it takes turns with a black screen as long as I keep pressed.
I keep the power button and the volume up button pressed. It is followed by one short vibration, another short one, and the three in a row. And then no further reaction.
I feel pretty dumb, can anyone help me with how to enter any of the alternative boot options? Thanks in advance!
I just don't know if there is something I am not seeing or if there is plainly something wrong with the phone. Not knowing this for sure is driving me crazy. Hopefully this is something others might learn from, as well.
____________
little edit about the text format

From your description, it seems like TWRP was not installed correctly. But don't worry, on this phone you do not have to install the recovery to use it. You can boot straight into recovery from your PC while the phone is in 'fastboot' mode. The 'fastboot' mode is what you get when you do 'adb reboot bootloader'. The screen off, blue LED is signalling that the phone is ready for fastboot commands. You can then run:
Code:
fastboot boot <recovery image file>
The phone should load and run the recovery.
Please note that adb will not see your device while it is in fastboot mode. Likewise, fastboot does not work while the phone is accessible through adb. adb support comes from the ROM, but TWRP also supports adb, so you can also use adb while in TWRP.

Rendini said:
So I looked around here and on the interwebz to find an answer to my question before I decided to state my question to you.
I just acquired the Sony Xperia X Compact (F5321; Android 7.1.1).
In order to get TWRP on it, I consulted a lot of online guides including those described here. Of which I thought this would be the most suitable:
https://forum.xda-developers.com/x-compact/development/recovery-twrp-3-1-1-xperia-x-compact-t3640914
So after:
having adb tools and fastboot incl. drivers (also tried the minimal)
developer options -- oem unlocking -- bootloader allowed to be unlocked; and developer options -- USB debugging -- debug mode when USB is connected
checking the service *#*#7378423#*#* , which shows "bootloader unlock allow : YES"
phone connected to PC
I encounter the following problem.
While the sony stock rom it comes with is running,
via adb I am able to feed the phone the following command with the respective outcome:
adb reboot fastboot (reboots into Android, with the LED lighting briefly up in red)
adb reboot recovery (reboots into Android, with the LED lighting briefly up in red)
adb reboot bootloader (boots down, but does not boot into Android; there is only a black screen and the LED is on and stays blue)
in any of those states, if I enter an adb command there is always this output as if the phone wasn't connected or recognized or off:
error: device '(null)' not found
So I am able to communicate commands to the phone when it is running. I assume this means my drivers are all in order, right?
Also. While it is off and disconnected from the PC.
I keep the power button and the volume down button pressed, the Sony Logo comes up and after that it takes turns with a black screen as long as I keep pressed.
I keep the power button and the volume up button pressed. It is followed by one short vibration, another short one, and the three in a row. And then no further reaction.
I feel pretty dumb, can anyone help me with how to enter any of the alternative boot options? Thanks in advance!
I just don't know if there is something I am not seeing or if there is plainly something wrong with the phone. Not knowing this for sure is driving me crazy. Hopefully this is something others might learn from, as well.
____________
little edit about the text format
Click to expand...
Click to collapse
Switch the phone off.
To enter fastboot mode: Hold the Volume UP and connect your phone to the USB port of your PC. The blue LED should come on and provided you have correctly installed drivers, you will be able to use fastboot commands.
To enter bootloader/flashmode: Hold Volume DOWN button and plug USB cable to your PC. Green LED should lit up and provided you have correctly installed the drivers, you will be able to use Flashtool, Emma or other software to flash firmware files.

FAILED (remote: Command not allowed)
Hey guys!
First of all, thanks for taking the time!
So, confirming how to enter bootloader/flashmode is much appreciated, since I was very much in doubt about the fact that the screen stayed off. On other devices I always had something on the screen in recovery mode and the like.
Now I know it was problem with the drivers indeed. Also appreciated, the hint that adb and fastboot work separately. While the device was recognized by adb when it was turned on, it was not in fastboot mode because of missing drivers. Finally it is being recognized and I can address the device via fastboot command.
And yet, I have the next brick wall. Any command I send via fastboot is answered by this output:
Code:
FAILED (remote: Command not allowed)
up to this point, I have not found one command that is being acknowledged and triggers another output, so I think it is a general problem. Maybe still with the drivers. Any hints would be celebrated. Anyways, in the meantime I will keep on trying until I succeed or until I get too frustrated and send it back and never try Sony devices again
not kidding XD

Rendini said:
Hey guys!
First of all, thanks for taking the time!
So, confirming how to enter bootloader/flashmode is much appreciated, since I was very much in doubt about the fact that the screen stayed off. On other devices I always had something on the screen in recovery mode and the like.
Now I know it was problem with the drivers indeed. Also appreciated, the hint that adb and fastboot work separately. While the device was recognized by adb when it was turned on, it was not in fastboot mode because of missing drivers. Finally it is being recognized and I can address the device via fastboot command.
And yet, I have the next brick wall. Any command I send via fastboot is answered by this output:
Code:
FAILED (remote: Command not allowed)
up to this point, I have not found one command that is being acknowledged and triggers another output, so I think it is a general problem. Maybe still with the drivers. Any hints would be celebrated. Anyways, in the meantime I will keep on trying until I succeed or until I get too frustrated and send it back and never try Sony devices again
not kidding XD
Click to expand...
Click to collapse
because your bootloader is not unlocked. you have set your bootloader to allow unlocking in developers options, but you need to do the actual unlock using "fastboot unlock" command. you need a unique unlock code from Sony Developers portal and keep in mind that unlocking your device irrevocably deletes DRM keys. it is advisable that you backup your DRM keys before unlocking your device.
the problem is not Sony device, but your unability to read and follow guides and get yourself informed and educated before you dive into trial and error, finaly blaming manufacturer for your own faults...