I was on Unofficial CM13 by SultanXDA!
For further update it requires OOS 3.1.3 Firmware, so I flashed OOS 3.1.3 pure!
It comes with its stock recovery i.e. I need to flash TWRP for same!
I had drivers and minimal adb-n-fastboot installed already and also $adb devices detects my device!
So, when i connect device with fastboot mode to flash TWRP it detects my Android bootloder device (according to device manager | win10) but
Code:
fastboot device
<waiting for device>
doesn't work and stuck there only!
If you can boot into OS could root with KingRoot and flash recovery with app like Rashr or Flashify.
Are you tried this process with other versions of Windows (lower than window 10)?
Windows 10 have some drivers problem.
Is your opx boot?
If Android Emulator program (Bluestack, Andy etc) is installed on your computer, you should remove it. And try again...
yuv93 said:
Are you tried this process with other versions of Windows (lower than window 10)?
Windows 10 have some drivers problem.
Is your opx boot?
Click to expand...
Click to collapse
Although I'm not the OP I had the same problem.
Used my older Laptop with Win7 and I was able to find my opx in fastboot mode thanks for saving my life <3
Nagesh_Noddy said:
I was on Unofficial CM13 by SultanXDA!
For further update it requires OOS 3.1.3 Firmware, so I flashed OOS 3.1.3 pure!
It comes with its stock recovery i.e. I need to flash TWRP for same!
I had drivers and minimal adb-n-fastboot installed already and also $adb devices detects my device!
So, when i connect device with fastboot mode to flash TWRP it detects my Android bootloder device (according to device manager | win10) but
doesn't work and stuck there only!
Click to expand...
Click to collapse
had the same on ubuntu, my solution may also work for your problem .. run the console as admin and see if it detects your device! if not you probably need to install oneplus drivers
regards,
OD
Related
I had TWRP installed and all was good. Then I tried an OTA update. Update failed and now I can't get into recovery or fastboot. When I try it stops at the 1+ logo with Fastboot Mode written under the logo. This happens if I try Volum Up + power button or adb reboot-bootloader. Device is listed with ADB but won't show up for fastboot.
How do I get back to stock recovery and get the update installed?
Thanks!
Is fastboot installed properly on your PC?
Drivers?
If not and you get it working, you can use fastboot to flash a new recovery. Otherwise read ahead.
Does your phone boot? Is it rooted?
If so, you can try to flash a new recovery via tools like FlashFire, Flashify, Rashr, etc.
If none of those work for you, you can try the un-bricking methods.
I've had my Oneplus 2 hardbrick 3 times on me so far. The solution was to put the phone into a Qualcomm QHUSB_BULK mode, installing unsigned drivers in Windows, and using Chinese software to push recovery files to your phone.
For my first two hard bricks (My phone wasn't responding to anything - it would just show up in the device manager when plugged into the PC). I was able to write the stock recovery and boot files onto my phone by using Method 1 from this OnePlus Forums thread: https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/.
I was then able to boot to recovery and dirty flash my OS without any data loss this way.
The last hard brick was much worse and required me to completely reinstall everything on my phone via one of the other methods (I used this link: http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449 and ended up with H2OS, which I then replaced with OOS 3.1.0) - if it comes to that I would recommend checking out the other methods in the OnePlus Forum link below to hopefully avoid going through H2OS - but if not, this one worked.
Also, for updates: You'll need to to reflash (dirty flash) your rom first (this is to unroot/undo any modifications you made to the system, otherwise the OTA will fail) and then flash the OTA. You should be able to use TWRP for this.
Thanks for the reply. Got fastboot working on a different computer.
Phone boots just fine. Not rooted. Just can't access recovery mode or install updates
I tried loading stock recovery (as per this thread) with no change. Thinking I'll have to treat it like it's bricked. Would rather not have to wipe phone though, but doesn't look like I have much choice .
For the past two days I had faced the issue of connecting the device in fastboot mode. Mobile is working fine, loaded with latest firmware OTA updates from OnePlus.
I would like to install TWRP on my mobile but the device is getting detected in the fastboot mode. Tried various steps, reinstalled adb & fastboot as well as OnePlus drivers nothing works. However my mobile is being detected in the adb mode. If I run the command adb devices, it displays my mobile serial number but in fastboot it just sits at the waiting for the device screen.
After a lot of googling, xda search & Oneplus forums search, nothing found. Then I tried reinstalling the adb interface drivers manually, where I have noticed that Win10 installed the latest drivers adb drivers updated in the month of Sep16. Here I have selected the older version driver which was released in the year 2014 and installed it successfully. I run the fastboot devices command again Voila... It worked. no restart, no rebooting the phone. Immediately worked.
Lesson learnt : - Always do not use latest drivers, sometimes try the older drivers if something is not working in your phone.
CrazyArjun said:
For the past two days I had faced the issue of connecting the device in fastboot mode. Mobile is working fine, loaded with latest firmware OTA updates from OnePlus.
I would like to install TWRP on my mobile but the device is getting detected in the fastboot mode. Tried various steps, reinstalled adb & fastboot as well as OnePlus drivers nothing works. However my mobile is being detected in the adb mode. If I run the command adb devices, it displays my mobile serial number but in fastboot it just sits at the waiting for the device screen.
After a lot of googling, xda search & Oneplus forums search, nothing found. Then I tried reinstalling the adb interface drivers manually, where I have noticed that Win10 installed the latest drivers adb drivers updated in the month of Sep16. Here I have selected the older version driver which was released in the year 2014 and installed it successfully. I run the fastboot devices command again Voila... It worked. no restart, no rebooting the phone. Immediately worked.
Lesson learnt : - Always do not use latest drivers, sometimes try the older drivers if something is not working in your phone.
Click to expand...
Click to collapse
can you share those drivers,,facing same issue actually
Yesterday I tried to flash a a new rom on my Xperia Z2 (unlocked bootloader).
From TWRP I did an advanced wipe and selected basically everything except my mircoSD (because it has the new files).
After a long time of waiting I tried to flash the ZIP file and it gave me an error. I thought this had to do with the wipe so I decided to reboot my phone.
As you can imagine, it got stuck on the Sony logo (because system would be empty).
From this moment I couldn't do anything with my phone, except from the tool Emma.
I now have some clean installation of Sony their Android 6.0.1 for the Z2 (23.5.A.0.570) but Im unable to flash TWRP through fastboot.
The command adb devices shows my phone, fastboot devices gives an empty response.
When I restart to the bootloader from adb and try to flash TWRP I get the message "< waiting for device >".
I tried on three different PCs including a clean install of Windows with all kind of different drivers, yet I cant get fastboot to work.
Am I stuck with this unrooted version of Android now or do you guys have any suggestions for me?
Thanks in advance!
Install drivers correctly
EugenStanis said:
Install drivers correctly
Click to expand...
Click to collapse
As I said I've tried all kind of different drivers (Android tools, Sony drivers and flahstool drivers). So for me it's hard to tell what I'm doing wrong.
My computer notices the phone (if I hold volume up and attach the charger), it just doesn't show up under fastboot devices.
EugenStanis said:
Install drivers correctly
Click to expand...
Click to collapse
Okay, apparently it was because of the driver signature stuff in Windows 10.. The fastboot command now works fine!
Next problem occurred though, flashed the newest TWRP recovery but as soon as I enter "adb reboot recovery" my phone just normally boots again..
Why do things never work out the right way for me as they are intended..
PaulusE said:
Okay, apparently it was because of the driver signature stuff in Windows 10.. The fastboot command now works fine!
Next problem occurred though, flashed the newest TWRP recovery but as soon as I enter "adb reboot recovery" my phone just normally boots again..
Why do things never work out the right way for me as they are intended..
Click to expand...
Click to collapse
Manually boot into recovery by booting up your device normally and when you see a violet LED, press vol+.
Hi People,
I hope I am putting this question in the proper location.
I have had several attempts ate flashing a new ROM to my device as it was the Chinese version & kinda useless to me not having Play store or several other APPs I want. I also wanted to try ROOT a phone for the first time.
I managed to get as far as getting ADB & fastboot working & TWRP installed on the device. The first ROM I had put in my file storage was corrupt so I tried the Lineage 17 version which "seemed"to install with a success message, but the phone would only boot into TWRP. so I tried the Havoc ROM from the thread in this site area. Same thing, would only boot into TWRP. Then I thought I would start over & install the factory ROM from: https://xiaomifirmwareupdater.com/miui/olivelite/stable/V12.0.2.0.QCPMIXM/ with ADB & fastboot. I got a success message from the MiFlash tool but the device is now saying the "MIUI verson cannot be installed on this device" in one screen from the Redmi-Recovery 3.0 menu that's now on it.
From here I can Reboot, wipe data or connect with MiAssistant. When I try MiAssistant (PC Suite) the phone does not connect to my PC but I can see the ADB device from device manager and ./adb fastboot devices shows a serial number -but connected as sideload if that makes a difference?
I hope I explained well enough to be understood. Is there anything I can do from here to get it working or is it fully stuffed?
Ur device's bootloader still unlocked?
T0B3R said:
Hi People,
I hope I am putting this question in the proper location.
I have had several attempts ate flashing a new ROM to my device as it was the Chinese version & kinda useless to me not having Play store or several other APPs I want. I also wanted to try ROOT a phone for the first time.
I managed to get as far as getting ADB & fastboot working & TWRP installed on the device. The first ROM I had put in my file storage was corrupt so I tried the Lineage 17 version which "seemed"to install with a success message, but the phone would only boot into TWRP. so I tried the Havoc ROM from the thread in this site area. Same thing, would only boot into TWRP. Then I thought I would start over & install the factory ROM from: https://xiaomifirmwareupdater.com/miui/olivelite/stable/V12.0.2.0.QCPMIXM/ with ADB & fastboot. I got a success message from the MiFlash tool but the device is now saying the "MIUI verson cannot be installed on this device" in one screen from the Redmi-Recovery 3.0 menu that's now on it.
From here I can Reboot, wipe data or connect with MiAssistant. When I try MiAssistant (PC Suite) the phone does not connect to my PC but I can see the ADB device from device manager and ./adb fastboot devices shows a serial number -but connected as sideload if that makes a difference?
I hope I explained well enough to be understood. Is there anything I can do from here to get it working or is it fully stuffed?
Click to expand...
Click to collapse
You should flash China factory rom, if you can.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
As the title suggests I have a Zenfone Max Pro M2. Currently running LineageOS 16 + TWRP 3.3.1.
I want to upgrade to LineageOS 18.1 so I thought I would update TWRP first, to the latest version (3.5.1). This is because when I installed LineageOS 16 I remember I had to upgrade TWRP for it to work (ROM wouldn't flash with older versions of TWRP).
I got my Android SDK tools from here: https://developer.android.com/studio/releases/platform-tools
I also have adb and fastboot that come from the standard Ubuntu repositories (installed with apt-get).
I'm following this guide to upgrade TWRP: https://twrp.me/asus/asuszenfonemaxprom2.html
And this guide to upgrade LineageOS: https://wiki.lineageos.org/devices/X01BD/install
With both versions of adb (standalone + from repos) it seems that my device is correctly detected:
# adb devices -l
List of devices attached
K9AXB76070808CH recovery usb:1-4 product:X01BD model:Zenfone_Max_Pro_M2 device:X01BD transport_id:2
But once I do adb reboot bootloader, and then fastboot devices, there are no devices showing in fastboot and I can't flash anything. Yes I have tried to run adb/fastboot as root, and obtained the same result.
I've done a lot of looking around on the web and I think this may be a driver issue, but I can't find any drivers for Linux that work with my phone model.
Can someone please help? Let me know if you need more info and I'll provide.
To get Fastboot work
1. enable OEM Unlock in Android's setting - and reboot phone
2. install on computer the official "Android USB Driver" suitable to your phone.
jwoegerbauer said:
To get Fastboot work
1. enable OEM Unlock in Android's setting - and reboot phone
2. install on computer the official "Android USB Driver" suitable to your phone.
Click to expand...
Click to collapse
I've enabled OEM unlock. Where can I find the USB drivers? If you mean these: https://developer.android.com/studio/run/oem-usb#Drivers there's no Linux version.
IDK where to download Linux ready driver.
heavenriver said:
I've enabled OEM unlock. Where can I find the USB drivers? If you mean these: https://developer.android.com/studio/run/oem-usb#Drivers there's no Linux version.
Click to expand...
Click to collapse
Why not do the operation in Win?
jwoegerbauer said:
IDK where to download Linux ready driver.
Click to expand...
Click to collapse
Okay, thanks anyway for trying to help. I hope someone else can supply a working solution.
pucko1 said:
Why not do the operation in Win?
Click to expand...
Click to collapse
Because I only have Linux, and I came here seeking help for how to do this with Linux.
Hello,
Testing Windows on my test Poco F1 after running the windows installer my fastboot does not work anymore.
Windows and MIUI are loading fine, but if i boot to bootloader the phone freeze on POCO logo, in recovery works (miui recovery) i can reinstall miui if i put the device in "mi assistant" in recovery, but the fastboot does not want to start anymore.
I wonder if anyone here know which partition was modified by the WIndows installer, or what was modified that damaged only fastboot mode?
I tried to use MiFlash in EDL mode, but my notebook USB seems to have issues, after finds the right COM port MiFlash say that the hello packet was missed....
Best regards,
Marc
What do you mean by testing windows
Bobmarley2022 said:
What do you mean by testing windows
Click to expand...
Click to collapse
I mean i have installed Windows 10, by testing i mean i am testing some EFI drivers, I created a USB stick with Windows 10 for ARM64 and installed windows, the installer performed some changes to the phone and i wonder if anyone here know what can be changed to brick only fastboot.
serdeliuk said:
I mean i have installed Windows 10, by testing i mean i am testing some EFI drivers, I created a USB stick with Windows 10 for ARM64 and installed windows, the installer performed some changes to the phone and i wonder if anyone here know what can be changed to brick only fastboot.
Click to expand...
Click to collapse
Use mi flash
Bobmarley2022 said:
Use mi flash
Click to expand...
Click to collapse
Unfortunately miflash gives error, say that missed hello packet.
But my question is about what the installer changed that broke the fastboot, i manually created the required partitions and normally nothing else was touched, yet fastboot is not working, but only fastboot mode was damaged