My Pixel after android 10 update dead. Won't turn on when pressing or long pressing or long pressing the power button for 5 minutes.
Key combination long pressing the volume down and power button leads to vibration feedback but the screen is black, can't even get to the bootloader.
Do you have an advanced guide to fix it? thanks
Congrats, it spontaneously combusted.
It happened back in Oreo -> Pie as well.
When you plug it in to a PC, you'll see that it shows up on Device Manager as a Qualcomm eDL 9008 device.
Solution? Get a complete image of the internal storage from a working Pixel XL -or- wait on someone to leak the Firehose/Sahara programmer files.
Sent from my Pixel XL using Tapatalk
WaseemAlkurdi said:
Congrats, it spontaneously combusted.
It happened back in Oreo -> Pie as well.
When you plug it in to a PC, you'll see that it shows up on Device Manager as a Qualcomm eDL 9008 device.
Solution? Get a complete image of the internal storage from a working Pixel XL -or- wait on someone to leak the Firehose/Sahara programmer files.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
pc does not see phone
trface said:
pc does not see phone
Click to expand...
Click to collapse
when plugged into the pc try holding the power and volume down for a while to see if it then recognizes it.
My XL is also having the same issue, but my pc does see a qualcom device. Can i retive the data from the phone? or reflash the update and keep the data and fix the phone? if so how do I do this?
Im new here.
WaseemAlkurdi said:
Congrats, it spontaneously combusted.
It happened back in Oreo -> Pie as well.
When you plug it in to a PC, you'll see that it shows up on Device Manager as a Qualcomm eDL 9008 device.
Solution? Get a complete image of the internal storage from a working Pixel XL -or- wait on someone to leak the Firehose/Sahara programmer files.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
My XL is also having the same issue, but my pc does see a qualcom device. Can i retive the data from the phone? or reflash the update and keep the data and fix the phone? if so how do I do this?
https://forum.xda-developers.com/pixel-xl/
Hello all, my google pixel1 32gb bricked after a SW update and it is going into EDL (emergency download mode) , can someone help me with .mbn file that I can flash with QPST tool?
Thanks
Related
Hi guys,
I have had my Nexus 5 rooted with franco kernel on it now for about 5 months. Yesterday I tried to autoflash to the new r57 of franco kernel and accidentally aborted it. My phone will now not boot or go into fastboot or recovery. The only way to get my computer to recognize it is by holding the volume up button and plugging in the usb cable. My computer recongnises it as "Qualcomm HS-USB QDLoader 9008 (COM8)". Did I kill my Nexus 5? Please help!.
P.S. please dont tell me how stupid I am, I know. :crying:
kevindj360 said:
Hi guys,
I have had my Nexus 5 rooted with franco kernel on it now for about 5 months. Yesterday I tried to autoflash to the new r57 of franco kernel and accidentally aborted it. My phone will now not boot or go into fastboot or recovery. The only way to get my computer to recognize it is by holding the volume up button and plugging in the usb cable. My computer recongnises it as "Qualcomm HS-USB QDLoader 9008 (COM8)". Did I kill my Nexus 5? Please help!.
P.S. please dont tell me how stupid I am, I know. :crying:
Click to expand...
Click to collapse
Have you tried for example these steps? http://trendblog.net/fix-soft-bricked-android-device-first-aid-guide/
Here are some good files it seems http://forum.xda-developers.com/goo...l-06-03-14-one-click-factory-restore-t2513937
Most often its possible to recover an android as long as you can access the Download mode.
linuxares said:
Have you tried for example these steps? http://trendblog.net/fix-soft-bricked-android-device-first-aid-guide/
Here are some good files it seems http://forum.xda-developers.com/goo...l-06-03-14-one-click-factory-restore-t2513937
Most often its possible to recover an android as long as you can access the Download mode.
Click to expand...
Click to collapse
I'm not able to access Download mode.
What about backuo bootloader? Vol up, down and power?
Sent from my Nexus 5 using Tapatalk
rootSU said:
What about backuo bootloader? Vol up, down and power?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
No, the only thing that does anything is just holding volume up while plugging it in to the computer. Screen stays black, but computer recognizes it as "Qualcomm HS-USB QDLoader 9008 (COM8)"
So to clarify, you cannot get into either the primary or secondary bootloader? You've tried both and literally nothing happens?
Sent from my Nexus 5 using Tapatalk
rootSU said:
So to clarify, you cannot get into either the primary or secondary bootloader? You've tried both and literally nothing happens?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
exactly
Well if you can't get lg flashtool to work, you're pretty screwed.
Sent from my Nexus 5 using Tapatalk
kevindj360 said:
exactly
Click to expand...
Click to collapse
Try the LG Flashtool. That's your only hope. If it doesn't fix your issue, RMA/repairing is the only option.
vin4yak said:
Try the LG Flashtool. That's your only hope. If it doesn't fix your issue, RMA/repairing is the only option.
Click to expand...
Click to collapse
Will google still accept my RMA. My phone is over 5 months old.
kevindj360 said:
Will google still accept my RMA. My phone is over 5 months old.
Click to expand...
Click to collapse
Try lg flashtool first. Click link in my signature and look in section 3 for the guide. It uses vol up + USB which may work for you
RMA is 1 or 2 years depending which country it is in however it is warranty for manufacturing defects not user destruction. If you RMA it and they identify (rightfully) that you caused this issue, they will charge you for a new phone.
You would be better sending it to LG who may offer to repair for cost. You won't have fried the memory, just corrupt the partition so I wouldn't expect it to be expensive.
But try flashtool first.
Sent from my Nexus 5 using Tapatalk
rootSU said:
Try lg flashtool first. Click link in my signature and look in section 3 for the guide. It uses vol up + USB which may work for you
RMA is 1 or 2 years depending which country it is in however it is warranty for manufacturing defects not user destruction. If you RMA it and they identify (rightfully) that you caused this issue, they will charge you for a new phone.
You would be better sending it to LG who may offer to repair for cost. You won't have fried the memory, just corrupt the partition so I wouldn't expect it to be expensive.
But try flashtool first.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I get to this screen here.
EDIT: Attached the photo
kevindj360 said:
I get to this screen here.
EDIT: Attached the photo
Click to expand...
Click to collapse
If you have qualcomm 9008 you cant do much just rma your device.
kevindj360 said:
I get to this screen here.
EDIT: Attached the photo
Click to expand...
Click to collapse
Tried the qpst tool?
https://drive.google.com/file/d/0B3E5yjXCeMBbUmVRdl9VSHhHVkE/preview
Newer version link
http://code.google.com/p/mydownloadsection/downloads/detail?name=QPST.2.7.374.rar&can=2&q=
doctor_droid said:
Tried the qpst tool?
https://drive.google.com/file/d/0B3E5yjXCeMBbUmVRdl9VSHhHVkE/preview
Newer version link
http://code.google.com/p/mydownloadsection/downloads/detail?name=QPST.2.7.374.rar&can=2&q=
Click to expand...
Click to collapse
He cant do anything with qpst tool without a nexus 5 specific flash programmer and a special nexus 5 bootloader.
It seems when you get "Qualcomm HS-USB QDLoader 9008" you have really bricked your phone (hardbrick). Someone with knowledge must program sometool to unbrick it. (example. for a HTC device http://forum.xda-developers.com/showthread.php?t=1627882)
I think it's best to send it to Google.
Hey guys how are you?
Well a friend gave me an OPO that is really bricked.
Seems like it went to 0% of battery. I charged it to 100% but it does not boot. It stays in loop with the "cyanogen" logo
I tried every solution in every "hard brick resolution" thread.
Instaled ColorOS drivers, Samsung drivers, etc etc etc. nothing works, why? Well..
When i plug the phone on my computer, its recognized has MTP device. The "update driver" option is disabled. Its never recognized as qhsusb_bulk our adb or anything.
It does not seems to enter in fastboot mode ether, has i press vol up + power and it goes to the cyanogen logo again.
Im trying to do this recovery with an windows 10 64bit computer.
I tried to install qualcomm drivers also, but not compatible with my OS.
Not really sure what to do next..
I had the same issue. Tried VOLUME+DOWN multiple times until it worked and showed up as "QHSUSB_BULK" and then used the OnePlusRestoreTool to unbrick the phone.
Manually selected these drivers for Windows 10 64bit through the Device Manager here:
Qualcomm HS-USB QDLoader 9008 2.1.0.5
x86: http://download.windowsupdate.com/ms...af53d237ff.cab
x64: http://download.windowsupdate.com/ms...ac311facc0.cab <-------- this one if you are on 64bit Windows 10
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Good luck.
hea9vy said:
I had the same issue. Tried VOLUME+DOWN multiple times until it worked and showed up as "QHSUSB_BULK" and then used the OnePlusRestoreTool to unbrick the phone.
Manually selected these drivers for Windows 10 64bit through the Device Manager here:
Qualcomm HS-USB QDLoader 9008 2.1.0.5
x86: http://download.windowsupdate.com/ms...af53d237ff.cab
x64: http://download.windowsupdate.com/ms...ac311facc0.cab <-------- this one if you are on 64bit Windows 10
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Good luck.
Click to expand...
Click to collapse
Thank you! But the download links aren't working
cheveux_ said:
Thank you! But the download links aren't working
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=58145465&postcount=48
You can find them in the post above. :fingers-crossed:
hea9vy said:
http://forum.xda-developers.com/showpost.php?p=58145465&postcount=48
You can find them in the post above. :fingers-crossed:
Click to expand...
Click to collapse
yeah i searched and downloaded the x64 version of qualcomm
But i tried 20 something times to power on the mobile phone with vol up and no luck. still appears in the device manager as MTP device
Steps im taking:
1- Connect the phone with USB cable. Its starts charging.
2-let the screen go off then power + vol up. I let go power button has soon as the phone vibrates.
3-goes to cyanogen log and appears on the device manager as mtp usb device
tried that for 20 times
cheveux_ said:
yeah i searched and downloaded the x64 version of qualcomm
But i tried 20 something times to power on the mobile phone with vol up and no luck. still appears in the device manager as MTP device
Steps im taking:
1- Connect the phone with USB cable. Its starts charging.
2-let the screen go off then power + vol up. I let go power button has soon as the phone vibrates.
3-goes to cyanogen log and appears on the device manager as mtp usb device
tried that for 20 times
Click to expand...
Click to collapse
Try it on a native USB port, so try different ports. Or if you have access to more than one pc/laptop try it on different ones.
I had the same issue a couple of months ago on my wife's oneplus. Spent an hour on my laptop and no go. Fired up the desktop and worked first time.
cheveux_ said:
yeah i searched and downloaded the x64 version of qualcomm
But i tried 20 something times to power on the mobile phone with vol up and no luck. still appears in the device manager as MTP device
Steps im taking:
1- Connect the phone with USB cable. Its starts charging.
2-let the screen go off then power + vol up. I let go power button has soon as the phone vibrates.
3-goes to cyanogen log and appears on the device manager as mtp usb device
tried that for 20 times
Click to expand...
Click to collapse
Read the answers that people give you " Tried VOLUME+DOWN " , did you try that ?
Cholerabob said:
Read the answers that people give you " Tried VOLUME+DOWN " , did you try that ?
Click to expand...
Click to collapse
Yes. i Tried both :/
1st thing if it shows the cyanogen logo its not hard brick as per my knowledge.
Yes as suggested try different ports.
hea9vy said:
I had the same issue. Tried VOLUME+DOWN multiple times until it worked and showed up as "QHSUSB_BULK" and then used the OnePlusRestoreTool to unbrick the phone.
Manually selected these drivers for Windows 10 64bit through the Device Manager here:
Qualcomm HS-USB QDLoader 9008 2.1.0.5
x86: http://download.windowsupdate.com/ms...af53d237ff.cab
x64: http://download.windowsupdate.com/ms...ac311facc0.cab <-------- this one if you are on 64bit Windows 10
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Good luck.
Click to expand...
Click to collapse
hi. my friend. will this work for a 100% bricked? the phone cannot even show anything on screen
Sent from my ONE A2003 using Xparent BlueTapatalk 2
https://m.youtube.com/watch?v=O2_x9SnJ1Ak
This guide helped me in getting my dead opo back....
sanjeev7 said:
https://m.youtube.com/watch?v=O2_x9SnJ1Ak
This guide helped me in getting my dead opo back....
Click to expand...
Click to collapse
not working for me.
my PC cannot detect my opo
Sent from my ONE A2003 using Xparent BlueTapatalk 2
Can you get to fastboot?
evertking said:
Can you get to fastboot?
Click to expand...
Click to collapse
no. 100%bricked. go see the YouTube link above my pervious post
Sent from my ONE A2003 using Xparent BlueTapatalk 2
thx. my opo is un bricked. but now back to the problem before I bricked it.
the phone baseband is unknown (no efs save)
and the opo keeps rebooting every few second. is there a way to fix it?
Sent from my ONE A2003 using Xparent BlueTapatalk 2
So still no luck.
I have no fastboot and no recovery.
Has i connect the cable, it starts to charge.
If i click vol up + power it goes to the cyanogen logo and stays there...forever..
The problem is it is always recognized has "mtp device". I'm using an windows xp installation now...
Send me a PM and I'll try to help you!
Jeffrey98 said:
Send me a PM and I'll try to help you!
Click to expand...
Click to collapse
I think i can't send you messages, so here it goes
Hey Jeffrey! Has you asked, here is the pm.
So, in advance, thanks for your help. font know if this can be solved but its nice having someone interested in helping.
So, what i have:
- An OPO that doesn't boot.
- When i press the power button, it shows the one plus logo, and then the cyanogen logo, staying there forever..
- When i press vol up + power, it does the exactly same thing, never entering fastboot
- When i press vol down + power, it does the same thing. never entering recovery
I've prepared an old notebook with windows xp to unbrick the opo. Its completly clean.
The phone is always recognized has mtp device. I've installed all drivers on the internet. ColorOS, samsung, qualcomm, etc etc, everything. nothing works has its never detected in msm8974 or anything.
what can i do?
Thanks in advance
This might help!
If nothing works email oneplus and request for a remote session i did that and they flashed the os, and ps. while doing that they will tell you to download some files and in that some will be password protected and after completing the process they will delete the file so that we cant use it. If possible, after installing drivers they will tell u to reboot the system and log in back but after rebooting just copy the file to another place and then log in back so they can continue the process. Those files may be helpful for a lot of people.I have attached screen shots. Never mind the first folder, the remaining zip files are to be downloaded and in that two are password protected.
Since Xiaomi and Micro$oft released a public ROM of Windows 10 Mobile for Mi4, the curiosity drives me to try it. But I felt so uncomfortable after successfully installed win10 on my mi4.
So I decided go back to Android roms. But sh*t happened - my mi4 got bricked during the flashing.
Phone won't boot with black screen and no boot options. Holding any buttons (including power button + volume down more than 2 minutes) won't work.
The pc can not recognize a USB device after it is plugged in (in both Windows XP and Windows 8.1).
Then I plug it into my Mac OS X with a VirtualBox of Windows 7 OS inside.
The USB devices shows a unknown device of id 05C6:F006.
I did a lot of googling of 05c6:f006 which seems to be 05c6:9008 and something Qualcomm related.
And the most important thing is to make my computer to recognize it.
So things I need to figure out:
Is my phone hardware damaged or software damaged (hard bricked or soft bricked)?
Do I need to disassemble it?
How can I make my pc to recognize it ?
Please add screenshot of your phone state. Maybe we can determine if its a hardware or software issue
darkmaster566 said:
Please add screenshot of your phone state. Maybe we can determine if its a hardware or software issue
Click to expand...
Click to collapse
My phone was recognized as a USB input device, VID_05C6&PID_F006, seems to be Qualcomm_QHSUSB 9008 related
I have exacly the same probleme here, do you have find any solution ?
If it's getting recognised, we can try flashing another recovery or directly boot into recovery from command prompt by using command fastboot boot recovery.img
Try this and let me know if it works
xiaomi mi4 lte not turn on
darkmaster566 said:
If it's getting recognised, we can try flashing another recovery or directly boot into recovery from command prompt by using command fastboot boot recovery.img
Try this and let me know if it works
Click to expand...
Click to collapse
Good evening. I have a problem with my Xiaomi 4 lte, after trying to return from 6 to android 4.4 android after this tutorial : ]Now the phone does not start, if you stick to connect to PC loaded or red LED flashes once and the computer sounds like something I plugged in but not afiseaja nimicc device. He is charged for 24 hours and not start and MIFLASH program is not found
Mi4w hard brick
darkmaster566 said:
Please add screenshot of your phone state. Maybe we can determine if its a hardware or software issue
Click to expand...
Click to collapse
Hey! I had bymistakely flashed wrong partition and tried flash in miii 6.3.3 ROM....
Now my device is bricked....Whenever i connect to charger the red light blinks....And when connected to pc....The red light comes.....But no drivers come on my pc...Means its to recognising.....Can you help me please????
Hello XDA Members,
I have recently bought a OnePlus 7 Pro (GM1915) T-Mobile, Oxygen OS 10.0.3.GM31CB
off of the Mercari app. The sim is locked. I was hoping I could get some assistance to
have it where it can work with my ATT carrier. Willing to dole out $$$ for help.
Is it carrier locked or blacklisted?
HanzoMain said:
Hello XDA Members,
I have recently bought a OnePlus 7 Pro (GM1915) T-Mobile, Oxygen OS 10.0.3.GM31CB
off of the Mercari app. The sim is locked. I was hoping I could get some assistance to
have it where it can work with my ATT carrier. Willing to dole out $$$ for help.
Click to expand...
Click to collapse
I bought a TMO version and converted it to global/international and it works fine on ATT. Just find the thread in Guides and follow the steps.
PhillyFlyer said:
I bought a TMO version and converted it to global/international and it works fine on ATT. Just find the thread in Guides and follow the steps.
Click to expand...
Click to collapse
I'll give this a shot:good:
PhillyFlyer said:
I bought a TMO version and converted it to global/international and it works fine on ATT. Just find the thread in Guides and follow the steps.
Click to expand...
Click to collapse
It's locked and I don't think it's possible without OEM UNLOCK plus TWRP and Root not sure but not found any thing about it
Just ented edl mode . Phone totally powered off , download this. Unzip , and run the msmdownload tool. If needed just download qualcomm drivers. Once ran the exe just press vol up and down at the same time during 4 or 5 seconds (before this keep the usb plugged in the computer but not the phone connector side). After the seconds just plug the cable onto the phone connector and wait unitl the program shows Connected or Ready. Once this is done just click Star and wait for the process to be done. After that just wait the phone boot and unlock bootloader if wished.
YazumiWuHung said:
Just ented edl mode . Phone totally powered off , download this. Unzip , and run the msmdownload tool. If needed just download qualcomm drivers. Once ran the exe just press vol up and down at the same time during 4 or 5 seconds (before this keep the usb plugged in the computer but not the phone connector side). After the seconds just plug the cable onto the phone connector and wait unitl the program shows Connected or Ready. Once this is done just click Star and wait for the process to be done. After that just wait the phone boot and unlock bootloader if wished.
Click to expand...
Click to collapse
What do you mean by "before this keep the usb plugged in the computer but not the phone connector side)"
YazumiWuHung said:
Just ented edl mode . Phone totally powered off , download.... Unzip , and run the msmdownload tool. If needed just download qualcomm drivers. Once ran the exe just press vol up and down at the same time during 4 or 5 seconds (before this keep the usb plugged in the computer but not the phone connector side). After the seconds just plug the cable onto the phone connector and wait unitl the program shows Connected or Ready. Once this is done just click Star and wait for the process to be done. After that just wait the phone boot and unlock bootloader if wished.
Click to expand...
Click to collapse
Looks like msmdownload tool hangs after click "Start".
I got a message "Param preload" in column "Status of Last Communication". Time is ticking but nothing happens.
What can provoke the issue? I use Windows 2008 Server. Can it cause the issue with msmdownload tool?
ok first pull up ur device manager and (ok there is a couple of different ways some ppl just like to argue. It is what it is.) Me personally this is how i do it ok. Just me it works everytime Hey its oneplus.
I reboot to the bootloader by powering off phone. thwn hold volume down and power button at the same time. When the oneplus logo appears you can let off. It mighttake you to the recovery screen or straight to the bootloader but that doesnt matter at all really if it takes you to recover the stock recovery go advance then bootloader yes and yes. Now your in the bootloader. You dont really have to be in the bootloader to do this for real. I chose to. then I plug my phone in and I leave the phone powered on ok now you wanna have your device manager ready and up cause some these phones you have like 10 secs. your going to hold the volume up and down and power button all 3 down together make sure your hands are comfortable cause sometimes it takes awhile. but if dide right your screen should be black. Now on your device manager you are goona expand the port section make sure that driver says quacomm hs-usb Qdloader 9008 ok now once it says that and u installed the right one I cant really tell you which one to use. really cause i went through alot the one i ended up with is the microsoft catalog (google oneplus 7 pro qualcomm hs-usb qdloader 9008 and take from there. and make sure u installed the lt drivers that came with the msm tool. install all certificates all that stuff. If done right. It will not freeze up It will have a green bar and it will be doing its thing for like 2-3 mins.
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