OPO did not registered at device manager win 10 - ONE Q&A, Help & Troubleshooting

Hi
Was my mistake,,,,,my opo was in good running condition and I use RR latest6.0.1 M
Today flash in Turga TWRP 3.0.3.1 reolacing official TWRP 3.0.2.0
Flash turga using fastboot .......and wrong command entered to boot
recovery.img. adb stuck and I pulled out the unit without cancelling the
link inside win 10.
Try to flash another twrp version....found out no communication between
my opo and win 10.
Tried many many procedure to rectify this .......no success.
Is fastboot coding kaput?
How to rectify this.............help me please.

RedBux said:
Hi
Was my mistake,,,,,my opo was in good running condition and I use RR latest6.0.1 M
Today flash in Turga TWRP 3.0.3.1 reolacing official TWRP 3.0.2.0
Flash turga using fastboot .......and wrong command entered to boot
recovery.img. adb stuck and I pulled out the unit without cancelling the
link inside win 10.
Try to flash another twrp version....found out no communication between
my opo and win 10.
Tried many many procedure to rectify this .......no success.
Is fastboot coding kaput?
How to rectify this.............help me please.
Click to expand...
Click to collapse
You're computer isn't recognizing your device? Is recovery working? Have you booted into recovery and tried the PC connection from there?

1.....Yes
2.....Yes
3.......NO
You mean ADB side load or Mount to computer? IF
that you meant NO I did not try yet.

fixed
striped down win 10
force in adb driver into device manager

Related

Can't flash twrp need help!

Okay so I received my opo today and wanted to unlock and root etc.. I managed to install drivers and download a toolkit which managed to unlock my bootloader but wouldn't flash the recovery so I attempted it manually via fastboot and after flashing it would reboot to a back screen then vibrate and reboot to system.. Been doing that all night? Any ideas? many thanks in advance new to this phone
Exactly what recovery version are you trying to flash? What OS is on the phone? Get rid of the toolkit, they're nothing but trouble.
Twrp 2.8.1. And its running android 4.4.4 cyanogen mod.. I have mate haha. I take it fastboot and adb are installed correctly as it shows my opo after typing fastboot devices and it unlocked my boot loader soo I'm confused
daviss101 said:
Twrp 2.8.1. And its running android 4.4.4 cyanogen mod.. I have mate haha. I take it fastboot and adb are installed correctly as it shows my opo after typing fastboot devices and it unlocked my boot loader soo I'm confused
Click to expand...
Click to collapse
Try flashing the recovery again, followed by this command
Code:
fastboot erase cache
Then:
Code:
fastboot reboot
Then try booting into recovery.
PS. You've unchecked the "update CM recovery" option in Developer Options, right?
same problem for me. tried manually installing any custom recovery, tried two different toolkits. it flashes and reboots, but then you can never enter the recovery app. even attempting to put stock back fails. i attempted the format the cache and that didn't do a thing for me. basically had to enable cm recovery updates and reset to factory in the os. after that i was back to scratch at least.
I was able to figure it out. Appears the version of TWRP is quite particular for some reason. Once I tried the latest build from here dl dot twrp dot me/bacon/ the problem was solved. Thanks for the tip @snickler
GrizzlyD said:
I was able to figure it out. Appears the version of TWRP is quite particular for some reason. Once I tried the latest build from here dl dot twrp dot me/bacon/ the problem was solved. Thanks for the tip @snickler
Click to expand...
Click to collapse
No problemo. ^_^

Revert from OxygenOS to Cyannogen - problem with recovery

