Develop Bugs

[Q] Please don't hate me... fastboot "brick" on VM

So, I know not supposed to post questions that are lame, but I can't seem to figure this out. I will state my specs/situation:
I am stuck on the first step of installing FFF on my first Kindle Fire 1st gen.
I am on a Macbook Pro Retina 15" mid-2012 (USB3.0/2.0 mix ports only)
I am using KFU on a Win8 64-bit Virtual Machine (VMWare latest version)
The kindle fire is in fastboot mode (I'm pretty sure, at least).
It is stuck on the stock Kindle fire boot-up logo.
install_Drivers was run successfully after enabling unsigned driver installs.
Run.bat was executed
selected Option 5 first, to install FFF
FFF was downloaded by KFU, the Fire rebooted and then got stuck.
As it rebooted, I had forgotten to automatically have my Fire connect to the Virtual Machine, so VMWare prompted my with what system I wanted the fire connected to. I'm not sure if that delay has something to do with the stall and failure of KFU to install FFF or get out of fastboot.
KFU doesn't recognize the Kindle ("waiting for device" message; ADB: Offline; Boot Status:Unknown).
In my "other devices" on Windows Device Manager I see "Base System Device" and "Unknown Device"
My questions are:
1. How do I go about getting it out of fastboot mode even though KFU can't see the device.
2. What was I doing wrong in the first place?
Before you tell me:
I have read through the Guide
I have read through and searched much of the KFU dev thread
I have searched the forums, without a clear solution.
Thank you very much for your help!!!

escoloader said:
2. What was I doing wrong in the first place?
Click to expand...
Click to collapse
This:
I am on a Macbook Pro Retina 15" mid-2012 (USB3.0/2.0 mix ports only)
I am using KFU on a Win8 64-bit Virtual Machine (VMWare latest version)
Click to expand...
Click to collapse
Use breakdroid instead
Sent from my Amazon Kindle Fire HD using Tapatalk 2

soupmagnet said:
This:
Use breakdroid instead
Click to expand...
Click to collapse
How do I get it back to normal booting first?
Thanks for your help!

escoloader said:
How do I get it back to normal booting first?
Thanks for your help!
Click to expand...
Click to collapse
Code:
fastboot -i 0x1949 oem idme bootmode 4000
Code:
fastboot -i 0x1949 reboot

Thepooch said:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
Code:
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
Thank you for the help, but could you please explain how I use that code, step by step if possible?
Thanks a lot
EDIT: I guess I should specify, I do NOT have a fastboot factory cable. Do I need one?

Okay since you can use windows on a vm start there. Shift+right click on the tools folder inside KFU select open command window here, plug in the kindle, type the first command hit enter, type the second command hit enter if all goes well it should reboot normally. Same concept on a mac whatever directory adb and fastboot are in open a terminal, same commands same method. Good luck
Edit: in fact you can just copy paste my commands then you know you got it right. Dunno about the cable yet see if the commands work.

Thepooch said:
Okay since you can use windows on a vm start there. Shift+right click on the tools folder inside KFU select open command window here, plug in the kindle, type the first command hit enter, type the second command hit enter if all goes well it should reboot normally. Same concept on a mac whatever directory adb and fastboot are in open a terminal, same commands same method. Good luck
Edit: in fact you can just copy paste my commands then you know you got it right. Dunno about the cable yet see if the commands work.
Click to expand...
Click to collapse
Did the first one, but still says "waiting for device" and nothing is happening. :/ (EDIT: for clarity's sake, nothing happening means its still stuck on the kindle fire white/orange stock boot logo)
btw, thank you for your help.

Hold the power button to turn the device off. Enter the command, and turn the device on when you see "waiting for device".

soupmagnet said:
Hold the power button to turn the device off. Enter the command, and turn the device on when you see "waiting for device".
Click to expand...
Click to collapse
still says "waiting for device" in the terminal.
also, windows still comes up with "usb unrecognized" message at the bottom right of my screen.
What's next?
Thanks for joining to help, soupmagnet

Okay rerun the driver.bat packaged with kfu then plug the device in see if it comes up in device manager.

Thepooch said:
Okay rerun the driver.bat packaged with kfu then plug the device in see if it comes up in device manager.
Click to expand...
Click to collapse
Still doesn't show up. (It also occasionally crashes my mac system when I plug the kindle in now :/ )
If I get a factory cable, will that likely solve this easily?

Well I'm not a Mac person but it's far better with drivers than Windows ever will be maybe google how to setup and and fastboot on a Mac and go from there. Download install breakdroid that should be accompanied with the drivers.

Thepooch said:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
Code:
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
Thepooch said:
Well I'm not a Mac person but it's far better with drivers than Windows ever will be maybe google how to setup and and fastboot on a Mac and go from there. Download install breakdroid that should be accompanied with the drivers.
Click to expand...
Click to collapse
Got it! Using Breakdroid, I was able to capture the Kindle as it powered on. I believe my main problem was that there was a significant enough delay in connecting the Kindle via USB to the Windows Virtual Machine, that the ADB couldn't access it in time to capture it. Or whatever.
Solution: I used BreakDroid on my Mac. Turned the kindle off, then back on while Breakdroid was waiting for my device to perform Step 1 on Breakdroid's Kindle Tools. Then it immediately captured the Kindle when I powered it on. Went through the steps on Breakdroid, and it's working with bootloader and recovery
Works great! Have all my stuff back. And...it's rooted
THANKS FOR ALL YOUR HELP, GUYS!
EDIT: Now how do I install Google Play?

[Q] fastboot drivers

I'm a need of help here. I've been searching around the web and here to find the answer that for some reason I can't find. When I connect Kindle Fire 2 using a fastboot cable the device that comes up in Device Manager is otter2-prod-04. I've tried to install drivers manually using "Have a Disk" method but adb would not communicate with device (adb devices doesn't return a value). I don't know if the android_winusb.inf has to be edited (it only seems to be the case with first gen kindle) but I haven't found any guides that tell you to do it for Kindle Fire 2. Any help or proper direction is appreciated.

Resolver1 said:
I'm a need of help here. I've been searching around the web and here to find the answer that for some reason I can't find. When I connect Kindle Fire 2 using a fastboot cable the device that comes up in Device Manager is otter2-prod-04. I've tried to install drivers manually using "Have a Disk" method but adb would not communicate with device (adb devices doesn't return a value). I don't know if the android_winusb.inf has to be edited (it only seems to be the case with first gen kindle) but I haven't found any guides that tell you to do it for Kindle Fire 2. Any help or proper direction is appreciated.
Click to expand...
Click to collapse
Have you ran a fastboot cmd? ADB and fastboot are totally separate from one another. Try running: fastboot -i 0x1949 getvar product
That will give you the product id while in fastboot.

onemeila said:
Have you ran a fastboot cmd? ADB and fastboot are totally separate from one another. Try running: fastboot -i 0x1949 getvar product
That will give you the product id while in fastboot.
Click to expand...
Click to collapse
Hmm that did help. I should make a noob friendly guide because all of these guides are so vague when it comes to fastboot.

fast boot commands not functioning, adb works fine
onemeila said:
Have you ran a fastboot cmd? ADB and fastboot are totally separate from one another. Try running: fastboot -i 0x1949 getvar product
That will give you the product id while in fastboot.
Click to expand...
Click to collapse
when i issue this command all it does is sit with < waiting for device >
adb works fine, but not fastboot. fastboot devices returns nothing.
I have a factory cable that does boot it it fastboot screen.

lgweaver said:
when i issue this command all it does is sit with < waiting for device >
adb works fine, but not fastboot. fastboot devices returns nothing.
I have a factory cable that does boot it it fastboot screen.
Click to expand...
Click to collapse
Then you have a driver issue. Get the device into fastboot and with it plugged in go to your device manager and right click the device that shows up(it will probably have a yellow triangle next to it. Then select update driver, then choose "browse my computer for device software", lastly choose "let me pick from a list of device drivers on my computer". Since you have adb working then you should have one that says "adb composite interface" or something like that. Once you install the driver you should be ok.

onemeila said:
Then you have a driver issue. Get the device into fastboot and with it plugged in go to your device manager and right click the device that shows up(it will probably have a yellow triangle next to it. Then select update driver, then choose "browse my computer for device software", lastly choose "let me pick from a list of device drivers on my computer". Since you have adb working then you should have one that says "adb composite interface" or something like that. Once you install the driver you should be ok.
Click to expand...
Click to collapse
Found those steps. but that driver was already installed and said it was functioning. I risked it and attempted the root and install of jellybean without the fastboot command showing devices. apparently it works. my Kindle fire 2 is running cyanogen mod without issue now.
thanks for the response.

Help! Bootloop - no recovery - no usb debugging

I just need to install TWRP

charackthe said:
I just need to install TWRP
Click to expand...
Click to collapse
Boot into Fastboot? If you can't use the unbrick guide, make sure you follow ALL steps or it won't work.

Puddi_Puddin said:
Boot into Fastboot? If you can't use the unbrick guide, make sure you follow ALL steps or it won't work.
Click to expand...
Click to collapse
Booting into fastboot doesn't do anything for me since "adb devices" command shows no device connected even though device is listed under "Android Phone" in device manager (OnePlus Android Bootloader Interface driver is installed)
I tried unbricking guides this (Mega Unbrick Guide) didn't work for mee because the Recovery Tool that has been provided in the thread (Mini and Full) doesn't recognize my device.
My device is listed as Qualcomm *something something* 9008 but it is required to be named "Qualcomm 9008"
1. ADB Doesn't see my device
2. Unbrick guide is useless
What should I do

charackthe said:
Booting into fastboot doesn't do anything for me since "adb devices" command shows no device connected even though device is listed under "Android Phone" in device manager (OnePlus Android Bootloader Interface driver is installed)
I tried unbricking guides this (Mega Unbrick Guide) didn't work for mee because the Recovery Tool that has been provided in the thread (Mini and Full) doesn't recognize my device.
My device is listed as Qualcomm *something something* 9008 but it is required to be named "Qualcomm 9008"
1. ADB Doesn't see my device
2. Unbrick guide is useless
What should I do
Click to expand...
Click to collapse
First of all, "adb devices" can not be used when the phone is in bootloader mode. The proper command is "fastboot devices". Try that.
Next, the Unbrick Guide has to be followed to the letter. No skipping or changing is permitted. Did you disable driver signing in Win 10?
If the driver is not named as stated in the Guide, you have to change the driver.

tnsmani said:
First of all, "adb devices" can not be used when the phone is in bootloader mode. The proper command is "fastboot devices". Try that.
Next, the Unbrick Guide has to be followed to the letter. No skipping or changing is permitted. Did you disable driver signing in Win 10?
If the driver is not named as stated in the Guide, you have to change the driver.
Click to expand...
Click to collapse
Yep you didn't follow the guide properly I believe.

tnsmani said:
First of all, "adb devices" can not be used when the phone is in bootloader mode. The proper command is "fastboot devices". Try that.
Next, the Unbrick Guide has to be followed to the letter. No skipping or changing is permitted. Did you disable driver signing in Win 10?
If the driver is not named as stated in the Guide, you have to change the driver.
Click to expand...
Click to collapse
Puddi_Puddin said:
Yep you didn't follow the guide properly I believe.
Click to expand...
Click to collapse
Guys thanks a lot. I figured this out like an hour before you replied. This was because I was too distracted. I knew both "fastboot devices" and "adb devices" but I've been awake for like 32 straight hours so I never thought of trying "fastboot devices" which is the right one. I've fixed my problem through fastboot.
But Mega Unbrick Thread's drivers weren't showing correctly and yes I disabled that annoying but useful driver signature thing. Thanks for your help!
I hope one day a fellow flashaolic read this and realize he needs to use "fastboot devices".
TL;DR: Device closed? "fastboot devices"
Device on? "adb devices"

Fastboot interface is missing. Help!

On Device Manager (Window 10). Were updating the driver, I can only see ADB interface but no Fastboot interface. I'm on the latest version SDK from Google and have OnePlus driver installed. I can command ADB but not fastboot. What am I missing? My device is OnePlus 7T TMobile is sim unlocked and I can toggle OEM unlocking and is on.

Not sure what mean, but fastboot only works when you're booted in bootloader. (Adb reboot bootloader)
Sent from my OnePlus7TPro using XDA Labs

That's correct but when I fastboot cmd it get stuck on "waiting for device". So I read around on XDA on how to fix it and I tried to follow the instruction on PC - device manager, still no go.

PesTicide. said:
That's correct but when I fastboot cmd it get stuck on "waiting for device". So I read around on XDA on how to fix it and I tried to follow the instruction on PC - device manager, still no go.
Click to expand...
Click to collapse
I myself have never had this problem, I can only suggestion reinstalling OnePlus drivers.
Hopefully you figure this out
Sent from my OnePlus7TPro using XDA Labs

I reinstalled couple of times. Still no go! This is the first time that this happening. Never had problem since day one on Nexus devices. I'm going to try again and search more around.

You can also use the universal drivers by clockworkmod https://adb.clockworkmod.com/
Here's what I did.
1) Extract the android sdk platform tools and put on your c:// drive
2) Install the universal usb drivers
3) Enable usb debugging on your one plus and connect to computer. Switch to usb debugging mode and accept the popup on your one plus to allow the connection.
4) Open cmd and run "cd C:\platform-tools", then run "adb devices" to ensure that your devices is connected properly
5) Run "reboot bootloader" and device will restart into bootloader mode and fastboot will now work
*This is all assuming that you've already oem unlocked your devices as well already*

It work till fastboot. Still stuck at "waiting for device".

PesTicide. said:
It work till fastboot. Still stuck at "waiting for device".
Click to expand...
Click to collapse
Are you trying to open? Command shell? In windows 10 right? So for your information in windows 10 it's not supported , you have to open that platform tool folder which you installed already named as adb, platform tools , sdk may go into that folder and you will see a folders directory above there .. just click on that and type cmd and hit enter and cmd will pop up now you can use all your commands it's not your fault it's windows 10 fault ..maybe hope it may work for you

That how I done it. Fastboot Command appear on my Google Pixel 2 and 3 but I can't do it on my 7T. I don't get it
Thanks for the help! I tried working on Device Manager on PC yet doesn't work. Adb shell command work but no Fastboot command.

I found the solution! This is what I did and it worked for me! Here's the link for anyone who has the same issue I went through. Here you go and follow the instruction. http://www.wtfandroid.com/fix-fastboot-device-not-recognised-problem/
Mod you can close this thread. Thanks again for everyone who tried to help me. :highfive:

Bootloop issue with boot reason

hello there, I'm currently using one plus 7 T, I don't know why , but after updating the last software update my device stuck in Boot loop, i can't able to turn it on, The boot reason says that : Init_user0_Failed . Unable to parse kernel log.Could you please help me to get out from this issue. As i'm outstation from the city, so i can't able to reach the service center. I need my data so i'm trusting you that you guys will sort out the issue, Thank you so much for reading this.

"fastboot set_active other" to switch slot

I'm facing the same problem. Please find a workable solution asap. I'll thank endlessly.

HueyT said:
"fastboot set_active other" to switch slot
Click to expand...
Click to collapse
How and where do I do this?

kiranlalge said:
How and where do I do this?
Click to expand...
Click to collapse
In bootloader mode (check YouTube for how to boot into bootloader or fastboot mode for OnePlus 7t)

HueyT said:
In bootloader mode (check YouTube for how to boot into bootloader or fastboot mode for OnePlus 7t)
Click to expand...
Click to collapse
"fastboot set_active other" to switch slot
It looks like the above needs to be typed in somewhere. Because I do not see any typing option on any of the screens the device shows in this situation.
Please help further. I'm not sure if the developer of the given ROM is reading my posts. I'm very hopeful on him to resolve my issue. Fingers crossed.

kiranlalge said:
"fastboot set_active other" to switch slot
It looks like the above needs to be typed in somewhere. Because I do not see any typing option on any of the screens the device shows in this situation.
Please help further. I'm not sure if the developer of the given ROM is reading my posts. I'm very hopeful on him to resolve my issue. Fingers crossed.
Click to expand...
Click to collapse
Plug phone into windows laptop with adb installed on laptop:
[Download] ADB Installer v1.4.3 - Drivers, ADB and Fastboot Tools
Install drivers, ADB and fastboot tools with one single installer.Advertisement What’s ADB Installer v1.4.3 This package includes all required drivers for Android: ADB drivers (Android Debug Bridge), Fastboot and Google USB-drivers. Very easy to install. Features: Small size. Fast installation...
xiaomifirmware.com

I installed the ADB driver , now what ?? Will this erase my phone's data ?

Hi:
I'm with the same problem here, and i'm trying the "fastboot set_active other" command, but it returns me: "waiting for any device".
How can I proceed to make the phone recognized by the PC?

Zesotar said:
Hi:
I'm with the same problem here, and i'm trying the "fastboot set_active other" command, but it returns me: "waiting for any device".
How can I proceed to make the phone recognized by the PC?
Click to expand...
Click to collapse
15 min adb fastboot drivers, OnePlus USB drivers, Qualcomm USB 9008 drivers (msmtool)

ashuetrx said:
I installed the ADB driver , now what ?? Will this erase my phone's data ?
Click to expand...
Click to collapse
Enable "USB debugging" in Dev.Options, Boot into fastboot mode on phone, type "fastboot devices" and it should give you a code--then your phone is ready for fastboot flashing files

Tried in another computer with Windows 10. It returns: "Slot change is not allowed in Lock State"
I get the a code with the fastboot devices, so it seems the phone is ready.

Finally used MSM tool. I lost all my photoss but I recovered the phone.
Thanks for all the help!

Zesotar said:
Finally used MSM tool. I lost all my photoss but I recovered the phone.
Thanks for all the help!
Click to expand...
Click to collapse
how exactly did you do it with MSM tool?

cromedo7 said:
how exactly did you do it with MSM tool?
Click to expand...
Click to collapse
5 seconds with Google.
Fastboot method is much easier and without data loss.
Download
https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/
Reboot to fastboot mode
Start minimal ADB and fastboot
Type: fastboot devices
If you see device and something like that:1S67gz everything's ok.
Now type: fastboot set_active other
Type reboot.
Done