Hi ! I have a big mistake when i update Oos 3.2.2 to 3.2.4 !?
I never can connect my Op3 to usb to my computer ?
I test to update drivers nothing
I test in dev option to change ptp to mtp etc nothing
I test to change to community build and now dirty flash Oos 3.2.6 but always no connect to computer
I test in mac os with Android file transfert nothing
I test in Windows never can update or recognized drivers error 29 microcode
I test with Qc qualcomm driver with turn off & press volume up nothing too ????
My last solution are I have a nandroid backup I haved make before mistake in Oos 3.2.2 but I don't know if that can resolve it !?
I have do a remote session with Oneplus but it can't connect too with qualcomm drivers.
Do you know what the problem ?
Thank you
Hi nobody for help me
I don't understand I had make a nandroid of oos 3.2.2 but I stock it in my mac and I do move with Ftp because are big folder and when I go to twrp restore I don't see my folder.
I do flash factory reset oos 3.2.2 for see but I can't see my nandroid backup ??? Rrrrr
I have a question I can do not a wipe but a format of my OP3 with Twrp and after Flash again Oos 3.2.2 and SuperSu ? Because if I make a format my Oos.zip do erase ?
Thank you
Solved I do to change it ! It was a hardware problem..
Related
I carelessly wiped the system in TWRP, now i have a big problem -"no OS ".Unfortunately,it can't mount USB driver by OTG and device can't be detected what ever in Recovery or bootloader mode . so I can't flash a new rom into it.What can I do now ?I have switched many PC with different OS ,windosw xp ,7 ,8 ,but none of them can recognize my device which make me can't install driver for it.What can I do now ?
lonelystar21 said:
I carelessly wiped the system in TWRP, now i have a big problem -"no OS ".Unfortunately,it can't mount USB driver by OTG and device can't be detected what ever in Recovery or bootloader mode . so I can't flash a new rom into it.What can I do now ?I have switched many PC with different OS ,windosw xp ,7 ,8 ,but none of them can recognize my device which make me can't install driver for it.What can I do now ?
Click to expand...
Click to collapse
Just flash the factory image and start from scratch.
http://forum.xda-developers.com/showthread.php?p=45671279#post45671279
You can also get drivers that will work with TWRP here:
http://forum.xda-developers.com/showthread.php?t=2391236
lonelystar21 said:
I carelessly wiped the system in TWRP, now i have a big problem -"no OS ".Unfortunately,it can't mount USB driver by OTG and device can't be detected what ever in Recovery or bootloader mode . so I can't flash a new rom into it.What can I do now ?I have switched many PC with different OS ,windosw xp ,7 ,8 ,but none of them can recognize my device which make me can't install driver for it.What can I do now ?
Click to expand...
Click to collapse
This is the driver you need in order to use ADB while in recovery in addition to the Google Driver or else you would see "Flo" under Unknown Devices in your computer device manager. Or you can restore the stock 4.3 ROM via fastboot.
the problem is it won't come out as "flo" or unknown devices when i connect to PC , it just nothing happen , that's the problem :crying::crying:
Hello!
I unlocked bootloader in my SXS yesterday and installed OpenSEMC Beta 3. Everything looks fine but I can't connect to pc with usb cable in file transfer mode. I don't see it in My Computer. I can only use fastboot mode. Tried on other OSes on other computers- same thing. PC Comanion doesn't see it as well. Tell me what to do. My backups of stock rom are in CWM location but now is TWRP installed on my device. Help!
I downloaded to phone OpenSemc beta-3 (earlier was 3.2) and installed. And problem with connection was gone I hope it will help someone.
hello guys sorry for my english,after installing a custom pie rom and go back to another oreo rom, i loose the posdibility to transfer data to my pc, transfer data is no longer showing, i try to wip cache and dalvik, hard resitting the phone, enabling usb debugging, install usb drivers, but still facing the issue
any help ?? thanks guys
also have an issue. factory reset and no go....
developer options dne help, or reinstalling all usb drivers on pc, or adb drivers.
You can use MTP from recovery
My device is Indonesian Android 10. I have twrp and root.
When I connect the device with the phone turned on normally, I cannot see the storage.
I see it at twrp and wifi ftp too.
The pc on the usb cable has no problem, tried it with another wire.
win x64 2004 20H1. but the problem is not caused by the pc. I made a full backup via twrp. as if this problem occurred after that.
please help
What is your pc processor? Have you updated your windows?
win x64 2004 20H1. but the problem is not caused by the pc. I made a full backup via twrp. as if this problem occurred after that.
Hello everybody
My main question is that if its possible to root the device without using an usb cable (typical flashing twrp's recovery with adb and then flashing the magisk zip in the recovery).
My phone cant be recognized by any pc, it gives me a descriptor error 43 on windows 10/8 in 3 differents pc's and changed many times the cable. Tried every thing on the internet about fixing the error 43 descriptor error. I need urgently the root because i have backup all my data with titanium backup before resetting the phone into factory due to some issues. After the reset i lost the root and the recovery mod so i cant use the titanium backup to restore all my data.
Any help will be appreciated.
Blackfox1010 said:
Hello everybody
My main question is that if its possible to root the device without using an usb cable (typical flashing twrp's recovery with adb and then flashing the magisk zip in the recovery).
My phone cant be recognized by any pc, it gives me a descriptor error 43 on windows 10/8 in 3 differents pc's and changed many times the cable. Tried every thing on the internet about fixing the error 43 descriptor error. I need urgently the root because i have backup all my data with titanium backup before resetting the phone into factory due to some issues. After the reset i lost the root and the recovery mod so i cant use the titanium backup to restore all my data.
Any help will be appreciated.
Click to expand...
Click to collapse
Use USB hub or win 7..
You can even find registry patch for win 10 on xda.
And use latest ADB/fastboot version.
Good luck and stay safe!
drnightshadow said:
Use USB hub or win 7..
You can even find registry patch for win 10 on xda.
And use latest ADB/fastboot version.
Good luck and stay safe!
Click to expand...
Click to collapse
Just tried an usb hub and it gives the same error. It must be something wrong about the phone. I ll tried later with win7, but i dont think it would be the problem since i even tried right now with linux mint and macOS and got a similiar error.
I always use the latest adb from here xda, any other tip to try with? If its possible to restore the backup file from titanium backup without root i dont really need the root tbh.
Blackfox1010 said:
Just tried an usb hub and it gives the same error. It must be something wrong about the phone. I ll tried later with win7, but i dont think it would be the problem since i even tried right now with linux mint and macOS and got a similiar error.
I always use the latest adb from here xda, any other tip to try with? If its possible to restore the backup file from titanium backup without root i dont really need the root tbh.
Click to expand...
Click to collapse
Titanium backup needs root or it will fail even froze the phone. Root is needed to flash.. you cab try flashify to flash twrp, but you can brick your device. I wouldn't try that.. try on win7 first, check drivers, version adb/fastboot , etc.
Check the official MIUI forum for drivers, adb, etc...
Good luck and stay safe!
drnightshadow said:
Use USB hub or win 7..
You can even find registry patch for win 10 on xda.
And use latest ADB/fastboot version.
Good luck and stay safe!
Click to expand...
Click to collapse
drnightshadow said:
Titanium backup needs root or it will fail even froze the phone. Root is needed to flash.. you can try flashify to flash twrp, but you can brick your device. I wouldn't try that.. try on win7 first, check drivers, version adb/fastboot , etc.
Check the official MIUI forum for drivers, adb, etc...
Good luck and stay safe!
Click to expand...
Click to collapse
Tried win7 already, got similar error, so, im almost sure that this descriptor error is something about the phone itself.
i guess i gonna buy a xiaomi mi 10 lite 5g for 200 bucks before this bf ends, root it and hope the data can be restored without too much issues.
Thanks for your time sir
Blackfox1010 said:
Tried win7 already, got similar error, so, im almost sure that this descriptor error is something about the phone itself.
i guess i gonna buy a xiaomi mi 10 lite 5g for 200 bucks before this bf ends, root it and hope the data can be restored without too much issues.
Thanks for your time sir
Click to expand...
Click to collapse
No problem, that's what XDA is here to help community.
Good luck and stay safe!
[/QUOTE]
Blackfox1010 said:
Hello everybody
My main question is that if its possible to root the device without using an usb cable (typical flashing twrp's recovery with adb and then flashing the magisk zip in the recovery).
My phone cant be recognized by any pc, it gives me a descriptor error 43 on windows 10/8 in 3 differents pc's and changed many times the cable. Tried every thing on the internet about fixing the error 43 descriptor error. I need urgently the root because i have backup all my data with titanium backup before resetting the phone into factory due to some issues. After the reset i lost the root and the recovery mod so i cant use the titanium backup to restore all my data.
Any help will be appreciated.
Click to expand...
Click to collapse
hallo there.. this is first time i comment on xda,sorry my bad english..
i have same problem with u,
can't connect to any pc afther installing update to miui 11
i try on win 7/10 on diferrent pc but can't connect to.
and then i try to open back case and release pcb port charging and reheat with air gun
250/2 for 10minute, and whoolaa its working again..
i don't know wheres the problem but it work on my phone
good luck and stay safe..