Hi!, I have a bricked Oneplus 2 so heres how it happened
My device was running oxygen os 3.0 with TWRP 3.0 and I decided to flash the resurrection remix ROM on my phone through twrp, and when I did flash it I think it gave me some error code, and then I rebooted my phone and now its stuck in a bootloop with no OS installed.
I tried going to TWRP and adb was not working and adb side load was not working, I went to fastboot and my computer wont detect my device through fastboot. I tried first aid kit and my phone was not being detected. I did try this with using 2 other computers running windows 10 and I tried it with a computer running Linux Mint. How ever when I check in Device Manager It shows "communications port (COM1) I tried updating that driver with the Oneplus 2 Qualcom drivers and it gave me a error code 10 and I tried installing an ADB interface driver to that to and I got the same error code 10. I also tried this method below with no luck.
"https://forums.oneplus.net/threads/updated-29-03-2016-mega-unbrick-guide-for-a-hard-bricked-oneplus-2.347607/"
Please help me and the community facing this problem, Thanks!
I have a same problem. so any advice how to fix this is more than welcome. Except Firstaid kit gave back Recovery (twrp) which Oxygen 3.0 Beta removed etc, Now i have TWRP 2.8.7.0 and thats it. PC just dont find device so that i could transfer nesessary files
E: Does it matter is this Oneplus 2 recovery tool for A2001 or A2003? i just noticed that the one i downloaded, folder name is A2001_save_brick_mini
SirMika said:
I have a same problem. so any advice how to fix this is more than welcome. Except Firstaid kit gave back Recovery (twrp) which Oxygen 3.0 Beta removed etc, Now i have TWRP 2.8.7.0 and thats it. PC just dont find device so that i could transfer nesessary files
E: Does it matter is this Oneplus 2 recovery tool for A2001 or A2003? i just noticed that the one i downloaded, folder name is A2001_save_brick_mini
Click to expand...
Click to collapse
I caint do any thing in twrp to, but I heard that there was a problem with twrp 3.0 that you caint transfer any files to pc, I think you might fix the problem by getting a usb type c usb otg and flashing the stock rom from there possibly. but I doint want to pay the price for it right now, but hopefully I will find a solution
SirMika said:
I have a same problem. so any advice how to fix this is more than welcome. Except Firstaid kit gave back Recovery (twrp) which Oxygen 3.0 Beta removed etc, Now i have TWRP 2.8.7.0 and thats it. PC just dont find device so that i could transfer nesessary files
E: Does it matter is this Oneplus 2 recovery tool for A2001 or A2003? i just noticed that the one i downloaded, folder name is A2001_save_brick_mini
Click to expand...
Click to collapse
And does your phone get recognized by fast boot? because you were saying that you used first aid to get recovery, and first aid uses fastboot, because you will beable to fix your phone through fastboot
yes, i just run fastboot commands and its unlocked etc but PC dont find OPT
---------- Post added at 10:27 AM ---------- Previous post was at 10:23 AM ----------
i just cant figure out how i transfer flashable zips in device to get oxygen or some decent rom
SirMika said:
yes, i just run fastboot commands and its unlocked etc but PC dont find OPT
---------- Post added at 10:27 AM ---------- Previous post was at 10:23 AM ----------
i just cant figure out how i transfer flashable zips in device to get oxygen or some decent rom
Click to expand...
Click to collapse
This might help you if your phone can be detected in fastboot:
http://www.androidsage.com/2016/03/12/restore-oneplus-2-full-stock-firmware/
It is a stock rom that you flash through fastboot
fahad999 said:
This might help you if your phone can be detected in fastboot:
http://www.androidsage.com/2016/03/12/restore-oneplus-2-full-stock-firmware/
It is a stock rom that you flash through fastboot
Click to expand...
Click to collapse
Sure i can try but i dont expect to get this work anymore..at leat awhile. earlier i tried to sideload stock OxygenOS but it failed because it says i need adb v 1.0.32 or newer, and surprise surprise it dont work properly in Windows 10.
SirMika said:
Sure i can try but i dont expect to get this work anymore..at leat awhile. earlier i tried to sideload stock OxygenOS but it failed because it says i need adb v 1.0.32 or newer, and surprise surprise it dont work properly in Windows 10.
Click to expand...
Click to collapse
It should work if your phone is recognized by fastboot, you have to download stock rom fastboot file and extract it, then connect your phone to fastboot to pc, then in the stockrom file click the run-all.bat and your phone should work but the problem with my phone is that my phone is not being recognized by fastboot
fahad999 said:
It should work if your phone is recognized by fastboot, you have to download stock rom fastboot file and extract it, then connect your phone to fastboot to pc, then in the stockrom file click the run-all.bat and your phone should work but the problem with my phone is that my phone is not being recognized by fastboot
Click to expand...
Click to collapse
not sure but i did similar procedure yesterday. see second post http://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863 but i had no idea what i suppose to do..all i had was stock recovery..
in adb, running command fastboot device it shows my phone
Guys I am stuck too, form oxygen os 3.0 I decided to restore my all old backup from twrp, and now my device is fried, recovery is not working too. I tried ton of ways, it can boot into fastboot, but my pc cannot detect it for some reason. In pc no fastboot devices. Nothing in ports. that 10second trick is also not working. Someone plz help
Getsuga Tenshou said:
Guys I am stuck too, form oxygen os 3.0 I decided to restore my all old backup from twrp, and now my device is fried, recovery is not working too. I tried ton of ways, it can boot into fastboot, but my pc cannot detect it for some reason. In pc no fastboot devices. Nothing in ports. that 10second trick is also not working. Someone plz help
Click to expand...
Click to collapse
it seems there is no way to fix it..my skills and knoledge aint high, but i´v done all by the book and nothing. it also goes in fastboot and twrp but thats it. i wish i could help you but were in a same boat
Getsuga Tenshou said:
Guys I am stuck too, form oxygen os 3.0 I decided to restore my all old backup from twrp, and now my device is fried, recovery is not working too. I tried ton of ways, it can boot into fastboot, but my pc cannot detect it for some reason. In pc no fastboot devices. Nothing in ports. that 10second trick is also not working. Someone plz help
Click to expand...
Click to collapse
Danm, that sucks. Later I may try using a virtual machine of Linux Mint on my computer and see if it will detect my phone in fastboot. And the sad thing is that this oneplus 2 is my only phone
Getsuga Tenshou said:
Guys I am stuck too, form oxygen os 3.0 I decided to restore my all old backup from twrp, and now my device is fried, recovery is not working too. I tried ton of ways, it can boot into fastboot, but my pc cannot detect it for some reason. In pc no fastboot devices. Nothing in ports. that 10second trick is also not working. Someone plz help
Click to expand...
Click to collapse
Just to refresh, the problem that we are looking at is that your PC does not recognize our phone (Driver Problem)
So together we have to find a solution to this driver problem, so this is the main problem. I myself am running Windows 10
fahad999 said:
Just to refresh, the problem that we are looking at is that your PC does not recognize our phone (Driver Problem)
So together we have to find a solution to this driver problem, so this is the main problem. I myself am running Windows 10
Click to expand...
Click to collapse
I think i need to get in my hands PC with Win7. i also came that conclusion the problem is Windows.
Oneplus drivers (/D) just keep pop-upping asking what todo, when selected nothing happens
EDIT: is it possible install proper softwares via USBstorage?
Guys, I am running a dual boot machine (windows 7 and 10) and on both there is not even a sign of detection. Same is happening on another laptop which runs on windows 7 too. Only phone boots to bootloader on connected (like a charger and nothing else).
Just before my fp stopped working. Last time it did, my usb type c cable also died. This time I don't know since I directly restored from twrp and did not connect it to my pc. There is a slight chance that our usb type c cables have malfunctioned (which is better than permanent brick). If you have any access/ friend with that cable please try it. If it works we might be in luck.
Note: SirMika, For you usb is working, you do not need to try this, did you try flashing revert files
Getsuga Tenshou said:
Guys, I am running a dual boot machine (windows 7 and 10) and on both there is not even a sign of detection. Same is happening on another laptop which runs on windows 7 too. Only phone boots to bootloader on connected (like a charger and nothing else).
Just before my fp stopped working. Last time it did, my usb type c cable also died. This time I don't know since I directly restored from twrp and did not connect it to my pc. There is a slight chance that our usb type c cables have malfunctioned (which is better than permanent brick). If you have any access/ friend with that cable please try it. If it works we might be in luck.
Note: SirMika, For you usb is working, you do not need to try this, did you try flashing revert files
Click to expand...
Click to collapse
I just got a Linux Mint virtual machine and still the phone is not being detected via ADB and Fastboot in Linux Mint, I think the only possible solution that we have is purchasing a USB Type C USB OTG and Side-loading a ROM on their and flashing it through recovery. But this possible solution is for people who still have access to their recovery and luckily I do.
Oxygen OS 3.0 Flashable ZIP: http://downloads.oneplus.net/2016-03-30/op2/OnePlus_2_OxygenOS_3.0_Beta/
USB TYPE C OTG: http://www.amazon.com/Adapter-RAVPo...qid=1463938874&sr=8-1&keywords=usb+type+c+otg
fahad999 said:
I just got a Linux Mint virtual machine and still the phone is not being detected via ADB and Fastboot in Linux Mint, I think the only possible solution that we have is purchasing a USB Type C USB OTG and Side-loading a ROM on their and flashing it through recovery. But this possible solution is for people who still have access to their recovery and luckily I do.
Oxygen OS 3.0 Flashable ZIP: http://downloads.oneplus.net/2016-03-30/op2/OnePlus_2_OxygenOS_3.0_Beta/
USB TYPE C OTG: http://www.amazon.com/Adapter-RAVPo...qid=1463938874&sr=8-1&keywords=usb+type+c+otg
Click to expand...
Click to collapse
Update! I know why our phones are bricked! when we installed custom roms you wiped the phone right. I was reading that there was a new feature in android in which you wipe the phone with a password, the bootloader gets locked. So I believe that our devices now have a locked bootloader
fahad999 said:
I caint do any thing in twrp to, but I heard that there was a problem with twrp 3.0 that you caint transfer any files to pc, I think you might fix the problem by getting a usb type c usb otg and flashing the stock rom from there possibly. but I doint want to pay the price for it right now, but hopefully I will find a solution
Click to expand...
Click to collapse
in twrp press format data (i mean format data no wipe data)...then yes...reboot and now your phone is well partitioned
after that (in orange twrp flash a oxygen oos 3.0 or h2os) or if you want to return to oos 2.x or any other custom rom use the LP steps in this forum....http://forum.xda-developers.com/oneplus-2/general/guide-helper-zips-to-switch-oos-3-0-oos-t3351253
---------- Post added at 10:26 PM ---------- Previous post was at 10:15 PM ----------
Getsuga Tenshou said:
Guys I am stuck too, form oxygen os 3.0 I decided to restore my all old backup from twrp, and now my device is fried, recovery is not working too. I tried ton of ways, it can boot into fastboot, but my pc cannot detect it for some reason. In pc no fastboot devices. Nothing in ports. that 10second trick is also not working. Someone plz help
Click to expand...
Click to collapse
see in connected devices that there is one that has no name or isnt recogniced the press update driver and choose update from a list drivers not update from online then choose android device and then try every (google or clockworkmod driver i think that the one who work is android adb interface...then your computer should detect your phone if not search one the internet because every computer is different in terms of drivers i am telling you the way that i solve alway in mine (you can allways use that chinese program to restore your phone to oos 2.1.1)
Guihardrock said:
in twrp press format data (i mean format data no wipe data)...then yes...reboot and now your phone is well partitioned
after that (in orange twrp flash a oxygen oos 3.0 or h2os) or if you want to return to oos 2.x or any other custom rom use the LP steps in this forum....http://forum.xda-developers.com/oneplus-2/general/guide-helper-zips-to-switch-oos-3-0-oos-t3351253
---------- Post added at 10:26 PM ---------- Previous post was at 10:15 PM ----------
see in connected devices that there is one that has no name or isnt recogniced the press update driver and choose update from a list drivers not update from online then choose android device and then try every (google or clockworkmod driver i think that the one who work is android adb interface...then your computer should detect your phone if not search one the internet because every computer is different in terms of drivers i am telling you the way that i solve alway in mine (you can allways use that chinese program to restore your phone to oos 2.1.1)
Click to expand...
Click to collapse
Sorry to say that this is not working for me and I have no OS installed, I formatted data in twrp and typed yes and still I got no luck. My device is not being recognized by pc in twrp, I installed many drivers (Oneplus Drivers, Google USB Drivers, 15 Sec ADB & Fastboot Drivers, Universal ADB Drivers) Still I got no luck, and nothing shows up in device manager, I tried this in 2 Computers awwell.
i have unlocked bootloader, latest TWRP but no OS. instead zip fils it should be image. adb cant find phone but fast boot does
Related
Hello,
After few months with my n1, finally I decide to root and put some roms.
Even when I already have done with my magic, tatoo, and hero, I can´t handle the driver problems in my nexus one.
I could unlock the bootloader. My problems came after this step.
Ive tested few things, but I will put my last experience.
In a just-formatted windows XP sp3, I downloaded the last android SDK and Ive downloaded the usb driver (R3).
After this, I connect my nexus one phone and it asked me for the drivers, I gave the path and it was successfully installed.
I unplugged the USB cable, turn the phone off and restart in debug mode, bootlader. Plug the cable, my PC reconigzed "something", and install some driver. "Unknowledge device". So, I tried to update the driver, giving the path to the USB-driver folder (inside of android-sdk-windows folder). And nothing. It tells me that there is not a better driver for my device. And I can´t connect to my phone. Of course Ive tried uninstalling the driver and nothing. (always from control panel).
I dont know what to do. Please, give me some suggestion because im totally frustrated.
Thank you
http://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/Posted Yesterday, 10:17 PM
ATT N1's can run CyanogenMod without any real trouble. The commands and guides remain the same as the Tmo N1
THE ONLY CAVEAT IS: YOU CANNOT USE CM 5.0.5.1 or 5.0.5.2 as your initial install base, as these releases were bugged. Use 5.0.5 here
For Nexus' you DO NOT NEED SUPERBOOT and steps are super easy.
Setup ADB/FASTBOOT
Fastboot oem unlock
fastboot flash recovery recovery-ra-blah-blah.img
Reboot into recovery
NANDROID
WIPE!!!! (if you dont wipe you get boot loops)
Flash CM
Flash Google (optional)
Reboot
Fastboot flash radio radio.img (unnecessary on ATT n1's)
cheloman said:
Hello,
After few months with my n1, finally I decide to root and put some roms.
Even when I already have done with my magic, tatoo, and hero, I can´t handle the driver problems in my nexus one.
I could unlock the bootloader. My problems came after this step.
Ive tested few things, but I will put my last experience.
In a just-formatted windows XP sp3, I downloaded the last android SDK and Ive downloaded the usb driver (R3).
After this, I connect my nexus one phone and it asked me for the drivers, I gave the path and it was successfully installed.
I unplugged the USB cable, turn the phone off and restart in debug mode, bootlader. Plug the cable, my PC reconigzed "something", and install some driver. "Unknowledge device". So, I tried to update the driver, giving the path to the USB-driver folder (inside of android-sdk-windows folder). And nothing. It tells me that there is not a better driver for my device. And I can´t connect to my phone. Of course Ive tried uninstalling the driver and nothing. (always from control panel).
I dont know what to do. Please, give me some suggestion because im totally frustrated.
Thank you
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=613217
Try those drivers.
jerrycycle said:
...For Nexus' you DO NOT NEED SUPERBOOT and steps are super easy.
Click to expand...
Click to collapse
jerrycycle said:
fastboot flash recovery recovery-ra-blah-blah.img
Click to expand...
Click to collapse
Thank you by your post, it was very usefull and I could change my drivers, so I have access in debug mode to my n1. Even with this, Ive tried to apply the root with modaco´s files, using the original ERE27 pack, but, it just stucks in "copying...".
Maybe the problem is that I was instructed about I should execute the .bat, in bootloader moder (no in fastboot). I have the adb commands with fastboot mode, but, when I do: fastboot devices in bootloader mode, I dont have any device. Maybe the tutorial that I followed its wrong and should I execute directly in fastboot not in bootloader.
Anyway, Ive quoted your post, because when you say that isnt necessary, the instructions of recovery installation, says about its a "pre-requirement"
You can check it in /showthread.php?t=611829 As new user, i cant put the link to the thread of RA recovery, sorry
I dont want to mess with this, because the consequence of bad procedure.
Thank you by your help and patience.
you might want to make sure you're using the main USB ports, not those extension ones or those that are built into PC cases. I used to have the problem with "unrecognised device" because of that.
Team Win Recovery Project 3.x, or TWRP3.x for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Download : TWRP For Catfish
Source Device Tree: Device Tree For Building TWRP
reserved
Thanks.
However...is there anyone would share a twrp backup of Chinese version stock rom? Thanks in advance.
What's the command to install this?
Sent from my BLA-L29 using Tapatalk
tfpiaoyang said:
Thanks.
However...is there anyone would share a twrp backup of Chinese version stock rom? Thanks in advance.
Click to expand...
Click to collapse
https://mega.nz/#F!BEFGBQKI!uetGnJxWqvG-JRmQNPeBvw
btw any qq grp to communicate?
MicrosoftBug said:
What's the command to install this?
Sent from my BLA-L29 using Tapatalk
Click to expand...
Click to collapse
fastboot oem unlock
fastboot flash recovery ***.img
restore to chinese version cant OTA, will get a big red "!" in recovery...
I have been out of the custom recovery world too long and never tried on a watch before. Trying to flash twrp on my new TW Pro (H) so I can flash janjans rom. Have ADB and drivers (windows 7), have twrp.img ready.
cmd prompt not recognizing adb command. Cant remember how to proceed...how to open fasboot, unlock bootloader.
I know im missing something simple but stuck. Can anyone help jumpstart me?
Update: Got twrp installed after flailing about for awhile. Bottom line, operator error.
This may be the wrong place to post, but I can't seem to find my issue anywhere and I'm getting a little desperate.
I'm Stuck! Accidentally deleted 'system' int twrp when deleting data for a reset for the watch. Now no OS installed and computer doesn't want to recognize the ticwatch pro through usb (directly attached to dock and then usb to windows 10). I'm not sure it's a driver issue because it should at least be recognized in device manager as 'unknown' but nothing is showing. I now only have bootloader and twrp recovery on my watch. I have everything I need to reinstall the os, but without a way to connect to the watch I can't move the files to the watch to flash it, nor can I connect through usb to push them over! I'm stuck! I'm missing something simple I'm sure, but I don't know what? I just want a way to connect the watch from it's dock to windows 10 through usb cable from watch dock. Then I'm good to go. But I can't.
HELP Please!
haplohaplo said:
This may be the wrong place to post, but I can't seem to find my issue anywhere and I'm getting a little desperate.
I'm Stuck! Accidentally deleted 'system' int twrp when deleting data for a reset for the watch. Now no OS installed and computer doesn't want to recognize the ticwatch pro through usb (directly attached to dock and then usb to windows 10). I'm not sure it's a driver issue because it should at least be recognized in device manager as 'unknown' but nothing is showing. I now only have bootloader and twrp recovery on my watch. I have everything I need to reinstall the os, but without a way to connect to the watch I can't move the files to the watch to flash it, nor can I connect through usb to push them over! I'm stuck! I'm missing something simple I'm sure, but I don't know what? I just want a way to connect the watch from it's dock to windows 10 through usb cable from watch dock. Then I'm good to go. But I can't.
HELP Please!
Click to expand...
Click to collapse
Did you try running fastboot from bootloader? Also maybe try sideload the rom from twrp, that worked for me.
haplohaplo said:
This may be the wrong place to post, but I can't seem to find my issue anywhere and I'm getting a little desperate.
I'm Stuck! Accidentally deleted 'system' int twrp when deleting data for a reset for the watch. Now no OS installed and computer doesn't want to recognize the ticwatch pro through usb (directly attached to dock and then usb to windows 10). I'm not sure it's a driver issue because it should at least be recognized in device manager as 'unknown' but nothing is showing. I now only have bootloader and twrp recovery on my watch. I have everything I need to reinstall the os, but without a way to connect to the watch I can't move the files to the watch to flash it, nor can I connect through usb to push them over! I'm stuck! I'm missing something simple I'm sure, but I don't know what? I just want a way to connect the watch from it's dock to windows 10 through usb cable from watch dock. Then I'm good to go. But I can't.
HELP Please!
Click to expand...
Click to collapse
That is probably a faulty USB cable, try a different cable or a different PC, Windows 10 should recognize your watch automatically and if you have generic adb drivers previously installed, it should work.
You may also try to manually install the drivers from here:
https://www.xda-developers.com/where-to-download-android-usb-drivers/
Kellicros said:
That is probably a faulty USB cable, try a different cable or a different PC, Windows 10 should recognize your watch automatically and if you have generic adb drivers previously installed, it should work.
You may also try to manually install the drivers from here:
https://www.xda-developers.com/where-to-download-android-usb-drivers/
Click to expand...
Click to collapse
Thanks. I've tried three different chargers (though I'm not sure if the other two that I bought are actually capable of transmitting data) and three different computers. I ordered a new charger that says it is able to transmit data, so hopefully when that arrives it will work. Makes no sense to me that I can get into bootloader and twrp and yet not see the watch in device manager.
Kellicros said:
That is probably a faulty USB cable, try a different cable or a different PC, Windows 10 should recognize your watch automatically and if you have generic adb drivers previously installed, it should work.
You may also try to manually install the drivers from here:
https://www.xda-developers.com/where-to-download-android-usb-drivers/
Click to expand...
Click to collapse
Thanks for the reply. I've got 4 different chargers (including the oem one) two of the additional ones I have state they are capable of data sync. I've tried them on 3 different computers and the watch doesn't not show in device manager, recognized or otherwise. I just can't see this as a cable issue, but I don't know what else to think. I just received the newest sync cable I ordered the other day (now my fourth) and still nothing. I'm stuck. If it would at least show in device manager then it would only be a matter of drivers, but it doesn't. Seems a little odd to me that it stopped when I accidentally deleted the OS. The OS isn't even required for bootloader or TWRP and both of those load on the watch. I can't figure it out and I opened a repair ticket with Mobvoi a few days ago, but there has been no response yet. So frustrating!
haplohaplo said:
Thanks for the reply. I've got 4 different chargers (including the oem one) two of the additional ones I have state they are capable of data sync. I've tried them on 3 different computers and the watch doesn't not show in device manager, recognized or otherwise. I just can't see this as a cable issue, but I don't know what else to think. I just received the newest sync cable I ordered the other day (now my fourth) and still nothing. I'm stuck. If it would at least show in device manager then it would only be a matter of drivers, but it doesn't. Seems a little odd to me that it stopped when I accidentally deleted the OS. The OS isn't even required for bootloader or TWRP and both of those load on the watch. I can't figure it out and I opened a repair ticket with Mobvoi a few days ago, but there has been no response yet. So frustrating!
Click to expand...
Click to collapse
You deleted the OS? What do you mean by that? Is the watch still working on its own?
Sounds to me like a faulty connector, I would send it back if it is still under warranty.
I wiped the system folder by mistake. I got click happy when doing an advanced wipe. My fat thumbs ticked the system folder. So no OS installed now. Just bootloader and TWRP. But since the watch isn't recognized by any PC on any of the 4 cables I have, I can't move a Rom on to it to flash it. Nor can I push one over on adb as neither fastboot in bootloader or adb in TWRP see the watch. Not a driver issue since I've tried every one I could find and because device manager doesn't see the watch at all, know or unknown.
haplohaplo said:
I wiped the system folder by mistake. I got click happy when doing an advanced wipe. My fat thumbs ticked the system folder. So no OS installed now. Just bootloader and TWRP. But since the watch isn't recognized by any PC on any of the 4 cables I have, I can't move a Rom on to it to flash it. Nor can I push one over on adb as neither fastboot in bootloader or adb in TWRP see the watch. Not a driver issue since I've tried every one I could find and because device manager doesn't see the watch at all, know or unknown.
Click to expand...
Click to collapse
Try 1. Flash boot.img via fastboot
2. Reboot and connect, check via adb if it's detected
3. Install via sideload ROM
(adb sideload file.zip)
This issue was that I couldn't connect with fastboot at all. That being said, it turns out the problem was with the watch itself. Mobvoi, replaced the watch with a brand new one free of charge so it's all good now.
Any chance you have, or know of, a TWRP for the TicWatch E2/S2 ?
Would be much appreciated.
Hey, is it possible to connect a SD card or usb flash drive to the watch via otg when booted into twrp to create a full backup?
Hello, what would I need to do in order to port this to the TicWatch Pro 2020? The hardware is almost identical, except it has more RAM, the codename is catfish_ext. I have an unlocked bootloader and tried to boot this recovery, but I get FAILED (remote: 'dtb not found').
EDIT: Nevermind, I have found that the recovery for the 4G EU verison also works with mine. Here is the link to a working image: https://drive.google.com/file/d/1XNejRoLecLeadEj1CAW_zrTUP5bkUJZ8/view?usp=sharing
And here is the original source: https://forum.xda-developers.com/smartwatch/other-smartwatches/rom-kernel-t3821013
I am not able to get Fastboot to reconginze my One Plus 6T. I have reinstalled the drivers numerous times to no avail. I have changed ports to no avail. I have change USB cables to no avail. Is anyone else having a similar problem and if so, any solution?
BTW, I am using a Windows 10 computer.
Also, I was able to install the International Version on my TMO variant One Plus 6T via the MSM tool method, so the drivers appear to be installed correctly.
Thank you in advance for any assistance.
phaino00 said:
I am not able to get Fastboot to reconginze my One Plus 6T. I have reinstalled the drivers numerous times to no avail. I have changed ports to no avail. I have change USB cables to no avail. Is anyone else having a similar problem and if so, any solution?
BTW, I am using a Windows 10 computer.
Also, I was able to install the International Version on my TMO variant One Plus 6T via the MSM tool method, so the drivers appear to be installed correctly.
Thank you in advance for any assistance.
Click to expand...
Click to collapse
Delete the drivers you have installed, boot into fastboot and have Windows automatically detect and install for you. Have you tried that? What source did you get your fastboot drivers from?
phaino00 said:
I am not able to get Fastboot to reconginze my One Plus 6T. I have reinstalled the drivers numerous times to no avail. I have changed ports to no avail. I have change USB cables to no avail. Is anyone else having a similar problem and if so, any solution?
BTW, I am using a Windows 10 computer.
Also, I was able to install the International Version on my TMO variant One Plus 6T via the MSM tool method, so the drivers appear to be installed correctly.
Thank you in advance for any assistance.
Click to expand...
Click to collapse
Msmdownload drivers are not the same at all, they are Qualcom drivers. Uninstall your fastboot drivers and let windows install them
phaino00 said:
I am not able to get Fastboot to reconginze my One Plus 6T. I have reinstalled the drivers numerous times to no avail. I have changed ports to no avail. I have change USB cables to no avail. Is anyone else having a similar problem and if so, any solution?
BTW, I am using a Windows 10 computer.
Also, I was able to install the International Version on my TMO variant One Plus 6T via the MSM tool method, so the drivers appear to be installed correctly.
Thank you in advance for any assistance.
Click to expand...
Click to collapse
Oh man, I had issues getting my 6t to connect to my PC when I first got my 6t. The answer for me was to plug my phone into a USB 2.0 port on the BACK of my PC instead of the front USB ports my PC has. Try using the back USB ports and let me know if that works for you!
Thank you all. I will try these suggestions later today and report back.
I tried the suggestions and still no success in fastboot connecting with my device. Thanks again for the suggestions.
After trying to multiple times reinstall the drivers, manually selecting "Android Bootloader Interface" did the trick for me on win10:
wtfandroid.com/fix-fastboot-device-not-recognised-problem/
Issue resolved. Selected Android Bootloader Interface in Device Manager and fastboot recognized my device. Unlocked Bootloader, installed TWRP and Magisk. Root achieved.
Thank you all!!!
jullev said:
After trying to multiple times reinstall the drivers, manually selecting "Android Bootloader Interface" did the trick for me on win10:
wtfandroid.com/fix-fastboot-device-not-recognised-problem/
Click to expand...
Click to collapse
Thank you! I can't believe I didn't think to check that.
it is solved for me oneplus 6t not recognized in fastboot
{ solved for me } hello brother, i got this problem also my head was about to explosing, install/uninstall drivers and adb drivers also, without any success, when the device is on normal mod the adb terminal can recognize it and in fastboot mod not recognize my devie (the list empty).
i was trying to install TWRP, so i have reboot my device to fastboot mod, and i didn't think about List of devices (because it not show my device) i wrote the comand to install TWRP directly so it success to install 100%,
so no need to write : adb devices when your device is in fastboot mod, it will not show you in the list, but you can apply what you want normally
good luck
hichemkanon said:
{ solved for me } hello brother, i got this problem also my head was about to explosing, install/uninstall drivers and adb drivers also, without any success, when the device is on normal mod the adb terminal can recognize it and in fastboot mod not recognize my devie (the list empty).
i was trying to install TWRP, so i have reboot my device to fastboot mod, and i didn't think about List of devices (because it not show my device) i wrote the comand to install TWRP directly so it success to install 100%,
so no need to write : adb devices when your device is in fastboot mod, it will not show you in the list, but you can apply what you want normally
good luck
Click to expand...
Click to collapse
Hello. I am having the same issues. But can you provide more steps on how to install TWRP. Can you provide the command/steps used to directly install TWRP?
Thank you.
phaino00 said:
Issue resolved. Selected Android Bootloader Interface in Device Manager and fastboot recognized my device. Unlocked Bootloader, installed TWRP and Magisk. Root achieved.
Thank you all!!!
Click to expand...
Click to collapse
Did this and still not able to recognize it in fastboot mode
sonice43 said:
Hello. I am having the same issues. But can you provide more steps on how to install TWRP. Can you provide the command/steps used to directly install TWRP?
Click to expand...
Click to collapse
Rijul30 said:
Did this and still not able to recognize it in fastboot mode
Click to expand...
Click to collapse
This is why I use Linux in my LOS Install Guide. You can boot Linux from a USB without installing it. Fastboot and ADB just work, without any drivers. Install TWRP, reboot and your PC will be back to windows. My guide covers installing TWRP.
Really need help. I'm going in circles and wasting a lot of time:
I'm attempting to root a OP6T A6013. Its already been unlocked.
My device is recognized when powered up as an ADB device.
But when i boot into the bootloader it isnt recognized as a fastboot device, and my laptop (Win 8.1) shows ""device malfunctioned. USB not recognized". I've also been trying to install the OP driver but I'm not sure its working correctly. But would that cause the problem with recognizing fastboot?
I've root my OP7Pro (twice, actually) and though I had some driver issues then eventually figured it out. But I never had issues with fastboot.
Any tips or direction?
Hey all , replying to share my solution to this exact problem I was having..
My OP6T (T-Mobile converted to international) was not showing in fastboot devices but showed in ADB.. after hours of searching google and XDA , I ended up just plugging my 6T into another computer and it worked! , instantly recognized my device without hassle.
So just a fyi, it could be something simple as switching USB ports or even another computer.
hopefully this helps if someone get's stuck at this point.
I had this issue with a OP8Pro... I went to Windows Update and selected View Optional Updates and found Android Bootloader Device on the list. I selected this to download, and then fastboot worked perfectly.
OhioYJ said:
This is why I use Linux in my LOS Install Guide. You can boot Linux from a USB without installing it. Fastboot and ADB just work, without any drivers. Install TWRP, reboot and your PC will be back to windows. My guide covers installing TWRP.
Click to expand...
Click to collapse
sudo fastboot oem unlock worked in linux in first shot while windows was unable to recognize the device.
Thanks a ton.
EDIT : Just to add .. this linux was in VM
OhioYJ said:
This is why I use Linux in my LOS Install Guide. You can boot Linux from a USB without installing it. Fastboot and ADB just work, without any drivers. Install TWRP, reboot and your PC will be back to windows. My guide covers installing TWRP.
Click to expand...
Click to collapse
I agree. Linux is far better when flashing android phones
anonymoustl said:
I had this issue with a OP8Pro... I went to Windows Update and selected View Optional Updates and found Android Bootloader Device on the list. I selected this to download, and then fastboot worked perfectly.
Click to expand...
Click to collapse
This worked for my OnePlus 9 Pro running Windows 10. Happy modding!
Hello everyone, so I recently flashed android 10.3.1 on my OnePlus 6t device.
After that I found that I no longer have TWRP as my recovery mode.
Now I'm trying to flash TWRP and root the device again.
But every time I get into fastboot mode, the phone gets stuck on it, and my windows 10 cannot detect my device anymore.
any suggestions?
try a different pc i have never used windows 10 only 7 or xp without any issues, the reason why twrp keeps going is because of stock rom verification, if you want to keep twrp then root and flash with custom rom, reflash twrp if necessary and then all will be fine.
Hope that resolves all your isssues
sajeel said:
try a different pc i have never used windows 10 only 7 or xp without any issues, the reason why twrp keeps going is because of stock rom verification, if you want to keep twrp then root and flash with custom rom, reflash twrp if necessary and then all will be fine.
Hope that resolves all your isssues
Click to expand...
Click to collapse
I just tried the same steps on windows 7 and got the same result, Once My phone gets into fastboot mode, my windows cannot detect it.
Does it show up in device manager at all? Perhaps as an unrecognized device?
xijar said:
Does it show up in device manager at all? Perhaps as an unrecognized device?
Click to expand...
Click to collapse
I think it does as an unrecognized device, but I tried to update it and nothing changed.
Im thinking it might be that the last version of TWRP os not compatible with 10.3.1 ?
YousefHadder said:
I think it does as an unrecognized device, but I tried to update it and nothing changed.
Im thinking it might be that the last version of TWRP os not compatible with 10.3.1 ?
Click to expand...
Click to collapse
That has strictly nothing to do with twrp
Driver issue or try another USB port or try another cable
Striatum_bdr said:
That has strictly nothing to do with twrp
Driver issue or try another USB port or try another cable
Click to expand...
Click to collapse
I've tried this before, but I don't think its a cable or port issue because before going into fastboot mode, it was detected by my laptop.
Thank you all, but it turned out to be a TWRP Issue, I found the solution on another post here at this forum with the latest unofficial stable TWRP version.
Now my device is rooted again and everything works fine
Tried miui 12 and after flashing rom the twrp is gone I tried to reflash it the same way I did first but sadly when I'm on fastboot PC can't detect it. also tried it with other softwares but same result. Device is fine and responds when open but not in fastboot mode. Currently running miui 11 .0.6 China stable. Stucked. Also all drivers are updated
Same here.
I accidentally flashed china stable 11.0.4 zip rom on my global device through twrp and upon booting up twrp was gone and when i plug in usb the pc doesn't detect anything. In order to make pc detect the phone via usb cable i have to reboot phone while plugging usb to laptop that way file transfer option shows up in laptop and adb works but fastboot doesn't work i can force boot to fastboot through adb but upon booting to fastboot the pc stucks at waiting for device. All the drivers are installed
Currently on china stable 11.0.6
Same issue indeed
That's exactly what's happening right now. I hope someone can help us
Quote me if u find any luck.
Same issues
That happens me sometimes. I only reboot the device into fastboot again, reboot the computer, and that it. This may change depending on your computer CPU, mine is AMD. And ussually I have to use a 2.0 USB or if it still does not work a USB 2.0 hub. I know the hub thing is strange but it worked for me when my pc does not detect the phone in fastboot. Hope it helps .
With my PC I have to open device manager, look for the device, usually has a yellow sign next to it. Right click on the device name, click update driver, click browse my computer for driver software, click let me pick from a list of available drivers on my computer and pick mtp USB device. Then I read it. I hope this helps.
daniml3 said:
That happens me sometimes. I only reboot the device into fastboot again, reboot the computer, and that it. This may change depending on your computer CPU, mine is AMD. And ussually I have to use a 2.0 USB or if it still does not work a USB 2.0 hub. I know the hub thing is strange but it worked for me when my pc does not detect the phone in fastboot. Hope it helps .
Click to expand...
Click to collapse
What hub?
Tried with multiple pcs with no success
epicblue8 said:
What hub?
Tried with multiple pcs with no success
Click to expand...
Click to collapse
I use a usb hub that is very old i guess, as it uses MiniUSB. By the way with multiple computer it should work, your error is very strange, I never saw it. A thing that may work is trying to use fastboot on a Linux system (no, with VMs no). So if you can flash a pen drive with a Ubuntu ISO or any linux distro, boot linux,install fastboot and check if it detects your phone.
daniml3 said:
I use a usb hub that is very old i guess, as it uses MiniUSB. By the way with multiple computer it should work, your error is very strange, I never saw it. A thing that may work is trying to use fastboot on a Linux system (no, with VMs no). So if you can flash a pen drive with a Ubuntu ISO or any linux distro, boot linux,install fastboot and check if it detects your phone.
Click to expand...
Click to collapse
Read my 1st reply to this op
Even file transfer option doesn't show up if i connect my phone via usb to laptop.
In order to make pc show file transfer option i have to reboot phone while connecting the phone to pc so.
That way i can use adb but as soon as i boot to fastboot via cmd pc doesn't detect the fastboot mode.
Tried with 3 laptops
Issue Fixed
epicblue8 said:
Same here.
I accidentally flashed china stable 11.0.4 zip rom on my global device through twrp and upon booting up twrp was gone and when i plug in usb the pc doesn't detect anything. In order to make pc detect the phone via usb cable i have to reboot phone while plugging usb to laptop that way file transfer option shows up in laptop and adb works but fastboot doesn't work i can force boot to fastboot through adb but upon booting to fastboot the pc stucks at waiting for device. All the drivers are installed
Currently on china stable 11.0.6
Click to expand...
Click to collapse
Dude I fixed it and I managed to flash global and maybe reflash EU when miui 12 stable arrive
Try another type c cord preferable the original one. I just change the cord and everything went fine fastboot can now be detected via "fastboot devices".
Chipotle crackers said:
Dude I fixed it and I managed to flash global and maybe reflash EU when miui 12 stable arrive
Try another type c cord preferable the original one. I just change the cord and everything went fine fastboot can now be detected via "fastboot devices".
Click to expand...
Click to collapse
Not with original but tried 3 type c cables and 3 pcs
epicblue8 said:
Quote me if u find any luck.
Click to expand...
Click to collapse
hey have find any solutions? we have the same problem