(Solved) Oneplus 8T Qualcomm logo blinking - OnePlus 8T Questions & Answers

Hi!
I have tried to install a custom rom, but there was an error. When I tried to boot back to bootloader mode, the qualcomm logo started blinking and the device is vibrating.
Tried to connect to pc, but I don't see any device in COM Ports in the device manager, also MSM tools says waiting for the device.
If I connect the cable while I am pressing the both volume button, I hear the sound from the pc that something is connected, but after a few seconds the device disconnects.
Can you help me?

Got the same problem installing a wrong firmware, probably. I'm hoping for someone knowing how to solve...

That was easy. Unfortunately I had to format the phone entirely (MSMTool), but it's back with the living.
Install Qualcomm EDL drivers
Download an MSMTool release for OnePlus 8T
Enter in EDL Mode. With the phone connected to a computer running Windows, press volUp + volDown right when you see the Snapdragon logo. The phone will stay with screen off
Follow the usual flashing procedure with MSMTool

Thanks, I just had to install the Qualcomm drivers exe file. After that it appeared in device manager.

Livingsilver94 said:
3. Enter in EDL Mode. With the phone connected to a computer running Windows, press volUp + volDown right when you see the Snapdragon logo. The phone will stay with screen off
Click to expand...
Click to collapse
Nothing happens when i press that. phone keeps on vibrating and flashing the logo
UPDATE: Got a different computer and it worked

Related

Vodafone Smart 4 Mini

I've broken my phone! I was rooted, and was installing a custom rom. It worked fine for a few hours, and now the phone won't boot up in normal, recovery or fastboot modes. All I get is the android logo and then a white screen for a few seconds, and this repeats until i get fed up and turn it off again.
My device is a Vodafone 785 and my pc is running Windows 7 with the latest drivers installed and updated.
When I plug the phone into the computer, it tries to register but the flashtool says the device is not recognized, so I can't re-install my recovery image.
I've been at this for about three weeks now, and I cannot for the life of me figure out how to get this working again. Can someone please help?
coling24 said:
I've broken my phone! I was rooted, and was installing a custom rom. It worked fine for a few hours, and now the phone won't boot up in normal, recovery or fastboot modes. All I get is the android logo and then a white screen for a few seconds, and this repeats until i get fed up and turn it off again.
My device is a Vodafone 785 and my pc is running Windows 7 with the latest drivers installed and updated.
When I plug the phone into the computer, it tries to register but the flashtool says the device is not recognized, so I can't re-install my recovery image.
I've been at this for about three weeks now, and I cannot for the life of me figure out how to get this working again. Can someone please help?
Click to expand...
Click to collapse
Hi, try this:
http://forum.xda-developers.com/android/help/vodafone-smart-4-mini-killed-vodafone-t2869185
Yes I tried that one and most of the other threads about this damn phone. It won't boot in recovery. I've tried Power button and volume up AND Power button and volume down. All I get is android logo for a few seconds and white screen for another few seconds and this will loop until the end of time. Using SP Flashtool, the computer won't recognize the device when I plug in the USB with either the battery removed or inserted into the phone.
coling24 said:
Yes I tried that one and most of the other threads about this damn phone. It won't boot in recovery. I've tried Power button and volume up AND Power button and volume down. All I get is android logo for a few seconds and white screen for another few seconds and this will loop until the end of time. Using SP Flashtool, the computer won't recognize the device when I plug in the USB with either the battery removed or inserted into the phone.
Click to expand...
Click to collapse
Unfortunately, it sounds like the device may be unrecoverable.
I'm not for giving up. Somehow I'll find a way to fix this thing. :fingers-crossed:
coling24 said:
I'm not for giving up. Somehow I'll find a way to fix this thing. :fingers-crossed:
Click to expand...
Click to collapse
Good luck!

[SOLVED] Oneplus 7 can't access Fastboot. Need help with MSM Unbrick tool

