Hello everyone,
History : So i was using Rice driod on my OP 8T peacefully and i got an update on the rom. i installed the update via local update of the rom and after reboot the phone never booted back. i tried all button combos to make to boot anything like fastboot or recovery etc but nothing worked.
Problem : While connecting to PC the device shows as "Qualcomm HS Diagnostic 900E" I know it should show as 'qualcomm hs loader 900' something which indicates EDL state. So i can't perform MSM. There are not port showing in MSM either. Its blank. Even after forcefully trying to boot EDL ( button combos ), it always boots back to same state.
Fixes i have tried : Reinstalled qualcomm drivers many times, also tried many other versions of MSM including the Hydrogen OS one. No solution.
Can anyone please help me with this situation. Its been few days now and i have really no hope left with the device.
alp47470 said:
Hello everyone,
History : So i was using Rice driod on my OP 8T peacefully and i got an update on the rom. i installed the update via local update of the rom and after reboot the phone never booted back. i tried all button combos to make to boot anything like fastboot or recovery etc but nothing worked.
Problem : While connecting to PC the device shows as "Qualcomm HS Diagnostic 900E" I know it should show as 'qualcomm hs loader 900' something which indicates EDL state. So i can't perform MSM. There are not port showing in MSM either. Its blank. Even after forcefully trying to boot EDL ( button combos ), it always boots back to same state.
Fixes i have tried : Reinstalled qualcomm drivers many times, also tried many other versions of MSM including the Hydrogen OS one. No solution.
Can anyone please help me with this situation. Its been few days now and i have really no hope left with the device.
Click to expand...
Click to collapse
complete noob here but I have heard someone said they fixed using indian msm tool, maybe I am wrong, idk
LR7875 said:
complete noob here but I have heard someone said they fixed using indian msm tool, maybe I am wrong, idk
Click to expand...
Click to collapse
I have tried MSM already no fix as it doesn't detect the device in EDL state. Hence no port shows up
alp47470 said:
I have tried MSM already no fix as it doesn't detect the device in EDL state. Hence no port shows up
Click to expand...
Click to collapse
does the computer even detect your device? what name of the device does it show up
alp47470 said:
I have tried MSM already no fix as it doesn't detect the device in EDL state. Hence no port shows up
Click to expand...
Click to collapse
1st, make sure your device is connected and recognized as 9008 HS-USB QDLoader.
2nd, try using MSM of 9R Ported ROM for 8T, it works in almost every situation
LinhBT said:
1st, make sure your device is connected and recognized as 9008 HS-USB QDLoader.
2nd, try using MSM of 9R Ported ROM for 8T, it works in almost every situation
Click to expand...
Click to collapse
The 1st one is main problem. It doesn't recognise as 9008 HS-USB QDLoader, it always keeps showing to 900E mode.
just a long shot, as i am on a 5t not the 8, but has windoze perhaps updated and "fixed" the usb driver on your behalf?
my 5t was invisible after unlocking, until i forced windoze to update the driver to an unsigned (working) version
[EOL][11.0][OFFICIAL] LineageOS 18.1 for Oneplus 5 & 5T
Is there anybody out there!đź¤
forum.xda-developers.com
alp47470 said:
The 1st one is main problem. It doesn't recognise as 9008 HS-USB QDLoader, it always keeps showing to 900E mode.
Click to expand...
Click to collapse
That's a total different device state, it's on Diag mode, not EDL mode. Try to turn off the device COMPLETELY, then either using hardkeys ( VOL + VOL - press and hold at the same time, plug in cable ) or use Deep-Fash cable to put the device into correct EDL 9008 mode.
So, guys i was finally able to fix the device by EDL point method. Somehow the device was able to boot to edl anyhow. The drivers were correct and so was the cable etc, Thank you all for still helping me.
So relieved so my 8T alive again.
alp47470 said:
So, guys i was finally able to fix the device by EDL point method. Somehow the device was able to boot to edl anyhow. The drivers were correct and so was the cable etc, Thank you all for still helping me.
So relieved so my 8T alive again.
Click to expand...
Click to collapse
Could you please be more specific as to how you got it to connect in EDL mode - it would help others who end up in the same situation.
BillGoss said:
Could you please be more specific as to how you got it to connect in EDL mode - it would help others who end up in the same situation.
Click to expand...
Click to collapse
As you know already the phone wasn't able to go to EDL mode no matter what i did. I really don't know what caused the issue and why it wasn't booting even after using button combos (both vol) or to power off manually (vol up and power) it was went to Diagnostic Mode.
Here's what i did :
-Went to local shop for removing the back panel by those heating machines
-Unplug battery
-Then used the EDL points on the motherboard to force the device to boot EDL (this method is more seen in Mi , Redmi phones)
-The device immediately recognised by just one tap on "enum" now.
Thats how i flashed the OS, plugged the battery and panel, reboot
Thanks for sharing that - much appreciated.
alp47470 said:
As you know already the phone wasn't able to go to EDL mode no matter what i did. I really don't know what caused the issue and why it wasn't booting even after using button combos (both vol) or to power off manually (vol up and power) it was went to Diagnostic Mode.
Here's what i did :
-Went to local shop for removing the back panel by those heating machines
-Unplug battery
-Then used the EDL points on the motherboard to force the device to boot EDL (this method is more seen in Mi , Redmi phones)
-The device immediately recognised by just one tap on "enum" now.
Thats how i flashed the OS, plugged the battery and panel.
Click to expand...
Click to collapse
So the localshop is using Testpoint trick. It has the same effect as using Deep-Flash cable but more trustable, only that u will have to open the back cover.
Congrats on successfully rescue the device mate
LinhBT said:
So the localshop is using Testpoint trick. It has the same effect as using Deep-Flash cable but more trustable, only that u will have to open the back cover.
Congrats on successfully rescue the device mate
Click to expand...
Click to collapse
Thanks bro. Actually the shop kepper didn't do anything. Instead he was saying that the battery was damaged or something (probably scamming me) or he actually didn't had any idea for real. I had read about EDL point thing, so i just asked the shopkeeper to just remove the back panel. Rest i came home and did everything lol. NGL it was scary as hell.
In the process i also discovered that 8T and 9R being mostly identical also have same EDL points on motherboard. Same positioning too.
alp47470 said:
Thanks bro. Actually the shop kepper didn't do anything. Instead he was saying that the battery was damaged or something (probably scamming me) or he actually didn't had any idea for real. I had read about EDL point thing, so i just asked the shopkeeper to just remove the back panel. Rest i came home and did everything lol. NGL it was scary as hell.
In the process i also discovered that 8T and 9R being mostly idenical also have same EDL points on motherboard. Same positioning too.
Click to expand...
Click to collapse
Ah I see, same here when I 1st try the Testpoint trick few years back, scary as hell cuz that was the only phone I had at that time ))))
Btw, yes, 9R and 8T shares almost everything besides of SOC's name ( Snap870 in fact is Snap865 OCing ). That's why I told u to use the MSM Tool of 9R port ROM for 8T, it passes almost every errors u may face when using MSM of 8T itself!
alp47470 said:
As you know already the phone wasn't able to go to EDL mode no matter what i did. I really don't know what caused the issue and why it wasn't booting even after using button combos (both vol) or to power off manually (vol up and power) it was went to Diagnostic Mode.
Here's what i did :
-Went to local shop for removing the back panel by those heating machines
-Unplug battery
-Then used the EDL points on the motherboard to force the device to boot EDL (this method is more seen in Mi , Redmi phones)
-The device immediately recognised by just one tap on "enum" now.
Thats how i flashed the OS, plugged the battery and panel, reboot
Click to expand...
Click to collapse
Hi, I'm the same boat after a bad flash of OSS12, hard brick, black screen, not detected in Windows devices manager, no vibration with every button combination ...
Could you share where the edl points are on the OnePlus 8T motherboard please ?
I would be eternally grateful!
NZX-DeSiGN said:
Hi, I'm the same boat after a bad flash of OSS12, hard brick, black screen, not detected in Windows devices manager, no vibration with every button combination ...
Could you share where the edl points are on the OnePlus 8T motherboard please ?
I would be eternally grateful!
Click to expand...
Click to collapse
Here.. hope it helps
Related
Hey guys. I need some help. this is my wrong doing !!
I got a network unlocked T mobile which I started using with AT&T. Today I received the unlock code from T mobile to unlock bootloader which I did. then I I installed TWRP and Magisk without any issues. then I tried to fix the persis.img coz fingerpritn is not working. it didnt work so I left it alone. But I dont know why I wiped cache, data and then phone got stuck at boot loop. (no backup). I tried to install using MSM tool but it didnt work. MSM tool was not detecting the phone. then in TWRP I clicked on EDL and now the phone screen is blank. tried every possible combination of keys but no luck. was doing all this on windows 10. any help would be greatly appreciated. thanks
kool_am said:
Hey guys. I need some help. this is my wrong doing !!
I got a network unlocked T mobile which I started using with AT&T. Today I received the unlock code from T mobile to unlock bootloader which I did. then I I installed TWRP and Magisk without any issues. then I tried to fix the persis.img coz fingerpritn is not working. it didnt work so I left it alone. But I dont know why I wiped cache, data and then phone got stuck at boot loop. (no backup). I tried to install using MSM tool but it didnt work. MSM tool was not detecting the phone. then in TWRP I clicked on EDL and now the phone screen is blank. tried every possible combination of keys but no luck. was doing all this on windows 10. any help would be greatly appreciated. thanks
Click to expand...
Click to collapse
So it turns out its not a hard brick. I'm stuck on TWRP. I'm able to get to fastboot. I tried to install Oxygen OS thru fastboot but the PC is not detecting the phone in fastboot. Mac detects it but I believe all the stock Roms are for PC use. I did try it on my MAc and was able to open a terminal window inside the Oxygen OS folder but then the fastboot device command is not found. any help would be greatly appreciated. I installed SDK and ADB drivers on PC but in device manager the device still only shows as Android device with no drivers. !! thanks
kool_am said:
So it turns out its not a hard brick. I'm stuck on TWRP. I'm able to get to fastboot. I tried to install Oxygen OS thru fastboot but the PC is not detecting the phone in fastboot. Mac detects it but I believe all the stock Roms are for PC use. I did try it on my MAc and was able to open a terminal window inside the Oxygen OS folder but then the fastboot device command is not found. any help would be greatly appreciated. I installed SDK and ADB drivers on PC but in device manager the device still only shows as Android device with no drivers. !! thanks
Click to expand...
Click to collapse
Solved !
solved how? i greatly would like to know how to flash from fastboot, i know that isnt what this thread was about but im having the exact same problems you are with msm. i can see the phone in fastboot but i have no idea how to flash or what to flash from there. I can get into recovery but i cant copy anything over to the phone and the drivers dont show up for adb. so i pretty much ONLY have fastboot and dont know what to do! 2 days since the phone been down and im lost AF
JCroffut said:
solved how? i greatly would like to know how to flash from fastboot, i know that isnt what this thread was about but im having the exact same problems you are with msm. i can see the phone in fastboot but i have no idea how to flash or what to flash from there. I can get into recovery but i cant copy anything over to the phone and the drivers dont show up for adb. so i pretty much ONLY have fastboot and dont know what to do! 2 days since the phone been down and im lost AF
Click to expand...
Click to collapse
Can msm detect the phone when connected in fastboot. Also check device manager in pc to make sure it detects the phone as qualcomm device. Otherwise msm will not work.
Download msm. Turn phone off. Connect phone to pc. Open msm. Press start. Press volume down and power button on phone. It should be detected by msm and should start flashing the software.
Standby....
When plugged in the phone in EDL it shows
QUSB_BULK_CID0412 with an exclamation mark inside a yellow triangle
When i plugged in the phone and open fastboot it shows
Android with an exclamation point inside a yellow triangle
I booted up msm, clicked other, clicked start, pressed volume down and volume up and plugged it in. still says waiting for device to connect. ive also tried this with a number of keys being help, ive tried to boot from twrp straight into edl mode, none of which works
which all says to me its a driver issue of some kind, but for 3 days ive been slaving away on xda and cannot for the life of me figure out where to get the drivers.
JCroffut said:
Standby....
When plugged in the phone in EDL it shows
QUSB_BULK_CID0412 with an exclamation mark inside a yellow triangle
When i plugged in the phone and open fastboot it shows
Android with an exclamation point inside a yellow triangle
I booted up msm, clicked other, clicked start, pressed volume down and volume up and plugged it in. still says waiting for device to connect. ive also tried this with a number of keys being help, ive tried to boot from twrp straight into edl mode, none of which works
which all says to me its a driver issue of some kind, but for 3 days ive been slaving away on xda and cannot for the life of me figure out where to get the drivers.
Click to expand...
Click to collapse
It is a driver issue for sure. When connected device manager should detect as qualcomm hd9008.......
kool_am said:
It is a driver issue for sure. When connected device manager should detect as qualcomm hd9008.......
Click to expand...
Click to collapse
i figured that, i am at a complete loss as to where to find the drivers. i actually might need you to hold my hand on this one a tiny bit because im about to smash the phone on the ground and say someone stole it. thats where i am with this phone haha
JCroffut said:
i figured that, i am at a complete loss as to where to find the drivers. i actually might need you to hold my hand on this one a tiny bit because im about to smash the phone on the ground and say someone stole it. thats where i am with this phone haha
Click to expand...
Click to collapse
qualcomm hs-usb qdloader 9008 - this is the exact name of the driver.
Try this link: https://forum.xda-developers.com/t/guide-fixing-hard-bricks-qualcomm-hs-usb-qdloader-9008.3403868/
kool_am said:
qualcomm hs-usb qdloader 9008 - this is the exact name of the driver.
Try this link: https://forum.xda-developers.com/t/guide-fixing-hard-bricks-qualcomm-hs-usb-qdloader-9008.3403868/
Click to expand...
Click to collapse
standby ill read through it now. we also have 2 different threads going so i can combine them if thats easier for you
kool_am said:
qualcomm hs-usb qdloader 9008 - this is the exact name of the driver.
Try this link: https://forum.xda-developers.com/t/guide-fixing-hard-bricks-qualcomm-hs-usb-qdloader-9008.3403868/
Click to expand...
Click to collapse
Only download the qualcomm driver from this link. Or search for it online.
I have spent much more time than you trying to figure this out. I have a pc and Mac both. Mac is not compatible with a lot of the software and my pc usb ports are all bad. Point being, leave it alone for a day or so. Come back at it with a fresh start and fresh mind.
kool_am said:
Only download the qualcomm driver from this link. Or search for it online.
I have spent much more time than you trying to figure this out. I have a pc and Mac both. Mac is not compatible with a lot of the software and my pc usb ports are all bad. Point being, leave it alone for a day or so. Come back at it with a fresh start and fresh mind.
Click to expand...
Click to collapse
i hear that. after 3 days of non stop working at it im pretty sure im just not smarter than the phone today lol. looks like this phone is now stolen and going into a trash can lol
JCroffut said:
i hear that. after 3 days of non stop working at it im pretty sure im just not smarter than the phone today lol. looks like this phone is now stolen and going into a trash can lol
Click to expand...
Click to collapse
If I were you, I wouldn't throw the phone away. Like I said it's a simple issue of driver. Install the correct driver and make sure you see it as qualcomm device in device manager. Trust me, from then on, it's just a matter of a few clicks.
I unbricked my phone to t mobile and then converted to global rom without any issues.
kool_am said:
If I were you, I wouldn't throw the phone away. Like I said it's a simple issue of driver. Install the correct driver and make sure you see it as qualcomm device in device manager. Trust me, from then on, it's just a matter of a few clicks.
I unbricked my phone to t mobile and then converted to global rom without any issues.
Click to expand...
Click to collapse
i sent you a private convo on here if thats ok so i dont spam the forum! You may be able to help me out if i could borrow a few minutes of your time!
JCroffut said:
i hear that. after 3 days of non stop working at it im pretty sure im just not smarter than the phone today lol. looks like this phone is now stolen and going into a trash can lol
Click to expand...
Click to collapse
i was definatly kidding tho this is my only phone and i have to solve this problem lol
I'm not sure if you have read this thread already. I messed up my phone a couple days ago as well and follow the steps there and was able to MSM my phone back to stock.
[OP8][OOS TMO 55CB] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
I try all commands and procedure like volume+/- and power button all things but still screen is black and when i connect it to pc in manager it show me qualcomm 9008..
And when i flash it with msm tool oneplus 9 msm tool india it always show me error
Wrong suggestion, so I edited it out. Good luck unbricking
noname122414 said:
Wrong suggestion, so I edited it out. Good luck unbricking
Click to expand...
Click to collapse
How?
I saw in another post that you are aware of your chinese version. So you probably already tried flashing this version ( https://forum.xda-developers.com/t/official-oneplus-9-oxygen-to-color-and-back.4256457/ ) just patch the to Oxygen again on the chinese version.
How i can patch i told my phone is stuck in Edl mode hard brick
So no fastboot commands are working? Fastboot devices says nothing? Say what you tried, and your current situation in as much detail as possible. People can only help you when they understand what happened and what is still possible to do.
Brother my device is stuck in Edl mode because when i connect to pc it show me qualcomm 9008 in device manager..
I tried all Fastboot commands, power + , power - button & power button but nothing happened still device stuck in Edl mode and also msm tools of india doesn't work
Did you ever get a good flash from msm tool? If not try the original chinese version phone came with.
Also you can try holding power button until phone reboots but nothing to boot too will just go back to edl.
Y
nujackk said:
Did you ever get a good flash from msm tool? If not try the original chinese version phone came with.
Also you can try holding power button until phone reboots but nothing to boot too will just go back to edl.
Click to expand...
Click to collapse
Yes i use msm tools many time on another devices it works but on this case it doesn't work on oneplus 9
Wolverine619 said:
Y
Yes i use msm tools many time on another devices it works but on this case it doesn't work on oneplus 9
Click to expand...
Click to collapse
Sorry bud, if you can't get a good flash with msm you're stuck far as i know.
nujackk said:
Sorry bud, if you can't get a good flash with msm you're stuck far as i know.
Click to expand...
Click to collapse
Do you told me about solution?
My phone battery was 100% when it's stuck in Edl mode any idea for 100% to 0%?
Holding the power button an unreasonable long time always worked for me did it with 6 and 7pro. Even if it goes back to edl if you have msm ready and waiting for device v when it reboots to edl should pick it up and begin flash
nujackk said:
Holding the power button an unreasonable long time always worked for me did it with 6 and 7pro. Even if it goes back to edl if you have msm ready and waiting for device v when it reboots to edl should pick it up and begin flash
Click to expand...
Click to collapse
See brother
I see what you mean. Not sure what sahara error state is. Not sure you'll be able to fix that on your own. You may need to contact oneplus see if they can help. They tend to be willing to help in most cases. But may cost you since I'm sure this wouldn't be covered under warranty.
sahara error usually happens when you flash the wrong firmware.
noname122414 said:
sahara error usually happens when you flash the wrong firmware.
Click to expand...
Click to collapse
Can anyone tell me how to fix it?
Did you try everything what's written here? https://blog.hovatek.com/how-to-fix-sahara-fail-error-in-qfil/ when nothing there first with your problem then write here again.
noname122414 said:
Did you try everything what's written here? https://blog.hovatek.com/how-to-fix-sahara-fail-error-in-qfil/ when nothing there first with your problem then write here again.
Click to expand...
Click to collapse
I don't have file's for oneplus 9
Any one know how to extract .ops file of Msm tool
Wolverine619 said:
I don't have file's for oneplus 9
Any one know how to extract .ops file of Msm tool
Click to expand...
Click to collapse
"Payload dumper 64" can get the files for you that's an application there is also a python script which does the same.
I personally used "payload dumper 64" then flashed the files vis fastboot to recover 2 Chinese variant until now( you have to use the right rom which is normally used to switch from Chinese rom to Oxygen)
This is just how I recovered the phones.
Edit: sorry it's late you are probably looking for the msm download tool files, I probably messed things up
Greetings to all
After flash rom on fastboot and rebooting the device, the device entered the recovery, but the recovery is not working just black screen
I have pressed the power button and volume down button for a long time but nothing works
Currently the device is completely damaged!!!
I want to get into the bootloader in any way
Power up and connect to a Windows PC, what does the device manager display?
ULTRAJC said:
Power up and connect to a Windows PC, what does the device manager display?
Click to expand...
Click to collapse
I was trying to connect it to a Mac
It is now connected to a Windows device and the device recognizes it
""Qualcomm CDMA Technologies MSM QUSB_BULK_CID:0412_SN10E679A""
twuijri said:
I was trying to connect it to a Mac
It is now connected to a Windows device and the device recognizes it
""Qualcomm CDMA Technologies MSM QUSB_BULK_CID:0412_SN10E679A""
Click to expand...
Click to collapse
I'm not sure what your ROM installation process was, however at this point sounds like you need to use the MSM tool and recover your phone.
Unbrick tool to restore your device to OxygenOS <-- Use this thread.
Also from that thread:
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update.
Click to expand...
Click to collapse
Drivers are in that thread.
Screen will be blank / off during this process when you are in this mode (what you are seeing). At least that is what I believe you are describing / seeing.
OhioYJ said:
I'm not sure what your ROM installation process was, however at this point sounds like you need to use the MSM tool and recover your phone.
Unbrick tool to restore your device to OxygenOS <-- Use this thread.
Also from that thread:
Drivers are in that thread.
Screen will be blank / off during this process when you are in this mode (what you are seeing). At least that is what I believe you are describing / seeing.
Click to expand...
Click to collapse
Thank you, the device has come back to life after using ""MsmDownloadTool Global_KB05AA"" my phone ""oneplus 8T KB2000""
After the device worked, I ran into another problem ""QUALCOMM CrashDump Mode""
Is there a MsmDownloadTool for China devices oneplus 8T KB2000?
I'm so sorry for the problems I'm raising but I need help
Thank you for your time and help in solving other people's problems
twuijri said:
Thank you, the device has come back to life after using ""MsmDownloadTool Global_KB05AA"" my phone ""oneplus 8T KB2000""
After the device worked, I ran into another problem ""QUALCOMM CrashDump Mode""
Is there a MsmDownloadTool for China devices oneplus 8T KB2000?
I'm so sorry for the problems I'm raising but I need help
Thank you for your time and help in solving other people's problems
Click to expand...
Click to collapse
Some_Random_Username said:
Why is my device getting in Qualcomm crashdump mode in spite of a successful download?
Your unit was most likely manufactured after March 9th 2021, see https://forum.xda-developers.com/t/...ice-to-oxygenos.4180837/page-14#post-84789741 for reference. You therefore need to use HydrogenOS 11.0.7.12 MSM to recover your device linked at https://www.oneplusbbs.com/thread-5886794-1.html (mirrored at https://mega.nz/file/O8UySbgR#cXGlHkdA_7CYEhKIrek9zzAEwJ7Vx1D5BZdemnPlvGE by @pikatenor ). Getting new OxygenOS MSM tools is nowadays impossible unless you own the device it is meant for, so OP will not be updated to add new OxygenOS MSM tools allowing to workaround this issue. Feel however free to reach out to me in DM if you would like to get told how to maximise your chances to obtain one.
Click to expand...
Click to collapse
Thank you from the heart. I read the entire topic and tried all the methods. It took me 10 hours to work
I was so frustrated that I thought about buying a new device
Only 10 hours after knowing the solution of MsmDownloadTool There was a whole day after the device died
Thank you, thank you for everything you do to serve others
""All user from XDA ULTRAJC & OhioYJ""
The device has returned to work
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
Hello . I have OnePlus 7 pro I update it to android 12 and the next day something went wrong and my phone started an error Qualcomm crash dump something... Now it is stuck in EDL . Display none , power key And volume key works but keep booting in EDL even without connecting the USB cable . I flash the firmware with msm tool firmware flashed %100 but it didn't boot still in EDL .can someone guide me how to fix it
Can someone help!
jahanzaiblohani said:
Can someone help!
Click to expand...
Click to collapse
Hello,first thing i noticed is that msm tool finished with around 200 sec.i think that's not normal.I often use msm tool and every time finishes around over 300 sec.I see you have correct Qualcomm drivers.i'm not an expert but you must investigate a little bit more.good luck
darksx said:
Hello,first thing i noticed is that msm tool finished with around 200 sec.i think that's not normal.I often use msm tool and every time finishes around over 300 sec.I see you have correct Qualcomm drivers.i'm not an expert but you must investigate a little bit more.good luck
Click to expand...
Click to collapse
Drivers are correct and I was flashing it with USB 3.0 port .
I would try older stock ROMs first. O+7pro have plenty of them regarding EDL/MSM mode.
Another thing are checksums. Try to check if your download was successfull by counting them from your side and by comparing what you have with provided download. It should match 1:1.
KyRol said:
I would try older stock ROMs first. O+7pro have plenty of them regarding EDL/MSM mode.
Another thing are checksums. Try to check if your download was successfull by counting them from your side and by comparing what you have with provided download. It should match 1:1.
Click to expand...
Click to collapse
I have the old stock ROM which I flashed it in EDL but phone didn't boot when it is completed phone reboot too but not in normal mode in EDL again
Most often people have bad experience with qualcomm drivers. So make sure that you have some released after 2020 year, as oneplus 7 pro was released in 2020 year. Another issue is related to usb 3.x, better avoid that and try USB 2.0 instead, most of people have best results with older interface of that kind. EDL is kind of old solution, so better to stay away with USB 3.x and use USB 2.0.
Have you got any idea your flash is successful in edl tool? Have you got clean results or warnings/errors?
To be honest with you, I have to use EDL too, because I did wrong upgrade. I used custom ROM instead of stock ROM. Now I have not access to fastboot nor adb via USB either.
try different EDL ROMs, I found 2 threads. one is here, second there. As almost nobody anserws our questions, I will let you know what I did if I do it successfully.
Well, I discovered that I'm in pretty bad situation. In my case not only adb and fastboot does not works. It appears that EDL does not work either. Why? because I connected another oneplus phone over USB to PC and EDL mode was detected spot on. In case my o+7pro, well still same error as previously with adb/fastboot over USB. Something messed with USB on my phone at software side.
So I have to get motherboard get cheap. I do not thik that I can desolder flash or eMMC and revert that so easy.
Sorry Man, can not help you any
further. Turns out my issue is signifigantly other than yours.