Hey everybody. I'm back from a long hiatus from rooting phones. I'm wanting to root my OP 8T, and adb is not seeing the phone when in recovery mode, so I can't even begin.
Win10, pretty sure drivers are up to date, adb up to date.
Computer and adb both see the phone when it's powered on normally, but I have to choose usb mode every time I plug it in. I suspect the adb not seeing it in recovery mode may have something to do with this, but I'm just guessing. I'm not sure how to overcome this. I know plenty of people have rooted this phone, so I don't get it.
Would be happy for any input on this issue. Idk where to go from here, and it's really frustrating, bc I'm excited to switch to this phone.
TIA
Have you tried checking Windows update when the phone is plugged in and in recovery mode? Do you have the Google fastboot drivers? Qualcomm drivers? OnePlus drivers? Are you using CMD or PowerShell for adb?
Zamkat said:
I'm wanting to root my OP 8T, and adb is not seeing the phone when in recovery mode, so I can't even begin.
Click to expand...
Click to collapse
yes, why should you? adb not available in recovery mode, expected behaviour.
Zamkat said:
I know plenty of people have rooted this phone, so I don't get it.
Click to expand...
Click to collapse
sure not from adb or recovery. did you mean fastboot? then boot phone into bootloader mode and install Android Bootloader Interface drivers.
alecxs said:
yes, why should you? adb not available in recovery mode, expected behaviour.
sure not from adb or recovery. did you mean fastboot? then boot phone into bootloader mode and install Android Bootloader Interface drivers.
Click to expand...
Click to collapse
It's been so long since I did this...I don't remember much about the procedure. I was just following the instructions. It said to turn it off, and then hold down and power to boot into fastboot mode. Then to connect it and type the reboot bootloader cmd.
I am using powershell.
These instructions aren't very good, I realize now. -_-
I guess I don't have the fastboot drivers...I'll try to get those and make another attempt. Thanks, I'll get back to you.
the driver is included in the same android_winusb.inf where the ADB driver is. you just need to disable windows driver signature enforcement before trying to install.
once you see device in 'fastboot devices' proceed with bootloader unlocking.
T-Mobile get Unlock Code to Submit to OnePlus for unlock token
This took me way too long to figure out so Hopefully this will make it quicker for someone: OnePlus Help Page Dr. Mario said: fastboot oem get_unlock_code (Found ten pages in at...
forum.xda-developers.com
Okay, well, this will make things difficult. Am I missing something here...???
Okay, hang on, I think I found the right instructions to install the sdkmanager... Ugh.
not sure what you are trying, but to run fastboot commands either navigate with cd into platform-tools directory from cmd.exe or in powershell type the path to file like this:
Code:
.\fastboot devices
Zamkat said:
Okay, hang on, I think I found the right instructions to install the sdkmanager... Ugh.
Click to expand...
Click to collapse
So, I followed these instructions exactly, and it's saying that sdkmanager is not a thing that exists.
Awesome. Super useful instructions. I never thought simply putting the tools needed to root my phone on my computer would be such a colossal pain in the ass.
I have never used sdkmanager and I don't know how that would involved in bootloader unlocking or rooting. It is also not mentioned anywhere in this device forum.
Zamkat said:
So, I followed these instructions exactly, and it's saying that sdkmanager is not a thing that exists.
Awesome. Super useful instructions. I never thought simply putting the tools needed to root my phone on my computer would be such a colossal pain in the ass.
Click to expand...
Click to collapse
Please go back to post #6. as we can see you're in folder "platform-tools" (left side of the cursor in your PowerShell window). This folder contains the files "adb.exe" and "fastboot.exe" and some more.
As a normal Windows user you would try to start these .exe files with a double click. Don't try it because it won't start anything. These .exe files are not executables, they are binaries. To run them you need to enter "adb" or "fastboot". That's all.
You need to use this: https://developer.android.com/studio/releases/platform-tools
And LineageOS have a great installation document: https://wiki.lineageos.org/adb_fastboot_guide
According to the instructions, I need to use the Sdk manager to install the fastboot drivers.
In order to get that, I apparently need the command line tools.
In order to get those enabled/installed in sdk, I need the Sdk manager...??? I'm so confused.
BillGoss said:
You need to use this: https://developer.android.com/studio/releases/platform-tools
And LineageOS have a great installation document: https://wiki.lineageos.org/adb_fastboot_guide
Click to expand...
Click to collapse
Holy ****, thank you.
Okay, I am in Fastboot mode, and I'm getting ready to install Twrp, but...it says my Device State is locked. Does that mean my bootloader is not unlocked? Because it is supposed to be.
alecxs said:
I have never used sdkmanager and I don't know how that would involved in bootloader unlocking or rooting.
Click to expand...
Click to collapse
The Platform Tools are part of the Android SDK. But Google offers them also as a single download, excluded from the Android SDK:
It's not wrong to install the whole SDK. But it's too much if only 2 binaries are being used.
how did you unlock the bootloader without fastboot?
alecxs said:
how did you unlock the bootloader without fastboot?
Click to expand...
Click to collapse
I'm an idiot. I need to do that still.
Device isn't being seen by adb in fastboot. Any suggestions?
Fyi, you shouldn't have posted the question in this forum but in the q&a forum https://forum.xda-developers.com/f/oneplus-8t-questions-answers.11583/
@BillGoss thread is moved soon, thx for reporting.
@Zamkat no device is seen by adb in fastboot.
Related
I trying to unlock my XOOM WIFI from COSTCO, when I ran the command
adb reboot bootloader
The XOOM reboots show the message STARTING FaSTboot protocol support and stuck in there, I have to VOL UP & Power to reset it.
What I am doing wrong.?
I do not want to do the ONE CLICK to avoid wiping the machine completely.
Do I need to wipe it the first time?
you need to have fastboot in your machine, then you can run:
fastboot oem unlock
it will ask you to use volume up/down keys to confirm "twice" the terms of service and will unlock it for you.
please not that unlocking it will void your warranty right away, so unless you are a developer or have a very good reason to do so, I would not recommend it.
You are doing it right.
adb reboot bootloader
is supposed to bring you to "Starting Fastboot protoco"l screen. Just continue and enter the commands as the instructions entail. If this is the first time you are rooting the device though you will end up wiping everything fyi.
ubuntu and fastboot....waiting for device
I am running Ubuntu 10.10. When I do adb reboot bootloader....when I run any fastboot command it says <Waiting for Device>…do I need to install USB drivers and how would I do that on Ubuntu.
Any help would be greatly appreciated...
Type in adb devices.
Does it list your device there?
Most likely it's a driver issue when it says "waiting for device."
I know nothing about ubuntu though so i wont be any help getting those drivers installed.
Yes it does before I get into the bootloader. After I get into the bootloader I get nothing.
Sent from my PC36100 using XDA Premium App
adb not reconized
Hello First thank you soo much for this wonderful information.
Sorry in advance if i am just not smart enough to follow your wonderful directions on how to overclock but when i put in adb my Command prompt says it is unreconizable and will not get past that. it is rooted i did that the other day thx
wmchristian said:
Hello First thank you soo much for this wonderful information.
Sorry in advance if i am just not smart enough to follow your wonderful directions on how to overclock but when i put in adb my Command prompt says it is unreconizable and will not get past that. it is rooted i did that the other day thx
Click to expand...
Click to collapse
Make sure you are running the commands from the directory on your computer that the adb file is in. For example, make sure you do a CD "\Program Files\Android\android-sdk\tools" if that is where adb and all the necessary files are.
thx for reply
Thought I did ill try again this weekend to over clock my xoom never was good at dos.
I'm trying to install the 4.4.1 update but my device isn't being detected in recovery mode and thus adb sideload is not working. Would really appreciate some help. I've tried almost every solution that I've googled and nothing seems to be working.
I had a similar issue. Found the naked drivers and they seemed to work after uninstalling the other drivers and rebooting my PC.
Sent from my Nexus 5 using xda app-developers app
jkimbro said:
I had a similar issue. Found the naked drivers and they seemed to work after uninstalling the other drivers and rebooting my PC.
Click to expand...
Click to collapse
Any chance you could post those drivers? Mine works fine, but it would certainly help others if you could post them, or at least post a link to where you found them.
You just need the Google drivers from their website:
http://developer.android.com/sdk/win-usb.html
I had to force the installation of the drivers for the "AOSP on Hammerhead" device in the device manager.
I couldn't even get the device to show until I pressed VolUp in recovery and selected the ADB option in the recovery.
I used USB ADB Composite Interface or something like that by pointing the device manager's Update Driver dialog to the USB drivers from the SDK that EddyOS pointed at.
Windows 7 x64
Yep, had issues with my work PC (Win 7 Pro x64) - had to manually point Device Manager to the android_winusb.inf so it would find the drivers. Bit of a ballache but all working after that!
greenkabbage said:
I couldn't even get the device to show until I pressed VolUp in recovery and selected the ADB option in the recovery.
Click to expand...
Click to collapse
ADB isn't enabled on stock recovery, and sideload is not the same thing. From Google's POV, ADB access on recovery would be a heavy security risk, since you can still access recovery even with your bootloader locked. That's why they created sideloading.
a hammerhead wrote this.
beekay201 said:
ADB isn't enabled on stock recovery, and sideload is not the same thing. From Google's POV, ADB access on recovery would be a heavy security risk, since you can still access recovery even with your bootloader locked. That's why they created sideloading.
Click to expand...
Click to collapse
ADB Server may not be enabled, but ADB obviously is, otherwise you wouldn't be able to connect in order to Sideload, which you can certainly do with stock recovery (even with a locked bootloader). Also, if ADB wasn't available on the device, it wouldn't show up with the "ADB Devices" command.
Now, maybe you mean it's not available once you boot into recovery until you select "apply update from ADB." That may be true (not sure), but that's not what I got from your statement.
jt3 said:
Any chance you could post those drivers? Mine works fine, but it would certainly help others if you could post them, or at least post a link to where you found them.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2513339
jt3 said:
ADB Server may not be enabled, but ADB obviously is, otherwise you wouldn't be able to connect in order to Sideload, which you can certainly do with stock recovery (even with a locked bootloader). Also, if ADB wasn't available on the device, it wouldn't show up with the "ADB Devices" command.
Now, maybe you mean it's not available once you boot into recovery until you select "apply update from ADB." That may be true (not sure), but that's not what I got from your statement.
Click to expand...
Click to collapse
Try it. Select "apply update from ADB", and then try to get a ADB prompt like you would normally, you know, ls /sdcard/, something.
I see that there are other threads for this and I have read through them but they don't seem to be helping. I was in the middle of using the Nexus Toolkit to install a Rom when the program temporarily booted TWRP after it removed old os and then it stopped working and I went to reboot from the temporary boot when it told me I had no OS. Because I do not have a ROM my computer does not detect ADB status so I cannot seem to get anytging on the device. I also can seem to get the sideload to work. I am not quite sure how to use the CMD for this and I have used other threads suggestions like starting cmd in the folder that has the rom i want to flash and the typing the adb commands but it doesn't seem to work. Can someone help please?
STOP USING TOOLKITS!
If you can't get adb to work, you need to sort it out first. Follow this thread: http://forum.xda-developers.com/showthread.php?t=2588979
yetipopsicle said:
I see that there are other threads for this and I have read through them but they don't seem to be helping. I was in the middle of using the Nexus Toolkit to install a Rom when the program temporarily booted TWRP after it removed old os and then it stopped working and I went to reboot from the temporary boot when it told me I had no OS. Because I do not have a ROM my computer does not detect ADB status so I cannot seem to get anytging on the device. I also can seem to get the sideload to work. I am not quite sure how to use the CMD for this and I have used other threads suggestions like starting cmd in the folder that has the rom i want to flash and the typing the adb commands but it doesn't seem to work. Can someone help please?
Click to expand...
Click to collapse
you need naked usb drivers to make adb work in recovery http://forum.xda-developers.com/showthread.php?t=2386956
Download any rom you want, then with adb push rom.zip /sdcard you can send teh rom zip to your phone then you can flash it. If it not visiable from recovery then reboot your recovery.
Edit: if you are on windows 8 or 8.1 turn off driver signature enforcement to be able to install the driver
I just don't know how to get these things to work. Is there a video or something to help me with this. I dont understand how to install these naked drivers. I just cant seem to get anything onto my phone.
yetipopsicle said:
I just don't know how to get these things to work. Is there a video or something to help me with this. I dont understand how to install these naked drivers. I just cant seem to get anything onto my phone.
Click to expand...
Click to collapse
There isn't any video.
If you want, download team viewer, then pick me up on hangouts: [email protected]
I will show you how to do that
yetipopsicle said:
I just don't know how to get these things to work. Is there a video or something to help me with this. I dont understand how to install these naked drivers. I just cant seem to get anything onto my phone.
Click to expand...
Click to collapse
This is why you really shouldn't use toolkits unless you know how to fix it if something goes wrong. It doesn't teach you the necessary skills to fix problems.
If there was a button to remove all toolkits off the face of the Earth, I would press it without hesitation.
Warning: This will delete all your data. You'll also see a large warning every time you turn on the device (attached), this disappears in less than a second.
Turn on developer mode
Turn on OEM unlock and USB debugging
Install LG drivers
Windows: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
Mac: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00320110909
Type adb devices and authorize your computer on the phone
Type adb reboot bootloader
Type fastboot devices and make sure your phone shows up
Type fastboot oem unlock
Type fastboot getvar all
Should say (bootloader) unlocked:yes
Type fastboot reboot
What's the purpose for an Unlock bootloader?
bhagiratha said:
What's the purpose for an Unlock bootloader?
Click to expand...
Click to collapse
It's the first step to rooting. If you plan to root, wiping your data now may be preferable.
bhagiratha said:
What's the purpose for an Unlock bootloader?
Click to expand...
Click to collapse
At this point, nothing. It's a prelude to rooting.
When I type in fastboot oem unlock, I get < waiting for any device >
And it waits, forever. (well, ok, like 15 minutes until I get impatient and pull the battery)
I'm on windows 10, installed the drivers from this post. When I check the device manage, the phone is listed as Android Bootloader Interface. I try updating the drivers by pointing it to the LG drivers folder, it says drivers are up to date. I've got ADB and OEM unlock both enabled in developer options. I've tried the phone on different USB ports, the cable works fine when the phone is booted normally, I've tried launching minimal adb&fastboot as admin and regular. What am I missing/doing wrong?
heldc said:
When I type in fastboot oem unlock, I get < waiting for any device >
And it waits, forever. (well, ok, like 15 minutes until I get impatient and pull the battery)
I'm on windows 10, installed the drivers from this post. When I check the device manage, the phone is listed as Android Bootloader Interface. I try updating the drivers by pointing it to the LG drivers folder, it says drivers are up to date. I've got ADB and OEM unlock both enabled in developer options. I've tried the phone on different USB ports, the cable works fine when the phone is booted normally, I've tried launching minimal adb&fastboot as admin and regular. What am I missing/doing wrong?
Click to expand...
Click to collapse
Try fastboot devices and reinserting the usb cable. Doesn't make sense that adb sees it but fastboot does not unless it's a different driver. I think fastboot driver differs actually so do that driver too.
Ubuntu
heldc said:
When I type in fastboot oem unlock, I get < waiting for any device >
And it waits, forever. (well, ok, like 15 minutes until I get impatient and pull the battery)
I'm on windows 10, installed the drivers from this post. When I check the device manage, the phone is listed as Android Bootloader Interface. I try updating the drivers by pointing it to the LG drivers folder, it says drivers are up to date. I've got ADB and OEM unlock both enabled in developer options. I've tried the phone on different USB ports, the cable works fine when the phone is booted normally, I've tried launching minimal adb&fastboot as admin and regular. What am I missing/doing wrong?
Click to expand...
Click to collapse
You can also load Ubuntu on a flash drive and boot your computer from the flash drive. Then run the commands.
https://www.ubuntu.com/
Cheers
heldc said:
When I type in fastboot oem unlock, I get < waiting for any device >
And it waits, forever. (well, ok, like 15 minutes until I get impatient and pull the battery)
I'm on windows 10, installed the drivers from this post. When I check the device manage, the phone is listed as Android Bootloader Interface. I try updating the drivers by pointing it to the LG drivers folder, it says drivers are up to date. I've got ADB and OEM unlock both enabled in developer options. I've tried the phone on different USB ports, the cable works fine when the phone is booted normally, I've tried launching minimal adb&fastboot as admin and regular. What am I missing/doing wrong?
Click to expand...
Click to collapse
First be on your c:\
Type in adb devices
If your phones serial comes up type in..
Adb reboot bootloader
Then
Fastboot oem unlock
ADB reboot bootloader boots straight into the OS on AT&T v20 :crying:
cordell12 said:
ADB reboot bootloader boots straight into the OS on AT&T v20 :crying:
Click to expand...
Click to collapse
Do you guys have the oem unlock option at least?
Also what helped me was downloading android studio with the sdk.. It installs android drivers which were necessary for me at least to get past the waiting for device message, windows located the drivers on my c drive and boom... Unlocked Bootloader.. Just saying
Sent from my LG-H918 using XDA-Developers mobile app
wing_addict_usa said:
Do you guys have the oem unlock option at least?
Click to expand...
Click to collapse
yup, even warns us that certain things won't work if we enable it. adb works just fine too
cordell12 said:
yup, even warns us that certain things won't work if we enable it. adb works just fine too
Click to expand...
Click to collapse
Yeah I am really curious if there may still be a way to unlock the bootloader with out AT&T variant. I wish I kept my phone on the Download Mode when I had gotten into it because I wanted to see if by any chance that might actually get fastboot to read the phone..
I'm curious if there's anyone with a T-Mobile variant that has their bootloader unlocked and wants to view their debug logs (specifically last_log/last_kmsg). As I was looking through mine and tried to boot into bootloader these lines were the only things I saw that might have interested me at all. I'm just curious on what the values are on their phone.
Code:
last_log
[ 0.711419] ro.boot.flash.locked=1
[ 0.711784] ro.bootloader=unknown
[ 0.711817] ro.oem_unlock_supported=1
last_kmsg
<6>[ 1.077087 / 01-01 00:00:01.069][3] [70] SW3800_Authentication [vendor code: 1]
<6>[ 1.077120 / 01-01 00:00:01.069][3] [110] set_dload_mode: download_mode:0
wing_addict_usa said:
It's the first step to rooting. If you plan to root, wiping your data now may be preferable.
Click to expand...
Click to collapse
It's quite possible the process of rooting will wipe the phone anyway.
twistedvip said:
Yeah I am really curious if there may still be a way to unlock the bootloader with out AT&T variant. I wish I kept my phone on the Download Mode when I had gotten into it because I wanted to see if by any chance that might actually get fastboot to read the phone..
I'm curious if there's anyone with a T-Mobile variant that has their bootloader unlocked and wants to view their debug logs (specifically last_log/last_kmsg). As I was looking through mine and tried to boot into bootloader these lines were the only things I saw that might have interested me at all. I'm just curious on what the values are on their phone.
Click to expand...
Click to collapse
power device off, hold volume up and keep it down and plug in USB cord while it's connected to PC. I tried fastboot from download mode though. the logs do look interesting, wonder what a T-MOBILE device says
Double0EK said:
First be on your c:\
Type in adb devices
If your phones serial comes up type in..
Adb reboot bootloader
Then
Fastboot oem unlock
Click to expand...
Click to collapse
Yup, I did that. And then I get an error. Well, not an error, just a lack of response. fastboot devices returns nothing. I'm currently downloading the full sdk, on the theory that perhaps it's a problem with the installation of 'minimal adb and fastboot' I have.
---------- Post added at 08:07 PM ---------- Previous post was at 07:36 PM ----------
manufan721 said:
Also what helped me was downloading android studio with the sdk.. It installs android drivers which were necessary for me at least to get past the waiting for device message, windows located the drivers on my c drive and boom... Unlocked Bootloader.. Just saying
Sent from my LG-H918 using XDA-Developers mobile app
Click to expand...
Click to collapse
Did you do anything specific after installing Android Studio to get it to install the drivers? Cos I've installed Android Studio, but am still having the same problem-fastboot devices returns nothing, and fastboot oem unlock hangs on <waiting for device>. I went into device manager and had it search the entire C: for drivers for the android bootloader interface, and it gave the same 'already up to date drivers' message as before I installed Android Studio.
EDIT- Even after installing the Google usb driver, no luck. Giving up for the weekend.
I'm a newbie, may I know have to fastboot from download mode?
having same issue just hangs at Fastboot oem unlock if anybody can help thanks in advance
twistedvip said:
Yeah I am really curious if there may still be a way to unlock the bootloader with out AT&T variant. I wish I kept my phone on the Download Mode when I had gotten into it because I wanted to see if by any chance that might actually get fastboot to read the phone..
I'm curious if there's anyone with a T-Mobile variant that has their bootloader unlocked and wants to view their debug logs (specifically last_log/last_kmsg). As I was looking through mine and tried to boot into bootloader these lines were the only things I saw that might have interested me at all. I'm just curious on what the values are on their phone.
Code:
last_log
[ 0.711419] ro.boot.flash.locked=1
[ 0.711784] ro.bootloader=unknown
[ 0.711817] ro.oem_unlock_supported=1
last_kmsg
<6>[ 1.077087 / 01-01 00:00:01.069][3] [70] SW3800_Authentication [vendor code: 1]
<6>[ 1.077120 / 01-01 00:00:01.069][3] [110] set_dload_mode: download_mode:0
Click to expand...
Click to collapse
[ 0.711817] ro.oem_unlock_supported=1 1=YES
did some digging into last_kmsg while trying to boot into bootloader (AT&T device) and found a reason it may not be allowing it.
http://forum.xda-developers.com/showthread.php?t=2708466
Its a start :good:
of course we need root in order to dd anything
LG issued a new driver update for the v20. Driver version is 4.1.1+. You can get the driver from the website.
Hi
Noob alert here.
I'm trying to flash a custom recovery (twrp) on a very old phone which has its bootloader unlocked. (the phone currently runs android 6.0, yes, that old...)
I read on the forums here that I need to use ADB from windows (Win10 here) in order to flash twrp onto the phone (to replace the stock recovery).
I DLed the neccessary files (platform tools), but it's just a bunch of files with nothing to actually install AFAICT...
MAny tutorials mention that I should just launch a CLI from within the folder containing the tools and then run ADB to flash twrp.
However, I get stuck at < waiting for any device > which, according to other tutorials, isa sign that drivers are not installed for my device in windows.
Some tutorial mention that I should INSTALL ADB (rather than just run it from CLI), so I'm starting to wonder what I am missing here.
- Should I INSTALL ADB? how?
- Should I install drivers for my device? It seems like my device is properly detected by Win10 and I couldn't find any driver to install anywhere.
I'm confused about what's going on.
Could you please help me out here?
Thanks a lot for your advice.
Best,
-a-
OK, I made a little progress I think. I'm not sure my issue is actually related to windows drivers but maybe I'm wrong.
Here's the deal:
When my phone is booted and connected to my PC,
adb device
spits up something : the phone is detected. Now after running
adb reboot bootloader
the phones reboots into bootloader mode (and displays the info that the bootloader is unlocked. But from now on,
adb device
in windows CLI outputs nothing : the phone is no longer detected.
Plus now the phone shows up as an unnknown device (fastboot2.0) in windows device manager. So? Missing driver I guess?
Running windows update found a driver for
Google Android Bootloader Interface
So I guess now it should work
I'll post the results
Thanks a lot
-a-
nope...
No luck
ADB still cannot see my device when in bootloader mode
asheenlevrai said:
nope...
No luck
ADB still cannot see my device when in bootloader mode
Click to expand...
Click to collapse
Actually it works!
Even though
adb devices
would not list anything when the phone wwas in bootloader mode, I was able to flash twrp
problem solved!
In the future some commands in Bootloader Mode require fastboot oppose to ADB.