Hi all,
I've seen I haven't been the only one with this problem, but I haven't seen a clear solution yet. My Poco F2 pro miui global gets recognised by adb, and by the unlocking software when in fastboot, but not by adb in fastboot. I am trying to install TWRP. I have tried various drivers (currently running one from the official mi forum), running the command prompt, powershell and terminal with admin rights, killing and starting the adb server, using a windows or linux system to do it, made sure to enable USB debugging, file exchange and permanently accepting fingerprints after connecting. But to no avail. Any suggestions on what to try next?
Thanks in advance.
herkio1 said:
Hi all,
I've seen I haven't been the only one with this problem, but I haven't seen a clear solution yet. My Poco F2 pro miui global gets recognised by adb, and by the unlocking software when in fastboot, but not by adb in fastboot. I am trying to install TWRP. I have tried various drivers (currently running one from the official mi forum), running the command prompt, powershell and terminal with admin rights, killing and starting the adb server, using a windows or linux system to do it, made sure to enable USB debugging, file exchange and permanently accepting fingerprints after connecting. But to no avail. Any suggestions on what to try next?
Thanks in advance.
Click to expand...
Click to collapse
Adb use Adb.exe and fastboot fasboot.exe (differente programs)
For Twrp you must use this command " .\fastboot flash recovery twrp.img "with CMD or Powershell.
download sdk Platform tools https://developer.android.com/studio/releases/platform-tools.
extract platform-tools folder.
Put this twrp https://androidfilehost.com/?fid=17248734326145679747 into platform tools folder
Phone in fastboot mode power and volume - (Obviously the phone must be detected on the pc)
use this command " .\fastboot flash recovery twrp.img "with CMD or Powershell.
Solved thanks, I used fastboot for fastboot mode and adb for in twrp/booted in system. I must have mistyped because I could flash the twrp.img file but it then gave me an error when trying to boot into it.
Related
Any way to setup a computer with ADB and Fastboot without admin rights? Can I setup up a flash drive with Fedora or Ubuntu, boot into that and get access? If so how do you set up drivers and adb on a linux distro.
Any help would be appreciated, Thanks!
I'm using Linuxmint 12 and I have ADB setup. Just click on the other platforms option and it gives you a pretty accurate description of how to set it up on linux.
I'm actually having a problem with using "fastboot oem get_identifier_token" on the bootloader unlock process because I get an error in the terminal saying the fastboot command isn't recognized in the terminal.
On Linux, I'm pretty sure all you need is the adb or fastboot executable. However, you must run it as root (either sudo or su into root). You can grab the exectuables by download the Android SDK.
If it's saying it can't find the fastboot executable, you're probably not in the same folder as fastboot. Type 'ls' and see if you see fastboot in the list. If it's not there, it won't work.
Hi,
is it just me or is there no answer to the question of the first post? Is there any way to install adb on a win Pc without admin rights?
regards
Hi,
I successfully unlocked my bootloader and the MacOS ADB can still see my device.
However, I have the TWRP files and Magisk downloaded and ready to go on the Mac (and on my phone) but the ADB commands won't work. Fastboot boot or Fastboot flash...
It's my girlfriends Mac and I'm not familiar with MacOS at all. Am I doing something obvious wrong..??? Any ideas please??
the.Great.Skua said:
Hi,
I successfully unlocked my bootloader and the MacOS ADB can still see my device.
However, I have the TWRP files and Magisk downloaded and ready to go on the Mac (and on my phone) but the ADB commands won't work. Fastboot boot or Fastboot flash...
It's my girlfriends Mac and I'm not familiar with MacOS at all. Am I doing something obvious wrong..??? Any ideas please??
Click to expand...
Click to collapse
cant find file?
Seems like youre in the wrong folder. Try to navigate to your download folder with the command cd
You can also send pictures in here
You have to open a Terminal window in the same folder where you have adb and fastboot.
Also, on OSX, the commands have to be preceded by ./
For example:
./adb devices
./fastboot boot twrp.img
Done it thank you.
I did the 'cd' command.
Then dragged the img. file from Finder to the terminal window. Then put the 'fastboot boot' command in front of that. It worked obviously.
I was unfamiliar with the file location name. This seems an easy way for someone that doesn't have a clue like me. ??
So I want to flash stock rom back but when flashing my laptop freeze and I cannot do anything....tried many times and same problem..try run adb command in platform tool and adb device list not showing my pixel..how to fix this problem?
The first time I got my pixel I had to manually install drivers from the official android developers website, after that my PC detected my phone when in ADB and fastboot.
Make sure you also have the latest platform tools (28.0.2), get them from here
My adb detect my pixel in fastboot command..but in adb command cannot detect "adb devices"
TENN3R said:
The first time I got my pixel I had to manually install drivers from the official android developers website, after that my PC detected my phone when in ADB and fastboot.
Make sure you also have the latest platform tools (28.0.2), get them from here
Click to expand...
Click to collapse
The latest is actually 29.0.1. They haven't been updating the changelog. Try to download it now, and you'll see.
:good:
Hey, im having trouble finding working ways to root my op7pro GM1913 (OOS 11.0.4.1 GM21BA)
Ive been trying this https://www.xda-developers.com/unlock-bootloader-root-oneplus-7-pro/
Currently trying to unlock bootloader. (Step 2)
I can connect via adb but when i go to bootloader/fastboot i lose connection to the phone.
Ive tried regular adb command tools and "TOOL ALL IN ONE" When the phone is on it responds to adb commands but when i need fastboot commands its not working and i can see the device id dissapear from the all in one tool.
I have tried multiple usb ports (2.0 and 3.0) and multiple usb C cords (Op oem + Samsung) Tried removing Windows signature verification and installing oneplus usb drivers, but it gets stuck at "Execute the commands..." (99% or so) When i try again it finds some installation files. When im in bootloader, Windows device manager still shows a generic android phone. Oem unlocking and usb debugging is on, also set default usb configuration to file transfer. No help.
I want to keep Oxygen os, but i want to be rooted and have magisk, preferably TWRP too but im open to other ways.
Windows 10 20H2 if that matters. (Latest update for me)
Oneplus 7pro GM1913 (Eu nordic)
Oxygen os 11.0.4.1 GM21BA
Download a Linux distro and install adb and fastboot like this: https://forum.xda-developers.com/t/guide-unlock-flash-root-for-the-pixel-2-xl-taimen.3702418/
Just download adb and fastboot tools package from Google, extract it,open command prompt inside where you extract it and enter these in terminal:
sudo install adb dmtracedump e2fsdroid etc1tool fastboot hprof-conv make_f2fs mke2fs mke2fs.conf sload_f2fs sqlite3 /usr/local/bin
sudo mkdir -p /usr/local/lib64
sudo install lib64/libc++.so /usr/local/lib64
Then adb --version (enter) fastboot --version (enter) like Nathan says in guide. Super easy and I guarantee you if you go this route you won't have any hiccups. Sounds like stupid windblows driver issues or outdated adb/fastboot tools. One of the two. Are you flipping on dev options and check marking little box that pops up on your phone to allow it to communicate with PC? A simple : adb devices (enter) should make it appear on phone screen. You don't even have to install Linux, you can boot it off a live USB. Takes about one minute to make one. If you make one you can boot the live USB , download adb and fastboot, and install as Nathan's guide says then reboot when you are done and your back in windblows. IDK why anyone wouldn't want Linux installed though. Best decision I ever made was switching from windows to Linux about 9 years ago. It really makes anything you do to your devices MUCH easier to do!! This may sound stupid but have you rebooted your PC? Because you will definitely need to , probably more than once on windblows to get it to work.
Thank you for the reply. No stupid questions, yes i tried rebooting pc/phone. Ill try your way and report in a couple days.
Solution is simple. From Android 11 on, OnePlus (and Android phones in general) uses the universal drivers, you just need to install them in Windows in order to use fastboot commands. See my answer in this post.
There are a few things you can try if your OP7 Pro is not responding to fastboot commands:
1. Make sure you have the latest drivers installed for your phone.
2. Try using a different USB cable.
3. If you're using Windows, try running the fastboot commands from a command prompt with administrator privileges.
4. Try booting your phone into recovery mode and running the fastboot commands.
Hi,
I am using a bootloader unlocked Surface Duo on Android 11 with ‘adb devices authorized’ and all permissions allow from developer menu.
However, when I type:
‘adb reboot bootloader’ my phone reboots and gets stuck on the Windows boot logo infinitely.
I am successfully able to enter recovery and fastbootD (fastbootd) using:
‘adb reboot recovery’ lands up in android icon
‘adb reboot fastboot’ shows menu with fastbootd and adb sideload.
If I type adb devices in the recovery, it prompts unauthorized error.
If I sideload ota update from fastbootd> adb sideload, it partially completes (94%) with unrecognized command error.
I am on non-rooted Surface Duo.
I have tried removing adb keys and reallowing from RSA several times.
I have tested different machines, Windows, Mac and Linux yet no success.
I cannot push Twrp or any boot.img file.
My goal is to be able to push a boot.img file or a twrp.img but i am unable to perform it due to lack of access to the bootloader.
Any suggestions?
anuragkanase said:
Hi,
I am using a bootloader unlocked Surface Duo on Android 11 with ‘adb devices authorized’ and all permissions allow from developer menu.
However, when I type:
‘adb reboot bootloader’ my phone reboots and gets stuck on the Windows boot logo infinitely.
I am successfully able to enter recovery and fastbootD (fastbootd) using:
‘adb reboot recovery’ lands up in android icon
‘adb reboot fastboot’ shows menu with fastbootd and adb sideload.
If I type adb devices in the recovery, it prompts unauthorized error.
If I sideload ota update from fastbootd> adb sideload, it partially completes (94%) with unrecognized command error.
I am on non-rooted Surface Duo.
I have tried removing adb keys and reallowing from RSA several times.
I have tested different machines, Windows, Mac and Linux yet no success.
I cannot push Twrp or any boot.img file.
My goal is to be able to push a boot.img file or a twrp.img but i am unable to perform it due to lack of access to the bootloader.
Any suggestions?
Click to expand...
Click to collapse
If you can access fastboot mode, try flashing the boot.img via fastboot. Place a copy of your boot.img in your fastboot folder on PC and rename the file to "boot.img". Then flash the boot.img via fastboot using the following command:
fastboot flash boot boot.img