Power + Vol Down pressed together gets you access to the F1's limited recovery mode.
Power + Vol up does not get you into the bootloader.
When you connect the phone to your PC it automatically loads its USB drivers to the PC with your consent.
ADB can see the phone once the USB drivers are installed and the phone is connected via USB cable.
ADB DEVICES provides the serial number of your phone.
ADB REBOOT RECOVERY gets you into the recovery mode mentioned above.
ADB REBOOT BOOTLOADER simply reboots the phone.
FASTBOOT can't see anything.
FASTBOOT DEVICES doesn't yield serial number.
Other FASTBOOT commands sit "waiting for device".
So FASTBOOT just does nothing useful. A google search shows that this behavior is known and people think that using different drivers overcome the problem, but I tried a number of driver solutions with no success. I just think that they've closed the Oppo F1 up rather tightly.
-----
ETA: Just heard elsewhere from a semi-official source that FASTBOOT has been disabled on the F1.
I just saw this "Decision by Oppo: No Bootloader/Fastboot access for Oppo Phones starting 2016" from here > http://forum.xda-developers.com/r7-plus/help/decision-oppo-bootloader-fastboot-t3348114
If this is true, the F1f will be our last oppo. It's not a big issue for the F1f as it's my wife's phone but I will avoid locked phones on principle now. Even Huawei are making it hard to unlock bootloader so my Mate 7 could be our last Huawei.
Guys anybody tell how to flash 'magictricks' zip to unlock boot loader and to flash twrp recovery safely...
I'm week in commanding adb devices and fastboot so I need steps,help will be thankful.
Sent from my F1f using XDA-Developers mobile app
friends. I want to flash myphone (flash tool) windows 7 but do not see it. even I reinstalled windows 7, but did not see. last driver installed on the MTK what to do - I do not understand
agreed. another computer, another cable, another driver (for flash tool)
Related
I was trying things on my Lenovo A7-10F and ended up rebooting in fastboot mode. Pressing power doesn't do anything (even for a whole minute..); with other buttons : nothing either. Non removable battery of course, and adb won't detect the device (tried to install different drivers).. What can i do? It's heating quite a lot..
In order to replicate how it is when the battery is taken out just allow it to drain completely. That might help with the reset of it. Hope you get more help here!
Yes that's the last thing I'd like to do though since it's heating a lot and it can last for +10 hours..
did it work by just letting the battery out?
Download, extract and install this Lenovo driver to your PC
Code:
lenovo-forums.ru/index.php?app=core&module=attach§ion=attach&attach_id=39195
Download and install Minimal ADB and Fastboot (search it on xda or google).
Run it.
Connect your device to PC using USB cable.
On the command prompt type: fastboot devices
It will verify your device. If fastboot is configured properly, your device code will appear.
Then you just have to type: fastboot reboot
and your device will reboot to system
Hope it works. Good luck
Hi,
First of all the bootloader is already unlocked.
Two problems:
1. - I was trying to flash twrp.img on my mobile but I am not getting that green android to show up in my screen all I get a black screen with blue led light, I usually power off the mobile, hold volume up and then connect the USB cable to my mobile.
2. - Can't find mobile device while using flash or fastboot, my mobile Developer option and USB debugging are turn on, mobile drivers and adb-setup-1.4.3 are installed, I have access to my mobile on my PC , when I do the process of flashing or fastboot I turn off the mobile and I unplug USB cable from my mobile, I press the keys to do flash or fastboot (I don't see no green android just a led light turn on) and connect the USB cable, problem is my PC can't find the mobile device, I use adb function eg. adb devices or fastboot devices I get nothing no device no info.
Is this problem with Win 10?
Was my problem understood in 2. - ?
Sa9aX said:
Is this problem with Win 10? Was my problem understood in 2. - ?
Click to expand...
Click to collapse
Most likely a drivers problem, Windows10 fails to tell you that it's not installed the drivers that you pressed the install button on. It also fails to assign the right drivers when you add the phone in flashmode/fatsboot.
You will need to add them manually.
Go into safe mode and use 'driver signing disabled', try adding the drivers again. Then plug in you phone in flashmode/fastboot, then look in the device manager for the phone and change it
Several people have reported success with Zdiag drivers
Didgesteve said:
Most likely a drivers problem, Windows10 fails to tell you that it's not installed the drivers that you pressed the install button on. It also fails to assign the right drivers when you add the phone in flashmode/fatsboot.
You will need to add them manually.
Go into safe mode and use 'driver signing disabled', try adding the drivers again. Then plug in you phone in flashmode/fastboot, then look in the device manager for the phone and change it
Several people have reported success with Zdiag drivers
Click to expand...
Click to collapse
Thanks! Great Info.
I removed the drivers manually in device manager and then used Zadig, now in command mode I getting something.
Next I have to figure how root the phone, do I need to flash twrp.img ?
I have all this stuff and I got confused which one I need to do next:-
boot.img
boot-G8141-47.2.A.10.45-hideunlock-rooted.img
twrp.img
twrp-3.2.1-0-maple
xperifix.zip
ss_maple.zip
zestmaple-latest.zip
ScriptWINg-master.zip
Sa9aX said:
Thanks! Great Info.
I removed the drivers manually in device manager and then used Zadig, now in command mode I getting something.
Next I have to figure how root the phone, do I need to flash twrp.img ?
I have all this stuff and I got confused which one I need to do next:-
boot.img
boot-G8141-47.2.A.10.45-hideunlock-rooted.img
twrp.img
twrp-3.2.1-0-maple
xperifix.zip
ss_maple.zip
zestmaple-latest.zip
ScriptWINg-master.zip
Click to expand...
Click to collapse
Back again...
I figured all out:-
twrp-3.2.1-0-maple.img
boot-G8141-47.2.A.10.45-hideunlock-rooted.img (latest firmware)
Magisk Manager
So here's the background: I have a OnePlus 6, which I had rooted previously. I accidentally updated it without first patching the boot image, so it's not rooted now.
In an attempt to root it again, I need to use fastboot. However, whenever I use
adb reboot bootloader
it reboots the phone to fastboot mode, as expected, but then
fastboot devices
displays nothing. I find this extremely strange, because I have used fastboot commands before on both my windows machine and on my Linux machine (though I recently switched distros and have a new installation on there, so it may be missing some driver or something).
I have tried looking for any necessary drivers (I saw that sometimes usb drivers are different from fastboot drivers, but I don't know if that's the case regarding OnePlus) but after installing everything I found, it still doesn't work.
I have also tried running adb as root (on Linux) and as administrator (on Windows) but neither worked.
I tried to use Tool All In One to root it for me, but it seemed to run into the same problem. It wouldn't detect the phone in fastboot mode.
I'm absolutely baffled as to why this may be; Anyone know why this happens or what I may do to fix it?
I had the similar issue last week when adb command of fastboot devices would not identify the device. I used the fastboot ROM method to reflash the stock rom and everything worked fine afterwards including fastboot devices command identifying the device correctly. Needless to say, it would delete everything on your phone. Here is the link:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Good luck!!
Fastboot version
Update your fastboot, maybe it's an old version.
Also check your device manager and see if the phone is listed there. Sometimes it's necessary to disable driver signature check in Windows 10. Also install the driver before you use your commands - some users reported that for some reason the driver or connection is lost after windows reboot.
A) Check fastboot drivers/reinstall them (adb and fastboot use different drivers). You might want to check if there are unknown devices in your Windows device manager, or the name of the device once fastboot mode is engaged and you plug the cable
B) Plug it in another USB port (less likely to be the problem, since ADB actually works)
Hello,
Had the phone for 2 years, and I was using a Google Pixel UI. I had some problem with phone auto rebooting while not in use. So I decided to install MUI, but I forgot its only in Chinese without google play.
So I have tried to install the TWRP recovery, but the fastboot is not recognized by the computer.
I have tried Xiaomi Poco X3, and fastboot its working fine on it. So its not issue with the cable.
I have installed some drivers, but it didnt help. I have tried most of the options, so not sure what I'm missing. Will try tomorrow, a different PC at work. MiFlash also cant see it.
Thanks for any help.
I am facing the same issue tried everything I could. I am able to to execute fastboot command on other devies such as one plus 5t but not with mi note 7 pro as it's not detected in fastboot mode no matter what I do.
It gets detected in adb but nothing pops up when I connect in fastboot mode. No devices is shown in fastboot mode. No changes in device manager when connected as fastboot.
Already tried.
-2 different cables
-Disable signature enforcement
-manually installed drivers
-3 different computers
Someone help us out..,.......
Any leads on the above problem guys?
Disable driver signature enforcement and download mi flash tool. It will prompt you to install all the drivers. Install them and check if it works. For me this was the solution. Another solution is to download the latest drivers from android at https://dl.google.com/android/repository/platform-tools-latest-windows.zip for windows and install it manually by using device manager. This fixes are of course only for windows
On my PC, I didn't try other devices in fast boot mode but I know that my redmi note 7 pro wasn't displaying even after installing those Google/phone drivers.
It eventually worked when I opened Device Manager and saw that my phone was showing as Unknown Device; I clicked on the option to update the driver from a folder on my PC, so I selected the folder containing the android_winusb.inf file and it worked
sumitsky33 said:
I am facing the same issue tried everything I could. I am able to to execute fastboot command on other devies such as one plus 5t but not with mi note 7 pro as it's not detected in fastboot mode no matter what I do.
It gets detected in adb but nothing pops up when I connect in fastboot mode. No devices is shown in fastboot mode. No changes in device manager when connected as fastboot.
Already tried.
-2 different cables
-Disable signature enforcement
-manually installed drivers
-3 different computers
Someone help us out..,.......
Click to expand...
Click to collapse
If you get solutions then please tell us
Hi All
I have ROG 5s tencent edition. it was modified by seller to global. I have been using it for more than 1 year now. Last night something happened and it went off. I tried turn it on but it kept bootlooping at logo. It is not detetedable by computer because bootloader was locked by seller before selling. I had no idea about that at that time.
MY device is now in bootloop. I can open bootloader but it won't take me to recovery mode. Fastboot commands are also not working . Phone not found by computer in any state. Can any one provide me with some pointers on how an i flash firware,
Recoery is not opening. When I select it from bootloader it keeps bootlooping
Fastboot is not seen by computer. Tried many cables, both ports.
If anyone can guide me that be a huge favor as this is my daily driver
Your device should be dected in bootloader mode even if it has been locked. Connect via the side port with a good data cable and check drivers on Windows.
Once you have verified you have access to send Fatboot commands to the device in Bootloader mode, you can simply do a RAW flash to any working version and then upgrade normally to the firmware version you want. You don't need unlocked bootloader to flash this way.
Andrologic said:
Your device should be dected in bootloader mode even if it has been locked. Connect via the side port with a good data cable and check drivers on Windows.
Once you have verified you have access to send Fatboot commands to the device in Bootloader mode, you can simply do a RAW flash to any working version and then upgrade normally to the firmware version you want. You don't need unlocked bootloader to flash this way.
Click to expand...
Click to collapse
I have tried but it is not detected as anything. Not even unknown device. I have installed qualcomm drivers. What other drivers are there? Could u tell?
dksoni411 said:
I have tried but it is not detected as anything. Not even unknown device. I have installed qualcomm drivers. What other drivers are there? Could u tell?
Click to expand...
Click to collapse
If there isn't a hardware issue with the device, you should be able to.
Try to delete the driver and re-install it. Use the official Android USB driver from the SDK as opposed to Qualcomm drivers from random places on the net. Plug it in from the side port and try to turn it on while connected. Have Device Manager in Windows open and notice changes. Read out what it is recognized as. If absolutely nothing, then it's the cable, Windows or the device may really have a motherboard defect.
I believe it's more likely motherboard. Is there any fix for it?