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"
Related
Good evening,
I followed the steps of the this guide: http://forum.xda-developers.com/showthread.php?p=37554849
In the fifth step of "How to root (Works on ANY Huawei stock firmware, except B130 EmUI)" it doesn't work.
When I write "fastboot devices" it just says "? fastboot".
The ADB worked and I've installed all the drivers.
Well, the only thing that was different was that on this instructions it says that when I'm in fastboot mode the device is called "Android 1.0" but my device was called "Blaze".
After I installed the fastboot drivers it's called "Android Bootloader Interface".
What should I do now?
Thank you in advance.
AlexGermany
AlexGermany said:
Good evening,
I followed the steps of the this guide: http://forum.xda-developers.com/showthread.php?p=37554849
In the fifth step of "How to root (Works on ANY Huawei stock firmware, except B130 EmUI)" it doesn't work.
When I write "fastboot devices" it just says "? fastboot".
The ADB worked and I've installed all the drivers.
Well, the only thing that was different was that on this instructions it says that when I'm in fastboot mode the device is called "Android 1.0" but my device was called "Blaze".
After I installed the fastboot drivers it's called "Android Bootloader Interface".
What should I do now?
Thank you in advance.
AlexGermany
Click to expand...
Click to collapse
I had the same experience. I think the drivers are installed correctly somehow when you see "? fastboot". Because when I tried to flash a custom recovery, it just worked! You should try it for yourself.
Sent from my U9200 using xda app-developers app
Krizzii said:
I had the same experience. I think the drivers are installed correctly somehow when you see "? fastboot". Because when I tried to flash a custom recovery, it just worked! You should try it for yourself.
Sent from my U9200 using xda app-developers app
Click to expand...
Click to collapse
i have the same problem: fastboot shows "? fastboot". commands like "fastboot reboot" works but when i tried to flash it shows device not recognized" . i tried in 2 different computers, also with google and huawei drivers but the result is the same. Phone is unrooted and runs on stock ICS.
Any suggestions what to do? My head is already empty
Huawei ascend p1 B226
I was follow the steps to root my phone so that i can install CWM on the phone.
But i cannot open fastboot/bootloader mode,
i tried to use the command "adb reboot bootloader" to log into the bootloader mode
but my phone was stuck at the logo.
the device manager also show me an unknown driver "Blaze".
i tried to install the driver "Blaze" into "adb bootloader interface"
but when i check on"fastboot devices"
i only get
"? fastboot"
You're using the wrong drivers for fastboot.
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Or manually load the Google USB driver as shown here:
http://www.teamandroid.com/2012/07/30/how-to-set-up-adb-fastboot-with-android-sdk/3/
es0tericcha0s said:
You're using the wrong drivers for fastboot.
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Or manually load the Google USB driver as shown here:
http://www.teamandroid.com/2012/07/30/how-to-set-up-adb-fastboot-with-android-sdk/3/
Click to expand...
Click to collapse
i don't get it, i install the installer from the link you gave me, but i'm still get blaze
i can't get the step of getting unknown device "usb 1.0" from 2nd url.
enzo19 said:
i don't get it, i install the installer from the link you gave me, but i'm still get blaze
i can't get the step of getting unknown device "usb 1.0" from 2nd url.
Click to expand...
Click to collapse
Ok, try this:
Extract the adb-setup-1.3.exe like you would a zip file.
Plug in phone while in bootloader mode
Open Device Manager
Follow the directions on the 2nd link, but use the android_winusb you find in the extracted exe /driver folder.
That really should do the trick. If it does not, let us know which version of Windows you are using and if it is 32/64.
Phone not showing "ADB Devices"/"fastboot -i 0x1532" devices after ADB reboot.
Good afternoon everyone,
I am new to the "rooting" scene and am looking for some help. I am trying to follow the tutorial on here to root and install magisk onto my new Razer on Oreo 8.1.
When I run the command "ADB Devices", my phone is displayed and I am able to execute the command "ADB Reboot Bootloader".
But it is at this point I get stuck, If i run the command "fastboot -i 0x1532" to show my device, it does not show up. Furthermore, When i try to proceed with the tutorial, I get stuck on "Waiting for device".
Some help or direction would be appretiated.
Thank you.
PukkaVXR said:
Good afternoon everyone,
I am new to the "rooting" scene and am looking for some help. I am trying to follow the tutorial on here to root and install magisk onto my new Razer on Oreo 8.1.
When I run the command "ADB Devices", my phone is displayed and I am able to execute the command "ADB Reboot Bootloader".
But it is at this point I get stuck, If i run the command "fastboot -i 0x1532" to show my device, it does not show up. Furthermore, When i try to proceed with the tutorial, I get stuck on "Waiting for device".
Some help or direction would be appretiated.
Thank you.
Click to expand...
Click to collapse
On your PC check your drivers in device manager. It is a different driver in download mode then it is when the phone is on. 99 percent of all these problems is caused by wrong or incomplete drivers. The Razer instructions for factory images will show you what is going on.
tabletalker7 said:
On your PC check your drivers in device manager. It is a different driver in download mode then it is when the phone is on. 99 percent of all these problems is caused by wrong or incomplete drivers. The Razer instructions for factory images will show you what is going on.
Click to expand...
Click to collapse
I can see the device now, but it's still not working. <Waiting for device>
PukkaVXR said:
I can see the device now, but it's still not working. <Waiting for device>
Click to expand...
Click to collapse
Does the device say "Android" ?
PC Drivers can be found here: https://s3.amazonaws.com/cheryl-fac...stall_Android_Fastboot_Drivers_on_Windows.pdf
You'll need to download google usb drivers
tabletalker7 said:
Does the device say "Android" ?
Click to expand...
Click to collapse
Mine does
zenakent said:
Mine does
Click to expand...
Click to collapse
Then you need to follow the instructions on the Razer website for installing the proper drivers.
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:
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