I unbricked my OP8t following this guide and decided that just a working phone is not enough for me (yes i so... stubborn)
I flash rom via twrp and got errors: "can't find system_root partition" and "can't find vendor partition".
i flash new twrp via sideload and reboot phone(DON'T DO IT!)
Now my pc can't see phone, but phone can charging.
I don't think anyone can help me... but it's worth a try
Hi, follow this giude: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/
gcsuri said:
Hi, follow this giude: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/
Click to expand...
Click to collapse
Hi, i can't start Qualcomm EDL mode, device does not connect to pc
so it doesn't work for me
Hi,
disconnect and turn off the phone. Start the msm tool and begin the process. Then Push VOL+and VOL- while you connect the phone to the PC. The upload process must be started. (I needed to use USB2 interface to work)
best regards,
gcsuri said:
Hi,
disconnect and turn off the phone. Start the msm tool and begin the process. Then Push VOL+and VOL- while you connect the phone to the PC. The upload process must be started. (I needed to use USB2 interface to work)
best regards,
Click to expand...
Click to collapse
computer still does not see the phone, i tried usb 2.0 and 3.0
qwerty960 said:
computer still does not see the phone, i tried usb 2.0 and 3.0
Click to expand...
Click to collapse
can you boot linux and use edl package? It works for me. Be very carefull, do not touch the persist and persist_bkp partition. It breaks your mobile forever.
i
gcsuri said:
can you boot linux and use edl package? It works for me. Be very carefull, do not touch the persist and persist_bkp partition. It breaks your mobile forever.
Click to expand...
Click to collapse
Hi, ubuntu can't see my device too
i think it's die
When your is not recognize in edl mode maybe you don't have installed the Qualcomm driver
qwerty960 said:
Hi, ubuntu can't see my device too
i think it's die
Click to expand...
Click to collapse
try the following: turn off the phone. Type a command to a shell in linux: journalctl -f
Then connect to phone to the PC while you press vol+andvol- .
What's happening?
gcsuri said:
What's happening?
Click to expand...
Click to collapse
absolutely nothing
qwerty960 said:
absolutely nothing
Click to expand...
Click to collapse
Are you using the 1+ cable?
Have your mobile charged a bit?
gcsuri said:
Are you using the 1+ cable?
Have your mobile charged a bit?
Click to expand...
Click to collapse
I use cable from OP nord 2, usb 2.0 port
I dont know, but it was charging for about ten hours on original 65wt charge
I've found that at times getting MSM to work can be difficult. But I've always been able to, somehow, get it working.
There have also been occasions when I've had to reinstall the Qualcomm driver.
I don't have any specific suggestions for your, but I just wanted to share the notes I've made/collected regarding the tool (attached). They might give you some ideas of things to try.
Note: my PC is running Windows 11 and I'm using the original OP cable.
Related
today i accidently wiped my nexus 5 OS.Butnow i cant restore stockrom as adb and fastboot not showing.My pc not installing drivers and otg is not mounted in twrp .anyone help
Have you really wiped your bootloader / partition table? Please double check that.
Try plugging it into your pc. if you get the qhsusb 9008 dload mode, follow this thread: https://forum.xda-developers.com/go...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
if you don't, make sure you shut down your phone completely as described in the thread above
I hope this will help you.
Jo_Jo_2000 said:
Have you really wiped your bootloader / partition table? Please double check that.
Try plugging it into your pc. if you get the qhsusb 9008 dload mode, follow this thread: https://forum.xda-developers.com/go...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
if you don't, make sure you shut down your phone completely as described in the thread above
I hope this will help you.
Click to expand...
Click to collapse
but my problem is my pc aint detecting my device its shwing like unknown usb (device desciptor failed).I have tried NRT but fails in adb connectivity.help spmeone
jude_ferolous said:
but my problem is my pc aint detecting my device its shwing like unknown usb (device desciptor failed).I have tried NRT but fails in adb connectivity.help spmeone
Click to expand...
Click to collapse
have you tried holding the pwr button 20 seconds? if you didn't, try following the thread *litteraly*
Jo_Jo_2000 said:
have you tried holding the pwr button 20 seconds? if you didn't, try following the thread *litteraly*
Click to expand...
Click to collapse
I have tried but still tht google logo
jude_ferolous said:
I have tried but still tht google logo
Click to expand...
Click to collapse
Having that logo = having fastboot mode.
Try uninstalling all drivers or use a virtual machine or another pc (even a raspberry pi works)
Jo_Jo_2000 said:
Having that logo = having fastboot mode.
Try uninstalling all drivers or use a virtual machine or another pc (even a raspberry pi works)
Click to expand...
Click to collapse
Kk will try and thanks
Jo_Jo_2000 said:
Having that logo = having fastboot mode.
Try uninstalling all drivers or use a virtual machine or another pc (even a raspberry pi works)
Click to expand...
Click to collapse
jude_ferolous said:
Kk will try and thanks
Click to expand...
Click to collapse
I have also tried in windows 7 &windows 10 but no luck still showing unknown device (device descriptor failed).Whether my device hardbricked and can i go back to factory version without any luck in adb connectivity and no otg help someone...
Bricked my OPO somehow flashing cosmic OS. I get the load screen and thats it. no recovery and no fastboot. I've found a million tutorials on how to fix a hard brick, but all of them show the opo in device manager as qualcomm. I've downloaded some drivers but not sure what to do from here to get that to read qualcomm so i can start the unbrick process. any help or suggestions?
Jjleininger said:
Bricked my OPO somehow flashing cosmic OS. I get the load screen and thats it. no recovery and no fastboot. I've found a million tutorials on how to fix a hard brick, but all of them show the opo in device manager as qualcomm. I've downloaded some drivers but not sure what to do from here to get that to read qualcomm so i can start the unbrick process. any help or suggestions?
Click to expand...
Click to collapse
Forget all the other guides...
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Just use this one and the drivers included.
It will easily restore back to cm11s(stock KK),after that you can flash MM(Cos13.1x) if you want through fastboot.
The key-point is you need to find one of Xp systems around you and then use that because win8/10 somehow makes driver signature a headache and takes more time to set-up.
Mr.Ak said:
Forget all the other guides...
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Just use this one and the drivers included.
It will easily restore back to cm11s(stock KK),after that you can flash MM(Cos13.1x) if you want through fastboot.
The key-point is you need to find one of Xp systems around you and then use that because win8/10 somehow makes driver signature a headache and takes more time to set-up.
Click to expand...
Click to collapse
I'll check this out this evening. I'm playing hell trying to get drivers working. All the write ups I see show the opo saying qualusb in device manager upon connection and no matter what I do I can't get mine to. I've got an old laptop running win7 maybe I'll give that a shot. This would be done and over if it showed as qualusb in "ports" instead of adb interface in "usb".
Thanks for the info.
Jjleininger said:
I'll check this out this evening. I'm playing hell trying to get drivers working. All the write ups I see show the opo saying qualusb in device manager upon connection and no matter what I do I can't get mine to. I've got an old laptop running win7 maybe I'll give that a shot. This would be done and over if it showed as qualusb in "ports" instead of adb interface in "usb".
Thanks for the info.
Click to expand...
Click to collapse
Remove all other drivers.
Again,XP is advisable,I don't think it takes long to dual boot XP alongside.
Downgraded to Windows 7, now the phone shows up as Qualcomm, but still can't get the program to recognize. Bootable xp drive failed, will try disc when I get home.
Jjleininger said:
Downgraded to Windows 7, now the phone shows up as Qualcomm, but still can't get the program to recognize. Bootable xp drive failed, will try disc when I get home.
Click to expand...
Click to collapse
Sorry for late reply.It should be "Qhs_bulk" or "qualcomm_diagnostics9006" not just "Qualcomm".
Just try refreshing through Ebus button and make sure you're using original 1+ cable and try changing ports likewise.
I'd still say try with XP,use rufus to make a bootable usb and if you're good to go.After you setup the drivers(from thread link I gave you or from the zip itself), make sure you run the program as an administrator.
Mr.Ak said:
Sorry for late reply.It should be "Qhs_bulk" or "qualcomm_diagnostics9006" not just "Qualcomm".
Just try refreshing through Ebus button and make sure you're using original 1+ cable and try changing ports likewise.
I'd still say try with XP,use rufus to make a bootable usb and if you're good to go.After you setup the drivers(from thread link I gave you or from the zip itself), make sure you run the program as an administrator.
Click to expand...
Click to collapse
I've got it so it says qualcomm hs-usb qdloader 9008. I'll continue refreshing and swapping ports. I've used Rufus and four whatever reason it's giving me bsod when booting via USB. I'll give a disc a try.
Jjleininger said:
I've got it so it says qualcomm hs-usb qdloader 9008. I'll continue refreshing and swapping ports. I've used Rufus and four whatever reason it's giving me bsod when booting via USB. I'll give a disc a try.
Click to expand...
Click to collapse
Your motherboard supports usb booting?
Mr.Ak said:
Your motherboard supports usb booting?
Click to expand...
Click to collapse
Yessir, just went from windows 10 to 7 via USB boot.
Jjleininger said:
Yessir, just went from windows 10 to 7 via USB boot.
Click to expand...
Click to collapse
You can use other software than rufus for XP but that'll make the process too slow,atleast while installing XP.
But a CD always does the work perfectly for XP!
Mr.Ak said:
You can use other software than rufus for XP but that'll make the process too slow,atleast while installing XP.
But a CD always does the work perfectly for XP!
Click to expand...
Click to collapse
I tried a straight jump from win 10 to xp with a disc and the installation option was grayed out, maybe with 7 it'll give me that option back. I'll burn a new one this evening and give it a go.
Jjleininger said:
I tried a straight jump from win 10 to xp with a disc and the installation option was grayed out, maybe with 7 it'll give me that option back. I'll burn a new one this evening and give it a go.
Click to expand...
Click to collapse
Dual boot?
Situation:
Everything is formatted and wiped. There is no OS/ RedWolf is there now. I press any key, either Volume plus/ volume down with power key or anything, I can only go into fastboot mode. That's it.
Now, I installed Minmal ADB and Fastboot, drivers, and everything, so that I can flash RedWolf again.
The thing is:
My Xiomi Redmi Note 5 Pro is connected to HP Win 10 using USB cable. Minimal ADB and Fastboot command prompt is opened. I entered "fastboot devices" command. Nothing is showing. So I restarted the phone. So it detected again. I immediately enterd the same command again. Deviced is showing. "c6165464". I again entered the same command. Now. ???????? fastboot is showing. and third time onwords empty showing.
So it is getting disconnted automatically. What should I do?
I am facing same problem with my realme 5 pro device. Is their any solution of it . Why it is shown?????? Fastboot and next time I put command then it shows no. And then if I put sma command or any other it gets disconnected . What should I do now?
Maybe you got a faulty cable or a faulty USB. Either try with a different cable or a different computer.
Fytdyh said:
Maybe you got a faulty cable or a faulty USB. Either try with a different cable or a different computer.
Click to expand...
Click to collapse
I tried 4-5 cables but still it remains same
Have you tried removing the drivers, restart the computer and adding them again?
Fytdyh said:
Have you tried removing the drivers, restart the computer and adding them again?
Click to expand...
Click to collapse
I also tried this many times.
Also checked from all ports but nothing works
TRYX30 said:
I also tried this many times.
Also checked from all ports but nothing works
Click to expand...
Click to collapse
Have you tried flashing stock using miflash?
Fytdyh said:
Have you tried flashing stock using miflash?
Click to expand...
Click to collapse
But I think this tool is worked on mi devices not on reealme
TRYX30 said:
But I think this tool is worked on mi devices not on reealme
Click to expand...
Click to collapse
Yeah, my bad. The original poster had a redmi. Well with the official realme tool.
Fytdyh said:
Yeah, my bad. The original poster had a redmi. Well with the official realme tool.
Click to expand...
Click to collapse
I found out what was the problem and I fixed it and now it's working fine. There is some problem with amd ryzen processers. To fix that problem I downloaded amd ryzen usb controller fix then my pc detecting my phone. BTW thnx for ur time.
TRYX30 said:
I found out what was the problem and I fixed it and now it's working fine. There is some problem with amd ryzen processers. To fix that problem I downloaded amd ryzen usb controller fix then my pc detecting my phone. BTW thnx for ur time.
Click to expand...
Click to collapse
Could you post a detailed solution for anyone who will stumble across this thread?
if anyone has amd ryzen then you could also face this problem. then you should download the attach file. then just extract it and then you will see the extracted file and then run it as adminstrator and then restart you pc. You will see that problem is solved.
TRYX30 said:
if anyone has amd ryzen then you could also face this problem. then you should download the attach file. then just extract it and then you will see the extracted file and then run it as adminstrator and then restart you pc. You will see that problem is solved.
Click to expand...
Click to collapse
You are my god
TRYX30 said:
if anyone has amd ryzen then you could also face this problem. then you should download the attach file. then just extract it and then you will see the extracted file and then run it as adminstrator and then restart you pc. You will see that problem is solved.
Click to expand...
Click to collapse
Brother please help me.When I am entering into fastboot mode the device is getting disconnected. I even installed the usb controller fix but its not working. Plzz help . I am using ryzen 5 5600h processor
Vivek2580_maxxy said:
I had also tried many solutions when i faced this problem but only this one which i mentioned above works for me.
Click to expand...
Click to collapse
As I mentioned I my pc can't seem to detect my phone at all..it just goes into charging mode as soon as I connect..no adb no MTP or anything.
But my other phone connects just fine.
Things I've tried but failed,
Turning on adb debugging
Setting default usb configuration to MTP
Installing OnePlus drivers in pc
Adb and fastboot drivers along with qfil and miflash tool installed.
Pls guys help me figure this out.
I'm using latest oxygen os 11.1.1.1
Did you boot into other modes and tried to connect? recovery, fastboot etc.
croperas said:
Did you boot into other modes and tried to connect? recovery, fastboot etc.
Click to expand...
Click to collapse
Havnt tried this..I'll get back to u soon...my bootloader is locked btw
croperas said:
Did you boot into other modes and tried to connect? recovery, fastboot
Click to expand...
Click to collapse
croperas said:
Did you boot into other modes and tried to connect? recovery, fastboot etc.
Click to expand...
Click to collapse
I've tried bro but doesn't detect there either
i.Desygner said:
I've tried bro but doesn't detect there either
Click to expand...
Click to collapse
If it's stock then i'm thinking hw issue but keep trying things.
Try this:
Fastboot Not Recognized
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...
forum.xda-developers.com
And maybe another computer just in case.
Thanks bro..but somehow I managed to get it to work with another usb cable..even that wasn't recognised at first,had to try and install various drivers and update them manually.
Do u think my one plus cable is broken now
i.Desygner said:
Thanks bro..but somehow I managed to get it to work with another usb cable..even that wasn't recognised at first,had to try and install various drivers and update them manually.
Do u think my one plus cable is broken now
Click to expand...
Click to collapse
Could be but keep in mind it has several pins so even if the data is broken or iffy you could always use it as a charging cable.
Either way use it as backup since it's less reliable
So i recently wanted to root my OOS 12 oneplus nord, and i bricked it..
i cant get into fastbootD, Recovery, or anything at all except fastboot, the device is detected as Android bootloader interface in device manager, i have tried using: msm tool, flashing normal rom (error: partition not found and Flashing is not allowed for critical partition)
As a last resort, this worked for me : [OPNORD][OOS AC01AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Azeld said:
As a last resort, this worked for me : [OPNORD][OOS AC01AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Click to expand...
Click to collapse
As I said, msm didn’t work for me
Hafted said:
As I said, msm didn’t work for me
Click to expand...
Click to collapse
may be need to reinstall drivers? should be displayed differently in the device manager than Android bootloader interface.
gorro8 said:
may be need to reinstall drivers?
Click to expand...
Click to collapse
Nope, I can’t get it into edl mode, I did manage once but I got the you need to restart error and I couldn’t get it back there
Hafted said:
Nope, I can’t get it into edl mode, I did manage once but I got the you need to restart error and I couldn’t get it back there
Click to expand...
Click to collapse
what do you do to enter the edl mode?
what cable are you using?
gorro8 said:
what do you do to enter the edl mode?
what cable are you using?
Click to expand...
Click to collapse
Using official one plus cable, I hold bot volume keys for about 40 seconds, then connect the cable and only then I let my hands go off the keys
I found a problem similar to yours. they say it's the wrong driver
[Bricked] OP8 : FASTBOOT rom : 'Flashing is not allowed for Critical Partitions
I messed up trying to install TWRP on c.17 OOS12 Now the mobile is bricked. 1. I tried the MSM tool, it shows the COM PORT but doesnt do anything. Just stuck at waiting for device. 2. I tried the ALL IN ON TOOL, but getting "UNHANDLED...
forum.xda-developers.com
download the correct drivers and replace them in the device manager
gorro8 said:
I found a problem similar to yours. they say it's the wrong driver
[Bricked] OP8 : FASTBOOT rom : 'Flashing is not allowed for Critical Partitions
I messed up trying to install TWRP on c.17 OOS12 Now the mobile is bricked. 1. I tried the MSM tool, it shows the COM PORT but doesnt do anything. Just stuck at waiting for device. 2. I tried the ALL IN ON TOOL, but getting "UNHANDLED...
forum.xda-developers.com
Click to expand...
Click to collapse
Ok, I’ll try that and give you an update, Ty!
worth trying another USB port too, even if they are supposed to be the exact same. Same thing happened with my laptop, tried another (presumably identical) USB port and it works first time, every time
Hafted said:
Using official one plus cable, I hold bot volume keys for about 40 seconds, then connect the cable and only then I let my hands go off the keys
Click to expand...
Click to collapse
1st, u really should find the exact drivers. But also very important to remember booting your PC into Test Mode with Driver Signature Enforcement OFF - BEFORE installing the EDL 9008 Drivers for your device.
Besides, after you press and hold both Vol buttons, u should plug the device in IMMEDIATELY, not waiting for 40 seconds, since each time the device boots into EDL mode, if there's no connection is established in 5 seconds , the device will automatically out of EDL mode.
Hey, so after some time (I got a new phone by now) I managed to fix it, turns out that i had to instantly put in the cable, just like how LinhBT Said
LinhBT said:
waiting for 40 seconds, since each time the device boots into EDL mode, if there's no connection is established in 5 seconds , the device will automatically out of EDL mode.
Click to expand...
Click to collapse
Here is something that might work for unbricking and/or getting in to EDL-mode:
Unable to reinstall Oxygen OS from custom ROM. FAILED (remote: Flashing is not allowed for Critical Partitions ). Need assistance, details below.
Hello, friends. So I am here following this exact tutorial : https://www.thecustomdroid.com/oneplus-nord-oxygenos-restoration-guide/ I currently am stuck there @pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$...
forum.xda-developers.com