I use the command fastboot -w update insert rom.zip or fastboot -w also fastboot update rom name.zip does not work. I use minimal adb fastboot I can't seem to sideload any roms even with the current build. What is going on? I get invalid sparse then failed within 20 seconds. Yes, I am in the bootloader screen and my phone is bootloader unlocked. Ones like StagOS for example or the more recent roms. I have no problem with Graphene OS or Caylx OS though.
UltimateGamer83 said:
I use the command fastboot -w update insert rom.zip or fastboot -w also fastboot update rom name.zip does not work. I use minimal adb fastboot I can't seem to sideload any roms even with the current build. What is going on? I get invalid sparse then failed within 20 seconds. Yes, I am in the bootloader screen and my phone is bootloader unlocked. Ones like StagOS for example or the more recent roms. I have no problem with Graphene OS or Caylx OS though.
Click to expand...
Click to collapse
Because you're not supposed to use "Minimal ADB and Fastboot". The binaries inside that package are years old. No wonder you're getting all those errors and have issues while trying to flash a ROM that is straightforward.
Download the latest platform-tools from Android's website (google).
Also, make sure that you're not using Windows PowerShell, but the actual CMD.
ekin_strops said:
Also, make sure that you're not using Windows PowerShell, but the actual CMD.
Click to expand...
Click to collapse
What is the reasoning behind this? I pretty much always use PS, guess I'll have to stop?
It being PowerShell or cmdline is irrelevant. Anyways..
Well, you should be using the latest platform-tools and have it added to PATH. A lot of unofficial drivers floating around on the internet install outdated adb/fastboot along with the drivers. Please refrain from installing these as well as minimal adb & fastboot; Use the official google driver and official platform-tools instead.
Alternatively you can prefix each adb/fastboot cmd with ./ while in the platform-tools folder via powershell or bash, etc.
For example:
./adb sideload ./rom.zip
Or
./fastboot -w update ./rom.zip
This tells the shell "Hey, I want to execute this local file, not the one in PATH".
Related
Adb is saying that it doesn't recognize "fastboot" as a command. I haven't really use ADB since I got the phone in February, has there been changes to the commands needed?
I did a simple search and found this: http://www.nexusoneforum.net/forum/...-fastboot-devices-command-not-recognized.html
GL Hope it helps.
Problem is not it recognizing cause Adb reboot-bootloader works.
This used to work
Cd\
Cd androidsdk/tools/
Fastboot oem lock
Has something been moved? And if so what is the new path?
sarge363 said:
This used to work
Cd\
Cd androidsdk/tools/
Fastboot oem lock
Has something been moved? And if so what is the new path?
Click to expand...
Click to collapse
Make sure fastboot is still in your tools folder. With some of the updated sdk fastboot gets removed. If it's not there you can get it from the cm wiki and just put it in the tools folder.
Sent from my PG06100 using Tapatalk
The problem is that you think you need to run adb to get fastboot to work.
adb and fastboot are 2 separate programs. ADB is the Android Device Bridge where fastboot is another standalone command line program s used to directly flash the filesystem etc.
If you download the Android SDK now, it won't have fastboot included, so you need to get it from somewhere else, like the old CM wiki as crump suggested.
Once you have the compiled fastboot file, you can navigate to it from a command prompt and execute the fastboot commands
Greetz
Thanks for the clarification. I really only used it once or twice when I first got the phone. And I just looked and I am missing the fastboot. I'll give it a shot.
In cm wiki there is only fastboot 32bit. I have 64bit, will it still work?
sarge363 said:
In cm wiki there is only fastboot 32bit. I have 64bit, will it still work?
Click to expand...
Click to collapse
Yes, 64 bit computers are backwards compatible for the most part
Sent from my illuminated black thing
Alright not really a question as much of a just wondering why. I've asks before and got 0 replies but I'm still hopeful as to an answer. When using fastboot for anything other than fastboot devices which will properly display the connected device I must run sudo ./fastboot. From there it doesn't matter whether it sudo ./fastboot flash recovery...or sudo ./fastboot flash system...what I'm getting at is why must I type sudo ./fastboot before every command as opposed to just typing fastboot flash. It also doesn't matter which directory I'm in I can use fastboot from anywhere in the terminal as long as I use sudo ./fastboot it will work without the sudo ./ it will not work regardless if I'm in the fastboot folder or not.
Beamer9408 said:
Alright not really a question as much of a just wondering why. I've asks before and got 0 replies but I'm still hopeful as to an answer. When using fastboot for anything other than fastboot devices which will properly display the connected device I must run sudo ./fastboot. From there it doesn't matter whether it sudo ./fastboot flash recovery...or sudo ./fastboot flash system...what I'm getting at is why must I type sudo ./fastboot before every command as opposed to just typing fastboot flash. It also doesn't matter which directory I'm in I can use fastboot from anywhere in the terminal as long as I use sudo ./fastboot it will work without the sudo ./ it will not work regardless if I'm in the fastboot folder or not.
Click to expand...
Click to collapse
If I understand well, you are asking why you have to use sudo. "Under GNU/linux systems (and specifically under Ubuntu systems), regular users can't directly access USB devices by default. The system needs to be configured to allow such access."
https://source.android.com/source/initializing.html check "Configuring USB Access"
I see what you're saying I've done that during my build environment setup. I should go on to say I have to use sudo for every command its not a insert once put password in and then run with it deal so it would go something like this
sudo ./fastboot flash recovery
Insert superuser password
Command done.
Now I can't go on to do
fastboot flash radio
fastboot flash system....and so on.
I must still
sudo ./fastboot flash....
sufo ./fastboot flash...
All the way down the line which I find odd. It does however work its just something I was wondering I could eliminate somehow.
Also this is all being done in same terminal I'm not running command closing opening new terminal.
Beamer9408 said:
I see what you're saying I've done that during my build environment setup. I should go on to say I have to use sudo for every command its not a insert once put password in and then run with it deal so it would go something like this
sudo ./fastboot flash recovery
Insert superuser password
Command done.
Now I can't go on to do
fastboot flash radio
fastboot flash system....and so on.
I must still
sudo ./fastboot flash....
sufo ./fastboot flash...
All the way down the line which I find odd. It does however work its just something I was wondering I could eliminate somehow.
Also this is all being done in same terminal I'm not running command closing opening new terminal.
Click to expand...
Click to collapse
What error message you get when you just use fastboot instead of sudo ./fastboot?
No error just waiting on device. I believe I get a toast message error on the phone but I'm not positive what it says.
Beamer9408 said:
No error just waiting on device. I believe I get a toast message error on the phone but I'm not positive what it says.
Click to expand...
Click to collapse
I've never seen a toast message in bootloader. Are you booted into the OS when running fastboot commands or in bootloader?
Errr.. I don't use Ubuntu, but I sure as hell don't need sudo to run fastboot commands.
Beamer9408 said:
No error just waiting on device. I believe I get a toast message error on the phone but I'm not positive what it says.
Click to expand...
Click to collapse
Well if that so, then you did not give permission for your user name on ubuntu to access the usb device.
I used this guide to give permission http://forum.xda-developers.com/showthread.php?t=921169
I don't think I have to use fastboot as sudo either and I'm running Ubuntu 14.10 64 bit. It may be a permissions thing on your system only.
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. ??
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.
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.