Hi,
Last month I've successfully switched my Oneplus One 16Gb to official Oxygen OS 2.1.4
Finaly I prefer the Cyanogen version and here I have a problem with the recovery tool.
I can't replace OxygenOS recovery at all and with it : not possible to install "super su" or cyanogen 12.1 rom.
With adb the installation of TWRP recovery or or cm12.1 recovery seems to work fine (transfer ok and no errors) but when I restart in recovery mode ((power + volume down) It's still OxygenOS Recovery in my phone.
Please help, I don't want to be stuck in this state :crying:
sylvainsjc said:
Hi,
Last month I've successfully switched my Oneplus One 16Gb to official Oxygen OS 2.1.4
Finaly I prefer the Cyanogen version and here I have a problem with the recovery tool.
I can't replace OxygenOS recovery at all and with it : not possible to install "super su" or cyanogen 12.1 rom.
With adb the installation of TWRP recovery or or cm12.1 recovery seems to work fine (transfer ok and no errors) but when I restart in recovery mode ((power + volume down) It's still OxygenOS Recovery in my phone.
Please help, I don't want to be stuck in this state :crying:
Click to expand...
Click to collapse
download the latest COS12.1.1 factory image to your pc, boot into fastboot mode and install the factory image via fastboot (flash aboot FIRST and do a "fastboot reboot bootloader" before you flash the rest ).
After that (or during, just replace recovery.img) you may install any custom recovery
Gesendet von meinem A0001 mit Tapatalk
Yes :good:
You brought me on the right track
I have successfully applied this method.
I nearly lost my phone because I had a power outage during the recovery but finally all is fine : I am back on COS 12.1.1 :victory:
A big thank-you
Revert from OxygenOS to Lineage - problem with recovery
Hi,
My phone OPO is currently running Oxygen Os
I am trying to switch to Lineage OS, however whenever the phone boots to the "Fast Boot" screen its just stuck at that.
Could someone please help me fix this?
[email protected] said:
Hi,
My phone OPO is currently running Oxygen Os
I am trying to switch to Lineage OS, however whenever the phone boots to the "Fast Boot" screen its just stuck at that.
Could someone please help me fix this?
Click to expand...
Click to collapse
Flash twrp with fastboot , then flash the lineage os :good:
Azhar_Fahry said:
Flash twrp with fastboot , then flash the lineage os :good:
Click to expand...
Click to collapse
Yes I am trying to flash TWRP
However, when I follow the below mentioned steps this is what i end up with :
List of devices attached
dc1c2a16 unauthorized
C:\Program Files (x86)\ClockworkMod\Universal Adb Driver>adb devices
List of devices attached
dc1c2a16 device
C:\Program Files (x86)\ClockworkMod\Universal Adb Driver>adb reboot bootloader
C:\Program Files (x86)\ClockworkMod\Universal Adb Driver>fastboot devices
C:\Program Files (x86)\ClockworkMod\Universal Adb Driver>fastboot oem unlock
< waiting for device >
And on the device screen it just reads "Fastboot mode"
So I kind of have the same problem but not exactly, I flashed the oxygen os and it worked perfectly but I wanted to change it to a nugget based rom and realized that I can not even boot into recovery. it gets stuck on the first oneplus logo that comes up and will not boot into the twrp. Any suggestions?
wait, so ur phone can't boot into the rom? or stuck at the fastboot mode everytime u try to turn on the phone ? I'm having that problem too, but I reinstall all the driver, and it worked.
Sent from my A0001 using Tapatalk
Azhar_Fahry said:
wait, so ur phone can't boot into the rom? or stuck at the fastboot mode everytime u try to turn on the phone ? I'm having that problem too, but I reinstall all the driver, and it worked.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
My device is just stuck at the Fast boot screen that shows a One Plus Logo under which "Fastboot Mode" is written after I try to boot into fast boot.
[email protected] said:
My device is just stuck at the Fast boot screen that shows a One Plus Logo under which "Fastboot Mode" is written after I try to boot into fast boot.
Click to expand...
Click to collapse
try to reinstall all the driver from this link ( https://goo.gl/MxKLjH ) and follow the instruction , i use that method and it worked
arashsh2002 said:
So I kind of have the same problem but not exactly, I flashed the oxygen os and it worked perfectly but I wanted to change it to a nugget based rom and realized that I can not even boot into recovery. it gets stuck on the first oneplus logo that comes up and will not boot into the twrp. Any suggestions?
Click to expand...
Click to collapse
Go to fastboot and flash latest twrp first. If you are rooted, you can do that also from running systen (flashify, twrp manager)
giaur said:
Go to fastboot and flash latest twrp first. If you are rooted, you can do that also from running systen (flashify, twrp manager)
Click to expand...
Click to collapse
Thank you for your response. I tried doing that but it gives me an error saying that there is already a twrp installed. I used Twrp Manager
giaur said:
Go to fastboot and flash latest twrp first. If you are rooted, you can do that also from running systen (flashify, twrp manager)
Click to expand...
Click to collapse
so I am still having the same issue, I got the latest twrp on there and still stuck, cant boot into recovery. everything I find online is about oneplus 2 and nothing about oneplus 1, can I use the same instructions for my oneplus1?
arashsh2002 said:
so I am still having the same issue, I got the latest twrp on there and still stuck, cant boot into recovery. everything I find online is about oneplus 2 and nothing about oneplus 1, can I use the same instructions for my oneplus1?
Click to expand...
Click to collapse
Yes, this is general procedure for any android phone. The only requirement is unlocked bootloader.
giaur said:
Yes, this is general procedure for any android phone. The only requirement is unlocked bootloader.
Click to expand...
Click to collapse
it is unlocked

stucked in fastboot mode

hello
i have got stucked in fastboot mode while installing custom rom.
please help me how to install os in my phone ( either cyanogen or miui).
Thanks in advance.
Regards,
jeevan.
Fastboot flash stock.
boyapatijeevan said:
hello
i have got stucked in fastboot mode while installing custom rom.
please help me how to install os in my phone ( either cyanogen or miui).
Thanks in advance.
Regards,
jeevan.
Click to expand...
Click to collapse
Hope this helps. Go to their website and download the fastboot ROM of your desired phone and desired locale. There you can also find the MiPhone Flasher exe file. Run that file on your PC, connect the device with a USB cable when in Fastboot Mode, the application will detect the device, then provide the Downloaded ROM path and hit Flash. within 2-3 mins you're good to go
I have same problem with my mi 4i
Falshing via miflash tool , adb and qfil still got stucked on fastboot mode
When i wipe using mirecovery got notice
Wipe data failed
Any more solution to solve this suck problem?

Unable to flash any custom recovery via adb on Realme Q???????

1. bootloader is unlocked and confirmed
2. im running on a Realme Q latest Stock Rom RMX1971_11_C.08
3 ADB and USB debuging are properly setup.
4. I have tried the following recoveries, none working.
-recovery-TWRP-3.3.2B-0227-REALME_Q-CN-wzsx150.img
-OrangeFox-HOMEMADE-RMX1971.img
-OrangeFox-R11.0_0-Stable-RMX1971.img
-twrp-RMX1971-20191121.img
ABD always confirm to push the recovery file succesfully but everytime I boot in recovery, I get the Realme UI recovery.
What I'm I doing wrong ?????
jungl1st said:
1. bootloader is unlocked and confirmed
2. im running on a Realme Q latest Stock Rom RMX1971_11_C.08
3 ADB and USB debuging are properly setup.
4. I have tried the following recoveries, none working.
-recovery-TWRP-3.3.2B-0227-REALME_Q-CN-wzsx150.img
-OrangeFox-HOMEMADE-RMX1971.img
-OrangeFox-R11.0_0-Stable-RMX1971.img
-twrp-RMX1971-20191121.img
ABD always confirm to push the recovery file succesfully but everytime I boot in recovery, I get the Realme UI recovery.
What I'm I doing wrong ?????
Click to expand...
Click to collapse
Ah yes. I've ran into similar issues last time I tried to revert from Pixel Experience Android 11 to stock RMQ firmware. I noticed if you start sending the recovery with fastboot flash recovery twrp.img, the fastboot cmd waits for device, you enter fastboot mode and then connect to the PC via usb 2.0 port the recovery will be successfully flashed BUT only that one file, whatever you want to flash next time for example vbmeta or system, vendor.img you'll have to repeat the cycle. Disconnect the usb cable, enter the flashing command to fastboot cmd on PC, boot back again to fastboot mode on your phone then connect the usb cable. This solved the issue for me.
greenys' said:
Ah yes. I've ran into similar issues last time I tried to revert from Pixel Experience Android 11 to stock RMQ firmware. I noticed if you start sending the recovery with fastboot flash recovery twrp.img, the fastboot cmd waits for device, you enter fastboot mode and then connect to the PC via usb 2.0 port the recovery will be successfully flashed BUT only that one file, whatever you want to flash next time for example vbmeta or system, vendor.img you'll have to repeat the cycle. Disconnect the usb cable, enter the flashing command to fastboot cmd on PC, boot back again to fastboot mode on your phone then connect the usb cable. This solved the issue for me.
Click to expand...
Click to collapse
Thank you very much for the tip ! I shall give it a try as soon as I'm back home , since I'm on holiday now and don't have the device !
jungl1st said:
Thank you very much for the tip ! I shall give it a try as soon as I'm back home , since I'm on holiday now and don't have the device !
Click to expand...
Click to collapse
It's worth a try for sure. Yesterday it took me more than 6 hours to set up a working RUI after Pixel Experience. One of these issues was that I couldn't flash custom recovery and vbmeta. I Always keep a modified vbmeta and twrp.img on my external SD card once I successfully managed to boot up into twrp after fastboot flash. Remember, keeping custom recovery installed should be your number one priority for you can pretty much solve anything with it.
greenys' said:
It's worth a try for sure. Yesterday it took me more than 6 hours to set up a working RUI after Pixel Experience. One of these issues was that I couldn't flash custom recovery and vbmeta. I Always keep a modified vbmeta and twrp.img on my external SD card once I successfully managed to boot up into twrp after fastboot flash. Remember, keeping custom recovery installed should be your number one priority for you can pretty much solve anything with it.
Click to expand...
Click to collapse
indeeed, custom recovery is the turning point to recover almost anything ! given the point that one manages to install it in the first place
greenys' said:
It's worth a try for sure. Yesterday it took me more than 6 hours to set up a working RUI after Pixel Experience. One of these issues was that I couldn't flash custom recovery and vbmeta. I Always keep a modified vbmeta and twrp.img on my external SD card once I successfully managed to boot up into twrp after fastboot flash. Remember, keeping custom recovery installed should be your number one priority for you can pretty much solve anything with it.
Click to expand...
Click to collapse
Hi, I actually managed to flash the recovery, how ever it seem not to properly overwrite the original recovery.
I mean, i can flash and boot in to TWRP, only once at a time, once I exit TWRP and reboot into recovery, I land into the Realme recovery again !!!!! dont know whats wrong

Can´t Install/Flash TWRP

Hello people,
i have a small problem here with my Oneplus 7 Pro.
I updated to the newest OOS11 via this tutorial.
[RECOVERY] [12] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
The actuall update went fine so far. I can boot into my 1+7pro, Magisk is still installed and it is still rooted?!
That shoud not be the case or am i wrong? Since i have to flash TWRP first?
But the actuall problem is that i cant install/flash the newest twrp-installer-3.6.0_11-0.
When i am in Windows 10 Pro
Version 10.0.19044 Build 19044 21H2 my 7Pro is showen in the ADB CMD window as a device. If i boot it into fastboot via adb reboot bootloader and look for it the list stays empty.
Windows recognises my phone if i reconnect the USB cable in fastboot mode.
What i did:
Installed Android USB Bootloader Driver
Tried several ADB tools
open CMD as admin
changed the setting from only data transfer to MIDI/PTP
Do i miss something or do someone know what the problem could be?
I did get it to work. I dont know what the actuall problem was. Because i could not just do fastboot boot twrp.img with the files in the ADB folder.
I had to Drag&Drop the img into the CMD window. Now it worked perfectly fine

Categories

Resources