Related
my oneplus one is hard bricked. i tried several tools to recover my OPO, sadly nothing worked. The problem i've figured out is, that after flasing the 8974_msimage.mbn image my phone disconnects (sound from windows), reconnects again and the msm8974 download tool starts again. so i'm stuck like in this video:
The Qualcomm Flash image loader doesn't give me an error message (i can flash everything - i did so with Color.zip and with OPO Recovery Tools files), but still i get no vibration, no led light or anything else from the phone.
so what can i do for now? that's actually not my first android phone which is hard bricked (i helped a lot of friends of mine and i'm computer scientist as well....), so can anyone, please, help me!!!!
regards
markus
Hi Guys,
Im new to the forums so i hope this is the right place for this post
I have a hardbricked oneplus one 64GB.
I have read and followed mutiple guides here and on youtube on how ot unbrick it.
But in every guide i followed mine "failed" at the same step.
When i start the "oneplus one recovery tool" or Msm8974DownloadTool this happens; (cant seem to use a link so ill try to explain it).
It starts with one green bar, when that is finished it stops an i hear the disconnected device sound.
I am currently on Win 10 but i also tried it on WinXP since mutiple posts suggested hat it would work better, but that also didnt help.
I also tried diffrent drivers (oneplus driver from the color zip), google multi driver, qualcomm driver etc.
Hope someone can help
Tiic said:
Hi Guys,
Im new to the forums so i hope this is the right place for this post
I have a hardbricked oneplus one 64GB.
I have read and followed mutiple guides here and on youtube on how ot unbrick it.
But in every guide i followed mine "failed" at the same step.
When i start the "oneplus one recovery tool" or Msm8974DownloadTool this happens; (cant seem to use a link so ill try to explain it).
It starts with one green bar, when that is finished it stops an i hear the disconnected device sound.
I am currently on Win 10 but i also tried it on WinXP since mutiple posts suggested hat it would work better, but that also didnt help.
I also tried diffrent drivers (oneplus driver from the color zip), google multi driver, qualcomm driver etc.
Hope someone can help
Click to expand...
Click to collapse
How your device got bricked?
Which recovery tool you tried?
Mr.Ak said:
How your device got bricked?
Which recovery tool you tried?
Click to expand...
Click to collapse
I don't have all the info since i got the phone from a "friend" who was about to throw it out, but ill do my best to provide accurate info
According to the privious owner the flashing of a custom rom or recovery went wrong and it ended up in it's current state.
The recovery tools i tried are;
- Oneplus one recovery tool by; Zyxxeil
- Oneplus one toolkit 1.5 by Manudroid19
- Msm8974DownloadTool
Tiic said:
I don't have all the info since i got the phone from a "friend" who was about to throw it out, but ill do my best to provide accurate info
According to the privious owner the flashing of a custom rom or recovery went wrong and it ended up in it's current state.
The recovery tools i tried are;
- Oneplus one recovery tool by; Zyxxeil
- Oneplus one toolkit 1.5 by Manudroid19
- Msm8974DownloadTool
Click to expand...
Click to collapse
Use the one with cm11s by Zyxxeil.Use Xp and use Qualcomm drivers,as this tool doesn't use fast boot/adb drivers and instead uses USB debugging port.
It need a few tries before device getting detected.
Make sure the device is getting recognized as "Qhs_bulk" or "Qualcomm diagnostics 9006" or some thing like that then install drivers manually.Also try different ports and refresh the toolkit. Open the toolkit with administrator rights.
Hope this helps
Mr.Ak said:
Use the one with cm11s by Zyxxeil.Use Xp and use Qualcomm drivers,as this tool doesn't use fast boot/adb drivers and instead uses USB debugging port.
It need a few tries before device getting detected.
Make sure the device is getting recognized as "Qhs_bulk" or "Qualcomm diagnostics 9006" or some thing like that then install drivers manually.Also try different ports and refresh the toolkit. Open the toolkit with administrator rights.
Hope this helps
Click to expand...
Click to collapse
I'm on windows xp now.
Made a clean install to be sure.
Phone is connected as Qualcomm HS-USB QDLoader 9008
The Zyxxeil tool recognizes it as a com port.
When i press start, it starts flashing 8974_msimage.mbn
When it finishes it just does the same. It looks like it's stuck on a loop at flashing 8974_msimage.mbn
I would post some pictures but i can't since im a new user
Edit; It is the same as this guy; youtube (dot) com/watch?v=TOw3-yX57jM
Flashing 8974_msimage.mbn nin a loop.... you're not the only one with this problem. I couldn't find a solution to this problem so far. Have tried fresh installs of Windows XP and Windows 7 and drivers installed in Test Mode without success. Please report back once you could figure out what's wrong.
Tiic said:
I'm on windows xp now.
Made a clean install to be sure.
Phone is connected as Qualcomm HS-USB QDLoader 9008
The Zyxxeil tool recognizes it as a com port.
When i press start, it starts flashing 8974_msimage.mbn
When it finishes it just does the same. It looks like it's stuck on a loop at flashing 8974_msimage.mbn
I would post some pictures but i can't since im a new user
Edit; It is the same as this guy; youtube (dot) com/watch?v=TOw3-yX57jM
Click to expand...
Click to collapse
Got it,it's because of a bad download or corrupt zip perhaps.Redownload the toolkit and also try with Color Os toolkit too.
If your device is recognized then there's no way you can't bring it back to life.
Mr.Ak said:
Got it,it's because of a bad download or corrupt zip perhaps.Redownload the toolkit and also try with Color Os toolkit too.
If your device is recognized then there's no way you can't bring it back to life.
Click to expand...
Click to collapse
Just redownloaded the tools and tried again.
Still the same issue, i also tried the color os toolkit like you suggested.
I have the same issue too, keep installing 8974_msimage.mbn again and again.
I'm still open for sugestions since the issue is still there
Right click msm tool, and RUN AS ADMINISTRATOR.
Problem solved.
kthejoker20 said:
Right click msm tool, and RUN AS ADMINISTRATOR.
Problem solved.
Click to expand...
Click to collapse
Although it is correct that you must run it as admin, this isn't the issue at all. There are phones that appear to be broken beyond the point where you can fix it with software.
MrBrainstorm said:
Although it is correct that you must run it as admin, this isn't the issue at all..
Click to expand...
Click to collapse
Yep, i always run tools like this as admin, the issue is something else in this case, but i wouldn't know what exactly
I may have found a solution/work-around to the problem described (in case anyone's still trying to unbrick a OPO after all this time). I must warn, however, that I really have no idea what I'm doing as I'm new to all of this, and have blundered through with no real understanding of what's going on, so pay heed at your own risk. It uses Qualcomm's QFIL program and Zyxxeil's OPO unbricking tool. I want give detail in describing the steps involved, so this will be fairly long.
***background***
My 64GB OPO has for the past couple of months almost always failed to get past the first 6-7 seconds of booting, and powered off before reaching the Cyanogen animation. It did the same when booting into fastboot and recovery, and at some point it stopped being able to access recovery at all. Very rarely it would boot, but pressing the power button while it was on would cause it to crash a few seconds later. I discovered that it would consistently boot properly if volume up were tapped while holding down the power button before it vibrates and the OnePlus logo appears, but this fix simply stopped working recently, and so it became impossible to turn the OPO on. Before giving up on it, I decided it would be worth trying the hard unbricking tool based on the ColorOS installer by Zyxxeil. However, I had the problem where the tool continually repeats the step of flashing 8974_msimage.mbn without progressing any further, to which nobody ever seemed to find a solution. I may have found a way to get around the problem, however.
Even though the procedure seems to have worked, the phone still shuts down after a few seconds as it did before (so I suspect my device has a hardware problem, possibly with the power button, and there's nothing that can be done for it). This means that I can't confirm that the fix actually works, but only that it appears to have worked. What it did was:
1) unbricked the phone - it probably wasn't even bricked before, but it definitely was after the installer hung on 8974_msimage.mbn ; it wouldn't respond to the power button at all afterwards. Applying the workaround allowed it to show signs of life again.
2) installed the COS11 fastboot. I'm not sure and can't tell whether the rest of the OS is there or intact, but the fastboot logo has changed from the newer small one to the bigger one from older versions.
***the problem***
The standard method for dealing with a hard-bricked OPO is to use the ColorOS tool as described in the "[GUIDE] [UNBRICK] Unbrick Oneplus One" thread and then flash Cyanogen, or to use Zyxxeil's tool which goes straight there. A common issue in both is that after pressing start, the tools repeat the step of flashing 8974_msimage.mbn , seemingly disconnecting the phone each time, and never progressing beyond that. This happened to me as well. This will happen if the tool is not run as an administrator, but for some people the same problem is seen even if it's run as an administrator. To the best of my knowledge, nobody has posted a solution to this problem, but some have suggested using alternative methods such as using QFIL (which I have gotten to work) or MiFlash.
***potential solution***
From what I understand, QFIL does the same thing as the unbricking tool, only not automatically. I directed it to use the files provided by Zyxxeil's tool, and it was then able to do something that unbricked the device as described above. This is what I did: (all on Windows 10, *not* using the original cable)
Required files:
1) Obtain the Qualcomm QDLoader driver. I used the the Qualcomm HS-USB QDLoader 9008 2.1.0.5 x64 driver from Zyxxeil's tool's thread (page 5, #48).
2) Download Zyxxeil's tool. I used the 64GB version. Extract DRIVER.iso and run setup.exe as described. I'm not sure whether this actually did anything and presume manually installing the driver in 1) overrides this, but I'm including this for completeness.
3) Download QFIL version 1.0.0.2 . I originally used 2.0.0.5 , but this did not work (it produced the error "unable to read packet header. only read 0 bytes", to which the recommended solution was to use an older version). This can be run from the extracted folder. Open it once, and then close it again - it seems not to behave properly the first time it is run.
Preparation:
4) Create a new folder, for instance on the desktop, and give it a short name. Copy and paste (or just move) the contents of the "OnePlusRestoreTool" folder from Zyxxeil's tool into here. This step is because QFIL supposedly doesn't like long folder names or locations (I'm not sure whether this is true or not but there's no harm in making sure).
5) Install the QDloader driver: (the PC may need to be disconnected from the internet for this stage, I think Windows may try to automatically download and install incorrect drivers)
>Open device manager, then plug the OPO into the computer. It should come up after a few seconds under "Ports (COM & LPT)" as something like QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008. Mine originally showed up as "Quectel QDLoader 9008". If it comes up as a malfunctioned device ("Unknown USB Device") under "Universal Serial Bus controllers", try holding the power button on the OPO down for a few seconds, or holding it down for a few seconds at the same time as volume up. If it's still not recognised, try rebooting the PC and repeating this step.
>Right click on the device as it appears in device manager, select "Uninstall device", tick the box saying "Delete the driver software for this device", and click on "Uninstall".
>The OPO will disappear from device manager. Unplug and then replug it into the PC, and after a few seconds it should be recognised again, perhaps as "Unknown USB Device" again, requiring the same procedure as above. It should now show up as QHSUSB_BULK under "Ports (COM & LPT)"
>Right click on the device and select "Update driver", then "Browse my computer for driver software". Paste in the file path for the folder containing the driver as downloaded above, which will be called "20561190_ed08f7139a2028da454a6668162f44ac311facc0" if using the driver specified above. Ensure "Include subfolders" is ticked, and click on Next. This should install the driver, and because it's signed, it shouldn't present problems often encountered in this stage. Your device should now be called "Qualcomm HS-USB QDLoader 9008", with (COM#) after it.
Fix:
6) Restart the PC, leaving the phone plugged in. Open device manager again. At this point, if it is detected as a malfunctioned "Unknown USB Device", do not try to remedy it as described above - leave it as it is. This is exactly what happened in my case.
7) Run QFIL.exe as an administrator. I don't know whether this is actually necessary to run as an administrator, but seeing as problems arise in the normal methods from not doing so, it seems sensible. If the device is listed as "Unknown USB Device", then QFIL should say "No Port Available".
8) In QFIL, click on "Browse" in the "select programmer" section. Navigate to the folder where the contents of Zyxxeil's tool were copied/moved to, and open "prog_emmc_firehose_8979.mbn". Lower down, click on "Load XML", which should give you three files to choose from. As I couldn't fully boot my OPO afterwards I don't know which one is most appropriate, but I have tried the procedure with each and it worked for all of them. Perhaps start with rawprogram_unsparse.xml and if that doesn't work try the other two. Click Open, then select patch0.xml , then click Open again.
9) Paying attention to the QFIL window, hold down power+volume up until the text changes from "No Port Available" to "Qualcomm HS-USB QDLoader 9008 (COM#). Incidentally, this will also cause the device to change from "Unrecognised USB Device" to "Qualcomm HS-USB QDLoader 9008 (COM#)" in device manager. I believe that this step starts "Qualcomm's debugging mode" as explained in Zyxxeil's thread, and this is necessary for the process to work.
10) Click on "Download" (below "Load XML"). QFIL should do its thing, and if nothing has gone wrong the phone might be unbricked at the end of the process. Disconnect from the PC and see if it works.
In my experience, where this step did not work it gave one of two errors:
"unable to read packet header. only read 0 bytes" - this happens on the newer version of QFIL, which is why I used the older one.
"unable to download flash programmer using sahara protocol" - this was the troublesome one. I believe it means that the phone is not in Qualcomm's debugging mode. This would probably be the case if, for whatever reason, the PC recognised the phone immediately as Qualcomm HS-USB QDLoader 9008, and so it wasn't necessary to hold power+volume up for the PC to recognise it properly. In my case the program ran properly the first time but was interrupted because I hadn't transferred all of the right files to the target folder. After I had done this and tried again, it gave this error. I fixed this by holding down power+volume up, while the device was recognised, until the PC made a sound indicating something had been plugged in. The next attempt to download was successful.
If the procedure doesn't work properly, it might also be worth using one of the other two XML files mentioned in step 9.
*** ***
Anyway, after hours of searching and trial and error, this unbricked the phone, with it becoming responsive once more to button presses, despite still having the original problem of powering down during boot. It seems to have the CM11 fastboot as expected, and I was able to have my PC recognise it in the short time it stays on using fastboot devices. Other than that, I'm afraid I don't know how successful this was, or how successful it would be for other people. I hope this is useful nonetheless!
hi follow this guide https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
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
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
Hi everybody,
I've Oneplus 8t kb2003 updated to the last ota firmware 13.1.
I tried to downgrade it to 13 by flashing full OTA payload.bin using fastboot enhance app but unfortunately the device is bricked.
Usually when such thing happen I boot the EDL mode and use msm tool to unbrick it which worked for me couple years before but for some reason the device is not detected at all on EDL mode!
The device manager not showing any thing called qualcomm even the msm tool not detecting any thing.
I tried to redownload the qualcomm driver and followed all instructions in this link , used 3rd party cables and the original cable and changed ports but nothing happens
It's like the phone is completely dead
any ideas how to get out of this mess ?
Reo0o said:
Hi everybody,
I've Oneplus 8t kb2003 updated to the last ota firmware 13.1.
I tried to downgrade it to 13 by flashing full OTA payload.bin using fastboot enhance app but unfortunately the device is bricked.
Usually when such thing happen I boot the EDL mode and use msm tool to unbrick it which worked for me couple years before but for some reason the device is not detected at all on EDL mode!
The device manager not showing any thing called qualcomm even the msm tool not detecting any thing.
I tried to redownload the qualcomm driver and followed all instructions in this link , used 3rd party cables and the original cable and changed ports but nothing happens
It's like the phone is completely dead
any ideas how to get out of this mess ?
Click to expand...
Click to collapse
Install all the necessary drivers and use MSM tool to restore your phone.
[OP8T][OOS KB05AA/BA/DA] 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
P.S: Don't use fastboot enhance app, as it wasn't updated for quite some time and was reason of bricking several phones after flashing.
If you used Fastboot Enhance it could have flashed the wrong xbl file for your RAM type. If is it so, the only thing you can try is a deep flash cable or shorting the test pins on the motherboard.