So i did something extremely stupid. I flashed an android 9 STOCK ROM while i was in android 10 to fix a magisk and WIFI issue i was having. As a result i cant get into fastboot now and i can only turn the phone on by holding power + volume up button. But doing so only shows the logo for some time which then freezes and the screen goes black. I think the phone has been hard bricked and my only option maybe the unbrick tool. But i can't understand how to use it. I have followed some threads but some of the things aren't adding up. For example in device manager my phone is being detected as Qualcomm HS-USB Diagnostic 900E(COM4) whereas it's supposed to be Qualcomm HS-USB Diagnostic 9008. And also pressing pressing ENUM in the unbrick tool does not detect my device. Any help would be appreciated.
UPDATE : Holding down both volume buttons and power button got me into fastboot mode but the normal way didn't. And from there I discovered I still had stock recovery. I just reset data and everything booted back up properly.
wolfsbane169 said:
So i did something extremely stupid. I flashed an android 9 STOCK ROM while i was in android 10 to fix a magisk and WIFI issue i was having. As a result i cant get into fastboot now and i can only turn the phone on by holding power + volume up button. But doing so only shows the logo for some time which then freezes and the screen goes black. I think the phone has been hard bricked and my only option maybe the unbrick tool. But i can't understand how to use it. I have followed some threads but some of the things aren't adding up. For example in device manager my phone is being detected as Qualcomm HS-USB Diagnostic 900E(COM4) whereas it's supposed to be Qualcomm HS-USB Diagnostic 9008. And also pressing pressing ENUM in the unbrick tool does not detect my device. Any help would be appreciated.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=80011568&postcount=2
_disable driver signature : https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
_update drivers
[ https://www.youtube.com/watch?v=jtc7EhNsfPA&feature=youtu.be ]
_ https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
daitalos said:
https://forum.xda-developers.com/showpost.php?p=80011568&postcount=2
_disable driver signature : https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
_update drivers
[
&feature=youtu.be ]
_ https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
Click to expand...
Click to collapse
I was able to fix the problem. Holding down both volume buttons and power button got me into fastboot mode but the normal way didn't. And from there I discovered I still had stock recovery. I just reset data and everything booted back up properly
wolfsbane169 said:
I was able to fix the problem. Holding down both volume buttons and power button got me into fastboot mode but the normal way didn't. And from there I discovered I still had stock recovery. I just reset data and everything booted back up properly
Click to expand...
Click to collapse
Great to hear that your phone is back!

Bricked...

Please Help Me!:crying:
My 7 Pro has been bricked.
circumstance:
i press VolUp + Power for a while, there are showed <!> screen (= warn for unlocking) only a few seconds.
but fastboot screen is not displayed. black out.
of course, recovery is the same. (black out)
if i connect 7 Pro to a PC, there is a response for a moment, but it does not appear in the device manager (similar things appear in the "Port").
when i flashed
OnePlus7ProOxygen_21.E.15_OTA_015_all_1907281610_e735c0c31ada4eee.zip
and
Magisk-v19.4.zip
from TWRP, It became current state after this operation.
This is the first time such a brick.
Does anyone have the same situation or have a solution?
MtnOrf said:
Please Help Me!:crying:
My 7 Pro has been bricked.
circumstance:
i press VolUp + Power for a while, there are showed <!> screen (= warn for unlocking) only a few seconds.
but fastboot screen is not displayed. black out.
of course, recovery is the same. (black out)
if i connect 7 Pro to a PC, there is a response for a moment, but it does not appear in the device manager (similar things appear in the "Port").
when i flashed
OnePlus7ProOxygen_21.E.15_OTA_015_all_1907281610_e735c0c31ada4eee.zip
and
Magisk-v19.4.zip
from TWRP, It became current state after this operation.
This is the first time such a brick.
Does anyone have the same situation or have a solution?
Click to expand...
Click to collapse
MSMDownload Tool.
That will get you back to a fresh OS.
MtnOrf said:
Please Help Me!:crying:
My 7 Pro has been bricked.
circumstance:
i press VolUp + Power for a while, there are showed <!> screen (= warn for unlocking) only a few seconds.
but fastboot screen is not displayed. black out.
of course, recovery is the same. (black out)
if i connect 7 Pro to a PC, there is a response for a moment, but it does not appear in the device manager (similar things appear in the "Port").
when i flashed
OnePlus7ProOxygen_21.E.15_OTA_015_all_1907281610_e735c0c31ada4eee.zip
and
Magisk-v19.4.zip
from TWRP,It became current state after this operation.
This is the first time such a brick.
Does anyone have the same situation or have a solution?
Click to expand...
Click to collapse
I actually also bricked mine today and also had to use the msm download tool.
It was fairly easy and I was happy with the process.
No worries ?
tech_head said:
MSMDownload Tool.
That will get you back to a fresh OS.
Click to expand...
Click to collapse
Device manager shows "Qualcomm HS-USB Diagnostics 900E(COM5)".
so(?) there are no responses in MSM tool.
schorrie said:
I actually also bricked mine today and also had to use the msm download tool.
It was fairly easy and I was happy with the process.
No worries
Click to expand...
Click to collapse
thanks.
but, ,my device manager shows "Qualcomm HS-USB Diagnostics 900E(COM5)".
so(?) there are no responses in MSM tool.
Do I need to use an EDL cable...?
I had this exact same problem last night. Plug it in via USB and make sure you have volume on your speakers. Press and hold volume up, down and power and for some reason the bootloader will come up. Pick power off, then press volume up and down at the same time and plug your USB cable into the phone and listen for the connection sound.

Neffos X-1 stuck in bootloop

Heya folks,
I have just attempted my first time flashing TWRP on my TP-Link Neffos X-1 following this guide: https://rootmygalaxy.net/twrp-root-...nd_Install_TWRP_Recovery_On_TP-Link_Neffos_X1.
Its looking kinda grim. It starts with the orange state Message and that the device will boot in 5 seconds, however after that it starts with an infinite bootloop. I also cannot access the Recovery (vol up + power), for it simply doesnt work anymore after the guide. When I plug it into my pc, it will automatically start with the bootloop (I can shut the phone off with vol down + power).
Attempting to get into fastboot mode over ADB (adb reboot bootloader), returns with the message error: device '(null)' not found. I think that is due to it not being recognized in the device manager(it doesnt show my phone anymore but unknown device). I tried to install the phone driver for the uknown device, however that keeps failing. I think its due to the phone permanently connecting and reconnecting to the pc.
So I'm wondering of what to do. I guess the biggest issue is that the drivers are not recognized, but as long as the phone keeps on restarting every couple of seconds i doubt i can properly install the driver. You guys got any ideas?
My guess is you haven't installed on Windows PC the appropriate Android USB Driver matching the device
I mean the appropriate USB driver had to be there for me to flash it with the TWRP in the first place, right?
Think I clearly said that the additionally required USB-driver has to be installed on Windows PC.
I have this one installed https://rootmydevice.com/download-neffos-usb-drivers/, is this the additionally required usb driver?
So far, despite what driver I pick for the device, it shows the code 10, device couldnt be started - probably because it never gets past the starting screen but keeps rebooting
slayingduck said:
Heya folks,
I have just attempted my first time flashing TWRP on my TP-Link Neffos X-1 following this guide: https://rootmygalaxy.net/twrp-root-...nd_Install_TWRP_Recovery_On_TP-Link_Neffos_X1.
Its looking kinda grim. It starts with the orange state Message and that the device will boot in 5 seconds, however after that it starts with an infinite bootloop. I also cannot access the Recovery (vol up + power), for it simply doesnt work anymore after the guide. When I plug it into my pc, it will automatically start with the bootloop (I can shut the phone off with vol down + power).
Attempting to get into fastboot mode over ADB (adb reboot bootloader), returns with the message error: device '(null)' not found. I think that is due to it not being recognized in the device manager(it doesnt show my phone anymore but unknown device). I tried to install the phone driver for the uknown device, however that keeps failing. I think its due to the phone permanently connecting and reconnecting to the pc.
So I'm wondering of what to do. I guess the biggest issue is that the drivers are not recognized, but as long as the phone keeps on restarting every couple of seconds i doubt i can properly install the driver. You guys got any ideas?
Click to expand...
Click to collapse
Try this TWRP file: TWRP_3.2.3_NeffosX1_TP902A_by_kiruha_21.img
The thing is, I cannot flash anything due to my phone constantly rebooting while inserted in the pc usb-slot. Neither ADB nor my device manager recognize the device and as mentioned before, I cannot install any drivers
slayingduck said:
The thing is, I cannot flash anything due to my phone constantly rebooting while inserted in the pc usb-slot. Neither ADB nor my device manager recognize the device and as mentioned before, I cannot install any drivers
Click to expand...
Click to collapse
Some MTK devices has this: Press both VOL+ & Power buttons. Only remove 2 buttons when you see Bootloader mode (recovery; fastboot; reboot system) or directly in the Recovery mode. Now you can use fastboot.
With the SPFT you can use same tip above. In the SPFT choose DOWNLOAD and plug USB device. Process to flash stock ROM or stock recovery.img & boot.img start.
If not start pugging USB: choose DOWNLOAD - press VOL- and plug USV device. You can try with buttons like only VOL- or VOL+ or combo buttons VOL+&VOL- or VOL-&VOL+ or other button combination.
You can try FIRMWARE UPGRADE too.
That's depend about LOCKED or Unlocked bootloader process that you made before actions!
If you unlocked bootloader so only need patience. If not so that's no good.

Bootloop after trying to install LineageOS 18.1

Hi,
I'm having troubles after following the guide here - https://wiki.lineageos.org/devices/guacamole/install
I initially had stock Android 11 with latest update. I've followed the instructions, all went well until I rebooted to system. It just tries to boot for a few minutes, then it restarts and does this again. Doesn't seem to boot.
Is there a way to fix this?
Also, would be possible to get back to stock rom and how?
Thank you in advance!
Managed to fix, in the end. Was a real headache.
If anyone is having similar problem and they have to unbrick their phone, I suggest this thread - https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.3954325/
Follow the steps in that thread. To enter EDL mode, you will have to turn off your device, hold Volume UP and Volume down (without power button) and while holding insert the USB cable into the phone and into your PC. By doing so, it will be detected by the computer and will show up in Device Manager.
The most annoying issue I had was the phone was connecting for a few seconds, then disconnect. What worked for me after many many tries was using a newer image, mine being an international device I used 10.3.8. I opened MSM from the 10.3.8 package and Device Manager, connected the cable to the computer, but not to the phone, I've pressed volume up and down, connected the cable to the phone while holding volume buttons and as soon as Qualcom driver showed up in Ports (COM & LPT), I hit start on MSM.
If it still gives you the error "Sahara Communication Failed. Please try again after power off phone" try with a different package version, for me this one worked, but before that I've tried with a different one and I was getting this error.
Hope it will help someone, at some point. I know how frustrating it is and if I helped you be less frustrated than I was, that's a win.

Categories

Resources