-
While i was trying to install ubuntu touch on my OPO i bricked it. I had all adb drivers installed on my PC but still the tool couldn't read them and i guess it semi-installed the ROM on the phone? Anyways now my OPO is stucked on the powered by ubuntu supported by: ubports screen and it cannot reach fastboot or recovery mode at all. I can't see the qualcomm port on the device manager. Before the failed installation i had lineageos 16.0 and twrp recovery. Any thoughts on solving this problem?
Thanks for your time. -
@Luthenor
You're phone is probably not bricked.
Have a good look at this similar thread: https://forums.ubports.com/topic/4071/trouble-installing-on-oneplus-one
You'll probably found useful tips there. -
@Luthenor It should boot to recovery power and vol down. Try clearing the cache and factory reset in android actions. Then restart the installer.
-
@Lakotaubp I tried to boot to recovery mode by holding vol down and power button multiple times but didn't work so i don't really know how to clear cache and do factory reset.
-
@AppLee I checked the forum and i got some tips but the core problem is that i don't have access to anything. I can't enter to fastboot and recovery. Also my pc doesn't recognise any port so i can't actually update the qualcomm drivers.
-
-
@Luthenor What OS are you installing from.
-
I'm nearly finished for today but will check back tomorrow. I can only suggest perhaps removing and install adb/fastboot again and trying that. Use the snap version of the installer if you can, you can watch it working in the terminal, that might give you a pointer.
Then there is always a live usb stick with Ubuntu on it and if your on windows use 15 sec adb from xda developers. Good luck it will get solved. -
@Lakotaubp I was installing from LineageOS 16.0 .
-
@Luthenor No I meant what is on your pc/laptop
-
@Lakotaubp Win 10 Pro 64bit
-
I tried using adb commands to boot my device on bootloader mode and it showed me this message on cmd
C:\adb>adb reboot-bootloader
adb server is out of date. killing...- daemon started successfully *
error: device '(null)' not found
So my computer cannot read my device.
- daemon started successfully *
-
@Luthenor Use this ADB version https://forum.xda-developers.com/showthread.php?t=2588979 Remove the other and all other device drivers.
-
Also read this https://forums.ubports.com/topic/4026/solved-problem-upgrading-mx4-from-ota15-to-ubport/6?_=1586857583373 it's not your device but same issue.
-
@Lakotaubp I tried the ADB version from the xda forum and all i got by typing adb devices to see if my pc reads my OPO is that:
C:\adb>adb devices
List of devices attached- daemon not running. starting it now on port 5037 *
- daemon started successfully *
Whatever i do with adb commands and drivers or reading forums about same issues with the one i have i cannot find any solution to my problem. I also tried multiple combinations with power + vol up or down and still nothing. I don't know if there's a way to restore OPO to factory state. Anyway thank you very much for your time, and i'll keep trying to find a solution.
-
@Luthenor said in Oneplus One bricked.:
I don't know if there's a way to restore OPO to factory state.
Found this https://forum.xda-developers.com/oneplus-one/development/toolbox-oneplus-one-toolbox-t2808987 and this (more recent) https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711
But read carefully those topic before attempt doing anything.
Your phone state's criticall so let's not do something too fast, read before, and maybe ask on XDA before doing anything.Little question : what's happening in windows device manager when you connect your phone (powered) to PC?
@Lakotaubp
Shouldn't this topic be in "support" part?2015-2023 : Meizu MX4 ☠️⚰️✝️
2023-2024 : Nexus 5 ☠️⚰️✝️
2024-***** : FPOS Fairphone 5
🇲🇫🇬🇧 -
@Keneda Before i answer your question i am a new member here and i don't really know what i had to do first before i create my first post sorry for that i am nervous. So about device manager, when i am plugging in my OPO it shows nothing. I can't really see the qualcomm port and thats a big deal because i cannot update OPO drivers.
-
@Luthenor The more recent all in one tool is not detecting my device.
-
@Luthenor said in Oneplus One bricked.:
@Keneda Before i answer your question i am a new member here and i don't really know what i had to do first before i create my first post sorry for that i am nervous.
No problem here, just asking modo to move it to the right place :beaming_face_with_smiling_eyes:
So about device manager, when i am plugging in my OPO it shows nothing. I can't really see the qualcomm port and thats a big deal because i cannot update OPO drivers.
The more recent all in one tool is not detecting my device.
Ok, i'll let more skilled users help you.
-
@Keneda said in Oneplus One bricked.:
Shouldn't this topic be in "support" part?
You're right.
I moved the topic.
No problem @Luthenor and I hope you'll find a way to install UT.Most of the time the problem seems to come from ADB not being able to detect the phone at some point.
People solved this by using another PC host or maybe trying with Ubuntu on a live stick...
Best of luck
